Chat now with support
Chat with Support

Rapid Recovery 6.2.1 - Release Notes

Exchange Server 2007

Rapid Recovery support for Exchange Server 2007 is deprecated

In April of 2017, Microsoft Exchange Server 2007 reached end of life. Microsoft no longer supports that version of Exchange Server.

Accordingly, Rapid Recovery support of Exchange 2007 is deprecated. In Rapid Recovery release 6.2.1, only limited support is provided for Exchange 2007. If customers encounter issues, Quest Data Protection Support will apply their best effort to provide known work-arounds or fixes. However, no coding effort will be applied to issues discovered in Exchange 2007 in relation to our software.

Quest recommends migrating to newer, supported versions of Exchange if you want to continue protecting your data using Rapid Recovery.

Rapid Recovery support for SQL Server 2005 is discontinued

In April of 2016, Microsoft SQL Server 2005 reached end of life. Microsoft no longer supports that version of Exchange Server.

Accordingly, customers are advised that Rapid Recovery no longer supports SQL Server 2005. Any remaining references to support of that version are expected to be removed in the next iteration of our documentation. See Documentation known issues for details.

Resolved issues

The following is a list of issues addressed in this release.

Table 1: Core and Windows resolved issues

Resolved Issue Description Issue ID Functional Area
After upgrade from Rapid Recovery Core release 6.1.3 to 6.2.1, Exchange database mountability checks failed with error 'Database was not shutdown cleanly. Recovery must first be run to properly complete database operations for the previous shutdown.' 107946 Exchange mountability
Error message: "Oops.. Looks like something went completely wrong!" appeared when the Core was launched with non-default service port. 107175 Service Port. Service port, settings
There was no ability to change ESXi export timeouts either from GUI or from the Windows registry. 106784 Virtual export, vCenter/ESXi
The custom retention policy for a virtual machine on a Hyper-V cluster was not saved and rollup was not performed. 106088 Retention policy
Mount point folders were not deleted after dismount on a specific environment. 105714 Mount points
Encryption Key value became 'Not Encrypted' after machine was re-protected. 105412 Encryption keys
Mountability check job failed for some Exchange 2016 databases with error "Mail store 'dbname' is not mountable. Error: 'Database was not shutdown cleanly. Recovery must first be run to properly complete database operations for the previous shutdown.'" 105203 Exchange, mountability
Replication failed to start with incorrect RPFS file size error in a specific case. 105048 Replication
It was impossible to protect ESXi VMs agentlessly due to timeout error in Wizard if Core already had 100 or more VMs under protection.  102893 Agentless protection, vCenter/ESXi
Sometimes the Core failed to restore the configuration for some services during the remount volumes job that occurred after a factory reset, but the remount volumes job showed as successfully completed. 104043 Core
Reference counting checks failed when the index was greater than the maximum valid index.
103813 RRT
In the Spanish UI, agentless virtual machines did not appear on the virtual machines tab in the Spanish interface. 103782 Localization
In the Korean UI, there was no ability to boot from a RASR USB flash drive due to invalid information in the BCD file (0xc0000098). 103775 Localization
The Agent service crashes when trying to collect cluster SQL metadata of a database with the FileAttributes.ReparsePoint attribute. 103740 Agent
The status of a virtual machine exported to ESXi appears as "Disabled" or "Stopped" after editing the export configuration, which is expected. 103704 ESXi
Replication started outside of the scheduled time if the job was added to the queue. 103702 Replication
Restoring ReFS volumes did not work on Windows Server 2016. 103698 Restore
There was no ability to add a cloud account for Azure Government. 103683 Azure
Core performance got worse and used a lot of system resources while mounting a recovery point from an attached Azure archive. 103670 Azure
A connection to the MongoDB reporting database cannot be established due to insufficient free ports, which is expected. 103664 Reports
Restoring a Core configuration with a configuration backup file of a previous Core was not restricted. 103632 Core
A machine with a root on a RAID volume didn't boot after a successful export. 103558 Export
Resolving overlapped records failed with the error "Unable to find assembly 'Core.NativeWrapper, Version=1.0.6353.24371, Culture=neutral, PublicKeyToken=null'" when both types of records existed in the repository.
103556 RRT
The limitation for the maximum concurrent exports did not work correctly after specific steps. 103515 Core
The error "Placeholder mismatch with format string [Checking volume images by read {0} on {1} recovery point {2}] and arguments ..." appeared while performing an integrity check on a DVM repository, even though the check was successful. 103492 Repository
Resizing the Dedup Cache failed with the error "cache_io_engine: windows error 87" if the Dedup Cache was located on a disk with a sector size of 4 KB. 103469 Repository
When protecting a vCenter virtual machine, agentless protections fails with the error "An item with the same key has already been added." 103426 Agentless protection
A Core localized in Brazilian Portuguese failed to communicate with the License Portal, because the string was not recognized as a valid DateTime. 103371 Localization
While protecting a machine agentlessly, if the maximum number of permitted snapshots was exceeded, an incorrect error message displayed. 103334 Agentless protection
A transfer failed because there are no retries present on the CleanupSnapshotInternal stage, which is as designed. 103310 Transfers
There was a logic issue with the option "Include only the recovery in the date range..." when this option was used for a scheduled archive. 103283 Archiving
Sometimes the export postprocessing step took a lot of time, because there was incorrect dismount logic in the driver. 102742 Export
Sometimes there was no ability to protect a second cluster that had the same hostname as the first cluster, even though it was from a different domain. 102702 Protection
Incremental and Virtual Standby Hyper-V exports failed if the location or name for the exported virtual machine contained Chinese symbols. 102589 Localization
The warning "VSS full snapshot was taken with excluded VSS writers 'Microsoft Exchange Writer has state'" appeared about a non-existing writer on a protected machine (SQL or Exchange, depending on the instance installed) during log truncation. 102567 Protection
Azure Market Place Offer used "dell_software" in the URI. 102521 Azure
Incremental snapshots were slow for volumes with specific write activity. 102493 Protection
Deferred delete canceled after a rollup job on French operating systems. 102436 Localization
After an upgrade to 6.1.2, repository maintenance failed after restoring the provisioning configuration. 102340 Upgrade
When repository maintenance job was in progress, the Agent Settings page on the Rapid Recovery Core Console would hang. 102321 Repository, Maintenance Job, GUI
After several days, the AAFileFilter driver caused a blue screen to appear on a Hyper-V cluster running Windows Server 2012 R2 or Windows Server 2016. 102232 Agentless protection, server cluster, driver
A seed drive job automatically canceled due to a NullReferenceException. 101617 Seed drive
On Windows 2016, some drivers were blocked during an installation of the Agent software with the "Secure boot" option enabled. 101573 Agent installation
The VMwareProxy service crashed due to TCP/IP port exhaustion. 101485 VMware proxy
A remount job did not restore the locale of a Core. 101316 Localization
If a letter was assigned to a Recovery partition, the status of the volume displayed as "Not valid." 101224  
On a system test environment, ESXi virtual standby failed with the error "An entry with the same key already exists." 100868 ESXi
The VMM actions were available while the ESXi host was in maintenance mode. 35740 ESXi
There was an incorrect validation for the "Maximimum connection pooling size" and the "Minimum connection pooling size" fields for the MongoDB connection. 35607 Reports
A base image was taken when the NTFS Boot Sector copy changed. 34981 NTFS
Virtual disk provisioning failed with Return Code 4 if the storage pool did not consistently have empty space, which is as designed. 34937 Virtual machines
Unexpected base images were taken of the ESX(i) virtual machines that had snapshots with quiescing enabled. 34916 ESXi
The Virtual Standby tab performance was slow. 34434 Exporting
The warning message "Information about allocated space for some volumes is unavailable..." appeared on the Summary tab for a protected virtual machine (VM) if that VM was located on an NFS datastore. 33551 Virtual machines
All running archive jobs failed with the error "There is not enough space on the disk" if more than one archive job was in progress at the moment when the target network storage ran out of space. 31827 Archiving
Rollback or export using SAN transport mode failed because one of the parameters had an invalid error in ESXi. 29508 Agentless

 

