Hardware Upgrade without reinstallation

Hi,

We are planning to replace our current hardware SUN v440 with v880 on UAT environment (with same ip & hostname).
Currently we are running TeamSite 6.5 SP3 on Solaris 8.

Our System Administrator is planning to install Solaris 8 on the new machine and then copy the TeamSite /app folder & /iw-store to the new machine. Followed by copy other files that is outside the IWHOME like /etc/init.d/iw*, /etc/iw* and log files (he is aware of the complete list.) Also setting up the users & groups in the new box.

By doing this, he is trying to save the effort of installing TeamSite and installing our customized code (multiple releases) in the new box.

Is this the right approach? (It may not be officially supported i.e. a different deal)

I prefer to install TeamSite on the new box and followed by installing our customization & application releases on top of it.

What are the issues expected with his approach?

Find more posts tagged with

Comments

moonkhanna

Hi,

We are planning to replace our current hardware SUN v440 with v880 on UAT environment (with same ip & hostname).
Currently we are running TeamSite 6.5 SP3 on Solaris 8.

Our System Administrator is planning to install Solaris 8 on the new machine and then copy the TeamSite /app folder & /iw-store to the new machine. Followed by copy other files that is outside the IWHOME like /etc/init.d/iw*, /etc/iw* and log files (he is aware of the complete list.) Also setting up the users & groups in the new box.

By doing this, he is trying to save the effort of installing TeamSite and installing our customized code (multiple releases) in the new box.

Is this the right approach? (It may not be officially supported i.e. a different deal)

I prefer to install TeamSite on the new box and followed by installing our customization & application releases on top of it.

What are the issues expected with his approach?

I would say, you can expect anything since this is not a supported method.

I would have gone with the supported approach..

ISCBorisB

Hi,

We are planning to replace our current hardware SUN v440 with v880 on UAT environment (with same ip & hostname).
Currently we are running TeamSite 6.5 SP3 on Solaris 8.

Our System Administrator is planning to install Solaris 8 on the new machine and then copy the TeamSite /app folder & /iw-store to the new machine. Followed by copy other files that is outside the IWHOME like /etc/init.d/iw*, /etc/iw* and log files (he is aware of the complete list.) Also setting up the users & groups in the new box.

By doing this, he is trying to save the effort of installing TeamSite and installing our customized code (multiple releases) in the new box.

Is this the right approach? (It may not be officially supported i.e. a different deal)

I prefer to install TeamSite on the new box and followed by installing our customization & application releases on top of it.

What are the issues expected with his approach?

You do not really think that re-install few dozen Files of your *customized code* (releases and all) is harder than re-install TS, do you?
An idea is seriously flawed. In Unix your SysAdmin can *probably* do it if he knows Unix and TS really well - but I doubt it.

a) I hope it's not a surprise that Software Install is plenty more than just Files copying.
(Think Environment, start-up, mounts, Security, Compilations, third-parties Components like Perl, Ant, Apache, Verity and on and on...)

b) Backing Store is a virtual mount's *real* Repository, it should not be simply copied (security settings again). You'd have to use iwmigrate.

I *beleive* that for 6.5 You will also have to regenerate your license, same IP is not enough (used to be based
on NIC MacID, not sure if it's still the case)

gzevin

b) Backing Store is a virtual mount's *real* Repository, it should not be simply copied (security settings again). You'd have to use iwmigrate.

agree wirth you on most point, except this one (above). You can take the backing store and move it to any Unix server. If this is a pre-6.5. store, then search will not work. But still this can be done - done too many times Smiley Happy

gzevin

What are the issues expected with his approach?

I'd even reinforce what the other's have said - DON'T DO IT.