DL4300 Appliance
Managing security
101
NOTE:
If you have another DVM repository on the target Core for which the Integrity Check job has
already been completed, or if you create a new additional repository for this target Core, you can perform
operations in that secondary repository while the integrity check job is running on the DVM repository you
specified.
1. Navigate to the Rapid Recovery Core Console.
2.
On the icon bar, click (More), and then select Repositories..
The Repositories page appears.
The DVM Repositories pane appears.
3.
In the repositories summary table, from the row representing the repository you want to check, click
and from the drop-down menu, select Check Repository Job.
A confirmation message appears.
CAUTION:
Before you confirm that you want to perform the job, you should carefully consider the
duration of time required. While the job is running, no other transactions can be performed in that
repository, including transfers (snapshot and base image backups, and replication), nightly jobs, and
so on.
4. From the Check Repository Job dialog box, to perform the integrity check, click Yes.
The dialog box closes. Any jobs that were queued or that are in progress are canceled, and the integrity
check job begins.
5. To monitor the progress of the Check Repository Job for a repository, including a determination of whether
additional steps are required after the check, from the icon bar, click
(Events).
6.
From the Events page, click
Job Details for the job to view more information about the job status.
•
If you see an error in any child tasks for this job, note the error and provide the information to a Dell technical
support representative.
•
If the Check Repository Job completes all child tasks successfully, you can then establish a custom retention policy
for this repository.
Parent topic
Managing security
The Core can encrypt protected machine snapshot data within the repository. Instead of encrypting the entire
repository, you can specify an encryption key during the protection of a machine in a repository which lets
the keys be reused for different protected machines. Encryption does not affect performance, as each active
encryption key creates an encryption domain, thus letting a single core support multitenancy by hosting multiple
encryption domains. In a multi-tenant environment, data is partitioned and deduplicated within the encryption
domains. Because you manage the encryption keys, loss of the volume cannot leak the keys. Key security
concepts and considerations include:
•
Encryption is performed using 256 bit AES in Cipher Block Chaining (CBC) mode that is compliant with SHA-3.
•
Deduplication operates within an encryption domain to ensure privacy.
•
Encryption is performed without impact on performance.
•
You can add, remove, import, export, modify, and delete encryption keys that are configured on the Core.
•
There is no limit to the number of encryption keys you can create on the Core.