Quantum vmPRO Release Notes Release 3.3 Build Number 7187 Supported Product Quantum vmPRO Date May 2015 Contents Purpose of This Release 2 Quantum vmPRO Requirements 3 Resolved Issues 5 Known Issues 9 © 2015 Quantum Corporation. All rights reserved.
Purpose of This Release Purpose of This Release vmPRO 3.3 includes the following new features and enhancements: l Support for VMware's Virtual SAN (VSAN) software-defined storage strategy and latest release of the vSphere 6.0 hypervisor. l Embedded help system. l Bug fixes to enhance stability, functionality, and security. VSAN Support VMware's VSAN is a cluster-wide resource that exists as datastores on a cluster of ESX servers.
Quantum vmPRO Requirements Security Updates Like many other companies, Quantum has been effected by POODLE, GHOST, and Samba Vulnerability bugs as follows: POODLE Vulnerability The POODLE vulnerability bug is a moderate vulnerability for applications and systems using Secure Socket Layer (SSL) 3.0 with cipher-block chaining (CBC) mode ciphers.This vulnerability can expose sensitive data transmitted during an encrypted web session, such as passwords, cookies, or other authentication tokens.
Quantum vmPRO Requirements Component Requirements Virtual Server At least one ESX/ESXi server, versions 4.0 update 2 or later, to host the vmPRO appliance and virtual machines (VMs) being backed up. Keep the following items in mind when configuring your ESX/ESXi servers: l l l Hardware (Host Server) Network (Host Server) In environments with numerous ESX/ ESXi servers hosting multiple VMs, we recommend deploying a vmPRO appliance on each ESX/ESXi server.
Resolved Issues Resolved Issues The following table lists issues that have been resolved for the Quantum vmPRO 3.3 release. ID Description Resolution 6421 SmartMotion™ backups stall and fail when the recovery_fs iSCSI write area becomes inaccessible. This write area is used for all device mappers related to recovery_fs, recovery_fs_files, and files_fs. vmPRO 3.3 detects whether the recovery_fs iSCSI write area becomes inaccessible.
Resolved Issues ID Description Resolution 6358 Full backups occur before the normal Changed Block Tracking (CBT) reset cycle after a SmartMotion retention schedule policy partially deletes a full backup. In vmPRO 3.3, full backups are no longer partially deleted if differential backups still need to occur during the CBT cycle. In addition, full backups, partial backups, and associated database entries are deleted at same time by the same retention schedule policy.
Resolved Issues ID Description Resolution 6339 Firefox browser version 33.1 does not connect to the vmPRO appliance's GUI due to an issue with verifying certificates against stored authorities. Remove stored authorities for Pancetera Software Customer certificates: a. From the Firefox menu, select Options to display the Options window. b. Click Advanced to display the Advanced page. c. Click the Certificates tab, and then click View Certificates to display the Certificate Manager window. d.
Resolved Issues ID Description Resolution 6327 The following SmartMotion error can occur if one ESX host within a group of ESX hosts being managed by a single vCenter server is not in a connected state: vmPRO 3.3 will not include VMs in the /export directory for backup until the initial full discovery of a hypervisor is complete. This sequence allows the vmPRO to recognize and add the VMs on healthy ESX hosts into /export. VM was not found in /export.
Known Issues ID Description Resolution 6172 When configuring search domains on the vSphere Client console's Network Configuration screen, you can only populate the first 3 domain fields for the Change Search Domains setting. In vmPRO 3.3, you can populate all 6 domain fields for the Change Search Domains setting. 5751 The following error can occur on the vmPRO Recover Virtual Machines Wizard when recovering VMs: vmPRO 3.3 assigns the correct name to the datacenter during a VM recovery.
Known Issues ID Description Workaround/Resolution 6123 SmartMotion backups can fail if you use a DXi appliance as your NAS target with an NFS share. Under heavy traffic loads, the DXi appliance can return ENOENT (no such file or directory) errors, potentially causing SmartMotion backups to fail. Upgrading to DXi firmware version 2.3.0.3 or newer can potentially reduce the occurrence of this issue. SmartMotion backups can fail when using with the Scalar LTFS appliance as a NAS target NFS share.
Known Issues ID Description Workaround/Resolution 4327 SmartMotion backups can fail and issue an error referencing -s001.vmdk. The vmPRO appliance is trying to back up a twoGbMaxExtentSparse disk, which was migrated from a VMware Workstation to an ESX server. Neither ESX servers nor the vmPRO appliance support this type of older virtual disk format. 3798 Time for SmartMotion is not correct when running from the panshell. When configuring your SmartMotion schedule, use the vmPRO GUI.
Known Issues ID Description Workaround/Resolution 1644 Quantum vmPRO does not currently support the following: the vmPRO appliance's GUI now displays Snapshots not supported by VMs configured with SCSI bus sharing for non-supported VMs. l l N/A VMs with missing BIOS UUIDs1. The vmPRO appliance cannot export such VMs. VMs configured with SCSI bus sharing cannot be snapshotted. The vmPRO appliance detects and excludes such VMs from the /export directory.
Known Issues ID Description Workaround/Resolution 5877 The following error message has been seen with various failed backups: No such file or According to the CIFS protocol, the following characters are not allowed in file names: directory on special characters “\”, “/”, “[“, “]”, “:”, “+”, “|”, “<“, “>”, “=”, “ ;”, “?”, “,”, “*” There are restrictions regarding the characters allowed in a file name when using a NAS target using a CIFS share.
Known Issues ID Description Workaround/Resolution 3283 Files that contain an illegal multi-byte sequence in the file name are not listed in the /files and /recover/files directories. If a file name that contains an illegal multi-byte sequence is encountered when listing a directory, the directory listing will appear empty.
Known Issues ID Description Workaround/Resolution 6274 Restarting the VMware Tools service on a guest VM during an Exchange Recovery may cause the recovery to stall. If the Exchange Recovery stalls VMware Tools services restart automatically when the VMware Tool application is updated or re-installed, or when a user manually restarts the VMware Tools services. a. Cancel the Exchange Recovery. b. Manually clean up the Exchange server. c. Check that the VMware Tools service is running on the guest VM.
Known Issues 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.
Known Issues ID Description Workaround/Resolution 3709 Enabling CBT requires the creation and removal of a snapshot if CBT is not already enabled on the hypervisor. We recommend enabling CBT only for VMs that are intended for backup. When you enable CBT for a VM and CBT is disabled on the hypervisor, a script that enables CBT for that VM is executed regardless of whether or not that VM is export-enabled.
Known Issues ID Description Workaround/Resolution 3194 NetBackup ignores CBT changes on CBTenabled VMs. During the backup of a CBTenabled VM, the vmPRO appliance only backs up the default 4 KB file, and ignores the actual changes to the pancbt.vmdk file. Resolve the issue a. Enable BUSY_FILE_ACTION on the NetBackup client, and set the repeat (retry) count to 81. b. Create a User Backup schedule with active execution window in the backup policy for the NetBackup client. c.
Known Issues ID Description Workaround/Resolution 2239 When copying a VM from a CIFS-mounted vmPRO directory, or when copying a VMDK into the /import directory mounted over a CIFS share, the copy operation may time out with the following messages: To resolve this issue, you must set the Windows LANManager Workstation setting SessTimeout to a higher number of seconds. 2460 2473 See the online support article: Copying a VM Times Out.
Known Issues ID Description Workaround/Resolution Unix/Linux file systems may contain symbolic links that are absolute paths to directories outside of the mounted volume directory structure. These absolute symbolic links are not backed up properly when accessing the file-level view over CIFS shares. Attempts to access these absolute symbolic links through the file-level view exported by the vmPRO appliance (over CIFS shares) result in a permission denied error.
