EVault - EVault Cloud Disaster Recovery v6.7.7 - Release Notes

Follow

Evault Cloud Disaster Recovery
Version 6.7.7 Build [18585]
Release Notes, November 13th, 2015
____________________________________________________________________
=============================================================
Contents

1    Overview
1.1  Release History and Changes

2    Features

3    Fixes

4    Known Issues

5    Installation Notes
5.1  Installation Requirements
5.2  Procedure for Installing/Uninstalling
5.3  Configuration

6    Product Support
6.1  Technical Support
6.2  Product Updates
6.3  Documentation

____________________________________________________________________
=============================================================
1  OVERVIEW

This document contains release notes for the latest release of EVault Cloud Disaster Recovery v6.7.7 [18585]

This release serves as a patch release that includes all previous fixes and features contained in all previous EVault Cloud Disaster Recovery v6.7.[n] releases to include an issue caused by attempting to upgrade the 32-bit version of JAVA 8 to Update 60.

-------------------------------------------------------------
1.1  Release History and Changes

Previously released:

EVault Remote Disaster Recovery v6.7.0 - March 5th 2013

EVault Remote Disaster Recovery v6.5.3 - December 5th 2011

____________________________________________________________________
=============================================================
2  FEATURES

EVault Cloud Disaster Recovery v6.7.7 is a High Availability (HA) and Disaster Recovery (DR) solution focused on Continuous Availability. Using fully redundant servers, EVault Cloud Disaster Recovery provides availability by ensuring each server is capable of taking an active role or a passive role when servicing clients. The servers can switch roles when the active server suffers any type of disruption or when you choose to do so manually for any reason. EVault Cloud Disaster Recovery monitors all of the key components of the operations environment and can take action to correct a problem before users experience any type of outage.

New Features -- This release of EVault Cloud Disaster Recovery includes the following new features:

  • EVault Cloud Disaster Recovery System Integrity
    • Enhanced resistance to EVault Cloud Disaster Recovery registry preference configuration information loss.
  • EVault Cloud Disaster Recovery now provides a predictable installation using an environmental validation process as an integrated component of EVault Cloud Disaster Recovery Setup.
  • Passive server performance improvements in the presence of Overlapped IO and support for Sparse Files used by SQL Server.
  • EVault Cloud Disaster Recovery v6.7.7 supports SQL Server 2008 file streams used for remote BLOB storage (which can be enabled when using SharePoint 2010).
  • A new Channel Communications implementation offering a far more robust experience in WANs particularly those that experience frequent channel disconnects, high latency and / or packet loss and features:
    • Improved memory buffer management to reduce occurrences of communications related out-of-memory problems.
    • Session orientated delivery to handle frequent channel disconnects and prevent lost messages blocking Apply.
    • Checksums on communications messages to guard against corruption introduced by the network.
  • Supportability - To help diagnose the cause of Java Out of Memory errors, EVault Cloud Disaster Recovery now triggers an automatic memory dump when a Java Heap Space problem is detected. The memory dump is written to the EVault\Cloud Disaster Recovery\R2\Logs folder.
  • Support for Windows Server 2012 and Windows Server 2012 R2 backward compatibility:
    • All features included in EVault Remote Disaster Recovery v6.5.3 installed on Windows Server 2008 R2 and new features added for EVault Cloud Disaster Recovery v6.7.7, which do not require new Windows Server 2012 features, will operate on Windows Server 2012.
  • Backward compatibility for all existing supported Windows Server 2008 R2 server features for a customer upgrading to Windows Server 2012 from a server with EVault Remote Disaster Recovery v6.5.3 installed where the previous servers were Windows Server 2003, 2008 or 2008 R2.
  • EVault Cloud Disaster Recovery v6.7.7 will co-exist with Windows Server 2012 features.
  • Support for Windows 8 and Windows 10 Client.
  • The ability to install using a single NIC on each server.
  • User Interface improvements for Controlled Shutdown.
  • Improved Split-brain Avoidance by employing Network Isolation Protection (NIP).
  • Enhanced Fast Check support for:
    • File servers with 1 Million + files
    • Closed files for running applications
    • Fast Check use at first time start-up
    • Improved administrator control over options for synchronization time versus application start-up time.
    • Configurable FileInfoCache.
  • Edit All capabilities when configuring a recovery actions policy for all protected services.
  • Addition of unique Windows Event IDs.

