none
none
To resolve this issue:
Steps to be followed on Node 1:
1. Delete the Edge Server and IO Servers on the DLO Console. Configure the Edge Server and IO Servers using the common hostname of the DLO Cluster.
2. Update context.xml file present in the DLO install path (E.g.: c:\Program files\Veritas\VeritasDLO\IOServer\Tomcat\webapps\DLOServer\META-INF\) with the common hostname of DLO Cluster as Server name.
3. Assign the IO Server to the storage location.
4. Update httpd.conf files with common IP address/common hostname/certificate name.
Update below lines in httpd.conf file present in the path C:\Program Files\Apache Software Foundation\Apache24\Conf\,
• hostname with common IP address of DLO Cluster
•
• ServerName common IPaddress
5. Restart Veritas DLO Web and Veritas DLO Edge Server Services.
6. Update the Edgeserver.ini file with the common hostname of DLO Cluster on the server machine, in the below paths:
Steps to be followed on other nodes:
1. Power off the Active node.
2. Update context.xml file present in the install path (E.g. C:\Program Files\Veritas\Veritas DLO\IOServer\Tomcat\webapps\DLOServer\META-INF\) with the common hostname of DLO Cluster as Server name.
3. Unassign the IO Server which was assigned to the storage location, and reassign again.
4. Update httpd.conf files with common IP address/common hostname/certificate name.
Update below lines in httpd.conf file present in the path C:\Program Files\Apache Software Foundation\Apache24\Conf\
• hostname with common IP address of DLO Cluster
•
• ServerName common IPaddress
5. Restart Veritas DLO Web and Veritas DLO Edge Server Services.
Notes:
1. If a SSL certificate is used for Edge Server, use the same certificate for all the nodes.
2. In case the DLO Desktop Agents are already installed, download the Edgeserver.ini and dloclient.pem files from the Web restore portal and replace them in the Install path of the DLO Agent.
Product version:
DLO 9.1