Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Primary Server (or primary node)

1. On the primary server (or primary RAC node), double click on the Dbvisit Standby installation executable. Click on Run.

2. Click on Next.

3. Accept the license terms.

4. Please ensure that the windows account that is used to install Dbvisit Standby is the same account that installed the Oracle software.

5. The components to install can be chosen. By default all components should be chosen. Dbvisit Standby is bundled with Bitvise WinSSHD and Bitvise Tunnelier software to securely transfer the database updates to the standby server. If an alternative SSH (secure shell) method is already installed, then this can be used. 

6. Choose the install location for Dbvisit Standby.

7. Choose the install location for Bitvise WinSSHD (www.bitvise.com). This is the SSH service that accepts secure transfers.

8. Choose the install location for Bitvise Tunnelier (www.bitvise.com). This is the secure SSH client that transfers the updates.

9. Please specify if this is the primary server. Answer Yes.

10. The Dbvisit software will be installed.

11. The Dbvserver Windows service will be created. The current Windows account password is needed to start the service. Please enter the password when requested.

12. The Dbvserver service has been created.

Setting up SSH connection between primary and standby servers

Dbvisit Standby uses an ssh connection between the primary and standby servers to manage the standby database. Bitvise software is used to configure and setup the ssh connection.

Bitvise WinSSHD Setup

13. Bitvise WinSSHD will now be installed in the background.

14. On completion a message will be displayed.

15. The WinSSHD service will be started.

Bitvise Tunnelier Setup

16. Bitvise Tunnelier will now be installed in the background.

17. On completion a message will be displayed.

SSH2 Setup

18. SSH2 (secure shell) will now be configured. Several background processes will start. The processes will generate unique SSH private and public encryption keys. These keys will be loaded into WinSSHD.

19. WinSSHD will need to cache the windows password of the current user. Note this is the password of the current user on the current server (not the password of the standby server).

20. To complete the SSH configuration, three of the generated encryption keys have to be copied over to the standby server. A readme file will be displayed that describes what needs to be done next.

21. Initiate the Dbvisit Standby install on the standby server (see below):

  • No labels