Chat now with support
Chat with Support

Rapid Recovery 6.1.3 - Release Notes

Resolved issues

Customer-facing issues resolved in this release are listed below.

Table 1. Central Management Console resolved issue

Resolved Issue Description

Issue ID

Functional Area

Was unable to authorize to Central Management Console on a single customer environment due to specific configuration of domain controller, groups and accounts.

101227

Authentication

Table 2. Core and Windows resolved issues

Resolved Issue Description

Issue ID

Functional Area

The Dismiss All button on the Event page for a protected machine removed all alerts for the Core instead of for the specific machine.

103386

Events

After executing the Get-UnprotectedVolumes PowerShell command for specific machines, protected volumes displayed instead of unprotected volumes.

103302

PowerShell

A CIFS repository went offline at random times dues to multiple connections.

103240

Repositories

The Core certificate contained two Common Names (CNs) hostname/localhost inside the issuer, instead of one CN hostname.

103233

Certification

A Core certificate with one CN hostname was not secure in Chrome 58.

103303

Certification

Archive compression speed for archives saved in 6.1.x decreased by as much as 50% over the speed attained in AppAssure release 5.4.3.

103229

Archive

The compression ratio of archives was too small after an upgrade from AppAssure 5.4.3 to Rapid Recovery 6.1.2.

103212

Upgrade

Retention policy logic does not account for specific cases that could result in skipping generation of a monthly recovery point during rollup. For example, when an error occurs during capture of an incremental snapshot, or if nightly jobs runs over and causes rollup not to run, then when the rollup policy enforces the logic to keep one recovery point per month, in rare cases, the monthly recovery point may not be created. This is as designed.

103165

Retention policy

If a Hyper-V Cluster was agentlessly protected, the Core System Events logs were spammed by a "DCOM" error.

103021

Agentless protection

The archive recycle actions "Erase completely" and "Replace this Core" did not function correctly.

102803

Archive

Repository mount failed with error, "Failed to mount repository because it is currently in use by another Core," because the damaged/not valid dfs.mbr file was not rewritten after a Repository Check job.

102719

Repositories

ESXi export job failed with permissions error for a protected machine that has disks with identical UUIDs.

102685

ESXi export

Base images were taken instead of incrementals for a volume with Hyper-V virtual disk files on a Windows Server 2016 Hyper-V protected machine.

102617

Hyper-V protection

Disks and volumes were not detected for VMs protected agentlessly if FIPS 140-2 protocol was enabled on Core.

102508

Agentless protection

Core could not create a DVM repository greater in size than 16TB when write caching was enabled.

102507

DVM repository

When using replication, the Core could not consume a seed drive named "AABackup."

102506

Replication, seed drive

In a unique environment, replication transferred all data instead of incremental because 'Recalculate deduplication cache for repository' failed. In the specific environment, this behavior is as designed.

102297

Replication

Local Hyper-V export failed on Windows Server 2016 with error: "WMI class "MsvmVirtualSystemGlobalSettingData" or error "properties in class 'MsvmVirtualSystemGlobalSettingData' was not found."

102223

Virtual export

Hyper-V agentless protection for all nodes in a cluster failed with error: "Unrecognized Guid Format" due to the specific state of a VM hosted on a cluster.

102221

Hyper-V agentless

Checking archive job was canceled if storage was corrupted, instead of failing with appropriate informative error.

102207

Archiving

For replicated protected machines, the nightly job setting for 'Check recovery points integrity' set to default (enabled) even if the setting on the source was changed to disabled before replicating.

102105

Replication

If you tried to perform a one-time export of a recovery point on a protected machine to Azure, errors appeared when you tried to specify a new cloud service name in the Deploy page of the Virtual Machine Export Wizard. The error was "Object reference not set to an instance of an object."

101819

VM export

There was no warning message that rollup was not performed for recovery points on a seed drive that had not yet been consumed. This was only relevant for environments that used replication with an outstanding seed drive.

