Hi
I have checked from my customer all backupjobs. In the Gui it sys in Last result Success! If I go inside the Job I see Processed 0Kb, there are no objects to backup. On the Veeam Backupdirectory I can't see a file from this backuped server! So the GUI show me the wrong result! I deleted the Job and created the same again, now its working.
This means I have to check all Jobs although it shows success???
Thanks
-
- Enthusiast
- Posts: 85
- Liked: 2 times
- Joined: Feb 05, 2010 4:12 pm
- Full Name: Zeller Werner
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Backupjob in Gui says Success, nov Backupfile
Hello Werner,
The last job run is successfull due to the Retry option being initiated. If you see there were no objects to backup that means the first backup attempt failed to get the list of VM to backup for some reason and later on the backup of zero objects was successfull. To avoid such situation you may disable retry option.
Hope it helps!
The last job run is successfull due to the Retry option being initiated. If you see there were no objects to backup that means the first backup attempt failed to get the list of VM to backup for some reason and later on the backup of zero objects was successfull. To avoid such situation you may disable retry option.
Hope it helps!
-
- Enthusiast
- Posts: 85
- Liked: 2 times
- Joined: Feb 05, 2010 4:12 pm
- Full Name: Zeller Werner
- Contact:
Re: Backupjob in Gui says Success, nov Backupfile
Hi Vitaliy S,
thanks, yes that can be the reason, I changed the retry option.
Thanks!
Have a nice weekend!
Novell2
thanks, yes that can be the reason, I changed the retry option.
Thanks!
Have a nice weekend!
Novell2
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Backupjob in Gui says Success, nov Backupfile
I would not recommend disabling Retry option though. It is very useful to handle intermittent network failures, so disabling it will reduce the overall backup success rate dramatically. I have asked devs to fix the above mentioned bug in v5, so that the job is not marked as successful when no VMs were backed up.
Who is online
Users browsing this forum: Baidu [Spider], Google [Bot], restore-helper and 69 guests