I see there is a chaining option to only start the backup if this backup is successfully finished. But the second back-up is scheduled when the first backup is not finished. What will happen with the next backup, will it wait to start till the first backup is finished or will it fail because another back-up process is already running?
Is there a way to program the backups in a chain, so the next backup will start after a backup is finished? What I want to reach is to program backup tasks like:
Run: Backup system to network share (2 weeks retention. every 2 weeks Sunday full, every day block)
Run: Backup data to network share (2 weeks retention. every 2 weeks Sunday full, every day block)
Run: Backup system to cloud (4 weeks retention. every first Sunday of the month full, every day block)
Run: Backup data to cloud (4 weeks retention. every first Sunday of the month full, every day block)
I don’t want to use hybrid because I don’t want to be depended to be the onsite (hybrid) is working
I want to use different retention for onsite and offsite
[reply=“QiQQ;917”] You can simply set schedule just for the first plan in the chain without setting up schedule for subsequent plans, that way you won’t have to worry about schedule, all backups will run one by one without overlapping.
Of course, you need to make sure that there is a certain time window between the chains.