toasters

toasters@lists.teaparty.net

13531 discussions

Start a nNew thread

Windows 2000 and DataONTap 5.3.4
by Blake Folgner 22 Oct '01

22 Oct '01

Is DataONTap 5.3.4.r3 compatible with Windows 2000?

1 0

RE: Veritas Netbackup Database
by ilya.birman＠abnamro.com 22 Oct '01

22 Oct '01

Manny, I could not try the disaster recovery. I did move the /usr/openv/netbackup/db to the NFS mounted file system. I am not backing this up with NDMP. I just use regular "catalog backups" to the tape. When you configure regular Solaris Backup class in NetBAckup, there is an option "Follow NFS". There is no option like that for catalog backups. I wonder if the catalog backups truly work. VEritas could not answer this question, their advice was to recover. I can not afford to fail and recover the DB right now, it is something on my list. Ilya "Manny Kaiser" To: Ilya Birman/US/ABNAMRO/NL@ABNAMRO <mkaiser@mmcn cc: "toasters@mathworks. com" <toasters(a)mathworks.com> et.com> Subject: RE: Veritas Netbackup Database 10/19/2001 01:07 PM Hi, did you test the ability to recover this database? Just to make sure I understand - /usr/openv/netbackup/db is an NFS mounted file system? Did you do a disaster recovery test to see that you can recover the database and then restore files from the database? What is the size of your database? Does the database reside on a Netapp - if so did you attempt to also backup the database using NDMP? I would assume that this won't work well since on the one hand the database changes as the backup progresses, on the other hand, NDMP is backing up a snapshot which will not contain the information of this backup. Manny -----Original Message----- From: ilya.birman(a)abnamro.com [mailto:ilya.birman@abnamro.com] Sent: Friday, October 19, 2001 7:25 PM To: Manny Kaiser Cc: toasters@mathworks. com Subject: Re: Veritas Netbackup Database We did that. Veritas did not tell us not to do it. We have a enormous amount of data do backup so we had to migrate the NteBackup DB of local disk. So for no problem. The concern we had is that on normal backup you can direct Veritas to "Follow NFS". There is no such option on NetBackup Catalog backups. We were concern if the catalog will be backed up properly. As far as NFS not being reliable, I think that battle had been fought many years ago. Ilya "Manny Kaiser" <mkaiser(a)mmcnet.co To: "toasters@mathworks. com" <toasters(a)mathworks.com> m> cc: Sent by: Subject: Veritas Netbackup Database owner-toasters@mat hworks.com 10/19/2001 10:03 AM Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

1 0

RE: DLT 7000 question
by Bokkelkamp Ernst SBS ITS ORS AHS 241 20 Oct '01

20 Oct '01

Hallo Rahul, the problem is that the 40/80GB label on the tape package is purely marketing based on the DLT8000 drive. What counts is the type of drive and the compressability of the data. In your case the DLT IV tape is marketed as 35/70GB. Without compression 35 and with 2:1 compression 70 GB. But the compression depends on the data, which means you can have more or less. My experience with the data I back up is about 55 GB compressed, but I have already written 120 GB to one tape. For more information you should read (or download) the DLT Hanbook from www.dlttape.com, this book explains almost everything you would like to know about the current DLT tape drives and cartridges. Bye Ernie -----Original Message----- From: Rahul Kumar [mailto:Rahul.Kumar@sdrc.com] Sent: Samstag, 20. Oktober 2001 05:49 Cc: toasters@mathworks. com Subject: DLT 7000 question Hi All, Can anyone tell me how to enable the compression on DLT7000 tapedrive attached to F740. I use a 40/80GB tape on the filer tape drive. The drive make is tandenberg . I usually see the drive compression led on. Is there any special option in dump command to reflect the compression.... right now i back up around 45 gb data.. but the dlt is asking to insert the second tape. the command which i issue to backup entire volume is (45gb---vol0) dump 0ufb rst0a 63 /vol/vol0 Rahul -----Original Message----- From: Manny Kaiser [mailto:mkaiser@mmcnet.com] Sent: Saturday, October 20, 2001 1:37 AM To: ilya.birman(a)abnamro.com Cc: toasters@mathworks. com Subject: RE: Veritas Netbackup Database Hi, did you test the ability to recover this database? Just to make sure I understand - /usr/openv/netbackup/db is an NFS mounted file system? Did you do a disaster recovery test to see that you can recover the database and then restore files from the database? What is the size of your database? Does the database reside on a Netapp - if so did you attempt to also backup the database using NDMP? I would assume that this won't work well since on the one hand the database changes as the backup progresses, on the other hand, NDMP is backing up a snapshot which will not contain the information of this backup. Manny -----Original Message----- From: ilya.birman(a)abnamro.com [mailto:ilya.birman@abnamro.com] Sent: Friday, October 19, 2001 7:25 PM To: Manny Kaiser Cc: toasters@mathworks. com Subject: Re: Veritas Netbackup Database We did that. Veritas did not tell us not to do it. We have a enormous amount of data do backup so we had to migrate the NteBackup DB of local disk. So for no problem. The concern we had is that on normal backup you can direct Veritas to "Follow NFS". There is no such option on NetBackup Catalog backups. We were concern if the catalog will be backed up properly. As far as NFS not being reliable, I think that battle had been fought many years ago. Ilya "Manny Kaiser" <mkaiser(a)mmcnet.co To: "toasters@mathworks. com" <toasters(a)mathworks.com> m> cc: Sent by: Subject: Veritas Netbackup Database owner-toasters@mat hworks.com 10/19/2001 10:03 AM Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

