Too many VMSN and VMDK files under VM folders[More than 300] ... How can I delete these files ?
Server is currently online and in production.
Server is configured with SRM,
backup tool - symantec netbackup,
Server size is 20 to 30 % extra than its original size.
timestamps is different for all files[bunch of vmsn and vmdk files are with same time stamp]
No snapshots ???
Is that what Snapshotmanager tells you ?
Dont listen - Snapshotmanager just looks at the vmsd-file and if that has been messed up by automatic backuptools it will be blank.
How can I delete these files ? - you should not even try to do that at the moment.
First step is to find out how many virtual disks are used by this VM.
To do that open the vmx-file with a text editor and find all entries like scsi*:*.filename = "name-00000*.vmdk
For each of this virtual disks you may have one hundred or even more snapshots.
You may also have a large number of virtual disks with just a few snapshots for each of them.
Before we can give you instructions for a safe way to get rid of your snapshots it would help to see your current vmx-file, the last vmware.log and a list of all files (including size and date)
Do not listen when somebody tells you: just creatre a new snapshot and then click "delete all" - that approach is ok with just a few snapshots. But it is way to risky if there are 100 snapshots.
What about your backuptool - didn't it tell you that the last backups failed ?
It would be a good idea to check the date of your last good backup.
Are you receiving any prompts/warnings about "Snapshot Consolidation needed", or anything to that effect?
continuum of course makes some great points; be really careful about simply trying to "Delete"/commit all of the snapshots.
As a trick, is it possible to clone the VM?
It has been a bit since I've had to do so, and someone please correct me if I need to update my information, but in the past I've even used VMware Converter to "convert" a VM with a lot of snapshots - you're not really "converting" it as it is already a VM, but when all is said and done the new VM won't have all of the -delta files/disks.
please find below details for more information.
Snapshot manager not showing any snapshot.
I check and found only four vmdk files are showing in vmx file. As server is configured with only four drives.
However on daily bases it creating few vmdk and vmsn files and its not getting deleted/removed automatically.
Its consuming around 1.5 GB space.
We need a list of all the files you have in the VM-directory.
Connect to the ESXi with putty - change directory to the directory where that VM is stored.
Then run the command ls -Ralh > filelist.txt
Attach filelist.txt to your next post.
It makes no sense to continue automatic backups of this VM before this problem is solved.
"Clone or V2V Migration using vconverter.....Is it really will help me????"
Well, the V2V is a "Band-Aid" that might or might not fix the problem permanently - for a given VM, the V2V'd copy will have the .vmdk files consolidated into a single set of .vmdk/-flat.vmdk files, and I've seen this "fix" the problem more than once meaning that for a given VM, the clone does not continue having the problems but as continuum said you really want to determine the *why* this is happening in case the V2V'd/clone VM continues having the issue.