Glossary

This article explains various terms that you can come across in this help system.

Backup Plan

A backup plan determines which files in your local storage should be monitored and uploaded to the destination (cloud or local) storage. These files can be referred to as "backup source" and CloudBerry Backup can upload multiple versions of each file to your destination storage.

CloudBerry Backup uses timestamps to identify which of your files have been modified and your backups include only files/folders that were modified since the previous backup date. The file version control is maintained by providing a synchronization layer between your cloud and local storages.

After you have scheduled a backup plan, the backup service will automatically execute it in the background at the specified time.

See Backup Plans to learn more.

Backup Chain

You can make CloudBerry Backup execute multiple backup tasks one after another by specifying which backup task should be performed next, after completing the current backup plan.

After chaining your backups, you can choose whether to execute the specified plan only after successfully completing the current task, or regardless of its execution result.

Backup Client

A separate instance of CloudBerry Backup is supposed to be installed on every computer that you wish to use for processing and uploading backups. This desktop application instance is referred to as a "backup client".

Backup Prefix

A single bucket (or container in terms of a different cloud provider) can store backups from different computers and the backup prefix is used to identify different backups within the same bucket.

See Changing the Backup Prefix to Access Backups from Another Computer for more information.

Backup Service

CloudBerry Backup does not need to be constantly running in the background. To be able to process backups on schedule, the installation registers a service (or daemon, in Linux terms) in your operating system that automatically performs the required tasks in the background without the need for any user intervention.

You can make the backup service to automatically restart scheduled backup/restore tasks when a computer starts up if the backup processing was previously interrupted for any reason.

Backup Source

A backup's configuration determines which files in your local storage the backup service should monitor and upload to the destination storage. These files can be referred to as backup source and CloudBerry Backup can upload multiple versions of each file to your destination storage.

CloudBerry Backup maintains the file version control by providing a synchronization layer between your cloud and local storages.

Block-Level Backup

As opposed to a full backup which uploads a complete copy of each file to a storage, a block-level backup uploads the full copy of your data only during the first execution of the backup plan and when explicitly forced to do this. In other cases, the backup service uploads only blocks (parts of a file) that were modified since the last backup date, which can dramatically decrease the processing time required for completing your backup routine, as well as reduce the required storage space.

Instead of uploading complete copies of modified files, which is the case with incremental backup, a block-level backup operates with modified file blocks.

See Block-Level Backup for more information.

Backup Service Account

The service account is a user account under which CloudBerry Backup is running. The privileges granted to this account may forbid processing of certain files (such as system and protected files).

The application is running under the Local System account by default, which can prevent the backup service from accessing certain files and folders.

You can also consider making the service account under which CloudBerry Backup is running a member of the Backup Operators group to ensure that files are backed up regardless of any security permissions assigned to them.

See Changing the Backup Service Account for more information.

Bucket / Container

A bucket (or container in terms of a different cloud provider) is used to store your data in the cloud. You can use buckets to organize your data and control access to it, but unlike directories and folders, you cannot nest buckets. The implementation of buckets may differ among various cloud providers. Please consult your cloud provider's documentation to learn more about using buckets/containers.

When a bucket stores backups uploaded from different computers, the backup prefix is used to identify different backups within the same bucket.

CLI

CloudBerry Backup provides command line interface for managing your backup routines without the need to use the application's graphical user interface (GUI).

Please be informed about the differences in CLI implementation between various CloudBerry Backup editions (Windows, Linux and Mac).

See CLI to learn about the supported commands and their parameters.

Data Seeding

When you need to back up data on a computer that has a slow Internet connection, it makes sense to perform a full backup from another computer that has a faster network connection and then let the first computer to perform subsequent block-level backups for which the bandwidth throughput is not as important. This process is known as data seeding and you can learn about it in the following article: Seeding Data.

Differential Backup

Backing up Microsoft SQL Server data is performed by using the native differential backup functionality of SQL Server.

File-Level Backup

As opposed to an image-based backup which can store a complete disk image as a single object, a file-level backup can contain data stored in individual files and/or folders.

See Back Up Files/Folders to learn how you can set up a file-level backup.

Full Backup

In general, creating any backup starts with uploading a full copy of your data to the storage. However, it is unreasonable to create and upload a full copy of every file each time when you need to apply any changes made to your locally stored data to the backup stored in the cloud.

The way in which a full (or incremental) backup processes your data depends on the kind of data that you back up. See Full Backup to learn more.

Hybrid Backup

When you need to upload your backup to two destinations at once (e.g., on-site and off-site) and avoid repeated processing of data, you can choose to create a hybrid backup.

Image-Based Backup

An image-based backup stores the system state at a specific point of time, to which you can roll back in case of a system failure. An image stores information about files and folders, as well as system, application and software configuration.

You can restore an image-based backup to different destinations:

  • to a virtual machine in the cloud (such as Amazon EC2);
  • to a dissimilar hardware;
  • to a Hyper-V or VMware instance.

You can even create a recovery USB drive (or ISO disk image), as well as restore individual files from an image-based backup.

Similar to a basic file-level backup, you can store multiple versions of an image, which allows you to restore to a specific point in time. Without versions, you would end up having just one last copy of a system image that could become damaged or outdated.

Incremental Backup

When backing up files and/or folders, a full backup re-uploads an entire file only if it has been changed since the last backup date, which is similar to how incremental backup works.

See Full Backup for more information.

Ransomware Protection

You can protect your file-level backups against ransomware attacks by making CloudBerry Backup detect suspicious encryption activity over locally stored files in your backup.

See Ransomware Protection to learn more about using this feature.

Real-Time Backup

With CloudBerry Backup, you can enable the backup service to continuously scan your source files in the background and update the backup storage on detecting any changes made to these files in real time, without compromising the overall performance of your computer.

At present, real-time processing is not available for image-based backups.

See the following article for more information: Schedule Your Backup Plan.

Repository

CloudBerry Backup uses a service SQLite database to keep track of the backed up data and ensure that the backup services will not repeatedly upload files that already reside in the cloud. This reduces the number of requests sent to the cloud and lowers your storage bills.

You can do one of the following to ensure that your local repository is up to date:

  • Perform a consistency check to detect any discrepancies between the repository and the backup storage and take appropriate action on finding any mismatch.
  • Synchronize your repository to delete the current repository and update it according to the current backup storage contents from scratch.

Restore Plan

Similar to backup plans, you can save your restore configurations to be able to run them at a later time. You can mange restore plans using the Restore Wizard or command line interface (CLI).

Storage Account

To be able to upload your backups to a cloud or local storage, you need to grant CloudBerry Backup access to your cloud service provider by creating a storage account.

This account stores the credentials (or other settings, such as access keys required by some cloud service providers) that the application uses to access the corresponding storage to upload or restore your backups. The storage associated with a created account becomes a destination or target storage for your backups.

The storage account is exclusively owned and managed by a service provider. CloudBerry Lab does not provide any storage on its own.

Synthetic Full Backup

When choosing Amazon S3 as a target storage for your image-based backup and enabling block-level backup, you can enable a synthetic full backup as well.