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

On the Options page of the wizard, you can set up backup job options. Proceed as described in the sections below:

Job Options

In the Job Options section, you can give a name to the backup job and enable/disable app-aware mode, change tracking, network acceleration, encryption, VM verification, and other.


Job Name

Enter a name for the backup job.

App-aware Mode

If the App-aware mode option is enabled, NAKIVO Backup & Replication will trigger the 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 also 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 dialog box that opens, select the checkboxes 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 to 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, due to wrong credentials).  
  • Enabled (proceed on error): In the dialog box that opens, select checkboxes 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 to the 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, due to wrong credentials).
  • Under Settings, you can select VMs for which the App-aware mode will be enabled. You need to specify credentials for them. In case Use agent for OS quiescing option is enabled, Windows VMs on Hyper-V 2012 and 2016 are selected by default.

Use Agent for OS Quiescing

If this option is enabled, NAKIVO Backup & Replication injects an agent into VMs to perform OS quiescing. 

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: When selected, NAKIVO Backup & Replication reads the entire contents of all VM disks in order to determine what data has changed since the last job run.
  • No change tracking (always full): When selected, NAKIVO Backup & Replication always performs a full VM backup of all source VMs. 

Network Acceleration

If the Network Acceleration option is enabled, NAKIVO Backup & Replication uses 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 are backing up over WAN without a VPN connection.

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

VM Verification

VM Verification allows you to check the integrity of the backup by starting it and interacting with it. For more details, refer to the VM Verification article. 

You can choose one of the following VM verification options: 

  • Disabled: VM Verification is disabled.
  • Screenshot verificationWhen enabled, all VM backups created by the job are verified: 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) and a screenshot of the recovered VM will be taken 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 displayed on the Jobs dashboard.
  • Boot verification: When enabled, all VM backups created by the job are verified as follows. After a VM backup is completed, NAKIVO Backup & Replication recovers the VM using Flash VM Boot, disables networking to prevent network connections, and verifies that system start is successful.

Important

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

After choosing Screenshot verification, 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 transporterChoose a proxy Transporter from the list of available Transporters.

  2. Set 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.

    3. Screenshot delay: The amount of time that the product should wait after the guest OS starts before taking a screenshot.

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

After selecting Boot verification, do the following in the dialog box that opens: 

  1. Provide a location of the VMs to be booted as described for the Screenshot verification option.

  2. Set 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.

     

Skip Swap Files and Partitions

With this option enabled, NAKIVO Backup & Replication automatically skips swap files and partitions during the backup process. 

Skip Unused Blocks

With this option enabled, NAKIVO Backup & Replication automatically skips unused disk blocks and blocks occupied by deleted files during processing of source objects running Windows OS. This feature allows for reducing backup storage space and object processing time.

Full Backup

If the Type of the Backup Repository that you selected on the Destination page 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 a 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. 

Note

On a full active backup, the entire source disks will be read even if Hyper-V RCT is selected.

Pre and Post Actions

NAKIVO Backup & Replication provides you with the ability to enable certain actions before a backup job begins and after it has completed. You can choose to send job run reports, truncate Exchange and SQL Server logs on specified VMs, and run local pre- and post- job scripts.


Email Notifications

NAKIVO Backup & Replication can send email notifications on job completion status to specified recipients. This feature complements global notifications and provides you with the ability to configure notifications on a 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.
  2. 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 Server Transaction Logs

Microsoft Exchange Server database transaction logs record all changes to a Microsoft 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 you with the option of deleting (or truncating) Microsoft Exchange Server logs on the source VMs after job completion.

The transaction logs are deleted after the job is completed so that the log files are available in the VM backup. Note that the product deletes only those transactions which have already been 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 box that opens, select the checkboxes next to the VMs running Microsoft Exchange and then select credentials next to each VM. These credentials will be used to log in to VMs you have selected.

Truncation of Microsoft SQL Server Transaction Logs

Microsoft SQL Server database transaction logs record all changes to a Microsoft 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 you with the option for deleting (or truncating) Microsoft SQL Server logs on the source VMs after job completion.

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

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

  1. In the Pre and Post Actions section, select the Truncate SQL logs option.

  2. In the dialog box that opens, select the checkboxes next to the VMs running Microsoft SQL Server and then select credentials next to each VM. These credentials will be used to log in to the VMs you have selected.

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 on which 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 box that opens:
  • Script path: Specify a local path to the script on the machine on which 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.

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 on which 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 box that opens:
    • Script path: Specify a local path to the script on the machine on which 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 one of the following job behaviors in relation to script completion:
      • Wait for the script to finish: When selected, the job will be in the "running" state until the script is completed.
      • Do not wait for the script to finish: When 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: When selected, script failure will not influence the status of the job.
      • Fail the job on script failure: When selected and the script has failed, the job status will be set to "failed" even if the VM backup has been successful.

Notes

  1. Pre- and post-job scripts can be executed only on the machine on which the Director is installed. 
  2. When Integration Services are used on Hyper-V 2016 and above, custom pre/post scripts are unavailable for Windows VMs.

Data Transfer

In the Data Transfer section of the Options page, you can specify a Transporter load and configure bandwidth throttling.


Transporter Load

You can limit the maximum number of Transporter tasks used by the job. By default, it is set to 3 concurrent tasks.

To change the default number of tasks, do the following:

  1. In the Data Transfer section, select the Limit transporter load to checkbox.

  2. Specify the number of concurrent tasks in the corresponding box.

Bandwidth Throttling

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 for details.

  2. Click the Settings link that becomes available.
  3. The Job Bandwidth Rules dialog box 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 box opens. Refer to the Bandwidth Throttling 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, clear the corresponding checkbox.
    • Edit a bandwidth rule. Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth Rule dialog box 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.

      x

Completing 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