Table 2: DL appliance resolved issues

Resolved Issue Description Issue ID Functional Area
On a DL1000, sometimes launching FTBU would hang on the splash screen after a required reboot of the server during a configuration using the first wizard. 105114 FTBU
Some ESXi export jobs failed with the error "VddkApiException: You do not have access rights to this file." 105029 ESXi
If one of the physical disks on a DL1300 or DL1000 was offline, the FTBU would hang after the first wizard on the "Applying Settings ..." window. 103699 FTBU
On a DL1300 or DL4300 with FI#3.2.55, the ApplianceProvisioningConfiguration.xml file was present on the RECOVERY partition after configuring FTBU. 103389 FTBU
Sometimes the message "Internal Server Error" appeared on the Backup tab. 102379 RASR
Jobs failed with the error "System.OutofMemoryException" on DL appliances after running for a period of time, which is as designed. 101246 Jobs
If a letter was assigned to a Recovery partition, the status of the volume displayed as "Not valid." 101224 Provisioning
Windows Backup could not be created because the necessary volume items for a backup could not be determined if the volume letters were changed. 100985 Windows Backup
If Windows Backup was forced on a server with old Winbackups of a 75 GB volume with no free space on the internal controller, the main appliance status was red and could not be resolved. 100887 Windows Backup
A restore of the provisioning configuration job failed with the uninformative error "Cannot mount volume to the folder 'I:\' because it contains files or folders," if the virtual disk has a letter that was already used before the remount. 35805 Provisioning
The behavior of the logic used to determine the provisioning size was incorrect. 35770 Provisioning
The GUI was not disabled immediately after confirming the remount process. 35579 Provisioning
The Start VM and Start Network Adapters buttons were not disabled when an ESXi or Hyper-V export of a machine was launched. 30989 Exporting

 

Table 3: DocRetriever resolved issues

Resolved Issue Description Issue ID Functional Area
DocRetriever failed to retrieve SharePoint hierarchy if a web application's port contained an extra space character. 105749 Restore
An incorrect username was displayed in the "Modified by" and "Modified" columns after restore of a file uploaded by another user. The file now shows the original username after restore. 105101 Restore
DocRetriever failed to open a SharePoint 2016 database with several sites that had similar IDs. 103710 SharePoint
DocRetriever did not restore "Content Editor" web parts in SharePoint 2013. 103241 Restore
The DocRetriever Agent did not work (all restore operations failed) on a machine with MOSS 2007 32-bit installed. Corrected for 6.1.2 and 6.1.3. 32-bit versions are no longer supported. 102522 Restore

 

Table 4: Documentation resolved issues

Known Issue Description Issue ID Functional Area
The components ANTLR 3.3.3 and ANTLR 4.0.2 previously appeared in the "Third-party contributions" topic found only within in-product help. These versions were not used in Rapid Recovery 6.1.3 and have been removed. The 6.2 version references ANTLR 3.4 and 4.0.2. 104031 Context-sensitive help
The component MongoDB 2.6 previously appeared in the "Third-party contributions" topic, even though it was not used in Rapid Recovery 6.1.3. For 6.2, the listing is updated to reference MongoDB 2.6.11. 104030 Context-sensitive help
The component Microsoft Windows Azure Storage 7.2.1 did not appear in the 6.1.3 third-party contributions topic. 6.2 uses version 8.2.0, which is included in the list. 102504 Context-sensitive help
The component DataGridViewImageAnimator 1.0 appeared in the 6.1.3 third-party contributions topic, even though it was not used in Rapid Recovery 6.1.3 and is no longer used. It has been removed in the current list. 102503 Context-sensitive help
The component SimpleRestServices 1.3.0.3 did not appear in the list of third-party contributions, whereas an outdated version had appeared. This version is included in the current list. 102502 Context-sensitive help
The component OpenStack.NET 1.4.0.2 did not appear in the list of third-party contributions, whereas an outdated version of the component appeared in its place. This version is included in the current list. 102501 Context-sensitive help
The component NLog 3.2.1 did not appear in the list of third-party contributions, whereas an outdated version of the component appeared in its place. The current list references version 4.4.1.2, which is used in release 6.2. 102500 Context-sensitive help
The component AWS SDK for .NET 3.3.1.2 did not appear in the list of third-party contributions, whereas an outdated version of the component appeared in its place. The current list references this version. 102499 Context-sensitive help

 

