2 Veeam Consoles

[onthax]

Hi All

We have 2 sites, a Primary and a Secondary.


Primary:
1 Veeam Server
Several hundred VM's being backed up
Replications inbound to Site 1's VC Server.

Secondary:
1 Veeam Server
100 or so vm's being replicated from Site 1 for DR failover.

We have an issue where if a Backup and a Replication job run at the same time, it has a hissy fit and can cause very long stun times (10-15min).

Anyone had any success with a similar situation.

We are looking at consolidating down to 1 Veeam Server at the secondary site (has to be there for DR failover purposes) which will handle the backups @ primary/secondary sites and the replication (will have local proxies and backup repositories at both sites) This would mean veeam has visiblity of the backup and replication jobs and makes the replication job wait while the vm is being backed up.

But are concerned about the amount of load and reliance on a single server.

Anyone run into this?

Any ideas?

[Vitaliy S.]

Hello,

Having a single backup server will, indeed, give you more control of job schedule, so that you could avoid job overlaps.

Can you please tell me how many jobs you have in total? Based on your infrastructure description, I would say that a single backup server should be more than enough. Also what kind of VM stun do you refer to? The one that might happen when VM snapshot gets committed?

Thank you!

[onthax]

Would be around 100 jobs,

about 900 VMs total across the 2 sites.

[Vitaliy S.]

Ok, thanks for additional details. Single Veeam backup console should be a good fit here. BTW, what about VM stun question? Does it happen when jobs overlap or during VM snapshot commit operation?

[onthax]

During the commit.

[Vitaliy S.]

In this case two consoles is not the reason for this behavior. Please look through this topic for additional details > Snapshot removal issues of a large VM (I know this is a huge topic, but start reading from the post I've pointed this URL to).