::adding that to my list::
thank you, Ed.
-Michèle
Immigration site: <http://LadySun1969.tripod.com>
Our new 2001 Miata: <http://members.cardomain.com/bpituley>
Tiggercam: <http://www.tiggercam.co.uk>
---------------------------------------------------------
There is always one more son-of-a-bitch than you counted upon.
---------------------------------------------------------
-----Original Message-----
From: Ed Crowley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 7:33 PM
To: Exchange Discussions
Subject: RE: Brick Level Backups
See FAQ Appendix F.
Brick Level Backups will not cause your car to rust out or your hair to fall
out. They are unlikely to make your system less reliable (but no guarantees
there), nor make your normal non-brick-level backups less reliable. They
do, however, use more tape, make your backup jobs take more time and wear
your tape drive out faster. They give you a false sense of security that
you can get something back when in fact you may not. And you often cannot
get everything back from a brick level backup.
Brick Level Backup is a kludgy crutch for administrators who insist on
managing their Exchange systems as if they were cc:Mail or MS Mail systems.
They want the benefits of a database e-mail architecture, but want to manage
it as if it were a file-based system.
If you follow the Ed Crowley Never Restore Method®, you can remain secure in
the knowledge that you'll almost never need to do a Brick Level Restore.
If, for some rare event you find that you need to restore a message or
mailbox, then you have a great opportunity to practice your disaster
recovery techniques on your recovery server. What? You don't have a
recovery server? Well, you need one whether or not you use Brick Level
Backup.
In a nutshell, Brick Level Backups aren't evil. But they're completely
superfluous.
Ed Crowley MCSE+Internet MVP
Tech Consultant
Compaq Computer Corporation (soon to be HP)
All your base are belong to us.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Sethi, Ali
Sent: Wednesday, September 12, 2001 3:25 PM
To: Exchange Discussions
Subject: Brick Level Backups
Hello,
Can someone tell me why Brick Level backups are a bad idea? I have been
doing brick level backups for a while and have not incurred into any
problems. Am I heading for a disaster by continuing to do brick level
backups? My users demand that mailbox be restored without the Exchange
server being down. I do frequently get calls from users accidentally
deleting emails and then frantically calling me to restore them immediately.
What are my alternatives? Email retention? How much disk space would that
require on my exchange server to setup a email retention for 30 days?
In order to skip brick level backups would I need a second exchange server
as a DR server? If that is the case and I setup a local lan with the exact
same domain, service account, site and organization name would it be a piece
of cake to restore a full backup on this server and recover all the data on
tape without any problems??
Exchange 5.5 sp4
Win 2k server
626 mailboxes
31GB Info store, about 100gb on server (Including emc drive array space)
1.5GB of ram. Do you think I need more Ram? I may...
At what point is it a good idea to begin to think about a 2nd exchange
server?
Thanks,
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
