In Data Protector 10.x schedules that were working perfectly mysteriously stop kicking off.

  • KM03166525
  • 24-May-2018
  • 24-May-2018

Summary

Maintenance Mode disables the schedules. This behavior may vary slightly between Data Protector Versions.

Question

If Data Protector is put into maintenance mode (omnisv -maintenance) this will disable the scheduler.  This is expected behavior.
 
However, Data Protector will remain in maintenance mode until an omnisv -maintenance -stop is executed.
 
Simply stopping the services and restarting them will NOT stop maintenance mode, therefore schedules will continue to be disabled.
 
 
Scheduler algorithm checks for the existance of the following file: C:\ProgramData\OmniBack\Config\Server\AppServer\maintenance
 
If it exists schedules are disabled.  This file should not be removed manually.  The correct procedure is to run
omnisv -maintenance -stop

Answer

Please note the following command sequence for a better understanding:
 
C:\Users\Administrator>omnisv status
    ProcName      Status  [PID]
===============================
    crs         : Active  [5944]
    mmd         : Active  [2796]
    kms         : Active  [5072]
    hpdp-idb    : Active  [5504]
    hpdp-idb-cp : Active  [7748]
    hpdp-as     : Active  [7812]
    omnitrig    : Active
    omniinet    : Active  [5796]
    Sending of traps disabled.
===============================
Status: All Cell Server processes/services up and running.
 
 
C:\Users\Administrator>omnisv -maintenance
Cell Server is entering maintenance mode
0  seconds left to abortion of all running sessions ...
No sessions to abort!
Cell Server will start terminating processes ...
 
No DBSM proccesses/sessions to abort!
Releasing locked resources (devices, media, VSS/ZDB, ...)
Cell Server is now in maintenance mode.
 
C:\Users\Administrator>omnisv status
    ProcName      Status  [PID]
===============================
    crs         : Maintenance  [5944]
    mmd         : Active  [2796]
    kms         : Active  [5072]
    hpdp-idb    : Active  [5504]
    hpdp-idb-cp : Active  [7748]
    hpdp-as     : Active  [7812]
    omnitrig    : Down
    omniinet    : Active  [5796]
    Sending of traps disabled.
===============================
Status: At least one of the Cell Server processes/services is not running.
 
C:\Users\Administrator>omnisv stop
Cell Server services successfully stopped.
 
 
C:\Users\Administrator>omnisv status
    ProcName      Status  [PID]
===============================
    crs         : Down
    mmd         : Down
    kms         : Down
    hpdp-idb    : Down
    hpdp-idb-cp : Down
    hpdp-as     : Down
    omnitrig    : Down
    omniinet    : Down
    Sending of traps disabled.
===============================
Status: At least one of the Cell Server processes/services is not running.
 
C:\Users\Administrator>omnisv start
Cell Server services successfully started.
 
 
C:\Users\Administrator>omnisv status
    ProcName      Status  [PID]
===============================
    crs         : Maintenance  [3756]
    mmd         : Active  [3552]
    kms         : Active  [4264]
    hpdp-idb    : Active  [6236]
    hpdp-idb-cp : Active  [5224]
    hpdp-as     : Active  [5300]
    omnitrig    : Down
    omniinet    : Active  [2564]
    Sending of traps disabled.
===============================
Status: At least one of the Cell Server processes/services is not running.
 
C:\Users\Administrator>omnisv -maintenance -stop
Maintenance mode successfully stopped
 
C:\Users\Administrator>omnisv status
    ProcName      Status  [PID]
===============================
    crs         : Active  [3756]
    mmd         : Active  [3552]
    kms         : Active  [4264]
    hpdp-idb    : Active  [6236]
    hpdp-idb-cp : Active  [5224]
    hpdp-as     : Active  [5300]
    omnitrig    : Active
    omniinet    : Active  [2564]
    Sending of traps disabled.
===============================
Status: All Cell Server processes/services up and running.
 
C:\Users\Administrator>