Backup Repository in Amazon EC2

Choose this option if you want to create a Backup Repository in Amazon EC2. The Backup Repository will be created in the same region where the assigned Transported is located. 


  • To avoid disrupting NAKIVO Backup & Replication processes and data corruption, add NAKIVO Backup & Replication to the white/exclusions list of the antivirus software running on the machine on which the NAKIVO Backup Repository is set up.

  • You may be additionally charged for using a 3rd-party resource. Please refer to the 3rd-party resource provider documentation for details.

To create a repository on an Amazon EC2, proceed as described in the following sections: 

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select Amazon EC2 and click Next to move to the next page of the wizard.

Create Backup Repository: Name and Location

On the Name & Location page of the wizard, do the following

  1. Enter the name of the Backup Repository in the Name box. 

  2. Select the Transporter from the Assigned transporter drop-down list. 

  3. Click Next to go to the next page of the wizard.

Create Backup Repository: Options

On the Options page, do the following:

Configure data storage options:

  • Volume type: Choose one of the following EBS volumes that will be used for creating the Backup Repository:

    • Cold HDD (sc1)

    • Throughput Optimized HDD (st1)

    • General Purpose SDD (gp2)

    • Magnetic Standard

  • Storage: Specify the size for the Backup Repository that will be allocated in Amazon EC2 using EBS Volumes. The volumes will be attached to the selected Amazon EC2 Transporter.

  • Storage Chunk: A Backup Repository in Amazon EC2 is created by using multiple EBS Volumes (chunks). The maximum size of the Backup Repository is limited by 50 EBS Volumes (chunks) or 16 TB (whatever comes first). The size of a storage chunk defines the size of each individual EBS volume. Also, the storage will be resized (either manually or automatically) with the minimal step of the storage chunk specified here. To scale up to 16000 GB, it is recommended that you have 400 GB storage chunk or bigger. Storage chunk cannot be changed later.

  • Automatically resize storage: If this option is selected, the cloud storage will be automatically increased and reduced as required.

Set up Storage Savings & Encryption options:

  • Data size reduction: If this option is enabled, NAKIVO Backup & Replication enables the use of data size reduction for this repository to save disk space. Note that this may put additional load on the CPU. Disabling data size reduction is required if the target is a deduplication storage appliance. Click settings to configure the settings. A popup window appears. Set the following:

    • Compression: Select a compression level that will be used to reduce the data size in the Backup Repository. Note that higher compression levels consume considerably more CPU and may slow down VM backup speed. The following options are available:

      • Disabled: The data in the Backup Repository will not be compressed.

      • Fast: Lowest compression level.

      • Medium: Medium compression level.

      • Best: Maximum compression level.

      This option cannot be configured after creating the Backup Repository.


    • Store backups in separate files: Select this option to enable this backup repository to store data of every machine in separate backup files. Enabling this option is highly recommended to ensure higher reliability and performance.

  • Encryption: This option is available only if the Backup Repository is created locally on the machine on which the Assigned Transporter is installed, and the machine is running a Linux OS. Select  Enabled from the drop-down list and specify an encryption password. (The password will be required for importing the Backup Repository into a new instance of the product.) The product will encrypt the repository destination (using ecryptfs for folders and cryptsetup (crypt-md) in LUKS mode for devices/partitions) prior to creating the Backup Repository.



    • To avoid ecryptfs errors, make sure that there are no other folders and files except the NakivoBackup folder in the repository location.

    •  Backup Repository encryption can significantly influence backup speed.


Set up Reliability & Maintenance options: 

  • Enable automatic repository self-healing: Leave this option selected to automatically trigger repository self-healing in case the product detects symptoms of problems in the backup infrastructure such as incorrect timestamps on metadata and data files. You can deselect this option and run self-healing manually.

  • Run repository self-healing on schedule: If required, select this checkbox to run repository self-healing on schedule. You can configure the schedule by clicking the schedule link when the option is selected. The default schedule is set to run every day at 11 AM.
    If Stop backup and recovery to run self-healing is selected, any jobs or recoveries which use this repository will be stopped to run scheduled self-healing. Otherwise, scheduled self-healing will be skipped in case there are running jobs or recoveries on this repository.

  • Run full data verification on schedule: If selected, NAKIVO Backup & Replication will run full verification of all data available in the Backup Repository on the specified schedule. The product will read each block of data and ensure that it is identical to the data block that was read on the source VM during the backup. This way, the product will verify each recovery points in the Backup Repository.
    If Stop backup and recovery to run backup verification is selected, any running jobs which use this Backup Repository will be stopped to run scheduled data verification. Otherwise, scheduled data verification will be skipped in case there are running jobs on this Backup Repository.


    Backup verification is a time-consuming process and consumes CPU of the Transporter assigned to the Backup Repository. It is recommended that you schedule backup verification during non-working hours


  • Reclaim unused space on schedule: If required, select this option to run the Backup Repository space reclaim process on schedule. Space reclaim will compact the data. Unused space will be reclaimed. Keep in mind that this process can be time-consuming.


    This option is available only if Store backups in separate files is not enabled.


    If Stop backup and recovery to run space reclaim is selected, any running jobs which use this Backup Repository will be stopped to run scheduled space reclaiming. Otherwise, scheduled space reclaiming will be skipped in case there are running jobs on this Backup Repository.


    Do not reboot/disconnect the "null" Transporter and storage device while space reclaim is in progress to avoid Backup Repository corruption.

  • Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all backup operations to this repository. This setting is considered more reliable but may lead to lower performance on certain storage devices. By default, the option is disabled.

Schedule detaching of the Backup Repository: 

  • Detach this repository on schedule: Select this option if you want to detach and then attach the Backup Repository on a schedule. Detaching a Backup Repository saves the Backup Repository data and metadata in a consistent state and then stops the product's interaction with the Backup Repository (so that the Backup Repository can be copied or moved). You can use this feature, for example, for the disk-to-disk-to-tape (D2D2T) data protection approach, in which backups are stored on a disk for fast operational recovery, and copied to a tape (while the repository is detached) for archiving and long-term storage. 

    • Delete and re-create the repository on attach: If this option is selected, all data in the Backup Repository will be erased prior to attaching it to the product. As a result, jobs that write to this Backup Repository will create full VM backups. You can use this option, for example, to create full daily, weekly, or monthly VM backups and write them to tape or removable media.

Click Finish to finish creating the Backup Repository.