35823

Replication

If a USBB device was connected to the Core machine and went into an unknown B state, the error "Failed to call Create File on disk '\\.\PhysicalDrive' - The specified network resource or device is no longer available" displayed and blocked the GUI, because the Core could not gather metadata.

35765

Protection

If a user tried to mount a volume with the single-instance storage (SIS) feature on the volume, even if the feature was disabled and a new base image was taken, the error "The current OS does not support Single Instance Storage and cannot be used to mount volumes" displayed and the volume would not mount.

35718

Mounting

Specific volumes were not mounted after virtual export of Linux machine. This defect applied only to customers with LVM volumes on an iSCSI Dell EqualLogic machine.

35288

Virtual export (ESXi)

During a repository check, the status for a repository appeared on the Core Console Home page as red.

34904

Repositories

Table 3. DL Appliance resolved issues

Resolved Issue Description

Issue ID

Functional Area

In a specific customer environment, the Provisioning appliance page was unavailable, with an error: "CIM Chassis error" due to a storage pool that referenced an enclosure that did not exist.

102495

GUI

User could launch several remount jobs simultaneously on DL Appliance.

102322

Storage Provisioning

FTBU failed when trying to start a Core service that was already in a "Starting" state.

101554

FTBU

There was an incorrect default value of Repository name field on the Add New Repository Wizard.

101348

Storage Provisioning

If the server was rebooted during FTBU, then the Compatibility Mode of the browser prevented the first launch of the Core after FTBU from performing successfully.

101313

FTBU

RASR failed to start with fatal exception on DL1300 and DL4300 with new ID modules.

101051

Storage Provisioning

If a repository name contained three dots in a row, the provisioning job failed with an error and the repository was not created.

100913

Provisioning

Parameters in 'Expand Existing Repository' pop-up did not reflect true available space for repository expansion on internal controller on DL1300 after upgrade via RUU#3.1.

100908

Windows Backup

Storage Provisioning and Restore the Provisioning Configuration jobs could be launched simultaneously in spite of incompatibility for launching of these jobs.

100907

Storage Provisioning

RASR USB could not be created on the server after upgrade using RUU if server was restored from Windows backup.

100905

Storage Provisioning

Core interface became unavailable if forced to collect Core and Appliance logs.

100904

RASR

The LSI Provider installation failed if the User Policy was set to Restricted.

99997

RUU

RUU hung after several double-clicks on the RUU window.

98537

RUU

Monitor Active Task hung at 95% during creation of RASR USB job.

35531

Storage Provisioning

Job "Restore the provisioning configuration" failed on a specific environment.

35137

RASR

Sometimes error "invalid state; already open" appeared on the Virtual Standby page for DL4x00 Appliances.

31477

Storage Provisioning

Table 4. DocRetriever resolved issue

Resolved Issue Description

Issue ID

Functional Area

DocRetriever did not restore the "Content Editor" web parts in SharePoint 2013.

103241

Restore

Old documents are not overwritten after a restore with the options "Merge containers" and "Overwrite" selected.

102616

Restore

Table 5. Documentation resolved issue

Resolved Issue Description

Issue ID

Functional Area

Context-sensitive help found in-product for Rapid Recovery Core was re-branded as of release 6.1.2 to reflect its ownership by Quest Software. Other than rebranding, no content changes appeared for help files in that release.

70130

Context-sensitive help

Table 6. Kaseya Add-On resolved issues

Resolved Issue Description

Issue ID

Functional Area

In some cases, credentials for Cores and Agents in the Kaseya Server were stored in unencrypted text in the AppRecoveryParams.json file.

102096

Authentication

Table 7. Linux resolved issues

Resolved Issue Description

Issue ID

Functional Area

Was unable to protect an Ubuntu Linux Agent if it contained a "non fs data" partition type.

102284

Metadata

