PowerProtect Data Manager 19.10 Administration and User Guide

Resume misfire jobs after a PowerProtect Data Manager update

During an update, the PowerProtect Data Manager system enters maintenance mode. Any job that is not in queue and is scheduled to run during the time that the PowerProtect Data Manager system is in maintenance mode will be missed. These missed jobs are known as misfires. As of this release, PowerProtect Data Manager uses the Quartz Scheduler to resume scheduled workflows when the service recovers or when the schedule resumes.

1. Log in to the PowerProtect Data Manager server by using SSH.
2. Copy the entrypoint.sh file from the scheduler container by typing the following:
   docker cp scheduler:/scheduler/bin/entrypoint.sh .
3. Configure the misfire conditions in the entrypoint.sh file:
   NOTE Before the last line in the output, -jar /${APP_NAME}/lib/scheduler-core.jar), add the lines for each misfire condition.
   1. To enable misfire and trigger each job once, add the following properties and corresponding values:

      -Dspring.quartz.properties.misfire.cron.strategy=WITH_MISFIRE_HANDLING_INSTRUCTION_FIRE_AND_PROCEED \

      NOTE This condition is enabled by default.

      -Dspring.quartz.properties.misfire.calendar.strategy=WITH_MISFIRE_HANDLING_INSTRUCTION_FIRE_AND_PROCEED \

   2. To enable misfire and trigger each job as many times as misfire happens, add the following properties and corresponding values:

      -Dspring.quartz.properties.misfire.cron.strategy=WITH_MISFIRE_HANDLING_INSTRUCTION_IGNORE_MISFIRES \

      -Dspring.quartz.properties.misfire.calendar.strategy=WITH_MISFIRE_HANDLING_INSTRUCTION_IGNORE_MISFIRES \

   3. To disable misfire, add the following properties and corresponding values:

      -Dspring.quartz.properties.misfire.cron.strategy=WITH_MISFIRE_HANDLING_INSTRUCTION_DO_NOTHING \

      -Dspring.quartz.properties.misfire.calendar.strategy=WITH_MISFIRE_HANDLING_INSTRUCTION_DO_NOTHING \

4. Save the entrypoint.sh file to the scheduler container by typing the following:
   docker cp entrypoint.sh scheduler:/scheduler/bin/
5. Restart the scheduler service by using one of the following methods:
   • Type docker container restart scheduler
     NOTE For the configuration to be applied successfully using this method, you can only restart the container. If you restart your scheduler service or your PowerProtect Data Manager operating system, the configuration will be lost.
   • Type the following to save the docker image and restart the scheduler service:

     docker commit scheduler dpd/ppdm/ppdmc-scheduler:PowerProtect Data Manager version

     scheduler restart

     where PowerProtect Data Manager version is the PowerProtect Data Manager version that is deployed on your system.

     You can use this method to permanently apply the configuration change after restoring the docker image.

     NOTE Ensure that the PowerProtect Data Manager version specified in the commit command matches the PowerProtect Data Manager version that is deployed on your system.