If the clients are on isolated networks, there shouldn't be an IP conflict. By isolated, I mean that the DR client cannot reach the production network. As long as the DR client can route to the Avamar but it can't route to the production network, you shouldn't have any problems. This might require some VLAN and routing gymnastics.
I believe there is a way to add multiple clients with the same name. I don’t know what it is though. EMC has been promoting using Avamar in the cloud for service providers, and I can imagine several situations where various customers can have clients with the same name.
You should be able to activate two clients with the same hostname to the grid without making any changes to the server configuration as long as you activate them into different domains.
Once the DR target has been activated (for example into a domain called /dr-test), run a redirected restore to that client using a backup of the original server. A word of warning, however -- if you are performing a VSS System State restore, this will overwrite the IP address of the DR server with the production hostname and IP.
This problem is a bit trickier without a replication target grid since the client that is the target of the DR restore will assume the identity of the production system once the restore is complete. Unless the two clients are on isolated networks, that could cause problems in production.
If you have a Gen4 grid and appropriate networking hardware you could have a separate VLAN configured to facilitate these DR tests. Properly configured, this could isolate the DR environment from the production environment while still leaving the Avamar server accessible from both.
If you have an ESX host available, you may want to talk to your account team about a small Avamar Virtual Edition instance to use for DR testing. You could replicate a backup to the AVE, activate the DR test client to the AVE, then run the restore with the DR target in an isolated environment.
Of course there is always the low-tech solution -- you could run the DR restore, then unplug the client from the network before rebooting.
Thanks ianderson. Once the restore is complete of the VSS (the clients will be on isolated networks), but as you stated, this is where my IP address conflict is going to come in. How can I restore a VSS from production into an isolated environment that ultimately will have a different IP address from it's twin in production?
Unfortuntaely, my grid is Gen3 and testing is within the next 45 days so I'm not sure how quick the turnaround is for the AVE method you mentioned.
Not sure the low-tech solution will go over well with the powers that be for documentation purposes.
ionthegeek
2 Intern
•
2K Posts
0
May 1st, 2012 08:00
If the clients are on isolated networks, there shouldn't be an IP conflict. By isolated, I mean that the DR client cannot reach the production network. As long as the DR client can route to the Avamar but it can't route to the production network, you shouldn't have any problems. This might require some VLAN and routing gymnastics.
aj2546
49 Posts
0
April 27th, 2012 08:00
I believe there is a way to add multiple clients with the same name. I don’t know what it is though. EMC has been promoting using Avamar in the cloud for service providers, and I can imagine several situations where various customers can have clients with the same name.
ionthegeek
2 Intern
•
2K Posts
0
April 27th, 2012 08:00
You should be able to activate two clients with the same hostname to the grid without making any changes to the server configuration as long as you activate them into different domains.
Once the DR target has been activated (for example into a domain called /dr-test), run a redirected restore to that client using a backup of the original server. A word of warning, however -- if you are performing a VSS System State restore, this will overwrite the IP address of the DR server with the production hostname and IP.
dawgpound75
1 Rookie
•
5 Posts
0
April 27th, 2012 10:00
Thanks. I believe that solves my issue for Windows (file-system) restores. In regards to a VSS System State restore, what might my other options be?
ionthegeek
2 Intern
•
2K Posts
0
April 30th, 2012 12:00
This problem is a bit trickier without a replication target grid since the client that is the target of the DR restore will assume the identity of the production system once the restore is complete. Unless the two clients are on isolated networks, that could cause problems in production.
If you have a Gen4 grid and appropriate networking hardware you could have a separate VLAN configured to facilitate these DR tests. Properly configured, this could isolate the DR environment from the production environment while still leaving the Avamar server accessible from both.
If you have an ESX host available, you may want to talk to your account team about a small Avamar Virtual Edition instance to use for DR testing. You could replicate a backup to the AVE, activate the DR test client to the AVE, then run the restore with the DR target in an isolated environment.
Of course there is always the low-tech solution -- you could run the DR restore, then unplug the client from the network before rebooting.
dawgpound75
1 Rookie
•
5 Posts
0
May 1st, 2012 08:00
Thanks ianderson. Once the restore is complete of the VSS (the clients will be on isolated networks), but as you stated, this is where my IP address conflict is going to come in. How can I restore a VSS from production into an isolated environment that ultimately will have a different IP address from it's twin in production?
Unfortuntaely, my grid is Gen3 and testing is within the next 45 days so I'm not sure how quick the turnaround is for the AVE method you mentioned.
Not sure the low-tech solution will go over well with the powers that be for documentation purposes.
Aditya_321
1 Message
0
April 2nd, 2020 00:00
Can We do a Full Avamar Server Recovery , From Replicated Grid.