toasters

toasters@lists.teaparty.net

13514 discussions

NT And SQL with Network Appliance
by Gagnon, Steven (P.) 03 Jul '01

03 Jul '01

Hi Lori, Doug Wellbaum asked me to answer some concerns you may have. You may contact me personally if you have any more questions. We have 2 databases running on the filer on the SQL (ver. 6.5) end. Both of them are 500MB. Relatively small but effective. We have encountered no problem with the filer. I haven't used the filer yet in a disaster recovery plan, but I'm sure I would have no issue. Best practice is to use SnapShots or Snap Mirror for added protection. I would consider running your SQL backups (log files) just a few minutes before a snap shot occurs, then in case of disaster, you have to most up to date information and can get your database back on line within minutes. Create a separate ID for the filer and give it Admin privileges. Have it log on as a service. Do not use your Administrator account as if you change your password you will get suspect databases. -- This is from the trenches, things where you go, Ooops! when you are learning for the first time... Make sure it is on a different volume than your data storage. I have never experienced any down time with the filer. We have had it for over a year so far. It's a F740. We have two of them. The other serves UNIX and Oracle. Oracle embraces NetApp. Still wondering why Microsoft is so far behind the ball on this one??? It is as reliable as the hard disk you are using, with snap shot it becomes more reliable and faster than SCSI. As for service from NetApp. It is A1. I have never seen any other company with such dedicated people. You've have already experienced this, I'm sure... They were here late in the evening, early in the morning. Their telephone support is top notch. They will not let you go until your problem is solved, and their expertise is number one. I have 100GB for file storage. This works great too. You can call me if you have any other questions. Thanks Steven Steven Gagnon Visteon Canada Inc. Tel: (905) 475 8510 Ext. 4207 NT / SQL System Administrator Pager: (416) 753 3132 Markham, Ontario, Canada FordNet: 854-4207 Fax: (905) 470 3296 "Man's mind, once stretched by a new idea, never regains its original dimensions." -Oliver Wendell Holmes

1 0

RE: 34F+ & 36F impact on snapmirror
by Debbie.Lane＠intermec.com 03 Jul '01

03 Jul '01

The 36 GB BCS drive (34F+) is .5GB smaller than the 36GB ZCS (36F) drive. Sorry I can't help with the other questions. -----Original Message----- From: NicholosC(a)maxis.net.my [mailto:NicholosC@maxis.net.my] Sent: Thursday, June 21, 2001 9:19 PM To: toasters(a)mathworks.com Subject: 34F+ & 36F impact on snapmirror All, Had an original F740 with two full shelves of 36F disks. Added a new F740 (for snapmirror purpose) with the same configuration but it came with the new 34F+ disks. Configured the new filer with the identical volume configuration for snapmirror. Original filer was running 5.3.7r3 while the new filer is running 6.1r1 because of the requirement of 34F+ disks. My issues are: (1) Anybody has the information on the "right-size" of the 34F+ disk? My understanding is that 36F has 34,500 KB. The yellow flyer says that 34F+ has lesser capacity but that does not help very much, how much lesser? (2) Because of the lesser capacity (I guess), the target volume can not be snapmirrored. I have to rearrange the volume configuration making the target volumes by one disk more than the source volume, only after that the snapmirror went through. The intention of the snapmirror is for disaster recovery. In the event that the source filer is not available, the target filer will be changed from snapmirrored status to regular volume. When the original source filer is ready for operation again, what is the best practice to move the data back? (3) Snapmirror back on the reverse direction would not work because now the original source filer volume is smaller than the original target volume. (4) Would vol copy falls into the same restriction of target volume has to be equal or larger? In my case, they could not be equal because of one is using 36F and the other is using 34F+. Thanks in advanced for your comments/suggestions. Nic

1 0

RE: Snapmirror, Snapshots and DF output
by Brookes, Matt 03 Jul '01

03 Jul '01

