toasters September 2008

toasters@lists.teaparty.net

52 participants
35 discussions

Inconsistent ndmpcopy performance on a 3020 cluster
by Nathan Patwardhan 17 Sep '08

17 Sep '08

Hello, We've got a 3020 cluster that's running OnTap 7.2.3; each node in the cluster is connected to DS14 and DS14MK2 shelves. We recently added some shelves (DS14 MK2) and as part of this maintenance we decided to migrate data off the existing traditional volumes to new flexible volumes since we're not interested in having traditional volumes anymore. For this purpose we used ndmpcopy -- to migrate data between shelves *local* to each node in the cluster, e.g.: filer> ndmpcopy -l 0 /vol/oldtradvol /vol/newflexvol Since we'd done this kind of maintenance on our other 3020s before, we'd expected throughput of ~18-20g/hr as this hardware is identical to filers we'd worked on in the past. Unfortunately results were totally inconsistent: node A performed as we'd expected and I was able to migrate 300g of data overnight. node B has consistently transferred 3-6g/hr. I'm not seeing any errors on node B and I've rechecked my cabling to make sure nothing is amiss. Why might I see such disparity in results on node A and node B? -- Nathan Patwardhan "But the album's biggest setback, other than the fact that its title sounds like a Neutrogena product, ..." -- review of Jewels' latest album

5 7

Re: Inconsistent ndmpcopy performance on a 3020 cluster
by Eino Tuominen 16 Sep '08

16 Sep '08

Nathan Patwardhan wrote: > > node A performed as we'd expected and I was able to migrate 300g of > data overnight. > node B has consistently transferred 3-6g/hr. Hi, Have you checked the utilization on the filers? How does sysstat -u compare? -- Eino Tuominen

1 0

Re: SnapManager for Vmware
by Darren Sykes 16 Sep '08

16 Sep '08

