Why Recreate a Disk Safe

Question

When should I start a new Disk Safe?

Solution

In CDP 2.0, there can be cases when you need to create a new Disk Safe and back up to it instead of the old one. Such cases are listed below. The backups will be sent to the latest Disk Safe. The other Disk Safe(s) are retained to restore from.

Note Once a backup is already queued to run against a particular Disk Safe, it will use it even if you have added a new Disk Safe. It pulls the active Disk Safe when the task is queued, so it may look like it is not using the correct one.

Creating a new Disk Safe means a new initial replica backup which can take a long time.

You need to create a new Disk Safe in CDP 2.0 in the following cases:

• If your Disk Safe has become corrupt, meaning the part of the Disk Safe that maps blocks back to where they live on the disk.

Any Disk Safes open for writing at the time of the crash will likely become corrupt. The "Repair" task can not fix the problem that occurs as a result of an unclean shutdown, etc. Resolving a corrupted Disk Safe means to start a New Disk Safe for this host.

• If you need to enable or disable Disk Safe encryption.

Encryption can not be disabled later without creating a new Disk Safe. Once a Disk Safe with enabled encryption is created, only the passphrase can be changed. You can not enable encryption for the existing Disk Safe.

• If you extend a logical volume.

If you resize partitions for an existing server, a new Disk Safe must be created. The old one will remain available for restores unless it is deleted manually.

CDP 3.0 The new Disk Safe in CDP Server 3.0 will not require a new Disk Safe in this case.

Related Articles