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

Job Name

Specify a name for the backup job.

App-aware Mode

If the App-aware mode option is enabled, VM backup will be performed using VMware Guest OS Quiescing (which in turn relies on Microsoft VSS) to ensure that application data is consistent.

Change Tracking

Select one of the options from the Change tracking drop-down list:

  • Use VMware CBT: If this option is selected, NAKIVO Backup & Replication will enable the Changed Block Tracking feature for source VMs. This feature enables the product to quickly identify which data blocks have changed since the last job run, which significantly increases the job speed. Click the error handling link to specify the following options:
    • On CBT error. Choose either of the following job behaviors in relation to CBT error:
      • Switch to NAKIVO change tracking: If VMware CBT fails to provide data on changed blocks for a VM and this option is selected, NAKIVO Backup & Replication will perform the incremental backup of the VM using the proprietary change tracking technology.

      • Reset CBT: If VMware CBT fails to provide data on changed blocks for a VM and this option is selected, NAKIVO Backup & Replication will reset VMware CBT for the VM. 

      • Fail VM processing: If VMware CBT fails to provide data on changed blocks for a VM and this option is selected, NAKIVO Backup & Replication will not process the VM and will state job failure (other VMs in the job will be processed).

  • Double-check changed blocks provided by CBT: If this option is selected, NAKIVO Backup & Replication will run a check on data blocks provided by VMware CBT to ensure that VMware CBT does not overstate the amount of changed data.
  • Use NAKIVO change tracking: If this option is selected, NAKIVO Backup & Replication will perform incremental backups using a proprietary change tracking technology. This feature requires reading the contents of all VM disks to determine which data blocks have changed since the last job run.
  • No change tracking (always full): If this option is selected, NAKIVO Backup & Replication will always perform a full VM backup of all source VMs. 

Network Acceleration

If the Network Acceleration option is enabled, NAKIVO Backup & Replication will use compression and traffic reduction techniques to speed up data transfer. Select this option if you plan to back up over WAN or slow LAN links.

Encryption

If the Encryption option is enabled, VM data will be protected with AES 256 encryption while traveling over the network.

Data encryption increases the backup time and CPU load on machines running Transporters. Select this option if you back up over WAN without a VPN connection.

You need at least one Transporter at source and target sites to enable encryption.

Screenshot Verification

If the Screenshot verification is enabled, all VM backups created by the job will be verified as follows: after a backup of a VM is completed, the VM will be recovered from the backup using Flash VM Boot (and will be disconnected from networks), a screenshot of the recovered VM will be made once the VM OS has booted, after which the VM will be discarded. VM screenshots will be included in email notifications (if they’re configured), and in job reports.

Warning

VMware Tools must be running on source VMs to enable screenshot verification for your backup job successfully.


After choosing Enabled in the Screenshot verification drop-down list, do the following in the dialog box that opens:

  1. Provide a location of the VMs to be booted:
    1. Target Container: Choose a target container (cluster, host, or resource pool) where VMs will be run using Flash VM Boot.
    2. Target Datastore: Choose a datastore that will host changes to the recovered VMs.
    3. Proxy transporter:Choose a proxy transporter from the list of available transporters.

      Note

      NAKIVO Backup & Replication will use proxy transporter in cases:
      1. The transporter assigned to the repository cannot use iSCSI port 3260 because it is occupied by other services.
      2. iSCSI packages are missing on the transporter assigned to the repository.

  2. Provide verification options:
    1. Verify not more than X VMs simultaneously: Specify the maximum number of VMs that can be started on the Target Container simultaneously. 
    2. Recovery time objective: Specify the amount of time allocated for verification of each VM backup. If a VM OS does not start within the specified amount of time, verification will be considered failed.

      Specified time must be sufficient to fully start the VM OS. Try increasing this amount if the default amount is not sufficient.

    3. Screenshot delay: The amount of time that the product should wait after Guest OS start before making a screenshot.

Full Backup

If the Type of the Backup Repository that you selected on the Destination step is set to "Incremental with full backups", you can specify the following options:

  • Create full backup: Specify how often full backups should be created. 
  • Full backup mode: Specify how the full backup should be created. You can choose between the following options:
    • Synthetic Full: If this option is selected, NAKIVO Backup & Replication will first perform an incremental backup (that is, will transfer only the data that changed since the last backup) and will then transform the available data into a full backup file. The benefits of this approach are as follows:
      • The Synthetic Full backup is usually faster than the Active Full backup
      • The load on the network is lower, as less data is transferred
      • The load on the source datastores running your production VMs is lower 
    • Active Full: If this option is selected, NAKIVO Backup & Replication will read all VM data from the source datastore and transfer it to the backup repository. 

