Hello,   That's great news, thanks for the update.  re:1.  Group Manager based snapshots can only capture the data that's on the array storage already or in the cache of the storage.  Any pending writes on the host wouldn't be included.  When you use ASM/ME the Volume Shadow Service is called first.  This pauses I/O and flushes out cache, then a snapshot is created. Making it more consistent.  A GUI based snapshot is said to be "crash" consistent.  At least as consistent as would be if the server crashed or lost power.  Using ASM/ME it's said to be "application" consistent.  Also ASM/ME integrates with MS SQL, Exchange and SharePoint to provide more consistency and additional features.  I.e. recover a single Exchange Mailbox entirely via the ASM GUI.   Re: 2.  It sounds like there is a virtual disk on local storage not on the SAN.  So if host A has a piece of the VM and you move to host B.  Host B can't quiet the filesystem on Host A.    You probably want to open a support case for that.  So they can review the logs and take a look.   Regards, Don  
Hi, We have 2 volumes which are limited to keep a maximum of 2 snapshots, however these go up to 8 or 9 snapshots. We can see the 2 scheduled snapshots but also the other snapshots taken at various times throughout the day. The snapshot times do not match with the scheduled times in ASM on the hosts. The snapshot policy is not set to 'Borrow snapshot space as needed' and set to 'Delete oldest snapshot'. We have upgraded ASM on the hosts to Version 5.0.0.8828, and the storage array firmware to version 8.1.10 (R436828) hoping this would resolve the issue but it hasn't. Any help would be appreciated?  Kind Regards Rash
Too many snapshots generated