Release Notes

Known Issues
Quantum vmPRO Release Notes 16
ID Description Workaround/Resolution
4903 Hotadd disks remain attached to the vmPRO
appliance after the vCenter server goes
down.
The vmPRO applaince removes hotadd disks when
the connection is restored.
4401 If you use the vSphere Client to delete a VM
while it is being backed up by the vmPRO
appliance, the flat and ascii vmdk for the disk
that is open in the /export directory will not be
deleted on the datastore.
You must manually delete the files from the
datastore if a VM is deleted while it is being backed
up by vmPRO appliance.
4338 You cannot backup a vmPRO share with
Symantec BE2012i. A communication failure
occurs.
Several changes have been made to BE (2012) from
BE (2010 R3). To accommodate these changes, you
must make configuration changes to the BE release
(2012). See Communication Failure Between
Backup Exec 2012 and vmPRO to perform the
required configuration changes.
3828 Deleting a node from the master vmPRO
appliance while the master appliance is
powered off does not remove the node. In
addition, the master appliance is not updated.
You may receive a message indicating that
the removal was successful. This message
is incorrect.
To remove a node from the master vmPRO
appliance, the master appliance must be powered
on.
3809 If you remove or add a datacenter while
copying a CBT-enabled VM, an I/O error is
generated when the pancbt file is copied. The
backup fails at this I/O error.
Do not remove or add a datacenter during a backup.
3801 An error occurs when a pancbt file is copied
into the /import directory.
See Single Step Recovery.
3755 Free ESXi servers generate messages in the
log stating that the ESXi version does not
support the operation.
Quantum vmPRO only fully supports the paid
version of ESXi.
3751
3748
The vmPRO appliance does not support file-
level recovery for volumes spanned across
multiple disks.
You cannot currently perform file-level recovery for
dynamic volumes that span across multiple disks.