Nabble - Network Appliance - Toasters

R: Linkedin group

2008-09-05T08:28:13Z

Happy to see that my proposal has been approved. Of course I want copy
right on that logo!!! Just joking... :-)

Bye!

-----Messaggio originale-----
Da: owner-toasters@... [mailto:owner-toasters@...]
Per conto di Lori Barfield
Inviato: sabato 30 agosto 2008 6.52
A: Nicholas Bernstein
Cc: Toasters
Oggetto: Re: Linkedin group

On Fri, Aug 29, 2008 at 7:27 PM, Nicholas Bernstein
<nick@...> wrote:
> I didn't happen to see a toasters group on linkedin (the professional
> networking site) so I made one. [...]

there are actually many netapp user groups. but none are
sporting the name "toasters" and (most importantly) no one
has come up with a creative toaster group logo yet.

http://www.linkedin.com/groupsDirectory?results=&sik=1220071642944

...lori

RE: How to identify a hot disk

2008-09-05T07:26:16Z

Hi,

Something to ask NetApp about, there may be an extra bit of cache hardware coming out (PAM - I think?) that can plug into a 31xx series box that will cache many of these de duped blocks alleviating the hot spot problem.

Futures bright.

Page, Jeremy wrote:

For anyone interested this was (is) being cause by SIS running on the
effected RGs, I'm moving a 1/2 TB a day or so to the new system so it's
got a lot to crunch right now. I'll send another message out in a week
or two and let folks know how it is acting once things calm down.

So far all NFS for our moderately sized ESX environment is running very
well. We've got 140 VMs moved over so far and things are running very
smoothly.

-----Original Message-----
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]
On Behalf Of Page, Jeremy
Sent: Thursday, June 05, 2008 8:38 PM
To: Blake Golliher; Blackmor, Chris
Cc: Hadrian.Baron@vegas.com; toasters@mathworks.com
Subject: RE: How to identify a hot disk

I don't understand how the fragmentation occurred in the first place,
this is a brand new filer, we've not even had any snapshots age out yet.
All the disks where added to the aggr at the same time, lots of free
space.

The only thing odd is that we did have ASIS run, I wonder if the
fragmentation is from all the stuff getting de-duped (it's a bunch of
VMs)

-----Original Message-----
From: Blake Golliher [mailto:thelastman@gmail.com]
Sent: Thursday, June 05, 2008 5:17 PM
To: Blackmor, Chris
Cc: Hadrian.Baron@vegas.com; Page, Jeremy; toasters@mathworks.com
Subject: Re: How to identify a hot disk

It'll depend on how busy your disks are during prime time. Safety first
people!