Table 5: Linux resolved issues

Resolved Issue Description Issue ID Functional Area
Snapshots and jobs for taking metadata failed for some Linux servers with RAID5 hardware. This was a specific environmental issue. 104919 Protecting
There was no ability to support LVM-based storage pools. 103488 LVM
Transfers from a Core failed on SLES 11.4 x32 with the following error: "The partition size is incorrect, please shrink the volume." 103300 SLES
There was an ability to select Linux system folders for a rollback restore, even though restoring to a system folder is not supported. 103178 Restore
The Agent service could not be started if it was installed on a machine that did not use the default init system, which is as designed. 35818 Agent
Specific volumes could not be mounted after the export of a Linux machine. 35288 Export

 

Table 6: Mailbox Restore resolved issues

Resolved Issue Description Issue ID Functional Area
MailboxRestore failed to perform restore to original location on specific environment due to wrong flags passed into OpenMsgStore MAPI method. 105755 Restore
Public folder permissions were not restored for empty folders. 105267 Restore
After opening an Exchange 2016 CU5 database in Mailbox restore, the Inbox folder was missing in some mailboxes. 104334 Restore
A security alert dialog did not display during a restore when the Exchange server used a self-signed certificate. 102765 Restore
A non-informative error message appears if the user was not found in GAL during a restore of permissions for a public folder. 102018 Restore

Known issues

The following is a list of issues known to exist at the time of release.

Third-party components are described in detail in our in-product help, which is refreshed only for major releases. In the interim, for legal compliance, updates to third-party components are included in the Documentation known issues section. If third-party components use a license not included in our in-product help, the license is included in these release notes. For example, see the GNU General Public License 3.

 

Table 7: DL Appliances known issues

Known Issue Description Issue ID Functional Area

Retention policy settings becomes disabled on DL1000 and DL1300 after upgrade to 6.2.0.

Workaround: Contact Quest Data Protection Support about this issue.

107303 Retention policy

In Rapid Recovery 6.0 and later, some non-English languages (namely French, Japanese, and Korean) use incorrect translations of the word "state" on the Backup page in the "Items Backed Up" section. The correct translation relates to the current condition.

Workaround: None.

35031

100061

DL appliance, Backups page

Table 8: Core and Windows known issues

Known Issue Description Issue ID Functional Area

The Core service can crash with AccessViolationException when it is replicating and is running with a newer .Net library than the one included with Rapid Recovery.

Workarounds: Use one or both of the following options:

  • Reduce the workload of the Core.
  • Pause replication
  • Downgrade the .Net framework to the version included with Rapid Recovery, which is .Net 4.6.2.
107708 Core

On Core protecting Oracle server, snapshots fail and Oracle service crashes with error: "The VSS writer 'Oracle VSS Writer - <database_name>' failed during the 'DoSnapshotSet' phase with error 'WriterErrorNonRetryable'.The VSS writer state is 'FailedAtFreeze'." Oracle is supported only in ARCHIVELOG mode. In this mode, the VSS writer calls the Oracle service to archive the existing re-do logs and create a new archive log file. The re-do logs are archived to Oracle's fast_recovery_area folder. When all space allocated to this folder is fully consumed, this error results. This behavior demonstrates Rapid Recovery Core functioning as designed. If you encounter this error, continue to the workarounds below.

Workaround: (1) Truncate logs manually to clear up disk space, restore using RMAN or VSS backups, and set a log truncation policy to avoid repetition. (2) Optionally, in SQL*Plus you can view and extend the space allocated for logs: Query:  "SHOW parameter db_recovery_file_dest;" Extension command (this example extends to 50GB): "ALTER system set db_recovery_file_dest_size = 50G SCOPE = both;" (3) Enable the "Log truncation for Oracle" nightly job using one of three deletion policies. You can truncate all jobs daily; or set a schedule to truncate them on a weekly or monthly basis; or retain a specified amount of new logs. For more information, see User Guide topics "About truncating Oracle logs" and "Manually truncating Oracle database logs."

107627 Oracle protection, log truncation
Data is lost on disk located on Scale Out File Server (SOFS) if you add some data to the disk and evict active SOFS cluster node.

Workaround: None.

107568 Hyper-V, agentless protection, clusters

When upgrading any Rapid Recovery release to release 6.2.x in languages other than English, the Compatibility informational mesage shows the wrong version in the message. The message should read: "Supported operating systems running Agent versions prior to 5.4.3 will be able to upgrade to 6.2.x automatically." The English version is correct.

Workaround: None.

106545 Installer, localization

Unexpected base images occur for cloned disks during Hyper-v agentless transfers.

Workaround: None.

106296 Hyper-V, agentless protection

Relocate recovery points to Virtual DR fails with error 'Job fails with RDS service exception. Error code: 'ConnectionResetByPeer.'

Workaround: None.

106200 Tiering

Customer request to decrease the number of events created during agentless backup on the vCenter.

Workaround: None. This item is an enhancement request.

105997 Events

Rollup job does not merge replicated recovery points according to the retention policy if seed drive for older recovery points was not consumed.

Workaround: None.

105830 Rollup jobs, replication, seed drive

Replication is not paused after upgrading Target Core from release 5.4.3 to release 6.2.x.

Workaround: None.

105606 Replication

