ADAM Server and Event ID: 2089

Discussion in 'Active Directory' started by jskalicky, Feb 17, 2008.

  1. jskalicky

    jskalicky Guest

    I am getting Event ID 2089 generated in the ADAm event LOg. I am running ADAM
    on a workgroup server not connected to a domain and I have only one instance
    of it no replica's. I am backing the ADAM directory up everyday as specified
    in the "ADAM Step by Step guide" from MS. I am using NTBackup to do the
    backup but am still receiving the event ID 2089. Any help would be
    appreciated..
     
    jskalicky, Feb 17, 2008
    #1
    1. Advertisements

  2. Looks like you are already working with PSS on this issue (they pinged me).
    By the looks of it, ADAM backups are not really taking place -- you should
    chase this down. Check for any errors/warnings during backup, and also at
    ADAM startup time.

    --
    Dmitri Gavrilov
    SDE, Exchange

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm
     
    Dmitri Gavrilov [MSFT], Feb 19, 2008
    #2
    1. Advertisements

  3. jskalicky

    jskalicky Guest

    Dmitri,

    I am working with PSS on this. This is what is going on. I do not see any
    errors upon startup or during the backup of the ADAm directory. The
    dsasignature attribute has a value in it though. PSS is thinking that that is
    the culprit. Please advise...
     
    jskalicky, Feb 19, 2008
    #3
  4. DsaSignature should be updated during each backup. You can verify this is
    taking place using repadmin /showObjMeta on the NC head object. The fact
    that the value was not updated since November (in your case) is triggering
    2089s (ADAM thinks backups are not happening).

    Can you verify if the backups are good? I.e. that you can restore ADAM data
    too?

    Lee Flight is also noticing this behavior (dsaSignature is not getting
    updated) -- I wonder if something got broken in backup around SP2. I
    notified AD folks.

    --
    Dmitri Gavrilov
    SDE, Exchange

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm
     
    Dmitri Gavrilov [MSFT], Feb 19, 2008
    #4
  5. jskalicky

    jskalicky Guest

    Dmitri,

    I restored our ADAM server today and ADAM data is OK. So, it looks like our
    backups are OK. I am still receiving the 2089 warning messages though. I
    deleted the value from the dsasignature attribute on both the app partition
    and the configuration partition on my restored server as per PSS. In regard
    tot he 2089 message - will ADAM tombstone all of the objects in my directory
    if it is not backed up in the 180 day interval? Please advise...
     
    jskalicky, Feb 19, 2008
    #5
  6. Your database is fine, don't worry. Nothing will be tombstoned, and ADAM
    will continue functioning normally, and your data will be fine. Don't worry
    about this.
    There's something not right about the backup however. I am not sure how
    usable it is. When you restored, did you verify that your data actually went
    back in time?

    Anyway, we have people looking into this from PSS side.

    --
    Dmitri Gavrilov
    SDE, Exchange

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm
     
    Dmitri Gavrilov [MSFT], Feb 20, 2008
    #6
  7. jskalicky

    jskalicky Guest

    Dmitry,

    I checked the backup and it looks OK. Also, I deleted the value out of the
    dsasignature attribute in the directory for each partition on my restored
    ADAM server - the app partition, configuration and schema partitions. I
    stopped getting the event id - 2089 generated. I then took a full backup of
    the server and checked the dsasignature attribute and it was not set. So, it
    looks like this is a bug with ntbackup and R2? Please advise...
     
    jskalicky, Feb 21, 2008
    #7
  8. Yes, I think it's a bug, most likely in ADAM VSS writer.
    By deleting the dsaSignature values, you updated attribute metadata. ADAM
    determines the time of last backup by looking at this metadata. So,
    currently ADAM thinks that you just did your backup. But in 90 days (or
    whatever your half-TSL is) it will start complaining again.

    I guess you can prevent generation of these events by touching dsaSignature
    values manually after each backup. However, I'd rather have this problem
    investigated and fixed. Please keep the pressure on PSS so that they get to
    the bottom of this.

    --
    Dmitri Gavrilov
    SDE, Exchange

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm
     
    Dmitri Gavrilov [MSFT], Feb 22, 2008
    #8
  9. jskalicky

    jskalicky Guest

    Dmitry,

    We are going ot be applying some patches this weekend to our production ADAM
    server that is exhibiting the 2089 issue. They are 943484 and 931374. Would
    you recommend that it is OK to apply these patches considering the state of
    ADAM on my server or should we hold off applying them until this issue is
    resolved? Please advise...
     
    jskalicky, Feb 22, 2008
    #9
  10. You should apply the patches.

    --
    Dmitri Gavrilov
    SDE, Exchange

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm
     
    Dmitri Gavrilov [MSFT], Feb 24, 2008
    #10
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.