On Thu, Jun 5, 2008 at 1:38 PM, Blackmor, Chris <Chris.Blackmor@amd.com>
wrote:
> My understanding of reallocate is that it will put a definite load on
your
> filer and shouldn't be run during prime time.
>
> ----- Original Message -----
> From: owner-toasters@mathworks.com <owner-toasters@mathworks.com>
> To: 'Page, Jeremy' <jeremy.page@gilbarco.com>; toasters@mathworks.com
> <toasters@mathworks.com>
> Sent: Thu Jun 05 10:57:12 2008
> Subject: RE: How to identify a hot disk
>
> It's good you are at 50% aggr usage, as you'll need 50% free space in
each
> volume you run the reallocate on. I think running the reallocate is
the
> best first step as it is fairly un-intrusive and you can run it during
the
> day unless you are hammering the filer constantly. When we run it we
use
> the parameter -f to force reallocation without caring how well it is
already
> laid out. Not sure about your question on A-SIS.
>
>
>
> HTH,
>
>
>
> - Hadrian
>
>
>
> From: owner-toasters@mathworks.com
[mailto:owner-toasters@mathworks.com] On
> Behalf Of Page, Jeremy
> Sent: Thursday, June 05, 2008 7:13 AM
> To: toasters@mathworks.com
> Subject: RE: How to identify a hot disk
>
>
>
> Thu Jun 5 10:06:02 EDT [gvr-array02: wafl.scan.layout.advise:info]:
WAFL
> layout ratio for volume nfs2 is 4.01. A ratio of 1 is optimal. Based
on your
> free space, 1.42 is expected.
>
>
>
> Would you say I need to do a reallocate? I'm not sure why this is so
> fragmented, this file system has never been more then 50% full, could
A-SIS
> have something to do with it?
>
>
>
> Jeremy M. Page____________________
>
> Systems Architect
>
> * email:Jeremy.Page@gilbarco.com - ( phone: 336.547.5399 - 6 fax:
> 336.547.5163 - ( cell: 336.601.7274
>
> ________________________________
>
> From: Uddhav Regmi [mailto:uddhav.regmi@worldnet.att.net]
> Sent: Thursday, June 05, 2008 9:38 AM
> To: Page, Jeremy; toasters@mathworks.com
> Subject: RE: How to identify a hot disk
>
>
>
> hmmm
>
> very interesting....
>
> looks like those are max out
>
> do wafl scan measure layout and see where you stand....
>
> if needed do reallocate.....
>
> I have seen hundreds of cases where it helped a lot
>
>
>
> -uddhav
>
>
>
> From: owner-toasters@mathworks.com
[mailto:owner-toasters@mathworks.com] On
> Behalf Of Page, Jeremy
> Sent: Thursday, June 05, 2008 8:27 AM
> To: toasters@mathworks.com
> Subject: Re: How to identify a hot disk
>
>
>
> Not sure why but I have two disks that are maxed out while the rest
are far
> lower utilization. What would cause this, the raid groups where
created all
> at the same time, there are 10 disks per raid group and 3 groups in
the
> aggragate.
>
>
>
>
>
> /aggr0/plex0/rg0:
>
> 1c.16 2 0.94 0.18 1.00 42250 0.49 12.18 1396
0.27
> 11.83 521 0.00 .... . 0.00 .... .
>
> 1c.32 6 2.56 0.49 1.00 104545 1.80 4.18 1323
> 0.27 11.83 634 0.00 .... . 0.00 .... .
>
> 1c.48 98 116.05 114.20 1.62 18481 1.53 4.24 1743
0.31
> 11.00 2649 0.00 .... . 0.00 .... .
>
> 1c.17 41 55.21 54.76 2.17 5697 0.27 20.17 1537
0.18
> 16.25 600 0.00 .... . 0.00 .... .
>
> 1c.33 49 72.07 71.62 1.84 4760 0.27 20.67 871
0.18
> 16.75 1239 0.00 .... . 0.00 .... .
>
> 1c.49 45 61.42 60.97 2.18 4047 0.22 23.00 913
0.22
> 14.40 931 0.00 .... . 0.00 .... .
>
> 1c.64 5 117.40 116.86 1.61 307 0.36 15.25 1336
0.18
> 18.00 319 0.00 .... . 0.00 .... .
>
> 1c.65 4 71.76 71.17 1.83 292 0.27 20.67 1298
0.31
> 10.43 370 0.00 .... . 0.00 .... .
>
> 1c.80 4 49.50 49.05 2.36 333 0.22 22.80 1333
0.22
> 14.60 712 0.00 .... . 0.00 .... .
>
> 1c.81 5 95.14 94.69 1.71 292 0.22 22.80 1325
0.22
> 14.60 548 0.00 .... . 0.00 .... .
>
> /aggr0/plex0/rg1:
>
> 1c.66 1 0.67 0.00 .... . 0.31 19.29 1311
0.36
> 10.50 238 0.00 .... . 0.00 .... .
>
> 1c.83 1 0.67 0.00 .... . 0.31 19.29 1415
0.36
> 10.50 190 0.00 .... . 0.00 .... .
>
> 1c.82 4 48.60 48.24 2.21 320 0.22 22.80 1553
0.13
> 21.33 234 0.00 .... . 0.00 .... .
>
> 1c.19 51 67.89 67.44 1.92 5315 0.22 22.80 1281
0.22
> 13.20 788 0.00 .... . 0.00 .... .
>
> 1c.18 55 72.75 72.34 1.90 4996 0.22 23.00 1122
0.18
> 16.00 1109 0.00 .... . 0.00 .... .
>
> 1c.35 30 36.10 35.52 2.67 3190 0.31 15.86 1802
0.27
> 11.33 588 0.00 .... . 0.00 .... .
>
> 1c.34 41 52.97 52.43 2.04 4207 0.31 16.29 1570
0.22
> 13.60 750 0.00 .... . 0.00 .... .
>
> 1c.51 100 119.82 119.46 1.57 25873 0.22 22.80 1588
0.13
> 21.33 2313 0.00 .... . 0.00 .... .
>
> 1c.50 59 72.03 71.44 1.83 7750 0.27 19.33 1233
0.31
> 10.86 1289 0.00 .... . 0.00 .... .
>
> 1c.67 4 94.60 94.15 1.68 279 0.18 24.50 1071
0.27
> 12.33 338 0.00 .... . 0.00 .... .
>
> /aggr0/plex0/rg2:
>
> 1c.85 1 0.94 0.00 .... . 0.54 12.00 1806
0.40
> 10.11 538 0.00 .... . 0.00 .... .
>
> 1c.84 1 0.94 0.00 .... . 0.54 12.00 1729
0.40
> 10.11 495 0.00 .... . 0.00 .... .
>
> 1c.21 47 67.40 66.90 1.86 4701 0.27 19.17 1452
0.22
> 14.20 845 0.00 .... . 0.00 .... .
>
> 1c.20 56 73.56 73.02 1.79 4866 0.18 25.50 1039
> 0.36 9.63 870 0.00 .... . 0.00 .... .
>
> 1c.37 51 68.79 68.21 1.76 6072 0.27 19.17 1174
0.31
> 11.43 988 0.00 .... . 0.00 .... .
>
> 1c.36 42 50.85 50.18 2.31 3807 0.40 12.78 1852
0.27
> 13.33 800 0.00 .... . 0.00 .... .
>
> 1c.53 59 75.85 75.18 1.86 5024 0.36 14.25 2237
0.31
> 10.43 493 0.00 .... . 0.00 .... .
>
> 1c.52 18 21.27 20.77 3.83 2205 0.27 19.17 1496
0.22
> 14.20 465 0.00 .... . 0.00 .... .
>
> 1c.69 5 71.76 71.00 1.96 296 0.40 12.78 2087
> 0.36 9.63 610 0.00 .... . 0.00 .... .
>
> 1c.68 5 71.58 71.13 1.84 352 0.22 23.60 1314
0.22
> 14.80 514 0.00 .... . 0.00 .... .
>
>
>
> This message (including any attachments) contains confidential
> and/or proprietary information intended only for the addressee.
> Any unauthorized disclosure, copying, distribution or reliance on
> the contents of this information is strictly prohibited and may
> constitute a violation of law. If you are not the intended
> recipient, please notify the sender immediately by responding to
> this e-mail, and delete the message from your system. If you
> have any questions about this e-mail please notify the sender
> immediately.
>
> This message (including any attachments) contains confidential
> and/or proprietary information intended only for the addressee.
> Any unauthorized disclosure, copying, distribution or reliance on
> the contents of this information is strictly prohibited and may
> constitute a violation of law. If you are not the intended
> recipient, please notify the sender immediately by responding to
> this e-mail, and delete the message from your system. If you
> have any questions about this e-mail please notify the sender
> immediately.
>
>

This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law. If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system. If you
have any questions about this e-mail please notify the sender
immediately.

This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law. If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system. If you
have any questions about this e-mail please notify the sender
immediately.

Re: Noob...

2008-09-04T09:13:22Z

Instead of snap sched vol_bond 0 0 0 you an use vol options vol_bond nosnap on

----- Original Message -----

From: G.Milazzo@...

To: Jochen.Willeke@... ; David.Ashton@... ; toasters@...

Sent: Thursday, September 04, 2008 9:06 AM

Subject: R: Noob...

A first answer came from Jochen and Ive to add that if you have a volume that has to contain a LUN (that is, with NetApp, a file) the default snapshot reservation area of 20% (or less) must be removed, so the snap schedule.

In your case

Filer> snap reserve vol_bond 0

Filer> snap sched vol_bond 0 0 0

This in case you use some software of Snapmanager suite (You did not tell us the usage of that lun) or the snapmirror snapshots will be placed in the active file system area having the necessary free space. Never size a volume less that 2/2.5 time the size of the contained luns.

Bye

Da: owner-toasters@... [mailto:owner-toasters@...] Per conto di Willeke, Jochen
Inviato: giovedì 4 settembre 2008 12.54
A: David.Ashton@...; toasters@...
Oggetto: RE: Noob...

Hi David,

as far as i can see, everything is as expected.
When you have fractional_reserve set to 100 (%), as soon as you create snapshots on that volume, ontap will reserve 100% of the Luns size within the volume, to gurantee writes to complete successfully.

The maths show:

820GB * 0,8 (for snap reserve) = 656 GB

320GB Lun * 2 (for fractional reserve) = 640 GB

P = 640 / (656*100) = 97,56 %

Think ontap is doing some rounding, so 98% is correct.

Regards

Jochen

From: owner-toasters@... [mailto:owner-toasters@...] On Behalf Of David.Ashton@...
Sent: Thursday, September 04, 2008 12:04 PM
To: toasters@...
Subject: Noob...

Hi, please excuse my noobness, I've recently inherited a Netapp system or 3, I'm fairly new to SANs in general and netapp in particular. This isnt my full time gig (storage), its one thing amongst the 2 thousand other things I'm working on today, but I allocate a fair amount of time to figuring this stuff out.

I'm struggling with something I'm sure all netapp storage people go through, I've read the manuals, I've played around for about 6 months on the filers and I cant answer this.

I have a FAS3020. I have a volume, lets call it vol_bond. Its 820GB, 20% snap reserve. It contains one lun, which is 320GB. The space guarantee is volume, and fractional reserve is 100.

Currently, there are 5 snapshots, totalling 8GB. It is snap mirrored to another filer. Snapshots are created nightly, there are no problems with that. At weekends, after various backup activity, these grow to about 80GB, but we only keep 5 and they're deleted.

Its all up and running, everythings fine.

Except for the filer status which reports: /vol/vol_bond is full (using or reserving 98% of space and 0% of inodes, using 49% of reserve) and the df -r output is

/vol/vol_bondv8/ 687865856 670681368 17184488 335194536 /vol/vol_bondv8/
/vol/vol_bondv8/.snapshot 171966464 14140040 157826424 0 /vol/vol_bondv8/.snapshot

What am I missing? I thought I had this thing nailed but obviously not.

Dave Ashton

**********************************************************************

The information contained in this e-mail and any attachments are intended for the named recipient(s) only. It may also be privileged and confidential. If you are not an intended recipient, you must take no action as a result of receiving it, including, but not limited to copying, distributing and amending it. If this communication has been sent to you in error, please contact us immediately and do not show the communication to any other party.

Rullion shall have no liability whatsoever in respect of the content of the communication and makes no warranty as to accuracy. Any views or opinions presented are solely those of the author.

Viruses:- Although we have taken steps to ensure that this e-mail and attachments are free from viruses, we advise that in keeping with good computing practice, the recipient should ensure they are actually virus free.

**********************************************************************

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Re: R: Noob...

2008-09-04T09:11:43Z

DO NOT DO THIS if it is an Oracle database. We did a few years ago and started having weird issues. Also, you are on your own if you do. Oracle does not support running databases over CIFS. They support NFS and LUNs, but no CIFS.

----- Original Message -----

From: G.Milazzo@...

To: David.Ashton@...

Cc: Jochen.Willeke@... ; owner-toasters@... ; toasters@...

Sent: Thursday, September 04, 2008 9:51 AM

Subject: R: R: Noob...

Ok.

If the lecacy application could do it consider the usage of a CIFS shared area instead of a LUN formatted and mounted on Windows VM.

The file system overall performances will be more than better ;-)

Double space available, snapshotting faster and so on…

Da: David.Ashton@... [mailto:David.Ashton@...]
Inviato: giovedì 4 settembre 2008 15.33
A: Milazzo Giacomo
Cc: Willeke, Jochen; owner-toasters@...; toasters@...
Oggetto: Re: R: Noob...

thanks all for the excellent advice and pointers. I'll remove the snap reserve, I think the sizing is probably correct then.

The lun is mounted on a windows server that has snapdrive installed. The rate of change - varies from 3GB somedays to 80GB on others.
The server runs a legacy app that uses an enormous 3.6 million flat text files (220GB), and the number of open files is in the 10,000's at any one time so it gets a battering.

Dave

Rullion Management Services Ltd is a company registered in England and Wales with company number 2797732.

"Milazzo Giacomo" <G.Milazzo@...>
Sent by: owner-toasters@...

04/09/2008 14:06

To

"Willeke, Jochen" <Jochen.Willeke@...>, <David.Ashton@...>, <toasters@...>

cc

Subject

R: Noob...

A first answer came from Jochen and I’ve to add that if you have a volume that has to contain a LUN (that is, with NetApp, a file) the default snapshot reservation area of 20% (or less) must be removed, so the snap schedule.
In your case

Filer> snap reserve vol_bond 0
Filer> snap sched vol_bond 0 0 0

This in case you use some software of Snapmanager suite (You did not tell us the usage of that lun) or the snapmirror snapshots will be placed in the active file system area having the necessary free space. Never size a volume less that 2/2.5 time the size of the contained luns.

Bye

Da: owner-toasters@... [mailto:owner-toasters@...] Per conto di Willeke, Jochen
Inviato: giovedì 4 settembre 2008 12.54
A: David.Ashton@...; toasters@...
Oggetto: RE: Noob...

Hi David,

as far as i can see, everything is as expected.
When you have fractional_reserve set to 100 (%), as soon as you create snapshots on that volume, ontap will reserve 100% of the Luns size within the volume, to gurantee writes to complete successfully.

The maths show:

820GB * 0,8 (for snap reserve) = 656 GB

320GB Lun * 2 (for fractional reserve) = 640 GB

P = 640 / (656*100) = 97,56 %

Think ontap is doing some rounding, so 98% is correct.

Regards

Jochen

From: owner-toasters@... [mailto:owner-toasters@...] On Behalf Of David.Ashton@...
Sent: Thursday, September 04, 2008 12:04 PM
To: toasters@...
Subject: Noob...

Hi, please excuse my noobness, I've recently inherited a Netapp system or 3, I'm fairly new to SANs in general and netapp in particular. This isnt my full time gig (storage), its one thing amongst the 2 thousand other things I'm working on today, but I allocate a fair amount of time to figuring this stuff out.

I'm struggling with something I'm sure all netapp storage people go through, I've read the manuals, I've played around for about 6 months on the filers and I cant answer this.

I have a FAS3020. I have a volume, lets call it vol_bond. Its 820GB, 20% snap reserve. It contains one lun, which is 320GB. The space guarantee is volume, and fractional reserve is 100.

Currently, there are 5 snapshots, totalling 8GB. It is snap mirrored to another filer. Snapshots are created nightly, there are no problems with that. At weekends, after various backup activity, these grow to about 80GB, but we only keep 5 and they're deleted.

Its all up and running, everythings fine.

Except for the filer status which reports: /vol/vol_bond is full (using or reserving 98% of space and 0% of inodes, using 49% of reserve) and the df -r output is

/vol/vol_bondv8/ 687865856 670681368 17184488 335194536 /vol/vol_bondv8/
/vol/vol_bondv8/.snapshot 171966464 14140040 157826424 0 /vol/vol_bondv8/.snapshot

What am I missing? I thought I had this thing nailed but obviously not.

Dave Ashton

**********************************************************************

The information contained in this e-mail and any attachments are intended for the named recipient(s) only. It may also be privileged and confidential. If you are not an intended recipient, you must take no action as a result of receiving it, including, but not limited to copying, distributing and amending it. If this communication has been sent to you in error, please contact us immediately and do not show the communication to any other party.

Rullion shall have no liability whatsoever in respect of the content of the communication and makes no warranty as to accuracy. Any views or opinions presented are solely those of the author.

Viruses:- Although we have taken steps to ensure that this e-mail and attachments are free from viruses, we advise that in keeping with good computing practice, the recipient should ensure they are actually virus free.

**********************************************************************

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

RE: R: Noob...

2008-09-04T07:28:08Z

Oh sure – I typically recommend to anyone who will listen that they always run their Oracle databases with an archive_log_dest that is either on a different volume, on the local machine, or ideally both. Do at least nightly manual snapshots with putting the database in hotbackup mode, etc., and then take scheduled snapshots. Depending on your transaction volume, it could actually be much faster to recover from a scheduled snapshot an hour ago with the database active, than to recover from the scheduled snapshot at midnight and run many hours of archive logs. But then I also recommend using DataGuard wherever possible in Oracle environments too. Much better to have to make a judgement call about which recovery strategy is optimal in a failure situation than to not have enough options.

Thanks,

Matt

From: Parisi, Justin [mailto:Justin.Parisi@...]
Sent: Thursday, September 04, 2008 10:21 AM
To: Matthew Zito; David.Ashton@...; Milazzo Giacomo
Cc: Willeke, Jochen; owner-toasters@...; toasters@...
Subject: RE: R: Noob...

Certainly.

The question is though, how important is it to you to restore quickly? :)

