toasters October 2001

toasters@lists.teaparty.net

136 participants
184 discussions

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

← Newer
1
...
4
5
6
7
8
9
10
...
19
Older →

Jump to page:

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 October 2001