Table 8. Local Mount Utility resolved issues

Resolved Issue Description

Issue ID

Functional Area

For mounted recovery points on a Windows Server 2016 machine, the "Explore" button was disabled.

101860

Mounts

Table 9. Mailbox Restore resolved issues

Resolved Issue Description

Issue ID

Functional Area

When Mailbox Restore loaded mailboxes from an Exchange 2016 CU5 database, the error "Property Blob version is invalid" displayed.

102696

Exchange databases

The "From" field incorrectly contained Asian characters in the message preview.

102586

Localization

MailboxRestore could not restore a message containing emoticon symbols such as unamused face (ASCII symbol "😒").

102360

Restoring

Known issues

The following is a list of customer-facing issues, including those issues attributed to third-party products, known to exist at the time of release.

Table 10. Core and Windows known issues

Known Issue Description

Issue ID

Functional Area

After an upgrade from release 6.1.1 to release 6.1.2 on an environment with a specific security policy, the Core Console does not open.

Workaround: Complete the following steps:

103783

GUI

In the Spanish translation of the product, agentless virtual machines (VMs) do not display on the Virtual Machines page.

Workaround: To view the VMs, change the language of the Core from Spanish to another language in the Core Settings.

103782

GUI

The Agent service on a cluster may crash when attempting to collect SQL metadata of a database with the FileAttributes.ReparsePoint attribute.

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

103740

Agent

A queued replication job begins after the scheduled start time has passed.

103702

Replication

The ability to restore ReFS volumes fails for Windows Server 2016.

Workaround: Move the existing repository to a Windows 2012 or Windows 2012 R2 operating system, and then perform the restore.

103698

Restore

There is no ability to add a new cloud account to the Azure Government cloud.

Workaround: None.

103683

Azure

The Core exhibits poor performance and high system resources usage when mounting a recovery point from an attached Azure archive.

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

103670

Azure

MongoDB cannot connect to the Rapid Recovery servers due to an insufficient quantity of available ports.

Workaround: None.

103664

Connectivity

It is possible to restore a recent Core configuration with a backup of an outdated Core version.

Workaround: None.

103632

Core

The setting for maximum concurrent exports does not enforce the limitation if the setting is changed to '1' while two or more exports are in progress.

Workaround: None.

103515

Core settings

During a successful repository check, a 'Placeholder mismatch' error displays in the Phase area of the Monitor Active Task details of the job.

Workaround: None.

103492

Repository check

ESXi export fails when the Quest NetVault Backup with BMR plugin is installed on the same machine as the Rapid Recovery Core.

Workaround: Complete the following steps:

103477

Virtual export

If the dedupe cache is on a disk with a sector size of 4KB, resizing the dedupe cache fails with the error "cache_io_engine: windows error 87."

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

103469

Repository

Agentless protection of an ESXi VM fails with the error "An item with hthe same key has already been added" for the vCenter server.

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

103426

Agentless

The Dashboard Transfer Job widget does not track jobs that expire while queued.

Workaround: None.

103412

Reporting

A Core set to display in Portuguese fails to communicate with the license portal, because the DateTime was not recognized.

Workaround: Set the Core to another language.

103371

Licensing

The error message "The specified display name is already in use by another agent" displays during agentless protection if the VM exceeded the maximum number of permitted snapshots.

Workaround: Delete snapshots for the VM so that it has fewer than the maximum number of snapshots allowed.

103334

Protection

Transfer failed due to the absence of retries during the CleanupSnapshotInternal stage of the transfer during a brief network outage.

Workaround: Attempt another backup.

103310

Transfers

A Core certificate with on CN (Common Name) hostname is not secure in Chrome 58.0.

Workaround: Use a different browser.

103303

Security

When a scheduled archive is set with the option "Include only the recovery points in the date range ...," a base image is archived.

Workaround: There is no workaround for this issue at this time.

103283

Archiving

