toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

Use VTL shelfs with netapp head
by Joel.Cooper＠lvvwd.com 04 Jun '09

04 Jun '09

Hello, we are retiring our VTL 600 head and would like add the disk shelfs to our existing Netapp 3140. Does anyone know if this is possible or has maybe done something similar? Thanks

1 0

RE: HSM/ILM for Netapp
by John Stoffel 04 Jun '09

04 Jun '09

Glenn> Honestly, moving volumes between aggregates (and controllers) Glenn> is the only thing I'm really looking forward to out of ONTAP 8. Glenn> If all blocks are just virtual pointers now, it makes no sense Glenn> that we cannot move volumes between aggregates and it is a huge Glenn> issue for us today. Hmm... will you be able to move volumes live? I assume you'll need to have the free space in the destination aggr to hold the entire vol you're moving, but that should be ok then. Just keeping the data live and in production during such moves would be a huge help. Glenn> If they bump the limit beyond 32TB, I care less - most of our Glenn> volumes we keep rather small to assist with backup limitations Glenn> and/or reduction of single points of failure. Sure, I agree too. I might even start to use more volumes then, instead of qtrees within volumes. John

3 4

Re: HSM/ILM for Netapp
by Weeks, Roger 04 Jun '09

04 Jun '09

This is not the case. Upgrades to Data ONTAP 8.0 can be performed non-disruptively from 7.3 releases. If you have not yet upgraded to a 7.3 release you will need to follow the guidelines to non-disruptively upgrade to the latest 7.3 release before upgrading to 8.0. Roger Weeks Technical Marketing Engineer MultiStore Security HA NetApp 408.822.6365 Direct rweeks(a)netapp.com www.netapp.com > -----Original Message----- > From: Nick Silkey [mailto:silkey@ece.utexas.edu] > Sent: Tuesday, 02 June, 2009 12:52 > To: Page, Jeremy > Cc: James Beal; toasters(a)mathworks.com > Subject: Re: HSM/ILM for Netapp > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 6/2/09 1:34 PM, Page, Jeremy wrote: >> I thought they where planning to move to 100TB volumes in the very > near >> future (7.4?) > > DOT 8.0 is supposedly bringing WAFL improvements to allow for 100TB > aggrs/vols (rumored to be dropping this summer). > > I also hear jumping any 7.x variant to 8.0 will be a disruptive upgrade. > > Cheers. > > - -- > Nick Silkey > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (Darwin) > > iEYEARECAAYFAkolgtEACgkQrDQjhjXrMeK+cACgqJtAvcin5cpurMh1sNyIjJMF > Zh4AoI8kZw+DWA4Xvo5YrG0VgGN4orMH > =ERgH > -----END PGP SIGNATURE-----

3 2

FAS2050C questions (clustering)
by Ray Van Dolson 03 Jun '09

03 Jun '09

