Start a Conversation

Unsolved

This post is more than 5 years old

C

508

January 31st, 2008 08:00

Questions on CC DR and Hardware Migration

My current environment is CC 5.2 SP4 running on Windows 2000 SP4.
I ultimately want to migrate to new hardware and then upgrade to CC 6.0.

I am looking over the EMC ControlCenter 6.0 Upgrade Guide P/N 300-004-033 REV A03.

Hardware Migration Question: On page 25 of Appendix C is says...
"The source host and the target host must have the same operating system"

Does this mean it just needs to be Windows to Windows
or does it have to be, in my case, Windows 2000 SP4 to Windows 2000 SP4?

DR Question: We have 2 data centers with replicated disk. I see that CC supports MSCS Clusters with SRDF/CE but I would prefer to boot from SAN and use SRDF to replicate the boot drive and the data drive. Does EMC support boot from SAN for CC?
If so, where is this documented?

Thanks

4 Operator

 • 

2.1K Posts

January 31st, 2008 10:00

So I have to ask (since you are going to new hardware AND a new version)...

Have you considered not "upgrading" and just install the new version on the new hardware and then get rid of the old?

Through many discussions with EMC (and some other customers) we have determined that we will be much better off with a fresh install of 6.0 as opposed to upgrading from our current 5.2 sp5. It's a bit more difficult for us because we are reusing the existing hardware, but I think it is something you should at least consider (unless you have a compelling reason not to).

As for the question of boot from SAN, I can't point to the official document that says yes (at the moment) but this was a suggestion made by an EMC solutions architect that specialized in ECC configurations, so I suspect it will be supported (it better be).

111 Posts

January 31st, 2008 13:00

Fair question...

We also discussed this with EMC and they recommended that we upgrade for the following reasons

1) We want to preserve our StorageScope Data
2) We want to preserve our Performance Manager Data
3) We want to maintain our current configuration (ie alerts and stuff)

I am a big believer in "Clean and Prestine" but my management wants to make sure we keep most of our historical information.

As far as boot from SAN, I am kind of assuming it would be supported but I hate to have an issue and discover otherwise. I would rather boot from SAN and manually failover disks and bring up cold nodes. I feel this would be a simpler solution then adding the complication of SRDF/CE.

4 Operator

 • 

2.1K Posts

February 1st, 2008 12:00

Hmmm... just a thought here with no real basis in reality, but if the need is to keep historic data, could you migrate just enough of your existing environment into a VM and use it to pull out historic reports? Then you could do a clean install of the new stuff and have all the advantages of not dragging your baggage with you.

The only real downsides I can see off the cuff would be lack of automated trending between the two timeframes, and the cost of the VM environment to maintain the historic data.

Anyone else have any thoughts on this?
No Events found!

Top