toasters

toasters@lists.teaparty.net

13531 discussions

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

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

14 Jan '09

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

1 0

panics with 7.2.6.1
by Peter D. Gray 14 Jan '09

14 Jan '09

Just reverted all our filers to 7.2.5.1 after we had 7 panics in one day on 7.2.6.1 (6 on a 270A and 1 on a 3170A) We had been on 7.2.6.1 for 2 days but today was the first work day. Looks like a problems in the quota handling. Mon Jan 12 14:48:38 EST [naga: sk.panic:ALERT]: replayed event: Panic String: ../common/wafl/quotas/quota.c:1684: Assertion failure. in process wafl_lopri on release NetApp Release 7.2.6.1 Mon Jan 12 14:48:38 EST [naga: sk.panic:ALERT]: replayed event: Panic String: ../common/wafl/quotas/quota.c:1684: Assertion failure. in process wafl_lopri on release NetApp Release 7.2.6.1 Mon Jan 12 15:03:59 EST [naga: mgr.stack.string:notice]: Panic string: ../common/wafl/quotas/quota.c:1684: Assertion failure. in process wafl_lopri on release NetApp Release 7.2.6.1 Mon Jan 12 15:03:59 EST [naga: mgr.stack.string:notice]: Panic string: ../common/wafl/quotas/quota.c:1684: Assertion failure. in process wafl_lopri on release NetApp Release 7.2.6.1 Mon Jan 12 15:03:59 EST [naga: mgr.stack.at:notice]: Panic occurred at: Mon Jan 12 14:48:38 2009 Mon Jan 12 15:03:59 EST [naga: mgr.stack.at:notice]: Panic occurred at: Mon Jan 12 14:48:38 2009 Mon Jan 12 15:03:59 EST [naga: mgr.stack.proc:notice]: Panic in process: wafl_lopri Mon Jan 12 15:03:59 EST [naga: mgr.stack.proc:notice]: Panic in process: wafl_lopri Mon Jan 12 15:03:59 EST [naga: mgr.stack.framename:notice]: Stack frame 0: sk_vpanic(0xd84ccc) + 0x0 Mon Jan 12 15:03:59 EST [naga: mgr.stack.framename:notice]: Stack frame 0: sk_vpanic(0xd84ccc) + 0x0 Anyone else seen this? Regards, pdg -- See mail headers for contact information.

5 8

RE: SMVI - Limitations?
by Darren Sykes 14 Jan '09

14 Jan '09

SMVI uses snapshot 'normal' snapshot functionality of the filer so the granularity is constrained by that. At the current time, you cannot snapshot a file of files within a volume/qtree so in your scenario, you'd consume more than the necessary amount of storage space in creating a snapshot. To get around that you could either: 1) Reorganise your Datastores (perhaps using Storage VMotion) so that VMs with common snapshot/backup requirements live on the same Datastore 2) Hope that Netapp release additional functionality in OnTAP (and corresponding features in SMVI) so that you can snapshot individual files. The only other thing to note is that SMVI does allow you select a subset of VM's on a datastore for backup. The effect this has is that SMVI doesn't waste time quiecing the VM's that you haven't included in the backup job. Darren -----Original Message----- From: Kumar, Rahul [mailto:kumarrahul@siemens.com] Sent: 14 January 2009 10:07 To: Sto Rage(c) ; toasters(a)mathworks.com; Darren Sykes; Adam.Fox(a)netapp.com 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/vp!1JnK84mHTndxI!oX7Ug+zP6wRoWawawux2rV25 mcJ4jEHfEKQsBBo5y31p0!L1slOaqyO5jedye7!a4hOmw== .

1 0

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

14 Jan '09

