Data Protector User Discussions
cancel

(DP) Support Tip: Data Protector 10.x schedules that were working mysteriously stop kicking off.

Highlighted
Micro Focus Expert
Micro Focus Expert

(DP) Support Tip: Data Protector 10.x schedules that were working mysteriously stop kicking off.


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.


The scheduler algorithm checks for the existance of the following file: C:\ProgramData\OmniBack\Config\Server\AppServer\maintenance and if it exists schedules are disabled. This file should not be removed manually. The correct procedure is to run omnisv -maintenance -stop


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>

3 REPLIES
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: (DP) Support Tip: Data Protector 10.x schedules that were working mysteriously stop kicking off.

Hi @THE_DP_GURU,

Why mysterious? This is expected behaviour and Cell maintenance mode must be enabled by a user. There is usually an intention associated with running omnisv -maintenance 1.

I use it quite often during upgrades to makes sure the IDB is not changed beside of the setup process therefore having a persistent maintenance mode is just perfect.

If the user only wants to stop the scheduler omnitrig -stop or the Scheduler maintenance in the Consolidated Scheduler is the right choice. Restarting the services will re-enable the scheduler.

Regards,
Sebastian Koehler

---
Please assign a KUDO to this post, if you find it useful.
Micro Focus Expert
Micro Focus Expert

Re: (DP) Support Tip: Data Protector 10.x schedules that were working mysteriously stop kicking off.

Hi,

The reason it is mysterious is because this behavior is not well known.  Disabling schedules via omnitrig I would say would be the prefered method.  But some environments have their backups started by outside triggers such as commandline invocations of onbar, backint, SAP-HANNA, something similar or other schedulers outside of the DP.  Putting DP in maintenance mode prevents backups triggered outside of DP from running.    

Al Hutchins
New Member.

Re: (DP) Support Tip: Data Protector 10.x schedules that were working mysteriously stop kicking off.

Let me interject a bit more into this scenario.

It was discovered in the 10.02 environment (and perhaps others, but not confirmed) that there may be an occasion where the user will put their environment in maintenance mode, then stop/start the DP services and will discover that their environment is reporting all services (including CRS) are up and running.  Havinig the CRS show as "Active" instead of "Maintenance" should not be the desired outcome of a DP service restart after being previously placed in Maintenance mode.

When this occurs, the user is left to think that maintenance mode is not longer effectively running.  Furthermore, the user will be led to believe that things are OK after being able to successfully start backups once again.  However, the DP scheduler will not be able to start backups.

It is because of the fact that the "maintenance" file ('/etc/opt/omni/server/AppServer/maintenance ' or '\ProgramData\omniback\config\server\AppServer\maintenance') still resides and is ultimately the prohibitive factor in the scheduler not being able to start backups.

A simple removal of this file will not effectively ease this stiuation.  And in fact, the only proper method for removal of the maintenace file at this point is to place the envionment back into and out of maintenance mode to get the scheduler to function.