Re: Restore ADAM Instance



?? 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
    ... 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: Replication failure after restore
    ... "Hii Sing Chung" < I restored a Windows 2000 DC from a most recent ghost image, but it cannot replicate to and from other DCs. ... The DC within the same site gives the "target principal name is incorrect" when trying to replicate to this restore DC. ... Just less than a week ago I did forestprep and domainprep to my Windows 2000 domain so as to allow a Windows 2003 server to be promoted to DC into this domain. ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication failure after restore
    ... "Hii Sing Chung" < I restored a Windows 2000 DC from a most recent ghost image, but it cannot replicate to and from other DCs. ... The DC within the same site gives the "target principal name is incorrect" when trying to replicate to this restore DC. ... Just less than a week ago I did forestprep and domainprep to my Windows 2000 domain so as to allow a Windows 2003 server to be promoted to DC into this domain. ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication failure after restore
    ... "Hii Sing Chung" < I restored a Windows 2000 DC from a most recent ghost image, but it cannot replicate to and from other DCs. ... The DC within the same site gives the "target principal name is incorrect" when trying to replicate to this restore DC. ... Just less than a week ago I did forestprep and domainprep to my Windows 2000 domain so as to allow a Windows 2003 server to be promoted to DC into this domain. ...
    (microsoft.public.win2000.active_directory)
  • Re: Restore ADAM Instance
    ... Replicate delete to B ... Auth restore B ... replicate the delete to B. I'd expect there to be a collision when it hit B ...
    (microsoft.public.windows.server.active_directory)

Loading