View Source

R1Soft CDP Server uses the [Virtual Full Backup|TP:Backup Method - Virtual Full Backup] method. First, the initial full backup (*Initial Replica*) is created. After that, each time a replication is performed, it stores only the differences (block-level deltas) since the last replication. 


Each replication creates a point-in-time image of the [Device|Devices], it is called a [Recovery Point|Recovery Points]. To map the block versions and Recovery Points, the block deltas database is used. This database is a *Disk Safe*. 


A Disk Safe is used to keep and arrange the pieces of replicated information. You can define a Disk Safe as a container for data needed for a restore.
{info:title=Tip}You can restore from any available Recovery Point in any Disk Safe.
Disk Safes have assigned *Device(s)* selected for backup. One Device can be assigned to multiple Disk Safes.
{note:title=Notice}You cannot start backing up a Device until there is a Disk Safe to which this Device has to be backed up.
To run a replication, you need to associate a *Data Protection Policy* with your Disk Safe. The Policy will back up the Disk Safe's associated Device(s).
{info:title=Tip}You can exclude folders/files from the replication while defining the Policy's properties.
On a physical level, Disk Safe is a directory containing:
* {color:blue}.db{color} file
* {color:blue}.db-journal{color} file
* {color:blue}metadata{color} folder

h5. Disk Safe Properties

Disk Safes have the following properties defined during Disk Safe creation:
* *Identification* \- Unique name to distinuguish the Disk Safe in the list and while defining policies.
* *Disk Safe Location* \- Location where the Disk Safe folder is physically saved.
* *Compression Type* \- Using compression helps to reduce the consumption of hard disk space or transmission bandwidth.
* *Devices* \- You can assign one or several hard Disks, Partitions, and other Volumes of a Host where file systems are mounted as Devices.

These characteristics, except Disk Safe Location, can be changed for an existing Disk Safe via CDP Server Interface.

In addition to the above properties, the following properties are available for the existing Disk Safes:
* *Enabled*
* *Recovery Points*
* *Size*

h5. Disk Safe States

Disk Safes can be in one (1) of the following states:
* *Opened* \- You can associate tasks including Backup with opened Disk Safes, and browse its Recovery Points.
* *Closed* \- Closing a Disk Safe prevents any tasks associated with it from running, and you will not be able to browse the Recovery Points contained within the Disk Safe.

h5. Available Disk Safes Actions

* Create new Disk Safes.
* Edit properties of existing Disk Safes.
* Attach(open) existing Disk Safes to the system.
* Close (disable) Disk Safes.
* Detach Disk Safes.
* Delete Disk Safe and all its data.
* Vacuum Disk Safe.
* Browse Recovery Points contained within the Disk Safes.
* Move Disk Safe from one location to another on a CDP Server.
* Copy Disk Safes from one CDP Server to another.
* Copy Disk Safes across Windows/Linux platforms.
{info:title=Tip}Tools like Windows Explorer drag-and-drop, {color:blue}scp{color}, {color:blue}xcopy{color}, {color:blue}ftp{color}, etc. can be used to move Disk Safes.

{card:label=Section Contents}
{card:label=PDF Downloads}

[!ug-a.png!||CDP Advanced Edition User Guide ]

[!ug-s.png!||CDP Standard Edition User Guide]

[!ug-e.png!||CDP Enterprise Edition User Guide]

{card:label=Related Articles}

{excerpt:hidden=true}General description of Disk Safes and available actions in CDP.{excerpt}