![]() Are there any other considerations, or arguments for or against changing to reverse incremental in this case. Would changing to reverse incremental be an issue, in terms of "best practice"? The backup jobs are configured to use Veeam's compression and deduplication, so there is no overhead on the storage device itself in that regard (which I know would be a strong indication against moving to Reverse). ![]() In order to achieve our aim do we need to change to Reverse Incremental or is there some "Veeam magic" that would create a full backup on the tape each day but leave the disk backup as-is (don't want additional fulls on the disk storage of course, due to space). We would like the daily tape backup to be a full backup of the environment, but of course at the moment the Veeam job creates an incremental backup each day (and a synthetic full once a week). We are currently backing up a number of VMs daily to disk, using a Forward Incremental chain, and are in the process of implementing a tape server so we can copy the backups to tape each day for offsite.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |