If the primary JobScheduler of a passive cluster is paused then the backup JobScheduler adopts this and is paused too when it goes active

Feature

• The Backup JobScheduler of a passive cluster adopts the pause/running state of the primary JobScheduler when it goes active.

Current Situation

• If a Backup JobScheduler is waiting for activation then it ignores commands to pause or continue it.
• But a Backup JobScheduler can start together with a pause command so it is paused when it goes active.