Not all disks are exported after the VirtualBox export of ESXi agentless VM based on Windows 8.1 x86 and Windows 8.1 x64.

Workaround: None.

105560 Virtual exports

The Trustedinstaller process is called during every metadata request.

Workaround: Contact Quest Data Protection Supportfor patch P-2281 to address this issue.

105445 Metdata

The RapidRecoveryCore service may be deleted during an upgrade of the Core if any Microsoft Management Console (MMC) windows are open.

Workaround: Close all MMC windows before you begin upgrading the Core.

105282 Upgrading

It is impossible to set GDPR if the user tries to install Core using the Add-on for Kaseya.

Workaround: After installing using the Kaseya add-on, set GDPR (set the "Agree to use of personal data" setting) using General Settings in the Core Console.

104812 Core settings, Privacy setings, GDPR, Kaseya VSA

Agentless backup fails with error: "Invalid URI: The hostname could not be parsed" when the shadow copy has the path "(\\?\Volume{fb3687e7-57b5-11e7-80c4-f48e38cee0fd}\diskc.vhdx)."

Workaround: None.

104393 Agentless

After upgrade from release 5.4.3 to release 6.1 and later, all task events convert to service events.

Workaround: None.

103945 Upgrading

If the Quest NetVault Backup with BMR plugin is installed on the same server as the Rapid Recovery Core, then ESXi exports fail.

Workaround: Copy the following DLLs from Coreservice\vddk\bin to the Coreservice folder, and then restart the Core service:

  • glib-2.0
  • gobject-2.0
  • gvmomi
  • iconv
  • intl
  • libcurl
  • libxml2
  • vixDiskLibVim
103477 Virtual exports

Dashboard Transfer Job widget doesn't track jobs which are expired in the queue.

Workaround: Review the status using other aspects of the Core Console UI, or using PowerShell scripts.

103412 Dashboard widget

A deploy to Azure fails if the cloud service name is specified in FQDN format.

Workaround: Specify only the hostname (without periods) in the Cloud service name text box. For example, instead of specifying companycloudhost.cloudapp.net, enter companycloudhost.

102756 Azure

Drive letters are not assigned on an exported machine that is identical to the original machine.

Workaround: Assign drive letters manually, or contact Support for a script to run on the exported machine that solves the issue.

102390 Virtual exports

Add menu for switching between pages with recovery points on the top of the Recovery Points page.

Workaround: None required since this is an enhancement request.

101736 Recovery Points, GUI

EC2 Export job fails with exception: 'Amazon.EC2.AmazonEC2Exception: The key pair '{key_name}' does not exist.' for replicated Agent from another region.

Workaround: None.

100569 Virtual exports, Amazon E2C

Volume letters are not assigned after BMR for GPT partitions of ESXi Agentless VM.

Workaround: Assign drive letters manually.

97451 BMR, ESXi agentless

Exported CentOS7 isn't bootable on ESXi when it has more than 6 system volumes and root volume with the 'xfs' filesystem.

Workaround: Perform VM export of 6 volumes; use restore for remaining volumes.

97017 Virtual exports, Linux, XFS

An ESXi agentless Red Hat machine is not bootable after export to VirtualBox.

Workaround: None.

31277

96616

ESXi, agentless protection, Linux

ESXi virtual export with automatic disk mapping using default configuration for the VM configuration location fails with unclear error. The Failure Reason is "Task 'ReconfigVM_Task' failed: Invalid configuration for device '0'."

Workaround: Reduce the amount of concurrent exports.

27309

93141

Virtual exports, ESXi
The New License and Privacy Policy parameters are not rewritten during a Core installation if the Core was previously uninstalled without configurations.

Workaround: In the Settings of the Core Console, set the Privacy Policy and License settings.

106243 Configuration
An export to Amazon EC2 fails if the Amazon account has few subnets.

Workaround: None.

106107 Exporting
There is no ability to deploy and protect the machines if an older version of the Agent (release 5.4.3, 6.0.1, or 6.0.2) is installed on the Hyper-V server and you raise an error: "Unexpected end of file."

Workaround: Manually upgrade the Agent on the Hyper-V server to release 6.2.

105500 Hyper-V agentless

Table 9: Kaseya Add-On known issues

Known Issue Description Issue ID Functional Area
Add-on for Kaseya displays only 10 Kaseya Agents within different tabs.

Workaround: None.

104856 Kaseya Add-on
There is no ability to create Tiering repository using the Add-on for Kaseya.

Workaround: Create a Tiering repository using the Rapid Recovery Core Console.

104825 Tiering, Kaseya

Table 10: Linux known issues
Known Issue Description Issue ID Functional Area

Exported CentOS 7 is not bootable on ESXi when it has more than 6 system volumes and root volume with the 'xfs' filesystem.

Workaround: Perform VM export of 6 volumes; use restore for remaining volumes.

97017 Virtual exports, Linux, XFS

An ESXi agentless RedHat machine is not bootable after virtual export to VirtualBox.

Workaround: None.

31277

96616

ESXi, agentless protection, Linux
Protection of volumes created with LVM-based storage pools fails. LVM functionality will be included in a future release.

Workaround: Contact Support to request a patch that addresses this issue.

103488 Protection
Agentlessly protected Linux machines are not bootable after BMR.

Workaround 1: Use the Rapid Recovery Agent on all supported Linux distributions instead of using agentless protection if BMR is required.

Workaround 2: To fix boot issues, engage a knowledgeable Linux administrator to update the volume, reinstalling grub and editing the content of /etc/fstab. Other steps may be required for individual distributions.

31206 BMR bootability

Table 11: Documentation known issues

Known Issue Description Issue ID Functional Area

SQL Server 2005 is erroneously listed as supported by Rapid Recovery in 6.2.1documentation. This is expected to be removed in future versions.

Workaround: In the Rapid Recovery 6.2.1 User Guide topic "About SQL attachability," and in the Rapid Recovery 6.2.1 System Requirements Guide topic "Supported applications and cluster types," please disregard the inclusion of SQL Server 2005, which is no longer supported.

 