Hi FPS France, :) You're probably experiencing bug 18560 http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=18560. The destination volume displays the default snap reserve of 20%. This is fixed in DataONTAP 6.0 and above, whereby the snap reserve set on the source volume is propagated to the destination. See NOW for current GA release - 6.0.1R3 at the time of writing. Regards, Matt. ________________________________________________________________ Matthew Brookes mailto:mbrookes@netapp.com Systems Engineer http://www.netapp.com Network Appliance Tel: +353 1 4064600 Unit 36, Rathfarnham Gate Fax: +353 1 4064601 Dublin 14, IRELAND Mob: +353 87 8575127 > -----Original Message----- > From: FPS France [mailto:fpsfrance@fps.fr] > Sent: 03 July 2001 17:10 > To: toasters(a)mathworks.com > Subject: Snapmirror, Snapshots and DF output > > > FPS France > > Hi, > > We had installed a snapmirror configuration with the following > particular trick : snap reserve volX 5 as the costumer would limit the > snapshot space consuption. > Now the snapmirror service works fine, the costumer > outlined something > strange in the DF output from each Filers. > Each Filer has a root volume mirrored on the other Filer. > As u can see > below, sources volumes are vol0 and mirrors volumes are mir_vol0. > From my calculation (less or more), I can check that for > vol0's volumes, > we had a snapshots reserved space around 5%, but in mir_vol0's we have > roughtly four times the snap space consuption more than the > source volume > (31.8 vs 7.9 and 15.6 vs 3.9 : 5% vs 20%). Before making those volumes > snapmirror destinations we took care to modify the snap > reserve to 5%. So > why do we got those outputs ? Any idea ? Any experience with > the df command > snap reserve 5 and snapmirror ? > All of this run on 5.3.7R3, F740. > > Netapp 1 : > << > ===== DF ===== > Filesystem kbytes used avail capacity > Mounted on > /vol/vol0/ 150937460 137664288 13273172 91% > /vol/vol0/ > /vol/vol0/.snapshot 7944076 1473572 6470504 19% > /vol/vol0/.snapshot > /vol/mir_vol0/ 62593232 155988 62437244 0% > /vol/mir_vol0/ > /vol/mir_vol0/.snapshot 15648304 510236 15138068 3% > /vol/mir_vol0/.snapshot > >> > > Netapp2 : > << > ===== DF ===== > Filesystem kbytes used avail capacity > Mounted on > /vol/vol0/ 74329460 155988 74173472 0% > /vol/vol0/ > /vol/vol0/.snapshot 3912076 510236 3401840 13% > /vol/vol0/.snapshot > /vol/mir_vol0/ 127105232 137664288 0 108% > /vol/mir_vol0/ > /vol/mir_vol0/.snapshot 31776304 1473572 30302732 5% > /vol/mir_vol0/.snapshot > >> >

1 0

36F disk
by Debbie.Lane＠intermec.com 03 Jul '01

03 Jul '01

Can a 36F Fibre Channel disk be used in a system that is not NetApp? I am asking because the decision to buy or lease was based on the belief that if at some point we wanted to discontinue using NetApp the disks could be used elsewhere. Thanks for your help. --Debbie

1 0

RE: Snapmirror, Snapshots and DF output
by Fox, Adam 03 Jul '01

03 Jul '01

2 things stand out in your message. 1. Reducing snap reserve does not contain snapshot usage. Snapshots will take up as much space as they need regardless of snap reserve size. What snap reserve does is contain the active file system blocks to a certain amount of space. This is an important concept in SnapShot planning. 2. It would be good to see the output of a snap reserve command from each filer. Something looks a little off. Becuase it seems that you adjusted the snap reserve AFTER the snap mirror occured because as I read it below, your sources are larger than your destinations and that is not possible with SnapMirror. 3. A sysconfig -r would also be useful just to match eveything up. While some volumes of different sizes work with SnapMirror, the simplest way to implement SnapMirror is to simply set up each source and destination the same way (if possible) so that it's easy to compare sizes properly. I realize that this isn't always possible, but if you have the opportunity to do it, it makes life easier. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > why do we got those outputs ? Any idea ? Any experience with > the df command > snap reserve 5 and snapmirror ? > All of this run on 5.3.7R3, F740. > > Netapp 1 : > << > ===== DF ===== > Filesystem kbytes used avail capacity > Mounted on > /vol/vol0/ 150937460 137664288 13273172 91% > /vol/vol0/ > /vol/vol0/.snapshot 7944076 1473572 6470504 19% > /vol/vol0/.snapshot > /vol/mir_vol0/ 62593232 155988 62437244 0% > /vol/mir_vol0/ > /vol/mir_vol0/.snapshot 15648304 510236 15138068 3% > /vol/mir_vol0/.snapshot > >> > > Netapp2 : > << > ===== DF ===== > Filesystem kbytes used avail capacity > Mounted on > /vol/vol0/ 74329460 155988 74173472 0% > /vol/vol0/ > /vol/vol0/.snapshot 3912076 510236 3401840 13% > /vol/vol0/.snapshot > /vol/mir_vol0/ 127105232 137664288 0 108% > /vol/mir_vol0/ > /vol/mir_vol0/.snapshot 31776304 1473572 30302732 5% > /vol/mir_vol0/.snapshot > >> >

1 0

Snapmirror, Snapshots and DF output
by FPS France 03 Jul '01

03 Jul '01

