CA ARCserveĀ® D2D r16 Update 7 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 Arcserve
1.0 Welcome
Welcome to the CA ARCserve D2D r16 Update 7 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:
- Option to create recovery sets (Disable infinite
incremental backups when needed).
You can configure how many recovery sets to retain,
starting with a full backup, and when the number of
recovery sets exceeds the user-specified one, the oldest
recovery set will be deleted, instead of merged.
- Merge Multiple Sessions at the Same Time.
This process separates the merge job in a dedicated
application, allowing the merge job to merge multiple
sessions at the same time. The merge job can be
started/stopped and paused/resumed on demand and does not
affect any other jobs.
This new merge process avoids multiple reads and writes
because it only merges the latest change for each block.
The merge process ignores all the changes that have
occurred to the same block during any intermediate
incremental backups. Merging multiple sessions at the same
time is faster than merging them individually.
- CA ARCserve D2D Probe for Nimsoft.
The CA ARCserve D2D Probe for Nimsoft is a software module
that sends the CA ARCserve D2D alerts and backup job status
to the Nimsoft server. You can view the alerts from both
the Nimsoft Infrastructure Manager and the Nimsoft Unified
Management Portal (UMP). However, you can only view the job
status data from the UMP. The advantage of using Nimsoft to
monitor the alerts and status is that you can monitor
multiple CA ARCserve D2D servers from one central location.
Nimsoft also lets you run CA ARCserve D2D commands such as
full backup, incremental backup, and verify backup using
the Nimsoft Probe utility.
3.0 Issues Fixed
This update fixes the following issues:
- A problem that displays the incorrect default vendor URL
for Fujitsu Cloud (Windows Azure) in the Cloud
Configuration dialog. (Test Fix T245774)
- A problem that causes an invalid username message when
specifying the Cloud Configuration for File Copy if
"username" is input instead of "domain\username" or
machinename\username". (Test Fix T245780)
- A problem that causes a file copy job to crash on resource
constrained systems. (Test Fix T2D2877)
Note: If the operating system is severely
resource-constrained, applying this fix may not help.
- An integration problem that causes a failed attempt to use
CA ARCserve Backup to back up to a CA ARCserve D2D
destination and gives a false indication (Error AE0802)
that the backup destination is busy with a CA ARCserve D2D
merge/purge operation. This problem occurs when the merge
lock file ("merge.lck") was not properly deleted from the
destination during a previous merge/purge operation. (Test
Fix T2D2878)
- A problem that causes a restore job to take a long time
while restoring the system file, "Thumbs.db". This file is
automatically generated when viewing pictures, so there is
no need to back up or restore it. Therefore, after you
apply this fix, the file is no longer available to restore.
(Test Fix T2D2893)
- A problem that causes the creation of a virtual machine on
the ESX 5.0 server with CA ARCserve Central Virtual Standby
to fail if the virtual disk size is larger than 256 GB.
(Test Fix T2D2899)
- A problem that causes the Exchange Granular Restore job to
crash. (Test Fix T2D2904)
- A problem that prevents recovery points from merging due to
not enough space on the backup destination. If the sessions
to be merged are both full backups, then CA ARCserve D2D
will not check for free space and allows the merge to
continue. (Test Fixes T2D2907,T2D2908 )
- A problem when restoring an MS Exchange mailbox that causes
a message "Insufficient privileges for the account" when
performed in a mixed environment of MS Exchange 2003, MS
Exchange 2007, and MS Exchange 2010. (Test Fix T2D2912)
- A problem that prevents CA ARCserve D2D from restoring
files under the following situations: (Test Fix T2D2914)
- If the backup job was run with no compression and no
encryption.
- Following messages are seen in AFStor log, but no message
is seen in the activity log.
- CDynamicVHD::Read(702)ReadFile(xxxx, xxxx) failed. err=xx
- MergeToparentVHD[path ] failed.
- CBLISession::PurgePhase1: Error merging [diskxxx.D2D].
[EC=0]
Important! This fix does not recover deleted data. It will
prevent future problems. After applying this fix, run a
full backup job.
- A problem that causes the CA ARCserve D2D home page summary
information to keep loading and then times out. The reason
is due to AFcoreFunction.dll crashing which causes the web
service to time out and the backup job to crash. (Test Fix
T2D2920)
- A problem that prevents CA ARCserve D2D from restoring
Mailbox attachments for Microsoft Exchange 2007 or
Microsoft Exchange 2003. (Test Fix T2D2921)
- A problem that causes merge of the recovery points to fail
while purging the S00000000XX_bak folder under Vstore and
the subsequent backup jobs crash. (Test Fix T2D2924)
- A problem in CA ARCserve Central Host-Based VM Backup for
VM that prevents the exchange transaction log from purging
even though the purge exchange log is enabled daily. (Test
Fix T2D2925)
- A problem that fails to differentiate the backup
destination and copy recovery points destination under
certain circumstances. For example, if both destinations
are on a USB disk. (Test Fix T5E5158)
- A problem where Fujitsu Cloud information is lost under
certain circumstances when trying to configure the file
copy destination to cloud. (Test Fix T5E5166)
- A problem when restoring a virtual machine where the VM
Datastore takes several minutes to load and causes the
Restore dialog to disappear after hanging for a few
minutes. This problem usually occurs when you perform one
of the following tasks: (Test Fix T5E5168)
- Recover a virtual machine backup up by CA ARCserve Central
Host-Based VM Backup to an alternate location.
- Select connecting to a vCenter which has a lot of
datastores attached (30+).
- A problem that causes Verify backup jobs to crash under
certain circumstances, such as a bad network environment or
an intensive read/write of the backup destination. (Test
Fix T5E5169)
- A problem that prevents the catalog job from being
generated. (Test Fix T5E5172)
- A problem that causes an error indicating that the system
volume was not backed up and you cannot perform a BMR from
the recovery point, even though the recovery point does
include the Windows System Volume. This usually occurs
when the System Volume is an OEM system volume with
different partition type/attributes.
Note: An incremental backup needs to be run after applying
this fix. This fix will not correct the recovery points
created before applying this fix. Contact support if you
need to do a BMR from these recovery points. (Test Fix
T5E5174)
- A problem that causes the catalog job to fail with the
following error in the activity.log:
An unexpected exception error occurred in vmdkimgdll.dll
(Test Fixes T5LF146, T5LF163, T5LF165)
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 7.
Important! The installation of CA ARCserve D2D r16 Update 7
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 7 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 Arcserve
Contact Arcserve Support
For your convenience, Arcserve provides one site where you
can access the information that you need for your Home
Office, Small Business, and Enterprise Arcserve products.
At http://arcserve.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
- Arcserve Support policies and guidelines
- Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about Arcserve product
documentation, you can send a message to techpubs@arcserve.com.
Copyright © 2012 Arcserve. All rights reserved. All
trademarks, trade names, service marks, and logos
referenced herein belong to their respective companies.