toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

Operations Manager 3.7 (DMF) and reporting
by steve klise 17 Jan '09

17 Jan '09

1st off, who decided to change the name of DFM to OM? Microsoft already had operations manager, now SCOM. I always have to say, OM, formally DFM.. ok, done ranting. I need to report on metrics for our storage, and I am still trying to get the requirements (half the battle). I have been playing with extracting the data from the OM ASA database, and trying to get it into crystal reports to make it look "dashboard'ish" to no avail. I just see numbers, and no aggregate names, vol names, etc. We currently use Sharepoint 2003, DFM 3.7, all windows servers with CIFS shares. I would like to have some sort of automated extract from OM and push into our sharepoint site for my storage metrics. I called Netapp support (which is REALLY good btw), but I was given the "you have to work with PS" shoulder. Has anyone done this? What are people using? Suggestions? -- View this message in context: http://www.nabble.com/Operations-Manager-3.7-%28DMF%29-and-reporting-tp2150… Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

4 4

Re: lun serial question
by Romeo Theriault 16 Jan '09

16 Jan '09

Thanks for the reply and clarification on the FC path misconfiguration errors". I understand that the error is caused by the client using the secondary path that goes through the cluster partners head, but I just can't figure out why and how to stop it. Here is why: The DMP (veritas vxdmp) is setup with two paths, one primary and another secondary and is vxdmp policy set to to use round-robin, so you would think that the partner path issue would be happening all the time on all luns, but it's not. It is only happening on a handful of them and only on some of the servers and all the Solaris servers have the same vxdmp configs. The other really bizarre thing is that I tried changing the DMP to use single-active during a maintenance window and about half of the luns would not even mount. (diskgroups went offline and disabled). So I had to set the dmp policy back to round-robin to even get them to mount again. So at this point I'm kinda thinking that the version of VXVM I'm running has some bugs in it that would hopefully be fixed by a newer version. I'm just running out of ideas and Netapp support has been of very little help at all. Thanks for the link and tips on udev, lun serials too. Romeo On Thu, Jan 15, 2009 at 1:59 PM, <jemans(a)xs4all.nl> wrote: > > Hi, > > Regarding "FC path misconfigured errors": > > Both your cluster filers present their own luns but also their partner > luns on each FC port, this means your clients will see double the amount > of paths for each LUN. To prevent the error from occurring you should make > sure all clients *ONLY* go through paths that are local to a filer. > > Example: > filer1 > LunA > LunB > > filer2 > LunC > LunD > > Client X sees LunA and LunC through both filers. LunA should *ONLY* be > accessed through filer1 although it is also available through filer1. The > reverse is true for LunC. You should configure this on the client not on > the filer. > > Changing your config to a supported one will not by itself do anything, > except that maybe NetApp will then help you fix it. > > As to the other issue on linux and seeing serial numbers, investigate > "udev" and "udevinfo": > http://www.reactivated.net/writing_udev_rules.html > > Also checkout the sysfs file system you can use this to figure out which > device has which serial. > > You can write rules to create file devices like: > /dev/scsi/lun-serialX > > That way the path is always unique for that LUN. You can then fdisk > /dev/scsi/lun-serialX or whatever. > > Regards, > > Johan > -- Romeo Theriault System Administrator

2 1

RE: SMVI - Limitations?
by Glenn Walker 15 Jan '09

15 Jan '09