Changed Features

  • Enhanced Controlled Shutdown:
    • Prevents application shutdown when the passive server is stopped.
    • Increases WAN timeout to 15 minutes.
    • Includes a default schedule outside of working hours.
    • Does not allow Administrator to prevent Controlled Shutdown on the active server.
  • The Configure Server wizard now provides a user selectable Network Topology control to enable/disable low bandwidth optimization (Ref-9993).
  • Improved Setup warning message text when WbAdmin is missing.
  • If Setup detects the kit contains blocked files because they originate from the Internet, the user is asked if they would like to unblock these files before continuing with the install of EVault Cloud Disaster Recovery (Ref-12704).
  • When installing EVault Cloud Disaster Recovery Client Tools on Windows XP, the user is prompted for the proper Service Pack level if not already installed (Ref-11144).

____________________________________________________________________
=============================================================
3  FIXES

The following issues have been fixed since the last release:

  • After an unplanned power failure, the Secondary/passive server fails shortly after restart (Ref-10695).
  • The Microsoft SQL ready for archive attribute on the Secondary/active server does not match the Primary/passive server (Ref-10834).
  • Immediately reinstalling of a plug-in may fail and display the message: Delete of target file path\to\plugin.dll failed (Ref-6132).
  • Providing incorrect credentials may cause the backup to fail and prevent you from going back to changed the credentials (Ref-7149).
  • Performance Counters missing on Secondary and Tertiary servers produce warnings and a degraded EVault Remote Disaster Recovery performance (Ref-7700).
  • If insufficient disk space for the backup exists, EVault Remote Disaster Recovery Setup cannot continue (Ref-8669).
  • If the backup target path last character is a backslash, the backup operation will fail (Ref-8877).
  • Multiple channels are not supported in WAN deployments, channel connection may not reconnect after a disconnect (Ref-9417).
  • Changing compression type using the Configure Server wizard in a LAN environment fails to make the change (Ref-9993).
  • A user that enables controlled shutdown on the passive server(s), stops the protected applications and then later reboots a passive server results in the following: Upon restart and reconnection to the replication chain, EVault Remote Disaster Recovery automatically restarts the protected applications (Ref-11086).
  • Log Collector doesn’t collect the data from all the machines if Server service is stopped on the remote servers (Ref-11100).
  • Changing the selected options on Fast Check may cause a Replication Error message to display on Windows Server 2003 (Ref-11431).
  • SQL Server file filter discovery will fail if the SqlServerConnections.xml is empty (Ref-10784).
  • When configuring failure actions for services, if a protected service also has dependent services, actions to take on failure should match those of the protected service (Ref-11437).
  • The Tertiary server does not join the replication chain after EVault Remote Disaster Recovery was restarted on Tertiary server because the server clocks are not in-sync with Primary and Secondary servers (Ref-11456).

____________________________________________________________________
=============================================================

