First backup copy job

[InFrance]

Hi,
Can you please tell me what is the best strategy for running a first copy job ?

I estimate the copy job will take a more than 2 full days to run the first copy job to object storage.
We have a bank holiday weekend here so I would like to profit from that extra time.

I have configured the copy job to use the repository as its source and to start after the local backup jobs have completed.

Should I schedule the copy job to run only on the Friday night (instead of daily), without a copy window configured, allowing the job a full 2/3 days to complete.

I would then modify the schedule and reduce the copy window after the bank holiday weekend.

Is this the best way or should I be doing something different?

Many Thanks

[david.domask]

Hi InFrance,

I think your plan is sound, remove the Backup Copy Window for the first run, and then return the window after the initial copy completes.

As per the User Guide for Backup Copy, the backup copy is designed to accommodate if the source job needs to run, so no need for concern there:

If a specific task in the backup copy job locks the source backup chain to read data from it, and the source backup job that needs to write data to this backup chain starts at this moment (for example, for reverse incremental backup), the task in the backup copy job is put on hold. The backup copy job can continue processing other tasks that use other sources (for example, backup files created by other backup jobs). After the source backup job releases the backup chain, the backup copy job resumes processing machines in this backup chain.

So indeed, remove the Backup Copy window for the initial copy, and then return it after the copy completes.

[InFrance]

Thank you for your quick reply

Regards

[SAFA_IT]

You can also use the Exclusions... button on the Objects screen to exclude most of the guests, let the schedule run with one or two smaller guests, then add one of the excluded guests each day until all the guests are included.