Synthetic full not done past midnight

[perjonsson1960]

Folks,

If I configure a daily backup job to create synthetic fulls each Saturday, and the job doesn't finish until past midnight, thus on Sunday, then the synthetic fulls don't seem to be done. Is this true for all jobs that start on one day and "spills over" to the next day? And is it the same with health checks and defrag/compact? If so, maybe it would be better to check which day of the week it is at the beginning of the job, instead of towards the end?

Regards,
Per Jonsson
Sweden

[foggy]

Hi Per, this looks unexpected, synthetic full tracks the job start time. Please contact technical support for verification. Thanks!

[perjonsson1960]

Okay. I have checked the logs more closely. It seems that the job in question completely missed an entire day. The synthetic full is set to be done on Sunday. And the job is configured to start AFTER another job is finished. On Saturday the job in question started just before midnight and ended a few minutes after midnight (Sunday), and on Sunday the job before it took a little longer, so that job didn't finish until after midnight, which was Monday. Thus, the job in question didn't start at all on Sunday, and therefore no synthetic full... So i guess this is "by design". I will have to reschedule the jobs somehow...

[foggy]

Yes, this is totally expected and actually one of the reasons not to chain the jobs like that.

[perjonsson1960]

I guess that you learn some things the hard way...
Sometimes I tend to use features that actually exist, because it seems like a good idea at the time...

Thanks!

[perjonsson1960]

When you rightclick a backup job there is an "Active full" option. Would it be possible to introduce a "Synthetic full" option, if you want to create a synthetic full manually?

[foggy]

There's a dedicated thread regarding similar requests.