Unable to Run an On-Demand Synthetic Full Backup

Valid on Windows platforms.

Symptom

When you submit an on-demand synthetic full backup job, the job does not execute and a message dialog opens indicating the reason why the synthetic full backup was not executed.

You may receive one of the following four messages:

  1. Cannot submit synthetic job since this job has been modified
  2. The synthetic full backup job was modified and no real full backup and incremental job is done.
  3. Unable to submit the data synthetic job, or there are no sessions that need to be synthesized
  4. The synthetic full backup job cannot synthesize full sessions because there are no suitable sessions that can be synthesized. This can occur due to two possible scenarios:
    • Sessions were already synthesized before this job was submitted, so there is no need to synthesize them again.
    • A previous incremental session was not backed up successfully.
  5. Data synthetic job submitted successfully
  6. Data synthetic job submitted successfully
  7. n sessions were skipped that failed
  8. Even though there were some sessions that were synthesized to full sessions, some of the sessions were either skipped or failed. This can occur due to two possible scenarios:
    • Sessions were already synthesized before this job was submitted, so there is no need to synthesize them again.
    • A previous incremental session was not backed up successfully.

Solution

  1. No action is required for this message. It will do a real full backup on the next synthetic day.
  2. If you have any sessions that failed, verify the previous incremental session and make any necessary adjustments to ensure a successful backup.

  3. No action is required for this message.

  4. If you have any sessions that failed, verify the previous incremental session and make any necessary adjustments to ensure a successful backup.