Follow

arcserve-KB : RO56479 :16.5: WIN-ARCSERVE BACKUP R16.5 CLIENT AGENT UPDATE 1

Last Update: 2016-04-20 13:58:07 UTC

Solutions Details
Operating System:    WINDOWS Solution No:    2
Confirmed Date:    04/15/2013 Updated Date:    10/31/2013
Component:    CA ARCSERVE CLIENT FOR WINDOWS COMMON-AXWCAW Release:     16.5
Fix:    RO56479 Hyper:    No
Distribution Code:    AVAILABLE     
Problem Description
Title: WIN-ARCSERVE BACKUP R16.5 CLIENT AGENT UPDATE 1
Description:
 *************************************************************************
 Please note:
 A problem was discovered when performing a RAW backup and restore
 of physical disks and volumes after applying this fix. Please reference
 https://arcserve.zendesk.com/hc/en-us/articles/208553496
 for additional information.
 *************************************************************************
 
 
  This update introduces enhancements and corrects
  problems that were discovered with CA ARCserve
  Backup r16.5. The following behaviors were
  updated:
 
  1. How to improve the throughput on raw disk
  backups and raw volume backups.
 
  With this update, you can now modify the
  following registry key to increase and decrease
  the size of the buffer read process for all input
  and output operations:
 
  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA
  ARCServe Backup\ClientAgent\Parameters\FileBufferSize
 
  Default: 512k
 
  Range: Up to 2048k (based on the available
  system resources)
 
 
  2. Backup operations can now read open files that
  are associated with Windows Server 2012 operating
  systems.
 
  With this update, CA ARCserve Backup now no
  longer skips files that are associated with
  Windows Server 2012 operating systems.
  Previously, CA ARCserve Backup could not read and
  back up various files that reported by system
  state writers. For example, AppCompat and
  BranchCache. The Client Agent for Windows now
  protects files that reside on the Windows system
  volume using the VSS option.
 
 
  3. Backup operations on folders named boot and
  bootmgr that reside on UEFI environments now
  complete successfully.
 
  Previously, the Client Agent for Windows did not
  back up folders named boot and bootmgr that
  reside on the system volume. Folders of this type
  were backed up as part of the system state.
 
  For normal volume backups, the agent added these
  folders to the exclude files list. In UEFI
  environments, the agent did not get the system
  volume and added folders named boot and bootmgr
  that existed in any volume to the exclude files
  list. As a result, backups of these folders
  failed.
 
  With this update, the agent no longer adds
  folders named boot and bootmgr that reside in any
  volume to the exclude files list when the agent
  cannot get the system volume.
 
  4. CA ARCserve D2D integration backup operations
  that consist of uncompressed CA ARCserve D2D
  backup sessions now complete successfully.
 
  Previously, backups of this type did not complete
  successfully because of the difference between
  the block sizes of D2D uncompressed backups and
  CA ARCserve Backup backups.
 
  With this update, CA ARCserve Backup now creates
  a 2-MB backup buffer when backing up uncompressed
  D2D backup sessions. This approach allows backups
  of this type to complete successfully.
 
  Note: This behavior was detected when backing up
  CA ARCserve D2D r16.5 with CA ARCserve Backup
  r16.5.
 
  5. How to improve the overall backup performance
  when backing up multithreaded CA ARCserve D2D
  integration backup sessions.
 
  With this update, you can control the quantity of
  threads that are used to read and the quantity of
  the maximum blocks that can be read at a time. To
  control the quantities, modify the following
  registry keys:
 
  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA
  ARCServe Backup\ClientAgent\Parameters\
  D2DreadThreadPoolSize
 
  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA
  ARCServe Backup\ClientAgent\Parameters\
  MaxConsequetiveD2DBlockReads
 
  As a best practice, match the quantity of threads
  with the available CPU cores by changing registry
  key named D2DreadThreadPoolSize. You can further
  optimize the disk IO using the
  MaxConsequetiveD2DBlockReads registry key.
 
 
  6. With this update, you can now move CA ARCserve
  D2D backup sessions that were replicated by CA
  ARCserve Replication and High Availability to CA
  ARCserve Backup media.
 
  The Client Agent for Windows uses a flag named
  ConnectToD2DServer in the CA_Liteintegration.ini
  file that is located in the agent installation
  folder.
 
  Location:
  C:\Program Files\CA\ARCserve Backup Client Agent
  for Windows.
 
  The agent uses the CA_Liteintegration.ini file to
  determine whether to connect to the CA ARCserve
  D2D server to retrieve the details about the
  destination or retrieve the details from the
  cache file (CA_Liteintegration.ini). For RHA
  scenarios, set the value of the flag to 0 so that
  agent that is running on the replica server does
  not connect with the original D2D server for the
  details about the destination.
 
  Example:
 
  C:\Program Files\CA\ARCserve Backup Client Agent
  for Windows
  [server_name]
  ConnectToD2DServer=0
  Destination=\\devpr01-test2\E\devpr01-2K8sp2
 
 
 
  PREREQS: None
 
  MPREREQS: None
 
  COREQS: None
 
  MCOREQS: None
 
  SUPERSEDED: None
 
 HYPER: NO
 
 DISTRIBUTION CODE: A (A=Available, I=Internal)
 
 PROBLEM RESOLUTION: Follow the instructions below:
 This fix requires CA ARCserve Backup Release 16.5 to be installed.
 
 1. Unzip the fix file as follows:
 
 CAZIPXP -U RO56479.CAZ
 
 2. Launch RO56479.exe.
 
 Note: This fix is for windows client agent.
 
 
 
 PRODUCT(S) AFFECTED: BAB Client Agent for Windows Release 16.5
 
 DOWNLOAD INFORMATION:
 ---------------------
 http://downloads.arcserve.com/patches/AXWBAS/nt/GA/RO56479/RO56479.CAZ
 
 UPDATED ROUTINES:
 ---------------
 ntagent.dll.wxp
 ntagent.dll.XP.2000
 ntagent.dll.2003.2008.2008R2
 ntagent.dll.w2k3
 ntagent.dll.wxp._x64
 ntagent.dll.X64.XP.2000
 ntagent.dll.w2k3._x64
 ntagent.dll.X64.2003.2008.2008R2
 RO56479.exe
 
 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments