Changing vzdump backend (adding a new archiver9

[fcorbelli]

Is there a 'simple' way to add a different archiver in vzdump, for a GUI-started backup?

Maybe with this "thing" ?

  --script <string>
           Use specified hook script.

What I want to do is to use an archiver with deduplication (zpaq) to store the various versions of backups in a single file
Thanks for any reply!

 

[fabian]

a hookscript can be used for backup archive postprocessing (e.g., some people use it to move the backup archives somewhere else). manually compressing the tar files there should also work - but note that there is no inverse pre-restore hookscript, so anything not supported by PVE requires extra steps by the admin in that case.

 

[Dunuin]

Did you have look at the proxmox backup server? That already comes with deduplication built-in.

 

[fcorbelli]

Did you hve look at the proxmox backup server? That already comes with deduplication built-in.

A good product, but way too complex for my (small) requirements

 

[fcorbelli]

a hookscript can be used for backup archive postprocessing (e.g., some people use it to move the backup archives somewhere else). manually compressing the tar files there should also work - but note that there is no inverse pre-restore hookscript, so anything not supported by PVE requires extra steps by the admin in that case.

I was assuming something like that, but I wasn't sure.
I will certainly make a crontab for backups, but it would have been very convenient to be able to do it from the GUI
Is there a 'simple' way to enrich the packaging (I suppose with an actual script or something) of vzdump?
How is it 'launched' from the GUI?

 

[fcorbelli]

I want to do "something" like that (just a snippet!)

zfs destroy  zp0/zd0@franco
zfs snapshot zp0/zd0@franco
zpaqfranz a /backup/200.zpaq /var/lib/vz/.zfs/snapshot/franco/images/200
zfs destroy  zp0/zd0@franco

 

[fabian]

no, there isn't, short of patching with all the downsides that come with such an invasive approach..

 

[fcorbelli]

So sad, I will need to make 'my' fvzdump (better a proxbackup inside zpaqfranz)

What, exactly, is needed for a backup?
Ok, the vmdks, raw, whatever virtual drives
What else?
Everything in var lib vz?
Thanks!

Ps is it possible to make a "fake" vzdump? Aka: do nothing but just run the hook?

 

[fabian]

I would not go down that path unless you are prepared to spend some time getting to know how everything works and is connected under the hoods. there's almost nothing worse than an unknowingly incomplete backup..

 

[fcorbelli]

I absolutely agree, and in fact I wrote my own little softwarefor storing zfs datasets at the bit level (zfs send), as well as at file livel.
Fortunately vzdump seems easy to modify, I think I'll "hack" just that (i.e. make an evolved version of it)

What I don't know is whether proxmox 'hides' outside the zfs partition (i.e. in the system partition, formatted ext4 to be clear) any kind of information useful for recovery.
It shouldn't, but I'm more of an ESXi/Virtualbox admin than proxmox

Assuming (no matter what) I can restore the entire contents of the zfs partition, is that enough?

Thanks for the help

 

[Dunuin]

Assuming (no matter what) I can restore the entire contents of the zfs partition, is that enough?

You still need stuff like the guests config file stored in /etc/pve/lxc or /etc/pve/qemu-server.

 

[fcorbelli]

I assumed in fact that it was not that simple