1.  You need Pool Free Space equal to the volume size to accomplish this type of restore with ASM/ME.  Check your volume reserve, this is the amount of space allocated to the volume from free pool space, without thin provisioning volume reserve is the same as reported size. 2. The restore will require the size of the base volume and the snapshot.  This is the full size of the volume you are restoring. 3. The group manager will display the volume space used is a “High water” mark, and not an indication of the exact data usage as displayed in the OS.  We have a solution that discusses this in greater detail on the support site.  Go to this link: [URL] (support login required), and then search the Knowledge Base for: “GUI space usage differs from what the OS shows”  (to get to the KB, go to Resources> KnowledgeBase) You may also want to review the KB titled: “Member Free Space Values are Different than Group and Pool Free Space” If you feel you have enough free pool space and still can't restore the selected database, I would suggest that you open a support case so that they can look at the specifics of your environment. Regards, Joe
Hi, I was wondering if anyone encountered this problem and what their resolution is.  I have created a Smart Snapshot on my backup server (to test this out) and I am trying to do a "in-place restore" (where I can apply additional differential/transaction logs restores), but the option to Restore Selected Databases is grayed out.  It says "Restore selected databases (Disabled: Inadequate free space to create clones for restore)". When I click on the database in Auto-Snapshot Manager (Applications -> SqlServerWriter -> TestDB), there is a Free Pool Space Warning that says: "Volume 'E:\ (SAN-A)' cannot be cloned due to insufficient Free Space on PS Series Group 'SAN' [2.97 TB required / 2.06 TB available]'." My questions are: Thank you for your help!
Auto-Snapshot Manager - Restore Selected Databases Grayed Out