Some changes in terminology have occured since CDP 2.0. See the table below.
|| CDP 2 || CDP 3 || CDP 3 Short-hand ||
| Backup Task | Data Protection Policy | Policy |
| Backup | Replication | Replica, Replicate, Synchronize, Sync |
| Delete Backup / Delete Recovery Point | Merge Recovery Points | Merge |
| Job/Task | Policy | |
----
{toc:location=top|maxLevel=3|minLevel=3|type=flat|separator=pipe|style=border:1}
----
h3. Advanced Edition {anchor:advanced}
See [CDP3:Advanced Edition].
----
h3. Agents{anchor:agent}
Agents are computers and servers that are being replicated. Multiple Agents can be managed within the [Enterprise|#Enterprise Edition] CDP. See: [CDP Agents|http://wiki.r1soft.com/display/CDP3/CDP+Agents].
----
h3. Alert{anchor:alert}
CDP system generates warning alerts to inform users that the current course of action could be in some way dangerous or detrimental.
----
h3. API{anchor:api}
An application programming interface (API) is an interface implemented by a software program that enables it to interact with other software. There is a list of CDP API provided by R1Soft. See [CDP3:API Documentation].
----
h3. Archive Point{anchor:archivepoint}
An Archive Point is basically a copy of the most recent [#Recovery Point], which can be used for long term data storage to provide further integrity and safe-keeping of data. It supports all of the Recovery Points' functionality. You can browse and restore your files as well as perform a [Bare-Metal Restore|#Bare-Metal Restore]. See [CDP3:Archiving].
----
h3. Archiving{anchor:archiving}
Refers to advanced recovery point archiving rules available in CDP. This process involves archiving the most recently available [recovery point|#Recovery Point] as configured on a daily/weekly/monthly basis for long term storage. See [CDP3:Archiving].
----
h3. Bare Metal{anchor:baremetal}
A new computer system that does not contain an operating system or any software.
----
h3. Bare-Metal Restore{anchor:bmr}
Bare-Metal Restore is the process of instantly rebuilding a computer or server from scratch after a catastrophic failure. The CDP application allows to restore servers directly from disk-based backup. There is *no* need to first partition your drive and install the operating system. Instead, you use the Bare-Metal Restore process built directly into the CDP Server. See: [Bare-Metal Restore|http://wiki.r1soft.com/display/CDP3/Bare-Metal+Restore].
----
h3. Blocks{anchor:block}
The file system of every operating system divides the hard disk into groups of bytes called blocks. Block-based backup application reads the data from these blocks. Compared to backup applications that read every file using file system, which is slow and time consuming process, block based backups are more efficient.
----
h3. Compression{anchor:compression}
Compression is the reduction in size of data in order to save disk space or transmission time. There are three types of compression in CDP: None, Zlib or QuickLZ.
----
h3. Control Panel Instance{anchor:instance}
Control Panel Instance is an occurrence of a Hosting Control Panel (a certain installation on the machine where the CDP Agent is installed.) The Instance must be added to the [Policy|#policy]. For each Instance, you need to specify Control Panel Type, Name, Description, and Virtuozzo Container ID (if exists). See [CDP for Hosting Control Panels].
----
h3. Delta {anchor:delta}
Deltas are the data that has changed since the last backup run. Various types of data can be treated as Deltas. It depends on how the backup application computes deltas. A delta could be a raw disk [block|#Blocks], a variables length portion of a file or even a complete file depending on the method.
----
h3. Disk Safe{anchor:disk safe}
To map the block [deltas|#delta] versions and [Recovery Points|#recoverypoint], the block deltas database is used. This database is a Disk Safe. Disk Safe contains the data needed to restore the Device(s) of [Agent|#agent]. See: [Disk Safes|http://wiki.r1soft.com/display/CDP3/Disk+Safes].
----
h3. Enterprise Edition{anchor:enterprise}
See [CDP3:Enterprise Edition].
----
h3. Export{anchor:export}
Moving files from a [#recovery point] in the [Disk Safe|#disk safe] to an off-site server or local hard disk. See [CDP3:Copying and Moving Disk Safes].
----
h3. File Excludes{anchor:file excludes}
File Excludes are files and folders that a user wants to excluded from [replications|#replication]. The system allows to define various exclude rules while customizing the settings of a replication. The user can exclude files and folders as well. See [CDP3:Excluding Files and Folders].
----
h3. Full Block Scan{anchor:fullblockscan}
This is a particular type of CDP [#replication] of a device. It happens under certain conditions and is required to get the asynchronous CDP replication back in sync. Usually this process takes much time and may reduce a network throughput.
----
h3. GUID{anchor:guid}
Globally Unique Identifier is generated by the system. This is a unique reference number used as an identifier in computer software. The value of a GUID is represented as a 32-character string, for example 0f6b6a6e-d444-4c77-a026-f76be7723e16.
----
h3. Hyper-V VHD Explorer{anchor:Hyper-V VHD Explorer}
R1Soft Hyper-V VHD Explorer allows you to mount and dismount your Hyper-V Virtual Hard Disk ([#VHD]) files. Explorer shell integration adds right-click "Attach" and "Detach" actions to .vhd files in MS Windows Explorer. Use the Hyper-V VHD Explorer graphical user interface to manage all your mounted [#VHD] files.
----
h3. Limit Disk Space Available to CDP{anchor:Limit Disk Space Available to CDP}
This option defines how much free space can be left. This is an effective limit defined in percents of the Device volume. If the limit is reached, then the system forbids generating new [Recovery Points|#recovery point]. The [replication|#replication] is interrupted and failed.
----
h3. Initial Replica{anchor:initialreplica}
The first [Recovery Point|#recoverypoint] containing all used (except for excludes) parts of the hard disk. Subsequent [synchronizations|#synchronization] only contain [Deltas|#delta].
----
h3. Locking Recovery Points{anchor:lock}
Locking [Recovery Points|#recoverypoint] means protecting them from being [merged (deleted)|#merge].
----
h3. Log Files{anchor:logfiles}
Log File is a file that lists actions that have occurred. Three types of log files are available in CDP: log file with messages from tasks performed by the backup agent ({color:blue}cdp.log{color}); log file with messages from the CDP Server ({color:blue}server.log{color}); log file with messages from the web GUI, and startup/shutdown tasks ({color:blue}monitor.log{color}). See [Accessing Log Files].
----
h3. Merge Recovery Points {anchor:merge}
The process of deleting a [Recovery Point|#recoverypoint] is actually a merge between the unwanted recovery point and closest existing recovery point. [Deltas|#delta] that have changed between the two Recovery Points can be discarded and the space they consume in the [Disk Safe|#Disk Safe] freed. See [CDP3:Merging Recovery Points].
----
h3. Mount Point{anchor:mountpoint}
In Unix-like systems, a mount point is the location in the operating system's directory structure where a mounted file system appears. In Microsoft Windows, mapping a drive is the equivalent to mount point.
----
h3. Multi-Point Replication{anchor:multipointreplication}
Multi-Point Replication is a function built-in CDP [Enterprise|#enterprise] Edition. It allows a secondary [#replication]of your CDP Enterprise Server machine. As the primary CDP Server itself could potentially crash due to hardware failure, virus attack, etc., you can run another CDP Server enabling you to protect the machine with your primary CDP Server installed. Using Multi-Point Replication function, you can replicate your primary CDP Enterprise Server machine by a secondary CDP Enterprise Server. See [Multi-Point Replication|CDP3:Multi-Point Replication].
----
h3. MySQL{anchor:mysql}
MySQL is a database software with a variety of tools providing multi-user access to a number of databases. The CDP system allows to backup and restore MySQL databases. See [CDP3:CDP for MySQL].
----
h3. Partition{anchor:partition}
Partition as an action means to divide memory or mass storage into isolated sections. The Partitions are specific areas within the hard disk. Partition Table is a placeholder for the description of a Partition on the hard disk.
----
h3. Policy (Data Protection Policy){anchor:policy}
Policy is assigned to a [Disk Safe|#disksafe]. It is a schedule of Disk Safe replication. You can schedule recurring Policies or create one-time Policies. The Policy starts at the time you have specified in the Policy properties. The Policy properties include information about how may [Recovery Points|#Recovery Point] to keep in the [Disk Safe|#Disk Safe]. See [CDP3:Policies].
----
h3. Policy Frequency{anchor:Policy Frequency}
Recurrence selected for running the Policy (On Demand, Minutely, Hourly, Daily, Weekly, Monthly, or Yearly)
----
h3. Recovery Point Retention{anchor:retention}
The rules that define how many [Recovery Points|#recoverypoint] to keep in the [Disk Safe|#disksafe]. Old Recovery Points are [merged|#merge].
----
h3. Recovery Point{anchor:recoverypoint}
A Recovery Point is a set of many [deltas|#delta]. Deltas represent the state of a disk volume [block|#Blocks] at a particular point in time. Each delta can be used by one or more Recovery Point. The relationship between Deltas and Recovery Points is maintained by the [Disk Safe|#Disk Safe]. See: [Recovery Points|http://wiki.r1soft.com/display/CDP3/Recovery+Points].
----
h3. Recovery Point Limit{anchor:Recovery point limit}
The limit indicates how many Recovery Points will be kept. The old Recovery Points will be merged automatically.
----
h3. Replication{anchor:replication}
The operation of copying block level [Deltas|#delta] from the [Agent|#Agents] to the CDP Server into a new [Recovery Point|#recoverypoint]. Each replication creates a point-in-time image (a [Recovery Point|#recoverypoint]) of the Device.
----
h3. Server Key{anchor:serverkey}
In order to keep the [CDP Agent|#Agents] secure, connections are only accepted from specified CDP Servers. To specify it, you need to add Server Public Key to the CDP Agent. It means creating a text file on the Agent machine. See [CDP3:Adding the Server Key to Linux Agent], [CDP3:Adding the Server Key to Windows Agent].
----
h3. Snapshot the Disk or Volume{anchor:snapshot}
This is the first stage of [#replication] process. The system creates a point-in-time snapshot of the servers file system for a consistent open file backup.
----
h3. Warn When Disk Usage Exceeds
This is a warning level where users are informed they are close to reaching their effective limit. The level is also defined in percents of the Device volume. This limit is usually a lesser value to [Limit Disk Space Available to CDP|#Limit Disk Space Available to CDP].
----
h3. Standard Edition{anchor:standard}
See [CDP3:Standard Edition].
----
h3. Synchronization{anchor:synchronization}
Synchronization is the process of creation of the [Disk Safe|#disksafe] point-in-time snapshot and computing [Deltas|#delta] based on the last completed synchronization.
----
h3. Vacuuming Disk Safes{anchor:vacuum}
Vacuuming [Disk Safe|#disksafe] is the process of reducing of the on-disk size. It is achieved by vacuuming [Blocks|#Blocks] which are not longer used by a file system.
----
h3. VHD{anchor:vhd}
Virtual Hard Disk (VHD) is typically used as a hard disk of a virtual machine. It allows you to deploy multiple operating systems on a single host machine. On the market, there are pre-configured VHDs with already installed software. Such VHDs enable you to evaluate different software solutions in your own environment without the need for dedicated servers or complex installations. Use the [Hyper-V VHD Explorer|#Hyper-V VHD Explorer] graphical user interface to manage all your mounted VHD files.
----
h3. Volume{anchor:volume}
Volume is a storage of one or more [Disk Safes|#disksafe]. Volumes are so-called containers in the [Replication|#Replication] system. See: [Volumes|http://wiki.r1soft.com/display/CDP3/Volumes].
----
{excerpt:hidden=true}CDP Glossary{excerpt}
|| CDP 2 || CDP 3 || CDP 3 Short-hand ||
| Backup Task | Data Protection Policy | Policy |
| Backup | Replication | Replica, Replicate, Synchronize, Sync |
| Delete Backup / Delete Recovery Point | Merge Recovery Points | Merge |
| Job/Task | Policy | |
----
{toc:location=top|maxLevel=3|minLevel=3|type=flat|separator=pipe|style=border:1}
----
h3. Advanced Edition {anchor:advanced}
See [CDP3:Advanced Edition].
----
h3. Agents{anchor:agent}
Agents are computers and servers that are being replicated. Multiple Agents can be managed within the [Enterprise|#Enterprise Edition] CDP. See: [CDP Agents|http://wiki.r1soft.com/display/CDP3/CDP+Agents].
----
h3. Alert{anchor:alert}
CDP system generates warning alerts to inform users that the current course of action could be in some way dangerous or detrimental.
----
h3. API{anchor:api}
An application programming interface (API) is an interface implemented by a software program that enables it to interact with other software. There is a list of CDP API provided by R1Soft. See [CDP3:API Documentation].
----
h3. Archive Point{anchor:archivepoint}
An Archive Point is basically a copy of the most recent [#Recovery Point], which can be used for long term data storage to provide further integrity and safe-keeping of data. It supports all of the Recovery Points' functionality. You can browse and restore your files as well as perform a [Bare-Metal Restore|#Bare-Metal Restore]. See [CDP3:Archiving].
----
h3. Archiving{anchor:archiving}
Refers to advanced recovery point archiving rules available in CDP. This process involves archiving the most recently available [recovery point|#Recovery Point] as configured on a daily/weekly/monthly basis for long term storage. See [CDP3:Archiving].
----
h3. Bare Metal{anchor:baremetal}
A new computer system that does not contain an operating system or any software.
----
h3. Bare-Metal Restore{anchor:bmr}
Bare-Metal Restore is the process of instantly rebuilding a computer or server from scratch after a catastrophic failure. The CDP application allows to restore servers directly from disk-based backup. There is *no* need to first partition your drive and install the operating system. Instead, you use the Bare-Metal Restore process built directly into the CDP Server. See: [Bare-Metal Restore|http://wiki.r1soft.com/display/CDP3/Bare-Metal+Restore].
----
h3. Blocks{anchor:block}
The file system of every operating system divides the hard disk into groups of bytes called blocks. Block-based backup application reads the data from these blocks. Compared to backup applications that read every file using file system, which is slow and time consuming process, block based backups are more efficient.
----
h3. Compression{anchor:compression}
Compression is the reduction in size of data in order to save disk space or transmission time. There are three types of compression in CDP: None, Zlib or QuickLZ.
----
h3. Control Panel Instance{anchor:instance}
Control Panel Instance is an occurrence of a Hosting Control Panel (a certain installation on the machine where the CDP Agent is installed.) The Instance must be added to the [Policy|#policy]. For each Instance, you need to specify Control Panel Type, Name, Description, and Virtuozzo Container ID (if exists). See [CDP for Hosting Control Panels].
----
h3. Delta {anchor:delta}
Deltas are the data that has changed since the last backup run. Various types of data can be treated as Deltas. It depends on how the backup application computes deltas. A delta could be a raw disk [block|#Blocks], a variables length portion of a file or even a complete file depending on the method.
----
h3. Disk Safe{anchor:disk safe}
To map the block [deltas|#delta] versions and [Recovery Points|#recoverypoint], the block deltas database is used. This database is a Disk Safe. Disk Safe contains the data needed to restore the Device(s) of [Agent|#agent]. See: [Disk Safes|http://wiki.r1soft.com/display/CDP3/Disk+Safes].
----
h3. Enterprise Edition{anchor:enterprise}
See [CDP3:Enterprise Edition].
----
h3. Export{anchor:export}
Moving files from a [#recovery point] in the [Disk Safe|#disk safe] to an off-site server or local hard disk. See [CDP3:Copying and Moving Disk Safes].
----
h3. File Excludes{anchor:file excludes}
File Excludes are files and folders that a user wants to excluded from [replications|#replication]. The system allows to define various exclude rules while customizing the settings of a replication. The user can exclude files and folders as well. See [CDP3:Excluding Files and Folders].
----
h3. Full Block Scan{anchor:fullblockscan}
This is a particular type of CDP [#replication] of a device. It happens under certain conditions and is required to get the asynchronous CDP replication back in sync. Usually this process takes much time and may reduce a network throughput.
----
h3. GUID{anchor:guid}
Globally Unique Identifier is generated by the system. This is a unique reference number used as an identifier in computer software. The value of a GUID is represented as a 32-character string, for example 0f6b6a6e-d444-4c77-a026-f76be7723e16.
----
h3. Hyper-V VHD Explorer{anchor:Hyper-V VHD Explorer}
R1Soft Hyper-V VHD Explorer allows you to mount and dismount your Hyper-V Virtual Hard Disk ([#VHD]) files. Explorer shell integration adds right-click "Attach" and "Detach" actions to .vhd files in MS Windows Explorer. Use the Hyper-V VHD Explorer graphical user interface to manage all your mounted [#VHD] files.
----
h3. Limit Disk Space Available to CDP{anchor:Limit Disk Space Available to CDP}
This option defines how much free space can be left. This is an effective limit defined in percents of the Device volume. If the limit is reached, then the system forbids generating new [Recovery Points|#recovery point]. The [replication|#replication] is interrupted and failed.
----
h3. Initial Replica{anchor:initialreplica}
The first [Recovery Point|#recoverypoint] containing all used (except for excludes) parts of the hard disk. Subsequent [synchronizations|#synchronization] only contain [Deltas|#delta].
----
h3. Locking Recovery Points{anchor:lock}
Locking [Recovery Points|#recoverypoint] means protecting them from being [merged (deleted)|#merge].
----
h3. Log Files{anchor:logfiles}
Log File is a file that lists actions that have occurred. Three types of log files are available in CDP: log file with messages from tasks performed by the backup agent ({color:blue}cdp.log{color}); log file with messages from the CDP Server ({color:blue}server.log{color}); log file with messages from the web GUI, and startup/shutdown tasks ({color:blue}monitor.log{color}). See [Accessing Log Files].
----
h3. Merge Recovery Points {anchor:merge}
The process of deleting a [Recovery Point|#recoverypoint] is actually a merge between the unwanted recovery point and closest existing recovery point. [Deltas|#delta] that have changed between the two Recovery Points can be discarded and the space they consume in the [Disk Safe|#Disk Safe] freed. See [CDP3:Merging Recovery Points].
----
h3. Mount Point{anchor:mountpoint}
In Unix-like systems, a mount point is the location in the operating system's directory structure where a mounted file system appears. In Microsoft Windows, mapping a drive is the equivalent to mount point.
----
h3. Multi-Point Replication{anchor:multipointreplication}
Multi-Point Replication is a function built-in CDP [Enterprise|#enterprise] Edition. It allows a secondary [#replication]of your CDP Enterprise Server machine. As the primary CDP Server itself could potentially crash due to hardware failure, virus attack, etc., you can run another CDP Server enabling you to protect the machine with your primary CDP Server installed. Using Multi-Point Replication function, you can replicate your primary CDP Enterprise Server machine by a secondary CDP Enterprise Server. See [Multi-Point Replication|CDP3:Multi-Point Replication].
----
h3. MySQL{anchor:mysql}
MySQL is a database software with a variety of tools providing multi-user access to a number of databases. The CDP system allows to backup and restore MySQL databases. See [CDP3:CDP for MySQL].
----
h3. Partition{anchor:partition}
Partition as an action means to divide memory or mass storage into isolated sections. The Partitions are specific areas within the hard disk. Partition Table is a placeholder for the description of a Partition on the hard disk.
----
h3. Policy (Data Protection Policy){anchor:policy}
Policy is assigned to a [Disk Safe|#disksafe]. It is a schedule of Disk Safe replication. You can schedule recurring Policies or create one-time Policies. The Policy starts at the time you have specified in the Policy properties. The Policy properties include information about how may [Recovery Points|#Recovery Point] to keep in the [Disk Safe|#Disk Safe]. See [CDP3:Policies].
----
h3. Policy Frequency{anchor:Policy Frequency}
Recurrence selected for running the Policy (On Demand, Minutely, Hourly, Daily, Weekly, Monthly, or Yearly)
----
h3. Recovery Point Retention{anchor:retention}
The rules that define how many [Recovery Points|#recoverypoint] to keep in the [Disk Safe|#disksafe]. Old Recovery Points are [merged|#merge].
----
h3. Recovery Point{anchor:recoverypoint}
A Recovery Point is a set of many [deltas|#delta]. Deltas represent the state of a disk volume [block|#Blocks] at a particular point in time. Each delta can be used by one or more Recovery Point. The relationship between Deltas and Recovery Points is maintained by the [Disk Safe|#Disk Safe]. See: [Recovery Points|http://wiki.r1soft.com/display/CDP3/Recovery+Points].
----
h3. Recovery Point Limit{anchor:Recovery point limit}
The limit indicates how many Recovery Points will be kept. The old Recovery Points will be merged automatically.
----
h3. Replication{anchor:replication}
The operation of copying block level [Deltas|#delta] from the [Agent|#Agents] to the CDP Server into a new [Recovery Point|#recoverypoint]. Each replication creates a point-in-time image (a [Recovery Point|#recoverypoint]) of the Device.
----
h3. Server Key{anchor:serverkey}
In order to keep the [CDP Agent|#Agents] secure, connections are only accepted from specified CDP Servers. To specify it, you need to add Server Public Key to the CDP Agent. It means creating a text file on the Agent machine. See [CDP3:Adding the Server Key to Linux Agent], [CDP3:Adding the Server Key to Windows Agent].
----
h3. Snapshot the Disk or Volume{anchor:snapshot}
This is the first stage of [#replication] process. The system creates a point-in-time snapshot of the servers file system for a consistent open file backup.
----
h3. Warn When Disk Usage Exceeds
This is a warning level where users are informed they are close to reaching their effective limit. The level is also defined in percents of the Device volume. This limit is usually a lesser value to [Limit Disk Space Available to CDP|#Limit Disk Space Available to CDP].
----
h3. Standard Edition{anchor:standard}
See [CDP3:Standard Edition].
----
h3. Synchronization{anchor:synchronization}
Synchronization is the process of creation of the [Disk Safe|#disksafe] point-in-time snapshot and computing [Deltas|#delta] based on the last completed synchronization.
----
h3. Vacuuming Disk Safes{anchor:vacuum}
Vacuuming [Disk Safe|#disksafe] is the process of reducing of the on-disk size. It is achieved by vacuuming [Blocks|#Blocks] which are not longer used by a file system.
----
h3. VHD{anchor:vhd}
Virtual Hard Disk (VHD) is typically used as a hard disk of a virtual machine. It allows you to deploy multiple operating systems on a single host machine. On the market, there are pre-configured VHDs with already installed software. Such VHDs enable you to evaluate different software solutions in your own environment without the need for dedicated servers or complex installations. Use the [Hyper-V VHD Explorer|#Hyper-V VHD Explorer] graphical user interface to manage all your mounted VHD files.
----
h3. Volume{anchor:volume}
Volume is a storage of one or more [Disk Safes|#disksafe]. Volumes are so-called containers in the [Replication|#Replication] system. See: [Volumes|http://wiki.r1soft.com/display/CDP3/Volumes].
----
{excerpt:hidden=true}CDP Glossary{excerpt}