Unsolved
This post is more than 5 years old
5 Posts
0
666
January 18th, 2007 03:00
OS upgrade on ECC Server
My ecc Server is a Win 2000 Server i would like to upgrade it Server 2003. Has anyone done this before? Any gotchas. I could not find a EMC document which discusses this. I was gone call in a support incident but thought I could also learn from the tales fof the real world.
Also I was thinking migrating a new server entirely with more horsepower. Comments? How would I transfer the existing ecc config to the new Server.
Thanks
Also I was thinking migrating a new server entirely with more horsepower. Comments? How would I transfer the existing ecc config to the new Server.
Thanks
No Events found!
crusso1
24 Posts
1
January 18th, 2007 08:00
FWIW, It's really not that big of a deal to reinstall ecc onto another box, assuming you keep the same hostname and IP address. all of your agents will be none the wiser. you will get a clean server with w2k3 and eccsp5.
GlenH
141 Posts
0
January 24th, 2007 01:00
As long as you are running ECC 5.2, then you can upgrade to Windows 2003.
If you have a 5.1.x or older environment, then you must upgrade to ECC 5.2 before you upgrade windows to 2003 (this is due to Oracle)
If you want to move to Windows 2003 SP1, then you need to have ECC 5.2 SP4 or higher.
Moving to a new server is quite complicated but it is possible. There are some instructions on Powerlink under the Downloads & Patches section. Do a search for "patch" and "3322" and you'll find it right away. I've included the pre-requisites below..
Depending on how much customisation you've done, it is probably easier to just re-install ECC on the new server (make sure the new host has the same hostname and domain name). Remember to backup the WLA archives from the old server if the archiver is on the infrastructure server. This does mean however you lose any customisations (users, alert definitions, DCP customisations etc), also the alert history and your storage scope history.. If those are not that important to you then its much easier to reinstall on a new server than do a migration...
All that being said, here's the requirements as documented for a successful migration:
1. ControlCenter 5.2 migration is supported.
2. The source host and target host must have the same Operating System (OS).
3. The original and new hosts must maintain the same fully qualified network name. The migration is limited to implementations based on DNS. Implementations not using DNS are not covered by this procedure.
4. Performance View migration is not supported.
5. Console migration is not supported.
6. EMC Log Utility (ELU) cannot be installed on a possible migrating/DR host.
7. If the original installation was a 5.0.x or 5.1.x and upgraded to later revisions, the IP's on the new host must match that of the old host.
8. Any Agent host that was installed using IP as opposed to hostname will need to have the ctg.ini and master.ini files updated in the event of an IP change.
9. If you are using multi-NIC, the primary and any additional NIC interface must map to the Fully Qualified Domain Name (FQDN) of the original installation.
10. ControlCenter cluster implementations are not supported.
11. The target (new hardware) host name must remain the same as the source (former) host with FQDN.
12. The EMC ControlCenter 5.2 Planning and Installation Guide, Volume 1 P/N 300-000-684 REV A04, was used and followed during the installation of a single infrastructure or distributed configuration.
Good Luck,
Glen.