...
It is recommended that when you perform a restart of the full stack (Dbvnet and Dbvserver) that you perform them in the following order.
| Note | ||
|---|---|---|
| ||
| Note | ||
Dbvnet must be running on both primary and standby servers to allow Dbvisit Standby version 7 to communicate and transfer files between the two nodes. |
It is recommended that you ensure your Dbvisit Schedules are stopped when performing a restart of the Dbvisit Standby stack (Dbvserver and Dbvnet). This include disabling cron schedules if they are used. |
Step 1: Stop Dbvserver (Dbvisit Standby Web Based Interface)
The following command is executed to stop the Dbvserver process. (note the stop command does not return any output and once executed you will be returned to a new line)
| No Format |
|---|
cd /usr/dbvisit/dbvserver ./dbvserverd stop |
...
Step 2: Stop Dbvnet (Dbvisit Standby Network Communication)
The following command is executed to stop the Dbvserver process. (note the stop command does not return any output and once executed you will be returned to a new line)
...
| No Format |
|---|
cd /usr/dbvisit/dbvserver rm log/* ./dbvserverd start |
...
Step 6: Review processes are running
The final step is to confirm that Dbvnet and Dbvserver are running.
...
For Dbvnet troubleshooting and testing tips, please see here
For Dbvserver, please make sure that there is no firewall blocking your connection to the default port 8443 used. If you are using Linux IPTables, please make sure this port is open (review as root user the output of: "iptables -L" command and your configuration in /etc/sysconfig/iptables)
...