Administration Guide › Log Storage › Configuring Non-Interactive Authentication for Restore › Example: Configure Authentication From a Storage Server to a Reporting Server

Example: Configure Authentication From a Storage Server to a Reporting Server

You can restore archived databases from a remote storage server back to their original reporting server, that is, the server from which they were auto archived. The advantage of this method is that you do not have to recatalog the CA Enterprise Log Manager archive database. The databases of log files you are restoring are already known to the reporting server. If you have multiple reporting servers, you configure non-interactive authentication between the remote storage server and each reporting server. The authorized_keys file exists in the .ssh directory on the reporting server. This authorized_keys file has the public keys of each key pair generated on a collection server that auto archives to this reporting server. Therefore, you create an authorized keys file with a suffix and then concatenate that file to the original authorized_keys.

The process for configuring non-interactive authentication from a remote storage server to a reporting CA Enterprise Log Manager involves the following procedures:

1. From the remote storage server:
   1. Configure the RSA public/private key pair for remote storage to reporting server authentication.
   2. Copy the public key as authorized_keys_RSS from the storage server to the /tmp directory on the reporting server.
2. From the reporting server:
   1. Copy the current authorized_keys from .ssh to /tmp.
   2. Concatenate authorized_keys_RSS in the /tmp directory to the authorized_keys file.
   3. Copy the appended authorized_keys file back to the .ssh directory.
3. From the remote storage server, validate successful non-interactive authentication between servers.
4. Repeat these steps for each remote storage server to reporting server combination.

More information:

Generate Keys and Copy the Public Key to a Reporting Server

Update the Existing Public Key File