Repository upgrade advisory
Upgrading the Core software to release 6.3 from any earlier version (for example, Rapid Recovery 6.2.x, 6.1.x, 6.0x, or AppAssure 5.x) changes the structure of your DVM repository. The updates let you use new features in the latest release, such as application support for Oracle Database 12c, agentless protection, and so on.
After you change the structure of your DVM repository through an upgrade, you cannot downgrade the version of Core. Should you determine in the future that you want to use an earlier version of Core after upgrade to this release, you will need to archive the data in your repository. You could then uninstall the new version, re-install the older version, and then re-import the information manually from the archive, which can be a substantial effort.
Automatic Update advisory
If upgrading from Rapid Recovery release 6.2 or later, you can use the Automatic Update feature to upgrade to this release, if it is enabled in your Core. Use of this feature requires you to consent to Quest using a limited amount of your personal data. For more details, see the topic "How Rapid Recovery uses personal information" in the Rapid Recovery 6.3 User Guide.
Due to parameters included as part of GDPR compliance in Rapid Recovery release 6.2 and later, customers using Rapid Recovery versions prior to 6.2 will not be able to use the Automatic Update feature to upgrade. You must manually upgrade the software one time instead. Once you have upgraded to Rapid Recovery release 6.2 or later and consented to the use of personal data, you can resume using the Automatic Upgrade feature.
Replication conflicts with agentlessly protected virtual machines on SMB shares
In specific cases, users cannot set up replication between 6.1.3 and 6.3 Cores. Users attempting to establish replication from a source Core running Rapid Recovery Core 6.1.3 to a target Core running version 6.2.0 or higher will fail if the target Core has recovery points from an agentlessly protected machine that had shared VHDX disks placed on a network shared volume using the Server Message Block (SMB) protocol.
If using such a configuration, all attempts to set up replication will fail (not only protection of agentless VMs). At this time, Quest does not expect to backport a fix. To resolve, upgrade your source Core to release 6.2.0 or later.
Content differences between context-sensitive help and technical documentation
Rapid Recovery Core includes in-product context-sensitive help. Help topics are derived from the Rapid Recovery 6.3 User Guide. To view help topics in a web browser, from the Rapid Recovery Core Console, click ![[Help menu]](/ko-kr/technical-documents/image/a8db0fac-3d25-458e-9719-4d4ab8905aa0)
![[Help]](/ko-kr/technical-documents/image/653081a1-f651-4a9e-bc1c-cd3f7c095e13)
Due to publication schedules, sometimes there are content differences between content in the in-product help and in the User Guide, with the latter document being the most recent. In such cases, these differences are typically documented in the Documentation section of the Known issues topic.
Since Rapid Recovery release 6.2, the "REST APIs" appendix appears only in the HTML and PDF versions of the User Guide. This topic, which describes how to download and work with Rapid Recovery REST APIs, does not appear in context-sensitive help. Likewise, as in previous releases, the help topic "Third-party contributions" appears only in context-sensitive help, or from the ![[About]](/ko-kr/technical-documents/image/e85bb903-ebd8-4cc8-997a-27d950e5e4cb)