Re: Restore ADAM Instance

Tech-Archive recommends: Fix windows errors by optimizing your registry

As part of the restore, it's appropriate to delete the files you're going to
restore. More specifically:
Restoring ADAM
When you restore a database to an existing ADAM instance, you must stop the
ADAM instance before you run the restore operation. In addition, it is
recommended that you move (or delete) the existing database and log files
from the ADAM instance before the restore operation.






"Doug" <kolpekdb@xxxxxxxxxxxx> wrote in message
news:1128606243.765393.202200@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> No. What files on which server?
>
> Doug
>
> Al Mulnick wrote:
>> One other question: did you remove the files prior to the restore?
>> In order to see what you're seeing, I'll have to recreate that
>> scenario...
>>
>> Al
>>
>> "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: Can not see Services in Configuration Context in ADAM
    ... What account are you using as the ADAM administrator? ... If you restore the backup to a clean install of ADAM ...
    (microsoft.public.windows.server.active_directory)
  • Re: Can not see Services in Configuration Context in ADAM
    ... you can see the full configuration NC of the ADAM instance? ... This is the process I used to backup and restore the ADAM instance to ...
    (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: ADAM app partition restore
    ... Do you see anything of interest in the ADAM instance event log? ... Is the application partition listed in the namingContexts on the rootDSE ... > and restore to a completly different server in order to provide a staging ...
    (microsoft.public.windows.server.active_directory)
  • Re: Restoring an ADAM Instance
    ... installing ADAM is only required if you reinstall the server, ... In your case if you restore ADAM you will always go back in time and loose the data/changes that were processed after the backup was created ...
    (microsoft.public.windows.server.active_directory)