Upgrading hardware?

Question

I need to upgrade hardware on both of my Win2K3 servers running my EMC AutoStart solution.
With minimal downtime, both servers will need to be replaced, plan on keeping server names, IP address, resource groups/ VIP address. Being that Mac addresses will change-Would Licenses be affected? If so, would it still run or would have to have new license keys ready?

This is what I am thinking

-Run the resource group on ¿old¿ serverA.
-Stop monitoring, power down ServerB.
-Replace/bring up "new" ServerB, with same name/IP address and configuration as old server.
-Install all software applications needed.
-Install AutoStart as a secondary client, connected to primary server.
-Force resync of data from ¿old¿ ServerA to ¿new¿ ServerB, or re-establish a complete mirror. After mirror is 100% complete.
-Then relocate and run resource group off of "new" ServerB. Validate system runs/data is correct.

Repeat the above process for old ServerA servers?

Any other idea's or concerns?
Has anyone done something of this sort? Ran into any issues or have a better game plan?

Thanks
David

tribicic · Answer

Hello David - don't worry about the licenses as they don't care about the MAC addresses. You plan is exactly as it should be, just keep in mind that you will have to bring your resource group ofline in order to delete and recreate the mirror data source but this should not take more than a few minutes. Once created again add it back to the resource group and bring everything online for the initial sync.

vongehr · Answer

Licenses would not be affected.The steps look like they are ok for the most part.Be sure when you install AutoStart back on Node B that it is at the same version and patch levels as it was before.Not sure what you mean by 'Install AutoStart as a secondary client'. When you reinstall AutoStart on Node B and restart, it should come back up as it was previously, listed as a Primary Agent in the AutoStart console. Make sure it is not listed as a Secondary Agent in the AutoStart console, if for some reason it is... promote it before moving on to your next step.Last thing, I would do to make sure you have data integrity. When you are moving the RG to Node B. First offline the RG on Node A. Then shutdown Node A. Then online the RG on Node B. Then 'check' the data and applications, be sure all is good before you wipe or replace Node A. If for some reason the data or applications do not look ok on Node B, you still have Node A as a last resort (and the data there as well). If you do as you were planning... when you relocate from Node A to Node B, the mirror will start mirroring from Node B to Node A, and now your previously good data on Node A cannot be failed back to as a last resort.Just a suggestion that may help you be super careful you don't have something weird happen and not have good data to get back to.Another suggestion I have given people, would be to offline the RG on Node A. Take the mirror out of the RG, then unconfigure the mirror (so you have access to the drive), then backup or archive the data on the drive. So now you are extra-super safe. Although you may think this is being a bit over the top. Really up to you about what you think is the best route and acceptable level of risk.Cheers,Daniel Norris VongehrEMC Tech Support

david.fontenot · Answer

hey thanks for the reply. I figured I wasn't to far off. I haven't tested any of that above, was just thinking out loud and figured I'd better write it down and ask if it has been done before....

Replication Manager

Upgrading hardware?

Was this post helpful?