locked
Forefront UAG ADAM Error following Server Restore RRS feed

  • Question

  • Hi All,

    We are currently running a two node Forefront UAG 2010 Array, (SP1, Update 1, Rollup 1) following running Operating System Updates on one of the nodes (the B node - Array Member) The server crashed after restarting while configuring updates. We've had to do a full restore of the Array Member. Active Directory Lightweight Directory Services (ADAM) is reporting the ADM_ISASTGCTRL service is stopped, and the following is reported in the events:

    'The Directory Server detected that the database has been replaced. This is an unsafe and unsupported operation. The service will stop until the problem is corrected.

    User Action:

    Restore the previous copy of the database that was in use on this machine. In the future, the user is strongly encouraged to use the backup and restore facility to rollback the database.

    This error can be suppressed and the database repaired by removing the following registry key.

    System\CurrentControlSet\Services\ADAM_ISASTGCTRL\Parameters'

    The Array member is still a member of the array, would reactivating the Forefront UAG configuration resync this?

    Thanks

    Chris

    


    http://chrisocallaghan.blogspot.com/


    Friday, May 4, 2012 2:16 PM

Answers

  • It may do (easy to try), but you may have to disjoin the array and rejoin again.

    You may also have to fix the ADAM issue first by deleting the DSA Database Epoch value name under the System\CurrentControlSet\Services\ADAM_ISASTGCTRL\Parameters key.

    Cheers

    JJ


    Jason Jones | Forefront MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk

    Friday, May 11, 2012 12:03 AM
  • Hi Jason,

    Thanks for replying. We raised the issue with Microsoft, the server was restored using Symantec Netbackup which did an over the top restore of the ADLDS instance (not a supported method http://technet.microsoft.com/en-us/library/cc725665(v=WS.10).aspx )

    Which caused the database engine's checksum to report the error, and stop the service from running. As we knew the database was the version we wanted, we removed the registry key as per above and it resolved the issue.


    http://chrisocallaghan.blogspot.com/

    Tuesday, May 15, 2012 9:43 AM

All replies