Well, crap: "Users can't clone a file or a LUN that exists only in a Snapshot. The file or LUN must exist in the active file system." So much for 'recovery'... this is great for deployment, however. Wonder if there is a caveat that the file must be cloned to the same flexvol. I _know_ it will mean same aggregate (which kills our deployment from templates already). Bummer... -----Original Message----- From: Matt Hallmark [mailto:matt@cosmictoaster.com] Sent: Thursday, January 15, 2009 11:15 AM To: Darren Sykes Cc: Glenn Walker; Fox, Adam; Kumar, Rahul; Sto Rage(c); toasters(a)mathworks.com Subject: Re: SMVI - Limitations? http://blog.scottlowe.org/2008/12/03/2031-enhancements-to-netapp-cloning -technology/ Looks like it's single-file flex clone, w/o having to have a snap behind the clone. I'd thought that I'd seen mention of it on NetApp's Storage Nuts 'n Bolts Blog as well, but I didn't find it again in a few minutes of searching. We'll see once 7.3.1 is out, which is "Real Soon Now" according to my sources. :) Matt On Jan 15, 2009, at 12:50 AM, Darren Sykes wrote: > I thought individual file cloning was not a feature which Netapp had > publically announced (so tried to avoid mentioning it!). Maybe I'm > behind > the times.... > > > > On 15/01/2009 05:27, "Glenn Walker" <ggwalker(a)mindspring.com> wrote: > >> Single File Snap Restore (especially with ASIS) is a bit slow >> \painful. >> 7.3.1 code (maybe even 7.3) is supposed to make File Cloning a >> reality, >> much like you can do with LUNs today - this should help a great deal. >> >> Because of the slow SFSR, we've been using CP from the ESX CLI to get >> the data back out of snapshots - unfortunately, this means that the >> VMDKs are thick again and will have to be deduped during the next >> run. >> >> I should probably preface the above with the fact we're running >> VMWare >> storage over NFS. If you were using LUNs, you'd be using the LUN >> Clone\Split functionality to recover data which is blazing fast - >> but it >> also means you're recovering an entire LUN and everything within it >> (similar to Snap Restore at the volume level)... NFS allows us to >> recover single VMDKs, but we're suffering a bit due to the newness of >> the solution set. >> >> Looking forward to the improved functionality - there's no way I'd >> ever >> consider ESX over anything other than NFS! >> >> Glenn >> >> -----Original Message----- >> From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com >> ] >> On Behalf Of Fox, Adam >> Sent: Wednesday, January 14, 2009 12:37 PM >> To: Kumar, Rahul; Sto Rage(c) ; toasters(a)mathworks.com; >> Darren.Sykes(a)csr.com >> Subject: RE: SMVI - Limitations? >> >> I have to admit, I am not an SMVI expert, but I do know a thing or >> three >> about WAFL so I was speaking specifically about how snapshots and >> SnapRestore work at the ONTAP/WAFL level. >> >> As far as dedup (SIS), I'm not sure if I understand how/if it would >> "interfere" with a SnapRestore. >> In the case of a volume-level SnapRestore, the volume reverts back to >> the way it looked at the time of the snapshot used for the >> SnapRestore, >> and dedup would be no different there since the block pointers as >> well >> as the fingerprint file would be a part of the SnapRestore. I've >> actually never tried to figure out how it would work with a single- >> file >> SnapRestore. The good news is that with the release of the 7.3 >> simulator, which supports dedup, anyone can try it in their lab >> without >> touching their production stuff (on a smaller scale, of course). At >> most, you might have to re-run a full scan, but I'm honestly not >> sure. >> >> -- Adam Fox >> Systems Engineer >> adamfox(a)netapp.com >> >> >> -----Original Message----- >> From: Kumar, Rahul [mailto:kumarrahul@siemens.com] >> Sent: Wednesday, January 14, 2009 12:09 PM >> To: Fox, Adam; Sto Rage(c) ; toasters(a)mathworks.com; >> Darren.Sykes(a)csr.com >> Subject: RE: SMVI - Limitations? >> >> Adam >> >> So in theory, the snaprestore via smvi does actually do an individual >> file restores (talking about the a single vm restore) though there >> may >> be 100 of vms on the volume. >> >> So that does mean that we need to dedicate/separate volumes >> according to >> the usage etc. >> Also does SIS interfere when vm snaprestores are done by any chance ? >> >> Thanks for making the issue clear.. I am not in grip of the >> scenario and >> possible workarounds or new processes to b e followed >> >> Rahul >> >> -----Original Message----- >> From: Fox, Adam [mailto:Adam.Fox@netapp.com] >> Sent: Wednesday, January 14, 2009 9:51 PM >> To: Kumar, Rahul; Sto Rage(c) ; toasters(a)mathworks.com; >> Darren.Sykes(a)csr.com >> Subject: RE: SMVI - Limitations? >> >> WAFL Snapshots are always at the volume level. If you use the snap >> restore software on the controller, you can restore either the entire >> volume or an individual file level. >> >> Hope this helps. >> >> -- Adam Fox >> Systems Engineer >> adamfox(a)netapp.com >> >> -----Original Message----- >> From: Kumar, Rahul [mailto:kumarrahul@siemens.com] >> Sent: Wednesday, January 14, 2009 5:07 AM >> To: Sto Rage(c) ; toasters(a)mathworks.com; Darren.Sykes(a)csr.com; Fox, >> Adam >> Subject: RE: SMVI - Limitations? >> >> Hi Toasters >> >> A general scene and a question related to it. >> >> We have over 5TB of NFS datastore spread across various qtrees. >> >> We were evaluating SMVI and came to know that it also requires >> snaprestore to restore the VM's >> >> Now my question is that if e.g there was a qtree with say 50 vms on >> it >> and we'd like to snapshot only a few of them. Will this work ? >> >> When a snap is created on the filer it will capture all the VM's thus >> eating up valuable disk space from the snapreserve as time goes by. >> >> Next when we do a restore of the individual machine, it does a snap >> restore, however I am not sure if this only restores the individual >> machine or the entire stuff >> >> Any insight/help into this will be helpful >> >> >> Thanks >> Rahul >> >> >> >> >> >> -----Original Message----- >> From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com >> ] >> On Behalf Of Sto Rage(c) >> Sent: Saturday, January 10, 2009 4:52 AM >> To: toasters(a)mathworks.com >> Subject: Re: SMVI - Limitations? >> >> On Fri, Jan 9, 2009 at 12:19 AM, Darren Sykes <Darren.Sykes(a)csr.com> >> wrote: >>> You can tell SMVI (v1.1) not to perform OS level disk quiecing on >> those >>> machines if that's any use to you? >>> You'll then get a completely transparent Netapp level snapshot and >> won't >>> interfere with the VM itself. >>> >>> Darren >> It is SMVI v1.01 BTW, not 1.1 >> Not sure I understand this correctly, but if you are bypassing OS >> disk quiesce (VMWare snapshot) and doing transparent NetApp level >> snapshot, then why do you even need SMVI installed? Can't we just do >> the regular filer level snap schedule? We just upgraded to 1.01 and >> noticed the checkbox and were wondering about its potential use. Any >> ideas? >> >> thanks >> -G >> >> >> >> To report this email as spam click >> https://www.mailcontrol.com/sr/ug0PLQWh+NDTndxI!oX7Us7PAc+Gwoki+tHufSOOi ve2d!w >> jVlrCgJRg5dmIWyzIG+CHg+eM4kfwq3xXRfv08Q== . >