From: Matthew Zito [mailto:mzito@...]
Sent: Thursday, September 04, 2008 10:17 AM
To: Parisi, Justin; David.Ashton@...; Milazzo Giacomo
Cc: Willeke, Jochen; owner-toasters@...; toasters@...
Subject: RE: R: Noob...

Even if it is a database, scheduled snapshots can still be useful, though it’s better if the database is in hotbackup mode or whatever the non-Oracle equivalent is. A snapshot taken while the database is active is still valid, it’s just that recovering to it is like the database state after a server crashes – you have to do media recovery, etc., and some transactions may have to be rolled back. Things like archive logs, etc. are perfectly valid in these scenarios as well.

Thanks,

Matt

From: owner-toasters@... [mailto:owner-toasters@...] On Behalf Of Parisi, Justin
Sent: Thursday, September 04, 2008 9:52 AM
To: David.Ashton@...; Milazzo Giacomo
Cc: Willeke, Jochen; owner-toasters@...; toasters@...
Subject: RE: R: Noob...

David,

Keep in mind that snapshots will only grow if you delete files. So if your data incorporates a lot of deletes, then you need to take that into consideration.

If this is a database, you will want to quiesce the DB to snapshot it; if the data is simple text files, you can snap it on the fly using the volume snap schedules. Giacomo mentioned setting your snap sched to 0 0 0, but if you're not using Snapmanager or other 3rd party backups and this is not a database, you'll want to allow snapshots to take place on a schedule.

