Backup Copy Job, How Run without expiration Period

[Gve]

Hello
Is it possible to Schedule a Copy Job for running until the cycle is done ?

scenario :
The first cycle take 2 weeks to upload the initial backup to a Cloud Connect Provider (slow wan connexion)
The other cycle start every nigh at 22h and terminate 2 hours after.

I would like to avoid re Schedule a Job after the intial copy.
I have no possibility to seeding copy.


best regards

[veremin]

I think the only option you have here is to specify the increased copy interval for initial cycle. Though, once the initial cycle is finished, you'll be able to setup whatever copy interval you're willing to. Thanks.

[Gve]

Thanks for your answer
No possibility to use the "Periodically" Schedule and Continuously for "Periodically Kind" ?

[veremin]

It's running in continuous mode and copy interval defines how often restore point will be created on target repository and how often backup copy job should look for a new restore point. Thanks.

[Gve]

Ok
I'm VCP with a lot of clients, so it's heavy to do that for each new client.
If i don't do that the inial copy take much more time to send...

I will make and Schedule a Powershell script.
Is it possible to think about it for the next version ?

Thanks.

Sorry for my English

[foggy]

I'd recommend to consider implementing the ability of seeding, especially if you have a lot of clients. They could just ship initial copies to your facility and then map their jobs to existing backups for further incremental transfers.

[veremin]

Copy interval settings are configurable via PowerShell. Take a look at parameters located under GenerationPolicy (more specifically, RecoverPointObjective ones). Thanks.