toasters

toasters@lists.teaparty.net

13514 discussions

RE: OnTap 7 and Samba
by Ryan Kather 03 Aug '05

03 Aug '05

Hello Mark, > Did you open a case with Netapp on the failure to access ntfs-style > shares using NFS? We have many customers doing that successfully. We did not open a case for NFS, but we did for the CIFS and Samba issues. I will open a ticket for NFS with NTFS Security mode. I am wondering if it would just be easier to run Mixed mode though. I can't really identify a downside to mixed mode. The open ticket for CIFS and Samba issues has been responded to. A NetApp support agent said that mount -t cifs issues could be a bug in OnTap 7, and they will begin evaluating our findings in a testing lab. As far as mount -t smbfs (Samba), the official line is that Samba is not supported and I will have to inquire with the Samba mailing list (which I have done). Of course Samba pins the issue back at NetApp. So is there an unofficial line I can try ;). While I have your attention, is there a way to insure that files copied via NFS will retain the same rights as their Windows CIFS accessed counterparts (perhaps this lies more in the realm of NFS 4 instead of 3). > Mark Thanks for your help Mark. > -----Original Message----- > From: Ryan Kather [mailto:rkather@missionpenguin.com] > Sent: Wednesday, August 03, 2005 7:09 AM > To: Alan McLachlan > Cc: toasters(a)mathworks.com > Subject: RE: OnTap 7 and Samba > > Hello Alan, > >> Hi Ryan, >> >> Just curious - if you have an NFS licence on your filer, why are you >> even bothering to mount a CIFS share rather than an NFS v3 export? > > We ran Mixed Security mode on OnTap 6.5, but upon NetApp's > recommendation > we moved to NTFS security mode. With NTFS security mode I am unable to > map to NFS exports (permission denied error). NetApp has also informed > us > that in NTFS, or Mixed Mode security, NFS does not maintain a complete > copy of filesystem rights. > > We are archiving these filers with RSYNC, and it is necessary that we > preserve the filesystem rights. > >> It just seems you are putting yourself through unnecessary trouble. > With >> Secureshare user mapping even SACL's for auditing will still work > fine, >> i.e. NFS reads and writes will still be logged as if they were CIFS >> accesses. > > I agree. I would much rather use NFS. I am not familiar with > SecureShare. Is this a way to view the NetApp windows users as Unix > UID/GID users? If so, this seems the optimal approach. Of course with > NTFS security mode I still cannot mount to NFS exports. Do you know of > a > way to do this, or would I have to convert to Mixed Mode? > >> If your Linux box is a server running an application with data stored > on >> the filer, an NFS hard mount (with intr) is much more efficient than a >> CIFS share - so much so that a few years back I was using the >> Hummingbird NFS client on Windows 2000 IIS servers rather than use > CIFS >> to support a web farm. >> >> If you set up a dedicated gigabit segment (multi-home both the filer > and >> the app servers) with jumbo frames (large MTU's), you can get as much > as >> 60MB/sec over NFS. That's with 9K MTU's so an 8K NFS transfer is one >> ethernet packet. Best I have seen on CIFS even with jumbo is 35MB/sec. >> >> (that's MegaBytes, not Megabits). > > That is a huge difference. NFS seems a much more elegant solution. I > am > still confused why I can't use CIFS or SMBFS though against the filer, > when they work fine against Windows Domain shares (from Windows Server > 2003). > > Thanks for your help, and I would be interested in any more information > you have on this topic. > > Regards, > Ryan > > >> >> regards, >> >> Alan McLachlan >> Technical Services Manager >> ComputerCORP ACT >> >> Tel: (02) 6242 3305 Mobile: 0428 655644 >> Fax: (02) 6255 6333 >> E-mail: Alan.McLachlan(a)computercorp.com.au >> Web: www.computercorp.com.au >> >> >> LEGAL INFORMATION: This e-mail may contain information which is >> confidential to ComputerCORP. If you have received this e-mail by >> mistake, please advise us by return e-mail and delete it and any >> attachments from your system. You may not disclose, copy or rely on > any >> part of this e-mail >> >> -----Original Message----- >> From: Ryan Kather [mailto:rkather@missionpenguin.com] >> Sent: Tuesday, 2 August 2005 10:09 PM >> To: toasters(a)mathworks.com >> Subject: OnTap 7 and Samba >> >> Greetings, >> >> I am having some difficulties accessing our filers with OnTap 7 via >> Linux. >> Perhaps someone in this list could point me in the right direction. >> >> The version of Linux is Open Enterprise Server (minimal install) which >> makes it functionally equivalent to SuSE Linux Enterprise Server 9 > SP1. >> It is running Kernel 2.6.5-155-smp and Samba 3.0.14a (originally 3.0.9 >> but >> updated when issues surfaced). >> >> The filers I have tried accessing consist of FAS270s and a R200. They >> are >> using FlexVols and OnTap 7. Data shares are available via CIFS and > NFS >> and are configured with NTFS Security Mode. The filers are members of >> an >> Active Directory Domain (Windows Server 2003 PDC). >> >> I have a number of odd issues that have surfaced. >> >> Issue 1; >> -------- >> smbmount returns permission denied and odd path presentation. >> >> The Linux box is a member of the active directory domain. I can use >> wbinfo to list domain users and groups, as well as getent passwd and >> group. I am able to authenticate via kerberos, and can use smbmount >> against Windows server shares fine. >> >> However, when I attempt to mount a share on a NetApp filer using mount >> -t >> smbfs -o username=someuser,workgroup=THEDOMAIN //NETAPP/SHARE > /mnt/SHARE >> the operation appears to complete successfully. If I enter mount I > can >> see the /mnt/SHARE as active. If I travese into the /mnt/SHARE folder >> and >> type ls I get a permission denied error. Syslog shows kernel: >> smb_lookup: >> find /// failed, error=-13. After some digging it appears that >> error=-13 >> is an EACCESS authentication issue. So I assumed I did not have >> permissions. >> >> If I type ls -alFG from the /mnt folder in Linux there is no > /mnt/SHARE >> directory. If I type ls there is one, and if I unmount /mnt/SHARE > then >> type ls -alFG the directory is there. >> >> In further troubleshooting I can browse the share from Windows, and > from >> the same Linux workstation smbclient //NETAPP/SHARE -U someuser -W >> THEDOMAIN allows me to browse succesfully. >> >> Issue 2; >> -------- >> /bin/ls: reading directory .: Cannot allocate memory >> >> If I mount the same share via cifs (mount -t cifs -o >> user=someuser,domain=THEDOMAIN //NETAPP/SHARE /mnt/SHARE) the > operation >> completes with no error. If I cd into /mnt/SHARE then type ls I get > the >> error above (/bin/ls: reading directory .: Cannot allocate memory). > If >> I >> continue to type ls it will eventually display the directory. If I cd >> into a subfolder the error returns. >> >> Both of these operations work fine against a Windows 2003 Server > share. >> Does anyone have any ideas? The messages file on the filer itself > does >> not provide any significant error messages. >> >> Thank you very much for any information anyone can provide. >> >> Linux Config Files; >> -------------- >> smb.conf-- >> >> [global] >> workgroup = THEDOMAIN >> realm = THEDOMAIN.COM >> idmap uid = 10000-20000 >> idmap gid = 10000-20000 >> security = ADS >> netbios name = LINUXBOX >> password server = PDC.THEDOMAIN.COM >> encrypt passwords = yes >> log level = 5 >> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 >> wins server = 10.0.0.1 10.0.0.2 >> name resolve order = wins lmhosts hosts bcast >> winbind enum users = yes >> winbind enum groups = yes >> winbind use default domain = yes >> >> krb5.conf-- >> >> [libdefaults] >> default_realm = THEDOMAIN.COM >> >> [realms] >> THEDOMAIN.COM = { >> kdc = pdc.thedomain.com >> } >> >> [domain_realm] >> .thedomain.com = THEDOMAIN.COM >> >> [logging] >> default = SYSLOG:NOTICE:DAEMON >> kdc = FILE:/var/log/kdc.log >> kadmind = FILE:/var/log/kadmind.log >> >> [appdefaults] >> pam = { >> ticket_lifetime = 1d >> renew_lifetime = 1d >> forwardable = true >> proxiable = false >> retain_after_close = false >> minimum_uid = 0 >> debug = false >> } >> >> >> >> >> >> >

1 0

RE: EOA gear
by Harold White 03 Aug '05

03 Aug '05

Standard Disclaimer: I am not employed nor do I have any affiliation with Union Computers Exchange, Inc. besides being a satisfied customer looking to get a cheaper parts for my old filer (F760). I get parts for my system (an old F760) for 2+ years with Union Computers Exchange. Contact info: ------------- Scott Fischmann Union Computer Exchange, Inc. 6233 Idylwood Lane Minneapolis, Minnesota 55436 phone: (952) 935-7282 | fax: (952) 935-5056 email: scott(a)unioncomputer.com -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Lai, Derek Sent: Wednesday, August 03, 2005 2:07 PM To: toasters(a)mathworks.com Subject: EOA gear Our parent company has a old netapp (F840) that they are lending to us for a 2-month critical project. Unfortunately the machine is out of maintenance. It has old X219F, X221D, X225B, X233A and X234B drives. I saw on NOW that these are all pretty much EOA drives. X219F is even End of Hardware Support. Does that mean basically you can't get them from NetApp at all? For the other drives, we are checking to see if we can get support for them. Although for 2 month, maybe we are better off just purchasing them from support? Is that something that we can readily do? What kind of turn-around can we expect? Anyone else been through this before? Derek

1 0

EOA gear
by Lai, Derek 03 Aug '05

03 Aug '05

Our parent company has a old netapp (F840) that they are lending to us for a 2-month critical project. Unfortunately the machine is out of maintenance. It has old X219F, X221D, X225B, X233A and X234B drives. I saw on NOW that these are all pretty much EOA drives. X219F is even End of Hardware Support. Does that mean basically you can't get them from NetApp at all? For the other drives, we are checking to see if we can get support for them. Although for 2 month, maybe we are better off just purchasing them from support? Is that something that we can readily do? What kind of turn-around can we expect? Anyone else been through this before? Derek

1 0

RE: OnTap 7 and Samba
by Ryan Kather 03 Aug '05

03 Aug '05

Hello Alan, > Hi Ryan, > > Just curious - if you have an NFS licence on your filer, why are you > even bothering to mount a CIFS share rather than an NFS v3 export? We ran Mixed Security mode on OnTap 6.5, but upon NetApp's recommendation we moved to NTFS security mode. With NTFS security mode I am unable to map to NFS exports (permission denied error). NetApp has also informed us that in NTFS, or Mixed Mode security, NFS does not maintain a complete copy of filesystem rights. We are archiving these filers with RSYNC, and it is necessary that we preserve the filesystem rights. > It just seems you are putting yourself through unnecessary trouble. With > Secureshare user mapping even SACL's for auditing will still work fine, > i.e. NFS reads and writes will still be logged as if they were CIFS > accesses. I agree. I would much rather use NFS. I am not familiar with SecureShare. Is this a way to view the NetApp windows users as Unix UID/GID users? If so, this seems the optimal approach. Of course with NTFS security mode I still cannot mount to NFS exports. Do you know of a way to do this, or would I have to convert to Mixed Mode? > If your Linux box is a server running an application with data stored on > the filer, an NFS hard mount (with intr) is much more efficient than a > CIFS share - so much so that a few years back I was using the > Hummingbird NFS client on Windows 2000 IIS servers rather than use CIFS > to support a web farm. > > If you set up a dedicated gigabit segment (multi-home both the filer and > the app servers) with jumbo frames (large MTU's), you can get as much as > 60MB/sec over NFS. That's with 9K MTU's so an 8K NFS transfer is one > ethernet packet. Best I have seen on CIFS even with jumbo is 35MB/sec. > > (that's MegaBytes, not Megabits). That is a huge difference. NFS seems a much more elegant solution. I am still confused why I can't use CIFS or SMBFS though against the filer, when they work fine against Windows Domain shares (from Windows Server 2003). Thanks for your help, and I would be interested in any more information you have on this topic. Regards, Ryan > > regards, > > Alan McLachlan > Technical Services Manager > ComputerCORP ACT > > Tel: (02) 6242 3305 Mobile: 0428 655644 > Fax: (02) 6255 6333 > E-mail: Alan.McLachlan(a)computercorp.com.au > Web: www.computercorp.com.au > > > LEGAL INFORMATION: This e-mail may contain information which is > confidential to ComputerCORP. If you have received this e-mail by > mistake, please advise us by return e-mail and delete it and any > attachments from your system. You may not disclose, copy or rely on any > part of this e-mail > > -----Original Message----- > From: Ryan Kather [mailto:rkather@missionpenguin.com] > Sent: Tuesday, 2 August 2005 10:09 PM > To: toasters(a)mathworks.com > Subject: OnTap 7 and Samba > > Greetings, > > I am having some difficulties accessing our filers with OnTap 7 via > Linux. > Perhaps someone in this list could point me in the right direction. > > The version of Linux is Open Enterprise Server (minimal install) which > makes it functionally equivalent to SuSE Linux Enterprise Server 9 SP1. > It is running Kernel 2.6.5-155-smp and Samba 3.0.14a (originally 3.0.9 > but > updated when issues surfaced). > > The filers I have tried accessing consist of FAS270s and a R200. They > are > using FlexVols and OnTap 7. Data shares are available via CIFS and NFS > and are configured with NTFS Security Mode. The filers are members of > an > Active Directory Domain (Windows Server 2003 PDC). > > I have a number of odd issues that have surfaced. > > Issue 1; > -------- > smbmount returns permission denied and odd path presentation. > > The Linux box is a member of the active directory domain. I can use > wbinfo to list domain users and groups, as well as getent passwd and > group. I am able to authenticate via kerberos, and can use smbmount > against Windows server shares fine. > > However, when I attempt to mount a share on a NetApp filer using mount > -t > smbfs -o username=someuser,workgroup=THEDOMAIN //NETAPP/SHARE /mnt/SHARE > the operation appears to complete successfully. If I enter mount I can > see the /mnt/SHARE as active. If I travese into the /mnt/SHARE folder > and > type ls I get a permission denied error. Syslog shows kernel: > smb_lookup: > find /// failed, error=-13. After some digging it appears that > error=-13 > is an EACCESS authentication issue. So I assumed I did not have > permissions. > > If I type ls -alFG from the /mnt folder in Linux there is no /mnt/SHARE > directory. If I type ls there is one, and if I unmount /mnt/SHARE then > type ls -alFG the directory is there. > > In further troubleshooting I can browse the share from Windows, and from > the same Linux workstation smbclient //NETAPP/SHARE -U someuser -W > THEDOMAIN allows me to browse succesfully. > > Issue 2; > -------- > /bin/ls: reading directory .: Cannot allocate memory > > If I mount the same share via cifs (mount -t cifs -o > user=someuser,domain=THEDOMAIN //NETAPP/SHARE /mnt/SHARE) the operation > completes with no error. If I cd into /mnt/SHARE then type ls I get the > error above (/bin/ls: reading directory .: Cannot allocate memory). If > I > continue to type ls it will eventually display the directory. If I cd > into a subfolder the error returns. > > Both of these operations work fine against a Windows 2003 Server share. > Does anyone have any ideas? The messages file on the filer itself does > not provide any significant error messages. > > Thank you very much for any information anyone can provide. > > Linux Config Files; > -------------- > smb.conf-- > > [global] > workgroup = THEDOMAIN > realm = THEDOMAIN.COM > idmap uid = 10000-20000 > idmap gid = 10000-20000 > security = ADS > netbios name = LINUXBOX > password server = PDC.THEDOMAIN.COM > encrypt passwords = yes > log level = 5 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > wins server = 10.0.0.1 10.0.0.2 > name resolve order = wins lmhosts hosts bcast > winbind enum users = yes > winbind enum groups = yes > winbind use default domain = yes > > krb5.conf-- > > [libdefaults] > default_realm = THEDOMAIN.COM > > [realms] > THEDOMAIN.COM = { > kdc = pdc.thedomain.com > } > > [domain_realm] > .thedomain.com = THEDOMAIN.COM > > [logging] > default = SYSLOG:NOTICE:DAEMON > kdc = FILE:/var/log/kdc.log > kadmind = FILE:/var/log/kadmind.log > > [appdefaults] > pam = { > ticket_lifetime = 1d > renew_lifetime = 1d > forwardable = true > proxiable = false > retain_after_close = false > minimum_uid = 0 > debug = false > } > > > > > >

1 0

RE: NDS and ONTAP
by Alan McLachlan 02 Aug '05

02 Aug '05

Fernan, See here: http://www.netapp.com/tech_library/3343.html Of particular interest is the statement: "LDAP on the filers is designed to map user credentials to UNIX® UID/GID pairs for NFS via the RFC2307 schema extensions and does not apply to the CIFS authentication and authorization process. Thus, it is not possible as of this writing to directly integrate the filer into eDirectory environments using LDAP alone." For older versions of Netware you have a few options: 1) Install a Windows PC as a domain controller and synchronise it using either the Novell or Microsoft directory synchronization tools. Then integrate the filer with the Windows domain. Your workstations will require the Microsoft networking redirector re-enabled if it was disabled during the Netware client installation. There are issues with this approach that mean that users should do any password changes at end of day (sync lag preventing logon for a period after password change). 2) Use a Netware server as a gateway - you can do NFS mounts from the filer to the Netware box which then servers the data to the workstations. However, the problem with this is that you're not gaining the wide sharing I/O capability of the NetApp box (workstation I/O will be bottlenecked at the Netware server). 3) Mount iSCSI volumes from the filer on the Netware box. Again like option 2, you are limited to the I/O capability of the Netware server. You need a Netware iSCSI initiator for this to work (I don't know if this is available for 5.11, it is for 6.x versions) The directory sync option is the only way to gain the server consolidation and performance benefits of the NetApp box, but it's messy to configure and maintain. If you are planning to upgrade to Netware 6.5 SP2, then you can use the Windows DC emulation as described in the URL above and life is good. regards, Alan McLachlan Technical Services Manager ComputerCORP ACT Tel: (02) 6242 3305 Mobile: 0428 655644 Fax: (02) 6255 6333 E-mail: Alan.McLachlan(a)computercorp.com.au Web: www.computercorp.com.au LEGAL INFORMATION: This e-mail may contain information which is confidential to ComputerCORP. If you have received this e-mail by mistake, please advise us by return e-mail and delete it and any attachments from your system. You may not disclose, copy or rely on any part of this e-mail -----Original Message----- From: Fernán Orjuela [mailto:fernan.orjuela@intek.com.co] Sent: Wednesday, 3 August 2005 1:14 AM To: 'NetApp Toasters List' Subject: NDS and ONTAP I need connect the Filer with ONTAP 7.0.1 to Novell 5.1 NDS LDAP database. How to identify the ldap.base, ldap.passwd, ldap......... in Novell and how to use the accounts in Novell NDS for assign permissions to shares from filerview. Cordialmente Fernán Orjuela Carvajal

1 0

Temperature sensor on Shelf
by devnull＠adc.idt.com 02 Aug '05

02 Aug '05

I have a misbehaving temperature sensor on my one of my shelves which is causing the shelf to claim to be at 53 C and then drop down to 26C every other minute. All of this activity generates a lot of autosupport emails. Anyone got any ideas on 1. How to disable this temperature probe fow now 2. Does the filer shut off if the temperature hits some number. This probe is generating faults every minute, and I dont want to shut autosupport off completely, but even at minimal, this generates about 100K. Annoying. Any suggestions will be appreciated.

3 3

TKO Notice: ***Urgent Safeharbor Department Notice***
by aw-confirm＠eBay.com 02 Aug '05

02 Aug '05

1 0

RE: Temperature sensor on Shelf
by David Dalby 29 Jul '05

29 Jul '05

Hi, I think you may find the units shut down at 50C .... I have seen this in a computer room where the AC failed and everything cooked .... System rebooted after an internal halt. Fri Jul 4 09:41:30 WST [monitor.shutdown.overTemp:EMERGENCY]: Emergency shutdown: System too hot! Emergency Shutdown: System too hot: sensor Temp_Unit_B Fri Jul 4 09:41:30 WST [monitor.shutdown.overTemp:EMERGENCY]: Emergency shutdown: System too hot! current temperature is 50 C, critical high is 50 C Fri Jul 4 09:41:30 WST [statd:warning]: Fri Jul 4 09:41:30 WST [monitor.shutdown.overTemp:EMERGENCY]: Emergency shutdown: System too hot! OVER_TEMPERATURE_SHUTDOWN !!! See the following ..... Bug Detail Bug ID 43776 Title False "Emergency shutdown: System too hot" message Duplicate of Bug Severity 3 - Serious inconvenience Bug Status Closed Product Data ONTAP Bug Type Unknown Description Formatted Filer reports an "Emergency shutdown: System too hot" message when the motherboard temperature sensor records above the high critical limit. In this condition, the filer will automatically halt to the ok prompt. Workaround Formatted If the ambient temperature indeed is above the maximum operating range for the filer, then this warning message is valid. Check the input airflow for any possible blockage, and turn off the filer until the ambient temperature is well within the recommended operating temperature range (<30 degrees Celsius). A typical output for the temperature sensors using the motherboard diagnostic environmental test is: --System temperatures (C): TempA=25, tempB=25, tempC=25 --System high limits (C): TempA=50, tempB=50, tempC=50 Environmental check ............... PASSED If the ambient temperature is much lower than 40 degrees Celsius, then use the motherboard diagnostic environmental test to confirm that all three system temperatures are reading within 3-4 degrees Celsius for a properly operating motherboard. If one of the sensors is measuring much more than the other two, replace the motherboard. Notes Formatted Related Solutions Fixed-In Version This bug is not scheduled to be fixed, you may opt to open a technical support case if you would like to contact Network Appliance regarding the status of this bug. A complete list of releases where this bug is fixed is available here. Related Bugs Bug Watch Status This bug is unwatchable. ************************************************************************ **************************** -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Barry Robison Sent: Friday, 29 July 2005 12:01 PM To: devnull(a)adc.idt.com Cc: NetApp Toasters List Subject: Re: Temperature sensor on Shelf devnull(a)adc.idt.com wrote: > I have a misbehaving temperature sensor on my one of my shelves which > is causing the shelf to claim to be at 53 C and then drop down to 26C > every other minute. All of this activity generates a lot of > autosupport emails. > > Anyone got any ideas on > > 1. How to disable this temperature probe fow now in DFM you can increase Environmental Monitoring Interval to something quite high... > > 2. Does the filer shut off if the temperature hits some number. no they don't. We looked into this for a filer we ahve in a self contained A/C rack. You have to script something up to power down the Filer head in overheat situations. hope this helps!

1 0

AW: Temperature sensor on Shelf
by Beckers, André, VIS 29 Jul '05

29 Jul '05

Do you have ESH-Modules in your shelfs??? We had a similar problem with one. It showed suddenly no temperature. Only way to fix it was to exchange it. You have to make a RMA. -----Ursprüngliche Nachricht----- Von: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von devnull(a)adc.idt.com Gesendet: Freitag, 29. Juli 2005 06:29 An: Barry Robison Cc: NetApp Toasters List Betreff: Re: Temperature sensor on Shelf >> 1. How to disable this temperature probe fow now > in DFM you can increase > > Environmental Monitoring Interval > > to something quite high... Dont have DFM, need to look into an alternative. >> >> 2. Does the filer shut off if the temperature hits some number. > > no they don't. We looked into this for a filer we ahve in a self > contained A/C rack. You have to script something up to power down the > Filer head in overheat situations. Luckily I dont have an overheating problem as of now. Just an errant probe.

1 0

RE: Traditional Volumes to Flex Volumes
by George, Andrew 28 Jul '05

28 Jul '05

OK...I'm probably being thick but why didn't snapmirror work for you? I havn't done a flexvol migration yet but for normal migration were using either snapmirror or ndmpcopy depending on what seemed best at the time. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of drew.odonnell(a)americas.bnpparibas.com Sent: Wednesday, 27 July 2005 8:32 AM To: toasters(a)mathworks.com Subject: Re: Traditional Volumes to Flex Volumes If all of your data is in qtrees, you can snapmirror from a traditional volume to a flexvol no prob. You can set up a cascade for a production swap fairly easily with this model. Snapmirror will not work if your data is not in a qtree. NDMP copy will work as well, but you have to do the whole volume at once which may or may not be desirable, or you may want to migrate slowly, or separate data etc.. Drew Internet bryer(a)sfu.ca To: steve.pitts cc: toasters Sent by: bcc: owner-toasters(a)mathworks.com Subject: Re: Traditional Volumes to Flex Volumes 07/26/2005 05:53 PM We've always used SnapMirror for our data migration needs. But when we talked to our NetApp rep about planning our migration from traditional volumes to flex vols he recommended ndmpcopy (SnapMirror wouldn't work for us). We used ndmpcopy to migrate from a FAS250 with traditional volumes to a FAS270 with flex vols. Worked beautifully. Next month I'll be doing the same thing to migrate from an F820 to a FAS3020. Level 0 ndmcopy to lay down the base, level 1 to copy the week's changes and then shutdown the necessary services and a final level 2 to pick up the last of the changes. That should minimize our downtime. On Tue, Jul 26, 2005 at 09:47:03PM +0200, Steve Pitts wrote: > I am looking to get a feel for what people think is the best way to > copy traditional volumes to flex volumes when I upgrade to 7G. > Currently I SnapMirror my 960C production volumes and qtrees to a > local R150 and a coop > R150 located several hundred miles away. I know I need to update the > R150 before upgrading the 960C. > On my R150 I should have enough space to build a large aggregate to > put multiple flex volumes in. I will be able to delete a couple of the > traditional volumes to free up more disk once copied into the flex volume. > I am leaning toward using ndmpcopy to copy the traditional copies to flex > volumes. I'm not sure what performance/speed I will get out of using ndmp. I > am open to suggestions if anyone has a better way of doing this. > Thanks, > Steve Pitts > General Dynamics -- Jeff Bryer bryer(a)sfu.ca Systems Administrator (604) 291-4935 Academic Computing, Simon Fraser University This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

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