Overview of Windows SSH connection
Dbvisit Standby uses Bitvise (www.bitvise.com) products to enable the transfer of archive log files between the primary and standby servers.
The components of Bitvise that are used are:
- WinSSHD this is a Windows service that runs in the background and accepts the connections.
- Tunnelier is an ssh client that initiates the connections and transfers the files.
Both products are installed and configured on the primary and standby servers.
For the connection between the primary server to the standby server, the following components are used:
- On the primary server, sftpc.exe (Tunnelier) is called which connects to WinSSHD on the standby server. WinSSHD on the standby server will be running as a Windows service.
For the connection between the standby server to the primary server, the following components are used:
- On the standby server, sftpc.exe (Tunnelier) is called which connects to WinSSHD on the primary server. WinSSHD on the primary server will be running as a Windows service.
The copy command that Dbvisit Standby uses from the primary to the standby server (ServerB) has the following format:
sftpc.exe ServerB -unat=y -hostKeyFile=B_SSH2PublicKey -keypairFile=A_TunnelierKeypair" -cmd="put -f ...."
In the Dbvisit Standby trace file there the actual copy command. You can copy and paste this onto a command prompt and run interactively to see if there is any further output:
UTIL_WIN32_copy_file_to_remote_server-> "C:\Program Files\Bitvise Tunnelier\sftpc.exe" .....
Testing the SSH2 connection between the primary and the standby server.
1. Start the "System Readiness Check" by starting the Dbvisit Standby Windows installer and select the following option.
...