Timetables - Running On Both Primary And Secondary Servers - Lucent Technologies CentreVu Release 3 Version 8 High Availability User Manual

User Scenarios
Timetables –
Running on both
Primary and
Secondary
servers
There may be instances where you want to run a Timetable from both the
Primary and Secondary CMS servers. For example, since the
Maintenance error log report is specific to a CMS server, you may want
the timetable to run and produce a Maintenance error log report for each
CMS server.
If you wish to run a timetable from both the Primary and Secondary CMS
3
servers, do the following:
1. Create a timetable on the Primary CMS server.
2. On the Primary CMS server, enter the timetable screen. You will
see the following:
This timetable will run only on this CMS server
< > Run only on this CMS server
<X> Run on this or another CMS server
Accept the default selection.
3. Use the Add command to add the timetable.
4. After you have created all the tasks for the timetable and use the
Stop function to end the task creation, the timetable screen now has
the following displayed (in addition to all timetable information):
This timetable will run on this or another CMS server
< > Run only on this CMS server
<X> Run on this or another CMS server
The timetable will now run as scheduled on the Primary CMS server
5. Back up the data on the Primary CMS server using Maintenance
Back Up Data.
6. On the secondary server, change CMS to single-user mode.
7. Restore the data on the Secondary CMS server using Maintenance
Restore.
8. Change CMS back to multi-user mode on the secondary server.
9. The timetable you restored to the Secondary CMS server is
automatically scheduled to run on the Secondary CMS server as
well as on the Primary CMS server.
If you log on to the Secondary CMS server and look at the timetable,
you will see the following lines at the bottom of the timetable screen:
This timetable will run on this or another CMS server
< > Run only on this CMS server
<X> Run on this or another CMS server
CentreVu CMS R3V8 High Availability User Guide
3-17