6. Red Hat Enterprise Linux 5.6, 5.7 and 5.8 versions (32-bit and 64-bit) Additional Requirements:

Transcription

1 Quorum onq version 3.2SP3 Release Notes Mar 12, 2013 These release notes cover all changes since onq 3.0, including all service packs and hot fixes. About this Release OnQ 3.2SP3 is a Service Pack release that includes a critical upgrade of hosting environment from XenServer version to 6.0.2, mainly to align with new Sandy bridge chipset based Dell hardware and to utilize the improvements and optimizations that come with the upgrade. XenServer will be used only for manufacturing new OnQ systems and there is no support of in-place upgrade of already deployed systems that are based on XenServer Changes in this release do not add or affect any 3.2SP2 level of OnQ or Archive Vault functionality and OnQ 3.2SP2 systems are not required to be upgraded to 3.2SP3 level. In addition, the release includes enhancements in the number of volumes protected and also a more efficient data transfer between HA and DR appliances. A PXE boot environment along with a single image installer for onq appliance manufacturing is also made available. Additional Documentation The On-line Help for onq and Archive Vault are available to access from their respective portals. On-line documentation for onq is available at and the same for the AV is available at Highlights of 3.2SP3 include: 15 Volume support: This release includes enhancement to support protecting up to 15 volumes per Protected Node. With this enhancement number of volumes supported for protection has now increased from 9 to 15 per Protected Node, provided that none of the volumes exceed 2TB in size. If a Protected Node includes volumes that are larger than 2TB, the total number of volumes that can be protected for the Protected Node will be less than 15. With some user interaction the enhancement also automates the process of rebuilding the Recovery Node completely when such a need arise. Improved data transfer speed: This release also includes enhancements to increase the data transfer efficiency between HA and DR appliances, and HA and Quorum s Hybrid Cloud service. Highlights of 3.2SP2 include: Linux Protected Nodes: Backup support for Red Hat Enterprise Linux versions 5.6, 5.7 and 5.8 (both 32 and 64 bit) is now available in onq and Archive Vault solutions. The protected data can be retrieved via File Level Recovery. Improved Bare Metal Restore and Incremental Failback: This release enhances the workflow of Bare Metal Restore (BMR) and Incremental Failback substantially. The BMR / Incremental Failback workflow is wizard driven, and includes intelligence to determine the state of the Restore Target and appropriately choose Bare Metal Restore or Incremental Failback as the case may be. The enhancement provides a Restore wizard that walks the user through simple steps to start a failback process. User can now close the portal session or navigate away from the Restore page and the restore process will continue without interruption.

2 Highlights of 3.2SP1 include: Windows Share Restore: This release adds a Windows Share Restore feature which allows browsing and retrieving files directly off of the onq or Archive Vault repository by mapping a share on to a windows machine. This feature is in addition to existing File Level Restore method of restoring files. Auto download of onq upgrade Software: This release enhances onq and Archive Vault to check onq Central over the internet and retrieve any available upgrade packages directly to the onq. Once onq downloads the newer packages, it offers a new Install Updates button on the dashboard for installing the upgrade packages. Upgrading to 3.2SP1 by usual means prepares the onq for downloading future revisions of software automatically. Auto upgrade of Quorum Service on PNs: Starting with this release, when onq is upgraded and with newer node packages, the onq upgrades all Protected Nodes automatically upon restart of protection following the upgrade. onq Installer: onq 3.2SP1 introduces a new onq installer. This enables installation and configuration of an onq system after the appliance has been received by the customer. This will eliminate the need to pre-configure onq appliances before shipping to the customer s location. Highlights of 3.2 include: Archive Vault: This release provides an Archive Vault solution, which is an optional extension to the onq system for extended storage needs. This solution enables the means to store data and also history of configuration changes to comply with regulatory bodies. Enhanced self-test support: This release extends the self-test capability for PNs that are on a different subnet than that of the onq. Support for truncating Exchange logs: An option in portal allows the administrators to enable the truncation of exchange logs following a successful backup. Quick Link Navigation: Quick links are now enabled between HA, DR, DR Mirror and Archive Vaults and are available from main portal pages. Highlights of 3.0SP3 include: File Level Restore Activity Log: This release enhances logging by capturing File Level Restore (FLR) activities performed by all users. The activity log report captures and presents details that include loggedin User Name, Time, Client IP address, Files/Folders selected and retrieved, Start & End times of the restore itself, and Destination where the files/folders were restored to. The Status of the FLR (successful completion or reason for failure) is also presented in the report. The report, as with other log reports, can be either viewed within the Portal or downloaded in the form of a text file. onq kernel OS upgrade from 32bit to 64bit: This release improves resource utilization by upgrading the onq Manager OS kernel from a 32bit to 64bit architecture. In internal benchmarks and at deployed beta sites, the overall performance of the onq is observed to increase significantly, especially for PNs with a large number of files. Highlights of 3.0SP2 include: DR Mirroring: DR Mirroring enables you to replicate the data in the DR Repository to another DR Appliance, a DR Mirror. A DR Mirror is identical to the DR Appliance. The data moves from the HA Appliance to the DR Appliance, as usual. The only difference is that, with DR mirroring, the DR Appliance transfers/replicates the data on to the DR Mirror. Remote upgrade of Quorum service on nodes: This release provides the ability to update the Quorum Service for all Protected Nodes from the HA portal. With this feature in place, there is no need to access each Protected Node to update the Quorum Service.

