Incremental daily & Full daily backup

eye4eye · 2018-09-18 14:07:53

Currently, we have a daily incremental backup running on a host. We would like to add a full daily backup to it. We are using --backup-prog=onediff for the incremental backup.

After completion of incremental backup, it creates a _XSIBAK file in VMware. Can the incremental & full backup be stored as two separate _XSIBAK files, within VMware? Or, will they overwrite each other?

Our current working cron script (Please note, using xxx- for security):
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backup-prog=onediff --time="Mon 05:00|Tue 05:00|Wed 05:00|Thu 05:00|Fri 05:00|Sat 05:00|Sun 05:00" --backup-point="/vmfs/volumes/HONEY120" --backup-type=custom --backup-vms="pdf" --mail-from=120@xxx --mail-to=xxx@xxx --smtp-srv=192.168.xxx.xxx --smtp-port=25 --smtp-usr=xxx@xxx --smtp-pwd=xxx --smart-info=yes

How do we add a second full daily backup to it?

Please let me know if you need more info.

admin · 2018-09-18 14:57:07

(c)OneDiff generates a mirror image and leaves a snapshot called xsibackupdiff hanging off the base disks
You can then configure a second Vmkfstools backup that backs up the same VM fully, cloning the VM from the hanging snapshot xsibackupdiff, which will in turn generate a new VM which will encompass the before mentioned snapshot.

Once the Vmkfstools finishes, the Virtual Machine is left at the point where the subsequent OneDiff cycle can re-take the job where the previous OneDiff cycle left it, namely with a snapshot called xsibackupdiff that includes al writes since the previous OneDiff backup.

Once you have configured such Vmkfstools backup, just chain it to the first one by using the --on-error and --on-success arguments on the first OneDiff backup.

If you backup to different paths, the VM folder, which never includes the suffix _XSIBAK, this is something that only appears in the VM name inside the .vmx file, will not be overwritten.

eye4eye · 2018-09-19 13:08:19

Our current working cron script for backing a host with 2 VMs:
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=01 --backup-prog=onediff --time="Mon 17:00|Tue 17:00|Wed 17:00|Thu 17:00|Fri 17:00|Sat 17:00|Sun 17:00" --backup-point="/vmfs/volumes/datastoreA" --backup-type=custom --backup-vms="vm_01" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx -- smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes --on-success="backupid->02" --on-error="backupid->02"
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=02 --backup-prog=onediff --backup-point="/vmfs/volumes/datastoreA" --backup-type=custom --backup- vms="vm_02" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx --smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes

Would I add at end:
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=01 --backup-prog=onediff --time="Mon 17:00|Tue 17:00|Wed 17:00|Thu 17:00|Fri 17:00|Sat 17:00|Sun 17:00" --backup-point="/vmfs/volumes/datastoreA" --backup-type=custom --backup-vms="vm_01" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx -- smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes --on-success="backupid->02" --on-error="backupid->02"
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=02 --backup-prog=onediff --backup-point="/vmfs/volumes/datastoreA" --backup-type=custom --backup- vms="vm_02" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx --smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes --on- success="backupid->03" --on-error="backupid->03"
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=03 --backup-prog=all --backup-point="/vmfs/volumes/datastoreB" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx --smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes

Please note, for the full daily backup, it HAS to be to a different path? What would happen, if I point it to datastoreA as well? Would it overwrite everything in datastoreA, or would it make a new folder (can we name this folder), since it's using --backup-prog=all
We would like to keep it in the same path, since this is one of many hosts that we backup daily. Obviously, adding a full backup, will increase total backup time.

Also, we would like the full backup to be on 3 rotations. Overwriting the oldest full backup on the third day's full backup schedule. How would we do this? What is the script to do so? Please advise.

Thank you.

admin · 2018-09-19 14:42:43

The backup jobs you are posing are different than the jobs proposed from our part. You are using --backup-prog=onediff on the backupId=02 when you should be using vmkfstools, as we state in our previous post. You cannot have a OneDiff backup being made to two different locations on the same VM, but you can have a OneDiff job plus a vmkfstools one.

Of course it has to be a different path. What happens when you copy one thing to the same path?, you clearly overwrite the previous data.
You cannot overwrite a backup on the third day, you can nevertheless delete the eldest backups after a given number of days to make room.

https://33hops.com/xsibackup-help-man-page.html#deldirs

We have moved this topic, you posted in the XSIBACKUP-FREE forum, when the arguments discussed are only available in the Pro version.

