The Rapid Recovery Core can encrypt snapshot data for all volumes within any repository using encryption keys that you define and manage from the Core Console.
Instead of encrypting the entire repository, Rapid Recovery lets you specify an encryption key for one or more machines protected on a single Rapid Recovery Core. Each active encryption key creates an encryption domain. There is no limit to the number of encryption keys you can create on the Core.
Key security concepts and considerations include:
For more information on this topic, please see the Rapid Recovery Basic Administration Course - Web Based Training (WBT).
Multi -tenant Cores: In a multi-tenant environment (when a single Core hosts multiple encryption domains), data is partitioned and deduplicated within each encryption domain. As a result, It is recommended to use a single encryption key for multiple protected machines if you want to maximize the benefits of deduplication among a set of protected machines.
You can also share encryption keys between Cores using one of three methods.
In all cases, once imported, any encryption key appears in the Core with a state of Locked. To access data from a locked encryption key, you must unlock it. Encryption keys may contain a state of unlocked or locked. An unlocked encryption key can be applied to a protected machine to secure the backup data saved for that machine in the repository. From a Rapid Recovery Core using an unlocked encryption key, you can also recover data from a recovery point. You cannot use a locked encryption key to recover data or to apply to a protected machine. You must first provide the passphrase, thus unlocking the key. The steps to unlock an encryption key are located in the User Guide in the section "Unlocking an encryption key"