Matt, Yep, that's what we've found too, and I've logged a feature request. We planned to use a pagefile datastore which was snapmirrored less frequently and not snapshotted. However, SMVI can't really handle that (unless you kludge it with independent disks) but Vibe has no problem doing so. The problem for me is that Vibe is free and although less polished has the same, if not more functionality than SMVI. Darren On 16/09/2008 07:41, "Matt Hallmark" <matt(a)cosmictoaster.com> wrote: > That would suck. It has more functionality (at present, I've filed > feature requests) than SMVI atm. For instance, VIBE has be ability to > select only specific datastore(s), whereas SMVI will select AND snap > associated datastores, based on the VMs. > > Matt Hallmark > > On Sep 15, 2008, at 4:10 PM, Glenn Walker wrote: > >> I was under the impression that vibe was going to go the way of the >> dinosaur in favor of SMVI? >> >> From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com >> ] On Behalf Of Darren Sykes >> Sent: Monday, September 15, 2008 10:47 AM >> To: Davies,Matt; toasters(a)mathworks.com >> Subject: RE: SnapManager for Vmware >> >> We¹ve been running it on our production VM¹s for a couple of weeks. >> >> It seems to do what it says on the tin. However, quite how much >> value it offers on top of their free Vibe product is debateable. >> >> >> >> From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com >> ] On Behalf Of Davies,Matt >> Sent: 15 September 2008 14:02 >> To: toasters(a)mathworks.com >> Subject: SnapManager for Vmware >> >> >> Hi all, >> >> Has anyone had any experience of SnapManager for VMware yet, either >> good or bad ? >> >> Thanks >> >> Matt >> >> >> ____________________________ >> Matt Davies >> Director of International IT Operations >> General Atlantic >> 83 Pall Mall >> London >> SW1Y 5ES >> >> Tel: +44 207 484 3203 >> Fax: +44 207 484 2803 >> Mobile: +44 777 559 4265 >> ____________________________ >> >> >> >> ____________________________________________________________ >> >> This e-mail (including all attachments) is confidential and may be >> privileged. >> It is for the exclusive use of the addressee only. If you are not >> the addressee, >> you are hereby notified that any dissemination of this communication >> is strictly >> prohibited. If you have received this communication in error, please >> erase all >> copies of the message and its attachments and notify us immediately at >> help(a)generalatlantic.com. Thank You. >> >> >> >> >> To report this email as spam click here. >> >

3 6

SnapManager for Vmware
by Davies,Matt 15 Sep '08

15 Sep '08

Hi all, Has anyone had any experience of SnapManager for VMware yet, either good or bad ? Thanks Matt ____________________________ Matt Davies Director of International IT Operations General Atlantic 83 Pall Mall London SW1Y 5ES Tel: +44 207 484 3203 Fax: +44 207 484 2803 Mobile: +44 777 559 4265 ____________________________ _____________________________________________________________ This e-mail (including all attachments) is confidential and may be privileged. It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at help(a)generalatlantic.com <mailto:help@generalatlantic.com>. Thank You.

3 2

Re: Snaplock Enterprise
by Steffen Kammerer 15 Sep '08

15 Sep '08

Hi all, I changed the snaplock volume to 0d today in the morning. I think it took some time to make it active... Now I can create a file, make it read only and delete it. No problem. Modifying the file is still not permitted but thats ok... Thanks for your help. Regards, Steffen -----Original Message----- From: Steiner, Jeffrey [mailto:Jeffrey.Steiner@netapp.com] Sent: Monday, September 15, 2008 1:47 PM To: Roesler, Brigitte; Steffen Kammerer Subject: RE: Snaplock Enterprise If you keep reading that KB article, there's a note at the bottom that explains that 0d=infinite was due to a bug. It was NOT the intended function of 0d. A retention of 0d should be immediately deleteable unless you're subject to the bug which was fixed in 7.1.2. I learned of this bug the hard way when I snaplocked about 2TB of data into infinity and had to get the entire aggregate replaced. > -----Original Message----- > From: Roesler, Brigitte [mailto:brigitte.roesler@siemens.com] > Sent: Monday, September 15, 2008 12:42 PM > To: Steffen Kammerer > Cc: ROESLER, BRIGITTE; Steiner, Jeffrey > Subject: AW: Snaplock Enterprise > > Hello, > > maybe the NetApp-articel > "https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb18 > 752" will help / will be of interest. > > Aggregates / Volumes created with the Snap Lock Compliance license > cannot be changed to the Snap Lock Enterprise license. > > So be very careful with the snaplock options "0d", because > **************************** > 0d is the same as "infinite" > **************************** > . > > Therefore we set the minimum and default snaplock period to "1d". > > Best regards, > Brigitte Rösler > > > -----Ursprüngliche Nachricht----- > Von: owner-toasters(a)mathworks.com > [mailto:owner-toasters@mathworks.com] Im Auftrag von Steiner, Jeffrey > Gesendet: Montag, 15. September 2008 12:42 > An: Steffen Kammerer; toasters(a)mathworks.com > Betreff: RE: Snaplock Enterprise > > Sorry, I mentally transposed Enterprise and Compliance. In any case, > the volume type is tied to the aggregate type. > > Still, you should be able to delete the file with a retention time of > 0d. That means WORM but deleteable right away. I've done it within > scripts a few times where I needed a file WORM right away but there > was a delay in determining what the retention time should be. The > script set that later on. > > > ________________________________ > > From: Steffen Kammerer [mailto:steffen.kammerer@brainlab.com] > Sent: Monday, September 15, 2008 11:17 AM > To: Steiner, Jeffrey; toasters(a)mathworks.com > Subject: RE: Snaplock Enterprise > > > I have set the retention time to 0d but it is not deleteable... I > think you have to wait for at least 23 hours > 59 minutes and 59 seconds... > > I have installed snaplock enterprise, so I can offline and destroy > volumes to test... > > > > ________________________________ > > From: Steiner, Jeffrey [mailto:Jeffrey.Steiner@netapp.com] > Sent: Monday, September 15, 2008 12:12 PM > To: Steffen Kammerer; toasters(a)mathworks.com > Subject: RE: Snaplock Enterprise > > > When you set a file to read-only with a retention time of zero days, > the file should be WORM but deleteable immediately. A snaplock volume > is tied to the overall aggregate, so it is correct that a Snaplock > Enterprise aggregate can host only Snaplock Enteprise volumes. > > Be extremely careful. If you commit a file with a particular > retention date, you cannot delete the volume or the aggregate until > all the contained files are expired. > There is no back door. > > > ________________________________ > > From: Steffen Kammerer > [mailto:steffen.kammerer@brainlab.com] > Sent: Monday, September 15, 2008 10:13 AM > To: toasters(a)mathworks.com > Subject: Snaplock Enterprise > > > Hi all, > > have anyone experienced snaplock enterprise? > > I have a snaplock enterprise aggregate in which I create volumes. As > far as I know the volume will inherit the snaplock enterprise. The > compliance clock is also set. > > -- > > The options of my testvol look like > > xxxxxx> vol options testvol > nosnap=off, nosnapdir=off, minra=off, no_atime_update=on, > nvfail=off, > ignore_inconsistent=off, snapmirrored=off, create_ucode=off, > convert_ucode=off, maxdirsize=20971, schedsnapname=ordinal, > fs_size_fixed=off, snaplock_enterprise, guarantee=volume, > svo_enable=off, svo_checksum=off, svo_allow_rman=off, > svo_reject_errors=off, no_i2p=off, > fractional_reserve=100, > snaplock_default_period=min, snaplock_minimum_period=0d, > snaplock_maximum_period=30y, extent=off, try_first=volume_grow > > snaplock options look like > > xxxxxx> options snaplock > snaplock.autocommit_period none > snaplock.compliance.write_verify off > > -- > > If I copy data in this volume (using cifs) and change the files to > read only I can not change data any more. > But the snaplock_minimum_period is set to 0 days. > > Now my final question: > > Is it not possible to create volumes within a snaplock enterprise > aggregate without using snaplock enterprise?! > > Do you have any hints?! > > Regards, > > Steffen > >

1 0

Snaplock Enterprise
by Steffen Kammerer 15 Sep '08

15 Sep '08

Hi all, have anyone experienced snaplock enterprise? I have a snaplock enterprise aggregate in which I create volumes. As far as I know the volume will inherit the snaplock enterprise. The compliance clock is also set. -- The options of my testvol look like xxxxxx> vol options testvol nosnap=off, nosnapdir=off, minra=off, no_atime_update=on, nvfail=off, ignore_inconsistent=off, snapmirrored=off, create_ucode=off, convert_ucode=off, maxdirsize=20971, schedsnapname=ordinal, fs_size_fixed=off, snaplock_enterprise, guarantee=volume, svo_enable=off, svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off, no_i2p=off, fractional_reserve=100, snaplock_default_period=min, snaplock_minimum_period=0d, snaplock_maximum_period=30y, extent=off, try_first=volume_grow snaplock options look like xxxxxx> options snaplock snaplock.autocommit_period none snaplock.compliance.write_verify off -- If I copy data in this volume (using cifs) and change the files to read only I can not change data any more. But the snaplock_minimum_period is set to 0 days. Now my final question: Is it not possible to create volumes within a snaplock enterprise aggregate without using snaplock enterprise?! Do you have any hints?! Regards, Steffen

3 5

hot swapping 3170 head
by Jerry 13 Sep '08

13 Sep '08

Has anyone tried or tested pulling out a 3170 head from the new dual head chassis on the fly? Is there any magic steps to make sure things don't blow up when you do this?

1 1

Best Practices !!!
by Zeeshan 10 Sep '08

10 Sep '08

Hello all We are upgrading our storage from IBM N3600 to FAS6040... What are the best/recommended practices for powering it up... Does any one have some installation guides/check lists on this??? Thanx

2 1

Re: Best Practices !!!
by unix_thai＠yahoo.com 10 Sep '08

10 Sep '08

You should power up the shelves first then the head. If these are supported devices, you should be able to get netapp tech support to help. ------Original Message------ From: Zeeshan Sender: owner-toasters(a)mathworks.com To: Toasters List Sent: Sep 10, 2008 12:46 AM Subject: Best Practices !!! Hello all We are upgrading our storage from IBM N3600 to FAS6040... What are the best/recommended practices for powering it up... Does any one have some installation guides/check lists on this??? Thanx Sent via BlackBerry by AT&T

2 1

Re: CIFS Guide
by unix_thai＠yahoo.com 09 Sep '08

09 Sep '08

The only thing I can think of is the manuals themselves. ------Original Message------ From: Cristian Rojas Sender: owner-toasters(a)mathworks.com To: toasters(a)mathworks.com Sent: Sep 7, 2008 11:06 AM Subject: CIFS Guide Hi list, which would be the most comprehensible CIFS Administration document you came across for OnTAP 7.2.3? THanks Cristian Sent via BlackBerry by AT&T

1 0

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 September 2008