Active replication schedules may become suspended, leading to incomplete replication tasks. This knowledge base article addresses the possible causes and provides solutions to this issue.

1. Manual Suspension: Active replication jobs can be manually suspended from the recovery page console while they are in progress.

2. Priority Conflict: The VembuBDR backup server may automatically suspend active replications for a backup if a backup request is received from a client machine to the backup server. This happens because backup jobs have higher priority compared to replication jobs. The replication is automatically resumed once the active backup schedule is completed.

1. Manual Suspension: If an active replication job has been manually suspended, it can be resumed from the recovery page console. Resuming the job will initiate the replication immediately.

2. Priority Conflict: In cases where the VembuBDR backup server suspends active replication due to a priority conflict, please be aware that this behavior is intentional. Backup jobs take precedence over replication jobs. The backup server will automatically resume the replication of the affected backup once the active backup schedule is completed.

Note: If the issue persists even after following the above steps or if you require further assistance, please contact Vembu support at vembu-support@vembu.com. Our team is here to assist you in resolving any outstanding concerns.