CA ARCserve® D2D r16 Update 8 Release Notes
1.0 Welcome
2.0 Enhancements
3.0 Issues Fixed
4.0 Known Issues
5.0 Limitations
6.0 Installation
6.1 Prerequisite Tasks
6.2 Installation Instructions
7.0 Contact CA
1.0 Welcome
Welcome to the CA ARCserve D2D r16 Update 8 Release Notes.
This Release Notes contains important information about
this update.
2.0 Enhancements
The following enhancements have been added to CA ARCserve
D2D for this update:
- Test Fixes installed. For more information, see Issues
Fixed in the Release Notes.
- Microsoft Exchange 2010 SP3 support is added.
3.0 Issues Fixed
This update fixes the following issues:
- A problem that causes a merge failure with a possible data
corruption after applying CA ARCserve D2D r16 Update 7.
(Test Fix T5E5182/RO53648).
This fix addresses a data corruption problem. This fix does
not repair the actual corruption, but prevents it from
occurring in the future. If this fix is applied after the
data corruption has occurred, then a new full backup is
required to create new fully-protected recovery points.
If you are unsure if you have data corruption, you should
use the data corruption detection utility (AFUtil.exe) to
perform a full scan of your recovery points to confirm the
integrity of the backed-up data. For more information about
this problem and the use of the data corruption detection
utility, see the Recovery Point Merge Failure May Render
Recovery Point Unrecoverable topic in the CA ARCserve D2D
online help.
Note: For CA ARCserve D2D r16, the data corruption
detection utility (AFUtil.exe) is automatically installed
along with Update 8 and is located in the BIN folder (by
default C:\Program Files\CA\ARCserve D2D\BIN).
- A problem that causes an "Invalid email 'Recipients'
address" message to be displayed if the email address in
the Recipients field contains a hyphen in its root domain
name. For example: xxx@yyy.zzz-z. (Test Fix T245803).
- A problem that causes an operation timeout error to occur
when the attempt to save your backup settings fails. (Test
Fix T2D2930).
- A problem that causes a catalog job to fail with the
following error in activity.log: "An unexpected exception
error occurred in vmdkimgdll.dll". (Test Fix T5LF180).
- A problem that causes a merge job to launch incorrectly
when there are crashed sessions involved. (Test Fix
T2D2932).
- A problem that causes a backup job to crash immediately
when the job is launched. (Test Fix T5E5180).
- A problem that causes the Exchange Server or SQL Server
logs to not get truncated daily despite the Truncate log
option being set to purge daily. (Test Fix T2D2935).
- A problem that causes hard link files to be restored as
separate normal files. (Test Fix T245799).
Note: After applying this fix, you need to perform a full
backup to fully resolve this problem.
- A problem that causes a failure to restore Microsoft
Exchange Dump email items if the user display name contains
"<>" or other special characters. The activity log displays
"Restore message to disk error: the filename, directory
name or volume label syntax is incorrect". (Test Fix
T2D2939).
- A problem that causes MergeMgr.exe to stop working if
switch "/BKDIR" is used. (Test Fix T245802).
- A problem that causes the merging of recovery points to
fail after some disks have already been merged completely.
(Test Fix T2D2944).
- A problem that causes a CA ARCserve D2D merge job to not be
launched after completion of a CA ARCserve Backup
integration backup for a CA ARCserve Central Host-Based VM
Backup session. (Test Fix T2D2945).
- A problem that causes full backups to always be performed
despite the backup schedule setting being configured to
perform incremental backups. (Test Fix T5LE118).
- A problem that causes virtual standby conversion jobs to
randomly fail. (Test Fix T2D2947).
- A problem that causes the following message to be displayed
while MergeMgr.exe is running after being manually started:
"WriteAttributeString: attr[DetailTime] value[<time
string>] failed" (Test Fix T245807)
- A problem that causes a Windows 2003 or Windows XP machine
to fail to boot after performing a BMR with the following
error message displayed: "Windows could not start because
the following file is missing or corrupt: <Windows
root>\system32\ntoskrnl.exe(or hal.dll etc)". (Test Fix
T5E5181/RO53672).
- A problem that causes a policy deployment failure for CA
ARCserve Central Host-Based VM Backup after applying Update
7. (Test Fix T2D2927/RO52115).
- A problem that causes a backup job to fail when CA ARCserve
D2D is unable to find the parent disk for the backup after
merge. The following error messages are seen in the log
file: (Test Fix T5LE119).
- Failed to write to virtual disk. Internal error=[CAN NOT
FOUND PARENT DISK].
- Failed to verify parent Unique ID for
\\xxx.xxx.xxx.xxx\...\diskxxxxxxxx.D2D.
- A problem that causes a merge job to fail with the
following errors in AFStor.log: (Test Fix T2D2951).
- A problem during the restore process of a Microsoft
Exchange mail item that prevents the FROM and SUBJECT data
from being restored. (Test Fix T2D2956).
4.0 Known Issues
The following issues are known to exist in this update:
- Remote deployment of CA ARCserve D2D r16 to a Windows XP
system can fail with error: Failed to get installation
status feedback from the remote target host.
Symptom:
A timeout error or a bad network connection can cause this
failure. The XP system shows the CA ARCserve D2D
installation is complete but the reboot fails. You cannot
reboot the system manually. Therefore, a hard reboot is
required. This problem is a known issue with Windows XP.
Solution:
Apply the following Microsoft patches before deploying CA
ARCserve D2D or install CA ARCserve D2D locally on a
Windows XP system:
- The process of generating catalogs may stop responding when
the volume extent is spread across a disk.
Symptom:
The volumes extent cannot have more than one logical extent
across a disk. This behavior occurs on striped volumes and
does not occur on simple, mirrored, and spanned volumes.
Solution:
To prevent this behavior from occurring, the volumes extent
should be contiguous on a disk or do not include this type
of volume in your backup.
- Intermittent failures in backup, restore, merge, and other
operations are observed if a network share on a “HP
StorageWorks D2D4106” device is used as the backup
destination for CA ARCserve D2D. It is not recommended to
use this device for the backup destination.
- For uncompressed and unencrypted backups, it may not be
possible to resume the merge after pausing it. CA
Technologies is in the process of resolving this issue.
5.0 Limitations
The following limitations are known to exist in this update:
- If multiple sessions are available to be merged, the
pause/resume merge function is applicable only for
compressed sessions.
- CA ARCserve D2D requires the file attribute "system" to
convert the backup destination folder to the ARCserve D2D
View. However, on some NAS filers, the file attribute
"system" is not supported, therefore you cannot change the
destination to the ARCserve D2D View.
- If you are attempting to upgrade CA ARCserve D2D by remote
deployment, the deployment may fail if the CA ARCserve
Universal Agent service (r16 or later) is running on the
target computer. To prevent this from happening, stop the
CA ARCserve Universal Agent service and continue the
upgrade.
6.0 Installation
The following sections provide information about
installation prerequisites and installation instructions.
6.1 Prerequisite Tasks
Consider the following prerequisite tasks before installing
this update:
- Before you install this update, verify that CA ARCserve D2D
r16 is installed (with or without any previous r16 Updates).
- Consider the following if you have a release prior to CA
ARCserve D2D r16 Update 6 and you want to upgrade to CA
ARCserve D2D r16 Update 8.
Important! The installation of CA ARCserve D2D r16 Update 8
will also update drivers and require a reboot upon
completion. If you are installing the update, triggered
from the user interface or from the tray monitor, then your
machine will automatically reboot after the upgrade is
successfully completed. As a result, you should save all
data before starting the installation of this update. If a
reboot is not desirable at this time, you should consider
postponing the installation of Update 8 until a more
convenient time.
6.2 Installation Instructions
You can use two methods to install this update:
Note: The D2D probe is available for download and
installation from the Nimsoft Internet Archive.
7.0 Contact CA
Contact CA Support
For your convenience, CA Technologies provides one site
where you can access the information that you need for your
Home Office, Small Business, and Enterprise CA Technologies
products. At http://ca.com/support, you can access the
following resources:
- Online and telephone contact information for technical
assistance and customer services
- Information about user communities and forums
- Product and documentation downloads
- CA Support policies and guidelines
- Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies
product documentation, you can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product
documentation, complete our short customer survey which is
available on the CA Support website at http://ca.com/docs.
Copyright © 2013 CA. All rights reserved. All trademarks,
trade names, service marks, and logos referenced herein
belong to their respective companies.