Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

4. It is also recommended to repeat these steps on the primary server. This is in case the Dbvisit Standby process needs to be reversed.

Resolution

...

3a – Run the Configure SSH2 setup again (through Windows installer)

Rerun the Dbvisit Standby installer and only choose the "Configure SSH2" component. This sets up and loads the public and private key combination.

...

  1. Through the Dbvisit Standby Windows Installer.
  2. Manually running a Dbvisit Standby command (see Resolution 3b below) .

Both options produce the same end result. They configure the ssh connection between the primary and standby database by reloading the SSH keys and loading the password into the WinSSHD cache. 

...

6. Run Dbvisit Standby again on the primary server to test if the issue has been resolved.

Resolution 3b – Run the Configure SSH2 setup again (through command line)

Setup SSH using a Dbvisit Standby command:

The SSH setup can also be done manually by running a Dbvisit Standby command. This sets up and loads the public and private key combination.

1. On the primary server, start the Dbvisit Standby command console and type:

...

        dbv_functions -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.

...