Quantum vmPRO 4000 Release Notes

Contents
Quantum vmPRO Release Notes
Release 3.3
Build Number 7187
Supported Product Quantum vmPRO
Date May 2015
Purpose of This Release 2
Quantum vmPRO Requirements 3
Resolved Issues 5
Known Issues 9
6-67534-13 Rev B, May 2015
*6-67534-13*

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. The vmPRO appliance manages VSAN through a vCenter server, which in turn is managing the ESX servers housing the VSAN datastores. vmPRO 3.3 supports both backing up virtual machines (VMs) from VSAN datastores to Network Attached Storage (NAS) targets, as well as recovering VMs from the NAS targets back to VSAN datastores. In addition, vmPRO 3.3 supports backing up VMs from one type of datastore (VSAN or non-VSAN), and then recovering VMs to either a VSAN or non-VSAN datastore.
Example
A VM backed up from a VSAN datastore can be recovered to a non-VSAN datastore.
vSphere 6
vmPRO 3.3 supports the latest release of VMware's vSphere 6.0, which includes increased security, scalability, and performance.
Embedded Help System
vmPRO 3.3 offers a new help system embedded in the appliance's GUI. Users can access topics to guide them through all menus, screens, and processes of the vmPRO appliance. Because this help system is embedded in the appliance's GUI, users do not need to be connected to the Internet to access the help topics. They can simply click on the Help > Help Contents menu to open the new help system.
Features of the new help system include the following:
l All content from the vmPRO3.3User'sGuide and UpgradeGuide in an easy-to-navigate format.
l Search functionality to locate specific topics addressing user needs.
l Interactive features giving the user control over the content to display.
Quantum vmPRO Release Notes 2

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. Attackers can use these tokens to impersonate an authorized user to then gain complete access to a website. For more information, see https://www.us-cert.gov/ncas/alerts/TA14-290A.
Although vmPRO versions 3.2.1 and earlier include versions of SSL that are vulnerable to POODLE, attackers would need privileged network access prior to exposing this vulnerability. For enhanced security, however, vmPRO 3.3 includes the updated OpenSSL version to resolve the POODLE vulnerability bug.
GHOST Vulnerability
The GHOST bug is a vulnerability in the Linux GNU C (glibc) library prior to version 2.18. This vulnerability allows remote attackers to take control of affected systems by executing remote code calls to the gethostbyname function. For more information, see https://www.us-cert.gov/ncas/current-
activity/2015/01/27/Linux-Ghost-Remote-Code-Execution-Vulnerability.
vmPRO 3.2.1 and earlier include versions of the Linux glibc library that are vulnerable to GHOST. For enhanced security, vmPRO 3.3 includes the updated RPM to resolve the glibc vulnerability.
Samba Vulnerability
The Samba daemon (smbd) has an uninitialized pointer that remote attackers can use to send specially crafted Netlogon packets. These packets allow attackers to execute arbitrary code under the guise of the user running smbd (by default, the root user). For more information, see https://www.us-
cert.gov/ncas/current-activity/2015/02/24/Samba-Remote-Code-Execution-Vulnerability.
vmPRO 3.2.1 and earlier include versions of Samba that are vulnerable to this remote code execution. For enhanced security, vmPRO 3.3 includes the updated RPMs to resolve this vulnerability.
Quantum vmPRO Requirements
Before installing your vmPRO appliance, make sure that your environment meets or exceeds the following system requirements.
Quantum vmPRO Release Notes 3
Quantum vmPRO Requirements
Component Requirements
Virtual Server
Hardware (Host Server)
Network (Host 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 In environments with numerous ESX/ ESXi servers hosting multiple VMs, we recommend
deploying a vmPRO appliance on each ESX/ESXi server.
l We recommend using paid versions of VMware ESX or ESXi servers. Free versions have
various API limitations that keep vmPRO from functioning as designed.
l You can manage your ESX/ESXi server(s) directly or through VMware vCenter. If you have
the option of using a vCenter server, we recommend that you do so.
l 12 GB of free disk space
l 1280 MB of free RAM
l Gigabit NIC port for data movement on the vmPRO host server
We recommend that you perform the following tasks in configuring your network:
l Configure a static IP address.
l Configure your network on the VLAN that has access to the vCenter or ESX/ ESXi servers to
be protected. If you use third-party backup software, its client that connects to the vmPRO network must be able to access the VLAN, as well.
Web Browser (Client)
Flash Player plug-in (Client)
Microsoft Exchange Servers
Any modern Web browser that supports Adobe Flash Player plug-in 9.X or higher.
Adobe Flash Player plug-in 9.X or higher.
One of the following versions of Microsoft Exchange for mailbox recovery:
l Windows 2008R2/Exchange 2010
l Windows 2008R2/Exchange 2013
l Windows 2012R2/Exchange 2013
For systems that use Microsoft Exchange servers running Windows 2008R2 and Exchange 2010, the Window Management Framework 3.0 must be installed.
Quantum vmPRO Release Notes 4

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.
6398 The Samba daemon (smbd) has an uninitialized
pointer that remote attackers can use to send specially crafted Netlogon packets. These packets allow attackers to execute arbitrary code under the guise of the user running smbd (by default, the root user).
6382 GHOST is a vulnerability in the Linux GNU C
(glibc) library prior to version 2.18. This vulnerability allows remote attackers to take control of affected systems by executing remote code calls to the gethostbyname function.
6368
A datastore_fs core dump in jdr_ds_
config() is occurring.
vmPRO 3.3 detects whether the recovery_fs iSCSI write area becomes inaccessible. If this write area issue occurs, all recovery operations are suspended, and the vmPRO appliance alerts uses that a problem exists with the external storage device. Users can then resolve the storage issue to continue with the backup and recovery operations.
vmPRO 3.3 includes the updated RPMs to resolve the Samba vulnerability.
vmPRO 3.3 includes the updated RPM to resolve the glibc vulnerability.
In vmPRO 3.3, the issue has been resolved.
datastore_fs
core dump
6360 During a configuration file import, which is
completed during the migration of an existing vmPRO appliance's records and settings to a new appliance, the database records of all backup history is lost.
Quantum vmPRO Release Notes 5
vmPRO 3.3 retains the database records of all backup history during a configuration file import.
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.
During differential backups, CBT needs to access data from the full backup disk's flat file. For this reason, the retention schedule policy partially deletes the full backup by leaving the flat file intact, but it also removes the database entry. The deletion of the database entry prevents CBT from detecting the flat file. Without being able to detect the flat file, CBT cannot perform a partial backup, and so it performs a full backup instead.
6352 The iSCSI target daemon (tgtd) can crash during
a forced delete of an iSCSI target file with a pending data transfer.
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.
In vmPRO 3.3, if the iSCSI tgtd crashes during a forced delete of an iSCSI target, the vmPRO appliance automatically reboots to reset the tgtd.
When a vmPRO appliance is rebooted, its connection to the iSCSI Initiator is lost, along with all previously written data. In addition, previously exported VMDKs are no longer available. You must perform a new iSCSI export and recovery.
6351 During a mailbox recovery, the
vmPRO appliance can fail to disconnect the recovery database if a user selects Cancel on the Exhange Recovery Wizard's Select mailbox to recover page.
A Failed to cleanup recovery database error displays from the Exchange Recovery Wizard.
6342 The Virtual Disk Development Kit (VDDK) used
with vmPRO 3.2.1 and older does not fully address recent OpenSSL security vulnerabilities.
vmPRO 3.3 includes updated logic to successfully disconnect the recovery database under these circumstances.
vmPRO 3.3 uses VDDK 5.5.3, which contains the updated OpenSSL library.. This updated version addresses recent OpenSSL security vulnerabilities.
Quantum vmPRO Release Notes 6
Loading...
+ 14 hidden pages