toasters October 2001

toasters@lists.teaparty.net

136 participants
184 discussions

Re: Disconnect serial console
by Kerry Schwab 10 Oct '01

10 Oct '01

A little off topic, but I just wanted to address this: " I know that some Sun servers crash when the console is disconnected". Actually they don't crash, but the serial driver interprets the disconnect as a break signal, and drops into the prom monitor. If this happens, you can just type "c" and the system will continue where it left off. This isn't usally a problem unless it was in the prom monitor for an extended period of time. ( in which case tcp connections from other machines get dropped, etc) On the newer machines, leaving the power selection in the "secure" position will keep this from happening at all. == Kerry >>> "Walsh, Warren (MN65)" <warren.walsh(a)honeywell.com> 10/10/01 09:41AM >>> Hi all - I need to move the serial console on my 530 and 740 filers. Basically, the console ports on the filers go to a pair of Wyse terminals. We need to move the Wyse terminals few feet, and that will require disconnecting and rerouting the serial cables. I've never disconnected the console while the filer is up and running. Will this crash the filer, or cause any problems? I know that some Sun servers crash when the console is disconnected, and I'd like to avoid that if at all possible. Thanks in advance for your help, -warren

1 0

RE: Disconnect serial console
by White, Lance 10 Oct '01

10 Oct '01

There is no issue with disconnecting a console from a Filer whilst it is running. -----Original Message----- From: Walsh, Warren (MN65) [mailto:warren.walsh@honeywell.com] Sent: Wednesday, October 10, 2001 7:41 AM To: toasters(a)mathworks.com Subject: Disconnect serial console Hi all - I need to move the serial console on my 530 and 740 filers. Basically, the console ports on the filers go to a pair of Wyse terminals. We need to move the Wyse terminals few feet, and that will require disconnecting and rerouting the serial cables. I've never disconnected the console while the filer is up and running. Will this crash the filer, or cause any problems? I know that some Sun servers crash when the console is disconnected, and I'd like to avoid that if at all possible. Thanks in advance for your help, -warren

1 0

RE: Disconnect serial console
by Toal, Dave 10 Oct '01

10 Oct '01

I've never had a problem unplugging laptop or console-server serial cables with the filer running. Turning the console-server *off* while connected is a problem for sun boxes; don't know if netapps pick up "three low bytes" as a break. -----Original Message----- From: Walsh, Warren (MN65) To: toasters(a)mathworks.com Sent: 10/10/01 10:41 AM Subject: Disconnect serial console Hi all - I need to move the serial console on my 530 and 740 filers. Basically, the console ports on the filers go to a pair of Wyse terminals. We need to move the Wyse terminals few feet, and that will require disconnecting and rerouting the serial cables. I've never disconnected the console while the filer is up and running. Will this crash the filer, or cause any problems? I know that some Sun servers crash when the console is disconnected, and I'd like to avoid that if at all possible. Thanks in advance for your help, -warren

1 0

RE: SQL2000 on F740 w/ Log Shipping?
by Wollermann, Brian 10 Oct '01

10 Oct '01

I'm not trying to run an app at all. Just one dumb database for testing. Thanks for the suggestions for the White papers. I'm drowning in tech documents. I'm making progress now at least. I have two SQL2000 servers in a failover configuration with the DB on the filer. The log shipping is working fine. I'm now working on getting the role change to work and do more testing. -----Original Message----- From: Todd Phillips [mailto:toddp@iarchive.com] Sent: Friday, October 05, 2001 5:44 PM To: 'Wollermann, Brian '; ''toasters(a)mathworks.com' ' Subject: RE: SQL2000 on F740 w/ Log Shipping? Hi Brian. What Cluster App are you running on the SQL Servers? Veritas, Legato, other? Have you checked the White Papers on NetApps Now site? Todd -----Original Message----- From: Wollermann, Brian To: 'toasters(a)mathworks.com' Sent: 10/5/2001 2:28 PM Subject: SQL2000 on F740 w/ Log Shipping? I'm trying to do some testing with our F740 and SQL2000. With the DBs hosted on the filer the stupid checkbox is greyed out for log shipping. Has anyone been able to setup a standby server that accesses databases on the filer w/ SQL2000? Any pointers would be appreciated. We are trying to have two servers in a failover configuration with DBs loaded on the filer. Thanks.

