Microsoft 365 consolidation job behavior in Backup Exec
book
Article ID: 100063639
calendar_today
Updated On:
Description
Error Message
The duplicate job from non-dedup disk storage to tape does not start until the consolidation job is completed.
Cause
The behavior is as per design in Backup Exec version before 24.
Resolution
Parallel consolidation is allowed from Backup Exec 24 release.
Backup Exec behavior prior to BE 24 :
The consolidation job or duplicate job should be scheduled such that they run at mutually exclusive times.
Behavior of Microsoft 365 (M365) consolidation job prior to BE 24:
- When the M365 consolidation job is running, direct backups to tape storage works.
- When the M365 consolidation job is running, duplicates from deduplication storage to tape shows running without a byte count. The duplicate job starts to show a byte count when the consolidation job has been completed.
- When duplicates from deduplication storage to tape are running and the M365 consolidation job is started. It shows loading media with a 0 byte count and changes status to Queued but eventually starts to run with increasing byte count.
- M365 Incremental Backup job runs even if a duplicate job to tape from deduplication storage is running.
- Two consolidation jobs will not run at the same time simultaneously.
- The duplicate jobs from non deduplication storage disk ( B2D) to Tape will not run when the consolidation job is running.
Issue/Introduction
Microsoft 365 consolidation job behavior in Backup Exec.
Error Message
The duplicate job from non-dedup disk storage to tape does not start until the consolidation job is completed.
Additional Information
ETrack: 4153452
Was this article helpful?
thumb_up
Yes
thumb_down
No