Rapid Recovery 6.1.2 - Release Notes

Deprecated in this release

This section includes a list of features, items, or related components that are deprecated in Rapid Recovery release 6.1.2.

Microsoft Exchange Server 2007 SP1 Rollup 5 deprecated

Microsoft ended extended support for Exchange Server 2007 on April 11, 2017, based on their support lifecycle policy.

Quest tested Exchange Server 2007 SP1 Rollup 5 with Rapid Recovery release 6.1.2, and found no issues. Thus, limited support for this version of Exchange Server is provided to customers with a support agreement for release 6.1.2. Testing of this version of Exchange with Rapid Recovery 7.0.0 is also planned, and it will be supported in that release.

However, this version of Exchange Server is deprecated, and support will be discontinued in a future release of Rapid Recovery. Customers using Rapid Recovery to back up Exchange Server 2007 SP1 are advised to plan and implement an update to an Exchange Server version that is supported by Microsoft.

Resolved issues

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

Table 1. Core and Windows resolved issues

Resolved Issue Description

Issue ID

Functional Area

After upgrading version 5.4.3 or 6.0.x of the Agent software on a machine running Windows Server 2012 R2 or Windows Server 2016, a base image was taken instead of an incremental snapshot.

102561

Upgrading

In a case of replication failure, data that successfully replicated before the moment of failure was cleared from the staging area (target), which forced the next replication job to start over from the beginning instead of resuming from the point where the failure occurred.

102578

Replication

Mount for volumes with ReFS file system did not work on Windows Server 2016.

102437

Mounting

Requesting deletion of the same snapshot two or more times in a specific sequence in a DVM repository sometimes introduced data inconsistencies, and spammed the Core log with the error: 'unmanagedDvm.storageSubsystem.'

102286

Repository

After implementing white labeling, the Volume page was empty for agentlessly protected VMs.

101891

Volumes page

When performing mountability checks on protected Exchange servers with large databases or servers under heavy load, gaps sometimes occurred between child jobs, which led to degradation of performance on the server, with some check jobs lasting hours.

101797

Exchange server checks

For customers on DL series backup and recovery appliances only, after running RUU 3.0.587 or newer, when opening the Appliance tab, some users experienced the sporadic error: "No instances of 'CIM_ComputerSystem' have been found." DL users experiencing this problem should upgrade to release 6.1.2.

101752

DL

The Reports PowerShell script did not execute due to the relocation of a contract during refactoring. The code was updated to resolve.

101678

PowerShell

Arcserve Unified Data Protection software was not identified as an incompatible product.

35798

Validation

Export rate was slow for recovery points from repositories that have high fragmentation.

34758

Virtual export, Repository

In the Add New Account dialog, there was no area for entering the service endpoint for an S3-compatible cloud account.

35736

Archiving

Archive to Amazon failed with error "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256" for buckets in Ohio, Mumbai and Seoul regions.

35733

Archiving

Korean translation in replication schedule settings was incorrect.

35726

Internationalization, replication

The 'State' column had the wrong translation on the Encryption Keys page for the Korean locale.

35716

Internationalization, encryption

In the Rapid Recovery software development kit, the AppRecoveryAPI sample AddClusterUnderProtectionSample did not work.

35694

SDK

Virtual export failed with the error "No physical extents have been found for cluster offset '19626746' cluster length '520.' Extent disk #'1' LCL '19627264' LCF '0' PSF '264192'" after specific steps.

35626

VM export

In the Settings page of the Core Console, validation in the client timeout fields sometimes worked incorrectly, showing the error "Uncaught Error."

35572

GUI, Core settings

In the Korean translation of the user interface, the Pause button showed the incorrect translation of Incorrect Korean translation of Pause button. instead of Correct Korean translation of Pause button..

35557

Localization, pausing protection

On the Schedule page of the Archive wizard, the tooltip text was wrong in all translations.

35556

Localization, Scheduled archive

In the Protect Machine wizards, the "Encrypt data using Core-based encryption with an existing key" option was highlighted when it was not selected.

35554

Protection, GUI

Volumes were not available after a recovery point from an attached archive created from an agentless Windows Server 2008 R2 protected machine was mounted as Writable.

35542

Archiving, Agentless protection

The email notification template reverts to the default after the Core service restarts.

35483

Email notifications template, GUI

