FAQs
Frequently asked questions...
- What do I need to know before creating a security key?
A security key is shared by controllers and secure-enabled drives within a storage array. If a secure-enabled drive is removed from the storage array, the security key protects the data from unauthorized access. - Why do I need to define a pass phrase?
The pass phrase is used to encrypt and decrypt the security key file stored on the local management client. Without the pass phrase, the security key cannot be decrypted and used to unlock data from a secure-enabled drive if it is re-installed in another storage array. - Why is it important to record security key information?
If you lose the security key information and do not have a backup, you could lose data when relocating secure-enabled drives or upgrading a controller. You need the security key to unlock data on the drives. - What do I need to know before backing up a security key?
If your original security key becomes corrupted and you do not have a backup, you will lose access to the data on drives if they are migrated from one storage array to another. - What do I need to know before unlocking secure drives?
To unlock the data from a secure-enabled drive that is migrated to a new storage array, you must import its security key. - What is read/write accessibility?
The Drive Settings window includes information about the Drive Security attributes. "Read/Write Accessible" is one of the attributes that displays if a drive's data has been locked. - What do I need to know about validating the security key?
After creating a security key, you should validate the key file to make sure it is not corrupt. - What is the difference between internal security key and external security key management?
When you implement the Drive Security feature, you can use an internal security key or an external security key to lock down data when a secure-enabled drive is removed from the storage array.
Give documentation feedback