Yes, this is a known problem which should have been fixed in 7.2.3 but apparently isn´t - the workaround is priv set diag ; setflag smb_vscan_delay_close_resp 1 ; priv set;vscan off ; vscan on Try that - if it works, then put it in the /etc/rc of your filer(s) - works fine for us - I tried it without the workaround after the last few ONTAP-Updates since it should be fixed, but always had to put it back into /etc/rc... Greetz, Rob -----Ursprüngliche Nachricht----- Von: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com]Im Auftrag von JamieB Gesendet: Dienstag, 13. Januar 2009 23:57 An: toasters(a)mathworks.com Betreff: VSCAN messages NetApp FAS270 FAS3020 and FAS3140A DOT ver 7.2.3 McAfee Vscan for NetApp Filers v7.1 I am seeing a lot of the following messages in /etc/messages ERROR: [vscan.virus.detected:error]: CIFS: Virus Detected - <file path> in share [Share name not available] accessed by client **unknown** (**unknown**) running as user **unknown** is infected. The filer received status message Error 5 ...Continuing and error code [5] from vscan (anti-virus) server **unknown**. The service account of the Vscan application is in the local admin group of the filer. NetApp has recommended upgrading to DOT 7.3 but I am somewhat hesitant since all of filers are using quotas and usermap.cfgs - have seen a few emails concerning "panic" problems. Has anyone else seen similar results with their Vscan application on the filers? Regards,

1 0

VSCAN messages
by JamieB 13 Jan '09

13 Jan '09

NetApp FAS270 FAS3020 and FAS3140A DOT ver 7.2.3 McAfee Vscan for NetApp Filers v7.1 I am seeing a lot of the following messages in /etc/messages ERROR: [vscan.virus.detected:error]: CIFS: Virus Detected - <file path> in share [Share name not available] accessed by client **unknown** (**unknown**) running as user **unknown** is infected. The filer received status message Error 5 ...Continuing and error code [5] from vscan (anti-virus) server **unknown**. The service account of the Vscan application is in the local admin group of the filer. NetApp has recommended upgrading to DOT 7.3 but I am somewhat hesitant since all of filers are using quotas and usermap.cfgs - have seen a few emails concerning "panic" problems. Has anyone else seen similar results with their Vscan application on the filers? Regards,

1 0

changing/setting flow control
by George Kahler 13 Jan '09

13 Jan '09

Hi guys, I would like to change/set one of the NICs on a FAS3040 to enable flow control after my Network Operations guys turn-on flow control on their switch port. Can I just "filer> ifconfig e0a flowcontrol full" while the filer is serving data or do I need to 'down/up' the interface ? The protocols on the filer is all nfs and some iSCSI. Thanks, George

7 8

Snapmanager for Virtual Infrastructure, RDM to VMFS/NFS Migrations...
by Ken Williams 12 Jan '09

12 Jan '09

Has anyone migrated from RDM to a standard VMFS or NFS Datastore? I was hoping Svmotion would handle the move without powering down the virtual machine but it looks like that may not be supported. I'd like to accomplish this without outages (or extremely limited downtime for the hosts), any ideas? __________________________________________________________ Ken Williams Storage Administrator, Business Technology Operations Sacramento Municipal Utility District E-Mail: kwillia(a)smud.org Phone: (916) 732-6744 Cell: (916) 240-4213

5 9

RE: SMVI - Limitations?
by Ken Williams 09 Jan '09

09 Jan '09

