Comprehensive data protection for all workloads
Post Reply
Posts: 55
Liked: never
Joined: Sep 23, 2010 2:36 pm
Full Name: George Kenny

Backup & Replication @ same time . . . Version5

Post by egroeg »

We have a customer who is currently using veeam version 5 and simply using it to conduct backups to a separate store from which they can use veeam VPower to boot these vms if necessary.

Now they want to look at replicating their server estate to a DR site using the Replication features but without impacting their local backup schedule.

Do we need to issue a separate veeam licence so that the replication aspect of their demands can take place in-line with the backups – and if so, what happens if two separate veeam licence servers try to speak to the same vm and snapshot that vm – will one fail – or is there a way to schedule two separate veeam licences so they don’t collide if backing up the same vm.

Veeam Software
Posts: 21066
Liked: 2114 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Backup & Replication @ same time . . . Version5

Post by foggy »

George, you need no additional license if you are going to use the same source hosts for replication. Veeam B&R is licensed per CPU socket on the hosts engaged in your backup/replication jobs.

Just make sure you are scheduling jobs properly as currently v5 does not allow to backup and replicate the same VMs simultaneously (VM files are being locked by the first job and you have to wait till it is finished in order to run the next one, otherwise it fails). For example, you can chain the jobs using post-job activity option and this script to check current job status (just trigger a subsequent replication job with PowerShell on receiving a "Success" status for the previous one).

However, v6's changed architecture will handle concurrent jobs scheduling automatically.
integrated Systems
Posts: 16
Liked: 1 time
Joined: Mar 05, 2010 4:57 pm
Full Name: Mike Walker

Backup interfering with replication

Post by integrated Systems »


I have a site with 8 VM's. I am backing up the VM's daily and am also doing a replication of all 8 VM's to an offsite ESX server. All of this works great until the two jobs overlap and try to process the same VM and then one of them fails (the one that starts second). Does anyone have any suggestions on how to make this work?
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 91 guests