NetVault Plug-in for VMware 13.2


	NOTE: CDP is only available with QoreStor version 7.1.2 or later. Only supported devices appear as available target storage. If you do not have a supported devices, then no devices appear as target options.

Performing continuous backups


	NOTE: Continuous backup job creation is not available from the Guided Configuration page.


	NOTE: Due to a limitation in the VMware Virtual Disk Development Kit (VDDK) 7.0, Plug‑in for VMware may not support browsing Resilient File System (ReFS) volumes on guest operating systems when the VMware proxy server uses Windows 2019.

To perform continuous backups

In the Navigation pane, click Create Continuous Backup Job to start the configuration wizard.

In Job Name, specify a name for the job.

Assign a descriptive name that lets you easily identify the job for monitoring its progress or restoring data. A job name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. There is no length restriction. However, a maximum of 40 characters is recommended on all platforms.

In the Selections list, select an existing Backup Selection Set, or complete the following steps to create a set:


	NOTE: Only CDP selection set appear as a selection sets.

To open the NetVault Selections page, click

Open the NetVault Client on which the plug-in is installed, and then open VMware Plugin.

Open the applicable VMware ESXi or VMware vCenter Server.

Depending on your VMware setup and inventory view type, open the applicable container nodes.


	NOTE: To switch between the two views (Hosts and Clusters and VMs and Templates), click the ESXi or vCenter Server, and select Toggle Inventory View from the context menu. This option is only available when server node is open.

Select the data that you want to back up:

•

Back up all virtual machines within a container: Select the container node. Data selection is possible at all levels, starting from the Datacenter node. For example, to back up all virtual machines hosted on an ESXi server, select the host node; in the VMs and Templates view, select the corresponding folder node.

•

Back up individual virtual machines: Open the applicable container nodes, for example, Datacenter, Cluster, and Resource Pool, and select the virtual machines that you want to back up. In the VMs and Templates view, open the folder node, and select the virtual machines that you want to back up.

You can also select the container node, and then clear the check marks for the virtual machines that you do not want to back up.

•

Back up individual virtual drives: Open the virtual machine node, and select the disks that you want to back up. The virtual drives are named “Hard Disk 1,” “Hard Disk 2,” … “Hard Disk n.” The plug-in only lists those disks for which it can generate a snapshot.

You can also select the container node — for example, Datacenter, Resource Pool, ESXi Server, or folder — or the individual virtual machines, and specify the disk type — system or data — in the Backup Options Set. For more information about this setting, see Virtual machine disk selection options.

The virtual machine configuration files, “.nvram”, and log files are always backed up whether you select the entire virtual machine or its individual disks.


	NOTE: For backup to be eligible for Instant Restore, select all disks.

Click Save, and in the Create New Set dialog box, type a unique name for the set.


	NOTE: If you enter the name of a non-CDP set, then an error appears stating that the name already exists. If the name is not visible as a CDP backup set, then it is present as a standard backup set.

A set name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Linux OS, the names can have a maximum of 200 characters. On Windows OS, there is no length restriction. However, a maximum of 40 characters is recommended on all platforms.

To close the dialog box, click Save.

In the Plugin Options list, select an existing Backup Options Set, or complete the following steps to create a set:


	IMPORTANT: On Windows, when you create a Backup Options Set for image‑level backups, you must use the default set “Default Backup Options — VMware Plugin — Windows” as the template. If you use any other set as the template, the backup may fail.

To open the VMware Plugin Backup Options page, click

Under Virtual machine disk selection options, select one of the following options.

The disk selection option is applied to all virtual machines that you have selected explicitly by selecting the corresponding nodes or implicitly by selecting the container node — for example, ESXi Server, Resource Pool, Datacenter, or folder. This option is not applied to virtual machines for which you have explicitly selected one or more virtual drives in the selections tree.


	CAUTION: When selecting disks, disable the Distributed Backup Job option.