Email Notifications

NAKIVO Backup & Replication can send email notifications on job completion status to specified recipients. This feature complements global notifications and provides the ability to configure notifications on the per-job level.

To enable this option, configure your Email settings.

To send email notifications, select Send job run reports to and specify one or more email addresses in the text box. The semi-colon character should be used to separate multiple email addresses.

Truncation of Microsoft Exchange Transaction Logs

Microsoft Exchange Server database transaction logs record all changes to an Exchange Server database. Over time, these log files accumulate and can consume all of the available disk space, if not periodically removed. NAKIVO Backup & Replication provides an option to delete (aka truncate) Microsoft Exchange Server logs on the source VMs after job completion.

The transaction logs are deleted after the job completion so that the log files are available in the VM backup. Note that the product deletes only those transaction logs which are already committed to (available in) the Microsoft Exchange database.

To set up Microsoft Exchange log truncation, do the following:

  1. Select the Truncate Exchange logs option.
  2. In the pop-up dialog that opens, select check boxes next to the VMs running Microsoft Exchange and then select credentials next to each VM. These credentials will be used to log in into VMs you have selected. 

Truncation of Microsoft SQL Transaction Logs

Microsoft SQL Server database transaction logs record all changes to an SQL Server database. Over time, these logs accumulate and can consume all of the available disk space, if not periodically removed. NAKIVO Backup & Replication provides an option to delete (aka truncate) Microsoft SQL Server logs on the source VMs after job completion.

The transaction logs are deleted after the job completion so that the original log records are available in the VM backup. Note that the product deletes only those transaction logs which are already committed to (available in) the Microsoft SQL database.

To set up Microsoft SQL log truncation, do the following:

  1. Select the Truncate SQL logs option.

  2. In the pop-up dialog that opens, select check boxes next to the VMs running Microsoft SQL and then select credentials next to each VM. These credentials will be used to log in into VMs you have selected.


Pre and Post Job Scripts

NAKIVO Backup & Replication provides the ability to run a script before VM backup begins (a pre job script) and after the backup of all VMs in the job has completed (a post job script). The scripts can be executed only on the machine where the Director is installed. Do the following:

Setting Up a Pre Job Script

To run a script before the product begins backing up VMs, do the following:

  1. Place a script file on the machine where the Director is installed.
  2. Select the Run local pre job script option.
  3. Specify the following parameters in the dialog that opens:
  • Script path: Specify a local path to the script on the machine where the Director is installed. Script interpreter should be specified. 
    • Example (Windows): cmd.exe /c D:\script.bat
    • Example (Linux): bash /root/script.sh
  • Job behavior. Choose either of the following job behaviors in relation to script completion:
    • Wait for the script to finish: If this option is selected, VM backup will not be started until the script is completed.
    • Do not wait for the script to finish: If this option is selected, the product will run the script and will start backing up VMs at the same time.
  • Error handling. Choose either of the following job behaviors in relation to script failure:
    • Continue the job on script failure: If this option is selected, the job will perform VM backup even if the script has failed
    • Fail the job on script failure: If this option is selected and the script fails, the job will be failed and VM backup will not be performed.

Setting Up a Post Job Script

To run a script after the product has finished backing up all VMs, do the following:

  1. Place a script file on the machine where the Director is installed.
  2. Select the Run local post job script option.
  3. Specify the following parameters in the dialog that opens:
    • Script path: Specify a local path to the script on the machine where the Director is installed. Script interpreter should be specified. 
      • Example (Windows): cmd.exe /c D:\script.bat
      • Example (Linux): bash /root/script.sh
    • Job behavior. Choose either of the following job behaviors in relation to script completion:
      • Wait for the script to finish: If this option is selected, the job will be in the “running” state until the script is completed.
      • Do not wait for the script to finish: If this option is selected, the job will be completed even if the script execution is still in progress.
    • Error handling. Choose either of the following job behaviors in relation to script failure:
      • Continue the job on script failure: If this option is selected, script failure will not influence the status of the job.
  • Fail the job on script failure: If this option is selected and the script has failed, the job status will be set to “failed” even if VM backup has been successful.

Data Transfer

In the Data Transfer section of the Options page, you can choose a transport mode, a transporter to be used for reading data from source VMs, and configure bandwidth throttling.

Transport Mode

