Configure secure shell – SSH (step 1) – Linux/Unix

This step can be skipped, if a SSH without a password or passphrase is already configured.Secure shell is the preferred method to transport the Oracle logs from the primary to the standby servers.It is recommended to setup secure shell. However, if remote shell is preferred please see Appendix B – Configure remote shell (rsh).To configure SSH without using a password or passphrase the utility ssh-keygen is run. You have to create a RSA authentication key to be able to log into a remote site from your account. This should be done as the Dbvisit Standby software owner, never as root!

1. On the primary server as Dbvisit Standby software owner (do not enter passphrase!):

2. On the standby server as Dbvisit Standby software owner (do not enter passphrase!):

3. On the standby server create a new empty file called .ssh/authorized_keys

4. Copy the contents of file .ssh/id_dsa.pub from the primary server to the new file .ssh/authorized_keys on the standby server. The file may be called identity.pub or id_rsa.pub instead of id_dsa.pub.

5. Ensure the new file .ssh/authorized_keys has the correct permission:

6. On the primary server create a new empty file called .ssh/authorized_keys

7. Copy the contents of file .ssh/id_dsa.pub from the standby server to the new file .ssh/authorized_keys on the primary server. The file may be called identity.pub or id_rsa.pub instead of id_dsa.pub.

8. Ensure the new file .ssh/authorized_keys has the correct permission:

SSH is now setup and configured. To test:

On the primary server:

On the standby server:

Secure shell configuration is now competed.