Replication to a second target Core did not start if volumes were missing from the source Core.

35358

Replication

On a specific environment, the GPT volume on an agentlessly protected virtual machine could not be opened from a mount point mounted in Read-only mode.

35100

Agentless protection

When searching all transfer events using the Transfer Job per Machine widget (on the Core Console in dashboard view), the text string 'Transfer' was not translated.

34774

Localization

On the Events page and the Delete Recovery Points Range window, the date and time pickers worked incorrectly until users refreshed the page.

34347

Events, GUI

Disk metadata size skews progress tracking during archive. For example, if there are many databases on a volume, the progress bar stays at 1% for too long, then speeds up.

32044

Archiving, Metadata

Could not open databases from recovery points when the logs and data files were located in different directories.

23285

Recovery, application support

Table 2. DocRetriever for SharePoint resolved issues

Resolved Issue Description

Issue ID

Functional Area

DocRetriever Agent did not work on a machine with Microsoft Office SharePoint Server 2007 (32-bit) installed.

102522

Restoring

When retrieving list items from a SharePoint 2010 database, restore was not possible if the stored value is a character disallowed in XML.

102062

Restoring

The error "Cannot find the original destination..." appears after trying to perform an in-place restore of a site from the "Farm" backup.

35614

Restoring

Table 3. Linux resolved issues

Resolved Issue Description

Issue ID

Functional Area

The packages-downloader script could not download mono package for Debian 8 due to a broken link that has subsequently been fixed.

102366

Debian 8

Users who had 'safenet' encrypted file partitions were unable to protect Linux machines using the Rapid Recovery Agent.

35226

Protection

Table 4. Local Mount Utility resolved issues

Resolved Issue Description

Issue ID

Functional Area

Volume image with enabled Data Deduplication (Windows Server 2012 feature) could not be mounted.

101472

Mounting

If the user tried to retrieve RPs for several Agents in the LMU, the "Connecting in progress … ” progress bar hung.

100635

GUI

Table 5. Mailbox Restore resolved issues

Resolved Issue Description

Issue ID

Functional Area

Messages from an archive mailbox were restored to the user's usual mailbox after restoring to the original location.

35654

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 6. Central Management Console known issue

Known Issue Description

Issue ID

Functional Area

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

Workaround: None. This issue is not expected to recur unless exact circumstances are duplicated.

101227

Authentication

Table 7. Core and Windows known issues

Known Issue Description

Issue ID

Functional Area

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

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.

Workaround: None.

103229

Archive

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 as soon as it is available.

103212

Archive

Validation is not present to restrict users from selecting Linux system folders as destinations for standard restore, resulting in error: "System.ApplicationException: We do not support rollback to system folders at [destination]."

Workaround: Use standard procedures to restore a non-system volume or perform a virtual export. To restore the system volume (for Linux or Windows machines), perform a bare metal restore, as documented in the Rapid Recovery User Guide.

103178

Restore, validation

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 run over and cause 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.

Workaround: If the cause is skipped rollup, workaround is to change the work that delays rollup from occurring.

103165

Retention policy

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

Workaround: Disable FIPS 140-2 or contact Support for assistance.

102508

Agentless protection

Core cannot create a DVM repository greater in size than 16TB when write caching is enabled.

Workaround: Create several 16TB or smaller storage locations in a single repository.

102507

DVM repository

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

Workaround: The folder name AABackup is reserved. If you specified the name AABackup for your seed drive, rename it to another value that does not include prohibited characters or phrases, as described in the glossary for the Rapid Recovery User Guide.

102506

Replication, seed drive

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

Workaround: Contact Support for a custom binary that addresses this situation.

102493

Backups

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

Workaround: Contact Support for a custom binary that addresses this situation.

102436

Localization, deletion

Sometimes exported machines use different drive letters than the source machines. Implement functionality to assign drive letters to exported machines that are identical to the drive letters associated with the original source machine.

Workaround: Contact Support for a custom binary that addresses this situation.

102390

Virtual export

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

Workaround: No workaround for local hyper-v server. Remote hyper-v export works as expected.

102223

Virtual export

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

Workaround: Contact Support and request the custom binary that addresses this issue.

102221

Hyper-V agentless

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

Workaround: None.

102207

Archiving

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

Workaround: None.

102105

Replication

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

