{toc:location=top|maxLevel=3|minLevel=3|type=flat|separator=pipe|style=border:1}
----
h3. alert{anchor:alert1}
Server Backup generates warning alerts to inform users that the current course of action could be dangerous or detrimental in some way.
----
h3. API{anchor:api1}
An application programming interface (API) is an interface implemented by a software program that enables the program to interact with other software. For more information about the Server Backup API, see [Use the Server Backup API].
----
h3. archive point{anchor:archivepoint1}
An archive point is a copy of the most recent [recovery point|#recoverypoint1], which is used for long-term data storage to provide further integrity and safe keeping of data. Archive points support all functionality of the recovery point. You can browse and restore your files as well as perform a [bare-metal restore|Perform a bare-metal restore]. For more information about archive points, see [Manage archiving].
----
h3. archiving{anchor:archiving1}
Server Backup includes advanced recovery point archiving rules. This process involves archiving the most recently available recovery point as configured on an hourly/daily/weekly/monthly/yearly basis for long-term storage. For more information about archiving, see [Manage archiving].
----
h3. Backup agent{anchor:Backup agent1}
The small application that runs on protected servers and communicates with the Server Backup Manager. The Backup agent is often referred to as the "cdp-agent" or "CDP Agent," which is the name of the startup script on Linux.
----
h3. Backup server{anchor:Backup server1}
The Backup server is the system where backups are stored and processed for restorations.
----
h3. bare metal{anchor:baremetal1}
A bare-metal system is a new computer system that does not contain an operating system or any software.
----
h3. bare-metal restore {anchor:baremetalrestore1}
The Server Backup bare-metal restore is the process of instantly rebuilding a computer or server from scratch after a catastrophic failure. Server Backup application allows to restore servers directly from disk-based backup. There is no need to first partition your drive and install the operating system. For more information about bare-metal restores, see [Perform a bare-metal restore|ServerBackup:Perform a bare-metal restore].
----
h3. blocks{anchor:block1}
The file system of every operating system divides the hard disk into groups of bytes called blocks. A block-based backup application reads the data from these blocks. Block-based backups are more efficient than backup applications that read every file using file system, which is a slow and time consuming process.
----
h3. compression{anchor:compression1}
Compression is the reduction in size of data in order to save disk space or transmission time. Server Backup uses two types of compression: Zlib or QuickLZ.
----
h3. control panel instance{anchor:instance1}
A control panel instance is an occurrence of a hosting control panel or certain installation on the server where the Backup Agent resides. When working with [policies|Manage policies], you must add the instance to the policy. For each instance, specify the control panel type, name, description, and Virtuozzo Container ID if it exists. For more information about control panels instances and hosting control panels, see [Hosting control panels|Hosting control panels].
----
h3. data protection policy{anchor:dataprotectionpolicy1}
See [policy|#policy1].
----
h3. delta {anchor:deltas}
A delta is the data that changed since the last backup run. Various types of data are considered deltas depending on how the backup application computes deltas. You may consider a delta as a raw disk [block|#Blocks1], a variables-length portion of a file, or even a complete file depending on the method of calculation.
----
h3. Disk Safe{anchor:disk safe1}
Server Backup uses the block deltas database to map the block [deltas|#deltas] versions and [recovery points|#recoverypoint1]. This database is a Disk Safe. Disk Safes contain the data needed to restore the devices on a server. Note that you can also create encrypted Disk Safes. For more information about Disk Safes, see [Manage Disk Safes].
----
h3. export{anchor:export1}
an export occurs when you move files from a [recovery point|#recovery point1] in the [Disk Safe|#disk safe1] to an off-site server or local hard disk. For more information about exporting a Disk Safe, see [Copy or move Disk Safes|Copy or move Disk Safes].
----
h3. file excludes{anchor:file excludes1}
File excludes are files and folders that a user wants to excluded from [replications|#replication1]. The system allows you to define various exclude rules while customizing the settings of a replication. For more information about file excludes, see [ServerBackup:Exclude files and folders].
----
h3. full block scan{anchor:fullblockscan1}
A full block scan is a particular type of Server Backup [replication|#replication1] of a device. This scan occurs under certain conditions and is required to get the asynchronous replication back in sync. Not that this is a time\- and resource-consuming process that may reduce network throughput.
----
h3. GUID{anchor:guid1}
The system generates a globally unique identifier (GUID) as a unique reference number in computer software. The value of a GUID is represented as a 32-character string, such as _0f6b6a6e-d444-4c77-a026-f76be7723e16_.
----
h3. Hyper-V VHD Explorer{anchor:Hyper-V VHD Explorer1}
R1Soft offers Hyper-V VHD Explorer for you to mount and dismount your Hyper-V virtual hard disk ([VHD|#VHD1]) files. Explorer shell integration adds right-click attach and detach actions to {{.vhd}} files in Microsoft Windows Explorer. Use the Hyper-V VHD Explorer as a graphical user interface to manage all your mounted [VHD|#VHD1] files. For more information about Hyper-V VHD Explorer, see the product page on the R1Soft Website at [www.r1soft.com|http://www.r1soft.com].
----
h3. initial replica{anchor:initialreplica1}
The first [recovery point|#recoverypoint1] that contains all used parts of the hard disk except for excludes. Subsequent [synchronizations|#synchronization1] contain only [deltas|#delta1].
----
h3. Limit disk space available to Server Backup {anchor:Limit Disk Space Available to Server Backup Manager1}
Limited disk space available to Server Backup is an option that defines how much free space is left available for use by Server Backup. This is an effective limit defined in percent of the device volume. When the system reaches the set limit, you cannot generate any new [recovery points|#recovery point1]. As a result, any [replication|#replication1] stops and fails.
----
h3.
h3. locking recovery points {anchor:lock1}
Server Backup allows you to lock [recovery points|#recoverypoint1] and protect them from a [merge|#merge1] or deletion. note that when a recovery point is locked, Server Backup cannot perform the Disk Safe verification task. For more information about this task, see [Schedule Disk Safe verification|Schedule Disk Safe verification].
----
h3. log files{anchor:logfiles1}
A log file is a file that lists actions as they occur. Server Backup includes log files that contain messages from tasks performed by the Backup Agent ({{cdp.log}}), log files that contain messages from the Backup Manager ({{server.log}}), and log files that contain messages from the Web GUI and start up/shut down tasks ({{monitor.log}}). For more information about log files, see [ServerBackup:Access log files].
----
h3. manager key{anchor:serverkey1}
As a security precaution, [Backup Agent|#Agents1] allows connections only from specified Backup Managers. To specify a Backup Manager, add a manager public key to the Backup Agent by creating the appropriate text file on the server. For more information about encryption keys, see [Add key to Linux Backup Agent] and [ServerBackup:Add the key to Windows Backup Agent].
----
h3. merge recovery points {anchor:merge1}
When you delete a [recovery point|#recoverypoint1] you are actually merging the unwanted recovery point and closest existing recovery point. You can discard [deltas|#delta1] between the two recovery points and free the space the data consumes in the [Disk Safe|#Disk Safe1]. For more information about recovery points, see [ServerBackup:Merge recovery points].
----
h3. mount point{anchor:mountpoint1}
In Unix-like systems, a mount point is the location in the operating system directory structure where a mounted file system appears. In Microsoft Windows, mapping a drive is the equivalent to a mount point.
----
h3.
h3. MySQL{anchor:mysql1}
MySQL is database software that features a variety of tools and provides multi-user access to a number of databases. Server Backup allows to back up and restore MySQL databases. For more information about Server Backup and MySQL, see [Protect MySQL].
----
h3. partition{anchor:partition1}
Partition as an action means to divide memory or mass storage into isolated section within the hard disk. A partition table is a placeholder for the description of a partition on the hard disk.
----
h3. policy (data protection policy){anchor:policy1}
A policy is a schedule of Disk Safe replication and is assigned to a [Disk Safe|#disksafe1]. You can create one-time policies or schedule recurring policies. Policy properties allows you to start the policy at a set time and include the number of recovery points you want to keep in the Disk Safe. For more information about using policies, see [Manage policies].
----
h3. policy frequency{anchor:Policy Frequency1}
Policy frequency is the recurrence selected for running the policy. You can select the policy to run:
* On demand
* By the minute or hour
* Daily, weekly, monthly, or yearly
For more information about using policies, see [Manage policies].
----
h3. recovery point{anchor:recoverypoint1}
A recovery point is a set of many [deltas|#deltas] that represent the state of a disk volume [block|#block1] at a particular point in time. Each delta is available for use by one or more recovery points. The [Disk Safe|#disksafe1] maintains the relationship between deltas and recovery points. For more information about recovery points, see [ServerBackup:Manage recovery points].
----
h3. recovery point limit or retention{anchor:retention1}
Recovery point limit or retention defines how many recovery points you want to keep in the [Disk Safe|#disksafe1]. Note that the system [merges|#merge1] old recovery points. For more information about recovery points, see [Manage recovery points].
----
h3. replication{anchor:replication1}
Replication is the operation of copying block-level [deltas|#deltas] from the [server|#agent1] to Server Backup into a new [recovery point|#recoverypoint1]. Each replication creates a point-in-time image or recovery point of the device. For more information about replication stages, see [Understand the replication stages].
----
h3. SBM{anchor:SBM1}
SBM (Server Backup Manager) is the abbreviation used to refer to both the SBM product and the management software running on the Backup server.
----
h3. servers{anchor:agent1}
Servers are computers that are backed up or replicated. Server Backup allows you to manage backups for multiple servers. For more information about servers, see [Manage servers].
----
h3. snapshot the disk or volume{anchor:snapshot1}
The first stage of [replication|#replication1] is to create a snapshot of the disk or volume. The system creates a point-in-time snapshot of the server file system for a consistent, open file backup.
----
h3. synchronization{anchor:synchronization1}
Synchronization is the process of creating the [Disk Safe|#disksafe1] point-in-time snapshot and computing [deltas|#deltas] based on the last completed synchronization. For more information about synchronization, see [Manage policies].
----
h3. vacuuming Disk Safes{anchor:vacuum1}
Vacuuming a [Disk Safe|#disksafe1] is the process of reducing the on-disk size by "vacuuming" or removing [blocks|#block1] that are no longer used by a file system. For more information about vacuuming, see [Vacuum Disk Safes|Vacuum Disk Safes].
----
h3. VHD{anchor:vhd1}
Virtual Hard Disk (VHD) is a file format used as a hard disk of a virtual machine. VHD allows you to deploy multiple operating systems on a single host machine. VHDs are available with software that enables you to evaluate different software solutions in your own environment without the need for dedicated servers or complex installations. The [Hyper-V VHD Explorer|#Hyper-V VHD Explorer1] allows you to manage all your mounted VHD files. For more information about Hyper-V VHD Explorer, see the product page on the R1Soft Website at [www.r1soft.com|http://www.r1soft.com].
----
h3. volume{anchor:volume1}
Volume is the storage capacity of one or more [Disk Safes|#disksafe1]. Volumes are containers in the [replication|#replication1] system. For more information about volumes, see [Manage volumes].
----
h3. Warn when disk usage exceeds
Warn when disk usage exceeds is a warning level where users are informed that they are close to reaching their effective limit. The level is also defined in percent of the device volume. This limit is usually a lesser value to the Limit disk space available to Server Backup option.
----
{excerpt:hidden=true}A glossary of terms for Server Backup Manager.{excerpt}
----
h3. alert{anchor:alert1}
Server Backup generates warning alerts to inform users that the current course of action could be dangerous or detrimental in some way.
----
h3. API{anchor:api1}
An application programming interface (API) is an interface implemented by a software program that enables the program to interact with other software. For more information about the Server Backup API, see [Use the Server Backup API].
----
h3. archive point{anchor:archivepoint1}
An archive point is a copy of the most recent [recovery point|#recoverypoint1], which is used for long-term data storage to provide further integrity and safe keeping of data. Archive points support all functionality of the recovery point. You can browse and restore your files as well as perform a [bare-metal restore|Perform a bare-metal restore]. For more information about archive points, see [Manage archiving].
----
h3. archiving{anchor:archiving1}
Server Backup includes advanced recovery point archiving rules. This process involves archiving the most recently available recovery point as configured on an hourly/daily/weekly/monthly/yearly basis for long-term storage. For more information about archiving, see [Manage archiving].
----
h3. Backup agent{anchor:Backup agent1}
The small application that runs on protected servers and communicates with the Server Backup Manager. The Backup agent is often referred to as the "cdp-agent" or "CDP Agent," which is the name of the startup script on Linux.
----
h3. Backup server{anchor:Backup server1}
The Backup server is the system where backups are stored and processed for restorations.
----
h3. bare metal{anchor:baremetal1}
A bare-metal system is a new computer system that does not contain an operating system or any software.
----
h3. bare-metal restore {anchor:baremetalrestore1}
The Server Backup bare-metal restore is the process of instantly rebuilding a computer or server from scratch after a catastrophic failure. Server Backup application allows to restore servers directly from disk-based backup. There is no need to first partition your drive and install the operating system. For more information about bare-metal restores, see [Perform a bare-metal restore|ServerBackup:Perform a bare-metal restore].
----
h3. blocks{anchor:block1}
The file system of every operating system divides the hard disk into groups of bytes called blocks. A block-based backup application reads the data from these blocks. Block-based backups are more efficient than backup applications that read every file using file system, which is a slow and time consuming process.
----
h3. compression{anchor:compression1}
Compression is the reduction in size of data in order to save disk space or transmission time. Server Backup uses two types of compression: Zlib or QuickLZ.
----
h3. control panel instance{anchor:instance1}
A control panel instance is an occurrence of a hosting control panel or certain installation on the server where the Backup Agent resides. When working with [policies|Manage policies], you must add the instance to the policy. For each instance, specify the control panel type, name, description, and Virtuozzo Container ID if it exists. For more information about control panels instances and hosting control panels, see [Hosting control panels|Hosting control panels].
----
h3. data protection policy{anchor:dataprotectionpolicy1}
See [policy|#policy1].
----
h3. delta {anchor:deltas}
A delta is the data that changed since the last backup run. Various types of data are considered deltas depending on how the backup application computes deltas. You may consider a delta as a raw disk [block|#Blocks1], a variables-length portion of a file, or even a complete file depending on the method of calculation.
----
h3. Disk Safe{anchor:disk safe1}
Server Backup uses the block deltas database to map the block [deltas|#deltas] versions and [recovery points|#recoverypoint1]. This database is a Disk Safe. Disk Safes contain the data needed to restore the devices on a server. Note that you can also create encrypted Disk Safes. For more information about Disk Safes, see [Manage Disk Safes].
----
h3. export{anchor:export1}
an export occurs when you move files from a [recovery point|#recovery point1] in the [Disk Safe|#disk safe1] to an off-site server or local hard disk. For more information about exporting a Disk Safe, see [Copy or move Disk Safes|Copy or move Disk Safes].
----
h3. file excludes{anchor:file excludes1}
File excludes are files and folders that a user wants to excluded from [replications|#replication1]. The system allows you to define various exclude rules while customizing the settings of a replication. For more information about file excludes, see [ServerBackup:Exclude files and folders].
----
h3. full block scan{anchor:fullblockscan1}
A full block scan is a particular type of Server Backup [replication|#replication1] of a device. This scan occurs under certain conditions and is required to get the asynchronous replication back in sync. Not that this is a time\- and resource-consuming process that may reduce network throughput.
----
h3. GUID{anchor:guid1}
The system generates a globally unique identifier (GUID) as a unique reference number in computer software. The value of a GUID is represented as a 32-character string, such as _0f6b6a6e-d444-4c77-a026-f76be7723e16_.
----
h3. Hyper-V VHD Explorer{anchor:Hyper-V VHD Explorer1}
R1Soft offers Hyper-V VHD Explorer for you to mount and dismount your Hyper-V virtual hard disk ([VHD|#VHD1]) files. Explorer shell integration adds right-click attach and detach actions to {{.vhd}} files in Microsoft Windows Explorer. Use the Hyper-V VHD Explorer as a graphical user interface to manage all your mounted [VHD|#VHD1] files. For more information about Hyper-V VHD Explorer, see the product page on the R1Soft Website at [www.r1soft.com|http://www.r1soft.com].
----
h3. initial replica{anchor:initialreplica1}
The first [recovery point|#recoverypoint1] that contains all used parts of the hard disk except for excludes. Subsequent [synchronizations|#synchronization1] contain only [deltas|#delta1].
----
h3. Limit disk space available to Server Backup {anchor:Limit Disk Space Available to Server Backup Manager1}
Limited disk space available to Server Backup is an option that defines how much free space is left available for use by Server Backup. This is an effective limit defined in percent of the device volume. When the system reaches the set limit, you cannot generate any new [recovery points|#recovery point1]. As a result, any [replication|#replication1] stops and fails.
----
h3.
h3. locking recovery points {anchor:lock1}
Server Backup allows you to lock [recovery points|#recoverypoint1] and protect them from a [merge|#merge1] or deletion. note that when a recovery point is locked, Server Backup cannot perform the Disk Safe verification task. For more information about this task, see [Schedule Disk Safe verification|Schedule Disk Safe verification].
----
h3. log files{anchor:logfiles1}
A log file is a file that lists actions as they occur. Server Backup includes log files that contain messages from tasks performed by the Backup Agent ({{cdp.log}}), log files that contain messages from the Backup Manager ({{server.log}}), and log files that contain messages from the Web GUI and start up/shut down tasks ({{monitor.log}}). For more information about log files, see [ServerBackup:Access log files].
----
h3. manager key{anchor:serverkey1}
As a security precaution, [Backup Agent|#Agents1] allows connections only from specified Backup Managers. To specify a Backup Manager, add a manager public key to the Backup Agent by creating the appropriate text file on the server. For more information about encryption keys, see [Add key to Linux Backup Agent] and [ServerBackup:Add the key to Windows Backup Agent].
----
h3. merge recovery points {anchor:merge1}
When you delete a [recovery point|#recoverypoint1] you are actually merging the unwanted recovery point and closest existing recovery point. You can discard [deltas|#delta1] between the two recovery points and free the space the data consumes in the [Disk Safe|#Disk Safe1]. For more information about recovery points, see [ServerBackup:Merge recovery points].
----
h3. mount point{anchor:mountpoint1}
In Unix-like systems, a mount point is the location in the operating system directory structure where a mounted file system appears. In Microsoft Windows, mapping a drive is the equivalent to a mount point.
----
h3.
h3. MySQL{anchor:mysql1}
MySQL is database software that features a variety of tools and provides multi-user access to a number of databases. Server Backup allows to back up and restore MySQL databases. For more information about Server Backup and MySQL, see [Protect MySQL].
----
h3. partition{anchor:partition1}
Partition as an action means to divide memory or mass storage into isolated section within the hard disk. A partition table is a placeholder for the description of a partition on the hard disk.
----
h3. policy (data protection policy){anchor:policy1}
A policy is a schedule of Disk Safe replication and is assigned to a [Disk Safe|#disksafe1]. You can create one-time policies or schedule recurring policies. Policy properties allows you to start the policy at a set time and include the number of recovery points you want to keep in the Disk Safe. For more information about using policies, see [Manage policies].
----
h3. policy frequency{anchor:Policy Frequency1}
Policy frequency is the recurrence selected for running the policy. You can select the policy to run:
* On demand
* By the minute or hour
* Daily, weekly, monthly, or yearly
For more information about using policies, see [Manage policies].
----
h3. recovery point{anchor:recoverypoint1}
A recovery point is a set of many [deltas|#deltas] that represent the state of a disk volume [block|#block1] at a particular point in time. Each delta is available for use by one or more recovery points. The [Disk Safe|#disksafe1] maintains the relationship between deltas and recovery points. For more information about recovery points, see [ServerBackup:Manage recovery points].
----
h3. recovery point limit or retention{anchor:retention1}
Recovery point limit or retention defines how many recovery points you want to keep in the [Disk Safe|#disksafe1]. Note that the system [merges|#merge1] old recovery points. For more information about recovery points, see [Manage recovery points].
----
h3. replication{anchor:replication1}
Replication is the operation of copying block-level [deltas|#deltas] from the [server|#agent1] to Server Backup into a new [recovery point|#recoverypoint1]. Each replication creates a point-in-time image or recovery point of the device. For more information about replication stages, see [Understand the replication stages].
----
h3. SBM{anchor:SBM1}
SBM (Server Backup Manager) is the abbreviation used to refer to both the SBM product and the management software running on the Backup server.
----
h3. servers{anchor:agent1}
Servers are computers that are backed up or replicated. Server Backup allows you to manage backups for multiple servers. For more information about servers, see [Manage servers].
----
h3. snapshot the disk or volume{anchor:snapshot1}
The first stage of [replication|#replication1] is to create a snapshot of the disk or volume. The system creates a point-in-time snapshot of the server file system for a consistent, open file backup.
----
h3. synchronization{anchor:synchronization1}
Synchronization is the process of creating the [Disk Safe|#disksafe1] point-in-time snapshot and computing [deltas|#deltas] based on the last completed synchronization. For more information about synchronization, see [Manage policies].
----
h3. vacuuming Disk Safes{anchor:vacuum1}
Vacuuming a [Disk Safe|#disksafe1] is the process of reducing the on-disk size by "vacuuming" or removing [blocks|#block1] that are no longer used by a file system. For more information about vacuuming, see [Vacuum Disk Safes|Vacuum Disk Safes].
----
h3. VHD{anchor:vhd1}
Virtual Hard Disk (VHD) is a file format used as a hard disk of a virtual machine. VHD allows you to deploy multiple operating systems on a single host machine. VHDs are available with software that enables you to evaluate different software solutions in your own environment without the need for dedicated servers or complex installations. The [Hyper-V VHD Explorer|#Hyper-V VHD Explorer1] allows you to manage all your mounted VHD files. For more information about Hyper-V VHD Explorer, see the product page on the R1Soft Website at [www.r1soft.com|http://www.r1soft.com].
----
h3. volume{anchor:volume1}
Volume is the storage capacity of one or more [Disk Safes|#disksafe1]. Volumes are containers in the [replication|#replication1] system. For more information about volumes, see [Manage volumes].
----
h3. Warn when disk usage exceeds
Warn when disk usage exceeds is a warning level where users are informed that they are close to reaching their effective limit. The level is also defined in percent of the device volume. This limit is usually a lesser value to the Limit disk space available to Server Backup option.
----
{excerpt:hidden=true}A glossary of terms for Server Backup Manager.{excerpt}