Site promote to 5.8

[Kevin Scantlan]

We are doing a site promote from 5.6 to 5.8 tonight.  In looking through the Site Promotion document (Chapter 14), I had some questions as to when I need to bring down our engine with respect to running the hcirootcopy script.

Based upon the documentation, I run the hcirootcopy to completion.  Then take down the engine under the old version, then bring it up under the new version.  However, I have some files that our engine writes to while running and if they get copied prior to bringing the engine down, it will not get the latest version of the file(s).

It appears that to be safe, I should bring the engine down prior to running the hcirootcopy.

Topic

[James Cobane]

Kevin,

You should be able to run the ‘rootcopy’ and site promotions well in advance of bringing the interfaces down. This will allow you time to validate your configurations prior to cutting over to the new release.

[Kevin Scantlan]

The files that I am talking about are not configuration files, but data files.  For instance,   I have a file that contains the message control ID from the previous message for a outbound interface.  I compare the message control ID of the current message to see whether or not it’s a duplicate.  So, for every message it’s being written to.  If it’s copied during the hcirootcopy run, it will not have the last value when the thread was taken down.

[James Cobane]

Gotcha.  Yes, what we normally do is tar’ up all the respective interface counter files (or run-time files such as you describe) after we have shut-down all the interfaces, then untar them in the new version.  This is normally part of our cut-over during the “down-time”.

Hope that makes sense.

Jim Cobane

Henry Ford Health

[Author]

Replies