1 0

DLT 7000 question
by Rahul Kumar 20 Oct '01

20 Oct '01

Hi All, Can anyone tell me how to enable the compression on DLT7000 tapedrive attached to F740. I use a 40/80GB tape on the filer tape drive. The drive make is tandenberg . I usually see the drive compression led on. Is there any special option in dump command to reflect the compression.... right now i back up around 45 gb data.. but the dlt is asking to insert the second tape. the command which i issue to backup entire volume is (45gb---vol0) dump 0ufb rst0a 63 /vol/vol0 Rahul -----Original Message----- From: Manny Kaiser [mailto:mkaiser@mmcnet.com] Sent: Saturday, October 20, 2001 1:37 AM To: ilya.birman(a)abnamro.com Cc: toasters@mathworks. com Subject: RE: Veritas Netbackup Database Hi, did you test the ability to recover this database? Just to make sure I understand - /usr/openv/netbackup/db is an NFS mounted file system? Did you do a disaster recovery test to see that you can recover the database and then restore files from the database? What is the size of your database? Does the database reside on a Netapp - if so did you attempt to also backup the database using NDMP? I would assume that this won't work well since on the one hand the database changes as the backup progresses, on the other hand, NDMP is backing up a snapshot which will not contain the information of this backup. Manny -----Original Message----- From: ilya.birman(a)abnamro.com [mailto:ilya.birman@abnamro.com] Sent: Friday, October 19, 2001 7:25 PM To: Manny Kaiser Cc: toasters@mathworks. com Subject: Re: Veritas Netbackup Database We did that. Veritas did not tell us not to do it. We have a enormous amount of data do backup so we had to migrate the NteBackup DB of local disk. So for no problem. The concern we had is that on normal backup you can direct Veritas to "Follow NFS". There is no such option on NetBackup Catalog backups. We were concern if the catalog will be backed up properly. As far as NFS not being reliable, I think that battle had been fought many years ago. Ilya "Manny Kaiser" <mkaiser(a)mmcnet.co To: "toasters@mathworks. com" <toasters(a)mathworks.com> m> cc: Sent by: Subject: Veritas Netbackup Database owner-toasters@mat hworks.com 10/19/2001 10:03 AM Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

1 0

Re: Veritas Netbackup Database
by ilya.birman＠abnamro.com 19 Oct '01

19 Oct '01

We did that. Veritas did not tell us not to do it. We have a enormous amount of data do backup so we had to migrate the NteBackup DB of local disk. So for no problem. The concern we had is that on normal backup you can direct Veritas to "Follow NFS". There is no such option on NetBackup Catalog backups. We were concern if the catalog will be backed up properly. As far as NFS not being reliable, I think that battle had been fought many years ago. Ilya "Manny Kaiser" <mkaiser(a)mmcnet.co To: "toasters@mathworks. com" <toasters(a)mathworks.com> m> cc: Sent by: Subject: Veritas Netbackup Database owner-toasters@mat hworks.com 10/19/2001 10:03 AM Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

2 1

RE: Netapp hardware
by McCarthy, Tim 19 Oct '01

19 Oct '01

You can add 36s and 18s in the same volume. If you add them to the same RAID group, the *first* 36GB disk becomes the parity(needed for the extra stripes) and the 18GB parity becomes a data drive(they flip roles). However, it is in my opinion, better to just simply make a new RAID group with the 36GB disks. They will be taken fully advantage of (i.e. they will be 36GB disks). However, if your current volume is a Zoned Checksum volume, and you add the new 36GB(34F) disks, you will lose the benefits of the BCS disks and they will work like Zoned checksum disks. Chances are your current 18GB disks do not have the little yellow labels and are ZCS. So you may want to create a new volume with the 36GB disks unless they are BCS disks already. This is perfectly legal, it has been being done for a long time now. (mixing drives of varying sizes). The one thing to remember, the largest disk in the RAID group is *always* the parity disk, unless of course they are all the same size in the RAID group. --tmac Timothy A. McCarthy System Engineer Network Appliance Federal Systems INC. http://www.netapp.com <http://www.netapp.com> 410-290-1581 Office Page Me at: 877-5-NETAPP --> -----Original Message----- --> From: White, Lance [mailto:Lance.White@netapp.com] --> Sent: Friday, October 19, 2001 2:34 PM --> To: 'Viper Rinspeed'; toasters(a)mathworks.com --> Subject: RE: Netapp hardware --> --> --> 1)Yes...but you won't want to do this for an extended --> period as you'll only be using half of the 36GB as a spare --> if an 18GB drive fails. Hence, when you get your --> replacement 18GB drive, simply replace the failed 18GB --> drive (new drive will show up as a spare), then MANUALLY --> fail the 36GB drive so that the 18GB reclaims the role, and --> 36GB goes back into the spares pool. --> 2) Same issue as above...the 36GB drives will essentially --> become 18GB drives. Rather wasteful. You CAN do this, but --> you probably won't want to. --> 3) Not a performance or reliability issue...more of a --> "digital waste" issue. --> --> -----Original Message----- --> From: Viper Rinspeed [mailto:debian22@yahoo.fr] --> Sent: Friday, October 19, 2001 11:19 AM --> To: toasters(a)mathworks.com --> Subject: Netapp hardware --> --> --> Hi, --> --> We have a Netapp 740 with a FC9 shelf (18Gb disks). --> We are planning to get a DS14 shelf with 36Gb disks. --> I have two questions: --> 1- Can we use only one spare disk (36Gb disk) instead of two --> (1 18Gb and 1 36Gb)? Will the spare 36Gb disk be used correctly --> to replace a failed 18Gb disk ? --> 2- Can I mix 18Gb and 36Gb disks in the same volume (same RAID)? --> If yes, how the data will be written? Let's say, I have --> 2x18G+2x36Gb (+parity). --> Will the 36Gb disks stored twice more data than the 18Gb ? --> Is there a performance issue ? a reliability issue (more --> data written-> more --> risk of failure?) ? --> --> Thank you very much. --> --> Jn --> --> --> ___________________________________________________________ --> Un nouveau Nokia Game commence. --> Allez sur http://fr.yahoo.com/nokiagame avant le 3 novembre --> pour participer à cette aventure tous médias. -->