3 Improved snapshot expiration policy: When repository disk space falls below critical levels, a new weighted algorithm is now used to remove oldest snapshots on a per Protected Node basis. Highlights of 3.0SP1 include: Automated Licensing: The onq Portal now provides an easier way to request, install and update Protected Node licenses. Alert Re-direction: onq can now be configured to send alerts through onq Central, which is a centralized support service for onq appliances. onq Central enhances our ability to support onq customers and eliminates difficulty in configuring onq alert reporting. Auto restart of RN build: onq now provides the ability to automatically restart an interrupted Recovery Node build. This is beneficial for Protected Nodes that have very large data sets and requirement multiple days to build the initial Recovery Node. IE 9 support: Internet Explorer 9 is now supported for use with onq Portal. How to Request Assistance or Report Problems Contact Customer Support at or support@quorum.net Terminology HA Appliance: the hardware on which the onq Manager runs on the local network. DR Appliance: the hardware on which the onq Manager runs on the remote network. DR Mirror Appliance: the hardware on which the onq Manager runs on a second remote network. Archive Vault: hosted on either HA and/or DR Appliance and connected to an external storage. Protected Node (PN): the physical or virtual server being protected by onq. Recovery Node (RN): the up-to-date, ready-to-run virtualized copy of the Protected Node that is ready-torun on the HA and DR Appliances. onq Manager: the onq software running on the HA and DR Appliances. onq Monitor Service: the Windows service running on the Protected Node. Also referred to as the Node Package. Portal: the web-based UI and server used to manage onq. The portal continues running even when the onq Manager (and protection) is stopped. Platform Requirements Protected Nodes: 1. Windows 2003 server R2 and above, 32 bit x86 2. Windows 2003 server R2 and above, 64 bit x86 3. Windows 2008 server, 32 bit x86 4. Windows 2008 & R2 server, 64 bit x86 5. VMWare ESX 4.0 & 5, Hyper-V 6.x and Xenserver 5.0 or above hypervisors are supported with guest operating systems listed above 6. Red Hat Enterprise Linux 5.6, 5.7 and 5.8 versions (32-bit and 64-bit) Additional Requirements: 7. Microsoft VSS must be enabled and have adequate snapshot space allocated 8. Maximum of 9 logical drives can be protected per PN Browsers: Mozilla Firefox 3.5 and above Internet Explorer 7, 8 and 9. IE required for PN installation ( Protect Me button) JRE (Java) 1.5 or above must be installed to use RN Consoles from UI Security and popup settings may need to be modified for proper RN console operation from UI Firewall/VPN Ports:

