I'm not sure if you mentioned what kinds of VMs they are... In my experience with VMware VMs, once you run out of diskspace, say, because you've got snapshots that have soaked up the rest of your datastores, then you'll need to call VMware as well. It's not as simple as moving the VMs to another LUN, because VMware won't let you if the VM has already run out of space. Especially older versions of VMware, where the simple presence of a snapshot prevents a storage vmotion. And snapshots can't simply be deleted using the vSphere client, because there's not enough space to process the snapshot deletion. Something to be mindful anyway, in case you're on VMware.
Mike On Thu, Sep 19, 2013 at 4:48 PM, Evan Pettrey <[email protected]> wrote: > Thanks for this excellent advice John and everybody else that chimed in. > > I've gone ahead and purchased a One Time Support agreement with NetApp for > $2,000 so now it's just a matter of working my way through all the various > levels of support they can throw at me. > > > You guys (and gals) are great, thanks again. > > > On Thu, Sep 19, 2013 at 4:16 PM, John Stoffel <[email protected]> wrote: > >> >> Evan> We're experiencing an issue with a NetApp SAN that I've recently >> Evan> inherited (on Monday) as a responsibility and which I'm lacking >> Evan> a depth of knowledge with. >> >> Ouch! Netapps can work with SAN LUNs, but it can be tricky and they >> are NOT space efficient, esp if you do snapshots. >> >> Evan> The previous sys admin thin provisioned everything and now >> Evan> everything has overgrown and VMs running on certain LUNs are >> Evan> fully down due to there not being enough storage available. >> >> Care to share some data on your system? You can use my attached perl >> script to get a nicely formatted overview of your aggregates and >> volumes. Doesn't know about LUNs or snapshots, but if people ask >> nicely... I could add that info. >> >> Evan> Can anybody recommend an expert to help with this as we do not >> Evan> have a support contract in place? Obviously this will be at a >> Evan> cost - that is acceptable. >> >> First off, get an overview of where your problem is. If you do a 'lun >> show -v' on the filer, does it show that some or all of the luns are >> offline? >> >> Next, look at the volumes. I life 'df -h' (again, directly on the >> filer) since it shows both volume and snapshot space. With LUNs, you >> generally need to reserve 120% of the disk space of the lun for >> snapshots. This is where Netapp falls down IMO, since luns are just a >> large single file to the Netapp. If a block changes, the entire >> file/lun needs to be copied to the snapshot area. Further changes are >> on a per-block level though, which helps. >> >> >> >> > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > >
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