From: David.Ashton@... [mailto:David.Ashton@...]
Sent: Thursday, September 04, 2008 9:33 AM
To: Milazzo Giacomo
Cc: Willeke, Jochen; owner-toasters@...; toasters@...
Subject: Re: R: Noob...

thanks all for the excellent advice and pointers. I'll remove the snap reserve, I think the sizing is probably correct then.

The lun is mounted on a windows server that has snapdrive installed. The rate of change - varies from 3GB somedays to 80GB on others.
The server runs a legacy app that uses an enormous 3.6 million flat text files (220GB), and the number of open files is in the 10,000's at any one time so it gets a battering.

Dave

Rullion Management Services Ltd is a company registered in England and Wales with company number 2797732.

"Milazzo Giacomo" <G.Milazzo@...>
Sent by: owner-toasters@...

04/09/2008 14:06

To	"Willeke, Jochen" <Jochen.Willeke@...>, <David.Ashton@...>, <toasters@...>
cc
Subject	R: Noob...

A first answer came from Jochen and I’ve to add that if you have a volume that has to contain a LUN (that is, with NetApp, a file) the default snapshot reservation area of 20% (or less) must be removed, so the snap schedule.
In your case

Filer> snap reserve vol_bond 0
Filer> snap sched vol_bond 0 0 0