1 0

Re: Two disks vol0 for root volume
by Rune Bakken 09 Oct '01

09 Oct '01

"Rob C. Tien" <rtien(a)Dominionsc.com> writes: > Hello, > > Does anyone out there has any thoughts on the pros and cons regrading > whether or not is a good idea to create a separate two disks vol0 for the > root volume on the Netapp Filer ? I understand that this question has been > posted here before and If someone could send me those discussion threads > that would be great !! At my site, the current policy is to have a separate two-disk root volume, as during our first tests with filers, one of my system developers managed to crash a filer by filling the root volume. It is kind of waste of disk space, so I have allowed use of the root volume on one or two filers, although with fascistic control of the qtree quotas in order to avoid the above. >>>>>>>>>>>>>>.rune -- Rune Bakken "I feel sorry for people who don't drink. System Administrator When they wake up in the morning, that's as Nextra, good as they're going to feel all day." - Telenor Company - Frank Sinatra

1 0

Re: Ack! I can't take it anymore!
by ScottUCE＠aol.com 09 Oct '01

09 Oct '01

******WINNING BIDDER!!!****** Network Appliance's own Britt Bolen -- out of their Durham, NC office -- is the proud new owner of a genuine chrome F540 filer front bezel! Congratulations, Britt! The bezel's new home is apparently going to be at the bottom of Britt's fishtank. Britt will be contributing $150.00 to the September 11th Fund. Thank you Britt, and thanks to the other bidders! Scott Fischmann Union Computer Exchange, Inc. 6233 Idylwood Lane Minneapolis, MN 55436 Phone: 952 935 7282 FAX: 952 935 5056 scott(a)unioncomputer.com

1 0

Two disks vol0 for root volume
by Rob C. Tien 08 Oct '01

08 Oct '01

Hello, Does anyone out there has any thoughts on the pros and cons regrading whether or not is a good idea to create a separate two disks vol0 for the root volume on the Netapp Filer ? I understand that this question has been posted here before and If someone could send me those discussion threads that would be great !! Thanks in advance for your inputs !! Rob Tien Dominion Semiconductor

2 1

RE: Two disks vol0 for root volume
by Fox, Adam 08 Oct '01

08 Oct '01

Personally, I'm not a big fan of them unless you are in a SnapMirror environment or another environment where you may want to take volumes offline. Other than that, it's only about 50MB of space, so pick one volume and let it sit there. Just my opinion. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Rob C. Tien [mailto:rtien@Dominionsc.com] > Sent: Monday, October 08, 2001 2:29 PM > To: toasters(a)mathworks.com > Subject: Two disks vol0 for root volume > > > Hello, > > Does anyone out there has any thoughts on the pros and cons regrading > whether or not is a good idea to create a separate two disks > vol0 for the > root volume on the Netapp Filer ? I understand that this > question has been > posted here before and If someone could send me those > discussion threads > that would be great !! > > Thanks in advance for your inputs !! > > Rob Tien > Dominion Semiconductor >

1 0

RE: Two disks vol0 for root volume
by lkaptan＠pro-link.net 08 Oct '01

08 Oct '01

It depends on the application you are planning to integrate with Filer. For instance multiple volumes for database environment enable you to use snaprestore efficiently. Putting the datafiles to another volume and seperating the root volume, provides flexibility. Is there anything else or anything wrong ? Original Message: ----------------- From: Rob C. Tien rtien(a)Dominionsc.com Date: Mon, 8 Oct 2001 14:29:22 -0400 To: toasters(a)mathworks.com Subject: Two disks vol0 for root volume Hello, Does anyone out there has any thoughts on the pros and cons regrading whether or not is a good idea to create a separate two disks vol0 for the root volume on the Netapp Filer ? I understand that this question has been posted here before and If someone could send me those discussion threads that would be great !! Thanks in advance for your inputs !! Rob Tien Dominion Semiconductor -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

