Configuring Transaction Log repository at server level

Procedure
  1. Click HPE Recovery Manager Central > Microsoft SQL.
  2. Click the Servers tab.
  3. From the Actions menu, click Configure Translog.
  4. Do one of the following:

    • To use the already configured global transaction repository, select Use Global Transaction log Repository.

    • If you do not want to use the global transaction repository, select Configure Transaction log Repository.

  5. Select the Server on which you want to configure the repository.
  6. Select the share path of the transaction log folder.

    RMC-S supports shared folder with HPE 3PAR, HPE Primera and HPE Nimble Storage disks as local drive or path. The shared path can be RDM or VFMS disk that are on HPE 3PAR, HPE Primera or HPE Nimble Storage.

    The path validation test starts. If the test fails, select the correct the path.

    NOTE:

    The following Windows shared folder paths are not supported:

    • Loopback path. For example, \\localhost\..\ or \\127.0.0.1\...\

    • Hidden or administrative shares. For example, \\servername\x$

    • Other UNC path formats. For example, \\?\x:\

    • Mapped network drives. For example, file://<filename> not supported.

    After a successful validation test, the Configure button is enabled.

  7. Click Configure.
  8. At the prompt, enable Yes, continue with configure transaction log and then click OK.

The following details are populated after successful configuration of transaction log repository.

Recovery Set Name

The configured transaction log volume Recovery Set name created by RMC.

Storage System Serial number

The serial number of the HPE storage system used to export volume to configure transaction log folder.

Volume Name

The name of the volume created for configuring transaction log.

Volume WWN

The WWN name of the configured transaction log volume.

Protected by Copy Policy

By default the transaction log repository is protected by RMC standard bronze policy. Under this policy, the snapshots are taken every 12 hours and are deleted after seven days of snapshot creation. You can configure the policy as per your requirements.