Hello folks,
Looking for ways to reduce RPO on our backup jobs (latest VBR build backing up VMware VMs using storage snapshots and CBT), our traditional backup jobs run once a day at a specific time, and when they complete, secondary target jobs are at play, specifically tape backup. This works great and is a very solid B2D2T process, the forever incremental B2D job takes 1 hour, and the B2T job takes about 10 hours (daily synthetic full tape).
Since the backup to disk job takes an hour, I can in theory schedule it to run more frequently, thus improving my backup job RPO.
If I were to try and flip the backup job to use continuous backup schedule, the tape job AFAIK would never run because the job "never ends", one could make use of schedule option (time periods) to set permitted/denied windows, so that the continuous B2D would run at a fixed time, every 2 hours as an example.
The question then is, what happens to the in-progress tape job that can take 10 hours to complete, if the backup job tries to run again, before the last tape job completes?
Maybe I am over complicating this, given the relatively quick B2D job that has a quite long B2T job linked to it, how does one improve on the RPO on the backup job itself?
Looking for ways to reduce RPO on our backup jobs (latest VBR build backing up VMware VMs using storage snapshots and CBT), our traditional backup jobs run once a day at a specific time, and when they complete, secondary target jobs are at play, specifically tape backup. This works great and is a very solid B2D2T process, the forever incremental B2D job takes 1 hour, and the B2T job takes about 10 hours (daily synthetic full tape).
Since the backup to disk job takes an hour, I can in theory schedule it to run more frequently, thus improving my backup job RPO.
If I were to try and flip the backup job to use continuous backup schedule, the tape job AFAIK would never run because the job "never ends", one could make use of schedule option (time periods) to set permitted/denied windows, so that the continuous B2D would run at a fixed time, every 2 hours as an example.
The question then is, what happens to the in-progress tape job that can take 10 hours to complete, if the backup job tries to run again, before the last tape job completes?
Maybe I am over complicating this, given the relatively quick B2D job that has a quite long B2T job linked to it, how does one improve on the RPO on the backup job itself?
Statistics: Posted by cerberus — Jul 14, 2025 11:42 pm