4 onq Appliances should NOT be open to any public access. The following ports must be accessible between the appliances (across VPN, firewalls, NAT, etc.): 22 TCP (may be remapped) 81 TCP (inter-appliance link monitoring, may be remapped) In addition, the following port(s) are required for administrative access to the portal on each appliance. Again, these should NOT be open to public access: 80 or 443 TCP (portal access) Generally, onq-to-pn communications are over a LAN that is not secured. In the event that there are any filtering devices between the PN and the onq appliance, the following ports need to be accessible: 5990 TCP (control) 5991 UDP (PN monitoring)

5 Enhancements 3.2SP3: 4219 Upgrade platform to Xenserver Automate install using PXE 4317 Winpy needs to load Xen tools 6.0 drivers during RN builds 4319 Winpy needs to inject Xen tools 6.0 drivers into RN images 4389 Upgrade onq VM drivers to XenServer Bug Fixes 3.2SP3: 3858 Sample pre_snap and post_snap scripts are missing 4731 failed FLR can stop subsequent FLR sessions from succeeding Enhancements 3.2SP2: 2201 Support Linux Protected Node 3748 Prevent onq/av disk from reaching a critical operation impacting level 3896 Provide backup progress bar to show PN Scan and Data transfer phases separately 3984 OnQ licenses to be retrieved via HTTP instead of SSH (443) from OnQ Central Quorum Rebranding changes to Portal 4019 Provide finer granularity for PN network BW utilization 4022 Varadmin session timeout set to Provide a progress bar indicator when creating the snapshot repo during manufacturing of onq appliance Proactive repository inspection and correction 4064 Prevent squirt-add of pre-added snapshots presented out of order 4076 Support specifying location & size of qfilter log files in squirtcopy.ini 4080 Ability to select a specific PN when requesting an event log in the portal Support failback to a PN from an RN in production without requiring a BMR 4139 Resolve symbolic links to SIS Common Store 4168 Add mult-threading to squirtcopy scan 4221 Provide means in portal to specify scan threads 4253 Support resumption of RN/BMR from an interruption. Enable r2v restart for SendError, ReplyError, and NetworkErr exceptions 4318 Redesign failback functionality in the UI to support new incremental failback method Create a process to manage seeding from a ReadyNAS unit onto a DR 4420 Increase maximum package upload size of portal 4434 Quark to include only Xen 5.5 and VMW 4 drivers Bug Fixes 3.2SP2: 2701 A SIS protected file when retrieved via FLR cannot be opened OpenVPN client rmps fail to install when going from 3.2 to Require additional confirmation before deleting production RN 4004 Repeating Object Count Inconsistency if PN system partition is d: 4015 Listing of directory contents while using WSR can take very long under certain conditions 4029 Win2k8R2 RN boots to a black screen 4034 VMWare Tools causes shutdown BSOD 4058 Protect Me fails on Re-install if already at license limit 4283 Qsync locks out squirt-add if an untrusted.db exists on DR 4376 File and Folders with $ in the name are not shown in WSR

6 Bug Fixes 3.2SP1-HF6: 4173 PN backup held back as a result of long retention expiration Bug Fixes 3.2SP1-HF5: 3844 BMR problem with EFI partitions 4333 QUARK GUI changes (for King Kullen) Bug Fixes 3.2SP1-HF4: 4259 Improve performance of confirm_chunk(schectman) Bug Fixes 3.2SP1-HF2: 4125 Squirt-export needs to support delta reversion 4149 Orderly system reboot result in squirtcopy abandoning qfilter trace logs and starting a fullscan Bug Fixes 3.2SP1-HF1: 4041 Improve efficiency of r2v handling of patch files in long jump delta manifests 4084 Remove unnecessary block_sums DB processing on DR side Enhancements 3.2SP1: 1794 Integrate download of upgrades into portal 3983 Create a 'Upgrade Log' in the portal where users can view upgrade history 2817 Full Rescan event logged into onq event log 3557 Auto upgrade Quorum Service on Protected Nodes 3676 Protection start to show STARTING on dashboard until onq is fully initialized 3831 Enhance AV to establish "initial job" if first scheduled job date elapsed without snapshot 3840 Automate software upgrade process 3853 Support remote onq appliance installation & configuration 3894 Provide Windows Share Restore feature to browse and retrieve files from backup repository 3906 Portal page to create & stop share 3950 Provide Windows Share Restore activity log 3924 QPKG installation should display all messages from the installation Post Install 3945 Restart R2V after the RN update/build is interrupted due to 'SelectTimeOut' error 3946 Increase hypervisor memory to alleviate xapi issues 4005 Commence transfer of any queued snapshots in todr when Protection starts Bug Fixes 3.2SP1: 3439 Perform cleanup tasks after onq appliance completely initializes upon protection start 3449 Check licensed node count before adding a new PN in the portal 3655 Modify hypervisor password on save in the portal 3518 Improve installation message consistency and feedback 3533 Large manifests cannot be parsed when performing incremental failback 3694 Control set 004 results in a blue screen when RN is booted 3762 Log expiration activity on Archive Vault 3828 Remove snapshots from aborted backups and retain only relevant logs 3834 Long sequences of expirations can preclude new snapshots from being added during the entire expiration 3838 Backup for a PN can fail forever if it goes offline during a backup 3846 Support Failback of a PN with EFI partition (inject BIOS boot files)

