HP StoreServ Application Suite for Oracle Media manual Backuphost# ssh username@ssname

Recovery Manager for Oracle User’s Guide

<backup_host># ssh <username>@<ss_name>

The authenticity of host '<ss_name>' can't be established.

DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '<InServ_name>' (DSS) to the list of known hosts.

where:

◆<user_name> is the CLI user created in 4.3.7 Setting Up Connections from the Backup Host to the NetBackup Master Server on page 4.13.

◆<ss_name> is the system name of the InServ Storage Server attached to the backup host.

4.3.11Setting Connections from the Primary Host to the InServ Storage Server

Skip this step if the primary host has the same SSH key pair as the SSH key pair of the backup host (see 4.3.4 Generating an SSH Key Pair for the Primary Host on page 4.11). 3PAR Recovery Manager uses the same CLI user to access the InServ Storage Server from either the backup host or primary host.

If you created a different CLI user for the primary host, perform the following to set up an SSH connection from the primary host to the InServ Storage Server.

1Log in to the primary host as root user.

2Make sure the SSH key pair exists as follows:

<primary_host> # ls ~/.ssh

id_rsa id_rsa.pub authorized_keys known_hosts

3Create a CLI user to be used by Recovery Manager to access the InServ Storage Server from the primary host. Skip this step if you wish to use an existing user (different from the user created for the backup host).

<primary_host># ssh <adm_user>@<ss_name> <adm_user>'s password: <adm_password>

cli% createuser -c <password> <username> all edit

4.16

Setting Up SSH Connections for Recovery Manager