A DVM repository stored on a Common Internet File System (CIFS) shared volume randomly goes offline with error: "Multiple connections error occurred while trying to map share."

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

103240

Repository

When database files are located on a quorum disk for a protected SQL Server cluster, log truncation does not occur, with error: "SQL log truncation for the protected has been skipped, because there aren't any SQL databases in protection group."

Workaround: Move the SQL Database on a different volume. Alternatively, schedule SQL log truncation separately using a post-transfer script or a scheduled job.

103225

SQL log truncation

Archives created in Rapid Recovery Core releases 6.0.2 and later have lower performance than archives created in earlier releases, relative to both speed and compression ratio. Not a defect in 6.0.1. This defect first appeared in release 6.02, and recurs in releases 6.1.0, 6.1.1, and 6.1.2.

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

103212

Archive

Deploy to Azure fails if you specify a cloud service name in Fully Qualified Domain (FQDN) format.

Workaround: Specify service name using hostname format.

102756

Azure

The export postprocessing step can sometimes take a long time to complete the dismount operation.

Workaround: Increase the protection interval.

102742

Exporting

Sometimes there is no ability to protect a cluster with the same hostname as a protected cluster from a different domain.

Workaround: Complete the following steps:

102702

Protection

Incremental Virtual Standby Hyper-V export fails if the location or name of the exported VM includes Chinese symbols.

Workaround: Replace the Chinese symbols with English characters in the location and name of the exported VM.

102589

Virtual export

The following warning about a nonexistent writer on a SQL Server or Exchange protected machine displays during log truncation: VSS full snapshot was taken with excluded VSS writers "Microsoft Exchange Writer has state" error.

Workaround: Ignore the warning, as it does not prevent the truncation job from completing.

102567

Log truncation

Slow incremental images are captured for volumes with specific write activity.

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

102493

Backups

Deferred delete cancels after rollup job when localization is set to a French OS.

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

102436

Localization, deletion

Sometimes the drive letters of an exported machine do not match the drive letters of the source machine.

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

102390

Virtual export

On the Recovery Points page of the Core Console, users are unable to navigate multiple pages of recovery points by using a menu.

Workaround: Use existing navigation.

101736

UI

Seed drive job fails with error: "Write data task has failed."

101617

Replication

When Secure boot option is enabled on Windows Server 2016, installation of some drivers are blocked during Agent installation, displaying error: "The transfer failed."

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

101573

Installer

After a few weeks, VM export fails. TCP/IP event 4227 appears in system log, with message "TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint." This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection.

Workaround: Temporarily increase dynamic port range, and restart the server periodically.

101485

Virtual export

ESXi Virtual Standby fails with error: "An entry with the same key already exists" on a system test environment.

100868

Virtual export

"Maximum connection pooling size" and "Minimum connection pooling size" fields for the MongoDB connection are not validated, allowing users to set a maximum value below the minimum value.

Workaround: Set a "Minimum connection pooling size" value that is less than the "Maximum connection pooling size" value.

35607

Core settings

A base image is captured instead of an incremental image on a Windows Server 2012 R2 protected machine when NTFS Boot Sector copy was changed. This defect only affects users who installed third-party software that changed in the NTFS Boot Sector copy.

Workaround: None.

34981

Backups

Unexpected base images captured in ESXi VMs that have snapshots with quiescing enabled. Defect affects users who protect vCenter virtual machines that have SAN snapshots with quiescing enabled. Workaround: Disable quiescing.

34916

Virtual export

Virtual standby performance is slow when performing export of multiple concurrent protected machines (for example, 36).

Workaround: Decrease the number of concurrent export jobs allowed.

34434

Virtual export

Warning message: "Information about allocated space for some volumes is unavailable... " displays on the Summary page for a protected machine if the VM is located on a Network File System (NFS) datastore.

Workaround: None. This is a limitation of VMs stored on an NFS datastore.

