Windows Server

Eshprof · Guest

We are about to do an SMS install on a very large 2000 Forest. The SMS
install is going to change the schema and I would like to know what I need to
do to backup the schema in case of a failure.

How do I back up the schema?
If there is a failure, how do I restore the schema?

Any good articles to read on this subject?

Mental Floss · Guest

Hi Eshprof:

Do an Authoritative backup of the server and back up the System State as
well as all boot files on the DC holding the Schema FSMO role. To restore
this backup, you need to use NTDSUTIL and force replication to all other DC's.

Read this article:
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ntbackup_system_state.asp

-MentalFloss

"Eshprof" wrote:

Nico · Guest

The procedure we follow before doing any schema updates is

Install a new temp DC in root domain
transfer schema master to new DC
Take this DC off the network
Perform the update on this DC
If the update works, put DC back on network and let schema replicate
transfer schema back to orginal DC
demote the temp DC

If the schema fail, then use NTDSUTIL to seize the schema back to orginal DC
and reformat temp DC, to avoid it getting added back to production network
by mistake.

Of course the above works only if the schema update process only updates the
schema and nothing else. Most good programs have a /schemaonly function for
install.

"Eshprof" <Eshprof@discussions.microsoft.com> wrote in message
news:D4B2EDD8-E1D6-496C-A35F-5883EC19F350@microsoft.com...

Eshprof · Guest

Thanks FM.

When you say an "Authoritative backup" are you saying primarily to backup
the System State using NTBackup or Veritas for example, or is this done using
NTDSUTIL?

"Mental Floss" wrote:

Allen Firouz · Guest

What I mean is to perform a full backup and include the System State as well,
using whatever backup program you choose. However, to restore from it, you
need to perform an Authoritative Restore, which forces replication from the
restored DC to all other DC's. This way, the Schema returns to its state
before the changes.

-Allen Firouz [MentalFloss]

"Eshprof" wrote:

Eshprof · Guest

Thanks MentalFloss.

I'm a little confused though in this regard...

In Article 241594 (previously published under article Q241594) entitled "How
to perform an authoritative restore to a domain controller in 2000", it
states "You cannot authoritatively restore the schema." Have I misread the
article or misunderstood? I'm guessing I can do and Non-authoritative
restore?

Also, I recently got a forum response that says, "You cannot recover a
Schema from backup in Windows 2000." That greatly concerned me, hence my new
post. If I can't recover the Schema in 2000, what would I do if the Schema
Master took a dive? Backing up the System State on the Schema Master makes
sense to me. If I couldn't do that would it be a matter of seizing the role
from the schema partition of another machine?

Thanks for your help.

Eshprof

"Allen Firouz" wrote:

Allen Firouz · Guest

Eshprof:

You are partially correct. You should never DELETE an extended schema
object. However, you can disable it. Schema extensions are there forever
(unless you blow away the domain and start from scratch). Restoring the
Schema retains all schema information, but you can disable any schema objects
created [make them null]. To go back to an old Schema, you have to do an
Authoritative Restore of your Active Directory. Here is a comprehensive
document (MS Word) on AD restores and Disaster Recovery:
http://go.microsoft.com/fwlink/?LinkId=8597

-Allen Firouz [MentalFloss]

-Allen Firouz [MentalFloss]

"Eshprof" wrote:

Eshprof · Guest

Thanks.

"Eshprof" wrote:

	Windows Server Forum Index -> Active Directory	All times are GMT
Page 1 of 1