This is what my vzdump default settings look like:
When I then run vzdump 102, this happens:
No backup is made and it seems the error starts with pigz. Any ideas? I really want to use pigz for backups and restoring as it should be much faster, I have plenty of threads to spare.
Code:
#vzdump default settings
tmpdir: /tmp
dumpdir: /mnt/pve/synology/dump
#storage: STORAGE_ID
mode: snapshot
compress: gzip
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#size: MB
#stdexcludes: BOOLEAN
#mailto: ADDRESSLIST
maxfiles: 2
#script: FILENAME
#exclude-path: PATHLIST
pigz: 1When I then run vzdump 102, this happens:
Code:
root@proxmox:/# vzdump 102
INFO: starting new backup job: vzdump 102
INFO: Starting Backup of VM 102 (qemu)
INFO: status = running
INFO: update VM 102: -lock backup
INFO: VM Name: docker
INFO: include disk 'virtio0' 'vol1:vm-102-disk-0' 512G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating archive '/mnt/pve/synology/dump/vzdump-qemu-102-2019_03_05-21_06_10.vma.gz'
Can't exec "pigz": No such file or directory at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 373.
ERROR: fork compressor 'pigz -p 6' failed
INFO: started backup task 'a11cec85-104c-4fc1-b05e-bdb18f6fda76'
INFO: status: 0% (3801088/549755813888), sparse 0% (995328), duration 0, read/write 3/2 MB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
ERROR: Backup of VM 102 failed - vma_queue_write: write error - Broken pipe
INFO: Backup job finished with errors
job errorsNo backup is made and it seems the error starts with pigz. Any ideas? I really want to use pigz for backups and restoring as it should be much faster, I have plenty of threads to spare.
