Mirroring DMSII Audit Files

Note: Mirroring is available as an additional Enterprise Server component and requires special licensing. Contact your sales representative for details.

After you have loaded a dump of a DMSII database to a secondary MCP host computer, you can propagate or "mirror" audit files from the primary computer through Enterprise Server to the secondary computer using audit file mirroring. After an audit file has been mirrored, you can use the standard DMSII recovery techniques to recover through the audit file and apply the changes to the secondary database. Because the audit files are first mirrored to the Enterprise Server environment, they are available even if the primary system is unusable. Mirroring in near real-time ensures that very few updates are lost in the case of a primary system failure.

There are two ways to mirror audit files for a configured source: from the DATABridge Enterprise graphical interface and from the command line. This procedure uses the graphical interface. The command line lets you specify a range of audit file numbers to be mirrored. For more information about mirroring audit files using the command line, see Command-Line Options.

To mirror audit files

  1. In the right pane of the DATABridge Enterprise window, right-click a base source and click Properties.
  2. In the Base Source Properties dialog box, click the Audit Mirror button.
  3. In the Audit Mirroring Properties dialog box, select the appropriate settings, and then click OK twice to close the Audit Mirroring Properties and the Base Source Properties dialog boxes.
  4. Click Save to record your new configuration.
  5. To mirror audit files for a configured source, right-click the Enterprise Server source, and select Start mirroring audit files.
  6. To configure the secondary DATABridge host, load the sample control file (DATA/AUDITMIRROR/SAMPLE/CONTROL) and save a copy as DATA/AUDITMIRROR/databasename/CONTROL.
  7. In the sample control file, modify the parameters described in the following table to reflect your installation. (See the sample configuration file in this section.)




    SOURCE name in Enterprise Server


    Hostname or IP address of the Enterprise Server computer


    Port number where the DBDirector service listens (for example, 5100)

    AUDIT "targetPath" on "pack"

    For targetPath and pack, type the directory path and pack on the secondary system where DBAuditMirror will write audit files it receives from Enterprise Server. The mirrored audit file will be created under the usercode that runs DBAuditMirror.


    Number of seconds to pause between retry attempts.

    MAXWAIT maxwait

    Maximum wait for additional audit updates before quitting. If maxwait is set to FOREVER, the host will retry indefinitely.

    The mirrored audit file will be created under the usercode running DBAuditMirror.

  8. On the secondary system, start DBAuditMirror

    START WFL/DATABRIDGE/AUDITMIRROR("databasename" [, ["logicaldbname"] [, startAFN[, endAFN]]])

    where databasename is the name of the secondary database. Optionally, you can include a logical database name as a second parameter, and can specify a starting and ending audit file number range as third and fourth parameters. If you want to specify a starting AFN but not a logical database name, include the comma where the logical database name would go and immediately follow it with another comma before the startAFN. For example:


    For additional details, view WFL/DATABRIDGE/AUDITMIRROR.