Please review the thread for the comprehensive explanation.owenwalker.bc wrote:Now where I'm not sure is best practise with running active full backups. I've seen information stating it's good to run a active full backup every 1-3 months when using reverse incremental, also seen information stating you don't need to run active full backups with later Veeam versions.
owenwalker.bc wrote:I'm also not sure exactly how the active full works. Does it create a completely seperate full backup, thereby requiring the full size of the VM x2. Or does it work by creating the incremental changes for the previous night. And then doing a fresh overwrite of the latest reverse backup?
Shestakov wrote:Do you use Surebackup?
Shestakov wrote:It creates a newly VBK file from the scratch. No incremental changes used. It requires 2x of the Full backup file, not VM size. Backup size is much lower than VM size due to compression.
I would emphasize that it`s recommended to keep a short chain on the primary repository for faster restores and longer chain on the secondary repository for restores of historical data.
is it true that a copy-job also protects you against bitrot, because the copy job compares it's data to the data from the backup job?
Totally true, and it's the main advantage of backup copy job compared to storage replication
Users browsing this forum: Bing [Bot] and 1 guest