Introduction to Rapid Recovery 6.2.1 Release Notes

Rapid Recovery 6.2.1 Release Notes

Revision A, September 2018

These release notes provide information about the Rapid Recovery release, build 6.2.1.99 (for Linux) and build 6.2.1.100 (for Windows). This Revision A edition of these release notes includes updates related to resolved defect 107946.

Topics include:

• About this release
• Rapid Recovery release designations
• Support policy
• Enhancements
• Deprecated features
• Resolved issues
• Known issues
• System requirements
• Product licensing
• Getting started with Rapid Recovery
• Globalization
• About us

About this release

Rapid Recovery software delivers fast backups with verified recovery for your VMs and physical servers, on-premises or remote. Rapid Recovery is software built for IT professionals who need a powerful, affordable, and easy-to-use backup, replication, and recovery solution that provides protection for servers and business-critical applications like Microsoft SQL Server, Oracle Database 12c, Microsoft Exchange, and Microsoft SharePoint. Using Rapid Recovery, you can continuously back up and protect all your critical data and applications from a single web-based management console.

Rapid Recovery 6.2.1 is a maintenance release, with some enhancements (see Enhancements for details). Some features, previously integrated software tools, or platforms are no longer supported. For more information, see Deprecated features. This maintenance release primarily contains defect fixes. For more information on defect fixes and known issues, see Resolved issues and Known issues, respectively.

For information relevant for any other release, please see the edition of release notes specific to that release on the Quest technical documentation website.

Rapid Recovery release designations

 Rapid Recovery release designations consist of up to four parts. Each part consists of a set of numerals separated by a decimal point.

• Major releases are specified by the first numeral. These releases include dramatic changes to UI, the repository, or application behavior.
• Minor releases are specified by the numeral following the first decimal point. If this number is greater than 0, it is part of a minor release. Minor releases introduce new functionality that is smaller in scope than the types of changes included in major releases.
• Maintenance releases are specified by the numeral following the second decimal point. If this number is greater than 0, it is a maintenance release. Maintenance releases correct previously identified defects or behaviors. Maintenance releases may also reflect changes (additions and deprecations) in supported operating system or application platforms.
• Build numbers (typically between 3 and 5 digits) are specified by the fourth set of numerals. This part is used to differentiate versions of the software program generated during the development process.
  • For the   Agent software, build numbers may differ between Windows and Linux versions. If the first three parts of the release number are identical, interoperability between the Core and Agent with different build numbers is not affected.
  • Updated builds of the same software release may be made available on to the   within a release cycle. Therefore, if your Core is set to automatically update the Agent version on protected machines, you may see differences in build numbers for a single release. These differences will not negatively influence functionality.
  • Build numbers will differ between the Core and the Add-on for Kaseya component.
  • Difference in build numbers does not affect replication when the Core has the same or a more recent build installed than the replicated target machine.

Note that updates are sometimes made available after initial release that results in a different build number. Such is the case with this release.

For release 6.2.1.100, the first digit (6) is the major release. The second digit, if greater than 0, represents a minor release. The third digit, if greater than 0, indicates a maintenance release. The build number (100) is last and is generally only referenced in release notes. The build number for this release is different for the Linux Agent (99) and remaining components (build 100 for the Core, Windows Agent, and components such as the Local Mount Utility).

Support policy

The Rapid Recovery support policy is to provide technical support to customers with an active Support agreement for specific software versions under the following terms:

• Rapid Recovery software versions supported follow the N-2 policy.
  • N represents the major and minor release numbers (for example, 6.2, 6.1, 6.0, 5.4) of the most recent generally available software release. For more information about parsing a Rapid Recovery release number, see Rapid Recovery release designations.
  • N - 1 refers to the most recent prior release, considering major and minor versions only. For example, in release 6.2, N-1 refers to release 6.1.
  • N - 2 refers to the penultimate major/minor release. For example, in release 6.2, N-2 refers to release 6.0.
• For each release, some versions are eligible for full support; some for limited support; and for some versions, support is discontinued.
  • The current version (N) and the most recent maintenance release (N-1) are fully supported.
  • For N-2 (6.0), the latest maintenance release (6.0.2) is in limited support. Patches or fixes are not written for releases in limited support; however, once identified and confirmed, software defects can be expected to be corrected in the most recent version of the software.
  • Support for all other versions is discontinued.

    Quest Software Inc. strives to put resources behind the most recent product releases in order to continually improve and enhance the value of our products. Support for earlier maintenance releases is discontinued because viable, easy-to-upgrade alternatives are available. For example, users of release 6.2.0 can upgrade directly to release 6.2.1, which is fully supported. Users of release 6.1.0 can upgrade directly to release 6.1.3, which is fully supported. Users of 6.0.1 can upgrade to 6.0.2 (in limited support) or to 6.1.3 (in full support).

• Limited support can be offered to other versions by exception. As of the date of publication, no releases currently are supported by exception.