FPS France Hi, We had installed a snapmirror configuration with the following particular trick : snap reserve volX 5 as the costumer would limit the snapshot space consuption. Now the snapmirror service works fine, the costumer outlined something strange in the DF output from each Filers. Each Filer has a root volume mirrored on the other Filer. As u can see below, sources volumes are vol0 and mirrors volumes are mir_vol0. From my calculation (less or more), I can check that for vol0's volumes, we had a snapshots reserved space around 5%, but in mir_vol0's we have roughtly four times the snap space consuption more than the source volume (31.8 vs 7.9 and 15.6 vs 3.9 : 5% vs 20%). Before making those volumes snapmirror destinations we took care to modify the snap reserve to 5%. So why do we got those outputs ? Any idea ? Any experience with the df command snap reserve 5 and snapmirror ? All of this run on 5.3.7R3, F740. Netapp 1 : << ===== DF ===== Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 150937460 137664288 13273172 91% /vol/vol0/ /vol/vol0/.snapshot 7944076 1473572 6470504 19% /vol/vol0/.snapshot /vol/mir_vol0/ 62593232 155988 62437244 0% /vol/mir_vol0/ /vol/mir_vol0/.snapshot 15648304 510236 15138068 3% /vol/mir_vol0/.snapshot >> Netapp2 : << ===== DF ===== Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 74329460 155988 74173472 0% /vol/vol0/ /vol/vol0/.snapshot 3912076 510236 3401840 13% /vol/vol0/.snapshot /vol/mir_vol0/ 127105232 137664288 0 108% /vol/mir_vol0/ /vol/mir_vol0/.snapshot 31776304 1473572 30302732 5% /vol/mir_vol0/.snapshot >>

1 0

deleting a qtree
by Leonard, Roger 03 Jul '01

03 Jul '01

is there any way to delete a qtree? i typo'ed one and now want to remove it. thanks Roger D. Leonard

2 1

RE: Vol copy max speed ? alternatives ?
by Fox, Adam 02 Jul '01

02 Jul '01

> - so we used ndmp through tapes because we were not sure > enought of the > NdmpCopy reliability - may I find a tool to validate NdmpCopy > in our lab ? > :) > I've had this question asked before and my answer was simple. All the ndmpcopy does is call our native dump and restore programs on the filer (or filers if you are copying filer to filer). The host running ndmpcopy is not involved in the tranfer other than telling each host what to do, the data path is within the same filer or filer to filer. So if you trust our dump and restore commands, then you should trust ndmpcopy since underneath the covers they are the same thing. Don't misunderstand. The way you did it was fine. But if you were willing to trust dump and restore with tapes, you should be able to trust ndmpcopy since they are making the same calls. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com

1 0

RE: F85 Vs 740
by Tom "Mad Dog" Yergeau 02 Jul '01

02 Jul '01

Look at it this way. The F85 is a replacement for the F720. The F820 is a replacement for the F760. What's the replacement for the F740? I don't see one yet. So my guess is NetApp plans to keep the F740 around for a while. I'd go for it. It's a better box in a lot of ways than the F85 (NetApp-designed hardware compared to COTS hardware, clusterable, a tad more scalable, FC drives instead of SCSI drives, etc). Tom -----Original Message----- From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] Sent: Friday, June 29, 2001 11:05 AM To: toasters(a)mathworks.com Subject: Re: F85 Vs 740 The 740 is an older model and the F85 is brand new. Since the end of availability dates have already been announced for the 720 and 760, I would want to have some idea how much longer Netapp will support the 740 as compared to the F85. Bear in mind that the 700 series uses a DEC Alpha processor and the new 800 series and F85 are Intel. Soon the 740 will be the only Alpha based filer that Netapp still sells. On the other hand, if you need something fast, and it's not clear how soon you can get a F85, then a 740 might look more attractive, especially if you are getting a nice discount because of the F85 unavailability. > > I'm a NetApp newbie looking for feedback from experience users of these > boxes. > > I just ordered a F85, but because of non availability of F85's was offered a > 740 instead. > I'm not as concerned w/ scalability as I am w/ performance. > The data that it will host is under a 100GB now and should grow much beyond > 200GB. > The F85 that I ordered has 12 36GB drives which I figure will leave me w/ > ~280GB of usable space. > > There are 120 NT 4 workstations and a handful of UNIX boxes on this network. > The majority of the data will be CIFS, some NFS and HTTP. I plan on moving > all of the users home folders and shared data to the filer. > The connectivity of the servers and filer will be at 100Mb and the > workstations are at 10Mb. > > Any feedback would be appreciated. > > Mark > > Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

1 0

win2000 conections
by David C Baumgardner 02 Jul '01

02 Jul '01

Hello fellow toasters, I just got my first win2000 box. I have ten network drives connected to my NetApp. The CIFS sessions on the NetApp (5.3.6r2)is showing ten separate sessions. My NT4.0 boxes show only one connection with ten shares. Anyone know what is going on with the win2000 box? is this normal? David Baumgardner CAD/CAM Administrator Container Engineering 419.247.8274

1 0

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