33551

Summary information

Replication rate becomes extremely slow if a virtual export job is started concurrent to the replication job.

Workaround: Use schedule to avoid replication and export run simultaneously.

33230

Virtual export, replication, resource consumption

When archiving 2 or more jobs simultaneously, if the target network storage device runs out of space, all running archive jobs fail with error: "There is not enough space on the disk."

Workaround: Create different schedules for running each archive so that the archives do not run simultaneously in the network share.

31827

Archiving

After virtual export of a WinXPx86 machine protected agentlessly, or virtual export of any machine protected on an ESXi host, the resulting VM is not bootable. Issue relates to controller drivers for SCSI and IDE controllers not present in the exported VM.

Workaround: None.

31705

Virtual export

After virtual export of RHEL 6 or 7 with the LVM or RAID volumes and more than eight HDDs from an ESXi host, the resulting VM is not bootable.

Workaround: To let the export be created with all disks on one single disk controller and let the machine boot successfully after export, use less than nine disks on one disk controller.

31277

Virtual export

ESXi agentless restore or virtual export using SAN transport mode fails with the error, "One of the parameters was invalid."

Workaround:Use Network Transport mode for restoring data.

29508

VMware agentless, restoring data

If using auto disk mapping for VM export from ESXi, in rare cases an error occurs with an uninformative message: "Task 'ReconfigVM_Task' failed: Invalid configuration for device '0'."

Workaround: Try the operation again and it should succeed.

27309

Virtual export

Table 11. DL Appliance known issues

Known Issue Description

Issue ID

Functional Area

After a factory reset, the Core may fail to restore the configuration for some services during the Remount Volumes job, but the Core shows the job as being successfully completed.

Workaround: Perform another Remount Volumes job.

104043

Restore

The MongoDB service cannot establish a connection to the Core, because there are not enough available ports.

Workaround: None.

103664

Connection

Sometimes "Internal Server Error" appears on Backup page.

Workaround: Ignore and close the error message.

102379

Storage Provisioning

After an upgrade to release 6.1.2, repository maintenance failed after a restore of the provisioning configuration.

Workaround: Contact Support.

102340

Windows Backup

Remount job does not restore Core's localization.

Workaround: Manually change Core localization from Core Settings.

101316

Storage Provisioning

Jobs are failing with error: "System.OutOfMemoryException" on DL Appliances after running for some time.

Workaround: Install the latest Windows updates and reboot the appliance. If this problem persists, contact Support.

101246

Storage Provisioning

Statuses of volumes are displayed as 'Not valid' if a letter is assigned to 'Recovery' partition.

Workaround: Wait until the RASR USB creation job completes or, if the driver letter was manually assigned to the Recovery partition, remove the drive letter.

101224

Virtual Export

Windows Backup failed when necessary volume letters were changed.

Workaround: Remove current policy with mixed/changed letters for partitions and create a new policy with heterogeneous volume labels.

100985

RASR

Main Appliance status receives a red state without the ability to resolve if Windows Backup was forced on the server with old Winbackups with volume size of 75GB and without free space on Internal controller.