2 1

Re: lun serial question
by Romeo Theriault 15 Jan '09

15 Jan '09

Great! This is exactly what I was looking for. Thanks, should be fairly easy to script too. On Thu, Jan 15, 2009 at 1:02 PM, Dalvenjah FoxFire <dalvenjah(a)dal.net>wrote: > Yup, you can -- the command is scsi_id from the udev packages. Note that > you have to have sysfs (/sys) mounted and active for this to work. > Determine the Linux block device name (e.g. /dev/sdc), then replace /dev/ > with /block/ and pass it to scsi_id: > /sbin/scsi_id -g -u -s /block/sdc360a.... > It's what the dm-multipath software uses to determine which devices are the > same LUN. > -dalvenjah > > On Jan 15, 2009, at 8:27 AM, Romeo Theriault wrote: > > Thanks for the reply. We're a unix shop so I don't have to worry about > windows. I was aware that I can get this kind of information from the Host > Utilities but was wondering if there was a way to get the info without > installing Host Utilities. I'd be mainly interested in Linux. > > Thanks for the help. > > Romeo > > On Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > >> There are tools in the NetApp Host Utilities that already do this very >> thing. It is recommended (and on some platforms it's mandatory) that you use >> this method to connect your systems to the NetApp SAN. >> >> On unix systems, a popular command that I use is: >> >> sanlun lun show -p >> >> Unfortunately, I am not as verse on Windows systems, but I expect >> something similar (if not the same). Good luck. >> >> Cheers, >> >> >> >> Stetson M. Webster >> Professional Services Engineer >> NCIE-SAN, NCIE-B&R, SNIA-SCSE >> NetApp Global Services - Southeast District >> >> 919.250.0052 Mobile >> Stetson.Webster(a)netapp.com >> >> Learn how: netapp.com/guarantee >> >> ------------------------------ >> *From*: Romeo Theriault >> *To*: toasters(a)mathworks.com >> *Sent*: Thu Jan 15 09:49:19 2009 >> *Subject*: lun serial question >> I recently became aware of the lun serial command and am wondering if >> there is anyway for a client that has said lun or luns presented to them to >> "see" this lun serial string. I'm thinking this would be an ideal way (i.e. >> script) to find out which lun corresponds to which filesystem/mountpoint on >> servers with lots of luns. >> >> Thanks, >> -- >> Romeo Theriault >> System Administrator >> Information Technology Services >> > > > > -- > Romeo Theriault > System Administrator > Information Technology Services > > > -- Romeo Theriault System Administrator Information Technology Services

1 0

Re: lun serial question
by Romeo Theriault 15 Jan '09

15 Jan '09

> > /opt/NetApp/santools/bin/ntap_config_paths ## the path on Solaris may be > different This file didn't seem to come with my Solaris Host Utilities. Poking around on netapp site I can only seem to find reference to it in regards to HP-UX. But I'll poke around a bit more. Thanks, Romeo On Thu, Jan 15, 2009 at 12:21 PM, Jeff Cleverley < jeff.cleverley(a)avagotech.com> wrote: > Romeo, > > The partner mismatch doesn't deal with the serial numbers as you mention. > It is telling you that the file systems are accessing the luns through the > incorrect path. I get this a lot on my hpux system which use pvlinks for > failover. All I have to do is run: > > /opt/NetApp/santools/bin/ntap_config_paths ## the path on Solaris may be > different > > and it re-orders the disks in the volume group using vgreduce/vgextend > commands. I wouldn't think this would require a VX* upgrade on anything. > > Jeff > > > Romeo Theriault wrote: > > Are you getting "FC Partner Path Misconfigured" errors from any of your >> NetApp SAN systems? >> > > Yes, actually! But this is another ball of wax. The machines that are > getting these errors have the Host Utilities installed. (Solaris 9). I've > been working with Netapp Support on this and what it comes down to is that > we are in an unsupported configuration. (Veritas VXVM, Veritas VXFS, but > using the Sun HBA drivers, which we have to due to the cards being Sun > branded cards.) To get to a supported configuration (and hopefully get rid > of these errors) I need to upgrade our VXVM to 5.0 and then upgrade the > Host Utilities to a version that supports our config. Oh, what fun. > > But..... The linux boxes I'd be interested in using such a script that I > initially asked about are using single pathed iscsi and are not causing any > errors. I'd just like a way to map this info without having to install Host > Utilities. > > Romeo > > > > On Thu, Jan 15, 2009 at 11:31 AM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > >> Are you getting "FC Partner Path Misconfigured" errors from any of your >> NetApp SAN systems? If so, you may want to reconsider your decision. The >> documentation and tools in the Host Utilities will resolve this. >> >> >> >> *Stetson M. Webster** >> *Professional Services Engineer >> NCIE-SAN, NCIE-B&R, SNIA-SCSE >> NetApp Global Services - Southeast District >> >> 919.250.0052 Mobile >> Stetson.Webster(a)netapp.com >> >> Learn how: netapp.com/guarantee >> >> >> >> [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> >> >> >> >> >> *From:* Romeo Theriault [mailto:romeotheriault@gmail.com] >> *Sent:* Thursday, January 15, 2009 11:27 AM >> *To:* Webster, Stetson; toasters(a)mathworks.com >> *Subject:* Re: lun serial question >> >> >> >> Thanks for the reply. We're a unix shop so I don't have to worry about >> windows. I was aware that I can get this kind of information from the Host >> Utilities but was wondering if there was a way to get the info without >> installing Host Utilities. I'd be mainly interested in Linux. >> >> >> Thanks for the help. >> >> Romeo >> >> On Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson < >> Stetson.Webster(a)netapp.com> wrote: >> >> There are tools in the NetApp Host Utilities that already do this very >> thing. It is recommended (and on some platforms it's mandatory) that you use >> this method to connect your systems to the NetApp SAN. >> >> On unix systems, a popular command that I use is: >> >> sanlun lun show -p >> >> Unfortunately, I am not as verse on Windows systems, but I expect >> something similar (if not the same). Good luck. >> >> Cheers, >> >> >> >> Stetson M. Webster >> Professional Services Engineer >> NCIE-SAN, NCIE-B&R, SNIA-SCSE >> NetApp Global Services - Southeast District >> >> 919.250.0052 Mobile >> Stetson.Webster(a)netapp.com >> >> Learn how: netapp.com/guarantee >> ------------------------------ >> >> *From*: Romeo Theriault >> *To*: toasters(a)mathworks.com >> *Sent*: Thu Jan 15 09:49:19 2009 >> *Subject*: lun serial question >> >> I recently became aware of the lun serial command and am wondering if >> there is anyway for a client that has said lun or luns presented to them to >> "see" this lun serial string. I'm thinking this would be an ideal way (i.e. >> script) to find out which lun corresponds to which filesystem/mountpoint on >> servers with lots of luns. >> >> Thanks, >> -- >> Romeo Theriault >> System Administrator >> Information Technology Services >> >> >> >> >> -- >> Romeo Theriault >> System Administrator >> Information Technology Services >> > > > > -- > Romeo Theriault > System Administrator > Information Technology Services > > > -- > > Jeff Cleverley > Unix Systems Administrator > 4380 Ziegler Road > Fort Collins, Colorado 80525 > 970-288-4611jeff.cleverley(a)avagotech.com > > -- Romeo Theriault System Administrator Information Technology Services

1 0

Re: lun serial question
by Romeo Theriault 15 Jan '09

15 Jan '09

> > Are you getting "FC Partner Path Misconfigured" errors from any of your > NetApp SAN systems? > Yes, actually! But this is another ball of wax. The machines that are getting these errors have the Host Utilities installed. (Solaris 9). I've been working with Netapp Support on this and what it comes down to is that we are in an unsupported configuration. (Veritas VXVM, Veritas VXFS, but using the Sun HBA drivers, which we have to due to the cards being Sun branded cards.) To get to a supported configuration (and hopefully get rid of these errors) I need to upgrade our VXVM to 5.0 and then upgrade the Host Utilities to a version that supports our config. Oh, what fun. But..... The linux boxes I'd be interested in using such a script that I initially asked about are using single pathed iscsi and are not causing any errors. I'd just like a way to map this info without having to install Host Utilities. Romeo On Thu, Jan 15, 2009 at 11:31 AM, Webster, Stetson < Stetson.Webster(a)netapp.com> wrote: > Are you getting "FC Partner Path Misconfigured" errors from any of your > NetApp SAN systems? If so, you may want to reconsider your decision. The > documentation and tools in the Host Utilities will resolve this. > > > > *Stetson M. Webster** > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Romeo Theriault [mailto:romeotheriault@gmail.com] > *Sent:* Thursday, January 15, 2009 11:27 AM > *To:* Webster, Stetson; toasters(a)mathworks.com > *Subject:* Re: lun serial question > > > > Thanks for the reply. We're a unix shop so I don't have to worry about > windows. I was aware that I can get this kind of information from the Host > Utilities but was wondering if there was a way to get the info without > installing Host Utilities. I'd be mainly interested in Linux. > > > Thanks for the help. > > Romeo > > On Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > > There are tools in the NetApp Host Utilities that already do this very > thing. It is recommended (and on some platforms it's mandatory) that you use > this method to connect your systems to the NetApp SAN. > > On unix systems, a popular command that I use is: > > sanlun lun show -p > > Unfortunately, I am not as verse on Windows systems, but I expect something > similar (if not the same). Good luck. > > Cheers, > > > > Stetson M. Webster > Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > ------------------------------ > > *From*: Romeo Theriault > *To*: toasters(a)mathworks.com > *Sent*: Thu Jan 15 09:49:19 2009 > *Subject*: lun serial question > > I recently became aware of the lun serial command and am wondering if there > is anyway for a client that has said lun or luns presented to them to "see" > this lun serial string. I'm thinking this would be an ideal way (i.e. > script) to find out which lun corresponds to which filesystem/mountpoint on > servers with lots of luns. > > Thanks, > -- > Romeo Theriault > System Administrator > Information Technology Services > > > > > -- > Romeo Theriault > System Administrator > Information Technology Services > -- Romeo Theriault System Administrator Information Technology Services

1 0

Re: lun serial question
by Webster, Stetson 15 Jan '09

15 Jan '09

There are tools in the NetApp Host Utilities that already do this very thing. It is recommended (and on some platforms it's mandatory) that you use this method to connect your systems to the NetApp SAN. On unix systems, a popular command that I use is: sanlun lun show -p Unfortunately, I am not as verse on Windows systems, but I expect something similar (if not the same). Good luck. Cheers, Stetson M. Webster Professional Services Engineer NCIE-SAN, NCIE-B&R, SNIA-SCSE NetApp Global Services - Southeast District 919.250.0052 Mobile Stetson.Webster(a)netapp.com Learn how: netapp.com/guarantee ________________________________ From: Romeo Theriault To: toasters(a)mathworks.com Sent: Thu Jan 15 09:49:19 2009 Subject: lun serial question I recently became aware of the lun serial command and am wondering if there is anyway for a client that has said lun or luns presented to them to "see" this lun serial string. I'm thinking this would be an ideal way (i.e. script) to find out which lun corresponds to which filesystem/mountpoint on servers with lots of luns. Thanks, -- Romeo Theriault System Administrator Information Technology Services

3 2

lun serial question
by Romeo Theriault 15 Jan '09

15 Jan '09

I recently became aware of the lun serial command and am wondering if there is anyway for a client that has said lun or luns presented to them to "see" this lun serial string. I'm thinking this would be an ideal way (i.e. script) to find out which lun corresponds to which filesystem/mountpoint on servers with lots of luns. Thanks, -- Romeo Theriault System Administrator Information Technology Services

2 1

AW: VSCAN messages
by Robert.Reber＠stadt.nuernberg.de 15 Jan '09

15 Jan '09

Yes, it´s 250419. The problem still appears (currently using ONTAP 7.2.5.1) though. -----Ursprüngliche Nachricht----- Von: Eugene Vilensky [mailto:evilensky@gmail.com] Gesendet: Mittwoch, 14. Januar 2009 15:23 An: Reber, Robert Cc: toasters(a)mathworks.com Betreff: Re: VSCAN messages On Wed, Jan 14, 2009 at 2:05 AM, <Robert.Reber(a)stadt.nuernberg.de> wrote: > Yes, this is a known problem which should have been fixed in 7.2.3 but > apparently isn´t - the workaround is Hi, Is there a bug ID on this?

2 1

RE: SMVI - Limitations?
by Fox, Adam 15 Jan '09

15 Jan '09

I have to admit, I am not an SMVI expert, but I do know a thing or three about WAFL so I was speaking specifically about how snapshots and SnapRestore work at the ONTAP/WAFL level. As far as dedup (SIS), I'm not sure if I understand how/if it would "interfere" with a SnapRestore. In the case of a volume-level SnapRestore, the volume reverts back to the way it looked at the time of the snapshot used for the SnapRestore, and dedup would be no different there since the block pointers as well as the fingerprint file would be a part of the SnapRestore. I've actually never tried to figure out how it would work with a single-file SnapRestore. The good news is that with the release of the 7.3 simulator, which supports dedup, anyone can try it in their lab without touching their production stuff (on a smaller scale, of course). At most, you might have to re-run a full scan, but I'm honestly not sure. -- Adam Fox Systems Engineer adamfox(a)netapp.com -----Original Message----- From: Kumar, Rahul [mailto:kumarrahul@siemens.com] Sent: Wednesday, January 14, 2009 12:09 PM To: Fox, Adam; Sto Rage(c) ; toasters(a)mathworks.com; Darren.Sykes(a)csr.com Subject: RE: SMVI - Limitations? Adam So in theory, the snaprestore via smvi does actually do an individual file restores (talking about the a single vm restore) though there may be 100 of vms on the volume. So that does mean that we need to dedicate/separate volumes according to the usage etc. Also does SIS interfere when vm snaprestores are done by any chance ? Thanks for making the issue clear.. I am not in grip of the scenario and possible workarounds or new processes to b e followed Rahul -----Original Message----- From: Fox, Adam [mailto:Adam.Fox@netapp.com] Sent: Wednesday, January 14, 2009 9:51 PM To: Kumar, Rahul; Sto Rage(c) ; toasters(a)mathworks.com; Darren.Sykes(a)csr.com Subject: RE: SMVI - Limitations? WAFL Snapshots are always at the volume level. If you use the snap restore software on the controller, you can restore either the entire volume or an individual file level. Hope this helps. -- Adam Fox Systems Engineer adamfox(a)netapp.com -----Original Message----- From: Kumar, Rahul [mailto:kumarrahul@siemens.com] Sent: Wednesday, January 14, 2009 5:07 AM To: Sto Rage(c) ; toasters(a)mathworks.com; Darren.Sykes(a)csr.com; Fox, Adam Subject: RE: SMVI - Limitations? Hi Toasters A general scene and a question related to it. We have over 5TB of NFS datastore spread across various qtrees. We were evaluating SMVI and came to know that it also requires snaprestore to restore the VM's Now my question is that if e.g there was a qtree with say 50 vms on it and we'd like to snapshot only a few of them. Will this work ? When a snap is created on the filer it will capture all the VM's thus eating up valuable disk space from the snapreserve as time goes by. Next when we do a restore of the individual machine, it does a snap restore, however I am not sure if this only restores the individual machine or the entire stuff Any insight/help into this will be helpful Thanks Rahul -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Sto Rage(c) Sent: Saturday, January 10, 2009 4:52 AM To: toasters(a)mathworks.com Subject: Re: SMVI - Limitations? On Fri, Jan 9, 2009 at 12:19 AM, Darren Sykes <Darren.Sykes(a)csr.com> wrote: > You can tell SMVI (v1.1) not to perform OS level disk quiecing on those > machines if that's any use to you? > You'll then get a completely transparent Netapp level snapshot and won't > interfere with the VM itself. > > Darren It is SMVI v1.01 BTW, not 1.1 Not sure I understand this correctly, but if you are bypassing OS disk quiesce (VMWare snapshot) and doing transparent NetApp level snapshot, then why do you even need SMVI installed? Can't we just do the regular filer level snap schedule? We just upgraded to 1.01 and noticed the checkbox and were wondering about its potential use. Any ideas? thanks -G

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters