Comprehensive data protection for all workloads
Post Reply
Coppens
Novice
Posts: 9
Liked: 2 times
Joined: Jun 19, 2019 7:12 am
Full Name: René Klomp
Contact:

Not able to retry synthetich full

Post by Coppens »

Yesterday some Hyper-V back-up jobs didn't run due to a network problem.
That is solved however I would want te rerun a synthethic full job that was missed.
Veeam however marked the problem with the warning 'No object to process'.
My guess it was already running the job and during the run the network failed.

Is there any way to retry this job although it has completed with a warning in stead of failed?

Some details:
Windows Server 2016 Standard
Veeam Backup & Replication 11 (11.0.1.1261 P20230227)
Mildur
Product Manager
Posts: 8735
Liked: 2294 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Not able to retry synthetich full

Post by Mildur » 1 person likes this post

Hello René

The next job run will create an incremental backup. You need to wait for the next scheduled sync full.

Workaround for retry synthetic full: In the job settings, change the day when the synthetic full is created to today. The next job session today will create the synthetic full.
Veeam however marked the problem with the warning 'No object to process'.
My guess it was already running the job and during the run the network failed.
A retry session will only backup the VMs if they were not yet processed. Looks like the backup may already have finished for all VMs.
Veeam Backup & Replication 11 (11.0.1.1261 P20230227)
Please consider an update to v12.1. V11 will be end of support by the end of this month.
End of Support: https://www.veeam.com/product-lifecycle.html
Most recent version: https://www.veeam.com/kb2680

Best,
Fabian
Product Management Analyst @ Veeam Software
Coppens
Novice
Posts: 9
Liked: 2 times
Joined: Jun 19, 2019 7:12 am
Full Name: René Klomp
Contact:

Re: Not able to retry synthetich full

Post by Coppens »

Good suggestion.

It would be better if Veeam would not mark it as success with warning but as an error.

Thanks for the update tip. On it.
Post Reply

Who is online

Users browsing this forum: No registered users and 111 guests