This KB article: CA Directory - DSA out of sync explains how to synchronize out-of-sync DSA with its peers when multi-write-disp-recovery is enabled.
But the fact is that running dxdisp commands, as described in the above article, does not make any sense when DISP recovery is disabled (and an error is returned: No Multiwrite-DISP DSA was found).
So how do we synchronize when multi-write-disp-recovery is set to 'false' in DSA configuration ?
Note: disabling multi-write-disp-recovery is required, for instance, for SiteMinder session store: Configure Symantec Directory as a Session Store
The DSA recovery procedure in case of disabled multi-write-disp-recovery setting is similar to the procedure described in CA Directory - DSA out of sync KB article, but there are some differences.
Notes about the procedure:
Backup the data from the good DSA (in our example we use DSA1)
To do that run the following command in the command line on CADIR1 machine:
dxserver onlinebackup DSA1
Alternatively, you may open DXConsole on CADIR1 machine and run the following command
Please note that backup operation may take a while. You need to monitor the DSA's warning log (<DSA name>_warn_<date>.log) till the following message appears:
WARN : Dump completed, X fragments
The above 'dxserver onlinebackup' or DXconsole 'dump' commands will generate a file with DSA name and '.zdb' extension under 'dxserver/data' folder (dxserver/data/DSA1.zdb in our example)
Delete/Move all the DSA2 data files in 'dxserver/data' folder on CADIR2 machine (in our example DSA2.db, DSA2.tx files)
Note: .dp and .dx files, mentioned in the CA Directory - DSA out of sync KB article, are not created when DISP recovery is disabled
Copy the only DSA1.zdb file from 'dxserver/data' folder on CADIR1 machine to 'dxserver/data' folder on CADIR2 machine (do not copy DSA1.tx)
Rename DSA1.zdb file to DSA2.db on CADIR2 machine
Start DSA2 service.
Run the following command on CADIR2 machine:
dxserver start DSA2