Preparing the Environment on

Extracting the Installation Package

Mon, 01 Jan 0001 00:00:00 +0000

Download the DatabaseProtector_WIN-ALL-64_x86-64_MSSQL-ALL-64_<version>.zip installation package made available by Protegrity.
Create a directory to install the protector.

Note: In case of a failure to create the installation directory, the script will use C:\Program Files\Protegrity\ as the default installation directory.
To obtain the signature files, extract the contents of the DatabaseProtector_WIN-ALL-64_x86-64_MSSQL-ALL-64_<version>.zip file.
- DatabaseProtector_WIN-ALL-64_x86-64_MSSQL-ALL-64_<version>.zip
- signatures\
- DatabaseProtector_WIN-ALL-64_x86-64_MSSQL-ALL-64_<version>.zip_10.0.sig
To obtain the installation files from the package, extract the DatabaseProtector_WIN-ALL-64_x86-64_MSSQL-ALL-64_<version>.zip file.

The following files are available in the installation package:

Mon, 01 Jan 0001 00:00:00 +0000

Log in to the database server as the user that has the permissions to install the Log Forwarder. Usually, this tends to be the instance owner.
Navigate to the directory containing the installation files.
To install the Log Forwarder, double-click the LogforwarderSetup_Windows_x64_<version>.exe file.

The Welcome to the Log Forwarder Setup Wizard dialog box appears.

Caution: It is mandatory to install the Log Forwarder before installing the RPAgent to ensure that the MSSQL Database Protector is configured correctly.

Mon, 01 Jan 0001 00:00:00 +0000

Before you begin:

Before proceeding with the RPA installation in secure mode, ensure that the required CA certificate is available and trusted on the system.

For ESA

Download the certificate from ESA.

For more information about downloading certificates from ESA, refer to Manage Certificates.

After obtaining the certificate, configure the system environment variable:

Variable	Value
SSL_CERT_FILE	Full path to the certificate file (for example, C:\Program Files\Protegrity\Database Protector\ca.crt)

Ensure the ESA hostname or IP is present in the ESA TLS certificate (SAN or CN) and it is resolvable from the RPAgent host.