eye4eye · 2018-09-19 20:03:39

Thanks for reply. Please note:
1) Host has two VMs
2) Want to do incremental on each VM daily to datastoreA
3) Want to do full backup on host daily to datastoreB
4) Want to keep three rotations of full backups (delete folder older than 2 days)

Is this correct?

/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=01 --backup-prog=onediff --time="Mon 17:00|Tue 17:00|Wed 17:00|Thu 17:00|Fri 17:00|Sat 17:00|Sun 17:00" --backup-point="/vmfs/volumes/datastoreA" --backup-type=custom --backup-vms="vm_01" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx -- smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes --on-success="backupid->02" --on-error="backupid->02"
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=02 --backup-prog=onediff --backup-point="/vmfs/volumes/datastoreA" --backup-type=custom --backup- vms="vm_02" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx --smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes --on- success="backupid->03" --on-error="backupid->03"
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=03 --backup-prog=vmkfstools --backup-point="/vmfs/volumes/datastoreB" --backup-type=all --del-dirs=+2d --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx --smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes

admin · 2018-09-20 14:06:43

First of all, please, upgrade to version 11.0.3 if you have the chance. It's a lot more advanced and stable in regards to backup chaining. In fact, you cannot use --del-dirs=+2d in older versions.

What you pose is correct, but: why do you split backup 01 and 02?, wouldn't it be easier to group VMs and write this instead:

/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=01 --backup-prog=onediff \
--time="Mon 17:00|Tue 17:00|Wed 17:00|Thu 17:00|Fri 17:00|Sat 17:00|Sun  17:00" \
--backup-point="/vmfs/volumes/datastoreA" --backup-type=custom --backup-vms="vm_01,vm_02" \
--mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx -- smtp-port=xxx --smtp-usr=xxx \
--smtp-pwd=xxx --smart-info=yes --on-success="backupid->02" --on-error="backupid->02"

eye4eye · 2018-09-24 15:42:23

Upgraded to 11.0.3
We tested on a host with just one VM. We decided to backup to a subfolder in same path. The thinking is that we want to keep the backups under same datastore, because we have multiple hosts to run backups for (once our test backup cron works)
- One incremental backup to subfolder in /vmfs/volumes/datastoreA/pdf_incremental
- One full backup to subfolder in /vmfs/volumes/datastoreA/pdf_full

/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=01 --backup-prog=onediff --time="Mon 05:00|Tue 05:00|Wed 5:00|Thu 5:00|Fri 5:00|Sat 05:00|Sun 05:00" --backup-point="/vmfs/volumes/datastoreA/pdf_incremental" --backup-type=custom --backup-vms="vm_01" --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx --smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes --on-success="backupid->02" --on-error="backupid->02"
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backupid=02 --backup-prog=vmkfstools --backup-point="/vmfs/volumes/datastoreA/pdf_full" --backup-type=all --del-dirs=+2d --mail-from=xxx --mail-to=xxx --smtp-srv=192.168.xxx.xxx --smtp-port=xxx --smtp-usr=xxx --smtp-pwd=xxx --smart-info=yes

When run, the incremental seems fine (no errors detected in log). However, the full doesn't seem to run at all. What is wrong with the syntax? Can we not backup to a subfolder in same path?

Also, please note, the --del-dirs=+2d option was introduced in 10.2.9, at least according to https://33hops.com/xsibackup-help-man-page.html#deldirs
We were on 10.3.1, before the upgrade.

Thanks for your advice.

admin · 2018-09-26 08:52:15

Please, note that since v 11.0.0 the way the cron works has changed. Changes are explained in detail here:

(c)XSIBackup Classic: changes in version 11.0.0

If --backupid=01 is working, it's just because you are still keping the old cron redirection to xsibackup-cron in the /var/spool/cron/crontabs/ file.

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

#1 2018-09-18 14:07:53

Incremental daily & Full daily backup

#2 2018-09-18 14:57:07

Re: Incremental daily & Full daily backup

#3 2018-09-19 13:08:19

Re: Incremental daily & Full daily backup

#4 2018-09-19 14:42:43

Re: Incremental daily & Full daily backup

#5 2018-09-19 20:03:39

Re: Incremental daily & Full daily backup

#6 2018-09-20 14:06:43

Re: Incremental daily & Full daily backup

#7 2018-09-24 15:42:23

Re: Incremental daily & Full daily backup

#8 2018-09-26 08:52:15

Re: Incremental daily & Full daily backup

Board footer