Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone had problems with SMVI were SMVI does not delete the snapshot from ESX and thus causes the VM's to say in a quiesced state. I have a customer that has about 50 VM in this state and it has caused major problems with the performance of the VM's.
Thanks
Dale
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could you please log a support case with all the logs as well for this. NGS can get to the root cause of the issue and help you get this fixed. We even have a script for orphaned snapshots More information on the script is available here
http://blogs.netapp.com/virtualization/2010/02/cleaning-up-vmware-snapshots.html
But you should log a support case for this.
Regards
Amrita
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dale,
I had something simular. In my case we did had uninstalled and installed SMVI again. Next morning we had trouble with the snapshots. There was a problem with renaming the snapshot to most recent because it already existed. Apparently the SMVI did not recognise the previous install had already made snapshots. Maybe this KB article from the Now website can help.
https://kb.netapp.com/support/index?page=content&id=2014553
I must say, I was glad I had my engineer from the reseller at hand.
I hope this helps you.
Regards,
Dirk-Pieter
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could you please log a support case with all the logs as well for this. NGS can get to the root cause of the issue and help you get this fixed. We even have a script for orphaned snapshots More information on the script is available here
http://blogs.netapp.com/virtualization/2010/02/cleaning-up-vmware-snapshots.html
But you should log a support case for this.
Regards
Amrita