7 3852 Disable LSI RAID drivers from service.regm 3865 File Level Restore Does not Warn That Protection ON Required 3874 onq portal hanging longer at protection start 3879 RN self test fails if DR is running on different subnet 3882 Open port 5000 in Windows Firewall during MSI install 3886 Put the onq name on the Dashboard 3887 onq Central alert setting lost on IP config setting change 3944 Enable Full Rescan for all PNs when onq is upgraded to 3.2SP1 to fix OCI Enhancements 3.2: 2760 Archive Vault: Provide long term archiving capability 3051 Support self-test when PNs are on a different subnet 3209 Add firewall rules when Quorum onq service is updated/installed on the PN 3355 Provide option to truncate exchange logs 3401 Install Tail application while upgrading/installing Quorum onq service on the PN 3422 Quick navigation between HA, DR, DR Mirror and Archive Vault 3436 Squirt server to verify md5 checksums 3455 Discard X_VHDs left behind when RN updates fail Bug Fixes 3.2: 3385 Lamd should try to terminate application process after the timeout of max starting time 3453 Squirtcopy needs to check errors on various file writes 3460 Test for existence of key folders/files before accepting a snapshot 3461 Protect against RN build update failures due to SelectTimeout 3477 Better manage ACD logs on Protected Nodes 3482 Terminate stray cppserver on startup of a new cppserver instance 3514 Retain custom settings made in crontab for backup activity reports 3532 Support PNs with EFI partition 3534 Disable drivers that prevent RN from booting 3541 Backups from PNs that have names with sub-strings matching could fail while adding to repository License page in portal to display exact count of PNs allowed to protect 3709 Support BMR by overriding normal state match requirement Enhancements 3.0SP3: 3464 Upgrade onq VM kernel to 64 bit version 3357 Improve robustness of messaging between onq and the PN software elements 3476 Provide File-level recovery activity report Bug Fixes 3.0SP3: 3474 DR site may not fully initialize upon protection start in certain scenarios 3477 Better manage ACD logs on Protected Nodes 3478 Remove additional logging instrumentation that may cause memory initialization failures

