Hi there,
I tried to backup my VMs via duply after stopping them and restarting afterwards but my upload speed is too slow to do it this way.
My next approach is to use vzdump with suspend then fire up the VM again and then run duply to backup the backup that vzdump generated.
Since duply does only upload the parts that have changed, I need to keep the backup to use the same file name but apparently vzdump can't do this. I
duply has a "pre" script that runs before the backup and I was planning to insert a command like this:
but that results in a file that contains the date.
Would this be a workaround?
I've disabled compression since that would affect duply's ability to diff the file.
I tried to backup my VMs via duply after stopping them and restarting afterwards but my upload speed is too slow to do it this way.
My next approach is to use vzdump with suspend then fire up the VM again and then run duply to backup the backup that vzdump generated.
Since duply does only upload the parts that have changed, I need to keep the backup to use the same file name but apparently vzdump can't do this. I
duply has a "pre" script that runs before the backup and I was planning to insert a command like this:
Code:
vzdump 100 -compress 0 -storage /root/vzdump
but that results in a file that contains the date.
Would this be a workaround?
Code:
vzdump 100 -compress 0 > /root/vzdump/vzdump-VM-ID-100
I've disabled compression since that would affect duply's ability to diff the file.