1 0

RE: "unrecognized error 0xb" -- correct slot for tape scsi?
by Toal, Dave 19 Oct '01

19 Oct '01

Steve, Unstable scsi bus, ok, thanks for the info. The dlt was originally on the filer's motherboard scsi; but now all combinations of cable, dlt, and filer I've tried are returning that error. 2 dlt's, 2 740's, mobo and pci scsi on both, 3 cables... no common bus in the tape library, it's all direct scsi. The dlt was checked first, but I asked netapp support to close the case when I discovered both 740's saw the same error. Time for another go-round with StorageTek, it looks like. Dave -----Original Message----- From: Parsons, Steve To: 'Toal, Dave'; toasters(a)mathworks.com Sent: 10/19/01 11:27 AM Subject: RE: "unrecognized error 0xb" -- correct slot for tape scsi? Dave, Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) The numbers in parentheses are SCSI status, ASC, and ASCQ, respectively. According to the SCSI spec, the drive is aborting the command (b) because it detected SCSI PARITY ERROR (47,0). It denotes an unstable SCSI bus, and could be caused by the adapter, the cable, the tape drive, or termitator. (The "unrecognized" is just a hint from the filer that it wasn't one of the errors that the filer would attempt to recover from on its own.) Steve -----Original Message----- From: Toal, Dave [mailto:dave.toal@t-t.com] Sent: Thursday, October 18, 2001 7:58 PM To: toasters(a)mathworks.com Subject: "unrecognized error 0xb" -- correct slot for tape scsi? Folks, I've been trying to get an F740 filer to recognize a dlt for several weeks. The error it returns is below. This same error also happens on another filer, also a 740. DLT checks out ok, according to the StorageTek tech's dignostics box. Have tried swapping cables, and using different dlt's -- _always_ this "unrecognized error". The filer has been rebooted many times during this process. mt fsf, bsf, weof, &c all work ok, according to mt status, but all tape writes fail. -- Dave Toal unix person T&T, nq, MA statler> dump u0f nrst0a /vol/spool DUMP: Dumping tape file 1 on nrst0a DUMP: creating "/vol/spool/../snapshot_for_backup.0" snapshot. DUMP: Using Full Volume Dump DUMP: Date of this level 0 dump: Fri Oct 19 02:02:52 2001. DUMP: Date of last level 0 dump: the epoch. DUMP: Dumping /vol/spool/ to nrst0a DUMP: mapping (Pass I)[regular files] DUMP: mapping (Pass II)[directories] Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) DUMP: Tape write failed. Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0) unrecognized error 0xbunrecognized error 0xb. DUMP: DUMP IS ABORTED DUMP: Deleting "/vol/spool/../snapshot_for_backup.0" snapshot. statler>

1 0

RE: Netapp hardware
by White, Lance 19 Oct '01

19 Oct '01

1)Yes...but you won't want to do this for an extended period as you'll only be using half of the 36GB as a spare if an 18GB drive fails. Hence, when you get your replacement 18GB drive, simply replace the failed 18GB drive (new drive will show up as a spare), then MANUALLY fail the 36GB drive so that the 18GB reclaims the role, and 36GB goes back into the spares pool. 2) Same issue as above...the 36GB drives will essentially become 18GB drives. Rather wasteful. You CAN do this, but you probably won't want to. 3) Not a performance or reliability issue...more of a "digital waste" issue. -----Original Message----- From: Viper Rinspeed [mailto:debian22@yahoo.fr] Sent: Friday, October 19, 2001 11:19 AM To: toasters(a)mathworks.com Subject: Netapp hardware Hi, We have a Netapp 740 with a FC9 shelf (18Gb disks). We are planning to get a DS14 shelf with 36Gb disks. I have two questions: 1- Can we use only one spare disk (36Gb disk) instead of two (1 18Gb and 1 36Gb)? Will the spare 36Gb disk be used correctly to replace a failed 18Gb disk ? 2- Can I mix 18Gb and 36Gb disks in the same volume (same RAID)? If yes, how the data will be written? Let's say, I have 2x18G+2x36Gb (+parity). Will the 36Gb disks stored twice more data than the 18Gb ? Is there a performance issue ? a reliability issue (more data written-> more risk of failure?) ? Thank you very much. Jn ___________________________________________________________ Un nouveau Nokia Game commence. Allez sur http://fr.yahoo.com/nokiagame avant le 3 novembre pour participer à cette aventure tous médias.

1 0

Netapp hardware
by Viper Rinspeed 19 Oct '01