1 0

RE: NetApp response on Microsoft Support for SQL Server and Exchange
by Clark Turner 08 Oct '01

08 Oct '01

>>> jack verdirame <jackv(a)netravision.com> 10/6/2001 4:16:12 PM >>> Hello, What you need to consider is why you bought the filer or for what reason the filer is being considered in the first place. There was probably some Value provided by Netapp. The only reason is for SQL and Oracle databases. I personally do not see the value as the 840 is $160k. Competition is less. But, we are not going purely for price. In the beginning we mentioned SQL and was told no problem. Now there is question. Netapp Engineer's will be here this week for onsite testing. It should be fun. As for defined support: It is interesting based on docs, MS support is in question in these environments, especially when other DB vendors support there product in a MS environment with Filers. You should start to question what MS is really supporting - their File System. A typical MS exchange outage in a Supported MS environment is several+ hours and could be days. Remember this is a MS product corruption and happens in a MS supported environment. Then what do you tell you upper management. In a Netapp environment that can be reduced to minutes+. I find it interesting that SQL can run error free for years on direct attached storage. The minute we put the data on the 840 we get corruption and blank records. That's unacceptable and has NOTHING to do with SQL or MS. It has everything to do with Netapp and there product. That's why they are going to come on site to try to fix the problem and to prove performance. So far the 840 is about 50% slower than local disks. The SQL issue is simple... We get Proof of support in writing or we will NOT purchase netapp's for our Network. We are an MS shop and we work with MS and rely on them for support. If someone on this forum does not like MS then so be it. I still have to guarantee uptime. This is not a problem now and I will not let it become a problem. If you really understand what Filers bring to your infrastructure and environment you should not be questioning Network Appliance but Microsoft. It is about time MS really started to understand what reliability, uptime, security and scalability are, not to mention a bunch of other verbs. I disagree and this is just an MS flame post. If you want to Flame MS that's fine, go ahead and make a fool of yourself. Saying that the SQL issue is MS's fault when SQL works perfectly on direct attached storage is just asinine. On a different subject - what about the gaping holes in MS OS and app security? What does management think of that? Oh yeah - download another SP and reboot. Management does not think of that as I take care of issues like that before they are a problem. I laugh at posts like this that slam Microsoft. It reminds of the movie Plains trains and automobiles. John candy(Del Griffith) turns to Steve martin(Neil page) and says "Gee, It must be nice to be perfect and Odor free". Have a good day, Have a good day and a good week. CT. Jack On Fri, 05 Oct 2001, Clark Turner wrote: > > Ken, > I know how you feel. I am in the same boat with the Netapp 840. We where about to migrate 150 DB's from SQL and oracle. > I hope my email did not scare you to much. I know people are running SQL with success. Others are not. I wanted to explain what I learned so Netapp could understand why I am worried. It was not meant to freak out others. > I would test and test and test and test to be Damn sure you do not have the problems we did. > > C > > >>> "Bunce, Ken" <KBunce(a)JunoLtg.com> 10/5/2001 8:55:02 AM >>> > Reading e-mails like one from Clark is really making me nervous, I just > convinced my corporation to migrate our SQL 7.0 database to a F840 based on > assurances from Sandy and our local representatives from NetApp of MS > support for SQL in a NAS environment. > > I, too, have gotten my email from NetApp regarding signing a NDA. Quit > worrying about protecting your tails and give us an honest answer. > > Ken Bunce > -----Original Message----- > From: Clark Turner > To: toasters(a)mathworks.com; sandra.lake(a)netapp.com > Sent: 10/5/01 10:25 AM > Subject: Re: NetApp response on Microsoft Support for SQL Server and > Exchange > > > Thanks for the information Sandy. I just read the QB article 5 times. > Towards the end of the article is states: > > Limited support is extended to only the SQL server application and DOES > NOT extend to any issues that may occur as a result of the use of non > windows Logo qualified products: > > EMC Clariion server > Network Appliance Filers (specifically the Netapp F760 and F800) > > > Nowhere in the article does it say that NAS is supported on The Netapp > products. There is a line stating "limited" support for NAS devices. > "Limited" is not a good enough reason for me to put my Job on the line > running SQL on this 840. > > Here is another quote: > > "Microsoft generally recommends that you store Database files either on > local disk subsystems or on storage area networks (SAN)." > > That's the one that grabs my attention. Add the lines about data > corruption and I am scared. > > Then add in a posts that passed through this list: > > "It is confirmed from our Microsoft Rep. that they will not support SQL > or > Exchange on NAS. But it is supported on SAN. We are moving our SQL > databases and exchange from NAS to a SAN. Leaving the F740 to do file > services at a > rather expensive cost." > > and > > "We > have also noticed that some of the databases have gone suspect when > there > was a hiccup on the comm side. You know as well as I that's not > acceptable. > In some instances the databases that went suspect could not be recovered > and > had to be restored from a SQL backup." > > > After all of this I thought I would test our loaner 840 out. I took a > copy of a production database that was 5 gig in size and then inserted > 34 million records into it. First I ran this on local Raid 5 on a Compaq > DL580. It took about 10 hours. Then I offloaded a fresh copy of the > database to the 840 and ran the test again. To our amazement the netapp > database was missing records. It failed to write the records down to > disk. Just as the above quote states and just as the MS article warns. A > single missing record means that my database us useless. I was never > able to fix the problem in a week of solid testing. Then a Netapp > employee sent me email talking about me signing a non disclosure > statement before Netapp would discuss the issue really made me step back > and think. > > I think our data is to important to chance. I know some people are doing > this but the events in the last week have told me that its just not > safe.I need a solution that is GUARANTEED and officially supported by > Microsoft. > > CT > > >>> "Lake, Sandy" <sandra.lake(a)netapp.com> 10/4/2001 6:12:51 PM >>> > Network Appliance has more than 200 customers using filers with SQL > Server 6.5, 7.0, or 2000 with databases ranging up to 800 GB. Microsoft > has published knowledge base article Q304261 on the Microsoft Web site, > which states support of their SQL Server product when used with Network > Appliance F760 or F800 series products. The article can be found at: > > http://support.microsoft.com/support/kb/articles/q304/2/61.asp?id=Q30426 > 1 > > The Microsoft rep in the field may not be aware of this knowledge base > article. Customers will receive SQL Server support from Microsoft > Product Support Services when they log a call. > > Network Appliance hosts 1.1 million Exchange seats at more than 200 > large Exchange accounts. Network Appliance is the primary provider of > support for SnapManager and filers deployed in Exchange 5.5 or Exchange > 2000 environments. When the Exchange log file and store are located on > filers and the customer experiences any problems getting to their data, > a support call would be opened with Network Appliance. Microsoft has > published knowledge base article Q237767, which covers offline and > snapshot backups in Exchange environments. That article can be found at > http://support.microsoft.com/support/kb/articles/q237/7/67.asp?id=Q23776 > 7 > > Working with the customer, Network Appliance will determine if the root > cause of the call is with SnapManager, filers, Exchange 5.5 or Exchange > 2000. If the root cause is unrelated to NetApp products, IBM Global > Services (IBMGS), NetApp's certified support partner for Exchange, is > brought into the call to assist us. Network Appliance, IBMGS, and the > customer work together to close the call to the customer's satisfaction. > The customer's support agreement would be contracted through NetApp. > There is no additional charge to the customer for the Exchange expertise > provided by IBMGS. Network Appliance offers customers several service > agreement levels that can be tailored to meet their specific support > requirements. > > Network Appliance offers many solutions that protect and enhance a > customers investment in the Microsoft platform, however this is not the > appropriate forum for that discussion. If you need or would like more > details about information in this email, please contact your local sales > rep. > > > ------------------------------------------------------------------------ > ------------ > ------------------------------------------------------------------------ > ------------ > > Sandy Lake > Director, Microsoft Alliances > Network Appliance > > <<InterScan_Disclaimer.txt>> > ---------------------------------------- Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Description: ----------------------------------------

2 1

← Newer
1
...
12
13
14
15
16
17
18
19
Older →

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