ADBO and running synthetic manually

[kyle_beckham_2]

Last night our incremental job ran fine and then our full synthetic job for ADBO started and then failed. This job is setup to run at the same time the incremental, but the policy has it setup to run after the incremental.

Run now I went into backup exec and did a Run Now of the synthetic job and its sitting there with a status of queued? Is that job doing anything or does it HAVE to have the incremental run before it always even when we run it manually before it will run?

[Shilpa_pawar_2]

Hi,

Which error do you see in job log when the synthetic backup fails?

A Synthetic backup is achieved in the following manner:
1. A Full backup is run that will act as a Baseline backup; any valid backup device can be targeted.
2. Incremental backups are run to gather data that has changed since the Baseline backup; incremental backups must have a Backup-to-Disk folder as the target backup device.
3. A Synthetic backup is run to combine the most recent version of files from the Baseline backup sets and Incremental backup sets; any valid backup device can be targeted.
4. The cycle repeats itself with the most recent Synthetic backup serving as the Baseline backup

Are there any active alerts in backup exec, when the job goes to status Queued?

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.