There may be instances when 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.
To run a timetable from both the primary and secondary CMS servers:
Create a timetable on the primary CMS server.
On the primary CMS server, enter the timetable screen by accepting the default selection:
ADDITIONAL INFORMATION:
This timetable will run only on this CMS server
< > Run only on this CMS server
<X> Run on this or another CMS server
Use the Add command to add the timetable.
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):
ADDITIONAL 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.
Back up the data on the primary CMS server by using MaintenanceBack Up Data option.
On the secondary server, change CMS to single-user mode.
Restore the data on the secondary CMS server using the Maintenance Restore option.
Change CMS back to multi-user mode on the secondary server.
ADDITIONAL INFORMATION:
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