107985 Supportability

The third-party contributions lists the wrong version of AWS SDK for .NET.

Workaround:Rapid Recovery release 6.2.1 uses AWS SDK for .NET 3.3.1.2.

N/A 3PC
In the Rapid Recovery third-party contributions, the component ANTLR is listed as version 3.3.3. Rapid Recoveryrelease 6.2.1 uses ANTLR 3.4. N/A 3PC
The license/copyright for the third-party component bash-completion 1.2 does not appear in the list of third-party contributions list in the product.

Workaround: The bash-completion 1.2 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3 . The source code for this component can be found at http://opensource.quest.com. Bash-completion 1.2 uses the following copyright:

Copyright © 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

N/A 3PC
The license/copyright for the third-party component btrfs-tools 4.4-1 does not appear in the list of third-party contributions list in the product.

Workaround: The btrfs-tools 4.4-1 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Btrfs-tools 4.4-1 includes the following copyright:

various

Copyright © 2007-2012 Oracle <http://www.oracle.com/>

see http://changelogs.ubuntu.com/changelogs/pool/main/b/btrfs-tools/btrfs-tools_4.4-1/copyright for details

N/A 3PC
The license/copyright for the third-party component ca-certificates 2016.10.04 does not appear in the list of third-party contributions list in the product.

Workaround: The ca-certificates 2016.10.04 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Ca-certificates 2016.10.04 includes the following copyright:

N/A 3PC
The license/copyright for the third-party component casper 1.376 does not appear in the list of third-party contributions list in the product.

Workaround: The casper 1.376 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Casper 1.376 includes the following copyright:

Copyright © 1999-2002 Aladdin Enterprises
All rights reserved

Others, see http://changelogs.ubuntu.com/changelogs/pool/main/c/casper/casper_1.376/copyright for details

N/A 3PC
In the Rapid Recovery third-party contributions, the component Castle Windsor is listed as version 2.5.2. Rapid Recoveryrelease 6.2.1 uses Castle Windsor 2.5.3. N/A 3PC
In the Rapid Recovery third-party contributions, the component Chromium is listed as version 43.0.2312. Rapid Recoveryrelease 6.2.1 uses Chromium 57. N/A 3PC
The license/copyright for the third-party component cURL 7.47.x does not appear in the list of third-party contributions list in the product.

Workaround: The cURL 7.47.x component uses the Curl 1.0 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright 1996 - 2008, Daniel Stenberg

N/A 3PC
The license/copyright for the third-party component docutils 0.14 does not appear in the list of third-party contributions list in the product.

Workaround: The python minimal 2.7.7 component uses the Python 2.7 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyrights:

  • Copyright 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Python Software Foundation; All Rights Reserved
  • Copyright 1995-2001 Corporation for National Research Initiatives; All Rights Reserved"
  • Copyright 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved.

N/A 3PC
The license/copyright for the third-party component efibootmgr 0.12-4 does not appear in the list of third-party contributions list in the product.

Workaround: The efibootmgr 0.12-4 component uses the GPL (GNU General Public License) 2.0, which is included in the "Third-party contributions" topic accessible from in-product help in the Rapid Recovery Core Console. This component is not actually used by our application, but it is provided with our product for our customers' convenience. It includes the following copyrights:

  • Copyright: 2001-2009 Dell, Inc <Matt_Domsch@Dell.com>
    • 2012-2014 Dell, Inc <Jordan_Hargrave@Dell.com>
    • 2013-2014 Peter Jones <pjones@redhat.com>
  • Copyright: 2001-2013 Bdale Garbee <bdale@gag.com>
    • 2013 Steve McIntyre <93sam@debian.org>
    • 2014 Daniel Jared Dominguez <Jared_Dominguez@Dell.com>
N/A 3PC
The license/copyright for the third-party component fakeroot 1.20.2 does not appear in the list of third-party contributions list in the product.

Workaround: The fakeroot 1.20.2 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The component includes the following copyrights:

N/A 3PC
The license/copyright for the third-party component gcc 4.5.3 does not appear in the list of third-party contributions list in the product.

Workaround: The gcc 4.5.3 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Gcc 4.5.3 includes the following copyright:

Copyright © 1987, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012

Free Software Foundation, Inc.

N/A 3PC
The license/copyright for the third-party component gdisk 1.0.1 does not appear in the list of third-party contributions list in the product.

Workaround: The gdisk 1.0.1 component uses the GPL (GNU General Public License) 2.0, which is included in the "Third-party contributions" topic accessible from in-product help in the Rapid Recovery Core Console. This component is not actually used by our application, but it is provided with our product for our customers' convenience. The source code for this component can be found at http://opensource.quest.com.

N/A 3PC
In the Rapid Recovery third-party contributions, the component Google APIs Client Library for .NET is listed as version 1.9.2. Rapid Recoveryrelease 6.2.1 uses Google APIs Client Library for .NET 1.32.2. N/A 3PC
The license/copyright for the third-party component htop 2.0.1-1 does not appear in the list of third-party contributions list in the product.

Workaround: The htop 2.0.1-1 component uses the GPL (GNU General Public License) 2.0. This component is not actually used by our application, but it is provided with our product for our customers' convenience. The source code for this component can be found at http://opensource.quest.com. Htop 2.0.1-1 includes the following copyrights:

  • Copyright: 2004-2016 Hisham Muhammad
  • Copyright: 2016 Daniel Lange
  • 2008-2016 Eugene V. Lyubimkin
  • 2004-2008 Bartosz Fenski
