- Posts: 4
- Liked: never
- Joined: Nov 30, 2010 10:30 am
- Full Name: Care Int
Bit of a crisis here:
After a full backup, I noticed that instead of server.vmdk being the default disk, it's something like server00002.vmdk or something like that.
Also, I believe it has something to do with the following error after backup:
RemoveSnapshot failed, snapshotRef "snapshot-214", timeout "3600000"
Unable to access file <unspecified filename> since it is locked
Veeam Backup will attempt to remove snapshot during the next job cycle, but you may consider removing snapshot manually.
Possible causes for snapshot removal failure:
- Network connectivity issue, or vCenter Server is too busy to serve the request
- ESX host was unable to process snapshot removal request in a timely manner
- Snapshot was already removed by another application
Now I believe that Veeam creates a snapshot during backup but is supposed to combine the snapshot with the original VMDK, is this correct? IF so, why is the snapshot not being combined after the backup, instead the VM is poiting to the 00002.vmdk file instead of the original. I remedied this issue by cloning the guest with the VM converter. But it's happened again and this time I went to manually poit the VMDK to the original and somehow it's gone! I'm running a restore right now HOPING I'm going to get this server back up or I'm DEAD.
I understand there some command to run through SSH, but this is annoying.
EDIT: I'm using Windows 2008 Server 64bit with the 64bit version of Veeam v184.108.40.206. I hear that a new version is out and this may fix the issue. Is this true?
- SVP, Product Management
- Posts: 28679
- Liked: 5188 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
More details > Solved error removing snapshot: Unable to access file