Move SMC 3.6 to new server

In the end I raised a call with Sun.

I haven't tried what Sun have advised me yet (and they said this isn't a supported answer) but for your information here it is.

'Although we don't officially support this procedure I have managed to do

a similar task previously but always to the same Solaris version

therefore you have a slight twist here.

The 'hostname' and IP address of the new server will need to be the same

as the old one, otherwise you'll need to manually change all the '*.dat'

files that reference these values and also all agents will need to

updated with the new information. This could result in an inconsistent

environment and if this does occur your only option would be to do a

"fresh" installation of server and agents.

Using the original 'hostname' and IP address means that you should be

able to use 'es-backup', although as I say moving to a new Solaris

version will be a new twist but I can't actually see any obvious issues.

The basic procedure would be:

* Use 'es-backup' on the current server to preserve the

configuration and historical data. Naturally the data needs to be

saved to either a NFS mount that both systems have access to or

once completed you'll need to move the files to the new server.

Also I wouldn't recommend using the 'on-line' option to

'es-backup' ('-o') in this situation.

* Install SunMC 3.6.1 on the new server and add exactly the same

addons that you installed on the original. You can use

'es-validate' to review the current installation.

* Update the ELP addon from

'http://www.sun.com/software/products/sunmanagementcenter/get.xml'

that supports the Ultra 45

* Run 'es-setup'; Remember that the same administration users will

need to be used.

* Run 'es-restore' which will restore the old databases and

settings. This step will only work if you have installed exactly

the same options as on the old server.

One area that I can see you may have an issue is with the Config-Reader

for the SunMC server itself as you are moving to a different

architecture. However this is defined in the 'base-modules.dat' file and

you could manually delete the applicable line and load the correct

Config-Reader after the restore has completed (Always run 'es-stop -A'

before manually editing any files). You may find it easier to un-load

the Config-Reader modules prior to running the 'es-backup' so that you

don't need to manually correct them later.

For SunMC 3.6.1 documentation please see 'http://docs.sun.com/app/docs/coll/810.8''

fisher11 at 2007-7-6 22:34:44 >