Multiple site large environment architecure

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 18
Comments: 24

I'm still toying with my new 12.5 environment in preparation for a cutover from my 11.5 environment which is fairly large at 250 or so windows 7 clients we routinely back up every week. The topic of catalogs is a concern re designing the 12.5 environment properly.

The environment: 210 nodes in primary site A in USA, 30 in site B (UK), and 10 in another USA secondary site C. A 4th site D gets a replicated copy of the nodes in site A only. The connectivity between sites A and D is > 10Gb and connectivity to all other sites is 100Mb.

The Acronis 12.5 documentation doesn't make it clear but it seems like each catalog added to a  management server will scan all registered storage locations. It doesn't make sense to add multiple catalogs except for redundancy as all will have the same data as I can't selectively point a catalog server to only some registered storage locations and not others. Is this accurate?

It also seems to indicate that having a single management server manage all sites above won't work well because one catalog will reach across slow links to sites B and C to catalog the remote data there which will slow it a bit. With 250 clients backing up weekly, the catalog is going to be pretty busy.

It makes more sense to create individual management servers for the two small sites (B and C, which I can do) and also install the storage node, catalog and deduplication DB to these windows servers as they serve fairly small client counts. The downside is of course no one management server to manage everything.

Can someone comment on whether these assumptions are accurate?

If so, IMO Acronis should add the ability for catalogs to selectively target storage locations and ideally introduce the concept of sites.

Thanks

Pete

Thu, 08/24/2017 - 15:10
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 18
Comments: 24

I think I found the answer to my own question. There is a concept of which Catalog Server manages which registered storage location on a storage node.

When registering a storage location (Add Location), choose an existing storage node, pick the local or UNC path the storage node will manage and then you must choose a catalog server.

If catalog servers per site are desired and the storage locations are already registered to the "wrong" catalog server, just delete the storage location and add it back again choosing the catalog server local to the storage location.

Thu, 08/24/2017 - 16:00