backup change tracking for same vm in different policies

[sanath.g@infosys.com]

we want 2 policies, 1 policy will backup with weekly full and daily incrementals for archival to cloud and second policy will backup with weekly full and hourly incremental without any archival to cloud

we will configure weekly full on different days, but will the jobs be smart enough to recognize what data is to be copied when on different policy schedules?

[Mildur]

Hello Sanath

Why not using a single job with the weekly full and hourly incremental. Then use a backup copy job from type "periodically" to copy the latest restore point once per day to the cloud (object storage or cloud connect).

Please consider you will have chains of 1 full and 167 increments. I suggest to think about which VMs would require hourly backups and which are not. Then create two jobs. Some workloads such as DNS server or terminal server (example: citrix) may only require one backup per day.

Best,
Fabian

[sanath.g@infosys.com]

This is a business requirement. Can you please tell me if there are two policies for same VM how will incremental backups track the backup changes in their respective policies?

[Mildur]

Hi Sanath

CBT is tracked via hidden snapshots. Those snapshots are called backup snapshots. You won't see them in the UI.
Each backup job creates it's own backup snapshot. During the next backup job session, a new backup snapshot is created. Our proxy will compare the difference between the new backup snapshot and the previous backup snapshot. This allows us to only read changed blocks.
You can read more about it here:
https://helpcenter.veeam.com/docs/vbahv ... tml?ver=40

While you don't see the snapshots in the console, you can see them when doing a restore of the VM. You can use the snapshot not only for CBT information, it can also be used as a restore point for the restore:


Best,
Fabian