Live Sync Configurations on combined CommServe & Media Agent deployment

The idea of CS Live Sync is to address the scenario of a CS not being available. Usually this means the entire server is likely unavailable, which would be your MA if it were left behind. I think whatever you are trying to design for needs to be addressed with a better approach. The CS and MA need to failover together since you will want both running on whichever HW is online and available.

Thanks,
Scott
 

Hi ​@Scott Moseman.

Thanks for the information.

In this scenario the customer has 2 small sites that should be protected. Both will only have a single server to host both CS and MA. 

What is the approach when both sites have active workloads to protect and backing up over the WAN/network is not an option?

So with CS services being offline with Live Sync at the secondary site, can the MA be configured on a separate instance to still cater for the workloads at the secondary site? The same goes for the MA services at the primary site in the event of a DR test where only the CS is failed over?

I understand that this is not the best approach but with limited hardware I am considering all options here.

Thanks.

Ignes

Yes, 3rd instance for MA, or add the MA package to the 2nd (LiveSync) instance

I agree both of these are probably options. My gut says to go with a 3rd instance so we’re not adding more components to the existing CS Live Sync configuration.  In the event of any issue with CS Live Sync, if there’s an additional agent installed, especially a Media Agent, I imagine it could create some curve balls.

Thanks,
Scott