Table 5. Virtual machine disk selection options
Option	Description
Back up all disks	To back up all available virtual drives for the selected virtual machines, use this option. NOTE: The plug-in only backs up those disks for which it can generate a snapshot. NOTE: This option is required for Instant Restore.
Exclude boot disk	To back up only the data disks and exclude the boot disks for the selected virtual machines, use this option. NOTE: For the backup to be eligible for Instant Restore, do not select this option.
Exclude data disks	To back up only the boot disk and exclude the data disks for the selected virtual machines, use this option. NOTE: To identify the boot disks, the plug-in only considers the active partitions on the MBR disk. Moreover, the plug-in only considers the first disk that meets the active boot partition criteria as the boot disk. The plug-in does not handle machines with multiple operating systems. NOTE: For the backup to be eligible for Instant Restore, do not select this option.

Under Other Options, configure the following settings:

Option

Description

Enable Active Block Mapping

ABM technology provides filters to remove unused blocks during backups. Removing the unused blocks reduces the backup size and the amount of data transferred over the network. You can use ABM with CBT to back up only active and changed blocks during Incremental and Differential Backups.

ABM is supported on the NTFS file system on basic disks and EXT file systems. ABM is not supported with XFS.

ABM is disabled by default. Selecting this check box enables ABM, which allows the plug-in to back up only those sections of the virtual drives that are active. ABM scans the disk and detects inactive blocks; these blocks are then omitted during backups.

NOTE: ABM also removes deleted data. When you restore a virtual machine that was backed up using ABM, you cannot perform undelete operations for that virtual machine. Without Active Block Mapping, CBT includes the deleted blocks.

If a backup job includes any unsupported disk types, this option is ignored for those disks.

Remove snapshots from previous backups

When you run a backup job, the plug-in creates a snapshot named “BKB_SNAP” on the virtual machine to back up the selected data. Regardless of whether the backup completes successfully or fails, the plug‑in removes the snapshot on job completion. The plug-in also removes the snapshot if the job is stopped or the parent or child processes are terminated for any reason. However, if a job exits abnormally, the cleanup process may fail to remove the snapshot. To address such cases, the plug‑in provides an option to delete the snapshot when you run the job next time.

You can select the Remove snapshots from previous backups check box to remove any existing snapshots when you run the current job. Only the snapshots named “BKB_SNAP” are removed from the virtual machines. This option does not remove any other snapshots that exist on the virtual machine.

Maximum Number of Parallel Streams

By default, the plug-in generates a single data stream for a backup job, and backs up the selected virtual machines in a sequential manner. To increase throughput and reduce overall backup time for image-level backups, you can configure the plug-in to perform parallel backups of multiple virtual machines.

This setting determines the maximum number of parallel data streams that can be generated for an image-level backup job. For example, if 10 virtual machines are included in a job, and you set this parameter to four, the plug-in tries to back up four virtual machines in parallel.

The actual number of parallel streams for a job depends on the following factors:

•

The number of backup devices or streams available to the backup job. For example, if you set this parameter to 4 and only two tape drives are available or a NetVault SmartDisk can only support two concurrent streams, the plug-in only processes two virtual machines concurrently.

•

The number of virtual machines included in the job. For example, if you set this parameter to 4, and the number of virtual machines selected for backup is 3, the plug-in creates only three data streams.

For parallel backups, the plug-in generates a parent process that coordinates the overall backup and individual child processes that perform the actual task of backing up the virtual machines. The maximum child processes that can be generated for a backup job is equal to the Maximum Number of Parallel Streams configured for the job. The parent and the child processes are all created on the NetVault Client on which the plug-in is running.

When a child process acquires a backup device and creates a backup stream, it is assigned a task to back up a virtual machine. After the task completes, the process is assigned the next task if there are any more virtual machines to be backed up. Each task is assigned a Task ID. A snapshot is generated only when a virtual machine is assigned to a child process.

When configuring Maximum Number of Parallel Streams, consider the following:

•

Verify that the value configured for this option does not exceed the number of backup devices or streams accessible to a job.

If the available devices are insufficient, more than one child process may try to access and write to the same device, causing significant increase in the overall backup time.

•