Workaround: Clear the Windows Backup logs as follows: 1) Open event viewer. 2) Go to Applications and Services Logs. 3) Navigate under Microsoft -> Windows -> Backup. 4) Right click on the Operational channel and select Save and Clear (or, if you don't want to save, select Clear).

100887

UI

Restore the provisioning configuration job fails with an uninformative error: "Cannot mount volume to the folder 'I:\' because it contains files or folders" if the virtual disk has a letter assigned that was already used before remount.

Workaround: Remove assigned letters from attached virtual media via disk manager. Perform Volumes Remount job again from Appliance Provisioning page.

35805

Provisioning

Incorrect behavior of provisioning size determining logic.

Workaround: When performing provisioning, specify the intended sizea few GB smaller than the available space.

35770

Windows Backup

VMM actions are available when ESXi host is in maintenance mode.

Workaround: Do not perform any VM operations from the Virtual Standby page if an ESXi host is in Maintenance mode.

35740

Storage Provisioning

The GUI should be disabled immediately after confirmation of the remount process.

Workaround: Wait for a few minutes and refresh Core Console page.

35579

Virtual Machine Management

On the Backups page, incorrect translation of 'State' appears in the 'Items Baced Up' section for some non-English language.

Workaround: None.

35031

Storage Provisioning

VD disk provisioning fails with return code 4 if storage pool does not have consistent empty space.

Workaround: Contact Support.

34937

Localization

"Start VM / Network Adapters" buttons remain enabled when an ESXi or Hyper-V export of a machine is launched on DL Appliances.

Workaround: Do not click these buttons until the corresponding VM export is complete.

30989

Virtual Machine Management

Table 12. DocRetriever known issues

Known Issue Description

Issue ID

Functional Area

DocRetriever fails to open a SharePoint 2016 database when several sites have a similar identifier.

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

103710

Databases

DocRetriever restore operations fail on 32-bit versions of Windows operating systems due to the absence of a necessary registry key.

Workaround: On the protected machine, manually create the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NETFramework\AssemblyFolders\SharePoint.

102522

Restore

Table 13. Documentation known issues

Known Issue Description

Issue ID

Functional Area

The components ANTLR 3.3.3 and ANTLR 4.0.2 appear in the list of third-party components found in the product, even though they were not used in Rapid Recovery 6.1.3.

Workaround: The component will be removed from the Third-Party Contributions list in a future release.

104031

Context-sensitive help

The component MongoDB 2.6 appears in the list of third-party components found in the product, even though it was not used in Rapid Recovery 6.1.3.

Workaround: The component will be removed from the Third-Party Contributions list in a future release.

104030

Context-sensitive help

The component Microsoft Windows Azure Storage 7.2.1 does not appear in the list of third-party components found in the product. An outdated version of the component appears in its place.

Workaround: Microsoft Windows Azure Storage 7.2.1 uses the Apache 2.0 license, which can be found in the Third-Party Contributions list in the in-product Help and hyperlinked from the About Rapid Recovery page.

102504

Context-sensitive help

The component DataGridViewImageAnimator 1.0 appears in the list of third-party components found in the product, even though it was not used in Rapid Recovery 6.1.3.

Workaround: The component will be removed from the Third-Party Contributions list in a future release.

102503

Context-sensitive help

The component SimpleRestServices 1.3.0.3 does not appear in the list of third-party components found in the product. An outdated version of the component appears in its place.

Workaround: SimpleRestServices 1.3.0.3 is used in Rapid Recovery 6.1.3. The component uses the MIT N/A license. A copy of this license can be found at http://quest.com/legal/third-party-licenses.aspx.

102502

Context-sensitive help

The component OpenStack.NET 1.4.0.2 does not appear in the list of third-party components found in the product. An outdated version of the component appears in its place.

Workaround: OpenStack.NET 1.4.0.2 was used in Rapid Recovery 6.1.3. The component uses the MIT N/A license. A copy of this license can be found at http://quest.com/legal/third-party-licenses.aspx.

102501

Context-sensitive help

The component NLog 3.2.1 does not appear in the list of third-party components found in the product. An outdated version of the component appears in its place.

Workaround: NLog 3.2.1 was used in Rapid Recovery 6.1.3. The component uses the BSD - Kowalski 2011 license, Copyright (c) 2004-2011 Jaroslaw Kowalski <jaak@jkowwalski.net>. A copy of this license can be found at http://quest.com/legal/third-party-licenses.aspx.

102500

Context-sensitive help

The component AWS SDK for .NET 3.3.1.2 does not appear in the list of third-party components found in the product. An outdated version of the component appears in its place.

Workaround: AWS SDK for .NET 3.3.1.2 uses the Apache 2.0 license, which can be found in the Third-Party Contributions list in the in-product Help and hyperlinked from the About Rapid Recovery page.

102499

Context-sensitive help

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

Workaround: When following this procedure, disregard Steps 4 through 8. The step currently numbered Step 9 should start with "On the Destination page...".

101859

Azure export

The Rapid Recovery User Guide procedure "Setting up continual export to Azure" for release 6.1.x contains unnecessary steps. 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. 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 User Guide.

Workaround: If you create a container from the Virtual Machine Export Wizard, 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. Future versions of documentation are to be modified accordingly.

101853

Azure export

When performing virtual export to Azure, the Rapid Recovery Core 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 User Guide procedure "Creating a container in an Azure storage account" for release 6.1.x does not specify that the Classic management model is required. Future versions of documentation are to be modified accordingly.

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

Table 14. Linux protection known issues

Known Issue Description

Issue ID

Functional Area

After a successful virtual export, a machine running Debian 7.11 with a root on a RAID does not start.

Workaround: Complete the following steps:

103558

Virtual export

Protection of volumes created with LVM-based storage pools fails.

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

103488

Protection

Transfer from Core failed on SLES 11.4 x32 with the error, "The partition size is incorrect, please shrink the volume."

Workaround: Use a different release of SLES or a different Linux distribution.

103300

Transfers

It is possible to select Linux system folders for a rollback restore.

Workaround: None.

103178

Restore

Unable to use Transport Layer Security (TLS) 1.2 protocol with Linux Agent.

Workaround: Disable TLS 1.0 and/or SSL3.

101279

Security

There is no warning message indicating that the Agent service cannot be started if it was installed on a Linux machine using an init system other than the originally installed system. For example, Debian 8 uses SysD by default. If SysD is removed and SysV installed, the Agent does not start.

Workaround: No workaround is required since the defect only describes the absence of a notification.

35818

Notifications

Agentlessly protected Ubuntu machine is not bootable after BMR.

Workaround: Use the Rapid Recovery Agent on Ubuntu instead of using agentless protection.

31206

BMR bootability

Table 15. Mailbox Restore known issues

Known Issue Description

Issue ID

Functional Area

The MAPI dialog does not display during a restore if the Exchange server uses a self-signed certificate, which causes the restore to fail.

Workaround: Add the certificate to local storage of trusted certificates on local machine by clicking "View Certificate," and then "Install Certificate" when the dialog displays.

102765

Security

During restore of permissions for a public folder, an uninformative error message displays if user was not found in the Global Address List.

Workaround: No workaround is required since the defect only describes an error message which can be ignored.

102018

Restoring

Rapid Recovery system requirements

This section describes the system and license requirements for installing the Rapid Recovery Core, Rapid Recovery Agent, and Rapid Recovery Central Management Console.

Recommended network infrastructure

For running Rapid Recovery, Quest requires a minimum network infrastructure of 1 gigabit Ethernet (GbE) for efficient performance. Quest recommends 10GbE networks for robust environments. 10GbE networks are also recommended when protecting servers featuring large volumes (5TB or higher).

If multiple network interface cards (NICs) are available on the Core machine that support NIC teaming (grouping several physical NICs into a single logical NIC), and if the switches on the network allow it, then using NIC teaming on the Core may provide extra performance. In such cases, teaming up spare network cards that support NIC teaming on any protected machines, when possible, may also increase overall performance.

If the core uses iSCSI or Network Attached Storage (NAS), Quest recommends using separate NIC cards for storage and network traffic, respectively.

Use network cables with the appropriate rating to obtain the expected bandwidth. Quest recommends testing your network performance regularly and adjusting your hardware accordingly.

These suggestions are based on typical networking needs of a network infrastructure to support all business operations, in addition to the backup, replication, and recovery capabilities Rapid Recovery provides.

Related Documents