Skip to main content
Solved

Automatic synthetic full scheduling with multiple schedules

  • May 12, 2026
  • 2 replies
  • 15 views

Forum|alt.badge.img+3

Hello community,

 

we currently have the following situation with our synth full in our plans:

Copies:

  • Primary - 15 days / deduped
  • Sync copy to tape / 30 days
  • Selective copy to tape (monthly fulls) / 1 year

Synth fulls:

  • Automatic every 15 days
  • On the 1st every month for extended retention

Previously I reduced the automatic synth full to 15 days to better align with the retention and therefore have better aging regarding the cycles.

We will also enable WORM on the Primary in the near future so I want to leave it this way to also align with DDB sealing.

My question is about the synth scheduling:

Because of the 15 days schedule I now encountered a situation where a synth ran on the 29th and then shortly after on the 1st because of extended retention.
This of course causes extensive amount of data on the sync copy as the full backups get expanded onto the tapes.

Should I sacrifice the automatic schedule in favor of a manual synth full backup (e.g. every month on the 15th) or are there other ways to avoid these situations with the automatic schedule?

 

Thanks in advance for any suggestions 🙂

Best answer by Sureshkumar S

Hi ​@Marcel_RE ,

Good day!

A simple way to avoid this is to move away from interval-based schedules like every 15 days, and instead use fixed dates.

For example, you could run:

  • One synthetic full on the 1st of every month for extended retention
  • Another one mid-month, say around the 15th

This way, you won’t have two synthetic fulls running back-to-back, which helps avoid unnecessary data getting written again to tape.

Regards,

Sureshkumar S

 

2 replies

Sureshkumar S
Vaulter
Forum|alt.badge.img+12

Hi ​@Marcel_RE ,

Good day!

A simple way to avoid this is to move away from interval-based schedules like every 15 days, and instead use fixed dates.

For example, you could run:

  • One synthetic full on the 1st of every month for extended retention
  • Another one mid-month, say around the 15th

This way, you won’t have two synthetic fulls running back-to-back, which helps avoid unnecessary data getting written again to tape.

Regards,

Sureshkumar S

 


Forum|alt.badge.img+3
  • Author
  • Apprentice
  • May 13, 2026

Hi ​@Sureshkumar S ,

so I assume there are no additional options on automatic synthetic full schedules where I could do fine adjustments to the scheduling behaviour?