Comprehensive data protection for all workloads
Post Reply
Daveyd
Expert
Posts: 283
Liked: 11 times
Joined: May 20, 2010 4:17 pm
Full Name: Dave DeLollis
Contact:

Ocassional job failures

Post by Daveyd » Oct 08, 2010 12:49 pm

I have a job that is backing up 20 VMs with 7 rollbacks.

On ocassion, the job and its 3 retrys will fail. On EVERY VM I get the following eror message: Constructing rollback file name TextToTar failed Client error: The process cannot access the file because it is being used by another process Failed to create or open file [\\xxx.xx.x.xxx\Veeam\Enterprise VM backups\Enterprise VM Backups.vbk]. Failed to backup text locally. Backup: [veeamfs:0:8ae0ec7e-d592-4680-a04c-f3cc4522794c (vm-3766)\summary.xml@\\xxx.xx.x.xxx\Veeam\Enterprise VM backups\Enterprise VM Backups.vbkVBK: 'veeamfs:0:8ae0ec7e-d592-4680-a04c-f3cc4522794c (vm-3766)\summary.xml@\\xxx.xx.x.xxx\Veeam\Enterprise VM backups\Enterprise VM Backups.vbk'RBK: ''].

Is that saying that something else is using the .vbk file while Veeam is trying to backup each VM? Or is is something else? This error doesn't happen every day

Vitaliy S.
Product Manager
Posts: 22860
Liked: 1538 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Ocassional job failures

Post by Vitaliy S. » Oct 08, 2010 1:38 pm

Hello Dave,

Yes, it seems like some other application is locking the vbk file, which prevents Veeam from accessing it and updating the data. Provided that this doesn't happen every time you run the backup job, I would suggest checking for any antivirus software or other applications (tape integration software) on the target machine, this might shed some light on your issue.

Thank you!

Daveyd
Expert
Posts: 283
Liked: 11 times
Joined: May 20, 2010 4:17 pm
Full Name: Dave DeLollis
Contact:

Re: Ocassional job failures

Post by Daveyd » Oct 08, 2010 3:36 pm

I have my Veeam backups pointed to a CIFS share that resides on an Exagrid dedupe appliance. There is no AV on the Exagrid appliance that would be scanning the CIFS share. The CIFS share that contains the Veeam backup files gets backed up to tape once a week via Backup Exec but that runs at opposite times as the Veeam backups. I'll have to do some digging.

ricardom
Novice
Posts: 3
Liked: never
Joined: Jun 21, 2011 9:27 pm
Full Name: RicardoM
Location: Los Angeles
Contact:

Re: Ocassional job failures

Post by ricardom » Jun 21, 2011 9:39 pm

Daveyd wrote:I have my Veeam backups pointed to a CIFS share that resides on an Exagrid dedupe appliance. There is no AV on the Exagrid appliance that would be scanning the CIFS share. The CIFS share that contains the Veeam backup files gets backed up to tape once a week via Backup Exec but that runs at opposite times as the Veeam backups. I'll have to do some digging.
@Daveyd Did you ever find a solution to the error? I'm experiencing the the same error.

cindermonkey
Novice
Posts: 4
Liked: never
Joined: Jul 29, 2011 4:05 pm
Full Name: Scott
Contact:

Re: Ocassional job failures

Post by cindermonkey » Jan 14, 2012 7:16 am

Listen, if anyone runs into this error on an Exagrid, it is because one of your shares does not have an IP (or more than one) of your Veeam Backup Server or a Transport Proxy or Proxies. Make sure go through your shares and double check that you did not miss one. Also don't forget about that registry scrip in the online library and that you will need to merge it even on the transport proxies (easy to forget after deploying the proxies from the veeam backup server).

Post Reply

Who is online

Users browsing this forum: Ashb, Bing [Bot] and 23 guests