Re-Balancing The Encryption Engine - Brocade Communications Systems Brocade BladeSystem 4/24 User Manual

20

Re-balancing the encryption engine

9. Select target port B, click LUNs, then click Add. Select the LUNs to be encrypted and the
10. Click Commit to make the LUN configuration changes effective in both paths simultaneously.
The Management application does not automatically commit LUN configuration changes. This
allows matching changes made in a multi-path environment to be committed together, preventing
cases where one path may be encrypting and another path is not encrypting, resulting in corrupted
data. You must remember to click the Commit button after any LUN configuration changes, even in
non-multi-path environments. The Encryption Targets dialog box displays a reminder if you attempt
to close the dialog box without committing LUN configuration changes.
NOTE
There is a limit of 25 uncommitted LUN configuration changes. When adding more than 12 LUNs in
a multi-path environment, repeat steps
target container at a time. Each commit operation, then, will commit 24 LUNs, 12 in each path.
Re-balancing the encryption engine
If you are currently using encryption and running Fabric OS version 6.3.x or earlier, you are hosting
tape and disk target containers on different encryption switches or blades. Beginning with Fabric
OS version 6.4, disk and tape target containers can be hosted on the same switch or blade.
Hosting both disk and tape target containers on the same switch or blade may result in a drop in
throughput, but it can reduce cost by reducing the number of switches or blades needed to support
encrypted I/O in environments that use both disk and tape.
The throughput drop can be mitigated by re-balancing the tape and disk target containers across
the encryption engine. This ensures that the tape and disk target containers are distributed within
the encryption engine for maximum throughput.
All nodes within an encryption group must be upgraded to Fabric OS version 6.4 or a later release
to support hosting disk and tape target containers on the same encryption engine. If any node
within an encryption group is running an earlier release, disk and tape containers must continue to
be hosted on separate encryption engines.
During re-balancing operations, be aware of the following:
•
•
To determine if re-balancing is recommended for an encryption engine, check the encryption
engine properties. Beginning with Fabric OS version 6.4, a field is added that indicates whether or
not re-balancing is recommended
You may be prompted to rebalance during the following operations:
•
•
•
•
558
encryption policies for the LUNs, making sure that the encryption policies match the policies
specified in the other path.
You may notice a slight disruption in Disk I/O. In some cases, manual intervention may be
needed.
Backup jobs to tapes may need to be restarted after re-balancing completes.
When adding a new disk or tape target container.
When removing an existing disk or tape target container.
After failover to a backup encryption engine in an HA cluster.
After an failed encryption engine in an HA cluster is recovered, and failback processing has
taken place.
step 8 through step 10 above, adding only 12 LUNs to each
DCFM Enterprise User Manual
53-1001775-01