Our databases are on RDMs, actually all our VMs are on RDMs. I'm working on migrating to NFS/IP storage and SMVI is part of that design. -----Original Message----- From: Matt Hallmark [mailto:matt@cosmictoaster.com] Sent: Thursday, January 08, 2009 4:00 PM To: Ken Williams Cc: Bill Holland; toasters(a)mathworks.com Subject: Re: SMVI - Limitations? Are your databases on VMDK's, RDM's or are you using an iscsi initiator in the VM? Thx, Matt On Jan 8, 2009, at 3:50 PM, Ken Williams wrote: > In our environment if we perform a VMWare snapshot of a SQL or Oracle > database it will crash. So we've actually set policy so those do not > get snapshots. > > From: Bill Holland [mailto:hollandwl@gmail.com] > Sent: Thursday, January 08, 2009 3:43 PM > To: Ken Williams; toasters(a)mathworks.com > Subject: Re: SMVI - Limitations? > > I've been experimenting with SMVI some and it appears to work hand- > in-hand with vCenter. Essentially, it takes a VMware snapshot, > followed by a filer snapshot (and snapmirror update if you tell it > to), then deletes the VMware snapshot. The VMware snapshot before the > filer snapshot ensures the volumes are quiesced and buffers flushed > before the filer snapshot to ensure consistency. > > I think you'll still have to place your databases in hot backup mode > before taking a snapshot. > > Currently our Oracle and SQL data, index, redo, and archives exist on > iSCSI LUNs with SnapDrive for Windows. As we progress with VMware, we > will likely place our OS and Applications either on NFS volumes or > VMFS formatted iSCSI LUNs. We will then continue to use SnapDrive for > Windows to manage our database LUNs as this is something we are > familiar with and are very comfortable with our current recovery model > in regards to the databases themselves. Plus we often wish to take > snaphots on them several times a day during our production cycles. > Simply go into hot backup mode, take snapshot of all but archive > volumes, exit hot backup mode, snapshot archive volume. It happens so > quickly our users never notice it and we have recovery points at key > times during our production cycle should something go wrong during one > of the daily operations. This is for Oracle. Our SQL databases are > small and not mission critical so simply taking a filer snapshot and > letting SQL do its crash recovery if we restore a snapshot works fine. > ----- Original Message ----- > From: Ken Williams > To: toasters(a)mathworks.com > Sent: Thursday, January 08, 2009 2:41 PM > Subject: SMVI - Limitations? > > We're making the plunge to move to NFS and SMVI (from RDM backed luns > and homegrown snapshot management scripts). > > Does anyone know of any limitation to how many VMs can exist in a data > store that SMVI is snapping? Is there any impact when snapping virtual > machines (outside of SQL/Oracle VMs)? > > __________________________________________________________ > Ken Williams > Storage Administrator, Business Technology Operations Sacramento > Municipal Utility District > E-Mail: kwillia(a)smud.org > Phone: (916) 732-6744 > Cell: (916) 240-4213 >

1 0

RE: RE-export volume/qtree question
by Kevin M. Parker 08 Jan '09

08 Jan '09

Resend, sorry. Hey Folks, I've a volume export entry that look like such /vol/volume -sec=sys,rw, root=xyz The client mounts it at the qtree like such Filer:/vol/volume/qtree I need to re-export this at the qtree level such that client do NOT have the ability to write into the volume, only the qtree, so new/proposed export entry will look like /vol/volume/qtree sec=sys,rw,root=xyz Since clients already mount at qtree level, can't I just re-export at the qtree, remove the volume export and exportfs? Will this be any impact, or change to FSID? Cheers, Best regards, -/- Kevin Parker 919.521.8413 http://theparkerz.com <http://theparkerz.com/> Blackle.com <http://www.blackle.com/> - Saving energy one search at a time.

2 1

fakeroot on a mixed qtree not working properly.
by Page, Jeremy 06 Jan '09

06 Jan '09

