We are looking to use Veeam for backup and replication (to DR site). The interface was a little different to what I imagined though and it's causing a little stress. I imagined that the backed up data would be replicated post processing. Essentially I wanted a full repositry of backups here on the main site, and the ability to extract backups at the DR site when necessary.
We only have a small pipe (30Mb/s) to the DR site and many TB's of data.
I have kicked off a full backup using CBT and I can now see the backups on my local server, great! Now I want to replicate it! So I made a replication job, and instead of asking which backups do I want to replicate, it offers me the VC and guests. So my 1st question is, where does the replication pull the data from, is it from the live servers or Veeams backup repository ?
My 2nd question is if it is replicating from the live servers and it is running as a separate job from the backup, will this messup the CBT as we have two jobs both with independent backups going (one a straight backup, one is a replication) both which use CBT independently....?
My final question (I'm sure its been asked before - I have looked!)
Is it recommended to "backup" the backup server to the DR site? I mean if CBT is used and the filesystem of the 1st backup file system is de-duping (I read in a state of flux every backup when it optimises itself) does this mean that even small updates to the 1st server will cause a lot of changes in the "backup" of the backup server? I am trying to minimise any bandwidth usage
The way I am understanding it at the moment is that Veeam is very good at backup and it is very good at replication but it falls down when trying to replicate the backups?