19 Oct '01

Hi, We have a Netapp 740 with a FC9 shelf (18Gb disks). We are planning to get a DS14 shelf with 36Gb disks. I have two questions: 1- Can we use only one spare disk (36Gb disk) instead of two (1 18Gb and 1 36Gb)? Will the spare 36Gb disk be used correctly to replace a failed 18Gb disk ? 2- Can I mix 18Gb and 36Gb disks in the same volume (same RAID)? If yes, how the data will be written? Let's say, I have 2x18G+2x36Gb (+parity). Will the 36Gb disks stored twice more data than the 18Gb ? Is there a performance issue ? a reliability issue (more data written-> more risk of failure?) ? Thank you very much. Jn ___________________________________________________________ Un nouveau Nokia Game commence. Allez sur http://fr.yahoo.com/nokiagame avant le 3 novembre pour participer à cette aventure tous médias.

1 0

RE: Veritas Netbackup Database
by Hubbard, Dan 19 Oct '01

19 Oct '01

Thats funny because I was just told by Veritas that this is a decent way of backing up ? Of course NDMP will be faster, but with the Solaris Vertias client / NFS its much cheaper (ie: no NDMP license needed). -----Original Message----- From: Manny Kaiser [mailto:mkaiser@mmcnet.com] Sent: Friday, October 19, 2001 10:03 AM To: toasters@mathworks. com Subject: Veritas Netbackup Database Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

1 0

Veritas Netbackup Database
by Manny Kaiser 19 Oct '01

19 Oct '01

Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

2 1

RE: "unrecognized error 0xb" -- correct slot for tape scsi?
by Parsons, Steve 19 Oct '01

19 Oct '01

Dave, Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) The numbers in parentheses are SCSI status, ASC, and ASCQ, respectively. According to the SCSI spec, the drive is aborting the command (b) because it detected SCSI PARITY ERROR (47,0). It denotes an unstable SCSI bus, and could be caused by the adapter, the cable, the tape drive, or termitator. (The "unrecognized" is just a hint from the filer that it wasn't one of the errors that the filer would attempt to recover from on its own.) Steve -----Original Message----- From: Toal, Dave [mailto:dave.toal@t-t.com] Sent: Thursday, October 18, 2001 7:58 PM To: toasters(a)mathworks.com Subject: "unrecognized error 0xb" -- correct slot for tape scsi? Folks, I've been trying to get an F740 filer to recognize a dlt for several weeks. The error it returns is below. This same error also happens on another filer, also a 740. DLT checks out ok, according to the StorageTek tech's dignostics box. Have tried swapping cables, and using different dlt's -- _always_ this "unrecognized error". The filer has been rebooted many times during this process. mt fsf, bsf, weof, &c all work ok, according to mt status, but all tape writes fail. -- Dave Toal unix person T&T, nq, MA statler> dump u0f nrst0a /vol/spool DUMP: Dumping tape file 1 on nrst0a DUMP: creating "/vol/spool/../snapshot_for_backup.0" snapshot. DUMP: Using Full Volume Dump DUMP: Date of this level 0 dump: Fri Oct 19 02:02:52 2001. DUMP: Date of last level 0 dump: the epoch. DUMP: Dumping /vol/spool/ to nrst0a DUMP: mapping (Pass I)[regular files] DUMP: mapping (Pass II)[directories] Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) DUMP: Tape write failed. Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0) unrecognized error 0xbunrecognized error 0xb. DUMP: DUMP IS ABORTED DUMP: Deleting "/vol/spool/../snapshot_for_backup.0" snapshot. statler>

1 0

RE: Good experience with Netapp & exchange
by Joe Luchtenberg 19 Oct '01

19 Oct '01

I was just about to note that. One futher point -- SnapManager 2.0 supports Exch2K but not with SP2. Joe -----Original Message----- From: Jay Newton [mailto:jnewton@chkenergy.com] Sent: Friday, October 19, 2001 11:16 AM To: Joe Luchtenberg Cc: 'toasters(a)mathworks.com' Subject: RE: Good experience with Netapp & exchange I was incorrect on the E2k SnapManager. I just checked the NOW site and there is a version for E2k in case anyone needs that version. -----Original Message----- From: Joe Luchtenberg [mailto:joe.luchtenberg@data-line.com] Sent: Friday, October 19, 2001 9:58 AM To: 'Jay Newton' Subject: RE: Good experience with Netapp & exchange Just curious, what is your particular configuration? Exchange 5.5 or 2K? SnapManager 1.1 or 2.0? If 2.0, what has been your experience with NetApp Drive? TIA. Joe Joe Luchtenberg Dataline, Inc. 757-858-0600 757-285-1223 (mobile) 757-858-0606 (fax) joe.luchtenberg(a)data-line.com www.data-line.com -----Original Message----- From: Jay Newton [mailto:jnewton@chkenergy.com] Sent: Friday, October 19, 2001 10:32 AM To: 'toasters(a)mathworks.com' Subject: RE: Good experience with Netapp & exchange I just finished migrating a 43 gig InfoStore to our 840 Filer. I created a new Exchange server and added it to the site. I then moved the new databases to the Filer and set up all the Snapshot stuff with SnapManager for Exchange. I then migrated all 679 mailboxes to the new server on the Filer and voila! 99% of the user population did not notice the difference. Address books and calendars pop up a little quicker as well. I then back up the Snapshot once a day to our tape library using CommVault Galaxy which has incredible Exchange support. There are a couple of really important things to remember when doing this. First, you really need a private network of 100 megabit or better for the Exchange server to talk to the Filer. You don't want to share traffic with everyone else. Use a crossover cable and use the IP in the path just to be 100% certain traffic is on the private network. Next, buy a copy of SnapManager for Exchange. It makes the whole thing work more smoothly. Finally, make sure you have another server attached to that private network to run Snap verifies. Snap verifies make sure the Snapshot you just took is consistent and restorable. You can Snap an Exchange database and defer verification until later and on another machine. That gives you about a 15 second window where performance marginally degrades every time you do a Snapshot. Our experience is 1 gig per minute doing a verify. Ours were taking 45 minutes and was slowing down the server pretty drastically. By moving to another server on the private network, we only incur the 15 second penalty instead of the 45 minute one. Not only does this run great, but test restores I have done to another server are incredibly fast. It takes longer to install the OS and Exchange than it does to restore the database! There was no data loss and logs rolled forward. -----Original Message----- From: netapp netappliance [ mailto:netapp@mail.be <mailto:netapp@mail.be> ] Sent: Friday, October 19, 2001 8:43 AM To: toasters(a)mathworks.com Subject: Good experience with Netapp & exchange I'm looking for good experience of migrating exchange to netapp ? ----------------------------------------------------- Mail.be, Free WebMail and Virtual Office http://www.mail.be <http://www.mail.be>

