Hi cerebus,
I think what's missing in your understanding is the space savings from Fast Clone which creates "spaceless" Synthetic Full backups. So only the space for an increment is _required_, if a block is eligible to be fast cloned, it will be fast clone'd as opposed to copying the block into the Synthetic Full backup.
Either solution above works; Virtual Fulls with Tape are in most cases the fastest way to put a full backup on tape, and you could do this with the first solution Hannes suggested (Forever Forward Incremental for your source jobs, schedule Virtual Fulls as desired). I think this is likely best bet for most environments.
Also, regarding the use-case of daily fulls to tape with Reverse Incremental, this use case is not lost on us and there are plans to address this "soon to be lost" use case and ensure daily fulls on tape, so stay tuned; either solution above is fine for now however and will achieve the same goal as Reverse Incremental + daily fulls to Tape.
I think what's missing in your understanding is the space savings from Fast Clone which creates "spaceless" Synthetic Full backups. So only the space for an increment is _required_, if a block is eligible to be fast cloned, it will be fast clone'd as opposed to copying the block into the Synthetic Full backup.
Either solution above works; Virtual Fulls with Tape are in most cases the fastest way to put a full backup on tape, and you could do this with the first solution Hannes suggested (Forever Forward Incremental for your source jobs, schedule Virtual Fulls as desired). I think this is likely best bet for most environments.
Also, regarding the use-case of daily fulls to tape with Reverse Incremental, this use case is not lost on us and there are plans to address this "soon to be lost" use case and ensure daily fulls on tape, so stay tuned; either solution above is fine for now however and will achieve the same goal as Reverse Incremental + daily fulls to Tape.
Statistics: Posted by david.domask — Jun 27, 2025 9:46 am