This in case you use some software of Snapmanager suite (You did not tell us the usage of that lun) or the snapmirror snapshots will be placed in the active file system area having the necessary free space. Never size a volume less that 2/2.5 time the size of the contained luns.

Bye

Da: owner-toasters@... [mailto:owner-toasters@...] Per conto di Willeke, Jochen
Inviato: giovedì 4 settembre 2008 12.54
A: David.Ashton@...; toasters@...
Oggetto: RE: Noob...

Hi David,

as far as i can see, everything is as expected.
When you have fractional_reserve set to 100 (%), as soon as you create snapshots on that volume, ontap will reserve 100% of the Luns size within the volume, to gurantee writes to complete successfully.

The maths show:

820GB * 0,8 (for snap reserve) = 656 GB

320GB Lun * 2 (for fractional reserve) = 640 GB

P = 640 / (656*100) = 97,56 %

Think ontap is doing some rounding, so 98% is correct.

Regards

Jochen

From: owner-toasters@... [mailto:owner-toasters@...] On Behalf Of David.Ashton@...
Sent: Thursday, September 04, 2008 12:04 PM
To: toasters@...
Subject: Noob...

Hi, please excuse my noobness, I've recently inherited a Netapp system or 3, I'm fairly new to SANs in general and netapp in particular. This isnt my full time gig (storage), its one thing amongst the 2 thousand other things I'm working on today, but I allocate a fair amount of time to figuring this stuff out.