NAKIVO Backup & Replication provides the following transport modes for retrieving VM data:

  • Hot Add: NAKIVO Backup & Replication can read data directly from source VM disks, bypassing the network, which can significantly increase the job performance. This is achieved with the help of VMware's Hot Add technology, which enables attaching source VM disks to a different machine and reading data from the disk. In order for the Hot Add feature to work, the source Transporter (the one that will be reading data from the source VM) should run on a host that has access to the datastore(s) with your source VM's disks.

    If hot-add cannot be enabled for at least one disk of a source VM (even if the disk is deselected in the job), then Hot-add will be unavailable for all disks of the VM.

  • SAN: If your VMs are located on a Fiber Channel or an iSCSI Storage Area Network (SAN) device, NAKIVO Backup & Replication can use the direct SAN access for data retrieval. Using this storage access mode can significantly increase the speed of backup and replication while decreasing the load on your production network.
  • LAN: Data will be retrieved via LAN.

To select a transport mode, do the following:

  1. In the Data Transfer section, choose a transport mode for retrieving VM data:
    Choose a transport mode for retrieving VM data
    • Automatic selection: If this option is selected, NAKIVO Backup & Replication will automatically select the best transport mode available:
      • If the source Transporter is installed on a VM, NAKIVO Backup & Replication will try to use transport modes in the following order: Hot Add > SAN > LAN.
      • If the source Transporter is installed on a physical machine, NAKIVO Backup & Replication will try to use transport modes in the following order: SAN > LAN. Hot Add is not supported for physical machines.
    • SAN only: If this option is selected, NAKIVO Backup & Replication will only use direct SAN access to retrieve VM data. If direct SAN access to VM data is not available, the job will fail.
    • Hot-add only: If this option is selected, NAKIVO Backup & Replication will only use Hot-add to retrieve VM data. If direct Hot-add is not available, the job will fail.
    • LAN only: If this option is selected, NAKIVO Backup & Replication will only retrieve VM data via LAN.

Transporters

In NAKIVO Backup & Replication, Transporters perform all of the heavy liftings: read data from the source VM, compress the data, transfer the data over the network, perform data deduplication, and so on. In large and geographically distributed environments multiple Transporters can be deployed to distribute the data protection workload, optimize network traffic, and improve data transfer speeds. Thus, if more than one Transporter is deployed for NAKIVO Backup & Replication, it is important to determine which one should be used to read data from a particular source VM (the target Transporter is always the one that is assigned to the Backup Repository).

By default, the product automatically determines which Transporter should be used to read data from the source VM. However, you can manually specify which Transporters should be used for the job. Here’s how:

  1. In the Data Transfer section, choose one of the following options:
    VMware Backup Job - Transporters
    • Automatic selection: The product will automatically determine which Transporters are the closest to source hosts (the hosts that run selected VMs) and will use those Transporters to retrieve data from source VMs.
    • Manual - configured for all VMs: Select this option to manually specify a single Transporter that will be used to retrieve data from source VMs.
    • Manual - configured per host: Select this option to manually specify which Transporter should be used to retrieve data from each source host.

The target Transporter for the backup job will always be the Transporter assigned to the Backup Repository.

Bandwidth Throttling

Please follow the steps below to regulate the speed of data transfer over the network for your backup job:

  1. For the Bandwidth throttling option, choose Enabled.

    Note

    If bandwidth throttling is disabled for the current job, global bandwidth rules may still apply to your job. Refer to Bandwidth Throttling Settings for details.

  2. Click the Settings link that becomes available.
  3. The Job Bandwidth Rules dialog opens displaying you the list of available rules. You have the following options:
    • Create a new bandwidth rule for your backup job:
      1. Click the Create New Rule button.
      2. The New Bandwidth Rule dialog opens. Refer to the Bandwidth Throttling Settings topic for details on creating a bandwidth rule.
      3. Click Save.
    • Activate an existing bandwidth rule for your job. Select the checkbox to the left of the necessary bandwidth rule. To deactivate a bandwidth rule for your job, deselect the corresponding checkbox.
    • Edit a bandwidth rule. Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth Rule dialog that opens.
    • Disable a bandwidth rule. Click the Disable link. The bandwidth rule will be disabled for all jobs.
    • Remove a bandwidth rule. Click the Remove link and then click Delete to confirm your operation.

Completing the New Backup Job Wizard for VMware

Click Finish or Finish & Run to complete the job creation.

Note

If you click Finish & Run, you will have to define the scope of your job. Please refer to Running Jobs on Demand for details.

  • No labels