1 0

RE: Good experience with Netapp & exchange
by Jay Newton 19 Oct '01

19 Oct '01

I was incorrect on the E2k SnapManager. I just checked the NOW site and there is a version for E2k in case anyone needs that version. -----Original Message----- From: Joe Luchtenberg [mailto:joe.luchtenberg@data-line.com] Sent: Friday, October 19, 2001 9:58 AM To: 'Jay Newton' Subject: RE: Good experience with Netapp & exchange Just curious, what is your particular configuration? Exchange 5.5 or 2K? SnapManager 1.1 or 2.0? If 2.0, what has been your experience with NetApp Drive? TIA. Joe Joe Luchtenberg Dataline, Inc. 757-858-0600 757-285-1223 (mobile) 757-858-0606 (fax) joe.luchtenberg(a)data-line.com www.data-line.com -----Original Message----- From: Jay Newton [mailto:jnewton@chkenergy.com] Sent: Friday, October 19, 2001 10:32 AM To: 'toasters(a)mathworks.com' Subject: RE: Good experience with Netapp & exchange I just finished migrating a 43 gig InfoStore to our 840 Filer. I created a new Exchange server and added it to the site. I then moved the new databases to the Filer and set up all the Snapshot stuff with SnapManager for Exchange. I then migrated all 679 mailboxes to the new server on the Filer and voila! 99% of the user population did not notice the difference. Address books and calendars pop up a little quicker as well. I then back up the Snapshot once a day to our tape library using CommVault Galaxy which has incredible Exchange support. There are a couple of really important things to remember when doing this. First, you really need a private network of 100 megabit or better for the Exchange server to talk to the Filer. You don't want to share traffic with everyone else. Use a crossover cable and use the IP in the path just to be 100% certain traffic is on the private network. Next, buy a copy of SnapManager for Exchange. It makes the whole thing work more smoothly. Finally, make sure you have another server attached to that private network to run Snap verifies. Snap verifies make sure the Snapshot you just took is consistent and restorable. You can Snap an Exchange database and defer verification until later and on another machine. That gives you about a 15 second window where performance marginally degrades every time you do a Snapshot. Our experience is 1 gig per minute doing a verify. Ours were taking 45 minutes and was slowing down the server pretty drastically. By moving to another server on the private network, we only incur the 15 second penalty instead of the 45 minute one. Not only does this run great, but test restores I have done to another server are incredibly fast. It takes longer to install the OS and Exchange than it does to restore the database! There was no data loss and logs rolled forward. -----Original Message----- From: netapp netappliance [ mailto:netapp@mail.be <mailto:netapp@mail.be> ] Sent: Friday, October 19, 2001 8:43 AM To: toasters(a)mathworks.com Subject: Good experience with Netapp & exchange I'm looking for good experience of migrating exchange to netapp ? ----------------------------------------------------- Mail.be, Free WebMail and Virtual Office http://www.mail.be <http://www.mail.be>

1 0

RE: Good experience with Netapp & exchange
by Jay Newton 19 Oct '01

19 Oct '01

