If metadata is not present on the lun – Brocade Fabric OS Encryption Administrator’s Guide Supporting RSA Data Protection Manager (DPM) Environments (Supporting Fabric OS v7.2.0) User Manual

Page 244

Advertising
background image

224

Fabric OS Encryption Administrator’s Guide (DPM)

53-1002922-01

Data mirroring deployment

4

If metadata is not present on the LUN

Beginning with Fabric OS version 6.4.0, this problem is eliminated by enabling the remote
replication mode. Remote replication mode may be enabled from either BNA (refer to

“Remote

replication LUNs”

on page 71) or from the command line interface (refer to

“Enabling remote

replication mode”

on page 181).

In very rare cases, when remote replication mode is not enabled, metadata may not be present on
the LUN. The record archived in the key vault refers only to the primary LUN, and not to the LUN
replication. With no metadata present in the replicated blocks, there is no key ID to use to retrieve
the DEK from the key vault. User intervention is needed to query the key vault to get the key ID.

1. Map the primary LUN to the replicated or snapshot LUN.

2. Based on the primary LUN information (mainly target WWN, LUN number, or LUN SN), you can

query key records from the key vaults. For this, you need to refer to key management system’s
documentation to find out how to query key records.

3. Identify the key used during the replication or snapshot of the LUN based on the creation and

expiry time of the key at the time the LUN was replicated.

4. When the record is identified, provide the Key ID for the key record as input to the LUN addition

for this LUN on the encryption switch or blade. This is done from the key management system’s
user interface. Refer to the user documentation for the key management system.

Advertising