Workaround: Directly from your Azure account, create the cloud service in the same resource group as your other resources, using the Classic management model. Then, from the wizard in the Core, specify the existing cloud service name.

101819

VM export

On the Recovery Points page of the Core Console, users would benefit from adding a menu for switching between the pages.

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."

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

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

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

35823

Replication

"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 appropriate values.

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: There is no workaround.

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

When searching all transfer events using the Transfer Job per Machine widget (on the Core Console in dashboard view), the text string 'Transfer' is not translated.

34774

Localization

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: There is no workaround. 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: There is no workaround at this time.

31705

Virtual export

After virtual export of RHEL 6 or 7 from an ESXi host, the resulting VM is not bootable.

Workaround: None.

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 8. DL Appliance known issues

Known Issue Description

Issue ID

Functional Area

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

Workaround: Contact Support and request the custom binary that addresses this issue.

102495

GUI

Sometimes "Internal Server Error" appears on Backup page.

Workaround: Ignore and close the error message.

102379

Storage Provisioning

Repository maintaining failed after the restore provisioning configuration after upgrade to 6.1.2.

Workaround: Contact Support.

102340

Windows Backup

User can launch several remount jobs simultaneously on DL Appliance.

Workaround: Do not launch remount job several times until you ensure that no other jobs are running. If you experience this issue, please contact Quest Support to remount repository.

102322

Storage Provisioning

Incorrect default value of Repository name field on the Add New Repository Wizard.

Workaround: Manually enter Repository name that fits the field validation rules.

101348

Storage Provisioning

Remount job does not restore Core's localization.

Workaround: Manually change Core localization from Core Settings.

101316

Storage Provisioning

ESXi virtual exports start to fail with error: "System.OutOfMemoryException" on DL Appliances under heavy load after several days.

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

101246

Virtual export

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.

101224

Virtual Export

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

Workaround: Contact Support.

101051

Storage Provisioning

Windows Backup could not be created due to inappropriate determining of necessary volume items for backup if letters for volumes were changed.

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

100985

RASR

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

Workaround: Expand repository from Repository configuration page.

100908

Windows Backup

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

Workaround: 1) Remove created Repository 2 Virtual Disk using OMSA. 2) Restart Core service.

100907

Storage Provisioning

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

Workaround: Perform RASR restore from the following places: 1) Previously created RASR USB; 2) RECOVERY partition by pressing F8 during POST; 3) RASRdisk virtual disk; 4) IDSDM (DL4300 only).

100905

Storage Provisioning

Core interface becomes unavailable if force collecting Core and Appliance logs.

Workaround: Refresh page to make GUI available again

100904

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

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

Workaround: Refresh the GUI. Typically, the job completes successfully, but in some cases does not reflect the correct status until you refresh the GUI.

35531

Storage Provisioning

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

Workaround: Detach all physical and virtual media from server before performing "Restore provisioning" operations.

35137

RASR

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

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

Workaround: Close the error message. If the issue persists, reload page by clicking F5.

31477

Storage Provisioning

Start VM / Network Adapters buttons should be all in disabled state if ESXi/Hyper-V export of machine was launched on Appliances. Workaround: Do not click these buttons until the corresponding VM export is complete.

30989

Virtual Machine Management

Table 9. Documentation known issues

Known Issue Description

Issue ID

Functional Area

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.2.

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.2. 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.2. 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.2. 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

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

70130

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 10. Kaseya Add-On known issues

Known Issue Description

Issue ID

Functional Area

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

102096

Authentication

Table 11. Linux protection known issues

Known Issue Description

Issue ID

Functional Area

Unable to protect an Ubuntu Linux Agent if it contains a "non fs data" partition type.

102284

Metadata

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

Workaround: Disable TLS.

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

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

Workaround: There is no workaround at this time.

35288

Virtual export (ESXi)

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 12. Local Mount Utility known issues

Known Issue Description

Issue ID

Functional Area

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

Workaround: Use Windows Explorer to find data in mounted recovery points.

101860

Mounts

Table 13. Mailbox Restore known issues

Known Issue Description

Issue ID

Functional Area

MailboxRestore cannot restore a message containing emoticon symbols such as unamused face (ASCII symbol "&#128530;").

Workaround: Contact Support and request the custom binary that addresses this issue.

102360

Restoring

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

Related Documents