Azure Repository
Rapid Recovery 6.5 adds support for a new repository type (Native Azure Storage) that enables direct repository connections to Microsoft Azure Blob storage.
Consider the following details when implementing this feature:
- This feature has been released in Beta status to allow for evaluation and testing. In some circumstances, performance is not suitable for production environments.
- This feature is intended for use as a replication target repository. Using an Azure repository for backup storage on a primary or source core is not recommended.
- Metadata files must be stored locally.
- Only one Azure repository is supported per Rapid Recovery Core
Complete the following steps to create an Azure Repository.
- Navigate to the Rapid Recovery Core Console.
- On the icon bar, click
(More), and then select
Repositories.
- At the top of the page, under the Repositories page title, click + Create.
- Select Azure Repository.
- On the Configuration page, enter the information as described below:
- Name - Enter the display name of the repository.
By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed. Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.
- Comments - Optionally, enter a descriptive note about this repository. You can enter up to 254 characters.
- Name - Enter the display name of the repository.
- Click Next.
- On the Storage Location page, enter the following information:
- Location - Specify the path to a storage location on Azure blob storage. Use only alphanumeric characters, hyphen, or period, with no spaces or special characters.
- Dedupe cache location - Select Azure blobs or Local file system.
- Index files location - Select Azure blobs or Local file system.
- Data Storage account -Select the appropriate Azure Storage account. Refer to Cloud Accounts in the Rapid Recovery User Guide for more information.
NOTE: If you have configured a Microsoft Azure Resource Management (for Virtual Export) account for use with VM export, that account cannot be used for the Azure repository.
- Account name - Enter the name of your Microsoft Azure storage account. The name must match the storage account name in Azure precisely. It must contain lower case letters and numbers only, and be between 3 and 24 characters in length.
- Access key - Enter the access key for your account. You can enter the primary or secondary key. Your access key can be found under the Settings > Access Keys section of your Azure Storage account.
- Account type - Choose your Azure account type; for example Azure, Azure Germany, Azure China, or (US) Government.
- Use https protocol - Select this option to use the secure https protocol instead of the standard http protocol.
- Click Next.
- On the Space Allocation page, specify the following :
- Azure repostory size in GB
- Deduplication cache size in GB
- When you have completed your repository configuration, click Finish.
The Create Repository Wizard closes, and Rapid Recovery applies the settings to your Core. If Toast alerts are enabled, you see messages indicating that repository creation has started, and the repository is mounted. Alternatively, you can monitor the progress of the repository creation by viewing alerts on the Events page.
After a brief pause, on the Repositories page, in the Repositories summary table, your new repository is listed
Enhancements
The following enhancements have been added to Rapid Recovery 6.5, or were not previously documented in earlier releases
- Multiple platform and application support updates:
- Support for SharePoint 2019
- Support for Ubuntu 19.10
- Support for Ubuntu 20.04
- Support for RHEL/CentOS/Oracle Linux 8
- Improved performance of SQLmetadata checks
- Added the ability to configure deletion of recovery points on a per volume basis
- Added the ability to enable/disable SQL Metadata Checking for protected machines via the UI
Resolved issues
This topic contains the issues resolved in this release:
The following is a list of issues addressed in this release.
Table 1: Issues resolved in this release
| Issue ID | Resolved Issue Description |
|---|---|
| 110503 | Live restore should be occurring simultaneously for all volumes and can access the files during the restore |
| 110450 | Incremental ESXi export fails with * An unexpected error occurred: An argument was unexpectedly null in code located in or called by 'EsxServer.SetCachedValue' |
| 110365 | Restore of linked Agent failed with error: The volume restore failed because it is in use |
| 110332 | Azure Cloud account (for export) Secret Key is written in plain text in Core registry |
| 110325 | Specific Windows Server 2019 BIOS (ESXi 6.5 version) is not booting after BMR |
| 110147 | PowerShell scripts failing with a dependency error |
| 110102 | Inbox folder is empty after opening an Exchange 2019 CU4 database |
| 110090 | Archive to Amazon S3 (Wasabi endpoint) job fails with "The remote server returned an error: (500) Internal Server Error." if chain contains volume image with size 0 MB |
| 110076 | VMs goes offline after changing HyperV cluster credentials |
| 110073 | Archiving to Amazon Government Cloud with Glacier option fails "The specified bucket is not valid" and "400 Bad Request" |
| 110070 | Export fails with "Replay.Common.Contracts.Win32Api.Win32ApiFailedException: Failed to open 'C:\Mount...\FatVolumeMetadata.xml' for writing - The file or directory is corrupted and unreadable" |
| 110020 | Incorrect description of transfer queue option "Maximum concurrent transfers from a single Hyper-V host" for cluster agentless protection |
| 109999 | Installer crashes while upgrading Rapid Recovery to version 6.4 on a SQL Server with Analysis Services Configuration in Tabular Mode |
| 109967 | Linux agent's service crash on the passive node of oracle cluster with shared device |
| 109951 | Core do not parsed Linux volumes with specific ID (more then 255) |
| 109902 | Rapid Recovery Linux driver attached to new block device without protection by Core |
| 109862 | There is no ability to protect Cluster using account/credentials saved in Credentials Vault |
| 109842 | Oracle metadata cannot be collected if the Oracle database has specific configuration and customized db registry key name |
| 109835 | Archive to Amazon S3 (Wasabi endpoint) job fails with "The remote server returned an error: (500) Internal Server Error." |
| 109790 | Agentless VM is in trial after re-protect with NPH front-end capacity license with large enough license pool applied |
| 109770 | Archive to Google job fails after 7 days |
| 109740 | Oracle metadata will not be obtained if the Oracle DB listener has non-default (customized) name |
| 109691 | Device does not detach or attach from the Rapid Recovery driver without refreshing metadata |
| 109615 | Transfer fails with "Length cannot be less than zero. Parameter name: length" error for specific ESXI agentless VM |
| 109600 | Transfer fails due to exception ' '.vmx' download failed with status 'NotFound' ' for ESXI if datacenter located in folder |
| 109188 | 24 hour interval not able to be saved correctly in Transfer Schedule Templates and leads to inoperative transfers |
| 108299 | Replicated data is calculated as Protected data with NPH capacity license applied on target Core |
| 104393 | Agentless backup fails with "Invalid URI: The hostname could not be parsed" error when the shadow copy has specific path (\\?\Volume{fb3687e7-57b5-11e7-80c4-f48e38cee0fd}\diskc.vhdx) |
| 102756 | Deploy to Azure fail if specify cloud service name in FQDN format |
Known issues
This topic contains known issues in the following categories:
- Core and Windows known issues
- Documentation known issues
- Linux known issues
- Local Mount Utility issues
Table 2: Core and Windows known issues
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
| 27309 93141 |
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'." | Reduce the number of concurrent exports. | Virtual exports, ESXi |
| 110523 | Exchange log truncation not working for ESXi agentless VMs if one database is dismounted | Mount all of the databases on the Exchange Server side. | Agentless protection, Exchange |
| 110479 | Newly created virtual machines don't automatically show up in the Core GUI Virtual Machines list of ESXi host. | Restart Core services to update Virtual Machines list. | |
|
110473 |
Exchange log truncation not working for HyperV agentless VMs |
Available workarounds are:
|
Agentless protection, Exchange |
| 109236 | Transfer job for VM with SharedVHDX on SOFS appears to fail with errors "Session with the id has not been found: fileTransmitSessionId" and "The process cannot access the file because it is being used by another process: " but recovery points actually are created. | ||
|
108972 |
Trying to perform an "Open Exchange Database" job from a recovery point fails with error "Multiple concurrent writable mounts of a single volume are not supported." |
Use the Local Mount Utility, or manually mount the recovery point and open the database. |
|
| 108764 | When performing a virtual export or a virtual standby and you choose 'Specific' network adapters, the virtual standby is created with an additional e1000 NIC on top of the one you specified | No workaround at this time. | Virtual export |
| 109828 | When Core services are restarted, a "Virtual environment component 'Hypervisor Storage' changed status to 'Warning" alert is displayed. | No workaround at this time. | |
| 109682 | When attempting to archive to an existing Azure Government cloud account, error 'Initialization of new instance of type...' appears and archive is unsuccessful. | No workaround at this time. | Archive, cloud, Azure Government |
| 109575 | On a specific environment, Core Console UI does not load, with the error "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." | No workaround at this time. | Core Console UI |
| 107978 | When deploying the Rapid Recovery Agent from the Core server, the Microsoft Store Install Service disappears from the list of services visible on the protected machine. | No workaround at this time. | Agent installation |
| 107947 | On a specific environment, virtual export fails to start, with error: 'Cannot connect to a remote machine '{0}' ' sometimes on unstable environment. | Contact Quest Support for a patch to resolve this issue. | Virtual export |
| 107855 | On a specific Dell PowerEdge Windows server environment, protected machine hangs briefly (up to 1 minute) every hour when the Rapid Recovery Agent service starts, seemingly due to a 20-30 BCD query. | Perform BCD queries one at a time, sequentially, to avoid this issue. For diagnostic steps, see Quest Knowledge Base article 259558. | Agent hang |
| 107784 | When protecting a cluster, there is no ability to add cluster nodes to Virtual Standby | No workaround at this time. | Virtual export |
| 107755 | When creating an archive using the Archive Wizard, if you return from the Options wizard page back to the Machines page, there is no ability to edit the date range. | Close the wizard without saving the archive, and run through the wizard again. | Archiving, usability |
| 107346 | When restoring or performing virtual export of a volume with 512-bytes per sector to a volume with 4096-bytes per sector, a warning message does not appear. | For workaround, please see Quest Knowledge Base article 144232. | Virtual export, notifications |
| 107304 | On a specific appliance environment, the error message "GetResponse Timed Out" appears when trying to open the Appliance page. | Contact Quest Support for a patch to resolve this issue. | Appliance, Core Console UI |
| 107182 | Encryption key does not apply to cluster nodes during cluster protection. | Select encryption key for nodes manually in Settings. | Encryption |
| 106938 | On a specific appliance environment, the "Storage Hardware" information is not available on the Appliance Health page. | Contact Quest Support for a patch to resolve this issue. | Appliance, Core Console UI |
| 106545 | When upgrading a Core (in languages other than English) that protects machines with Agent version earlier than 5.4.3.106, the Compatibility page of the Rapid Recovery Core Installer wizard incorrectly shows Agent version 7 in the message instead of Agent 6.2 or Agent 6.3 (based on the installer being used). | None available. Disregard the version number. Protected machines with supported operating systems will be upgraded to Rapid Recovery Agent version 6.3. | Installer, localization |
| 105830 | Rollup job does not merge replicated recovery points according to the retention policy if seed drive for older recovery points was not consumed. | Consume the seed drive on the target core. | Rollup jobs, replication, seed drive |
| 105445 | Trustedinstaller process called during every metadata request from Agent, consuming about 100MB of additional RAM. | Contact for a patch to address this issue. | Metadata |
| 103477 | If the Quest NetVault Backup with BMR plugin is installed on the same server as the Rapid Recovery Core, then ESXi exports fail. | Copy the following DLLs from Coreservice\vddk\bin to the Coreservice folder, and then restart the Core service:
|
Virtual exports |
| 102390 | Drive letters are not assigned on an exported machine that is identical to the original machine. | Assign drive letters manually, or contact Support for a script to run on the exported machine that solves the issue. | Virtual exports |
| 97451 | Volume letters are not assigned after BMR for GPT partitions of ESXi Agentless VM. | Assign drive letters manually. | BMR, ESXi agentless |
Go to the top of the Known issues topic.
Table 3: Documentation known issues
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
|
109897 |
The following corrections were made to the Rapid Recovery 6.4 User Guide but not in the in-product help:
|
Please refer to the PDF or HTML-based User Guide on the Quest technical documentation website to see the latest content in the topics specified. When reviewing these topics within in-product help, disregard the minor discrepancies, and take heed of the updated information regarding deduplication cache which is flushed and re-created if the deduplication cache size is reduced. |
In-product help, technical product documentation |
|
109793 |
Within in-product help, on the Settings page of the Core Console, if you click the
|
To read about licensing in release 6.4, see the Rapid Recovery 6.4 Installation and Upgrade Guide topic "Managing Rapid Recovery licenses." In previous editions of in-product help, this Core setting included a link to information about licensing. That topic no longer appears in the User Guide or in-product help. The |
In-product help, Rapid Recovery Core Console, Core Settings, License Details |
| N/A | The information for the following third-party components has been added or updated in Rapid Recovery Core release 6.4 after in-product help was produced. The following notifications comprise supplemental updates to in-product help for third-party contributions. Their purpose is to provide proper attribution and meet legal and copyright requirements related to the use of the listed components. |
Consult these notifications in Release Notes for the latest updates to legal and copyright requirements. | In-product help, Third-party components, copyrights, legal requirements |
|
|
|
Component p7zip 16.0.2 uses the Mozilla Public License (MPL) 1.1. A copy of the MPL can be found as a linked license in Rapid Recovery's Third-Party Components link within in-product help. |
|
|
|
|
This component is not actually used by Rapid Recovery, but may be used by protected Linux machines. NBD is not available on the Linux DVD. Red Hat Enterprise Linux, CentOS and Oracle Linux installation packages download NBD source code from a publicly-accessible web location. Direct links differ based on distribution used; see the relevant Rapid Recovery Agent installation package. For assistance, please contact Quest Data Protection Support. Component NBD (various versions) uses the GNU General Public License 2.0, which can be found in Rapid Recovery's Third-Party Components link within in-product help. The copyright attributions there are accurate and complete. |
|
![[Help icon]](/ko-kr/technical-documents/image/70570a3f-8559-43ba-8646-b6fee7c1513e "Help")
Help icon for the License Details Core setting, a generic error message appears.Go to the top of the Known issues topic.
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
| 107984 | When installing Rapid Recovery Agent on a Linux machine, minor misspellings appear on the command line for firewall settings. | No workaround at this time. The text "Configured manualy. May be reconfigured…" is expected to be changed to "Configured manually. This may be reconfigured...". | Linux, Agent installation |
Go to the top of the Known issues topic.
Table 5: Local Mount Utility known issues
| Issue ID | Known Issue Description | Workaround | Functional Area |
|---|---|---|---|
| 108540 | Toast pop-up notifications appear outside of the Local Mount Utility application window/frame. | No workaround at this time. | Notification |
| 107756 | Tthere is no ability to set Core Connection Timeout using the LMU UI. | You can set the Core Connection Timeout using the Windows registry using key CoreConnectionTimeout. For more information, see Quest Knowledge Base article 210006. | LMU, Connection timeout |
| 110364 | [LMU] There is no ability to open Exchange databases for ESXi agentless VMs due to error database does not exist |
Go to the top of the Known issues topic.