...
- On the standby server, sftpc.exe (Tunnelier) is called as the client which connects to WinSSHD on the primary server. WinSSHD on the primary server will be running as a Windows service.
To setup the connection between Tunnelier and WinSSHD a combination of public and private keys are used. The keys need to match with the key (X_WinSSHDKeypair) that is loaded into WinSSHD. The Windows account username and password also needs to be loaded into WinSSHD so that when sftpc.exe connects it can execute the actual copy command on the target server.
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 is 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.
...
2. If the Dbvisit Standby Windows installer is no longer available, the System Readiness Check can be started manually with the following command:
dbv_functions.exe
...
–a
...
system_readiness
This command should be run on both the primary and standby servers to test the connectivity going both ways.
...
dbvisit -ReverseCopy <DDC>
Where
...
DDC
...
is
...
the
...
name
...
of
...
the
...
Dbvisit
...
Database
...
Configuration.
...
In
...
most
...
cases
...
this
...
is
...
the
...
same
...
as
...
the
...
database
...
name.
...
The
...
DDC
...
refers
...
to
...
the
...
DDC
...
file
...
name
...
which
...
is
...
in
...
the
...
form:
...
dbv_DDC.env
...
and
...
contains
...
the
...
Dbvisit
...
Standby
...
settings
...
for
...
a
...
particular
...
primary
...
and
...
standby
...
configuration.
13. More information about the configuring groups and accounts for WinSSHD can be found here: http://www.bitvise.com/wug-accounts
...
1. On the primary server, start the Dbvisit Standby command console and type:
...
dbv_functions.exe
...
-Y
...
primary
...
setupssh
Follow the instructions.
2. On the standby server, start the Dbvisit Standby command console and type:
...
dbv_functions.exe
...
-Y
...
standby
...
setupssh
Follow the instructions.
3. Run the System Readiness Check to check the connection between the primary and standby servers:
...
dbv_functions.exe
...
–a
...
system_readiness
This command should be run on both the primary and standby servers to test the connectivity going both ways.
Resolution 4 – Ensure Windows accounts are similar.
...
Ensure the Windows user accounts are similar between the primary and the standby server. Both user accounts must be either domain accounts (within the same domain) or single user accounts.It is not possible to run Dbvisit Standby using a Windows domain account on the primary server and on the standby server run Dbvisit Standby using a standalone Windows user account or vice versa. This is a requirement of WinSSHD to establish a secure and trusted connection.If the standby server is not part of the same domain as the primary server, then the WinSSHD settings are a little different. The account in WinSSHD on the standby server should then be a virtual account and group. Please see http://www.bitvise.com/wug-accounts for more information and http://www.dbvisit.com/forums/showthread.php?p=2865
Resolution 5 – Please contact Dbvisit support.
...