Encryption Engine Rebalancing - Brocade Communications Systems WFT-2D User Manual

20

Encryption engine rebalancing

4. Do either of the following:
Encryption engine rebalancing
If you are currently using encryption and running Fabric OS 6.3.x or earlier, you are hosting tape
and disk target containers on different encryption switches or blades. Beginning with Fabric
OS 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 might 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 6.4 or later 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 rebalancing operations, be aware of the following:
•
•
To determine if rebalancing is recommended for an encryption engine, check the encryption engine
properties. Beginning with Fabric OS 6.4, a field is added that indicates whether or not rebalancing
is recommended.
You might be prompted to rebalance during the following operations:
•
•
•
•
840
•
Uncompressed Bytes: The number of uncompressed bytes written to tape.
•
Compressed Bytes: The number of compressed bytes written to tape.
•
Host Port WWN: The WWN of the host port that is being used for the write operation.
•
Click Clear to clear the tape LUN statistics for member LUNs in the container, then click
Yes to confirm.
•
Click Refresh to update the tape LUN statistics on the display.
You might notice a slight disruption in Disk I/O. In some cases, manual intervention may be
needed.
Backup jobs to tapes might need to be restarted after rebalancing is completed.
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 a failed encryption engine in an HA cluster is recovered, and failback processing has
occurred.
Brocade Network Advisor SAN User Manual
53-1003154-01