• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 22353
  • Last Modified:

Veeam Backup - encountered "File does not exist or locked" error on some of my VMs

Dear Experts,

I am using Veeam Backup and Replication to do backup on our Virtual Machines sitting on ESXi vSphere 4.1

In one of my backup jobs, there are 3 virtual machines to be backed up daily. 1 of the VM is having no problems, the other 2 is getting the error as shown below:

Initializing target session
GetLocalText failed
Client error: File does not exist or locked. VMFS path: [[iscsistore1] SGSIN1S002 LIVE/SGSIN1S002 LIVE.vmx].
Please, try to download specified file using connection to the ESX server where the VM registered.
Failed to create NFC download stream. NFC path: [nfc://conn:10.129.96.81,nfchost:host-107,stg:datastore-45@SGSIN1S002 LIVE/SGSIN1S002 LIVE.vmx].

Server error: End of file


Any help is much appreciated. Thanks in advance.~

0
SG_IT
Asked:
SG_IT
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have you checked the server is on that datastore?
0
 
SG_ITAuthor Commented:
thanks hanccocka for your reply.
i've checked, yup they are on that datastore.

any other things i can check?

thanks.
0
 
coolsport00Commented:
How are you doing the backups? i.e. How is the b/u job configured? If you use VMware vStorage API, what happens is Veeam takes a snapshot of the VM and attaches it to the VM that Veeam is installed on (if indeed you have Veeam installed on a VM). After the b/u of the VM is done, the snap is released from the Veeam VM and is deleted/committed, and the process continues to the next VM in the b/u job until the backup job has completed backing up all VMs. Sometimes, once the b/u of a VM is done, Veeam (for whatever reason) doesn't 'release' the snap from the VM Veeam is installed on. You can easily check this by going into the Veeam VM's Edit Settings and see if there is another 'hard disk' attached to your VM. You will see the name of the hard disk as your failed VM (the name will be greyed out). To release the disk/snap, just simply remove the disk from the Veeam VM (*DO NOT SELECT TO DELETE FROM DISK, but simply REMOVE FROM VM*). You can then restart the b/u job and it should work. Regardless, if that is what happened, I recommend contacting Veeam to see why the snap isn't releasing from the VM.

All that being said, if you don't have a snap/hard disk on your Veeam VM, or if your Veeam server isn't a VM, either the path Veeam uses to 'see' your VM disks can't be found, or something has a lock on your VM, like having an active snapshot or something like that. Make sure your 2 non-working VMs don't have snapshots. Also, look in the VM's folder on the datastore to see if you see any .lck files. If you do, there is your problem...something has a 'lock' on your VM and its files such that the b/u job can't run.

Regards,
~coolsport00
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
SG_ITAuthor Commented:
test.
0
 
SG_ITAuthor Commented:
sorry i had issues replying earlier.

yes coolsport00, we have veeam installed on one of the VM, then we added the vCenter server. from there, the backup jobs are then created (using Virtual Appliance mode).
i am unsure where to locate the Edit Settings u mentioned? to check if there is another h/d attached.
can u advise me? is it in the properties of the Job backup?

thanks much.
0
 
coolsport00Commented:
Go to the VM that Veeam is installed on. Rt-click on the VM and select Edit Settings. On the Hardware tabl (default tab that is displayed), see if there are any other Hard Disks attached to the Veeam VM that is not part of the VM. The 'normal' hard disk will be accessible and modifiable. If there is another hard disk attached, it will probably 1. be the name of one of your VMs your backing up or replicating and is failing, and 2. the disk modification area will be greyed out.

~coolsport00
0
 
SG_ITAuthor Commented:
hi coolsport00, i've checked. there is no "extra" hd attached.
u mentioned searching for any .lck files? these would be find where?

thanks..
0
 
coolsport00Commented:
The VM(s) you're not able to backup/replicate. Go to the datastore they are on (Datastore Browser) and go into the VM's folder to see if there are any .lck files...
0
 
SG_ITAuthor Commented:
none are .lck files.
i have .vmdk, .vmxf, vmsd, vmx and log files.
how do i view the log files? i tried to copy or download..it won't work.

should i just re-create a new job and point to a new datastore to see if it works?
0
 
coolsport00Commented:
The Veeam log files can be accessed by going in the Veeam console -> go to Help menu -> Support. It will open up a list of job logs. Look for the log with the job name that's failing & see if anything in it stands out. If not, & you're able to, yes...try to recreate the job. Also, make sure you have proper SSH credentials for the hosts you added under the Servers heading in the Veeam console.
0
 
SG_ITAuthor Commented:
hmm i created new jobs, this time pointing to another location for the backup to be stored.
Still i face the same issues, 2 out of 3 VMs will fail with the same type of error.

0
 
coolsport00Commented:
My only other suggestions at this point are 1. check the logs to see if anything stands out; 2. verify host credentials, although if all your VMs are on the same host and at least 1 VM is backing up correctly, that probably isn't the issue; 3. Veeam support.

~coolsport00
0
 
SG_ITAuthor Commented:
thanks coolsport00, yup have sent to Veeam support.
Will update when i get the resolution.
0
 
coolsport00Commented:
Great; interested in hearing what they have to say...keep me posted.

~coolsport00
0
 
SG_ITAuthor Commented:
Hi coolsport00,
After checking the logs, Veeam support replied:
"Please make sure that credentials \administrator have full administrative permissions on the Vcenter.
And make sure you have DNS resolution between virtual center, esxi host and the client PC used to upload files from the datastore."

Could you briefly guide me on how to check?
is it on Veeam Backup or the vCenter?

Many thanks in advance.
0
 
coolsport00Commented:
Well, basically, you more than likely installed vCenter Server with admin credentials. When you added vCenter as a 'Server' node in Veeam, you had to use those same admin credentials. If you click on the "+" next to your vCenter Server in Veeam, you should be able to expand it to see your ESX/i hosts. Otherwise, you'll get prompted to set your credentials. So, that's what they are referrring to (I hate when they say only that and don't call you and help you further with it; Veeam support used to be better than what it is now).

For DNS, that just means you should have a DNS server in your org. Make sure your vCenter Server, ESX/i hosts, and your workstation all have DNS records properly configured (simply an 'A' record).

~coolsport00
0
 
SG_ITAuthor Commented:
Hi coolsport00,
thanks for the reply, yup when i click on the "+", i am able to expand and see all the ESXi hosts.

forgot to mention, Veeam support also did a test:
On the server that has Veeam B&R, install the vSphere client, login using the admin credentials.
Then access the datastore and attempt to download the vcenter.vmx file.
i get an I/O error which suggest to them that it is not an Veeam issue but rather VMware.

0
 
coolsport00Commented:
Hmm...at this point, I'm outta ideas. This is a 'new' b/u correct? Or, are the 3 VMs in 1 job and 2 of the VMs complete and the 1 doesn't? Veeam should still address this because...well...you're getting an error while trying to use *their* app to do VM back ups. If it's something outside of their product that needs addressed, they should know what it is needing attention.
0
 
PenguinNCommented:
Did you find a solution?. What hardware are you running on?
0
 
SG_ITAuthor Commented:
hi all, i didn't get a solution for the problem.
but i have re-added the storage & recreated the backup jobs, it has been working since.
0
 
coolsport00Commented:
Thanks for the update. Weird issue for sure. Glad it's working for you now...

~coolsport00
0
 
SG_ITAuthor Commented:
unable to solve.
0
 
fix-my-computerCommented:
We have/had the same issue. I called veeam (who as usual are as useful as a chocolate fireguard!) who said i needed to restart the management agent on the hosts. I choked as we have 10 hosts. Anyways after a little research i found that all the erroring vm's were all on the same host.
Restarted the management agent - as per Veeam's help - Nothing
Put it in to maintenance mode and rebooted - Working!!

As with most things veeam, i may never know what happened, however it is working without having to recreate my jobs again.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now