Record the job details

Capture Job ID, datasource, protection group, start time and current status before making changes.

Check active operations

Determine whether another backup, synchronization, recovery or replica consistency operation is using the same datasource.

Review MABS and SQL logs

Correlate the job timestamp with MABS event logs and SQL Server activity. Look for blocked database operations or worker failures.

Check processes

Review MABS worker processes and resource usage. Avoid terminating a process that is servicing another active backup job.

Avoid unnecessary service restarts

If production backups are running, do not restart MABS services simply to clear a stale status. First establish whether the job is still progressing or waiting on a dependency.

Recovery

After the active dependency clears, verify whether the job transitions automatically. If escalation is required, preserve logs and job identifiers before intervention.

More practical infrastructure guides

Browse the TechRunbook article library for Windows Server, VMware, Hyper-V, Azure, PowerShell and MABS troubleshooting.

Browse all articles →