I would say that depends on how much time you want to wait to get the DB from tape or whatever backup source you are using and how much time you can afford to have the database offline. If you don't mind it taking 3 days to get the database back online maybe 100GB isn't too large. But if you want it back online in 15 minutes it's going to have to be less than 15GB and you probably don't want to use tape as your only backup option. Oh, if you want it back that quickly you should probably practice restoring often, otherwise it may take you more than 15 minutes just to figure out what you have to do, let alone actually do it!
I would say anything under 15GB - 20GB **could** still be consider small. But that would depend on the size of your organization. It's really a relative term. For a company with 20 - 30 users 15GB might be huge. But if you're talking about an organization with more than 20,000 people 20GB might be small. It just depends on what you're used to seeing. Regards, Doug Jones -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: Wednesday, March 17, 2004 6:13 PM To: Exchange Discussions Subject: RE: Failover Servers AND Restore/Recovery Server How small IS a small DB? Regards, Orin -----Original Message----- From: Bridges, Samantha [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 2:02 PM To: Exchange Discussions Subject: RE: Failover Servers AND Restore/Recovery Server Awesome...thank you! Great advice and an interesting story to go along. Samantha :) -----Original Message----- From: Douglas A. Jones [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 2:34 PM To: Exchange Discussions Subject: RE: Failover Servers AND Restore/Recovery Server I would say to spend the money on quality and redundant hardware so you don't have to recover in the first place. Because if it like any place I've even done work for, you're not going to come close to recovering a server in 30 minutes let alone 15. You best bet is to keep for databases as small as possible. I did work for a law firm that managed to let one of its databases on a 5.5 server get to be almost 100GB. Then the server crashed... Need less to say it took about 8 hours to get if off tape to a server with enough disk space, then 3 hours to just copy it to the restore server over the network. Never mind how long it took to run an ISINTEG to run because someone messed up bring it back up. Since the server had more than 40 or 50 attorneys on it who bill out at more than $500 / hour who couldn't get to their e-mail they were not pleased. Shortly afterwards they spend more than $100K on new exchange 2000 servers. Moral of the story, keep you databases small and hardware redundant so you don't have to ever recover... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bridges, Samantha Sent: Tuesday, March 16, 2004 11:57 AM To: Exchange Discussions Subject: RE: Failover Servers AND Restore/Recovery Server No. Sorry if this is a redundant question. Just say the "budget" is $20,000. Just wondering if anyone here has a "great" way of recovering Exchange 2000 in 15 minutes or less. I have gone over the many articles and white papers for exchange disaster recover server but was interested in the forums comments. Thanks Samantha (still the same ol' Samantha) -----Original Message----- From: Fyodorov, Andrey FTL [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 11:45 AM To: Exchange Discussions Subject: RE: Failover Servers AND Restore/Recovery Server Do we have the same person asking the same question every day under a different name? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bridges, Samantha Sent: Tuesday, March 16, 2004 9:03 AM To: Exchange Discussions Subject: Failover Servers AND Restore/Recovery Server Windows 2000 Advanced Server Exchange 2000 Dual Processor Compaq ML350 25 GB IS Hello All. My management wants a high availability solution put in place that includes both a failover solution AND a recovery solution. A failover for hardware failures and a recovery for IS corruption etc... If the primary IS corrupts than most likely the secondary will corrupt also. I have been looking at SteelEye and Neverfail for a failover solution (any comments on these two companies would be appreciated). Have been having a problem getting neverfail to work and will start testing the SteelEye next week sometime. As for the recovery server I am interested in your thoughts. I asked my management two questions, 1)How long are you willing to wait for services to be restored? And 2)How much data are you willing to lose? Their answer to those questions were, 1) 15 minutes and 2) NONE. Ok...with those questions being answered, does anyone in this forum have a solution in place that can meet the request of my management? They want another solution in place in case the failover "fails". Is the answer to have a third server that just sits there (pre built of course) ready to go incase the failover solution falls short? I do nightly online backups of Exchange and would need time to restore the backup on the recovery server plus add the transaction logs in. This will take more than the 15 minute allotment. Any ideas or comments would be helpful. Thanks, Samantha Bridges Macomb Intermediate School District _________________________________________________________________ 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. --- [This E-mail scanned for viruses by Declude Virus] _________________________________________________________________ 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. --- [This E-mail scanned for viruses by Declude Virus] _________________________________________________________________ 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. _________________________________________________________________ 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.