I'm running Exchange 5.5 with SP4. E2k isn't supported until SnapManager for Exchange v2.0 comes out Real Soon Now(tm). I'm running 1.1 which has NetApp Drive in it. It's a little clunky but works just fine. Our Exchange site consists of 2 Exchange 5.5 SP4 servers. One server houses all mailboxes and is attached to the Filer. The other houses all connectors like Zetafax and the IMS and is not using the Filer. The server with no mailboxes does all the verifies for the other server. Nobody ever notices when Snapshots take place. I run 2 snapshots a day. Once at noon and again at 8:00pm. I've noticed that the server with all the mailboxes doesn't have to work as hard anymore. I rarely see drive activity and the processors are rarely above 10%. It's performance is better now than it's ever been. -----Original Message----- From: Joe Luchtenberg [mailto:joe.luchtenberg@data-line.com] Sent: Friday, October 19, 2001 9:58 AM To: 'Jay Newton' Subject: RE: Good experience with Netapp & exchange Just curious, what is your particular configuration? Exchange 5.5 or 2K? SnapManager 1.1 or 2.0? If 2.0, what has been your experience with NetApp Drive? TIA. Joe Joe Luchtenberg Dataline, Inc. 757-858-0600 757-285-1223 (mobile) 757-858-0606 (fax) joe.luchtenberg(a)data-line.com www.data-line.com -----Original Message----- From: Jay Newton [mailto:jnewton@chkenergy.com] Sent: Friday, October 19, 2001 10:32 AM To: 'toasters(a)mathworks.com' Subject: RE: Good experience with Netapp & exchange I just finished migrating a 43 gig InfoStore to our 840 Filer. I created a new Exchange server and added it to the site. I then moved the new databases to the Filer and set up all the Snapshot stuff with SnapManager for Exchange. I then migrated all 679 mailboxes to the new server on the Filer and voila! 99% of the user population did not notice the difference. Address books and calendars pop up a little quicker as well. I then back up the Snapshot once a day to our tape library using CommVault Galaxy which has incredible Exchange support. There are a couple of really important things to remember when doing this. First, you really need a private network of 100 megabit or better for the Exchange server to talk to the Filer. You don't want to share traffic with everyone else. Use a crossover cable and use the IP in the path just to be 100% certain traffic is on the private network. Next, buy a copy of SnapManager for Exchange. It makes the whole thing work more smoothly. Finally, make sure you have another server attached to that private network to run Snap verifies. Snap verifies make sure the Snapshot you just took is consistent and restorable. You can Snap an Exchange database and defer verification until later and on another machine. That gives you about a 15 second window where performance marginally degrades every time you do a Snapshot. Our experience is 1 gig per minute doing a verify. Ours were taking 45 minutes and was slowing down the server pretty drastically. By moving to another server on the private network, we only incur the 15 second penalty instead of the 45 minute one. Not only does this run great, but test restores I have done to another server are incredibly fast. It takes longer to install the OS and Exchange than it does to restore the database! There was no data loss and logs rolled forward. -----Original Message----- From: netapp netappliance [ mailto:netapp@mail.be <mailto:netapp@mail.be> ] Sent: Friday, October 19, 2001 8:43 AM To: toasters(a)mathworks.com Subject: Good experience with Netapp & exchange I'm looking for good experience of migrating exchange to netapp ? ----------------------------------------------------- Mail.be, Free WebMail and Virtual Office http://www.mail.be <http://www.mail.be>

1 0

RE: which disk
by Mike Sphar 19 Oct '01

19 Oct '01

Seriously though, if I thought that Netapp hardware was the kind of thing that would "go up in a puff of smoke" from something as simple as an incorrect disk drive, I never would have let it in my server room in the first place. These are well-built robust machines. In my experience, they're not going to go tits up over something as basic as that. I can't envision anything bad happening worse than the disk just not being used. This isn't like a plain old scsi bus where connecting a device incorrectly can short the whole bus out (I've scene a couple of sparcstations die that way). These things are designed to be hot-swappable. If the disk is for some reason the wrong size or manufacturer or type, it will a) probably not even fit in the shelf, or b) just not get recognized by the filer. If there's some great risk of plugging in an unknown disk, I'd like to hear about it. -- Mike Sphar - Sr Systems Administrator - Engineering Support Peregrine Systems, Inc. -----Original Message----- From: Jim Harm [mailto:jharm@llnl.gov] Sent: Thursday, October 18, 2001 4:27 PM To: toasters(a)mathworks.com Subject: RE: which disk Thanks, I will. ... not. Your users love you! > > >Or, the whole filer might go up in a big puff of smoke. Try it and let us >know! >

2 1

RE: Good experience with Netapp & exchange
by Jay Newton 19 Oct '01

19 Oct '01

I just finished migrating a 43 gig InfoStore to our 840 Filer. I created a new Exchange server and added it to the site. I then moved the new databases to the Filer and set up all the Snapshot stuff with SnapManager for Exchange. I then migrated all 679 mailboxes to the new server on the Filer and voila! 99% of the user population did not notice the difference. Address books and calendars pop up a little quicker as well. I then back up the Snapshot once a day to our tape library using CommVault Galaxy which has incredible Exchange support. There are a couple of really important things to remember when doing this. First, you really need a private network of 100 megabit or better for the Exchange server to talk to the Filer. You don't want to share traffic with everyone else. Use a crossover cable and use the IP in the path just to be 100% certain traffic is on the private network. Next, buy a copy of SnapManager for Exchange. It makes the whole thing work more smoothly. Finally, make sure you have another server attached to that private network to run Snap verifies. Snap verifies make sure the Snapshot you just took is consistent and restorable. You can Snap an Exchange database and defer verification until later and on another machine. That gives you about a 15 second window where performance marginally degrades every time you do a Snapshot. Our experience is 1 gig per minute doing a verify. Ours were taking 45 minutes and was slowing down the server pretty drastically. By moving to another server on the private network, we only incur the 15 second penalty instead of the 45 minute one. Not only does this run great, but test restores I have done to another server are incredibly fast. It takes longer to install the OS and Exchange than it does to restore the database! There was no data loss and logs rolled forward. -----Original Message----- From: netapp netappliance [mailto:netapp@mail.be] Sent: Friday, October 19, 2001 8:43 AM To: toasters(a)mathworks.com Subject: Good experience with Netapp & exchange I'm looking for good experience of migrating exchange to netapp ? ----------------------------------------------------- Mail.be, Free WebMail and Virtual Office http://www.mail.be

