Page tree
Skip to end of metadata
Go to start of metadata

Prerequisites for Creating a Backup Repository on a Windows (CIFS) Share

If you want to create a Backup Repository on a Windows (CIFS) share, make sure that:

  • The folder where you want to create the Backup Repository already exists on the share.
  • The share can be accessed from the machine where NAKIVO Backup & Replication is installed.
  • Each Backup Repository is managed only by one Transporter (called Assigned Transporter) which writes data to and reads data from the Backup Repository. Make sure the share can be accessed from the machine where the Assigned Transporter is installed.
  • You have credentials with the “write” permissions to the share.
  • The share is compatible with Version 2 or later of the SMB protocol.

Creating a New Backup Repository

To create a new Backup Repository, follow the steps below:

  1. Click Configuration in the upper right corner of the product.
  2. Go to the Repositories tab and click Add Backup Repository:
  3. Click Create new backup repository
  4. Fill out the fields as described below:
    1. Name: Type in a name for the Backup Repository.
    2. The target is a deduplication appliance: Select this option in case the destination storage is a data deduplication appliance.
    3. Assigned transporter: Choose a Transporter that will be managing (i.e. writing data to and reading data from) this Backup Repository.
    4. Type: 
      • Forever incremental: After the initial full backup, all subsequent backups will transfer and store only changed data (increments) to the backup repository.  
      • Incremental with full backups:  After the initial full backup, backup jobs will store changed data (increments) in separate files and will periodically create full backups as specified in the job settings. Backup deduplication is not available when this option is selected.
    5. Location:
      • Local folder on assigned transporter: Choose this option if you want to create a backup repository locally on the machine where the Assigned Transporter is installed. Specify the path to the local folder on the Assigned Transporter in the appropriate field.
      • Remote CIFS share: Choose this option if you want to create a backup repository on a Windows CIFS share. In the appropriate fields, specify the following:

        1. Path to the CIFS share.

        2. Username.

        3. Password.

          If you're using domain credentials to access the share, enter your domain username using the following format: domain\username.

        4. Advanced mount options if needed. Please refer to the mount man pages for detailed description of CIFS share mount options.
      • Remote NFS share:  Choose this option if you want to create a backup repository on an NFS share. In the appropriate fields, specify the following: 

        1. Path to the NFS share.

          If the Assigned Transporter is installed on a Windows OS, you need to enable the "Client for NFS" feature on a machine where the Transporter is installed.

        2. Advanced mount options if needed. Please refer to the mount man pages for detailed description of NFS share mount options.

      • Amazon EBS: 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. 
        • Volume type: Choose a type of EBS volumes that will be used for creating the backup repository.
        • Storage: Specify the size for the Backup Repository that will be allocated in Amazon EC2 using EBS Volumes. The volumes will be attached to 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 to 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.

          Important

          1. To avoid disrupting NAKIVO Backup & Replication processes and data corruption, add the application to the whitelist / exclusions list of the antivirus software running on the machine where the NAKIVO backup repository is set up.

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

  5. To specify advanced options, click More options and do the following:

    Storage Savings & Encryption

    • Compression: Choose 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 changed after the Backup Repository is created.

    • Deduplication: Leave the Enabled option to store only unique blocks of data in the Backup Repository in order to save storage space.

      This option cannot be changed after the Backup Repository is created.

    • Encryption: This option is available only if the backup repository is created locally on the machine where the Assigned Transporter is installed, and the machine is running a Linux OS. Choose 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. 

      Backup repository encryption can significantly influence backup speed.

    Reliability & Maintenance

    • 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 check box to additionally 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 the Scheduled self-healing has higher priority over running jobs option is selected:
        • Any running jobs which use this backup repository will be stopped to run self-healing. 
        • When the self-healing is running, new jobs will not be able to start and the job run will fail.
      • If the Scheduled self-healing has higher priority over running jobs option is deselected:
        • Self-healing will be canceled if there are any running jobs which use this repository. 
        • Self-healing will be canceled if a job, which uses this backup repository is started.
    • Run full data verification on schedule: If selected, the product 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 the Scheduled data verification has higher priority over running jobs option is selected:
        • Any running jobs which use this backup repository will be stopped to run data verification. 
        • When the data verification is running, new jobs will not be able to start and the job run will fail.
      • If the Scheduled data verification has higher priority over running jobs option is deselected:
        • Data verification will be canceled if there are any running jobs which use this repository. 
        • Data verification will be canceled if a job, which uses this backup repository is started.

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

    • Reclaim unused space on schedule: If required, select this option to run the Backup Repository space reclaim process 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 Saturday at 12 pm.
      • If the Scheduled space reclaim has higher priority over running jobs option is selected:
        • Any running jobs which use this backup repository will be stopped to run space reclaim. 
        • When the space reclaim is running, new jobs will not be able to start and the job run will fail.
      • If the Scheduled data verification has higher priority over running jobs option is deselected:
        • Space reclaim will be canceled if there are any running jobs which use this repository. 
        • Space reclaim will be canceled if a job, which uses this backup repository is started.

    Scheduled Detach

    • 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 archival 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 a tape or removable media.
  6. Click Create. The Backup Repository is created with the options that you have specified.

  • No labels