toasters

toasters@lists.teaparty.net

13514 discussions

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

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