I'm the proud new owner of an IBM N3600 A20 (rebranded FAS2050C) with 20x30GB SAS disks. I'm trying to determine the best way to get this thing set up, and realized I have only a bit of a fuzzy understanding as to how the clustering or failover filer head should work. My initial thoughts were to aim for the following setup: - Set up all 20 disks in a RAID-DP aggregate with one spare (17 data, 2 parity and one spare, or maybe two spares). - Bond a NIC from the first controller with a NIC from the second controller to give us a 2Gbps connection to our "storage network". - Third and fourth NIC's would go to our regular network. My hope was that I could lose one filer head and the other would take over seamlessly. We'd lose half of our network bandwidth but still be up and running. However, it sounds like my understanding of how the clustering works might have been a bit flawed and that I actually need to treat the filer heads as two separate filers. So I may be forced to do something like the following: - Split my disks up between the two filers (7 data, 2 parity, one spare -- or maybe I can have one spare available to both heads). - Probably can't team NIC's from multiple filer heads meaning if I team the two NIC's on the filer I can no longer connect to my management network. I probably need to order more NIC's :( - If I lose one head, I lose one aggregate unless manual intervention is taken. - Each filer has a different hostname/IP for network access. This maybe gives me better performance, but at the expense of total disk space and flexibility if my understanding is correct. Maybe someone could help clear this up. It doesn't appear IBM has a RedBook on clustering... I'm searching around in NOW and have come across the Data ONTAP 7.3 Active/Active Configuration Guide which I am now reading. Is there something similar for Active/Passive setups (which seems to be more what I am after) or other documents that would be recommended reading? Any advice or best practices? This filer will be serving NFS to a pair of ESX servers. We plan to add a second shelf of disks later this year. Thanks in advance. No sales inquiries please. Ray

5 6

Re: FAS2050C questions (clustering)
by Ray Van Dolson 03 Jun '09

03 Jun '09

On Tue, Jun 02, 2009 at 09:26:17AM -0700, Steve Francis wrote: > You can get a performance boost by splitting it up. > Which is why I don't like to do that, in general, for performance > sensitive workloads. :-) > > Otherwise, in the event of a head failure, the surviving head may not > have the CPU/cache to deal with the extra work - even if both heads > are normally under 50% load. > Most workloads grow linearly - until they hit an elbow an don't grow linearly. > The only true way to be sure you have failover capacity is to run that > way all the time. > > Your mileage/budget/workload/performance requirements may vary. Thanks all. Great advice. So, my question is: if the second head can take over the personality of the failed head, why do I need to allocate any disks at all to the second head to begin with? Just a design thing? I'll probably do the even split thing.... and look into ordering additional NIC's. Can I have a "spare" that is available to either aggregate on either filer? This way I could do two RAID-DP's on each head with one common "spare" disk and rely on 4hr support to get me replacement disks quickly. Ray

3 3

HSM/ILM for Netapp
by Babar Haq 03 Jun '09

03 Jun '09

Hi all, IHAC who is searching for a product that can provide HSM/ILM function for massive NAS environment. This product can be either a hardware appliance, a software, or combination of both that can provide a total transparent solution for our user (i.e. regardless where is the physical data location, user can remain using it old logical path to access the same data) with tiered storage. So far I can only identify two products one hardware Acopia and the other one is software approach CommVault. Both have it pros and cons but the biggest challenges for both products are not able to manage snapshot and do not go down to qtree level. Thanks in advance. Regards, Babar Haq -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com

9 9

Re: HSM/ILM for Netapp
by John Stoffel 02 Jun '09

02 Jun '09

John> You don't want to backup through the acopia, since it's a big John> bottleneck, so you backup the Filers directly. But then you need to John> manage and track *where* your files really are stored, and that John> becomes a nightmare to deal with. Kyle> The latest version of the F5/Acopia software (v5.0.0) introduces Kyle> a feature called File Tracking to specifically address this Kyle> issue. This doesn't help when you do NDMP backups, does it? Also, do you *ever* trust version X.0 software? *grin* I'm not moving to CommVault 8.x or OnTap 7.3.x until they're more stable and widely tested. I need stability at work. John

1 0

ESX volume design question
by steve klise 02 Jun '09

02 Jun '09

What would you do? ESX 3.5 running all windows servers; FCP with all fiber drives We have an existing 6030 with 1 aggr, 1 large volume with ~5 LUNS 500GB a piece; running DOT 7.24. (upgrading soon, so no dedupe running yet). We have a new HA 6040 (PAM cards) =). The existing volume on the 6030 is still at 100 percent fractional reserve. We have SMVI running in our test environment, but not in prod yet. We wanted to snapmirror from the 6030 to the 6040 and visa versa. The 6040 is running 7.3.1.1 so I can only go from the 6030 to the 6040 for now. No vmware on the 6040 yet. Question: I have 3 shelves each for each head (6 300gb total for the 6040) and 1 big aggr on the 6030, 11.5TB agr 4.97used in the volume on the 6030. I was thinking of having the volumes for the 6040 @ 750GB and 1 LUN. I am averaging ~20 windows boxes. I figured when SMVI runs, it is only 1 snapmirror update vs running the job with allt he LUNS in 1 big aggr and multiple snapmirrors happening. I will make the fractional reserve set to 50% on the 6040 with thin provisioning at the LUN level, and dedupe. Pros: I think its more granular. Having to find a location for 6TB is a bit difficult Con: Not as much dedupe by having all VM's in 1 volume. Thoughts, experiences, gotchas.? -- View this message in context: http://www.nabble.com/ESX-volume-design-question-tp23821864p23821864.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

