PBS sze of itemplate/vzdump
- Thread starter TErxleben
- Start date
I find that hard to believe. VZDump also works with compression. So, it should be at least less than 16 TB. The question is more about how efficiently the data of an initial VM can be compressed. As an example, let's take a Windows VM I used, whose outrageous storage requirements in the backup can be reduced by 20%+ using sdelete within the VM.
Or have you actually tried it and backed up elicitly without compression?
Or have you actually tried it and backed up elicitly without compression?
You did not say anything about the kind of the data. So we need to calculate with "backups of your vacation videos" - which are usually not compressible, as they are already compressed.
In that case @news is absolutely right.
In the context of PVE and VMs the result is smaller than 16 TB because the disk images are compressible and are usually not nearly full.
But at the same time I would never go back to classic vzdump. PBS exists for a reason. For your 16 TB example: perhaps you can store two backups of that 16 TB source onto one 16 TB destination medium. With PBS and with my actual data I could store more than 50 backups of the 16 TB source on that 16 TB destination. (My dedup factor lies between 25 and 35, daily backup.)
----
Edit: if you are talking about an empty VM, just to evaluate the overhead: why not go and test it? I am keen to see your result
Last edited:
I specifically mentioned a newly created PBS VM. It's obvious that a populated PBS VM is virtually impossible to compress (just like already compressed data of any format).
That's precisely why I expect a VZDump file of the size: BootDisk (minus free space) + a minimal surcharge for a completely empty data partition, regardless of size.
I only want to use the backup as a stopgap for a configured PBS, without storing gigantic amounts of dead/empty data.
Or to easily make a new, already configured, empty PBS available annually.
P.S.: VZDump files do have the advantage of being able to be restored without overhead. However, at 10TB+, this becomes less and less practical.
That's precisely why I expect a VZDump file of the size: BootDisk (minus free space) + a minimal surcharge for a completely empty data partition, regardless of size.
I only want to use the backup as a stopgap for a configured PBS, without storing gigantic amounts of dead/empty data.
Or to easily make a new, already configured, empty PBS available annually.
P.S.: VZDump files do have the advantage of being able to be restored without overhead. However, at 10TB+, this becomes less and less practical.
Last edited: