Restart incrementals from a given point...

[solmssen]

Hi - I made a config mistake, and my system is doing a new full backup because it's the first of July. I just did a full backup a week ago, and have incrementals to last night. Is it possible to cancel the full backup, and just pick up doing incrementals from where I left off? Would help me a lot with a storage situation. Windows 2008r2, Hyper-V, Agent 3.0x. Thanks for any info you can provide...

[wishr]

Hi Andrew,

Could you please specify what has been changed in the configuration, how it looked like before the change and looks now?

Thanks

[solmssen]

Nothing's changed - When I set up the job on 6/20 I set Active Full Backups on the 1st of Jan, April, July, and Oct as I usually do, without thinking about the fact that the job takes 40-50 hrs and uses up 5+ TB and I might not have room for 2 sets on my 10.6TB Synology backup target. So 7/1 rolled around and it started a new backup. If I cancel the backup, and change the schedule so there's no Full scheduled, will it continue with incrementals from the point it left off on 6/30, or do a new full anyway?

[wishr]

Not an issue. You may cancel the current Active Full backup and change the schedule as you described. That will result in VAW creating new incrementals.

[solmssen]

Not what happened. I cancelled, removed the scheduled Active Full for July 1, and relaunched. It's doing a Full now.

[wishr]

What is the current schedule for Active Fulls?

[solmssen]

Was set for Jan 1, Apr 1, Jul 1, and Oct 1. I cancelled the full backup, edited the job to remove the Jul 1 full (so only Jan 1, Apr 1, and Oct 1), and then restarted the job. It started writing a .vbk file.

[wishr]

Thank you, Andrew! We are trying to reproduce it now. I'll let you know the results.

[RubinCompServ]

Is there an update to this?

[wishr]

Hi guys,

Yes, we were able to reproduce it and can confirm that this behavior is expected.

You may workaround it by performing the following steps:
1. Start the job and then instantly stop it;
2. Make sure the corresponding .vbk has disappeared from the target storage;
3. Start the job and confirm it is producing incrementals now.

Thanks