-
- Novice
- Posts: 5
- Liked: never
- Joined: Jun 07, 2013 2:51 am
- Full Name: Jeff Nevins
- Contact:
Synthetic Full Stuck at 80%
My backup is stuck at "Synthetic full 80% done" in the statistics view (for the past 3 hours).
The previous message is "All VMs have been processed."
How can I figure out what the problem is here?
Thank you.
The previous message is "All VMs have been processed."
How can I figure out what the problem is here?
Thank you.
-
- Chief Product Officer
- Posts: 31804
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Synthetic Full Stuck at 80%
Open a support case and let our engineers investigate the debug logs.
-
- Enthusiast
- Posts: 44
- Liked: 2 times
- Joined: Dec 01, 2009 8:09 pm
- Full Name: Addy
- Contact:
Re: Synthetic Full Stuck at 80%
I had the same case, stuck at 85%.
options from support: kill the task or try to stop it. Disadvandage: your synthetic full is lost.
My job was running for 77hours (it did not interfere with anything else). It had been on 85% for about 20 hours, but all of a sudden it completed successfully. Looks like the % are not updated anymore at the end of the process.
So another option could be: wait it out.
options from support: kill the task or try to stop it. Disadvandage: your synthetic full is lost.
My job was running for 77hours (it did not interfere with anything else). It had been on 85% for about 20 hours, but all of a sudden it completed successfully. Looks like the % are not updated anymore at the end of the process.
So another option could be: wait it out.
-
- Chief Product Officer
- Posts: 31804
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Synthetic Full Stuck at 80%
This is unexpected (% not updated) and I cannot see why would they stop updating. What is your support case ID?
-
- Novice
- Posts: 4
- Liked: never
- Joined: Jul 24, 2012 12:10 pm
- Full Name: Fabrizio Da Pra
- Contact:
Re: Synthetic Full Stuck at 80%
I had the same problem and it was due to the Synthetic part of the job,
after moving the veeam Lun from the old (windows 2003) veeam server to a new veeam 7 (windows 2012) server the next job was a very big incremental job, nearly as big as a Full backup and the synthetic was taking ages, I just killed the job and did an active full.
After that everything works fine
after moving the veeam Lun from the old (windows 2003) veeam server to a new veeam 7 (windows 2012) server the next job was a very big incremental job, nearly as big as a Full backup and the synthetic was taking ages, I just killed the job and did an active full.
After that everything works fine
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 119 guests