November 24, 2014
NAKIVO Backup & Replication Components – Backup Repository
A backup repository is one of the key components of NAKIVO Backup & Replication and is a regular folder where the product stores VM backups and backup metadata. When you add a new repository, NAKIVO Backup & Replication creates a folder named “NakivoBackup” in the specified location and keeps all the VM data and backup metadata in that folder.
To enable forever incremental backups, compression, and global data deduplication VM backups are stored in a proprietary format using the “full synthetic” mode. This means that each recovery point “knows” which data blocks in the backup repository should be used to reconstruct an entire VM. Thus, there is no need to apply increments one by one to get to a particular recovery point or periodically transform backed up data to create a new recovery point.
Backup Repository Creation
To make initial setup simple, a backup repository (named “Onboard repository”) is created by default with the product installation, to enable you to start backing up VMs right after deploying NAKIVO Backup & Replication.
Also, you can create a repository either on a Windows (CIFS) share or in a local folder on the machine where a Transporter is installed. This way you can mount any storage type (such as SAN, NAS, NFS, and so on) to the machine where a Transporter is installed and use it as a backup repository.
Note that both data compression and deduplication features are turned on by default when a new backup repository is created. However, these features can be turned off if, for example, you want to use a hardware-based deduplication device such as an EMC® Data Domain.
You also need to specify an Assigned Transporter, the one that will be used to read data from and write data to your new Backup Repository:
The Assigned Transporter is responsible for all interaction with its Repository. However, a single Transporter can be assigned to and manage multiple backup repositories:
Should you lose your NAKIVO Backup & Replication instance, you can always install a new copy of the product and import your existing backup repositories.