Future customer capacity requirements will exceed the maximum capacity of the HCP300. The customer already has VSP and HUS storage in place.
If this is a 1:1 migration (existing HCP300 to a new HCP500), your best bet is standard HCP replication. If you need to migrate the data to an existing HCP500 (which doesn't seem to be the case from what I understand), you're better off using HCP-DM.
Thanks Michael, that was what I suspected. So there would be a period of time where data is replicated/refreshed and then a brief outage where the new systems replace the old in regards to FQDN?
That is correct. You may need to seek additional information if you want to know the process in detail, but this is basically how it works.
Hi Mike, how are you doing with that HCP migration?
Hello Michael, the HCP500s are scheduled to be installed next week. The struggle right now is to get the HCP300s upgraded to 6.x so dual outbound replication can be used to seed the PROD HCP500 while not disrupting the existing PROD -> DR HCP300 replication.
I've been toying with the 6.x virtual appliances and I think all should go well. But you know what they say, "Everything is easy until you actually start to do it."
More to come ...
Retrieving data ...