18 Backing Up and Restoring DRM Environments

This section explains how to back up installation-specific entropy file, repositories, and DRM configurations.

Oracle Data Relationship Management uses installation-specific configuration information, such as stored passwords and connection credentials.

The configuration entropy file is unique to each Data Relationship Management installation.

As a result, restoring only the DRM repository database may not be sufficient to fully restore a Data Relationship Management environment.

Backup Requirements

When backing up a DRM environment, include the following components:

Table 18-1 Backup Installation Specific Files

Component	Purpose	Required
DRM Repository Database	Stores application metadata and encrypted configuration values.	Yes
DRM Configuration Files	Stores application and service configuration.	Yes
drm-dpapi-entropy.key	Required to decrypt installation-specific protected secrets.	Recommended

Restore Guidelines

If the matching configuration entropy file is not restored:

• Data Relationship Management may be unable to decrypt stored passwords or other protected values.

• Repository or service startup may fail if required protected secrets cannot be decrypted.

If the original key or entropy files are unavailable, affected passwords or connection strings must be re-entered using supported Data Relationship Management configuration tools.

Note:

• The drm-dpapi-entropy.key file is part of DRM's local secret-protection mechanism.

• Back up the drm-dpapi-entropy.key file securely together with the matching DRM configuration and repository backup.

• Restore it only to authorized DRM hosts, and protect it using appropriate operating-system file permissions.