The load of running multiple processes on a NetVault Client can have a negative impact on performance.

•

The load of backing up multiple virtual machines from the same datastore can increase the I/O activity on the datastore.

•

The load of backing up multiple virtual machines that are managed by the same ESXi Server can increase the load on the host if you are using the LAN Transport mode (NBD/NBDSSL) for data transfer.

NOTE: Only a single child process is used to back up the multiple disks of a virtual machine even if more data streams are available. The child process creates a snapshot of the whole virtual machine and retains the snapshot until the job completes regardless of whether the whole virtual machine or its individual disks are backed up.

Automatic diagnose virtual machine on backup failure

To run predefined tests that can identify the cause of a virtual machine backup failure, select this check box.

For more information about the Diagnose method, see Diagnosing virtual machine issues.

You can access the Diagnostic Results dialog box from the View Logs page. The details are stored as log context objects.

Disable distribution of backup job to other VMware Backup Proxy

If you configured your environment to use the Distributed Jobs feature, select this check box to turn off the feature for a specific job. This option is disabled by default.

Enable Job Level Transport Mode

If you are using the Distributed Jobs feature and you want to set the transport mode manually at the job level, select this option, and then select the applicable Primary Transport Mode and Fallback Transport Mode.

Click Save, and in the Create New Set dialog box, type a name for the set.

To close the dialog box, click Save.

To select Schedule options, click

and complete the following steps:

In the Schedule window, set the number of hours you want to have between each incremental snapshot. The minimum value is 1 hour.

Set the number of days you want to have between each synthetic full backup.

Click Save.

To select Target Storage options, click

and complete the following steps:


	NOTE: CDP is only available with QoreStor version 7.1.2 or later. Only supported devices appear as available target storage. If you do not have a supported devices, then no devices appear as target options.

In the Backup Target window, select an available QoreStor device.

Click Save.

To select the Advanced Options, click

and complete the following steps:

Select the number of synthetic full backups to keep before deleting the previous synthetic full backups.

Optionally, select Make Backup immutable.


	NOTE: The length of time that you select in Step a also determines the length of time for which a backup is immutable.

Click Save.

For more information about Advanced Options sets, see the Quest NetVault Administrator’s Guide.

On the Create Backup Job page, to submit the job for scheduling, click Save & Submit.

To save the job definition without scheduling it, click Save. You can view, edit, or run this job from the Manage Job Definitions page. This job is not displayed on the Job Status page until you submit it.

You can monitor the job progress from the Job Status page and view the logs from the View Logs page.


	CAUTION: Do not use the Run Now option on the CDP backup job. Doing so would result in inconsistencies in the synthetic full schedule and the instance number count.

For more information about Job Status, View Logs, and Manage Job Definitions, see the Quest NetVault Administrator’s Guide.

Continuous data protection and Data Copy

The ability to make a copy of a continuous data protection (CDP) backup is available either via phase 2 secondary copy or with the built-in Plug-in for Data Copy.

Ensure that the schedule for Data Copy between Synthetic Full backups does not overlap. Allow enough time for the next Synthetic Full backup to compete before the Data Copy job begins.

Table 6. Replicating CDP backups using Data Copy
Data Copy Method	Schedule	Target Storage	Copy Type	Amount of time for copy
Secondary copy	Any	QoreStor 7.1.2 or later	Replication of differences	Time to copy only the changes in the backup, Very fast, preferred
Backup	Any incremental backup or synthetic full or full backup	QoreStor 7.1.2 or later	Replication	Time to copy only the changes in the backup
	Once on demand for synthetic full and incremental backups	QoreStor 7.1.2 or later	Replication of differences	Time to copy only the changes in the backup
	Once on demand for synthetic full backups	Other target storage	Full copy of backup	Time to copy all of the data in the backup
Backup Set	Between two synthetic full backups with no overlap	QoreStor 7.1.2 or later	Replication of differences	Time to copy only the changes in the backup
Backup Set	Between two synthetic full backups with no overlap	Other target storage	Full copy of backup	Time to copy all of the data in the backup