4  KNOWN ISSUES

  • Performing a Service Pack upgrade does not upgrade the System Plug-in. The System Plug-in must be upgraded separately using the procedure provided in CDR-REFID-2330 (Ref-7123).
  • Installation of Client Tools using a file path longer than 100 characters may cause the installation of Client Tools to fail (Ref-13343).
  • When installing EVault Cloud Disaster Recovery on a non-English OS, although the installation path is displayed in English (for example, C:\Program Files\EVault), the application path may display in the non-English language (for example, C:\Programme\EVault) (Ref-10719).
  • The DNSUpdate task may fail when run under the System account on the Secondary/active server after switchover (Ref-10837).
    Workaround: Configure the DNSUpdate task to run under an account other than the System account with permissions to update DNS.
  • After multiple start/stop operations on applications and services, the following error is reported: Handling error: Responding to error: File/registry update data lost (Ref-10826)
  • When installing EVault Cloud Disaster Recovery using a single NIC on the Primary server, Secondary server, and Tertiary server (if installed), validate displays a warning message that two NICs are required.
    Workaround: Ignore warning message. Continue installation (Ref-14309).
  • When resizing the EVault Cloud Disaster Recovery Management Client window, some buttons may disappear as a result of the resizing (Ref-10720)
  • EVault Cloud Disaster Recovery Tasks and Events are not logged in vCenter 4.1 and earlier so will not appear in the vSphere Client (Ref-12831).
  • After restoring the backup file to the Secondary server with differing hotfixes, the server keeps rebooting (Ref-8519)
  • Restoring to a non-cloned Secondary or Tertiary server results in the following pop-up being displayed: 'This copy of Windows is not Genuine' (Ref-9444)
  • DNSUpdate is not querying for the correct zone name.
    Workaround: Manually configure the DNSUpdate task (Ref-8358)
  • After performing a switchover or failover, if network ping targets have not been configured, the message "-1 missed pings appear" is present (Ref-14262).
    Workaround: Navigate to Network > Configure Pings > Ping Routing and configure the ping targets.
  • After a switchover in a WAN deployment, the DNSUpdate task status is not updated on the Applications: Tasks page until after the applications are started (Ref-11015).
  • The EVault Cloud Disaster Recovery Packet filter does not work after a P2V installation if VM Tools were installed before running Setup.
    Workaround: Please uninstall VM Tools before attempting to install EVault Cloud Disaster Recovery in a Physical to Virtual environment. After successful installation of EVault Cloud Disaster Recovery, you can reinstall VMware Tools. (Ref-10993).
  • When attempting to run Log Collector on Windows Server 2003, .Net 2 must be installed. If .Net 2 is not installed, Log Collector will fail to complete.(Ref-14507).
  • When attempting to uninstall EVault CDR Exchange Plug-in an error stating that a specified file could not be found is displayed although the uninstall procedure completes successfully (Ref-12570).
  • The Log Collector should not put EVault Cloud Disaster Recovery in maintenance mode if Server Service is not protected (Ref-11058)
  • When attempting to collect logs via the EVault CDR Data Collector Service Configuration Tool, the dialog prompting you to put EVault Cloud Disaster Recovery into the Maintenance Mode is hidden behind the EVault CDR Data Collector Service Configuration Tool dialog and prevents you from collecting the logs (Ref-14294).
    Workaround: Either maximize the dialog icon from the Windows Toolbar or use Alt + Tab to bring the dialog forward so that a response can be given to the prompt.
  • When navigating to Data: Replication and clicking the Show Summary Of All Out Of Sync Files And Directories button to expand the Out-of-Sync Summary panel, the panel appears and then minimizes. (Ref-11436)
  • The System Plug-in fails to load on the passive-Tertiary server; the service starts but appears to be deadlocked (Ref-11454).
  • DNS Update does not execute when administrator access is denied to its temp directory (Ref-12239).
  • The command to make the Secondary server active by using the Make Active button may cause the NFServerR2 service to hang if a connection to the Secondary server is lost (Ref-13661).
  • When collecting logs, selecting all servers or local servers using the Log Collector, the following message appears: " Windows Features The following feature couldn't be installed: .NET Framework 3.5 (includes .NET 2.0 and 3.0) " (Ref-13900).
  • Quota settings configured for the Administrators group are not replicated to the passive server(s) (Ref-14009).
  • When performing installation logged into only the Primary server causes Validate installation on the Secondary server to fail (Ref-14016).
  • During upgrade from EVault Remote Disaster Recovery v6.5.3 to EVault Cloud Disaster Recovery v6.7.7, the EVault CDR Data Collector fails to upgrade (Ref-14208).
  • Performance counters missing on Secondary and Tertiary servers produce warnings and a degraded EVault Cloud Disaster Recovery performance. (Ref-7700).
    Workaround: Shutdown EVault Cloud Disaster Recovery on the Secondary / Tertiary server and run the following from a command prompt:
    lodctr /R in a cmd window
  • When performing an installation of EVault Cloud Disaster Recovery v6.7.7 with ghost NICs present, the server may get into a BSOD loop (Ref-14209).

____________________________________________________________________
=============================================================
5  INSTALLATION NOTES

5.1  Installation Requirements

Please refer to the Installation Guide for EVault Cloud Disaster Recovery v6.7

Documentation is available at: http://csp.evault.com
For more information, refer to the Documentation section of these release notes.

-------------------------------------------------------------

5.2  Procedure for Installing/Uninstalling

Please refer to the Installation Guide for EVault Cloud Disaster Recovery v6.7

Documentation is available at: http://csp.evault.com
For more information, refer to the Documentation section of these release notes.

-------------------------------------------------------------
5.3  Configuration

Please refer to the Administrator's Guide for EVault Cloud Disaster Recovery v6.7

Documentation is available at: http://csp.evault.com
For more information, refer to the Documentation section of these release notes.

____________________________________________________________________
=============================================================
6  PRODUCT SUPPORT

6.1  Technical Support

For support for this product, contact: http://csp.evault.com

-------------------------------------------------------------
6.2 Product Updates

Product updates are available through Technical Support.

6.3 Documentation

The documentation available for this product is as follows:

Installation Guides for EVault Cloud Disaster Recovery v6.7
Administrator's Guide for EVault Cloud Disaster Recovery v6.7
Getting Started With EVault CDR Data Collector Service v5.3.0

KBID-2893

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.