Re: Restore ADAM Instance



Please confirm you followed the same steps:

1. Added a user in the directory called "BeforeBackup"
2. Backed up the instance <server1>
3. Added a user in the directory called "AfterBackup"
4. Removed the user "BeforeBackup"
5. Stopped ADAM instance <server1>
6. Restored the ADAM instance from backup

If you did and you are seeing both users after the restore, that makes
no sense. You should only see the BeforeBackup user because the
AfterBackup user was created AFTER the backup was taken. It sounds
like it's not working for you either. Are you certain you did step 4
above?

We just tried again and deleted the dit and log files before restoring
and had the exact same results as before. We are on Windows 2003
Server and we are also not restoring the Windows\ADAM files.


Al Mulnick wrote:
> Doug, I followed the exact same process with the following exceptions:
> 1) mine were both on the same machine - Windows XP
> 2) I deleted the dit and log files prior to restoration of the db.
> 3) I did not restore the windows/adam files. There was no need (note: you
> may not have either, but I needed to call that out in my test).
> 4) waited 20 minutes for the replication to take place.
>
> My results: Both accounts now exist in the directory in both instances.
>
> I'm not sure why you're getting different results at this point. Can you
> try again with the deletion of files and verify that you get the same
> results you had before?
>
>
> "Doug" <kolpekdb@xxxxxxxxxxxx> wrote in message
> news:1128541011.429000.301760@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Sure, here is what we did:
> >
> > NOTE: We have 2 ADAM servers <server1> and <server2> where <server2>
> > is a replica of <server1> and they are set for immediate replication.
> >
> > 1. Added a user in the directory called "BeforeBackup"
> > 2. Backed up the instance <server1>
> > 3. Added a user in the directory called "AfterBackup"
> > 4. Removed the user "BeforeBackup"
> > 5. Stopped ADAM instance <server1>
> > 6. Restored the ADAM instance from backup
> > 7. Opened ADAM command prompt
> > 8. typed: dsdbutil
> > 9. typed: activate instance <ourinstancename>
> > 10. typed: authoritative restore
> > 11. At the authoritative restore prompt typed: restore database
> > 12. When it was done, closed.
> > 13. Restarted ADAM instance
> >
> > When we viewed the ADAM directory with ADSI edit on that server the
> > data looked as it should showing that the BeforeBackup user was there
> > and the AfterBackup user was not. However, if we looked at the
> > directory on <server2> it is still showing AfterBackup and no
> > BeforeBackup user. Then moments later on the <server1> directory it
> > now started showing the AfterBackup user and not the BeforeBackup user.
> >
> > Are we missing something? Thanks.
> > Doug
> >
> > Al Mulnick wrote:
> >> ?? You did the restore and then marked some OU or object as
> >> authoritative
> >> using dsdbutil?
> >>
> >> Can you provide more details about what happened and what you expected to
> >> have happen?
> >>
> >>
> >> "Doug" <kolpekdb@xxxxxxxxxxxx> wrote in message
> >> news:1128527365.805731.54530@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> > The authoritative restore was what we ran, that's why we're confused at
> >> > the results.
> >> >
> >> > Doug
> >> >
> >> > Al Mulnick wrote:
> >> >> That would be the expected behavior. Here's why I say that: a restore
> >> >> is
> >> >> a
> >> >> point in time picture of the data. If you replicate data between
> >> >> servers,
> >> >> then both of them should theoretically be the same. If you then put a
> >> >> day
> >> >> old copy back into the synchronization fabric, it should bring itself
> >> >> up
> >> >> to
> >> >> date with the rest of the environment. That's referred to as backfill
> >> >> in
> >> >> JET terminology (JET being the underlying db technology being used.)
> >> >>
> >> >> It sounds like you want the authoritative restore. Here's some
> >> >> information
> >> >> on that procedure:
> >> >> http://technet2.microsoft.com/WindowsServer/en/Library/86f99639-f9f4-4b51-9175-e94b626285d11033.mspx
> >> >>
> >> >> Al
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> "Doug" <kolpekdb@xxxxxxxxxxxx> wrote in message
> >> >> news:1128521570.580075.34420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> >> > We have ADAM installed on 2 servers. The 2nd server we installed as
> >> >> > a
> >> >> > replica. We are trying to test out the backup/restore function and
> >> >> > are
> >> >> > following the steps related to backing up/restoring an ADAM instance
> >> >> > that belongs to a configuration set. Are these the correct steps?
> >> >> >
> >> >> > Does it matter which server we backup from/restore to?
> >> >> > Do we shut down both ADAM services or just the one we are restoring
> >> >> > to?
> >> >> > If we restore to one, will it replicate to the other or do we need
> >> >> > to
> >> >> > restore to both?
> >> >> >
> >> >> > We are getting the restore to work but then the other ADAM server
> >> >> > replicates back to the one we restored to.
> >> >> >
> >> >> > Thanks
> >> >> >
> >> >
> >

.



Relevant Pages

  • Re: Restore ADAM Instance
    ... is a replica of <server1> and they are set for immediate replication. ... Added a user in the directory called "BeforeBackup" ... Restored the ADAM instance from backup ... At the authoritative restore prompt typed: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Restore ADAM Instance
    ... did you remove the files prior to the restore? ... > is a replica of <server1> and they are set for immediate replication. ... Restored the ADAM instance from backup ... > data looked as it should showing that the BeforeBackup user was there ...
    (microsoft.public.windows.server.active_directory)
  • Re: Restore ADAM Instance
    ... Joe Richards Microsoft MVP Windows Server Directory Services ... When you auth restore something it restores the attributes and increases the metadata version number for the attributes such that they replicate out authoritatively. ... Since the backup had no knowledge of the afterbackup userid, it could have no impact on it in the rest of the directory and would replicate into the auth restored ADAM instance as soon as it was able to. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Backup/restore ADAM database
    ... ADAM instance should work. ... The instance you restore *should* be isolated from your production network ... Builtin Administrators security principal to the original ADAM instance ... Copy the backup file from machine1 to machine2. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD/ADAM (MS LDS) disaster recovery
    ... Depending on the size of your ADAM instance you might find it safer to take ... So if you lose the box follow AD restore procedures (do ... In short, for a only 1 DC AD environment, with ntbackup. ... I setup another test system on VM too. ...
    (microsoft.public.windows.server.active_directory)

Loading