Data Protector A.10.04 supports various operations that can be useful if the whole Data Protector Cell or parts of it need maintenance (IDB, devices) or the environment needs upgrades.
- Scheduler maintenance from Consolidated Scheduler
- omnitrig -stop | -start
- omnisv -maintenance 1 | -maintenance -stop | Exit Maintenance Mode from MFC GUI
- omnisv -start -idb_only | -stop -no_idb
- Disable a device | Enable a device
While there are so many options, it is hard for the user to decide what option is correct in which situation. Moreover, there are plenty of “blind spots” not covered at all but required for daily operations. For example:
- We can disable a device, but not a whole library.
- We cannot disable a client that is temporarily not reachable. We need to remove the client from the specifications, which is a manual process.
- While no session manager can write to the IDB when omnisv -maintenance 1 is active the trigger running automated activities (media sessions clean-up expired media, free pool update, DCBF purge, etc.) will run. Change in the IDB is not expected.
- The JCE database is not read only when omnisv -maintenance 1 is active. Consolidated Scheduler remains active.
- Missed Job Executions are not logged to when omnisv -maintenance 1 is active.
- omnitrig -stop will halt the quartz scheduler and legacy trigger, but the Enable Scheduler from Consolidated Scheduler Maintenance will only start the quartz scheduler.
- Scheduler Maintenance is not persistent (if the services are stopped, e.g. during an upgrade)
- Sessions are executed on clients that are currently upgraded. Upgrades on clients that have running/scheduled sessions is possible. This should be prevented.
The idea is to Streamline the Cell Manager Maintenance operations and reduce the amount of available options to what is actually necessary for upgrades, IDB maintenance (e.g. running offline SQL scripts on the IDB) and client and device maintenance.
Having the right options available to maintain the Cell Manager, clients and device is key for critical and large environments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.