The info below was sent to me by one of our engineers. I also tried switching the qtree to UNIX instead of mixed but it gives me an error "qtree update: qtree security style update: qtree: There are shares with connections on qtree" Any suggestions? Below is an example of fakeroot not working properly. First I present what should happen (this is on a local machine not using my network drive) kuebert@gsows-eng138:~/tmp$ mkdir foo kuebert@gsows-eng138:~/tmp$ ls -l total 4 drwxr-xr-x 2 kuebert kuebert 4096 2009-01-05 15:52 foo/ kuebert@gsows-eng138:~/tmp$ fakeroot chown root:root foo kuebert@gsows-eng138:~/tmp$ ls -l total 4 drwxr-xr-x 2 kuebert kuebert 4096 2009-01-05 15:52 foo/ kuebert@gsows-eng138:~/tmp$ touch foo/bar kuebert@gsows-eng138:~/tmp$ ls -l foo total 0 -rw-r--r-- 1 kuebert kuebert 0 2009-01-05 15:52 bar kuebert@gsows-eng138:~/tmp$ fakeroot chown root:root foo/bar kuebert@gsows-eng138:~/tmp$ ls -l foo total 0 -rw-r--r-- 1 kuebert kuebert 0 2009-01-05 15:52 bar kuebert@gsows-eng138:~/tmp$ rm -rf foo kuebert@gsows-eng138:~/tmp$ This is what happens on my network home drive (I did this on gsovm-psbs03): kuebert@gsovm-psbs01:~/tmp2$ mkdir foo kuebert@gsovm-psbs01:~/tmp2$ ls -l total 4 drwxr-xr-x 2 kuebert cvs 4096 2009-01-05 15:51 foo/ kuebert@gsovm-psbs01:~/tmp2$ fakeroot chown root:root foo kuebert@gsovm-psbs01:~/tmp2$ ls -l total 4 drwxr-xr-x 2 root root 4096 2009-01-05 15:51 foo/ kuebert@gsovm-psbs01:~/tmp2$ touch foo/bar touch: cannot touch `foo/bar': Permission denied kuebert@gsovm-psbs01:~/tmp2$ rm -rf foo kuebert@gsovm-psbs01:~/tmp2$ So basically what I think is happening is in the second case my fakeroot command is actually changing the file on the filesystem, at least from Linux's perspective, even though it's not supposed to. When I go to touch the file in the foo directory it won't let me because it thinks the directory is owned by root:root which it is not. Due to a problem like this I can't build deb packages without being root which is kind of a big deal (the dir permissions get hosed up and then the package creation fails). Jeremy M. Page________________ Systems Architect Gilbarco Veeder-Root, a Danaher Company 7300 West Friendly Avenue Greensboro, NC 22087 * email:Jeremy.Page@gilbarco.com - * phone: 336.547.5399 - 6 fax: 336.547.5163 - * cell: 336.601.7274 Open a Helpdesk Ticket <http://heat.gilbarco.com/heatselfservice/simple/en-us/> View the IT Wiki <http://gsovmwiki01.gilbarco.com/mediawiki/index.php/Main_Page> Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance. In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.

2 1

Upgarding filer head with LUNs and MSCS
by Borzenkov, Andrey 05 Jan '09

05 Jan '09

Hi, We are going to upgrade several filers (FAS270 -> FAS3140). They host FCP LUNs and Windows with MSCS connected. Now what I have been told: - MSCS records disks (LUNs) serial numbers; when these serial numbers change, MSCS won't detect and configure its disks. Basically, cluster has to be recreated from scratch - LUN serial number on filer depends on sysid; when sysid changes, LUN serial number will change - as during head upgrade sysid will change so will serial numbers; so MSCS will be very unhappy. Is the above correct? Now we'd rather avoid recreating all MSCS configuration. Are there any pitfalls if we save original serial numbers and set them again on new head before MSCS will go online? Will this work or some more tuning is necessary? Thank you! С уважением / With best regards / Mit freundlichen Grüβen --- Andrey Borzenkov Senior system engineer

3 3

Success using Bacula to back up an iSCSI-only NetApp
by David Lee Lambert 23 Dec '08

23 Dec '08

We have a two-controller FAS2020 NetApp with 1.5TB of storage (1TB on one, 500GB on the other), licensed for iSCSI only, and an old desktop system connected to a 12-tape library of LTO-4 (800GB uncompressed) tapes. I have gotten Bacula to back up files stored on ext3fs (Linux) and NTFS (Windows) partions on iSCSI LUNs on the NetApp. The Bacula instance is running under Ubuntu Gutsy (a "long-term supported" release), using the Gutsy package, 2.0.3. We're using Postgres version 8.2.5 as the database, because that's the available Ubuntu package and we use Postgres elsewhere. We're using the "open-iscsi" initiator, from an Ubuntu package. LVM and device-mapper are not installed on the backup-host, and it only has a single Fast Ethernet connection. (The hosts that are being backed up generally have dual Gigabit Ethernet connections to the filers.) I wrote several scripts to allow Bacula to take snapshots on the filer and mount them in a known place before the backup-job runs, then clean them up afterward. I can't publish them because they have a lot of details specific to our network, but the general outline is as follows: "easy_snap" takes 3 arguments: an NTFS or ext3fs volume-label, an indication of which filer the volume is on, and the complete path to the LUN on the filer (such as "/vol/vol5/testdatav2.lun"). It makes up a name to use for the snapshot. It issues "snap create", "lun clone create" and "lun map" commands via RSH to the filer. (It also checks to see if another snapshot of the same volume is still mounted by mistake; if so, it unmounts and unmaps it.) If another snapshot with the same name exists, the script tries to delete it, and renames it if that doesn't work. It cleans up any old "bacula-" snapshots. Then it issues a local "iscsiadm -m session --rescan" command, and if it still can't see the new LUN, logs the iSCSI session out and in again. It mounts the partition using "LABEL=" syntax, to a mount-point under /mnt where the last part is the lower-case form of the volume-label. "easy_unsnap" takes the same 3 arguments as "easy_snap". It unmounts the partition, logs out the iSCSI session, unmaps the LUN, and tries to delete the snapshot. We noticed that the snapshots weren't always being deleted, which is one reason why "easy_snap" tries to clean up old snapshots several ways. If a backup spans an hour-boundary where hourly snapshots are being created, or midnight for the nightly snapshot, the mapped LUN becomes part of the snapshot and the snapshot we took can't be deleted until the hourly or nightly snapshot goes away. I tried backing up Linux hosts with a filesystem on a raw (no partions) LUN using this script, but it didn't work: when the LUN is discovered, the /dev/disk/by-label/LABEL symlink does not get created. We wouldn't be able to back up LVM volumes with this configuration either, because LVM depends on device-mapper, and device-mapper would try to grab the disks itself. Right now our performance is limited by the network interface for LUNs containing a few large files, and by Postgres INSERT performance for filesystems with lots of small files. We get 9MByte/sec for the big-file LUNs, so for example a 46-GB SQL Server database takes an hour and 18 minutes to run. We have a test-system with over 300,000 files (including over 100,000 zero-length ones) in just a few directories, but only 580 MB of total data; that took two and a half hours to back up last night. However, our entire backup (except test-systems) ran within 6 hours, and we already have more than half of our production data being backed up with Bacula. For the most part, Bacula does what we want it to do in this case, and it allows a lot more flexibility with restoring files than we were able to achieve trying to use the "dump" command on the NetApp filers. -- David L. Lambert Yahoo! IM: davidleelambert ** MSN IM: lamber45(a)cse.msu.edu

1 0

Limiting SnapDrive user capabilities
by Borzenkov, Andrey 23 Dec '08

23 Dec '08

Hi, We are looking for a possibility to limit SnapDrive account to the bare minimum. The goal is to allow some SD operations (effectively, connecting and disconnecting snapshots) to a (Windows) user, while not giving this user full administrative capabilities on a filer. I have a feeling that careful usage of roles on filer could accomplish this; anybody has done it before? I would appreciate any hints. Thank you and Merry Christmas! С уважением / With best regards / Mit freundlichen Grüβen --- Andrey Borzenkov Senior system engineer

2 1

SMVI Command Line questions
by hollandwl＠gmail.com 23 Dec '08

23 Dec '08

Just started evaluating SMVI 1.01 in our Dev environment to get a feel for how it works. A couple of things showed up immediately that I could use some clarification on: 1. Is there any way to get it to simply pass the logged on Windows credentials and not prompt for a password the first time? The current behavior totally defeats the ability to script the operations as we do not wish to store passwords in clear text. 2. Is there any way to have it create backups/snapshots in a user friendly format? Using the -backup-name switch puts the name you enter into the snapshot name, but you still end up with something like smvi-backupname-someobscenelylonguid-volname. This naming convention makes integration with snapvault difficult as I know what name I pass with -backup-name, but don't know what the hiddeously long name is going to be. It would be EXTREMELY helfpful if the snapshot name were the same as -backup-name passed on the command line.

1 0

RE: Quick question about "LUN protocol type"
by David L. Lambert 19 Dec '08

19 Dec '08

OK, I guess I phrased my question poorly. I want to make a LUN that will only be accessed by a Linux host. It will have a partition-table, and one partition in that partition-table. That partition will have a labeled ext3fs filesystem on it (Ubuntu's "mount LABEL=..." seems more reliable if I do it that way). Should I tell the NetApp that it's a "Windows" or a "Linux" LUN? Or will the NetApp behave exactly the same either way? -- David Lee Lambert -----Original Message----- From: Jeff Mohler [mailto:speedtoys.racing@gmail.com] Subject: Re: Quick question about "LUN protocol type" Why not map two Luns? ___ Sent from my $400 phone that has no text editing tools. Yay. On Dec 15, 2008, at 7:59 AM, David Lee Lambert <dlambert(a)bmtcarhaul.com> wrote: > In the FilerView LUN wizard, I see the following options for "LUN > protocol > type": > > [...] > > If we're making a LUN with a DOS partition table and one partiton that will be used by a Linux host, should we use the "Windows" or "Linux" setting? Or does it matter? > > -- > David L. Lambert > Yahoo! IM: davidleelambert ** MSN IM: lamber45(a)cse.msu.edu

2 1

Serial console cable shenanigans (FAS3020s to Cyclades)
by Nick Silkey 16 Dec '08

16 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 toasters -- I am trying to troubleshoot connectivity issues between my serial consoles and my 3020s. Per NetApp, we are 'required' to hang the X881[1] rj45-to-db9 dongle off the filers. But my Cyclades can easily grok rj-45. A phone call to NetApp revealed that a pin-out of: 4 -> 4 3 -> 6 6 -> 3 should allow me to not have to used the NetApp dongle (TSE appears to have walked the pin-outs backwards to come up with the above). Havent tested this yet; looking to confirm from those on the list since the pinout is non-standard. So is anyone out there tapping into their Cyclades without the NetApp db9 dongle hanging off their 3xx0 filer? Insight appreciated. Thanks. [1]: http://now.netapp.com/NOW/knowledge/solutions/kb13794_X881.jpg ; taken from https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb13794 - -- Nick -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAklGkAgACgkQrDQjhjXrMeJX7gCfUol7uWHNjlE8m0R1gC863CqK dqYAniNUoFg4mrgC9LNjJ09vO3VKkBAh =UPnp -----END PGP SIGNATURE-----

1 1

Leopard globalSAN iSCSI and 7.1.3
by Carl Howell 15 Dec '08

15 Dec '08

On one of our Xserve¹s, I¹ve used the Studio Network Solution¹s iSCSI initiator(3.3.0.43) with OnTap version 7.0.5 and didn¹t have any problems. Now, after upgrading to OnTap version 7.1.3, I get the following error: Mon Dec 15 16:18:36 CST [iscsi.protocol.violation:warning]: ISCSI: iSCSI protocol violation, 'Initiator did not respond to offered MaxBurstLength' Does anyone have any ideas on how to fix this? Thanks, --Carl

1 0

Re: Quick question about "LUN protocol type"
by David Lee Lambert 15 Dec '08

15 Dec '08

No, when I say a "DOS partition table" I mean what I get by running the program "/sbin/fdisk" under Linux, and subsequently doing e.g. mke2fs -L APPDATA -j /dev/sde1 instead of just doing mke2fs -L APPDAT -j /dev/sde On Monday 15 December 2008 11:19:48 am Webster, Stetson wrote: > Question: Is DOS directly interfacing with the lun? Do you have SAN device > drivers for DOS? > -----Original Message----- > From: David Lee Lambert [mailto:dlambert@bmtcarhaul.com] > Subject: Quick question about "LUN protocol type" > > In the FilerView LUN wizard, I see the following options for "LUN protocol > type": > [...] > > If we're making a LUN with a DOS partition table and one partiton that will > be used by a Linux host, should we use the "Windows" or "Linux" setting? > Or does it matter? -- David L. Lambert Software Developer, Precision Motor Transport Group, LLC Work phone 517-349-3011 x223 Cell phone 586-873-8813

1 0

Quick question about "LUN protocol type"
by David Lee Lambert 15 Dec '08

15 Dec '08

In the FilerView LUN wizard, I see the following options for "LUN protocol type": Solaris Windows - "The LUN will be used to store a raw disk device in a single-partition Windows disk" HP-UX AIX Linux - "The LUN will be used to store a Linux raw disk with no partition table" NetWare VMware The "na_snap" manpage also lists the types "windows_gpt" and "vld". If we're making a LUN with a DOS partition table and one partiton that will be used by a Linux host, should we use the "Windows" or "Linux" setting? Or does it matter? -- David L. Lambert Yahoo! IM: davidleelambert ** MSN IM: lamber45(a)cse.msu.edu

1 0

RE: qtree "top" tool
by Glenn Walker 14 Dec '08

14 Dec '08

All good points. That said, when I said 'write tool' and 'cifs top' I was thinking more interactive on the CLI of the actual filer to spot check stuff. I could have all of the talent in the world and not be able to produce this without getting it checked into the ONTAP code ;) Perhaps I will un-lazy myself when I get free time and give a client script version of this a whirl. Glenn -----Original Message----- From: Jeff Mohler [mailto:speedtoys.racing@gmail.com] Sent: Friday, December 12, 2008 10:37 PM To: Glenn Walker Cc: Todd C. Merrill; Nicholas Bernstein; Toasters Subject: Re: qtree "top" tool Netapp -could- write a lot of things. But there'd always be the "It'd be nice if..." But..then they'd be paying script writers instead of engineers by the lot, and the CLI and ZAPI are pretty open and available. But if I had any talent at all to script anything, Id be doing something like this too, perhaps. On Fri, Dec 12, 2008 at 7:25 PM, Glenn Walker <ggwalker(a)mindspring.com> wrote: > This is a good point. > > Using the perfstat tool will give you some running incrementals (it > zeroes for each iteration), but I think you want more of a tool like > cifs top, no? I don't see why NetApp couldn't easily write something > like this, and it would be a good tool to have: sysstat only goes so > far. > > Glenn > > -----Original Message----- > From: Todd C. Merrill [mailto:tmerrill@mathworks.com] > Sent: Friday, December 12, 2008 2:25 PM > To: Glenn Walker > Cc: Nicholas Bernstein; Toasters > Subject: RE: qtree "top" tool > > > Yes, I know about `qtree stats`. But, just like nfsstat, > it gives you cumulative stats. > > The NFS top tool I mentioned does an incremental nfsstat. > I'm looking for the same--*incremental* qtree stats, > in order to debug high usage as it is happening. > > > On Wed, 10 Dec 2008, Glenn Walker wrote: > >> You mean qtree stats? >> >> It shows CIFS and NFS ops per qtree - doesn't work at the vol level >> (wish it would). >> >> Glenn >> >> -----Original Message----- >> From: owner-toasters(a)mathworks.com > [mailto:owner-toasters@mathworks.com] >> On Behalf Of Nicholas Bernstein >> Sent: Wednesday, December 10, 2008 1:00 PM >> To: Toasters >> Subject: Re: qtree "top" tool >> >> I don't have a filer in front of me to test, but isn't there a stats >> show >> qtree? >> >> >> On 12/9/08 6:16 PM, "Todd C. Merrill" <tmerrill(a)mathworks.com> wrote: >> >> > Folks, >> > Before I write one myself or modify the NFS top tool >> > on the NOW toolchest: >> > >> > http://now.netapp.com/NOW/download/tools/ntaptop/ >> > >> > does anybody have an equivalent one for `qtree stats`? >> > >> > >> > Until next time... >> > >> > The MathWorks, Inc. 508-647-7000 x7792 >> > 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX >> > tmerrill(a)mathworks.com http://www.mathworks.com >> > --- >> > >> >> -- >> Nicholas Bernstein >> Technologist, Consultant, Instructor >> http://nicholasbernstein.com >> >> >> >> > > > Until next time... > > The MathWorks, Inc. 508-647-7000 x7792 > 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX > tmerrill(a)mathworks.com http://www.mathworks.com > --- > > >

1 0

do toaster need a day off? (WAFL scans)
by Todd C. Merrill 13 Dec '08

13 Dec '08

Two scenarios: 1. R200, 7.2.2, two 12 TB aggregates, 85 volumes of various sizes, 70-80% full snapvault secondary, ALWAYS receiving snapvaults and nearly ALWAYS spinning to tape. 2. 6070, 7.2.4, two 8 TB aggregates, 27 volumes between 150 and 700 GB, 60-70% full recent migration (via volume snapmirrors) from 980's, serves home directories to NFS and CIFS clients. We stopped all snapmirrors/snapvaults to the R200, terminated CIFS, and shut off NFS. CPU utilization remained 90%+ and disk reads remained high for the next 6-7-8 hours until it finally quieted down. After volume snapmirroring the home dirs from the 980's to the 6070, we re-pointed the snapvaults (modify; start -r) and allowed NFS and CIFS access. 5 days later, file server performance still blows (worse than the 980's -- D'oh! Egg, meet Face; Face, meet Egg), with moderate CPU load 30-40-50% but high disk reads. In both cases, we determined that lots of WAFL scans were going on: container block reclamation volume deswizzling active bitmap rearrangement (of course...this NEVER seems to stop) and a few other types that have already scrolled out of my buffer. So, we figure--eventually--the WAFL scans will catch up and performance will go back to normal on the 6070. The performance of the R200 always blows. So...here finally is the question: do toasters need a day off? Said another way, to maintain acceptable performance and low/fast response times, do toasters need a goodly amount of (relatively) idle time in order for these WAFL scans to complete? Could the sub-optimal performance of another group of six 6070's that we have, that we *pound on* 7x24, be explained in part by always having at least the container block reclamation scan going on? Until next time... The MathWorks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill(a)mathworks.com http://www.mathworks.com ---

5 7

Snapvault hangs after tranfering a gig of data?
by Page, Jeremy 11 Dec '08

11 Dec '08

Going from a 7.2.4 machine to a 7.3 machine. This is an update. Here's what the secondary says: sim-array01*> snapvault status -l sim-array01:/vol/gso_shares/snapvault Snapvault secondary is ON. Source: 172.1.0.2:/vol/shares Destination: sim-array01:/vol/gso_shares/snapvault Status: Transferring Progress: 1209016 KB State: Snapvaulted Lag: 39:53:10 Mirror Timestamp: Tue Dec 9 23:02:54 EST 2008 Base Snapshot: sim-array01(0101197614)_gso_shares-base.2 Current Transfer Type: Update Current Transfer Error: - Contents: Transitioning Last Transfer Type: Update Last Transfer Size: 19680896 KB Last Transfer Duration: 05:11:29 Last Transfer From: 172.1.0.2:/vol/shares And here is what's on the primary: gvr-array02*> snapvault status -l sim-array01:/vol/gso_shares/snapvault Snapvault primary is ON. Source: gvr-array02:/vol/shares Destination: sim-array01:/vol/gso_shares/snapvault Status: Transferring Progress: 1212912 KB State: Source Lag: 39:56:53 Mirror Timestamp: Tue Dec 9 23:02:54 EST 2008 Base Snapshot: sv_daily.1 Current Transfer Type: - Current Transfer Error: - Contents: - Last Transfer Type: - Last Transfer Size: 19680896 KB Last Transfer Duration: 05:11:32 Last Transfer From: - I am at a loss, do I need to kill it and do a -r? This is the second time it's stopped (last night it did the same thing and I had to kill it, thus the long Lag: time. Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance. In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.

3 3

Snapvaults schedules not at the top of the hour
by Page, Jeremy 10 Dec '08

10 Dec '08

What would be the best way to get snapvault to move a snapshot from the primary that's not created on an hour boundary? We're putting our DB into hot backup mode at 9:05 and I don't want to make the DBA change his scripts if possible, is there a way (maybe with rsh+cron) that I can manually create a snapshot at 9:15 and then use snapvault to transfer it? Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance. In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.

3 2

Jump to page:

2026

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