WaaSuuuup Roger,
Good to hear from you. That is exactly what were considering 1 cold standby instead of clustering. All we would have to do is change the World Wide Name of our HBA fiber card in the SAN switch and were back up and running. Thanks for the info I will follow up with that, and will make sure I post my findings back here when I have them. -TOny -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Seielstad Sent: Friday, January 09, 2004 10:44 AM To: Exchange Discussions Subject: RE: Location of Transaction Logs Yo, Tony! I see you survived the trip back from Orlando... If I remember correctly, you can bypass caching at the RAID group (not the LUN) level through Navisphere. I don't currently have access to mine to check, but I know I asked that question. Another option is to change the read/write cache percentage to be mostly read caching and reduce the potential exposure. I'd suggest skipping boot-from-SAN, but that's just me. The only reason I'd see boot-from-SAN helping is if you are going to have identical cold standby hardware available to replace in the case of system failure. I'm not sure you want to use non-identical hardware for cold spares in that kind of case. Roger -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. > -----Original Message----- > From: Anthony Sollars [mailto:[EMAIL PROTECTED] > Sent: Friday, January 09, 2004 12:11 PM > To: Exchange Discussions > Subject: Location of Transaction Logs > > > > Hello all, > > ����������� > ����������� We are planning a global Exchange upgrade here to > 2003 and are > researching an issue that an email admin here is having with > the location of > the Transaction logs in our new Exchange Architecture. We are > planning to > Deploy Quad-proc servers that are boot-to-SAN on an EMC > Clarion CX600. The > OS, Logs and DATA will be stored on the SAN. The problem is > we are not sure > if the transaction log data will be secure in the case of > server outage, > since the SAN utilizes a very hefty cache before it writes > the data to SAN > disk. We have already begun queuing our SAN vendor and MS, > but they do take > awhile in complex questions such as these, I was wondering if > anyone in the > list has deployed Exchange 200x on a SAN and has come across > this question? > > Thanks again, > > Anthony L. Sollars��������������������______________ > Technology Consultant > Information Technology Division, PACCAR Inc. > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t ext_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
