designing backup env with immutable. Copy reg backup copies

[galbitz]

Hello,

We are going to be redesigning our backup environment.

The goal is to have an immutable linux repo at our main location as the sole repo there. I have used these in the past and I am fairly comfortable with the setup of that repo.

We also want to perform a backup copy job to a second DR site, and run replication from backup jobs there. We will have a second repo at the DR site, likely not immutable but I am open to a conversation about that. The plan was to run a single instance of veeam at the DR location. We would have proxies/wan accelerators throughout.

My question/concern is the following:

We backup a few large vms, our prod oracle database is a 9tb VM. We seed this before starting the backup copy relationship today absent the immutable repo.

Are there any gotchas/should we be concerned about the fact that the linux immutable repo at the main site is going to require a synthetic full periodically (our retention to date is very low, 7 days currently). My concern is that synthetic active full may create a file too large to process over the wan for the backup copy job. Perhaps I am misunderstanding the resulting file from that process, but I am concerned it would throw our backup copy schedules into a bad situation. If it is a problem, what would be the recommended solution to work around this?

[PetrM]

Hi Grant,

Backup copy does not transfer just backup files but syncs the actual state of data from the primary repository to the secondary one. Thus, only new data blocks must be copied to the secondary repository even after synthetic full. Therefore, I wouldn't expect any issues and I don't think that you should seek for some special workarounds.

Thanks!