8 3484 Remove name conflicts in configuration files because of substring matching 3491 FLR interface may not display directories that contents underneath 3505 Adding snapshots to repository may fail on DR under certain circumstances 3506 LAMD continues to restart due to errors while accessing winlsm.dll Enhancements 3.0SP2: 1884 Restart of interrupted backup under certain conditions 2330 Improved disk-based expiration policy 2341 Remote upgrade of Quorum Service on protected nodes 3306 Set default threads for squirtcopy to 4 for Protected Nodes newly configured. This will not modify the current configuration of nodes already protected Mirrored DR appliances 3347 Improved process for adding data to repository Bug Fixes 3.0SP2: 2573 Include drive/volume letter on Protected Node for which the vdisk is 90% full 2771 Improve accuracy of daily health report 3271 Improve portal pages loading 3296 Update OpenManage from 6.3 to 6.5 on Dell appliances to install several usability improvements provided by Dell 3322 Certain values entered for bandwidth can cause transfer to DR fail 3326 Delete database not required after migration to 3.0SP Support duplicate command line parameters for squirtcopy 3344 FLR to retrieve files from deep directory structure 3353 Upgrading onq systems from 3.0 to 3.0SP1 is very slow 3360 Revert squirtcopy to perform a normal backup when vss snapshot is deleted 3361 Failure to delete snapshot set should be non-fatal 3411 Make squirt-browse and squirt-repo-check process independent Enhancements 3.0SP1: 1774 Integrate license request and distribution into the Portal 2341 Show version of onq service installed on the Protected Node in the Portal 2782 Integrate onq Central with onq 2809 Restructure internal onq databases to increase backup efficiency Provide means to disable snapshot transfer from HA to DR through the Portal 3159 Make RN build re-startable 3185 Implement IE 9 support for onq Portal 3190 Allow number of threads to be configurable per PN in portal 3218 Support Favicon in the Portal 3220 Implement portal access to PN auto-upgrade 3312 Tighten onq VM firewall config Known Limitations and Issues Contact Customer Support if you encounter these issues and require assistance 1601 RNs for multi-tier applications must be started in proper sequence/combination (same as if booting PNs) 1708 Caps lock key does not work from Java console 1719 onq must be restarted after installing DCRM Node package 1720 Win2k3 below SP2 is not supported: squirtcopy might not stop due to MS Taskkill.exe bug 1756 Certain hardware-specific or dependent Windows Services must be disabled for proper RN functionality. Service disabling requires editing of the service.regm file on the PN

9 1769 Disks added to the PN after initial enrollment must be manually added (they are not automatically protected) 1783 The HA-DR link speed indicator may be inaccurate, especially on fast links 1802 Provide means of extending storage to external NAS/iSCSI in UI 1823 Only one Java console may be launched per RN 1935 onq service install on PN does not abort on errors and may leave partial installation 1968 RNs running on DR appliance are not backed up if HA is not running/connected. To enable backups, DR appliance role should be changed to HA 2101 Virtual PNs on Xenserver prior to version 5.0 cannot be protected by onq 2173 File Level Recovery needs to be restarted if interrupted 2186 FLR fails if there is not enough disk space on the target, but still indicates OK (check disk space before FLR) 2319 FLR status screen is only refreshed every 30 seconds 2371 Protect Me' onq installation requires Internet Explorer browser (only) 2484 RN creation may fail if many replication cycles are missed - reinitialize RN to correct 2543 After completely filling an RN disk, the RN may be required to be reinitialized after correcting the situation 2551 If an export error is encountered with protection ON, repeat the export (will run much faster) 2852 A maximum of 9 logical drives are supported per PN 2994 After rebooting the PN, if onq cannot communicate with the PN, protection may need to be restarted 4421 Manual configuration of boot manager may be required to boot a windows 2008 server after a Bare Metal Restore 4431 A widows 2003 server hosted on a VMWare (ESXi5) when protected, the RN may require its windows activated before it can be used Network adapter and Disk controllers may be required to be injected via Quark interface after performing an incremental failback to the original PN hardware 4435 Running OS adjustment process in the QUARK may be required when a VMWare windows 2003 server is restored on to a Xen host. Tasks Requiring onq CLI The following tasks may have manual steps that cannot be completed through the web UI and require the use of the onq CLI. Please contact your Reseller or QuorumLabs Support if you need to perform these tasks Deleting all backups of a PN after it is removed in the Protection Config may require semi-manual actions that require onq CLI 1756 Certain hardware-specific or dependent Windows Services must be disabled for proper RN functionality. Service disabling requires editing of the service.regm file using the onq CLI 1802 Use of external (iscsi, NFS) storage is semi-manual and requires onq CLI Third Party Licenses Operating systems and applications running on the Recovery Nodes (RNs) may have licensing terms or license management that require action on the users part to enable them on the RN. From their perspective, the RN is a different machine than the PN. These licenses are not managed by or under the control of QuorumLabs.

10 Upgrading OnQ Systems Procedure Operational OnQ systems that are built on Xen Server are not required to be upgraded to 3.2SP3 and not a supported path. All new OnQ appliances manufactured and shipped following this release would be built on Xen Server and OnQ version 3.2SP3.