Authoritative restore using Veritas not working

[Guest]

I have been doing test with authoritative restores on a test network. When I
restore from a backup created using ntbackup.exe it works fine. When I
restore from a backup created using BackupExec, I cannot get the changes to
stay after making it authoritative. I have checked to verify that the data
is being restored properly by rebootin into AD with the network connection
unplugged. I am doing all of the steps in the same order that I do them when
using the ntbackup files. Any ideas?

 

[Herb Martin]

I have been doing test with authoritative restores on a test network. When I
restore from a backup created using ntbackup.exe it works fine. When I
restore from a backup created using BackupExec, I cannot get the changes to
stay after making it authoritative. I have checked to verify that the data
is being restored properly by rebootin into AD with the network connection
unplugged. I am doing all of the steps in the same order that I do them when
using the ntbackup files. Any ideas?

I have not idea the answer to your question (I use NTBackup)
but a good friend and student of mine reported something
similar with a DIFFERENT third party backup, just this week.

I wonder what is going on and will be watching this thread.

One presumes you didn't (accidently) make an "incremental
or differential backup" -- NTBackup does NOT support that
for System State.

 

[Guest]

It was a full backup, not incremental.

I have not idea the answer to your question (I use NTBackup)
but a good friend and student of mine reported something
similar with a DIFFERENT third party backup, just this week.

I wonder what is going on and will be watching this thread.

One presumes you didn't (accidently) make an "incremental
or differential backup" -- NTBackup does NOT support that
for System State.

 

[Herb Martin]

It was a full backup, not incremental.

I really didn't think that was going to be it but
didn't want to take a chance on filtering it out
of the info for you.

 

[Paul McGuire]

i had the same problem about a year ago with backupexec i would restore the
info and then reboot into AD restore mode and do the ntdsutil commands. but
when i rebooted it would not work. I have never seen this work properly
with backupexec

 

[Guest]

BackupExec requires that you have an administrator for the domain do the
sysvol backup, I believe. Go to your NT Services Control panel on your
server and find all the Backup Exec services, note the user that is logged to
run the backups. This user will be the only one able to run the backup. The
user must also be added to your group policies to "run as a service". Rather
restrictive, but I believe if these things are being done, you will be able
to backup your sysvol.

 

[Herb Martin]

BackupExec requires that you have an administrator for the domain do the
sysvol backup, I believe. Go to your NT Services Control panel on your
server and find all the Backup Exec services, note the user that is logged to
run the backups. This user will be the only one able to run the backup. The
user must also be added to your group policies to "run as a service". Rather
restrictive, but I believe if these things are being done, you will be able
to backup your sysvol.

BUT, these people (and my friend for certain) all seem to
be talking about a case where the Backup completed
successfully but the restore was corrupted.

That is terribly distrurbing, although it plays into my
standard advice that if you have not actually TESTED
your backups you cannot truth them.

I have been continuously shocked over the years by all
the people with good intentions who religiously made
backups (they seldom if every used), only to find that
when needed the backups were worthless.

 

[Guest]

The backups have all been done with a domain admin account. The problem is
not that the backups are not successful, as I can verify all of the data is
restored properly. The problem is only with making the data authoritative.
The authoritative restore using ntdsutil says it runs successfully, but when
rebooting into AD, the data from the other servers gets replicated over my
restore.

 

[Herb Martin]

The backups have all been done with a domain admin account. The problem is
not that the backups are not successful, as I can verify all of the data is
restored properly. The problem is only with making the data authoritative.
The authoritative restore using ntdsutil says it runs successfully, but when
rebooting into AD, the data from the other servers gets replicated over my
restore.

If it has been some time since the backups were made OR
you have previously used NTDSUtil (since the backup) then
you might double check the "verinc" switch to bump the
INCREMENT high on the update numbers.

Note: I originally thought this was a "bad backup/restore" problem
(as perhaps others did) and not a failure to do the authoritative
marking.

Suggestion: read chapter 9 of the Distributed Systems Resource
Kit Guide (Win2000 Server ) and follow the procedure exactly.

 

[Hotwires]

Try this 3rd party product, does a object level restore
and has a wizard for doing a complete authorative restore.

http://wm.quest.com/products/recoverymanagerad/