As Marco said, the first fact is that you can do this only for standard filesystem backups because vm backups are always incrementals.
The second issue is that it is a pain to set this up. I am pretty sure that sooner or later you will be confused because there is no straight way to follow. As Marco said, the best way is to use a short retention for the backup policy/workflow and use clone jobs (prefered: scripted) which you run on a daily base to copy the full save sets to a volume pool with a longer retention. Such will also speed up potential recover processes.
actually I can only suggest to use multiple workflows and each can be assigned to a different group, and use the different specification in the workflow.
Also with vm backup you can actually perform always incremental if you use the CBT+ Data Domain, the image is reconstructed and indexed using the changed blocks. And if you need a copy for long retention you can always perform a clone (even to other kind of devices), since the data should be rehydrated in the clone process.
ivanst007
2 Posts
0
December 22nd, 2020 04:00
I understand that there is a way to do that for normal Clients but for VMware Clients, I haven't been able to find any information.
bingo.1
2.4K Posts
1
December 22nd, 2020 07:00
As Marco said, the first fact is that you can do this only for standard filesystem backups because vm backups are always incrementals.
The second issue is that it is a pain to set this up. I am pretty sure that sooner or later you will be confused because there is no straight way to follow. As Marco said, the best way is to use a short retention for the backup policy/workflow and use clone jobs (prefered: scripted) which you run on a daily base to copy the full save sets to a volume pool with a longer retention. Such will also speed up potential recover processes.
Marco.Ceruti
1 Message
1
December 22nd, 2020 07:00
Hello,
actually I can only suggest to use multiple workflows and each can be assigned to a different group, and use the different specification in the workflow.
Also with vm backup you can actually perform always incremental if you use the CBT+ Data Domain, the image is reconstructed and indexed using the changed blocks. And if you need a copy for long retention you can always perform a clone (even to other kind of devices), since the data should be rehydrated in the clone process.
Regards,
Marco