• Problem defragging the DAOS directory

    By Jef Debacker 1 decade ago

    Hello,

    We run DominoDefrag 2.4.4 (an older version, I know) on all of our Domino 8.5.2 mail servers. It's scheduled to run weekly.
    All of our mail servers are enabled for DAOS.

    On one of them, DominoDefrag  seems to skip the DAOS directory, even though it is configured to process it..
    I checked for configuration differences, at the Domino and DominoDefrag level, but found none.

    Has anyone an idea what might be wrong?
    Your help is appreciated.

    Jef


    Here' an extract from the log.nsf of the server that skips DAOS:
    Note that is says, just before terminating, "DominoDefrag: D:\DAOS DAOS Defrag already being processed"

    2012-02-12 19:00:38   Running Program document for 'DominoDefrag'
    2012-02-12 19:00:39   DominoDefrag: v2.4.4 (23 May 2010 C++ API version)
    2012-02-12 19:00:39   DominoDefrag: Initializing...
    2012-02-12 19:00:39   DominoDefrag: Running on Windows 6.1.7600.
    2012-02-12 19:00:39   DominoDefrag: Running on Domino 379
    2012-02-12 19:00:39   DominoDefrag: Using contig.exe 1.55
    2012-02-12 19:00:39   DominoDefrag: 32bit version running on 64bit platform
    2012-02-12 19:00:39   DominoDefrag: DominoDefrag_Directory parameter not found. Defaulting to data directory
    2012-02-12 19:00:39   DominoDefrag: Directory -> d:\lotus\domino\data
    2012-02-12 19:00:39   DominoDefrag: Process Full Text Index -> On
    2012-02-12 19:00:39   DominoDefrag: DominoDefrag_MinuteInterval parameter not found. Task will only run once
    2012-02-12 19:00:39   DominoDefrag: Run Time -> 720
    2012-02-12 19:00:39   DominoDefrag: Start Point -> 10
    2012-02-12 19:00:39   DominoDefrag: Verbose Logging -> Off
    2012-02-12 19:00:39   DominoDefrag: Compact Database Before Defrag -> Off
    2012-02-12 19:00:39   DominoDefrag: Transaction Log -> Off
    2012-02-12 19:00:39   DominoDefrag: DAOS -> On. Will defrag directory D:\DAOS
    2012-02-12 19:00:39   DominoDefrag: Performance Check  -> Off
    2012-02-12 19:00:39   DominoDefrag: Initialization complete
    ...

    2012-02-13 00:25:30   DominoDefrag: D:\DAOS DAOS Defrag already being processed
    2012-02-13 00:25:30   DominoDefrag: Total databases to be processed -> 2136
    2012-02-13 00:25:30   DominoDefrag: Total databases defragged -> 482
    2012-02-13 00:25:30   DominoDefrag: Total databases partially defragged -> 0
    2012-02-13 00:25:30   DominoDefrag: Total databases already defragged -> 340
    2012-02-13 00:25:30   DominoDefrag: Total databases below start point -> 1313
    2012-02-13 00:25:30   DominoDefrag: Total databases with not enough disk space to defrag -> 0
    2012-02-13 00:25:30   DominoDefrag: Total databases with no access to defrag -> 0
    2012-02-13 00:25:30   DominoDefrag: Total full-text indexes defragged -> 19
    2012-02-13 00:25:30   DominoDefrag: Total full-text indexes partially defragged -> 0
    2012-02-13 00:25:30   DominoDefrag: Total full-text indexes already defragged -> 7
    2012-02-13 00:25:30   DominoDefrag: Total full-text indexes below start point -> 98
    2012-02-13 00:25:30   DominoDefrag: Total full-text indexes with not enough disk space to defrag -> 0
    2012-02-13 00:25:30   DominoDefrag: Total DAOS files to be processed -> 0
    2012-02-13 00:25:30   DominoDefrag: Total DAOS files defragmented -> 0
    2012-02-13 00:25:30   DominoDefrag: Average DAOS before fragments -> 0
    2012-02-13 00:25:30   DominoDefrag: Average DAOS after fragments -> 0
    2012-02-13 00:25:30   DominoDefrag: Termination complete
     

     

    And here's an extract from log.nsf of one of our other servers where the DAOS directory is properly processed:
    Note that the startup sequence reports identiacl values, proving (I think) that the configuration is identical too.

    2012-02-12 19:00:12   Running Program document for 'DominoDefrag'
    2012-02-12 19:00:13   DominoDefrag: v2.4.4 (23 May 2010 C++ API version)
    2012-02-12 19:00:13   DominoDefrag: Initializing...
    2012-02-12 19:00:13   DominoDefrag: Running on Windows 6.1.7600.
    2012-02-12 19:00:13   DominoDefrag: Running on Domino 379
    2012-02-12 19:00:13   DominoDefrag: Using contig.exe 1.55
    2012-02-12 19:00:13   DominoDefrag: 32bit version running on 64bit platform
    2012-02-12 19:00:13   DominoDefrag: DominoDefrag_Directory parameter not found. Defaulting to data directory
    2012-02-12 19:00:13   DominoDefrag: Directory -> d:\lotus\domino\data
    2012-02-12 19:00:13   DominoDefrag: Process Full Text Index -> On
    2012-02-12 19:00:13   DominoDefrag: DominoDefrag_MinuteInterval parameter not found. Task will only run once
    2012-02-12 19:00:13   DominoDefrag: Run Time -> 720
    2012-02-12 19:00:13   DominoDefrag: Start Point -> 10
    2012-02-12 19:00:13   DominoDefrag: Verbose Logging -> Off
    2012-02-12 19:00:13   DominoDefrag: Compact Database Before Defrag -> Off
    2012-02-12 19:00:13   DominoDefrag: Transaction Log -> Off
    2012-02-12 19:00:13   DominoDefrag: DAOS -> On. Will defrag directory D:\DAOS
    2012-02-12 19:00:13   DominoDefrag: Performance Check  -> Off
    2012-02-12 19:00:13   DominoDefrag: Initialization complete
    ...

    2012-02-13 03:33:11   DominoDefrag: Total databases to be processed -> 2027
    2012-02-13 03:33:11   DominoDefrag: Total databases defragged -> 481
    2012-02-13 03:33:11   DominoDefrag: Total databases partially defragged -> 0
    2012-02-13 03:33:11   DominoDefrag: Total databases already defragged -> 296
    2012-02-13 03:33:11   DominoDefrag: Total databases below start point -> 1250
    2012-02-13 03:33:11   DominoDefrag: Total databases with not enough disk space to defrag -> 0
    2012-02-13 03:33:11   DominoDefrag: Total databases with no access to defrag -> 0
    2012-02-13 03:33:11   DominoDefrag: Total full-text indexes defragged -> 41
    2012-02-13 03:33:11   DominoDefrag: Total full-text indexes partially defragged -> 0
    2012-02-13 03:33:11   DominoDefrag: Total full-text indexes already defragged -> 12
    2012-02-13 03:33:11   DominoDefrag: Total full-text indexes below start point -> 86
    2012-02-13 03:33:11   DominoDefrag: Total full-text indexes with not enough disk space to defrag -> 0
    2012-02-13 03:33:11   DominoDefrag: Total DAOS files to be processed -> 1691404
    2012-02-13 03:33:11   DominoDefrag: Total DAOS files defragmented -> 25
    2012-02-13 03:33:11   DominoDefrag: Average DAOS before fragments -> 1
    2012-02-13 03:33:11   DominoDefrag: Average DAOS after fragments -> 1
    2012-02-13 03:33:11   DominoDefrag: Termination complete
     

    • Check for DominoDefrag lock files

      By Andrew Luder 1 decade ago

      Hi Jef,



      check for existance of any DominoDefrag lock files (have extension ".dd") in the Domino program folder and manually remove them. A lock file is created before a folder or file being defragged and removed after completion. This allows multiple dominodefrag server tasks to run at the same time on the server and a message ending with "….already being processed" will appear when a task tries to defrag a file or folder already being defragged.



      In older DominoDefrag versions there was a bug that would intermittently leave them behind. So you will probably have a file in your program directory called "ddaos.dd" - just manually remove it and will be ok for next run.

      • DD_ProcessingDAOS=1

        By Jef Debacker 1 decade ago

        Hi Andrew,

        There was no ddaos.dd file to be found on this server.
        There was one other *.dd file though, but it was associated with a single DB. Removing that one did not help.

        However I found an undocumented line in the server's notes.ini: DD_ProcessingDAOS=1
        A quick checking on our other mail servers showed that this line is present on every one of them, but mostly with a value of 0.
        Only two other servers showed a value of 1. This first server also refused to defrag DAOS files (same lines found in the log), while the other one timed out before it completed defragging the Notes DBs.

        Anyway, I've reset DD_ProcessingDAOS=0 on these 3 servers, and we'll see after the weekend where it brings us.
        I guess this value=1 must be a left-over from a run that was interrupted by a crash or reboot without halting Domino first.