toasters April 2005

toasters@lists.teaparty.net

59 participants
67 discussions

RE: EMC vs Netapp
by Ben Rockwood 01 Apr '05

01 Apr '05

HAHA! Thats a pretty good one. Where did you find that? Gotta love Apr fools. benr. -----Original Message----- From: owner-toasters(a)mathworks.com on behalf of Linux Admin Sent: Fri 4/1/2005 11:26 AM To: NetApp Toasters List Cc: Subject: EMC vs Netapp Is that true that EMC is purchasing NetAPP?

1 0

Re: Upgrading to 6.5
by jbrigman＠nc.rr.com 01 Apr '05

01 Apr '05

Robert - Note what platform you'll be installing on. For example, if you have a cluster, 6.5.1 had a bug that caused one machine to lose time sync with the other. If you have a certain NVRAM board, you'd get bogus messages that the NVRAM was failing. Make sure you go, at least, to 6.5.2. You'll miss some significant bugs there. JKB ----- Original Message ----- From: Robert Borowicz <rbaus(a)swbell.net> Date: Friday, April 1, 2005 7:38 am Subject: Upgrading to 6.5 > I'm upgrading to 6.5 this weekend. Is there any gotchas? (yes I'll > be > reading the Release Notes) > > Isn't there an issue with the exports file being re-written? I > thought I > remembered seeing that discussed here a while back. > > -Rob >

2 1

Re: Upgrading to 6.5
by jbrigman＠nc.rr.com 01 Apr '05

01 Apr '05

Oh, and of course, make sure the firmware on all your drives is updated. You do not want to update firmware in the course of an upgrade, unless you have only very few drives that need firmware updates! JKB ----- Original Message ----- From: Robert Borowicz <rbaus(a)swbell.net> Date: Friday, April 1, 2005 7:38 am Subject: Upgrading to 6.5 > I'm upgrading to 6.5 this weekend. Is there any gotchas? (yes I'll > be > reading the Release Notes) > > Isn't there an issue with the exports file being re-written? I > thought I > remembered seeing that discussed here a while back. > > -Rob >

1 0

[Fwd: RE: Upgrading to 6.5]
by Robert Borowicz 01 Apr '05

01 Apr '05

6.5.4 was released just this week. The issue was "fixed" in later 6.5 releases? -Bob Get a current version...like 6.5.3P11 I am unsure about 6.5.4, Although I think there is a 6.5.4P1. This will be sure to avoid all the known NFS/export issues. -----Original Message----- From: Robert Borowicz [mailto:rbaus@swbell.net] Sent: Friday, April 01, 2005 7:39 AM To: toasters(a)mathworks.com Subject: Upgrading to 6.5 I'm upgrading to 6.5 this weekend. Is there any gotchas? (yes I'll be reading the Release Notes) Isn't there an issue with the exports file being re-written? I thought I remembered seeing that discussed here a while back. -Rob

1 0

Upgrading to 6.5
by Robert Borowicz 01 Apr '05

01 Apr '05

I'm upgrading to 6.5 this weekend. Is there any gotchas? (yes I'll be reading the Release Notes) Isn't there an issue with the exports file being re-written? I thought I remembered seeing that discussed here a while back. -Rob

1 0

RE: Exchange 5.5 and OnTap 7.0.0.1 Problem?
by Holland, William L 01 Apr '05

01 Apr '05

Neither - using NAS. -----Original Message----- From: McCarthy, Tim [mailto:timothy.mccarthy@netapp.com] Sent: Friday, April 01, 2005 6:46 AM To: Holland, William L Subject: RE: Exchange 5.5 and OnTap 7.0.0.1 Problem? You did not mention in your post if you were using VLD or iSCSI, your version of SnapManager for Exchange and your version of SnapDrive. Have you checked the compatibility Matrix on NOW? --tmac ====================== -----Original Message----- From: Holland, William L [mailto:hollandwl@state.gov] Sent: Friday, April 01, 2005 5:59 AM To: 'toasters(a)mathworks.com' Subject: Exchange 5.5 and OnTap 7.0.0.1 Problem? The F825 hosting the message stores were upgraded to OnTap 7.0 on 3/5/2005 and to 7.0.0.1 on 3/23/2005. Also, on 3/23/2005 we started SnapMirror'ing the message stores to an R200 running 7.0.0.1. On the afternoon of 3/28/2005 we saw one server cycle its Exchange services a few times and on 3/29/2005 both Exchange servers were cycling their Exchange services. By 3/30/2005 it had become so bad and so frequent we made the decision to move the message stores to the local storage to isolate if the problem was with the filer or with the databases themselves. All is running fine now. On 3/28/2005 I conducted a test to determine if backups performed with SnapManager (snapbexc) were truly recoverable. To do so I built a new Exchange 5.5 SP4 server (same organization and site name, but did not join existing site and did not configure any connectors) on NT4 SP6a, connected it via direct GbE to an F810 running OnTap 7.0.0.1 and used ndmpcopy to copy from the snapshots on the F825 to the F810. When I tried to start the Directory Store I received an error message. I used ESEUTIL to repar the database and when I tried to start it then I was informed that it would not start as the computer I was attempting to start it on was not the same name as the one it had been created on. At this point I shut this server down and deleted the files and volumes created for the test. It was within minutes of this that we saw the first cycle of the Exchange services on the server whose database I was using a copy of to test. I could almost believe that this could have caused a problem on one server but not two and then also given the fact that now that we have moved the message stores to local storaget they are running fine. But, in any event, I've learned not to discount anything as possible in a networked environment.

1 0

Exchange 5.5 and OnTap 7.0.0.1 Problem?
by Holland, William L 01 Apr '05

01 Apr '05

The F825 hosting the message stores were upgraded to OnTap 7.0 on 3/5/2005 and to 7.0.0.1 on 3/23/2005. Also, on 3/23/2005 we started SnapMirror'ing the message stores to an R200 running 7.0.0.1. On the afternoon of 3/28/2005 we saw one server cycle its Exchange services a few times and on 3/29/2005 both Exchange servers were cycling their Exchange services. By 3/30/2005 it had become so bad and so frequent we made the decision to move the message stores to the local storage to isolate if the problem was with the filer or with the databases themselves. All is running fine now. On 3/28/2005 I conducted a test to determine if backups performed with SnapManager (snapbexc) were truly recoverable. To do so I built a new Exchange 5.5 SP4 server (same organization and site name, but did not join existing site and did not configure any connectors) on NT4 SP6a, connected it via direct GbE to an F810 running OnTap 7.0.0.1 and used ndmpcopy to copy from the snapshots on the F825 to the F810. When I tried to start the Directory Store I received an error message. I used ESEUTIL to repar the database and when I tried to start it then I was informed that it would not start as the computer I was attempting to start it on was not the same name as the one it had been created on. At this point I shut this server down and deleted the files and volumes created for the test. It was within minutes of this that we saw the first cycle of the Exchange services on the server whose database I was using a copy of to test. I could almost believe that this could have caused a problem on one server but not two and then also given the fact that now that we have moved the message stores to local storaget they are running fine. But, in any event, I've learned not to discount anything as possible in a networked environment.

1 0

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 April 2005