• Controlling the number of active databases

    By Iain Chapman 1 decade ago

    Hi,



    OS: Windows Server 2003 SP2 x64

    Domino: Domino R8.5 FP1 x86

    DominoDefrag: 1.7 x86



    Decided to try this DominoDefrag out on a test server. Put the necessary files in place, and then called the routine using:



    load dominodefrag mail.



    Hence, software ran with it's defaults, and I told it to look at the Mail subfolder.



    Routine started, and announced on the Domino console that it was defragging a mailbox, and then moved onto the next. On each database it announced that it was defragging the database.



    On closer inspection, in the background more and more CMD and CONTIG tasks were being fired up until such time as the system stopped responding.



    Did I miss a setting or similar that would make it so that it can only handle xx number of databases at any given time?.



    It just seemed to be working thru my list of mailboxes trying to defrag them all in one hit.



    Example from the log.nsf:





    > load dominodefrag mail

    19/10/2009 11:57:09 DominoDefrag: v1.7 (16 Sep 2009)

    19/10/2009 11:57:09 DominoDefrag: Initializing…

    19/10/2009 11:57:09 DominoDefrag: Running on Windows 5.2.3790.Service Pack 2

    19/10/2009 11:57:09 DominoDefrag: Running on Domino 359

    19/10/2009 11:57:09 DominoDefrag: Using contig.exe 1.55

    19/10/2009 11:57:09 DominoDefrag: 32bit version running on 32bit platform

    19/10/2009 11:57:09 DominoDefrag: Directory -> mail

    19/10/2009 11:57:09 DominoDefrag: Process Full Text Index -> Off

    19/10/2009 11:57:09 DominoDefrag: DominoDefrag_MinuteInterval parameter not found. Task will only run once

    19/10/2009 11:57:09 DominoDefrag: DominoDefrag_StartPoint not found. Defaulting to 2

    19/10/2009 11:57:09 DominoDefrag: Verbose Logging -> Off

    19/10/2009 11:57:09 DominoDefrag: Compact Database Before Defrag -> Off

    19/10/2009 11:57:09 DominoDefrag: Initialization complete

    19/10/2009 11:57:10 DominoDefrag: mail\aaylett.nsf Defragging

    19/10/2009 11:57:10 DominoDefrag: mail\abirch.nsf Defragging

    19/10/2009 11:57:10 DominoDefrag: mail\achiron.nsf Defragging

    19/10/2009 11:57:11 DominoDefrag: mail\acoates.nsf Defragging

    19/10/2009 11:57:11 DominoDefrag: mail\aconway.nsf Defragging

    19/10/2009 11:57:11 DominoDefrag: mail\acook.nsf Defragging

    19/10/2009 11:57:12 DominoDefrag: mail\admansfie.nsf Defragging

    19/10/2009 11:57:12 DominoDefrag: mail\adorr.nsf Defragging

    19/10/2009 11:57:13 DominoDefrag: mail\adykes.nsf Defragging

    19/10/2009 11:57:13 DominoDefrag: mail\aflewell.nsf Defragging

    19/10/2009 11:57:14 DominoDefrag: mail\afulford.nsf Defragging

    19/10/2009 11:57:14 DominoDefrag: mail\ahill.nsf Defragging

    19/10/2009 11:57:15 DominoDefrag: mail\ahunt.nsf Defragging

    19/10/2009 11:57:15 DominoDefrag: mail\airwin.nsf Defragging

    19/10/2009 11:57:16 DominoDefrag: mail\akuck.nsf Defragging

    19/10/2009 11:57:17 DominoDefrag: mail\alefedji.nsf Defragging

    19/10/2009 11:57:18 DominoDefrag: mail\amansfie.nsf Defragging

    19/10/2009 11:57:19 DominoDefrag: mail\amariaud.nsf Defragging

    19/10/2009 11:57:20 DominoDefrag: mail\amitchel.nsf Defragging

    19/10/2009 11:57:21 DominoDefrag: mail\araffy.nsf Defragging

    19/10/2009 11:57:22 DominoDefrag: mail\arawicz.nsf Defragging

    19/10/2009 11:57:23 DominoDefrag: mail\arussell.nsf Defragging

    19/10/2009 11:57:24 DominoDefrag: mail\askinner.nsf Defragging

    19/10/2009 11:57:25 DominoDefrag: mail\asparks.nsf Defragging

    19/10/2009 11:57:26 DominoDefrag: mail\asu.nsf Defragging

    19/10/2009 11:57:27 DominoDefrag: mail\athiol.nsf Defragging

    19/10/2009 11:57:28 DominoDefrag: mail\awatts.nsf Defragging



    I'd have thought that it would call CONTIG.EXE and wait for it to terminate before it moved onto the next database. Having done another test on a single database, I noted that the log showed:





    > load dominodefrag mail\ichapman.nsf

    19/10/2009 12:23:19 DominoDefrag: v1.7 (16 Sep 2009)

    19/10/2009 12:23:19 DominoDefrag: Initializing…

    19/10/2009 12:23:19 DominoDefrag: Running on Windows 5.2.3790.Service Pack 2

    19/10/2009 12:23:20 DominoDefrag: Running on Domino 359

    19/10/2009 12:23:20 DominoDefrag: Using contig.exe 1.55

    19/10/2009 12:23:20 DominoDefrag: 32bit version running on 32bit platform

    19/10/2009 12:23:20 DominoDefrag: File -> mail\ichapman.nsf

    19/10/2009 12:23:20 DominoDefrag: Process Full Text Index -> Off

    19/10/2009 12:23:20 DominoDefrag: DominoDefrag_MinuteInterval parameter not found. Task will only run once

    19/10/2009 12:23:20 DominoDefrag: DominoDefrag_StartPoint not found. Defaulting to 2

    19/10/2009 12:23:20 DominoDefrag: Verbose Logging -> Off

    19/10/2009 12:23:20 DominoDefrag: Compact Database Before Defrag -> Off

    19/10/2009 12:23:20 DominoDefrag: Initialization complete

    19/10/2009 12:23:21 DominoDefrag: mail\ichapman.nsf Defragging

    19/10/2009 12:23:21 DominoDefrag: Total databases to be processed -> 1

    19/10/2009 12:23:21 DominoDefrag: Total databases defragged -> 1

    19/10/2009 12:23:21 DominoDefrag: Total databases already defragged -> 0

    19/10/2009 12:23:21 DominoDefrag: Total databases below start point -> 0

    19/10/2009 12:23:21 DominoDefrag: Total databases with not enough disk space to defrag -> 0

    19/10/2009 12:23:21 DominoDefrag: Total databases compacted before defrag -> 0

    19/10/2009 12:23:21 DominoDefrag: Termination complete



    Which, suggest it's finished, and yet the CMD.EXE and CONTIG.EXE tasks were still active according to Task Manager after the "Termination complete" message.





    Thanks



    Iain

    • try new version 1.8

      By Andrew Luder 1 decade ago

      I've used task manager to watch contig.exe and cmd.exe on many servers and never seen multiple instances occur when DominoDefrag is running. The proper behaviour is to close the instance of contig.exe before proceeding to the next database.



      In this version I've stopped using cmd.exe to invoke contig.exe, so hopefully this will make a difference on your test server.