1 0

Good experience with Netapp & exchange
by netapp netappliance 19 Oct '01

19 Oct '01

I'm looking for good experience of migrating exchange to netapp ? ----------------------------------------------------- Mail.be, Free WebMail and Virtual Office http://www.mail.be

1 0

"unrecognized error 0xb" -- correct slot for tape scsi?
by Toal, Dave 19 Oct '01

19 Oct '01

Folks, I've been trying to get an F740 filer to recognize a dlt for several weeks. The error it returns is below. This same error also happens on another filer, also a 740. DLT checks out ok, according to the StorageTek tech's dignostics box. Have tried swapping cables, and using different dlt's -- _always_ this "unrecognized error". The filer has been rebooted many times during this process. mt fsf, bsf, weof, &c all work ok, according to mt status, but all tape writes fail. -- Dave Toal unix person T&T, nq, MA statler> dump u0f nrst0a /vol/spool DUMP: Dumping tape file 1 on nrst0a DUMP: creating "/vol/spool/../snapshot_for_backup.0" snapshot. DUMP: Using Full Volume Dump DUMP: Date of this level 0 dump: Fri Oct 19 02:02:52 2001. DUMP: Date of last level 0 dump: the epoch. DUMP: Dumping /vol/spool/ to nrst0a DUMP: mapping (Pass I)[regular files] DUMP: mapping (Pass II)[directories] Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) DUMP: Tape write failed. Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0) unrecognized error 0xbunrecognized error 0xb. DUMP: DUMP IS ABORTED DUMP: Deleting "/vol/spool/../snapshot_for_backup.0" snapshot. statler>

1 0

RE: which disk
by Mike Sphar 18 Oct '01

18 Oct '01

Well, at the very least you can just run in degraded mode while you get the correct disk. I would expect you could simply plug the other disk in. If it's the wrong one, the netapp should just ignore it, I would think. Then you just go about ordering a correct one. Or, the whole filer might go up in a big puff of smoke. Try it and let us know! (This is one reason why I prefer to always keep at least one spare available on all my filers. I prefer to let it grab a spare on its own, then I just have to show up at my convenience to swap in the replacement for the bad one.) -- Mike Sphar - Sr Systems Administrator - Engineering Support Peregrine Systems, Inc. -----Original Message----- From: Jim Harm [mailto:jharm@llnl.gov] Sent: Thursday, October 18, 2001 3:12 PM To: toasters(a)mathworks.com Subject: Re: which disk I did not make myself clear. the disks are in the shelves and I am going to fail one that is noisy with errors and remaps of sectors. I know which disk it is. I don't know if my spare, in my hand(SHZHB-ZZ), can replace the one in the shelf(ST15230N). I'd like to know before I fail the disk. Can I plug in a SHZHB-ZZ to replace a failed ST15230N? I can't event tell if a SHZHB-ZZ is a scsi or a 4 GB disk! We haven't had to replace a disk on this unit for over three years! All my production systems that I work on now are 760s and 840s. At 2:33 PM -0700 10/18/01, Chris Lamb wrote: > > >> How do I correlate the identification of the disk on the >> weekly report with the label on the disk? > > The report says 4 GB disk ST15230N and one of my disks says SHZHB-ZZ. >> Nowhere on the disk is there a designation of size, scsi or ultra, >> or even if it is scsi. > >Yow! That is old. :-) An F330, perhaps? What version of ONTAP are you >running? > >From the part number, that drive is a Seagate fast/narrow SCSI drive. >Have you looked at the front of the machine? Even on the old StorageWorks >SCSI shelves the red LED should light to indicate a failed drive... but >it's been a long, long time since I ran one of those. > >Good luck, > >-- Chris > -- }}}===============>> LLNL James E. Harm (Jim); jharm(a)llnl.gov System Administrator Compaq Clusters (925) 422-4018 Page: 423-7705x57152

2 1

Re: which disk
by Jim Harm 18 Oct '01

18 Oct '01

I did not make myself clear. the disks are in the shelves and I am going to fail one that is noisy with errors and remaps of sectors. I know which disk it is. I don't know if my spare, in my hand(SHZHB-ZZ), can replace the one in the shelf(ST15230N). I'd like to know before I fail the disk. Can I plug in a SHZHB-ZZ to replace a failed ST15230N? I can't event tell if a SHZHB-ZZ is a scsi or a 4 GB disk! We haven't had to replace a disk on this unit for over three years! All my production systems that I work on now are 760s and 840s. At 2:33 PM -0700 10/18/01, Chris Lamb wrote: > > >> How do I correlate the identification of the disk on the >> weekly report with the label on the disk? > > The report says 4 GB disk ST15230N and one of my disks says SHZHB-ZZ. >> Nowhere on the disk is there a designation of size, scsi or ultra, >> or even if it is scsi. > >Yow! That is old. :-) An F330, perhaps? What version of ONTAP are you >running? > >From the part number, that drive is a Seagate fast/narrow SCSI drive. >Have you looked at the front of the machine? Even on the old StorageWorks >SCSI shelves the red LED should light to indicate a failed drive... but >it's been a long, long time since I ran one of those. > >Good luck, > >-- Chris > -- }}}===============>> LLNL James E. Harm (Jim); jharm(a)llnl.gov System Administrator Compaq Clusters (925) 422-4018 Page: 423-7705x57152

1 0

which disk
by Jim Harm 18 Oct '01

