Lucent Technologies CentreVu Release 3 Version 8 High Availability User Manual page 43

User Scenarios CentreVu CMS R3V8 High Availability User Guide
7. When the Primary server is returned to service, choose between the
following options:
a. If you have not made any CMS administration changes on the
Secondary server (including timetable modifications or
revisions) which you wish to transfer to the Primary server,
return the timetables on the secondary server to their normal
run state by using the most recent CMS Administration backup
created on the Primary server and restoring it onto the
Secondary server. The remaining steps (presented below)
can be disregarded.
b. If you have made any CMS administration changes on the
Secondary server and you wish to transfer them to the Priamry
server after it is brought back to service, continue with the
additional steps listed below to return all timetables to their
normal run state on the two HA servers.
8. Perform a CMS system administration backup of the Secondary
CMS server.
9. On the Primary server, change CMS to single-user mode.
10. Restore System Administration data to the Primary CMS.
11. Return CMS to multi-user mode on the Primary server.
Now, all timetables on the Primary CMS server are duplicates of the
timetables on the Secondary. However, since the "Run timetables
only on this CMS server" global edit on all timetables occurred on
the Secondary CMS server, none of the timetables will run on the
Primary.
12. Repeat steps 1 through 6 of this procedure on the Primary server to
globally edit the timetables to run only on the CMS server.
13. Perform a CMS system administration backup on the Primary server
and restore it onto the Secondary server.
3-19