srch

19.01.2012 · Getting the message "File is locked by running session (Name of Current Job)" Cause If the job was stopped incorrectly or the Veeam Server was rebooted, SQL might not have had enough time to receive the queries to properly stop the job in the database.

Datastore unmount error: Cannot unmount volume because file system is busy August ... Make sure the Veeam vPower NFS Service is running on the Mount Server.

Once the above requirements are met, an NFS FileStore location profile can be ... click New Profile on the profiles page and choose the Veeam Backup Server ...

Backup job fails, indicating that a file is locked by another process/task. ... is a PID for the VeeamAgent process, meaning Veeam has a lock on this file.

01.11.2016 · File lock message. I did have a few jobs that fails every other day with the ": Error: The process cannot access the file because it is being used by another process."-message. Veeam Support solved the issue, but I still would like a better message in the first place.

04.09.2018 · Re: File does not exist or locked. Post by foggy » Mon Sep 03, 2018 4:50 pm this post Forum search shows that restarting ESXi management agents helped in similar cases, though I'd continue looking into this with the help of support.

19.03.2018 · 1) Port 902 can telnet from backup server. 2) Manually, We can download the VM files to the backup server (with out using veeam) 3) We can backup VM's when it's power off state through Veeam. 4) we can ping IP as well as Esxi host name from backup server. Please help me resolve the above problem.

veeam file share backup license has been exceeded Open the “Settings”, go to “Network traffic”, and select “Use multiple upload streams per job”.

19.11.2014 · File Locks can come from a variety of sources. If a job is unexpectedly terminated due to a network drop, it is plausible that the Veeam Agent finished but never received a terminate command. If the repository uses deduplication, the storage may have too aggressive of a profile active and is locking the file(s) as soon as Veeam releases a lock ...

Failed to create or open file [G:\Backups\NightlyBackupV3\NightlyBackupXXXXXX-XX-XXXXXXX.vbk]. It looks like the file has been locked by another ...

But they have to be on there own host... Error message: Getting VM info from vSphere. Error: DiskLib error: [13].The file is locked or in use -- ...

The file is locked. The problem is on 3 Lync servers, they are running on the own host in a VMware cluster. Thats because there is something wrong with tha latest versjon of VMWare that makes Lync lose packages (or something) am not 100% what the problem was there. But they have to be on there own host...

Hi all, We have an environment of 5 ESXi hosts all connected to an iSCSI SAN. we use Veeam Backup and Replication 6 to backup the VM's.