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

NAKIVO Backup & Replication allows you to use advanced deduplication appliances for data protection.

Notes

  • Before creating a Backup Repository on a Dell EMC DD, you need to install BoostFS Plugin and create a storage unit on the data domain backup appliance. Refer to Integrating with EMC DD Boost for details.
  • Before creating a Backup Repository on an NEC HYDRAstor, you need to configure the NEC HYDRAstor and the machine on which NAKIVO Transporter is installed. Refer to Integrating with NEC HYDRAstor for details.
  • To create a Backup Repository on other deduplication appliances, refer to Backup Repository on NFS Share

 To create a repository on a deduplication appliance, proceed as described in the following sections: 

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select Deduplication Appliance and click Next to go to the next page of the wizard.

Note

Refer to Storage Integration Requirements to see the list of supported advanced deduplication appliances.


Create Backup Repository: Device

  1. On the Device page, select one of the devices:
    • Dell EMC Data Domain Boost
    • HP StoreOnce Catalyst
    • NEC HYDRAstor
  2. Click Next to go to the next page of the wizard.


Create Backup Repository: Name and Location

On the Name & Location page, specify the following:

  1. Name: Enter a name for the Backup Repository.
  2. Assigned transporter: Choose a Transporter that will manage (that is, write data to and read data from) this Backup Repository.
  3. Depending on the deduplication appliance, provide the following information:
    • Dell EMC Data Domain Boost
      1. Name: Enter the name of your Backup Repository.
      2. Assigned transporter: Select the assigned Transporter.
      3. Path to the share: Enter the path to the share folder in the following format: <backup_appliance>:/<storage_unit>. Refer to Creating a NAKIVO Backup & Replication Backup Repository on EMC Data Domain Backup Appliance for details. 



    • HPE StoreOnce Catalyst
      1. Name: Enter the name of your Backup Repository.
      2. Assigned transporter: Select the assigned Transporter.
      3. Connection typeSelect one of the connection types to be used to access the Backup Repository:
        • IP address
        • Fibre Channel
      4. Depending on the connection type, do the following:
        • Server name (if IP address connection type is selected): Enter the server name or IP address of the HPE StoreOnce Catalyst.
        • COFC identifier (if Fibre Channel connection type is selected): Enter the COFC identifier. You can find your COFC identifier by going to Catalyst Settings>Fibre Channel in the StoreOnce Management Console.
      5. Catalyst store name: Enter the Catalyst store name.
      6. Username: Provide the username to the Catalyst store.
      7. Password: Provide the password to the Catalyst store.



    • NEC HYDRAstor
      1. Name: Enter the name of your Backup Repository.
      2. Assigned transporter: Select the assigned Transporter.
      3. Path to the mount point: Enter the path to the mount point in the following format: /opt/nakivo/repository/hsva. 


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

Create Backup Repository: Options

On the Options page, do the following:

  1. Set up Reliability & Maintenance options: 
    • Enable automatic repository self-healing: Leave this option selected to automatically trigger repository self-healing if the product detects symptoms of problems in the backup infrastructure, such as incorrect timestamps on metadata and data files. Optionally, you can deselect this option and run self-healing manually.
    • Run repository self-healing on schedule: If required, select this checkbox to additionally run repository self-healing according to a 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.
      When Stop backup and recovery to run self-healing is selected, any jobs or recoveries that use this Backup Repository are stopped before running scheduled self-healing. When the option is not selected, scheduled self-healing is skipped if there are running jobs or recoveries on this repository.
    • Run full data verification on schedule: When selected, full verification of all data available in the Backup Repository are performed as scheduled. The product reads each block of data and ensures that it is identical to the data block that was read on the source VM during the backup. This way, the product verifies each recovery point in the Backup Repository.
      When Stop backup and recovery to run backup verification is selected, any running jobs that use this Backup Repository are stopped before running scheduled data verification. If the option is not selected, scheduled data verification is skipped if there are running jobs on this Backup Repository.
  2. 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 according to 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: When this option is selected, all data in the Backup Repository is erased prior to attaching it to the product. As a result, jobs that write to this Backup Repository create full VM backups. You can use this option, for example, to create full daily, weekly, or monthly backups, and write them to tape or removable media.
  3. Click Finish to finish creating the local Backup Repository.



  • No labels