VEEAM - Forward Incremental and Cloud Storage

[CHiLL]

We've been using reverse incremetal backups for years now and the processing rate is much slower as it performs 3 I/O operations per data block compared to Forward Incremental's 1 I/O per data block. The reason we use reverse incremental is because the latest backup file is the full backup, which can easily be copied off, along with the metadata file to somewhere else, including cloud locations. So I don't need to copy the incremental files as well.

 

My understanding is that if I wanted to store copies of the forward incremental data of say last night, I'd have to copy the earliest full backup file and all subsequent incremental files as well to my other/cloud storage. Is that correct? Because that's ultimately much more data than copying the reverse backup file.

 

I'm trying to weigh up on-site backup performance vs ease of off-site backup/time.

 

Note: We use scripts/rclone to copy the data from our on-site repository to cloud locations, so we don't use any VEEAM features to do it.

[sparkeh]

My understanding is that if I wanted to store copies of the forward incremental data of say last night, I'd have to copy the earliest full backup file and all subsequent incremental files as well to my other/cloud storage. Is that correct?

 

Correct... but you could look at efficiency of creating synthetic full backups and copying those offsite compared to the reverse incremental solution.

 

Because that's ultimately much more data than copying the reverse backup file.

Yep if are copying the first backup and all the increments but again look at the synthetic backup idea.