| Table of Contents |
|---|
Introduction
Dbvisit Standby’s new Network Layer is one of the exciting new features introduced in Dbvisit Standby version 7. Dbvnet’s functionality removes the dependency earlier Dbvisit Standby versions had on SSH for providing network communication between the primary and standby nodes. By making use of Dbvnet no additional SSH software is required to be installed, configured or maintained on Windows. When using UNIX based systems, Dbvisit Standby can now be configured to make use of the new Dbvnet (default option) or if required, SSH is still fully supported by Dbvisit Standby and can be configured and used on Unix based systems only. Password-less SSH authentication must be enabled between the primary and standby nodes if using Dbvisit Standby with SSH as communication layer.
| Note |
|---|
On Linux (UNIX) based systems, SSH can still be used for communication and file transfer between the primary and standby server. If your network has regular disconnects or is unstable - using SSH is recommended. To revert back to using SSH, ensure that SSH_PORT=22 is specified (SSH user equivalence between the primary and standby must be enabled - passwordless authentication using keys) To disable DBVNET and Enable SSH, the DBVNET_PORT is set to an empty (NULL) value in the DDC file: DBVNET_PORT= Important: This option of using SSH is not available for Windows based systems. Windows based systems must use Dbvnet. |
...
- To perform a basic status check which confirms that the primary and standby server can communicate using Dbvnet:
- dbvnet-test [-s|--status] SERVER[:PORT]
- dbvnet-test [-s|--status] SERVER[:PORT]
- To perform a more detail check, testing network connectivity, you can run the following:
- dbvnet-test [-f|--fulltest] SERVER TMPDIR SERVER:PORT
In the example below, dbvlin101 is the primary server and dbvlin102 is the standby server. Dbvisit Standby was installed using default values and no additional configuration has been performed at this stage. Dbvnet and Dbvserver is running on both nodes, but only Dbvnet is required and used for these tests:
...
You need to review the banner size (lines) and you can specify: SSH_SKIP_OUTPUT_LINES in the Dbvisit Standby DDC file to tell Dbvisit Standby to ignore these lines.
Example if the SSH Banner looks like this one below, we can see 3 lines are used:
| No Format |
|---|
######################### # This is server X ######################### |
...
To tell Dbvisit Standby to ignore this banner, set the following value in the DDC file:
| No Format |
|---|
SSH_SKIP_OUTPUT_LINES=3 |
...