This version of the RUU update provides the enhancements listed below:
The following is a list of known issues present in the DL Appliance at the time of this RUU release. For a complete list of known issues in Rapid Recovery 6.1.3, refer to the Rapid Recovery 6.1.3 Release Notes.
Workaround: Perform another Remount Volumes job. |
|
Workaround: None. |
|
Sometimes "Internal Server Error" appears on Backup page. Workaround: Ignore and close the error message. |
|
After an upgrade to release 6.1.2, repository maintenance failed after a restore of the provisioning configuration. Workaround: Contact Support. |
|
Remount job does not restore Core's localization. Workaround: Manually change Core localization from Core Settings. |
|
Workaround: Install the latest Windows updates and reboot the appliance. If this problem persists, contact Support. |
|
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. |
|
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. |
|
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). |
|
Workaround: Remove assigned letters from attached virtual media via disk manager. Perform Volumes Remount job again from Appliance Provisioning page. |
|
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. |
|
The GUI should be disabled immediately after confirmation of the remount process. Workaround: Wait for a few minutes and refresh Core Console page. |
|
Workaround: None. |
|
VD disk provisioning fails with return code 4 if storage pool does not have consistent empty space. |
|
Workaround: Do not click these buttons until the corresponding VM export is complete. |
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center