Error Message

This is due to settings in the Content.xml files being being misread, which prevents communications to the Dedupe server.

To resolve this issue, the attached DLO_Config_Utility.exe utility needs to be run on the machines where the Dedupe Server and IO Server components are installed.
Note: The utility can also be downloaded as a Hotfix package from the VEMS portal or SORT server.

• If the Dedupe Server and IO Server are installed on the same machine, then run the utility once on that server
• If the Dedupe Server(s) and IO Server are installed on different machines, then run the utility on those machines

Note: It is mandatory to run this utility, following an upgrade to DLO 9.3.2 or a new installation.

Steps to run the utility:
The utility should be run on the machines where the Dedupe Server or IO Server are installed in a DLO setup.

1. Save the attached DLO_Config_Utility.zip to the servers where the Dedupe Server and\or IO Server is installed. Extract that zip file to a temporary directory.
2. In the DLO Administration Console, go to Tools > Blackout Windows menu option
3. Configure a blackout window for the DLO Server to be 'on a specific date', set to be the current time & date and to run for a period of 20-30 min (depends how many servers you need to run the utility on). This ensures that no user backups run during this process.
4. Once the Blackout Window is active, Double click on the utility DLO_Config_utility.exe

Note: This is a silent installation and requires approximately 4 mins for execution.

Steps to verify the utility has run successfully are as follows:

Please ensure that the context.xml file in the following paths are updated.

• For Dedupe Server path:

\Dedupe\Tomcat\webapps\DedupeServer\META-INF
i.e. default path is C:\Program Files\Veritas\Veritas DLO\Dedupe\Tomcat\webapps\DedupeServer\META-INF

• For IO Server path:

\IOServer\Tomcat\webapps\DLOServer\META-INF
i.e. default path is C:\Program Files\Veritas\Veritas DLO\IOServer\Tomcat\webapps\DLOServer\META-INF

The Context.xml file parameters should be now be updated, as detailed below

maxActive  ->  maxTotal
maxWait   ->  maxWaitMillis
removeAbandoned   ->  removeAbandonedOnBorrow

Original Content.XML :
maxActive="1000" maxIdle="30" maxWait="10000" factory="com.middleware.db.DBConnectionPoolFactory"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" removeAbandoned="true"

Updated Content.XML :
maxTotal="1000" maxIdle="30" maxWaitMillis="10000" factory="com.middleware.db.DBConnectionPoolFactory"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" removeAbandonedOnBorrow="true"