First off, most people (when dealing with TSM) define a Bare Metal Restore as starting off with a clean h/w system (no data, os), then install OS, install TSM client, restore your data.
The issues listed below may not require a BMR. 1. Botched Schema update - MS says you cannot authoritatively restore the schema so don't expect TSM to help you. 2. Accidental deletion of OU - just use directory service restore mode - don't need BMR. 3. Database corruption - if you can still boot into ds restore mode (which doesn't use AD) you can use this to restore AD. 4. System state - no requirement for BMR. 5. Accidental deletion of DNS zone, if AD integrated I believe this is similar to 2. If not integrated you simply restore your DNS zone file. 6. File print servers etc no issue here - as long as your server and tsm is operational you can restore. I really wish TSM would support a true bare metal restore function - boot from floppy restore system (they say buy TKG's product). I'm pretty sure Tivoli will support any of the issues above with TSM (except the schema!). You really have to test these out and understand all the issues. Tim Rushforth City of Winnipeg -----Original Message----- From: Consiglio, Tony [mailto:[EMAIL PROTECTED]] Sent: July 12, 2002 11:37 AM To: [EMAIL PROTECTED] Subject: Re: Backup a W2K Domain Controller? Given the Examples of backup reasons below: Has any one every had a AD corruption that that used TSM to recover from after the GC's have already replicated that corrupted data out? If so, did TSM support stand by them all the way until the issue was resolved?? We are sort of leery about using TSM so the simple reason that they always say "We do not support BMR" and on a DC with AD this is critical..... Any help would be great **************************************************** "1.) Botched Schema update 2.) Accidental deletion of OU (or any other object) 3.) Database corruption **** (AD Corruption) 4.) System State. 5.) Accidentally deletion of a DNS zone 6.) Some DC's are also File/Print servers, DHCP, etc. *** Some of these scenarios would require an authoritative restore or a complete rebuild of the Active Directory, as some changes are replicated immediately." ****************************************************
