Making the switch permanent
Making the switch permanent (DDM)
In the procedure Switching the manager to the upgraded backup, you switched your manager promoting your new version backup manager to the role of manager.
To make this configuration fully operational and persistent
through JnextPlan, complete the following procedure on the new manager,
referred to as new_mgr_cpu:
- Edit the localopts file and modify the following entry as shown:
where new_mgr_cpu is the workstation name of the new manager. For more information about localopts file, see Setting local options.DEFAULTWS=new_mgr_cpu
- Change the workstation definition of the back-level master by running:
and in the definition substitute type=manager with type=ftacomposer modify cpu=old_mgr_cpu
- Change the workstation definition of the new manager by running:
and in the definition substitute type=fta with type=manager.composer modify cpu=new_mgr_cpu
- Ensure that the optman cf option is set to all.
- Rebuild the plan to activate the changes to the database:
JnextPlan -for 0000
- Restore the previous setting of the optman cf option, if necessary.
- Edit the
/TWA_DATA_DIR/mozart/globalopts file and modify the
master=old_mgr_cpu entry as shown:
where new_mgr_cpu is the workstation name of the new master. For more information about optman, see Setting global options.master=new_mgr_cpu
In this way the reports reptr-pre and reptr-post can run when you run JnextPlan.
- On the previous dynamic domain manager launch the
following command to export the security
file:
dumpsec > <file_name>.txt
- Copy the <file_name>.txt file to the new dynamic domain manager.
- On the new dynamic domain manager,
launch the following command to compile and install the security
file:
makesec <file_name>.txt
For more information about the dumpsec and makesec commands, see Updating the security file.
You can now proceed to Installing the new master domain manager configured as a backup.