6 6

How are you using SnapDrive + iSCSI HBAs on a separated storage LAN ?
by Filip Sneppe 29 May '09

29 May '09

Hi, I am struggling to get the following setup to work properly: - A separated storage IP subnet, not routed to the LAN - A multihomed NetApp filer with an IP address on both the storage IP subnet and the LAN - A Windows 2003 server with a normal NIC on the LAN and an iSCSI HBA on the storage subnet. - The iSCSI HBA is a dual Qlogic HBA, but only one of them is connected, the other one is left unconfigured. I don't intend to use MPIO. - The setups I've worked on lately have all been boot-from-SAN setups, but I don't know if that's really relevant to the problem. Now, presenting LUNs and using them on the server (or even booting from them) has not been much of a problem, no issues there. The problem arises when I want to use SnapDrive for LUN management tasks such as snapshotting. From the docs I've read, what I gather is that I have to install the MS iSCSI initiator even when using iSCSI HBAs: https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb8988 (this doc is not 100% clear to me: should I only select the iSCSI service during the installation, or also the MS iSCSI initiator itself ? What is the impact of selecting the MS iSCSI MPIO ?) I also make sure to change the initiator name on the HBA to the iSCSI initiator name used by the MS iSCSI initiator: https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb21672 The end result is that my LUNs are accessible from the HBA. However, when opening the Computer Management MMC and going to the disks managed by SnapDrive, no disks are shown and the SnapDrive service is logging that filer IP address a.b.c.d is dead, as described in this article: https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb30762 This article talks about fixing up domain credentials and name resolution, but from a network routing point of view, I can see where this error is coming from: the Windows server is not aware of the HBA connected to the storage segment and cannot reach it via its normal NIC, so it reports a dead filer IP address. Now, the quick fix would be to add the necessary routes to/from the storage IP network, but that would mean that this network is no longer fully isolated from the rest of the network, whcih I would very much like to avoid. What really drives me mad is that I have a setup at a customer site described as above that works perfectly fine (ie. SnapDrive shows the LUNs in the MMC and SMSQL can create snapshots & backups), yet I have another customer site where SnapDrive is unable to do anything because it cannot find the LUNs. Just today I was at a customer site with a setup as described above, where SnapDrive was able to work with the LUNs. They hadn't installed the host utilities, so I did the following: - Installed a MS hotfix required by the host utils - Installed the host utils - uninstalled a version of SMSQL and installed version 2.1.2 After a server reboot: boom, SnapDrive doesn't see ane LUNs any more, so no way to take any snapshots any more of these LUNs. So that's two out of three setups that are not working. I fiddled around a little with things: ie. installed the MS iSCSI MPIO, reinstallled the host utils (5.1) with MPIO support, etc. At one point, I had uninstalled the host utils & SMSQL, and then reinstalled the MS iSCSI initiator and SnapDrive, and I saw the LUNs again using MMC. I reboot one last time to make sure everything's fine, and ... bang ... no more visible LUNs from SnapDrive. So at this point I would like to know: - Has anyone had similar experiences ? - If you are using iSCSI HBAs on a separated storage network, what is your magic formula to get things working correctly ? Should I be able to get this thing to work without adding a route to the storage network ? Thanks in advance for your suggestions ! Best regards, Filip

2 3

lun resize of FCP vmware lun
by Linux Admin 22 May '09

22 May '09

Can I do lun resize of live vmware lun? What are the steps in Vmware (just rescan?) any consideration?

2 1

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