I'm struggling with something I'm sure all netapp storage people go through, I've read the manuals, I've played around for about 6 months on the filers and I cant answer this.

I have a FAS3020. I have a volume, lets call it vol_bond. Its 820GB, 20% snap reserve. It contains one lun, which is 320GB. The space guarantee is volume, and fractional reserve is 100.

Currently, there are 5 snapshots, totalling 8GB. It is snap mirrored to another filer. Snapshots are created nightly, there are no problems with that. At weekends, after various backup activity, these grow to about 80GB, but we only keep 5 and they're deleted.

Its all up and running, everythings fine.

Except for the filer status which reports: /vol/vol_bond is full (using or reserving 98% of space and 0% of inodes, using 49% of reserve) and the df -r output is

/vol/vol_bondv8/ 687865856 670681368 17184488 335194536 /vol/vol_bondv8/
/vol/vol_bondv8/.snapshot 171966464 14140040 157826424 0 /vol/vol_bondv8/.snapshot

What am I missing? I thought I had this thing nailed but obviously not.

Dave Ashton

**********************************************************************

The information contained in this e-mail and any attachments are intended for the named recipient(s) only. It may also be privileged and confidential. If you are not an intended recipient, you must take no action as a result of receiving it, including, but not limited to copying, distributing and amending it. If this communication has been sent to you in error, please contact us immediately and do not show the communication to any other party.

Rullion shall have no liability whatsoever in respect of the content of the communication and makes no warranty as to accuracy. Any views or opinions presented are solely those of the author.

Viruses:- Although we have taken steps to ensure that this e-mail and attachments are free from viruses, we advise that in keeping with good computing practice, the recipient should ensure they are actually virus free.

**********************************************************************

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.