Configuring transaction log backup

The transaction log folder is not configured by default. Hewlett Packard Enterprise recommends you not to store any database or instance files in the transaction log folder as there might be issues during a restore. The restore of transaction log folder Snapshot or Express Protect overwrites the database or instance files.

  1. Click HPE Recovery Manager Central > Microsoft SQL.
  2. Click the Servers tab and then click + Configure Translog.
  3. Select Path and then specify the share path of transaction log folder.

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


    The following Windows shared folder paths are not supported:

    • Loopback path, for example, \\localhost\..\ or \\\...\

    • Administrative shares, for example, \\servername\x$

    • Other UNC path formats such as \\?\x:\

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

    • Loopback or localhost name is not supported. Hidden or Administrative shares, for example, \\servername\x$ are not supported.

  4. To validate the path specified after the shared path for transaction log folder is added, click Validate.

    If validation path test fails, correct the path.

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

After a successful validation test, the OK button enables to proceed.
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 7 days of snapshot creation. You can configure the policy as per your requirements.