You should be able to edit the alert, and use elements of the alert definition in a top n dashboard widget to show the list of snapshots
1 of 1 people found this helpful
Hello, you can get list of the snapshots when you get details of the alert via email. Just configure SMTP settings, modify the alert to send you results
and then you can parse the snapshot files from body of the email.
An example of the email:
Alert Active for:
1. Datastore: esx-05:LocalStorage01 ([esx-05:LocalStorage01] VMAN001/VMAN001-000005.vmdk, )
2. Datastore: datastore2 ([datastore2] sql_test/sql_test_7-000006.vmdk, [datastore2] sql_test/sql_test-000006.vmdk, )
Do you have 6.1.1 deployed? We had a problem with On-Demand Reports being broken in 6.1 that was fixed in 6.1.1. If it's still broken in 6.1.1, do you have an open ticket with support so we can track this down?
Yes, and yes. I had a case open, 701014, which I tried to reopen, and I just opened a new one, 710412.
I guess I was not 100% correct--the phantom snapshot files alert contains a subset of the files that I'm looking for, but it doesn't completely identify all orphaned files, so I'll need to see whether the orphaned files report can be resurrected to get the whole picture.
I'm new to VMAN.. just installed version 6.3 about a week ago. I experienced the exact same issue. A handful of my Virtual machines had VMDK file names like %VMNAME%_#-00000# Example: VSRVxxxx_4-000003.vmdk This raised the phantom snapshot alerts in VMAN.
After trying several different possible resolutions:
Deleting all snapshots on the VM
Deleting any vmdk files that are not in use inside the VM folder on the datastore.
Running consolidation on the VM.
Created a new snapshot and deleted it.
None of these fixed my issue the VMDK file name was still VSRVxxxx_4-000003.vmdk
Resolution that worked for me. I'm running Vsphere 5.5
Storage Vmotion the virtual machine disks to another datastore. After the VMotion the VMDK was renamed to the correct file name and the Alert in VMAN is now in a lowered state.
Before Vmotion file name - VSRVxxxx_4-000003.vmdk After Vmotion file name - VSRVxxxx_4.vmdk
I guess it's been a while since I've logged into Thwack . . . anyway, I would expect the VMDK filenames you are posting to be associated with a snapshot. It sounds like VMware did not clean up after a snapshot and VMAN got confused.