18 Oct '01

I have a filer that is old and still used for testbeds. The disk failed and we have spares, but; How do I correlate the identification of the disk on the weekly report with the label on the disk? The report says 4 GB disk ST15230N and one of my disks says SHZHB-ZZ. Nowhere on the disk is there a designation of size, scsi or ultra, or even if it is scsi. It is from NetApp, but the only label from netapp on it is the test sticker. -- }}}===============>> LLNL James E. Harm (Jim); jharm(a)llnl.gov System Administrator Compaq Clusters (925) 422-4018 Page: 423-7705x57152

1 0

Re: ONTAP with RedHat linux
by Jered Heeschen 18 Oct '01

18 Oct '01

It's nice to hear I'm not the only one who's run into the hang with the 2.4 kernel, though it sounds like we get it more consistently. I've seen the same issue on a RedHat 6.2 box that's updated to the 2.4 kernel, which is why I'd point to something in the kernel rather than something RedHat-specfic. The best workaround seems to be using TCP to mount the NFS shares - that should allow for better performance than limiting readand write sizes to 1023. To do that, add "tcp" to the mount options, either in /etc/fstab or using the -o flag for "mount". You'd also need to turn on the nfs.tcp.enable option on the filer. Jered Steve Losen <scl(a)sasha.acc.virginia.edu>@mathworks.com on 10/18/2001 10:25:54 AM Sent by: owner-toasters(a)mathworks.com To: toasters(a)mathworks.com cc: Subject: Re: ONTAP with RedHat linux I am running RedHat 7.1 and NFS mounting a netapp F820 running 6.0.1R3. Things work pretty smoothly, but I have experienced the same problem as another poster (sorry, lost the message) where NFS writes occasionally delay and a "NFS server not responding" error is logged. I have not tried the rsize=1023,wsize=1023 work around. I have experienced the same problem with NFS servers other than Netapp, including a IBM RS6000 running AIX. Non Linux NFS clients are having no delay problems with the Netapp filers, so I'm pretty sure it is on the Linux end. For awhile I thought the NIC on my Linux box had botched the speed/duplex negotiation with the ethernet switch. Our network folks can tell me what speed the switch port has negotiated, but I don't know how to check my NIC from Linux. The network folks tell me they see no errors on my switch port when I experience NFS delays. I don't seem to have any other network problems, so I doubt this is the problem. I have been able to duplicate the problem on a second Linux box. However, on a third box, essentially identical to mine and also running RH 7.1, I could not duplicate it. A couple of things to be aware of with RedHat Linux and NFS. Prior to RedHat 7.0, only NFS v2 was supported. Furthermore, Linux only supported 16 bit uids and gids. We have a lot of files on our Netapp filers with uids greater than 65535. RedHat 7.1 supports NFS v3 and 32 bit uids and gids. 32 bit uids are critical in our environment. I administer our filers and when I was running RH 6.2, I could not get accurate file owner information with "ls" and I could not "chown" files to uids over 65535, so I had to use another unix box for filer administration. Now I can do it all from my Linux box. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

1 0

RE: disk_fw_update
by Geoff Hardin 18 Oct '01

18 Oct '01

Thanks for the responses everyone! Jeff Sloan wrote: Yes there is definitely spin up issues with some of the old firmware on the 18G FCAL disks. Upgrading the firmware to the newest releases is the right move. Doing it individually is a very safe method up updating them, and definitely desirable, as you've had a few disk fail on you. I would like to note this is just on the older firmware revisions on the 18G drives. (hence once you finish upgrading you won't have to worry about this repeating itself). In regard to your current situation, The solution is to reboot the node that is reporting the mailbox disk error. We have a workaround that allows you to avoid rebooting, but it's only for ONTAP 6.1X and above. Did you halt the second system when upgrading the firmware? There's a specific process to upgrading the disk firmware on a cluster pair. You can review that process here: http://now.netapp.com/NOW/knowledge/docs/ontap/rel601r3/html/sag/fw_up5.htm… Cheers! :-) Jeff > -----Original Message----- > From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com] > Sent: Thursday, October 18, 2001 1:40 PM > To: Sloan, Jeff > Subject: Re: disk_fw_update > > > Jeff, > The cluster is running DOT NetApp Release 5.3.4R2. We > are updating the firmware in anticipation of upgrading to > DOT 6.1.1R1. We have had problems with some of our filers > with the old 18GB disks during the upgrade; during the last > upgrade, we lost 3 disks, fortunately in 3 separate RAID > groups. Needless to say, it made for a very long, very > tense night as the disks rebuilt. We were hoping to update > the firmware of each disk separately so that we could avoid > this problem. > > Geoff Hardin > geoff.hardin(a)dalsemi.com > Politicians and diapers need changing often for similar reasons.

1 0

disk_fw_update
by Geoff Hardin 18 Oct '01

18 Oct '01

filer1> cf status filer1 has detected a mailbox disk error, takeover of filer2 disabled I have just finished upgrading the disk firmware on filer2. I had turned off clustering per the disk_fw_upgrade instructions prior to upgrading the disks. Once I had finished, I tried to turn clustering back on on filer1 and received the error message above. Any idea what's going on? filer2 does not report any errors on cf status. Thanks for the help! Geoff Hardin Dallas Semiconductor MIS UNIX geoff.hardin(a)dalsemi.com Politicians and diapers need changing often for similar reasons.

2 1

Jump to page:

2026

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