wamdam / backy2

backy2: Deduplicating block based backup software for ceph/rbd, image files and devices
http://backy2.com/
Other
192 stars 39 forks source link

Documentation is unclear #80

Open pertoft opened 3 years ago

pertoft commented 3 years ago

Hi,

I am trying to use Backy2 to perform scheduled backups of Ceph RBD volumes.

I have extended the incremental backup example script to tag each backup with an e.g. hourly tag. Full: backy2 backup -t "$TAG" -s "$SNAPNAME" -r "$TEMPFILE" rbd://"$POOL"/"$VM"@"$SNAPNAME" $VM Incremental: backy2 backup -t "$TAG" -s "$SNAPNAME" -r "$TEMPFILE" -f "$BACKY_SNAP_VERSION_UID" rbd://"$POOL"/"$VM"@"$SNAPNAME" "$VM"

This will create and initial full backup and incremental backups.

Now if I want to schedule the backups, i need to run a scheduled script. Looking at the example: https://github.com/wamdam/backy2/blob/master/demo/backup.sh

The script should run a backy2 due -s "schedule" Example: `root@os-backup:~/backy2# backy2 due -s hourly INFO: [backy2.logging] $ /usr/bin/backy2 due -s hourly +---------------------------------------------+------------+---------------------+ | name | schedulers | expire_date | +---------------------------------------------+------------+---------------------+ | volume-14208e3d-7196-4f3a-9aa2-a070e8eb5428 | hourly | 2020-11-24 13:47:33 | +---------------------------------------------+------------+---------------------+ INFO: [backy2.logging] Backy complete.

root@os-backup:~/backy2#`

Now it become unclear as the example does not contain a source volume name.

Should the script run a backy2 backup "volume-name" -t "TAG" -e "Expire ts" for each volume? Or is there a clever way to do it for all expired tags? Why shall the tag and expire be appended again?

It would be really nice with a clarification in the docs.