I think your analysis is correct and you will see better performance if you deploy proxies directly at site B.
If I were setting this up, I would configure the proxies to protect only local datastores. Avamar will never dispatch a job to a proxy that does not have access to the datastores required to run the job.
we did the same thing. and the point that ianderson is making is a good point.
once we created proxies for both sites
and I went to each proxy and did the edit and put check marks in the boxes for the datastores.. I only check that sites datastores..
proxies in siteA only had datastores in siteA checked
proxies in siteB only had datastores in siteB checked
this was to prevent any mistakes of added a vm to the wrong avamr grid.
if I added a vm from siteB to the siteA grid and policy/group the backup would fail because it could not get to the datastore from a siteA proxy. Thus preventing us from doing any backup across sites.
(and yes I have done that twice now! but the failure of the vm backup pointed out my mistake)
At this point we have proxies configured for both sites and they're only set to be used by vm backups at each of those sites. However things are still moving pretty slowly. The first backup of a 2 TB file server has been running for 72 hours and only processed 812 GB of data. I think the limitation is the 10 Mbps link they have between the proxies and the Avamar server.
ionthegeek
2 Intern
•
2K Posts
0
November 5th, 2012 11:00
I think your analysis is correct and you will see better performance if you deploy proxies directly at site B.
If I were setting this up, I would configure the proxies to protect only local datastores. Avamar will never dispatch a job to a proxy that does not have access to the datastores required to run the job.
J_H_
2 Intern
•
498 Posts
0
November 6th, 2012 14:00
we did the same thing. and the point that ianderson is making is a good point.
once we created proxies for both sites
and I went to each proxy and did the edit and put check marks in the boxes for the datastores.. I only check that sites datastores..
proxies in siteA only had datastores in siteA checked
proxies in siteB only had datastores in siteB checked
this was to prevent any mistakes of added a vm to the wrong avamr grid.
if I added a vm from siteB to the siteA grid and policy/group the backup would fail because it could not get to the datastore from a siteA proxy. Thus preventing us from doing any backup across sites.
(and yes I have done that twice now! but the failure of the vm backup pointed out my mistake)
JWeinsheimer
91 Posts
0
November 14th, 2012 17:00
At this point we have proxies configured for both sites and they're only set to be used by vm backups at each of those sites. However things are still moving pretty slowly. The first backup of a 2 TB file server has been running for 72 hours and only processed 812 GB of data. I think the limitation is the 10 Mbps link they have between the proxies and the Avamar server.