N/A 3PC
In the Rapid Recovery third-party contributions, the component JavaScriptEngineSwitcher is listed as version 1.2.4. Rapid Recoveryrelease 6.2.1 uses JavaScriptengineSwitcher 2.0.0. N/A 3PC
In the Rapid Recovery third-party contributions, the component jQuery is listed as version 1.8.2. Rapid Recoveryrelease 6.2.1 uses jQuery 1.9.2. N/A 3PC
In the Rapid Recovery third-party contributions, the component Json.NET is listed as version 4.5. Rapid Recoveryrelease 6.2.1 uses Json.NET 9.0.1. N/A 3PC
In the Rapid Recovery third-party contributions, the component jsTree is listed as version 1.0-rc3. Rapid Recoveryrelease 6.2.1 uses jsTree 1.0.0. N/A 3PC
In the Rapid Recovery third-party contributions, the component libc is listed as version 2.11.3. Rapid Recoveryrelease 6.2.1 uses libc 2.23. N/A 3PC
The license/copyright for the third-party component libc6-dev 2.23 does not appear in the list of third-party contributions list in the product.

Workaround: The libc6-dev 2.23 component uses the LGPL (GNU Lesser General Public License) 2.1, which is available at http://www.quest.com/legal/license-agreements.aspx. The source code for this component can be found at http://opensource.quest.com. Libc6-dev 2.23 includes the following copyrights:

Copyright © 1991-2015 Free Software Foundation, Inc.

and others, see http://changelogs.ubuntu.com/changelogs/pool/main/g/glibc/glibc_2.23-0ubuntu10/copyright

N/A 3PC
The license/copyright for the third-party component libc-dev-bin 2.23 does not appear in the list of third-party contributions list in the product.

Workaround: The libc-dev-bin 2.23 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Libc-dev-bin 2.23 includes the following copyrights:

  • Copyright © 1991-2015 Free Software Foundation, Inc.
  • Copyright © 1991 Regents of the University of California.
  • All rights reserved.
  • Portions Copyright © 1993 by Digital Equipment Corporation.
  • Portions Copyright © 1996-1999 by Internet Software Consortium.
  • Copyright © 2010, Oracle America, Inc.
  • Copyright © 1991,1990,1989 Carnegie Mellon University
  • All Rights Reserved.
  • Copyright © 2000, Intel Corporation
  • All rights reserved.
  • Copyright © by Craig Metz
  • Copyright © 1992 Eric Young
  • Copyright © 2002, 2003, 2004, 2011 Simon Josefsson
  • Copyright © 1999, 2000 Tom Tromey
  • Copyright 2000 Red Hat, Inc.
  • Copyright © The Internet Society (2003). All Rights Reserved.
  • Copyright © 1998 WIDE Project.
  • All rights reserved.
  • Copyright 1995 by Tom Lord
  • Copyright 1992, 1993, 1994, 1997 Henry Spencer. All rights reserved.
  • Copyright © 1997-2003 University of Cambridge
  • Copyright © 1993 by Sun Microsystems, Inc. All rights reserved.
  • Copyright © C E Chew
  • Copyright 2001 by Stephen L. Moshier <moshier@na-net.ornl.gov>
N/A 3PC
The license/copyright for the third-party component libesedb 20150409 does not appear in the list of third-party contributions list in the product.

Workaround: The libesedb 20150409 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Libesedb 20150409 includes the following copyright:

Copyright © 2009-2015, Joachim Metz <joachim.metz@gmail.com>

N/A 3PC
In the Rapid Recovery third-party contributions, the component libext2fs is listed as version 1.42.12. Rapid Recoveryrelease 6.2.1 uses libext2fs 1.43.4. N/A 3PC
The license/copyright for the third-party component libfakeroot 1.20.2 does not appear in the list of third-party contributions list in the product.

Workaround: The libfakeroot 1.20.2 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Libfakeroot 1.20.2 includes the following copyrights:

  • Copyright © 1997, 1998, 1999, 2000, 2001 joost witteveen
  • Copyright © 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Clint Adams
  • Copyright © 2009 Regis Duchesne
N/A 3PC
The license/copyright for the third-party component libreadline5 5.2 does not appear in the list of third-party contributions list in the product.

Workaround: The libreadline5 5.2 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Libreadline5 5.2 includes the following copyrights:

  • Copyright © 1987-2009 Free Software Foundation, Inc.
  • Copyright © 1999 Jeff Solomon (examples/excallback.c)
  • Copyright © 2003-2004 Harold Levy (examples/rl-fgets.c)
  • Copyright © 1993-2002 Juergen Weigert (examples/rlfe)
  • Copyright © 1993-2002 Michael Schroeder (examples/rlfe)
  • Copyright © 1987 Oliver Laumann (examples/rlfe)
N/A 3PC
The license/copyright for the third-party component linux-libc-dev 4.4.0 does not appear in the list of third-party contributions list in the product.

Workaround: The linux-libc-dev 4.4.0 component uses the GPL (GNU General Public License) 2.0, which is included in the "Third-party contributions" topic accessible from in-product help in the Rapid Recovery Core Console. This component is not actually used by our application, but it is provided with our product for our customers' convenience. Linux-libc-dev 4.4.0 includes the following copyrights:

N/A 3PC
The license/copyright for the third-party component lsscsi 0.27-3 does not appear in the list of third-party contributions list in the product.

Workaround: The lsscsi 0.27-3 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Lsscsi 0.27-3 includes the following copyrights:

  • Copyright: 2003-2005 Doug Gilbert <dgilbert@interlog.com>
  • Copyright: Copyright 2005 Matt Taggart <taggart@debian.org>
N/A 3PC
The license/copyright for the third-party component lupin-casper 0.57 does not appear in the list of third-party contributions list in the product.

Workaround: The lupin-casper 0.57 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Lupin-casper 0.57 includes the following copyright:

Copyright © 2007 Agostino Russo <agostino.russo@gmail.com>.

N/A 3PC
The license/copyright for the third-party component lvm2 2.02.167 does not appear in the list of third-party contributions list in the product.

Workaround: The lvm2 2.02.167 component uses the LGPL (GNU Lesser General Public License) 2.1, which is available at http://www.quest.com/legal/license-agreements.aspx. The source code for this component can be found at http://opensource.quest.com. Lvm2 2.02.167 includes the following copyright:

