![]() However, in the newer version of ONTAP, it does not give where to place the LAN in the volume. "It would be better if they just improved the performance of the system." "It used to give us the volume where LANs should be placed when we created a LAN in the older version. ![]() Sometimes, that can be what makes or breaks our case." Things happen really rapidly, when they happen, and being able to say, "Yeah, we can get this up and running in a day, if you want," or even less time in some cases. When you are running a business, where time is a factor, that is the biggest selling point. Its configuration and flexibility are also good." "Technical support is good." "It impacts customer retention because of its overall ease. That includes the SAN national cloud." "It has a good interface. VMware workloads, the database, and Oracle Solaris are hosted on AFF, which means that our primary priority workloads are on AFF and that the secondary ones are on FAS. If you were to compare one of those products to NetApp, head to head from a feature perspective, NetApp would wind up in the top 10." "Technical support has been okay." "This solution helps accelerate demanding enterprise applications. In fact, frankly, they do have an advantage in that regard, however, they don't have the functionality. It is not impossible, but when you are accustomed to the older version of ONTAP, it just takes a bit getting used to it, but it is about the same as before." "Other manufacturers claim simplicity. The efficiency is very important because we can buy fewer disks for more data." "The newest version of ONTAP has a bit of a learning curve because you need to learn where things are to find them. Please see: "The most valuable features are the performance and the storage efficiency, due to the compression and deduplication. This will then allow ESX to tell ONTAP which deleted blocks can be recovered from the storage, hopefully to help avoid this situation again. Then delete the old LUN to release the blocks.ĭepending upon your version of ESX (VMware ESX 5.0 and later is supported), when you create the new LUN ensure the space_alloc option is enabled (disabled by default). This could be down to either storage efficiencies that ESX does not understand so cant also report the savings, or deleted blocks in the ESX filesystem that the storage cannot map - so does not delete and just sits there.Īssuming you have space capacity in the aggregate, the easiest thing is to create a new LUN/datastore and Storage vMotion the contents of the full LUN into that one. It sounds like ESX is reporting the LUN full but there is actually free space. It is also good practice to regularly run (out of hours) SnapDrive Space Reclaimer (only supported on physical RDMs) or enable the space_alloc feature on the LUN to release those deleted blocks. You do not need to worry about the LUN itself being 100% full. You will need to increase the size of the RDM LUN on the storage and make that available to the Windows server to expand the file system.Īgain, just to point out that since you've thin provisioned both the volume and LUN, you only need to monitor the space of the volume (and aggregate) as well as the file system. ![]() The space savings for block based (SAN) storage is on the storage, unlike file based (NAS) storage that passes those savings to the clients. To realise storage efficiency savings directly on the hosts you will need to use NFS datastores. In your thin provisioned environment (both LUN and volume), the storage efficiency savings are at the storage layer only and release blocks back to the aggregate to allow you to create additional volumes/LUNs. Hi Rene, in short.the guest will not see any of the storage efficiency savings you can't claim that space back for the file system to use.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |