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, NAKIVO Backup & Replication will trigger Volume Shadow Copy Service (VSS) inside guest OS of source VMs prior to making a VM snapshot. The VSS service will instruct VSS-aware applications and databases to flush data from memory to disk and save data in a consistent state. Thus, the VM snapshot taken after triggering the VSS service will contain consistent data.

We recommend reading the support articles about the App-aware mode requirements:


Select one of the following options from the App-aware mode drop-down list: 

 

  • Disabled: VM backup will be performed without application awareness. 
  • Enabled (fail on error): In the pop-up dialog that appears, select check boxes next to the VMs for which you want to create application-aware backups, and then select credentials next to each VM. These credentials will be used to log in into VMs you have selected and trigger the VSS service. When this option is selected, NAKIVO Backup & Replication will fail the backup if the app-aware mode fails (for example, because of wrong credentials).  
  • Enabled (proceed on error): In the pop-up dialog that appears, select check boxes next to the VMs for which you want to create application-aware backups, and then select credentials next to each VM. These credentials will be used to log in into VMs you have selected and trigger the VSS service. When this option is selected, NAKIVO Backup & Replication will proceed with the backup even if the app-aware mode fails (for example, because of wrong credentials).

Under Settings, you can select VMs for which the App-aware mode will be enabled. You need to specify credentials for them.

Change Tracking

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

  • Use Hyper-V RCT: Native Hyper-V change tracking method. This option enables the fastest incremental backup. 
  • Use proprietary method: If this option is selected, NAKIVO Backup & Replication will read entire contents of all VM disks in order to determine what data has 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 screen verification is enabled, it will be performed for all backups after each job run. All backups of the job will be verified using the settings provided in the current job. This feature requires Hyper-V Integration Services in all VMs.

Screen verification operates in the following way:

  1. When a backup of a VM is completed, the VM will be test-recovered from the backup using Flash VM Boot and will be disconnected from networks.
  2. A screenshot of the recovered VM will be made once the VM OS has booted.
  3. Test-recovered VM will be discarded.
  4. VM screenshots will be included in the job report notifications given that this is configured in NAKIVO Backup & Replication Configuration.

Warning

Hyper-V Integration Services must be running on source VMs to enable screenshot verification for your backup job successfully.

After choosing Enabled for the Screenshot verification option, do the following in the dialog box that opens:

  1. Target Container: Choose a target container – cluster or host,– where test-recovered VMs will be run using Flash VM Boot.
  2. Verify not more than X VMs simultaneously: Specify the maximum number of VMs that can be started simultaneously. 
  3. 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.
  4. Screenshot delay: Specify 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, do the following:

  1. In the Pre and Post Actions section, select the Send job run reports to option and specify one or more email addresses in the text field. 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. In the Pre and Post Actions section, select the Truncate Exchange logs option:
  2. In the 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. In the Pre and Post Actions section, select the Truncate SQL logs option.

  2. In the SQL Server Log Truncation 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. In the Pre and Post Actions section, select the Run local pre job script option:
  3. Specify the following parameters in the dialog that appears:
  • 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 scrip 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 scrip 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. In the Pre and Post Actions section, 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 scrip 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 scrip 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.

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 Microsoft Hyper-V

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