Copyright © 2008-2013 Red Hat, Inc. All rights reserved.

N/A 3PC
The license/copyright for the third-party component make 4.1 does not appear in the list of third-party contributions list in the product.

Workaround: The make 4.1 component uses the GPL (GNU General Public License) 2.0, which is included in the "Third-party contributions" topic accessible from in-product help in the Rapid Recovery Core Console. This component is not actually used by our application, but it is provided with our product for our customers' convenience. The source code can be found at http://opensource.quest.com.

N/A 3PC
The license/copyright for the third-party component mc 3.4.8 does not appear in the list of third-party contributions list in the product.

Workaround: The mc 3.4.8 component uses the GPL (GNU General Public License) 2.0, which is included in the "Third-party contributions" topic accessible from in-product help in the Rapid Recovery Core Console. This component is not actually used by our application, but it is provided with our product for our customers' convenience. The source code can be found at http://opensource.quest.com. Mc 3.4.8 includes the following copyright:

various, mostly

Copyright © Free Software Foundation, Inc.

N/A 3PC
The license/copyright for the third-party component mdadm 3.3-2ubuntu7 does not appear in the list of third-party contributions list in the product.

Workaround: The mdadm 3.3-2ubuntu7 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com.

N/A 3PC
The license/copyright for the third-party component Microsoft Windows Azure Storage 8.2.0 does not appear in the list of third-party contributions list in the product.

Workaround: The Microsoft Windows Azure Storage 8.2.0 component uses the Apache 2.0 license, which is included in the "Third-party contributions" topic accessible from in-product help in the Rapid Recovery Core Console.

N/A 3PC
The license/copyright for the third-party component Mono class libraries 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The Mono class libraries 5.2.0 component uses the MIT N/A license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright © 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

N/A 3PC
The license/copyright for the third-party component Mono eglib 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The Mono eglib 5.2.0 5.2.0 component uses the MIT N/A license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

© 2006 Novell, Inc© 2006 Novell, Inc

N/A 3PC
The license/copyright for the third-party component Mono Garbage Collector 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The Mono Garbage Collector 5.2.0 component uses the MIT N/A license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright © 2001, 2002, 2003 Ximian, Inc and the individuals listed on the ChangeLog entries.

N/A 3PC
The license/copyright for the third-party component mono man 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The mono man 5.2.0 component uses the MIT N/A license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright © 2001, 2002, 2003 Ximian, Inc and the individuals listed on the ChangeLog entries.

N/A 3PC
The license/copyright for the third-party component mono msc/jay 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The mono msc/jay 5.2.0 component uses the BSD-style N/A license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright © 1989 The Regents of the University of California. All rights reserved.

N/A 3PC
The license/copyright for the third-party component Mono Support 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The Mono Support 5.2.0 component uses the LGPL (GNU Lesser General Public License) version 2.1 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright © Mono project (authors listed in individual ChangeLog entries)

N/A 3PC
The license/copyright for the third-party component mono tools 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The mono tools 5.2.0 component uses the MIT N/A license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright © 2001, 2002, 2003 Ximian, Inc and the individuals listed on the ChangeLog entries.

N/A 3PC
The license/copyright for the third-party component Mono VM 5.2.0 does not appear in the list of third-party contributions in the product.

Workaround: The Mono VM 5.2.0 component uses the LGPL (GNU Lesser General Public License) version 2.1 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright © Mono project (authors listed in individual ChangeLog entries)

N/A 3PC
In the Rapid Recovery third-party contributions, the component MsieJavaScriptEngine is listed as version 1.4.3. Rapid Recoveryrelease 6.2.1 uses MsieJavaScriptEngine 2.0.0. N/A 3PC
The license/copyright for the third-party component Newtonsoft.json 9.0.1 does not appear in the list of third-party contributions in the product.

Workaround: The Newtonsoft.json 9.0.1 component uses the MIT N/A license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyright:

Copyright (c) 2001Copyright (c) 2007 James Newton-King

N/A 3PC
The license/copyright for the third-party component openssh-server 1.7.2 does not appear in the list of third-party contributions in the product.

Workaround: The openssh-server 1.7.2 component uses the OpenBSD 1.19 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyrights:

  • Copyright 1995 Tatu Ylonen , Espoo, Finland
  • Copyright 1998 CORE SDI S.A., Buenos Aires, Argentina
  • Copyright 1996 David Mazieres
  • Copyright 1995 The Regents of the University of California.
  • Copyright Markus Friedl, Theo de Raadt, Niels Provos, Dug Song, Aaron Campbell, Damien Miller,
  • Kevin Steves, Daniel Kouril, Wesley Griffin, Per Allansson, Nils Nordman, Simon Wilkinson. All rights reserved.
N/A 3PC
The license/copyright for the third-party component Oracle.ManagedDataAccess 12.1.24160719 does not appear in the list of third-party contributions in the product.

Workaround: Rapid Recovery uses the Oracle.ManagedDataAccess 12.1.24160719 component. The component uses the Oracle Technology Network License Agreement. End users are not permitted to redistribute this component. The component may contain open-source components for which source code is available upon written request submitted to the following address:

Oracle America, Inc.
500 Oracle Parkway
Redwood City, CA 94065

N/A 3PC
The license/copyright for the third-party component parted 3.2.-15 does not appear in the list of third-party contributions list in the product.

Workaround: The parted 3.2.-15 component uses the GPL (GNU General Public License) 2.0, which is included in the "Third-party contributions" topic accessible from in-product help in the Rapid Recovery Core Console. This component is not actually used by our application, but it is provided with our product for our customers' convenience.

N/A 3PC
In the Rapid Recovery third-party contributions, the component PuTTY is listed as version 0.63. Rapid Recoveryrelease 6.2.1 uses PuTTY 0.62. N/A 3PC
In the Rapid Recovery third-party contributions, the component RazorGenerator is listed as version 2.1. Rapid Recoveryrelease 6.2.1 uses RazorGenerator 2.4.8. N/A 3PC
The license/copyright for the third-party component screen 4.3.1-2build1 does not appear in the list of third-party contributions list in the product.

Workaround: The screen 4.3.1-2build1 component uses the GNU General Public License (GPL) 3 license, which is available at GNU General Public License 3. The source code for this component can be found at http://opensource.quest.com. Screen 4.3.1-2build1 includes the following copyrights:

  • Copyright © 1993-2002
  • Juergen Weigert (jnweiger@immd4.informatik.uni-erlangen.de)
  • Michael Schroeder (mlschroe@immd4.informatik.uni-erlangen.de)
  • Copyright © 1987 Oliver Laumann
N/A 3PC
The license/copyright for the third-party component Select2 4.0.3 does not appear in the list of third-party contributions list in the product.

Workaround: The Select2 4.0.3 component uses the the Apache 2.0 license, which is included in the "Third-party contributions" topic accessible from in-product help. The Select2 4.0.3 component includes the copyright "© Kevin Brown."

N/A 3PC
In the Rapid Recovery third-party contributions, the component SSH.Net is listed as version 2013.4.7. Rapid Recoveryrelease 6.2.1 uses SSH.Net 2016.1.0. N/A 3PC
In the Rapid Recovery third-party contributions, the component zlib is listed as version 1.2.5. Rapid Recoveryrelease 6.2.1 uses zlib 1.2.8. N/A 3PC
The license/copyright for the third-party component python minimal 2.7.7 does not appear in the list of third-party contributions in the product.

Workaround: The python minimal 2.7.7 component uses the Python 2.7 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyrights:

  • Copyright 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Python Software Foundation; All Rights Reserved
  • Copyright 1995-2001 Corporation for National Research Initiatives; All Rights Reserved
  • Copyright 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved.

106842 3PC
The license/copyright for the third-party component openssh-server 1.7.2 does not appear in the list of third-party contributions in the product.

Workaround: The openssh-server 1.7.2 component uses the OpenBSD 1.19 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyrights:

  • Copyright 1995 Tatu Ylonen , Espoo, Finland
  • Copyright 1998 CORE SDI S.A., Buenos Aires, Argentina
  • Copyright 1996 David Mazieres
  • Copyright 1995 The Regents of the University of California.
  • Copyright Markus Friedl, Theo de Raadt, Niels Provos, Dug Song, Aaron Campbell, Damien Miller,Kevin Steves, Daniel Kouril, Wesley Griffin, Per Allansson, Nils Nordman, Simon Wilkinson. All rights reserved.

106841 3PC
A change was introduced in Rapid Recovery Core after the Rapid Recovery 6.2 User Guide was published and translated related to log truncation for Oracle databases. The "Log truncation for Oracle" nightly job is now disabled by default, to keep parity with default behavior of log truncation for other supported applications. Future editions of the User Guide will update topics "About protecting Oracle database servers" and "About truncating Oracle logs" to note that the nightly job is disabled by default. Since archive logs can consume substantial space, the first topic will also be revised to include the requirement to implement a log truncation regime.

Workaround: Users are advised that log truncation for Oracle is disabled by default. Determine and implement a log truncation strategy. You can enable the "Log truncation for Oracle" nightly job to truncate logs automatically (using one of three deletion policies); you can manually truncate logs on demand; or you can include both options.

106264 Technical documentation, nightly jobs, log truncation

The Rapid Recovery User Guide procedure "Deploying a virtual machine in Azure" for release 6.2 contains unnecessary steps 4 through 8. Future versions of documentation are to be modified accordingly.

Workaround: When following this procedure, disregard steps 4 through 8. After performing step 3, skip to step 9. This step is performed on the Destination page of the Deploy to Azure Wizard.

101859 Azure export

The Rapid Recovery User Guide procedure "Setting up continual export to Azure" for releases 6.1.x and 6.2.0 contains unnecessary steps 4 and 5. Future versions of documentation are to be modified accordingly.

Workaround: When following this procedure, disregard steps 4 and 5. Since you are defining ongoing continual export, you are not prompted to select a recovery point. After performing step 3, skip to step 6. Likewise, there is no Summary page at the end of the wizard. On the Volumes page of the wizard, click Finish (instead of Next).

101858 Azure export
Containers created in Azure are used to store virtual machines exported from the Rapid Recovery Core to your associated Azure account. If you create a specific container prior to performing virtual export, the Virtual Machine Export Wizard typically displays that container as one of the choices in the Container name field of the Destination window. If you create the container by typing a valid container name into the Container name field as part of the process of defining a virtual export, the container may not be immediately visible in the wizard. This behavior is not reflected in the appropriate procedures in the Rapid Recovery 6.2 User Guide.

Workaround: If you create a container from the Virtual Machine Export Wizard in Rapid Recovery Core release 6.1x or 6.2x, and that container is not accessible in the wizard UI, simply close the wizard, and launch it again, and you should then be able to access the newly created container. Azure Service Management (ASM, known as the Classic deployment model) is being de-supported by Microsoft. Accordingly, support for ASM is being replaced in a future release of Rapid Recovery Core exclusively with support for Azure Resource Manager, and will only support Azure containers created using ARM. When this change occurs, documentation will be modified accordingly.

101853 Azure export
When performing virtual export to Azure, the Rapid Recovery Core release 6.2.1 and earlier uses Azure storage and containers created using the Classic management model. Containers created in Azure using the newer Resource Manager deployment model are not recognized by the Core. The Rapid Recovery 6.2 User Guide procedure "Creating a container in an Azure storage account" does not specify that the Classic management model is required.

Workaround: Use the Classic management model to create storage accounts and containers for virtual export. If you already have a storage account created using the Classic model, any new containers created for it will automatically use the correct model (Classic).

101837 Azure export
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating