CA Technologies

CA ARCserve® Backup r15 SP1 Readme

5.0 Upgrade Considerations
5.1 Upgrade Considerations for the CA ARCserve Backup Base Product

6.0 General Considerations

7.0 Supported Upgrade Paths
7.1 Backward Compatibility

9.0 Included Fixes
9.1 Additional Information for Included Fixes

10.0 Language Certifications

11.0 Contact CA

1.0 Welcome

Welcome to the CA ARCserve Backup r15 SP1 Readme. This readme contains issues and other information discovered after publication including a complete list of the known issues for this release.

For details about how the features and enhancements for this release might affect you, see the CA ARCserve Backup Release Summary. You can access the most up-to-date product documentation (Online Help and PDFs) from the CA ARCserve Backup website at https://support.ca.com/prodinfo/arcserve.

CA ARCserve Backup supports the following suites:

CA ARCserve Backup for Windows Essentials Module

CA ARCserve Backup Guest Based Virtual Machines Agent Bundle

CA ARCserve Backup for Windows Advanced Module

CA ARCserve Backup for Windows Standard Module

CA ARCserve Backup for Windows Enterprise plus Module

2.0 Operating System Support

The following topics provide information about the supported operating systems for the CA ARCserve Backup base product, agents and options. For the most current information regarding supported operating systems, see the compatibility matrix on support.ca.com.

2.1 Supported Operating Systems for the Base Product

You can install the CA ARCserve Backup base product on the following operating systems. For the most current information regarding supported operating systems, see the compatibility matrix on support.ca.com.

Windows Server 2008 R2

R2 Standard (x64)

R2 Enterprise (x64)

R2 Data Center (x64)

Windows Web Server 2008 R2

R2 Core (x64) (CA ARCserve Backup Member Server, CA ARCserve Backup Disaster Recovery Option, CA ARCserve Backup Enterprise Module with ACSLS and IBM 3494 installation disabled, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Agent for Virtual Machines, CA ARCserve Backup Client Agent for Windows)

Failover Cluster support (Windows Server 2008 Enterprise, Windows Server 2008 Standard only). Install locally and follow instructions for cluster environment.

Itanium based systems

Note: Windows Server 2008 R2 only supports NEC clusters, not MSCS clusters.

Windows Server 2008 SP1, SP2

R2 Standard and Core Editions (x64) (CA ARCserve Backup Member Server, CA ARCserve Backup Disaster Recovery Option, CA ARCserve Backup Enterprise Module with ACSLS and IBM 3494 installation disabled, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Agent for Virtual Machines, CA ARCserve Backup Client Agent for Windows)

Enterprise (x86, x64)

Standard (x86, x64)

Data Center (x86, x64)

Web Server (x86, x64)

Itanium Based systems

Core (x86, x64) (CA ARCserve Backup Member Server, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Agent for Virtual Machines)

Failover Cluster support (Windows Server 2008 Enterprise, Windows Server 2008 Standard only). Install locally and follow instructions for cluster environment.

Note: Windows Server 2008 SP1, SP2 only supports NEC clusters, not MSCS clusters.

Windows Server 2008 Foundation

x64 systems: (CA ARCserve Backup Server, CA ARCserve Backup Enterprise Option, CA ARCserve Backup Tape Library Option, CA ARCserve Backup Storage Area Network Option, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Disaster Recovery Option)

R2 (x64) systems: (CA ARCserve Backup Server, CA ARCserve Backup Enterprise Option, CA ARCserve Backup Tape Library Option, CA ARCserve Backup Storage Area Network Option, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Disaster Recovery Option)

Windows Essential Business Server 2008

Standard Edition (x64 only) (CA ARCserve Backup Server, CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files, Disaster Recovery Option, CA ARCserve Backup Agent for Microsoft Exchange Server, CA ARCserve Backup Agent for Microsoft SQL Server) SP1, SP2

Premium Edition (x64 only) (CA ARCserve Backup Server, CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files, Disaster Recovery Option, CA ARCserve Backup Agent for Microsoft Exchange Server, CA ARCserve Backup Agent for Microsoft SQL Server) SP1, SP2

Windows Small Business Server 2008

Standard Edition (x64 only) (CA ARCserve Backup Server, CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Agent for Microsoft Exchange Server, CA ARCserve Backup Agent for Microsoft SharePoint Server, CA ARCserve Backup Agent for Microsoft SQL Server)

Premium Edition (x64 only) (CA ARCserve Backup Server, CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Agent for Microsoft Exchange Server, CA ARCserve Backup Agent for Microsoft SQL Server)

Windows Storage Server 2008

x86 and x64: (CA ARCserve Backup Server, CA ARCserve Backup Tape Library Option, CA ARCserve Backup Storage Area Network Option, CA ARCserve Backup Network Attached Storage Option, CA ARCserve Backup Agent for Open Files, CA ARCserve Backup Disaster Recovery Option)

Windows Server 2003

R2 Standard Edition (x86, x64) or R2 Service Pack 2

R2 Enterprise Edition (x86, x64, IA64) at minimum Service Pack 1 or Service Pack 2

Standard Edition (x86, x64) at minimum Service Pack 1 or Service Pack 2

Web Edition (x86 only) at minimum Service Pack 1 or Service Pack 2

Datacenter (x86, x64)

Storage Server R2 Service Pack 1 or Service Pack 2

Small Business Server R2 Service Pack 1 or Service Pack 2

Failover Cluster Server (x86, x64, and IA64)

The CA ARCserve Backup base product is not supported on Windows Vista and Windows 7 systems. However, the following CA ARCserve Backup components are supported:

Windows Vista (x86 and x64) SP1, or SP2

CA ARCserve Backup Client Agent for Windows

CA ARCserve Backup Agent for Virtual Machines

CA ARCserve Backup Agent for Open Files

CA ARCserve Backup Manager Console only (the CA ARCserve Backup Server is not supported)

CA ARCserve Backup Agent Deployment

Windows 7 Professional, Ultimate and Enterprise Editions (x86 and x64)

CA ARCserve Backup Manager Console only (the CA ARCserve Backup Server is not supported)

CA ARCserve Backup Client Agent for Windows

CA ARCserve Backup Agent for Virtual Machines

CA ARCserve Backup Agent for Open Files

CA ARCserve Backup Agent Deployment

2.2 Supported Operating Systems for CA ARCserve Backup CA ARCserve Replication (formerly, CA XOsoft) Integration

To integrate CA ARCserve Backup with CA ARCserve Replication, install the following:

CA ARCserve Replication version 4.0, r12, r12 SP1, r12.5 SP1, SP2, or r15

Master servers

Microsoft Windows 2000 Server and Advanced Server SP4

Microsoft Windows Server 2003 SP1, SP2 or R2 (32-bit and 64-bit)

Microsoft Windows Server 2008 (CA ARCserve Replication r12.5, r12 SP1, or r15)

Microsoft Windows Server 2008 R2 (CA ARCserve Replication r12.5 SP2, r15)

Replica servers

Microsoft Windows Server 2003 SP1, SP2 or R2 (32-bit and 64-bit)

Microsoft Windows Server 2008 (CA ARCserve Replication r12.5, r12 SP1, or r15)

Microsoft Windows Server 2008 R2 (CA ARCserve Replication r12.5 SP2, r15)

For more information about integration, refer to the CA ARCserve Backup for Windows CA ARCserve Replication Integration Guide.

2.3 Supported Operating Systems for the CA ARCserve Backup Client Agents

You can install the CA ARCserve Backup Client Agent for Windows on the following operating systems:

Windows Vista (x86 and x64) at minimum, SP1, or SP2 (CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, and CA ARCserve Backup Agent for Open Files)

Windows XP Professional x86 (CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files) (at minimum SP1, SP2, and SP3)

Windows XP Professional x64 (CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows and CA ARCserve Backup Agent for Open Files ) (at minimum SP1 and SP2)

Windows Server 2003 Web Edition (x86 only) (SP1, SP2)

Windows Server 2003 Standard Edition (x86 and x64) (SP1, SP2, R2, R2 SP2)

Windows Server 2003 Enterprise Edition (x86, x64, and IA64) (SP1, SP2, R2, R2 SP2)

Windows Server 2003 Cluster x86 (SP1, SP2, R2, R2 SP2) x64 (SP1, SP2, R2, R2 SP2) and IA64 (SP1, SP2)

Windows Storage Server 2003 (WSS) x86 (SP1, SP2, R2, R2 SP2), x64 (R2, R2 SP2)

Windows Storage Server 2008 (WSS) x86 (SP1, SP2) and x64 (SP1, SP2)

Windows 2003 Datacenter (x86 and x64) (SP1, SP2)

Windows 2000 Professional x86 (SP4 and SP4 Rollup 1)

Windows 2000 Server x86 (SP4 and SP4 Rollup 1)

Windows 2000 Advanced Server x86 (SP4 and SP4 Rollup 1)

Windows 2000 Datacenter x86 SP4 Rollup 1

Windows 2000 Cluster Server x86 (2 node Advanced Edition) (SP4 and SP4 Rollup 1)

Windows Powered NAS (2000) x86 (SP4 Rollup 1)

Windows Server 2008 Enterprise Edition (x86, x64, and IA64) (SP1, SP2)

Windows Server 2008 Standard Edition (x86, x64, and IA64) (SP1, SP2)

Windows Server 2008 Web Edition (x86 and x64) (SP1, SP2)

Windows Server 2008 Data Center (x86 and x64) (SP1, SP2)

Windows Server 2008 Core (x86 and x64) (SP1, SP2)

Windows Server 2008 R2 (x64)

Windows Server 2008 R2 Core (x64)

Windows Storage Server 2008 (x86 and x64)

Windows 7 (x64, x86)

You can install the CA ARCserve Backup Client Agent for UNIX on the following operating systems:

Solaris 8, 9, and 10 SPARC

Solaris 10 (x86 32-bit)

Solaris 10 x64

IBM AIX 5.2, v5.3, and v6.1

HP-UX 11.23, and 11.31 PA-RISC

HP-UX 11.23 and 11.31 Itanium (IA64)

Tru64 v5.1b

FreeBSD version 7.2 (x86, x64)

You can install the CA ARCserve Backup Client Agent for Linux on the following operating systems:

Red Hat Enterprise Linux 3.x, 4.x, 5.x, (AS, ES, WS) (x86, AMD64, Intel EM64T, IA64)

SuSE Linux Enterprise Server 9.x, 10.x, 11.x (x86, AMD64, Intel EM64T, IA64)

Turbolinux 11.0

Miracle Linux 4.0 (x86, AMD64, Intel EM64T)

Red Flag Data Center Server 5.0 (x86, AMD64, Intel EM64T, IA64)

Asianux 3.0 (x86, x64)

Debian 4.0 (x86)
Note: To run CA ARCserve Backup on Red Hat Enterprise Linux 4 IA64, you must install the IA-32 Execution Layer from Red Hat. For more information, see the Red Hat Enterprise Linux 4 release notes.

You can install the CA ARCserve Backup Client Agent for Linux on OS/390 on the following operating systems:

Red Hat Enterprise Server 3.x, 4.x, and 5.x (32-bit and 64-bit) including SMP

SuSE Enterprise Server 9 and 10 (32-bit and 64-bit) including SMP

You can install the CA ARCserve Backup Client Agent for Mac OS X on the following operating systems:

Apple OS X 10.5 (both Intel and PowerPC)

Note: For more information about support for newer versions of the operating systems in the above list, contact CA Support at http://ca.com/support.

You can install the CA ARCserve Backup Client Agent for OpenVMS on the following operating systems:

VAX 6.2, 7.1, 7.2, 7.3

AXP 6.2, 7.1, 7.2, 7.3

You can install the CA ARCserve Backup Enterprise Option for AS400 on the following operating systems:

AS400 V5 R2 (5.2), V5 R3 (5.3), and V5 R4 (5.4)

AS400 V6 R1 M0 (v6.1.0)

You can install the CA ARCserve Backup Client Agent for NetWare on the following operating systems:

NetWare 5.1 SP8

NetWare 6.0 SP5

NetWare 6.5 SP7, SP8 (requires a Pentium-class processor with at least 512 MB RAM)

2.4 Supported Operating Systems for the Agent for IBM Informix

You can install the CA ARCserve Backup Agent for IBM Informix on the following operating systems:

Windows 2000 Advanced Server SP4, SP4 Rollup 1 (x86)

Windows 2003 Enterprise, Standard, Data Center SP2 (x64, x86)

Windows 2003 R2 Enterprise, Standard, Data Center SP2 (x86)

Windows 2003 R2 SP2 (x64)

Windows Server 2008 Enterprise, Standard, Data Center SP2 (x86)

Windows Server 2008 R2 Enterprise, Standard, Data Center (x64)

Windows Server 2008 R2 (x64)

Note: Windows 2000 Advanced Server supports Informix 10.00 only.

2.5 Supported Operating Systems for the Agent for Lotus Domino

You can install the CA ARCserve Backup Agent for Lotus Domino on the following operating systems:

Windows 2000 Server or Advanced Server SP4, SP4 Rollup1 with Lotus Domino 7.0, 7.0.2, or 7.0.3 (without db2 enabled)

Windows 2003 Standard or Enterprise Server, SP1, SP2, or R2, R2 SP2 with Lotus Domino 7.0, 7.0.2, 7.0.3, 8.0, 8.0.1, 8.0.2, 8.5, or 8.5.1 (without db2 enabled).

Windows 2003 Standard or Enterprise Server (x64) SP2, R2, R2 SP2 with Lotus Domino 8.0.2, 8.5, or 8.5.1 WOW (without db2 enabled)

Windows Server 2008 Standard or Enterprise SP1, SP2 with Lotus Domino 8.5, 8.5.1, or 8.5.2 (without db2 enabled)

Windows Server 2008 Standard or Enterprise (x64) SP1, SP2 with Lotus Domino 8.5, 8.5.1, or 8.5.2 WOW (without db2 enabled)

Note: The Agent for Lotus Domino supports x86 and x64 systems, but not on IA64 systems. When installing on x64 systems, the default installation path is:

C:\Program Files (x86)\CA\ARCserve Backup Agent for Lotus Domino\

2.6 Supported Operating Systems for the Agent for Microsoft Exchange Server

You can install the CA ARCserve Backup Agent for Microsoft Exchange Server on the following operating systems:

For Microsoft Exchange Server 2000, Exchange Server 2000 SP1, SP2, SP3
- Microsoft Windows 2000 Server Edition SP3,SP4 or SP4 rollup 1
- Microsoft Windows 2000 Server Advanced Edition SP3, SP4 or SP4 rollup 1
- Microsoft Windows 2000 Server Datacenter Edition SP3 , SP4 or SP4 rollup 1

For Microsoft Exchange Server 2003,Exchange Server 2003 SP1 or SP2
- Microsoft Windows 2000 Server Standard Edition SP3 or SP4
- Microsoft Windows 2000 Server Enterprise Edition SP3 or SP4
- Microsoft Windows 2000 Server Datacenter Edition SP3 or SP4
- Microsoft Windows 2003 Server Standard Edition for x86, Windows 2003 SP1, or SP2
- Microsoft Windows 2003 Server Enterprise Edition for x86, Windows 2003 SP1, or SP2
- Microsoft Windows 2003 Server Datacenter Edition for x86, Windows 2003 SP1, or SP2

For Microsoft Exchange Server 2007, Exchange Server 2007 SP1, SP2, SP3
- Microsoft Windows Server 2003 Standard Edition for x64, 2003 for x64 SP1, or 2003 for x64 SP2
- Microsoft Windows Server 2003 Enterprise Edition for x64, 2003 for x64 SP1, or 2003 for x64 SP2
- Microsoft Windows Server 2003 R2
- Microsoft Windows Server 2008 R2
- Microsoft Windows Server 2008 for x64 (only Microsoft Exchange Server Version 2007 SP1 or SP2 are supported) Windows 2008 SP1, SP2

For Microsoft Exchange Server 2010, Exchange Server 2010 SP1
- Microsoft Windows Server 2008 Standard Edition x64, SP2
- Microsoft Windows Server 2008 Enterprise Edition x64, SP2
- Microsoft Windows Server 2008 R2 Standard Edition
- Microsoft Windows Server 2008 R2 Enterprise Edition

2.7 Supported Operating Systems for the Agent for Microsoft SharePoint Server

You can install the CA ARCserve Backup Agent for Microsoft SharePoint Server on the following operating systems:

For Microsoft Office SharePoint Server 2007

Microsoft Windows Server 2003 Standard Edition SP1, SP2,

Microsoft Windows Server 2003 Enterprise Edition SP1, SP2

Microsoft Windows Server 2003 Datacenter Edition SP1, SP2

Microsoft Windows Server 2003 Web Edition SP1, SP2

Microsoft Windows Server 2003 R2 SP2 Standard Edition

Microsoft Windows Server 2003 R2 SP2 Enterprise Edition

Microsoft Windows Server 2003 R2 SP2 Datacenter Edition

Microsoft Windows Server 2003 R2 SP2 Web Edition

Microsoft Windows Server 2008 Standard Edition SP1, SP2 (Only for SharePoint Server 2007 with SP1)

Microsoft Windows Server 2008 Enterprise Edition SP1, SP2 (Only for SharePoint Server 2007 with SP1)

Microsoft Windows Server 2008 Datacenter Edition SP1, SP2 (Only for SharePoint Server 2007 with SP1)

Microsoft Windows Server 2008 Web Edition SP1, SP2 (Only for SharePoint Server 2007 with SP1)

Microsoft Windows Server 2008 R2 Standard Edition (Only for SharePoint Server 2007 x64 with SP2)

Microsoft Windows Server 2008 R2 Enterprise Edition (Only for SharePoint Server 2007 x64 with SP2)

Microsoft Windows Server 2008 R2 Datacenter Edition (Only for SharePoint Server 2007 x64 with SP2)

Microsoft Windows Server 2008 R2 Web Edition (Only for SharePoint Server 2007 x64 with SP2)

Microsoft Windows Server 2008 Foundation Server Edition (Only for SharePoint Server 2007 x64 with SP2)

Microsoft Windows Server 2008 Foundation Server R2 Edition (Only for SharePoint Server 2007 x64 with SP2)

For Microsoft SharePoint Server 2010

Microsoft Windows Server 2008 Standard Edition SP2

Microsoft Windows Server 2008 Enterprise Edition SP2

Microsoft Windows Server 2008 Datacenter Edition SP2

Microsoft Windows Server 2008 R2 Standard Edition

Microsoft Windows Server 2008 R2 Enterprise Edition

Microsoft Windows Server 2008 R2 Datacenter Edition

2.8 Supported Operating Systems for the Agent for Microsoft SQL Server

You can install the CA ARCserve Backup Agent for Microsoft SQL Server on the following operating systems:

For 32-bit Systems:

Microsoft SQL Server 7.0 (SP2, SP3, or SP4) Support
- Windows 2000 Server SP4

Microsoft SQL Server 2000 (SP3, SP3a, or SP4) Support
- Windows 2000 Server SP4
- Windows Server 2003 SP1, SP2 or Windows 2003 R2 SP2

Microsoft SQL Server 2005 (SP1,SP2,SP3) Support
- Windows 2000 Server SP4, Advanced Server SP4
- Windows Server 2003 SP1, SP2 or Windows 2003 R2 SP2

Microsoft SQL Server 2005 (SP2,SP3 only) Support
- Windows Server 2008 SP1, SP2

Microsoft SQL Server 2008 (SP1) Support
- Windows Server 2003 SP1, SP2 or Windows Server 2003 R2 SP2
- Windows Server 2008 SP1, SP2

Microsoft SQL Server 2008 R2 Support
- Windows Server 2003 SP2 or Windows Server 2003 R2 SP2
- Windows Server 2008 SP2

Microsoft SQL Server 2008 (SP2) Support
- Windows Server 2008 SP2

For 64-bit Systems:

Microsoft SQL Server 2000 for IA64 on Windows 2003 for IA64-based systems

Microsoft SQL Server 2000 for x86 on Windows 2003 SP2 or Windows 2003 R2 for x64-based systems

Microsoft SQL Server 2005 (SP1,SP2 or SP3) for x64 on Windows Server 2003 SP1,SP2, R2 SP2

Microsoft SQL Server 2005 (SP1,SP2 or SP3) for IA64 on Windows Server 2003 SP1, SP2 for IA64-based systems

Microsoft SQL Server 2005 (SP2,SP3 only) for x64 on Windows Server 2008 SP1, SP2 for x64-based systems

Microsoft SQL Server 2005 (SP2,SP3 only) for IA64 on Windows Server 2008 SP1, SP2 for IA64-based systems

Microsoft SQL Server 2008 (SP1) for x64 on Windows Server 2003 SP2, R2 or Windows Server 2008 SP1, SP2 for x64-based systems

Microsoft SQL Server 2008 (SP1 only) for x64 on Windows Server 2008 R2 for x64-based systems

Microsoft SQL Server 2008 (SP1) for IA64 on Windows Server 2003 SP2, R2 or Windows Server 2008 SP1, SP2 for IA64-based systems

Microsoft SQL Server 2008 (SP1 only) for IA64 on Windows Server 2008 R2 for IA64-based systems

Microsoft SQL Server 2008 (SP2) for IA64 on Windows Server 2008 SP2 for IA64-based systems

Microsoft SQL Server 2008 (SP2) for x64 on Windows Server 2008 SP2 for x64-based systems

Microsoft SQL Server 2008 R2 for x64 on Windows Server 2003 SP2 or Windows Server 2008 SP2,R2 for x64-based systems

Microsoft SQL Server 2008 R2 for IA64 on Windows Server 2003 SP2 or Windows Server 2008 SP2,R2 for IA64-based systems

2.9 Supported Operating Systems for CA ARCserve Backup for Microsoft Windows Essential Business Server

You can install CA ARCserve Backup for Microsoft Windows Essential Business Server on the following operating systems:

Windows Server 2008 SP1, SP2 (x64)

2.10 Supported Operating Systems for CA ARCserve Backup for Small Business Server Editions

You can install CA ARCserve Backup for Small Business Server Editions on the following operating systems:

Windows Server 2003 SP1, SP2

Windows Server 2008 SP1, SP2 (x86 and x64)

2.11 Supported Operating Systems for the Agent for Oracle (UNIX/Linux)

You can install the CA ARCserve Backup Agent for Oracle on the following UNIX operating systems:

Solaris 8, 9, and 10 SPARC

Solaris 10 (x86)

IBM AIX v5.2, v5.3, and v6.1

HP UX 11.23, 11.31 PA-RISC

HP-UX Itanium 11.23, 11.31, IA64

Tru64 v5.1b

You can install the Agent for Oracle on the following Linux operating systems:

Red Hat Enterprise Linux 3.x, 4.x, 5.x (x86/x64)

Red Hat Advanced Server 3.0

SuSE Enterprise Server 9.x, 10.x, and 11.x (x86/x64)

2.12 Supported Operating Systems for the Agent for Oracle (Windows)

You can install the CA ARCserve Backup Agent for Oracle (Windows) on the following operating systems, running the following versions of Oracle:

For Microsoft Windows Server 2000 SP4:
- Oracle Server version 9, 9i, 10g R1 or 10g R2, 11g R1
- Oracle Fail Safe (OFS):
  - Version 3.3.2 on 9i
  - Version 3.3.3 on 9i and 10g R1 or 10g R2
- Oracle RAC 9i, 10g R1, 10g R2

For Microsoft Windows Server 2003 (32-bit), Windows Server 2003 SP1 (32-bit), Windows Server 2003 SP2 (32-bit):
- Oracle Server version 9i, 10g R1 or 10g R2, 11g R1
- Oracle Fail Safe (OFS):
  - Version 3.3.3 on 9i and 10g R2
  - Version 3.3.4 on 10g R2 and 11g R1
- Oracle RAC 9i, 10g R1, 10g R2 and 11g R1

For Microsoft Windows Server 2003 R2 SP2 (32-bit):
- Oracle Server version 9i, 10g R1 or 10g R2, 11g R1
- Oracle Fail Safe (OFS):
  - Version 3.3.3 on 9i, 10g R1, 10g R2
  - Version 3.3.4 on 10g R1, 10g R2, 11g R1
- Oracle RAC 9i, 10g R1, 10g R2, 11g R1

For Microsoft Windows Server 2008 (32-bit), Windows Server 2008 SP1 (32-bit), Windows Server 2008 SP2 (32-bit):
- Oracle Server version 10gR2, 11gR1
- Oracle Fail Safe (OFS) version 3.3.4 on 10g R2
- Oracle Fail Safe (OFS) version 3.4.1 on 11g R1
- Oracle RAC 10g R2, RAC 11g R1

For Microsoft Windows 2003 (64-bit), Windows Server 2003 SP1 (64-bit), Windows Server 2003 SP2 (64-bit):
- Oracle Server version 10g R1, 10g R2, or 11g R1
- Oracle Fail Safe (OFS):
  - Version 3.3.4 on 10g R1, 10g R2
  - Version 3.4.1.2 on 11g R1
  - Version 3.4.1.4 on 11g R1
- Oracle RAC 10g R1, 10g R2, 11g R1
- Oracle 10g R2, 11g R1 WOW
- Oracle Fail Safe WOW
- Oracle RAC 10g R2 WOW

For Microsoft Windows Server 2003 R2 (64-bit), Microsoft Windows Server 2003 R2 SP2 (64-bit)
- Oracle Server version 10g R1, 10g R2, or 11g R1
- Oracle Fail Safe (OFS):
  - Version 3.3.3 on 10g R1, 10g R2
  - Version 3.3.4 on 10g R1, 10g R2
  - Version 3.4.1 on 11g R1
  - Version 3.4.1.4 on 11g R1
- Oracle RAC 10g R1, 10g R2, 11g R1
- Oracle 10g R2, 11g R1 WOW
- Oracle Fail Safe (OFS) WOW
- Oracle RAC 10g R2 WOW

For Microsoft Windows Server 2008 (64-bit), Microsoft Windows 2008 SP1 (64-bit), Microsoft Windows Server 2008 SP2 (64-bit):
- Oracle Server version 10g R2, 11g R1
- Oracle Fail Safe (OFS)
  - Version 3.4.1 on 10g R2
- Oracle RAC 10g R2,
- Oracle RAC 10g R2 WOW

For Microsoft Windows Server 2008 (64-bit), Microsoft Windows Servers 2008 SP1 (64-bit), Microsoft Windows Server 2008 SP2 (64-bit):
- Oracle Server version 10g R2, 11g R1
- Oracle Fail Safe (OFS) version 3.4.1 on 10g R2
- Oracle RAC 10g R2
- Oracle RAC 10g R2 WOW

For Microsoft Windows Server 2008 R2 (64-bit):
- Oracle Server version 11g R1
- Oracle Fail Safe (OFS) version 3.4.2 on 11g R2

For Microsoft Windows Server 2003 SP2 (IA64):
- Oracle Server version 9i, 10g R1, 10g R2
- Oracle Fail Safe (OFS) version 3.3.2, 3.3.3, or 3.3.4 on 9i
- Oracle Fail Safe (OFS) version 3.3.3 on 10g R1 or 10g R2
- Oracle Fail Safe (OFS) version 3.3.4 on 10g R1 or 10g R2
- Oracle RAC 9i, 10g R1, 10g R2
- Oracle RAC 9i 10g R2 WOW

2.13 Supported Operating Systems for the Agent for Open Files

You can install the Agent for Open Files on the following operating systems:

Windows 2000 x86, SP4, SP4 Rollup 1

Windows Vista (x86, x64) SP1, SP2

Windows XP Professional (x86) SP2, SP3 (x64) SP1, SP2

Windows Server 2003 Standard Edition (x86, x64,) SP1, SP2, R2, R2 SP2

Windows Server 2003 Enterprise Edition (x86, x64) SP1, SP2, R2, R2 SP2 (IA64) SP1, SP2

Windows Server 2003 Small Business Server (x86) SP1, SP2, R2, R2 SP2

Windows Server 2003 Web Edition (x86) SP1, SP2

Windows Server 2003 Datacenter (x86, IA64) SP1, SP2 (x64) SP1, SP2, R2, R2 SP2

Windows Server 2003 Storage Server (x86) SP1, SP2, R2, R2 SP2 (x64) R2, R2 SP2

Windows Server 2003 Cluster Server (x86, x64) SP1, SP2, R2, R2 SP2 (IA64) SP1, SP2

Windows Server 2008 Enterprise Edition (x86, x64) SP1, SP2

Windows Server 2008 Standard Edition (x86, x64) SP1, SP2

Windows Server 2008 Web Server Edition (x86, x64) SP1, SP2

Windows Server 2008 Core Server Edition (x86, x64) SP1, SP2

Windows Server 2008 Datacenter (x86, x64) SP1, SP2

Windows Server 2008 R2 (x64)

Windows Server 2008 R2 Core (x64)

Windows Server 2008 Cluster Server

Windows Server 2008 R2 Cluster Server

Windows 7 (x86, x64)

Agent for Microsoft Volume Shadow Copy Service (VSS)

The CA ARCserve Backup Agent for Open Files now includes functionality for the CA ARCserve Backup Agent for Microsoft Volume Shadow Copy Service (VSS). This agent is not supported on Windows XP systems.

2.14 Supported Operating Systems for the Agent for Sybase

You can install the CA ARCserve Backup Agent for Sybase on the following operating systems:

Windows 2000 Advanced Server SP4, SP4 Rollup 1 (x86)

Windows 2003 Enterprise, Standard, Data Center SP1, SP2 (x86)

Windows 2003 R2 Enterprise, Standard, Data Center SP2 (x86)

2.15 Supported Operating Systems for the Agent for Virtual Machines

You can install the Agent for Virtual Machines on the following operating systems:

Windows Server 2008 R2:
- Windows Server 2008 x64 R2 Standard, Enterprise, Datacenter and Web Server editions

Windows Server 2008:
- Windows Server 2008 x64 Standard, Enterprise, Datacenter, Web Server, HPC editions
- Windows Server 2008 x64 without Hyper-V Standard, Enterprise, Datacenter editions
- Windows Server 2008 x86 Standard, Enterprise, Datacenter, Web Server, HPC editions
- Windows Server 2008 x86 without Hyper-V Standard, Enterprise, Datacenter editions
- Windows Server 2008 x64 Service Pack 2 Standard, Enterprise, Datacenter, Web Server, HPC editions
- Windows Server 2008 x64 Service Pack 2 without Hyper-V Standard, Enterprise, Datacenter editions
- Windows Server 2008 x86 Service Pack 2 Standard, Enterprise, Datacenter, Web Server, HPC editions
- Windows Server 2008 x86 Service Pack 2 without Hyper-V Standard, Enterprise, Datacenter editions

Windows Server 2003:
- Windows Server 2003 x86 with Service Pack 2 Standard, Enterprise, Datacenter, Web Server editions
- Windows Server 2003 x64 with Service Pack 2 Standard, Enterprise, Datacenter editions

Windows Server 2003 R2:
- Windows Server 2003 R2 x86 with Service Pack 2 Standard, Enterprise, Datacenter, Web Server editions
- Windows Server 2003 R2 x64 with Service Pack 2 Standard, Enterprise, Datacenter editions

Windows Server 2000:
- Windows Server 2000 with Service Pack 4
- Windows Server 2000 Advanced Server with Service Pack 4

Windows 7:
- Windows 7 x86 Professional, Enterprise, Ultimate editions
- Windows 7 x64 Professional, Enterprise, Ultimate editions

Windows Vista:
- Windows Vista x86 with Service Pack 1 Business, Enterprise, Ultimate editions
- Windows Vista x64 with Service Pack 1 Business, Enterprise, Ultimate editions
- Windows Vista x86 with Service Pack 2 Business, Enterprise, Ultimate editions
- Windows Vista x64 with Service Pack 2 Business, Enterprise, Ultimate editions

Windows XP Professional:
- Windows XP Professional x86 Edition with Service Pack 3 (for VMs configured with 1 or 2 virtual processors)
- Windows XP Professional x86 Edition with Service Pack 2 (for VMs configured with 1 virtual processor)
- Windows XP Professional x64 with Service Pack 2 (for VMs configured with 1 or 2 virtual processors)

Windows Server 2008 Hyper-V:
- Windows Server 2008 Standard (x64) SP1, SP2
- Windows Server 2008 Enterprise (x64) SP1, SP2
- Windows Server 2008 Data Center (x64) SP1, SP2
- Windows Server 2008 R2 (x64)

VMware -- VMware Virtual Disk Development Kit (VDDK) and VCB Framework are independent software products provided by VMware. The Agent for Virtual Machines requires VDDK, VCB Framework, or both, to back up VMs hosted on ESX Server systems running the following applications:

VMware ESX/ESXi Server Version	VMware VCB Framework Version	VDDK Version	VMware vCenter Server Version
3.0	1.0, 1.0.1	--	--
3.0.1	1.0, 1.0.1, 1.0.2	--	--
3.0.2	1.0.3, 1.1, 1.1 Update 1, 1.5	--	2.0.2, 2.5
3.0.3, Update 1	1.0.3, 1.1, 1.1 Update 1, 1.5, 1.5 Update 1	--	2.0, 2.5, 4.0
ESX 3.5, Update 1, Update 2, Update 3, Update 4, Update 5 ESXi 3.5, Update 1, Update 2, Update 3, Update 4, Update 5	1.1, 1.1 Update 1, 1.5, 1.5 Update 1, 1.5 Update 2	1.1, 1.1.1	2.5 Update 1, Update 2, Update 3 and Update 4, Update 5, Update 6, and VMware vCenter Server 4.0, 4.0 Update 1, Update 2
VMware ESX Server 4.0 (vSphere), Update 1, Update 2 (Supports all editions)	1.5 Update 1, 1.5 Update 2	1.1, 1.1.1	VMware vCenter Server 4.0, Update 1, Update 2
ESXi 4.0, Update 1 Update 2 (Supports all editions)	1.5 Update 1, 1.5 Update 2	1.1, 1.1.1	VMware vCenter Server 4.0, Update 1, Update 2
ESX 4.1 (Supports all editions)	1.5 Update 2	1.1, 1.1.1, 1.2, 1.2.1	VMware vCenter Server 4.1
ESXi 4.1 (Supports all editions)	1.5 Update 2	1.1, 1.1.1, 1.2, 1.2.1	VMware vCenter Server 4.1

You can install Agent for Virtual Machines on all operating systems supported by VMware for VCB/VDDK proxy server, on all Windows guest operating systems supported by VMware (except Windows NT 4.0), on Microsoft Hyper-V host server, and on all Windows guest operating systems supported by Microsoft Hyper-V.

Notes:

CA ARCserve Backup supports Agent for Virtual Machines on all OS supported by VMware for VCB proxy server.

CA ARCserve Backup supports Agent for Virtual Machines on all Windows Guest Operating Systems supported by VMware, except Windows NT 4.0.

CA ARCserve Backup supports Agent for Virtual Machines on all Windows guest operating systems supported by Microsoft Hyper-V.

2.16 Supported Operating Systems for the Disaster Recovery Option

The Disaster Recovery Option supports the following methods:

Bootable floppy disaster recovery (only 32-bit supported)
- Windows 2000 Professional Edition SP4, SP4 Rollup1
- Windows 2000 Server Edition SP4, SP4 Rollup 1
- Windows 2000 Advanced Server Edition SP4, SP4 Rollup 1
Note: Use of a Japanese USB keyboard during bootable floppy disaster recovery is not supported on Windows 2000.

Windows 2000 does not support Disaster Recovery Option but does support Remote Disaster Recovery.

Bootable tape disaster recovery (only 32-bit supported)
- Windows 2003 Web Edition SP1, SP2
- Windows 2003 Standard Edition SP1, SP2, R2, R2 SP2
- Windows 2003 Enterprise Edition SP1, SP2, R2, R2 SP2
- Windows 2003 SBS Edition SP1, SP2, R2, R2 SP2
Note: Bootable tape disaster recovery from a USB tape drive is not supported on Windows 2000 and Windows XP.

Bootable media image disaster recovery
- Windows XP Professional Edition (x86 and x64)SP2, (x86) SP3
- Windows 2003 Web Edition SP1, SP2
- Windows 2003 Standard Edition (x86, x64, and IA64) SP1, SP2, R2, R2 SP2
- Windows 2003 Enterprise Edition (x86, x64, and IA64) SP1, SP2, R2, R2 SP2
- Windows 2003 Datacenter Edition (x86, x64, and IA64) SP1, SP2, R2, R2 SP2
- Windows 2003 SBS Edition SP1, SP2, R2, R2 SP2
Note: The version of Windows you use to generate the boot media should be the version of Windows installed on your machine.

Windows XP does not support Disaster Recovery Option but does support Remote Disaster Recovery.

The ARCserve bootable CD is a CD containing OS, CA ARCserve Backup, Machine-Specific Disk, Drivers for NIC and Mass Storage (SCSI/Fibre/RAID). For Windows 2008 systems only, the creation of a unified CD is not supported, but a bootable CD is supported. Machine-Specific Data may reside on a USB drive.

Bootable CD disaster recovery
- Windows 2000 Professional Edition SP4, SP4 Rollup 1
- Windows 2000 Server Edition SP4, SP4 Rollup 1
- Windows 2000 Advanced Server Edition SP4, SP4 Rollup 1
- Windows XP Professional Edition (x86 and x64) SP2, (x86) SP3
- Windows 2003 Web Edition SP1, SP2, R2, R2 SP2
- Windows 2003 Standard Edition (x86, x64, and IA64) SP1, SP2, R2, R2 SP2
- Windows 2003 Enterprise Edition (x86, x64, and IA64) SP1, SP2, R2, R2 SP2
- Windows 2003 Datacenter Edition (x86, x64, and IA64) SP1, SP2, R2, R2 SP2
- Windows 2003 SBS Edition SP1, SP2, R2, R2 SP2
- Windows Server 2008 SP1, SP2 (x86, x64, and IA64)
- Windows Server 2008 R2 (x64)
Create a Machine Specific Disk that contains network drivers if you need to perform disaster recovery remotely, on a member server of a SAN, or from a remote File System Device because you will likely face network connection problems at the time of a disaster recovery. You may re-create a Machine Specific Disk using the Disaster Recovery Create Boot Kit Wizard, if you realize later that you do not have network drivers. The procedure is the same as for initial creation.

Bootable CD DR is also supported on UEFI:
- Windows 2003 IA64
- Windows 2003 R2 IA64
- Windows Server 2008 x64
- Windows Server 2008 IA64
- Windows Server 2008 R2 x64
- Windows Server 2008 R2 IA64
Note: Windows 2000 and Windows XP does not support Disaster Recovery Option but does support Remote Disaster Recovery.

2.17 Supported Operating Systems for the Enterprise Module

You can install the Enterprise Module on the following operating systems:

Windows Server 2003 SP1, SP2, R2, R2 SP2

Windows Server 2003 x64

Windows Server 2003 R2 x64

Windows Server 2008 SP1, SP2

Windows Server 2008 R2 (x64 only)

Windows Server 2008 x64

Windows Server 2008 R2 x64

Windows Server 2008 x86

The Enterprise Module includes the following CA ARCserve Backup options, some of which may not be supported on all operating systems:

Image Option--Not supported on IA64 platforms for Windows Server 2003, 2008, 2008 R2
Note: The Enterprise Option does not support using the Image Option to recover system volumes from a disaster on all Windows Server 2008 operating systems (for example, drive C:\). This limitation applies when the backup includes only the system volume and you try to recover the system volume.

Serverless Backup Option--Not supported on Windows 2008 systems

Enterprise Option for IBM 3494--Disaster Recovery is NOT supported with this option. In addition, this option is NOT supported on x64 systems

Enterprise Option for StorageTek ACSLS--Disaster Recovery is supported for StorageTek ACSLS on Windows Server 2003 (x86 and x64) and Windows Server 2008 x86 platforms.

Enterprise Option for VSS Hardware Snap-Shot.
Note: For more information about the Enterprise Option for VSS Hardware Snap-Shot, see the CA ARCserve Backup Microsoft Volume Shadow Copy Service Guide.

2.18 Supported Operating Systems for the Enterprise Option for SAP R/3 for Oracle

You can install the Enterprise Option for SAP R/3 for Oracle on the following operating systems:

Windows 2003 Enterprise Edition Service Pack 1, Service Pack 2, R2 Service Pack 2 with BR*TOOLS 6.2, 6.4 for Oracle 9i or BR*TOOLS 7.0 for Oracle 10g

Windows 2003 Enterprise x64 Edition Service Pack 1, Service Pack 2, R2 Service Pack 2 with BR*TOOLS 6.4 for Oracle 9i 32-bit or BR*TOOLS 7.0 for Oracle 10g 32-bit, 64-bit

Windows 2003 Enterprise Edition IA64 Service Pack 1, Service Pack 2 with BR*TOOLS 6.4 for Oracle 9i or BR*TOOLS 7.0 for Oracle 10g

Windows 2000 Service Pack 4 with BR*TOOLS 6.2 for Oracle 9i

Notes:

SAPDBA or BR*TOOLS should be installed on the same machine as the agent BACKINT option.

SAP R/3 for Windows is required.

BR*TOOLS 4.6X is no longer supported.

For use with the Agent for SAP, BR*TOOLS 6.4 for Oracle 9i 32-bit on Windows 2003 Enterprise x64 Edition systems, ensure the Oracle release is 9.2.0.8 or later (32-bit).

2.19 Supported Operating Systems for the NDMP NAS Option

You can install the NDMP NAS Option on the following operating systems:

Windows Server 2003 SP1, SP2, R2, R2 SP2 (x86 and x64)

Windows Server 2008 SP1, SP2 (x86 and x64)

Windows Server 2008 R2 (x64 only)

2.20 Supported Operating Systems for the Storage Area Network (SAN) Option

You can install the Storage Area Network (SAN) Option on the following operating systems:

Windows Server 2003 SP1, SP2, R2, R2 SP2

Windows Server 2008 SP1, SP2, R2

2.21 Supported Operating Systems for SRM

The Storage Resource Management features are supported on all Windows Server 2000 systems (and later).

Note: The Alert when PKI is Reaching Threshold feature is supported on x64 and x86 systems only; it is not supported on IA64 systems.

2.22 Supported Operating Systems for the Tape Library Option

You can install the Tape Library Option on the following operating systems:

Windows Server 2003 SP1, SP2, R2, R2 SP2

Windows Server 2008 SP1, SP2, R2

2.23 Supported Operating Systems for CA ARCserve Backup UNIX and Linux Data Mover

The CA ARCserve Backup UNIX and Linux Data Mover is supported on the following operating systems:

Red Hat Enterprise Linux (x86/IA64/x64)
- 3.x
- 4.x
- 5.x

SuSE Enterprise Linux (x86/IA64/x64)
- 9.x
- 10.x
- 11.x
- Linux OES2 (x86/x64)

AIX
- 5.2
- 5.3
- 6.1

HP-UX
- 11.23 (PA-RISC/IA64)
- 11.31 (PA-RISC/IA64)

Solaris
- SPARC 9
- SPARC 10

2.24 Supported Operating Systems for CA ARCserve Backup Dashboard

CA ARCserve Backup Dashboard supports all operating systems listed for the base product, except Itanium-based platforms because the required Microsoft .NET Framework v3.5 SP1 is not supported by these systems. In addition, CA ARCserve Backup Dashboard supports the following email clients:

Microsoft Outlook 2003

Microsoft Outlook 2007

For Outlook Express running on Windows 2003 systems, email formatting is not retained with default view settings. To retain formatting, enable the Message in HTML option from the Outlook Express View menu while the email is open.

2.25 Supported Operating Systems for the CA ARCserve Backup Global Dashboard

CA ARCserve Backup Global Dashboard is supported on the following operating systems:

Central Primary Server:

The requirements for a CA ARCserve Backup primary/standalone server to be designated and configured as a Central Primary Server are as follows:

CA ARCserve Backup must be configured to use SQL Server 2005/2008/2008 R2 as the CA ARCserve Backup database.

CA ARCserve Backup Global Dashboard can be installed on any of the Windows operating system versions supported by CA ARCserve Backup Dashboard.

Branch Primary Server:

The requirements for a CA ARCserve Backup primary/standalone server to be designated and configured as a Branch Primary Server are as follows:

CA ARCserve Backup Global Dashboard can be installed on any of the Windows operating system versions supported by CA ARCserve Backup Dashboard.

Global Dashboard Console:

The requirements for a machine to be designated and configured as a Global Dashboard Console are as follows:

CA ARCserve Backup Global Dashboard Console can be installed on any of the Windows operating system versions supported by CA ARCserve Backup Manager except Itanium-based systems.

2.26 Supported Operating Systems for CA ARCserve Backup Infrastructure Visualization

CA ARCserve Backup Infrastructure Visualization supports all operating systems listed for the base product except Itanium-based platforms because the required Microsoft.NET Framework v3.5 SP1 is not supported by these systems.

2.27 Supported Virtualization Platform for CA ARCserve Backup

VMware ESX Server (x86 and x64) version 3.0, 3.0.1, 3.0.2, 3.0.3

VMware ESX Server 3.5, Update 1, Update 2, Update 3, Update 4, Update 5

VMware ESXi version 3.5, Update 1, Update 2, Update 3, Update 4, Update 5

VMware ESX Server 4.0 (vSphere), Update 1, Update 2, ESX 4.1

VMware ESXi version 4.0 (vSphere), Update 1, Update 2, ESXi 4.1, ESXi 3.5, Update 1, Update 2, Update 3, Update 4, Update 5

VMware ESX Server 2.5, 2.5.4

VMware GSX Server version 3.0, 3.1

VMware Server version 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 2.0, 2.0.1, 2.0.2

VMware Workstation version 4.0, 4.5, 5.0, 5.5, 6.0, 7.0

Microsoft Virtual PC 2007 (x86 only)

Microsoft Virtual Server 2005 R2 SP1 (x86 and x64)

Microsoft Hyper-V Server 2008 x64, 2008 x64 SP2, 2008 R2

Citrix XenServer 5.0, 5.5, 5.6

Citrix XenApp 5.0, 5.0 Feature Pack 1, 5.0 Feature Pack 2, 6.0

Note: All components of the ARCserve which are supported inside operating systems running on a physical machine, are also supported inside the same Guest operating system running on the above virtualization platform.

3.0 System Requirements

The following sections provide information about the minimum system requirements for each CA ARCserve Backup component.

3.1 System Requirements for the CA ARCserve Backup Base Product

The minimum system requirements for CA ARCserve Backup are:

CPU: 600 MHz Pentium III-compatible or faster processor; 1 gigahertz (GHz) or faster processor recommended

RAM: 512 MB, 1 GB or more recommended

Disk Space:
- Primary Server: 800 MB, plus 1.3 GB for Agent Deployment Packages
- Member Server: 450 MB, plus 1.3 GB for Agent Deployment Packages

This version of CA ARCserve Backup installs the following .NET components:
- .NET 2.0 SP2 up to 500 MB of available disk space may be required
- .NET 3.0 SP1 up to 500 MB of available disk space may be required
- .NET 3.5 SP1 up to 500 MB of available disk space may be required.

To perform backup jobs for Transportable Shadow Copies using the Microsoft Exchange Server writer, you must have Microsoft Exchange Server installed on your CA ARCserve Backup server. Backups of this type will fail if the Microsoft Exchange Server is not installed on the CA ARCserve Backup server.

Microsoft .NET Framework

CA ARCserve Backup requires the following versions of Microsoft .NET Framework.

Microsoft .NET Framework 3.5 SP1 on Windows Server 2003, and Windows Server 2008 systems

CA ARCserve Backup Database

CA ARCserve Backup supports the following applications to host the CA ARCserve Backup database (ASDB):

Microsoft SQL Server 2008 Express Edition. This is the default CA ARCserve Backup database application.
Note: To install Microsoft SQL Server 2008 Express Edition on Windows Server 2003 systems, SP2 is required. Otherwise, you must install a supported version of Microsoft SQL Server to host the CA ARCserve Backup database.

Microsoft SQL Server 2008 Enterprise/Standard Edition

Microsoft SQL Server 2008 R2 Enterprise/Standard/Express Edition

Microsoft SQL Server 2000 with Service Pack 4

Microsoft SQL Server 2005 with Service Pack 1, Service Pack 2 or Service Pack 3
Note: In addition to these requirements, you should consider the disk space necessary for the default CA ARCserve Backup database. Depending upon usage, the database can grow to several GB in size.

Adobe Reader

Adobe Acrobat Reader 8 and later

Internet Browser

Internet Explorer 6.0 SP1

Internet Explorer 7.0

Internet Explorer 8.0 (all rendering modes)

3.2 System Requirements for CA ARCserve Backup and CA ARCserve Replication Integration

No additional hardware is required beyond the Minimum Requirements previously listed.

In addition to the file protection, CA ARCserve Backup and CA ARCserve Replication integration supports data protection for the following:

Microsoft Exchange Server 2000 Standard SP4

Microsoft Exchange Server 2003 Standard SP1 and SP2

Microsoft Exchange Server 2007 SP1

Microsoft Exchange Server 2010

Microsoft SQL Server 7.0 Standard Edition and Enterprise Edition SP4

Microsoft SQL Server 2000 Standard Edition SP2, SP3, SP3A, and SP4

Microsoft SQL Server 2005 SP1, SP2, SP3

Microsoft SQL Server 2008 SP1

For more information about integration, refer to the CA ARCserve Backup for Windows CA ARCserve Replication Integration Guide.

3.3 System Requirements for the CA ARCserve Backup Client Agents

No additional hardware is required beyond the Minimum Requirements previously listed.

To install the agents, your system must meet the following minimum hardware requirements. For more details, see the CA ARCserve Backup Client Agents Readme.

Windows-based platforms:
- CPU: 200 MHz
- RAM: 256 MB
- Disk Space: 100 MB

Windows IA64 platforms:
- CPU: 200 MHz
- RAM: 256 MB
- Disk Space: 100 MB

Netware-based platforms:
- CPU: Netware versions 5.1 SP8, 6.0 SP5, 6.5 SP7, 6.5 SP8 require a Pentium-class processor with at least 512 MB RAM
- Disk Space: 20 MB

UNIX-based platforms:
- CPU: 1 GHz
- RAM: 256 MB
- Disk Space: 25 MB on the client agent installation file system, 25 MB (temporary) on /var/tmp file system

Linux-based platforms:
- CPU: 500 MHz
- RAM: 256 MB
- Disk Space: 25 MB

Mac OS X
- RAM: 128 MB
- Disk Space 10 MB

3.4 System Requirements for the Agent for IBM Informix

The CA ARCserve Backup Agent for IBM Informix also requires the following:

Informix Dynamic Server 10.00, 11.10, or 11.50

IBM Informix-Connect is installed and working properly

3.5 System Requirements for the Agent for Lotus Domino

The Agent for Lotus Domino requires the following:

CPU: 512 MHz

RAM: 512 MB

Disk Space: 10 MB

3.6 System Requirements for the Agent for Microsoft Exchange Server

Note: The Agent now installs the Exchange Database Level Agent with the Exchange Document Level Agent.

To install the Agent for Microsoft Exchange Server, the following hardware must be available and configured according to the version of Microsoft Exchange Server you are running:

The basic Microsoft Exchange Server hardware requirements (for information about these requirements, see the Microsoft website)

CPU:
- 166 MHZ if using Exchange Server 2000
- 133 MHz if using Exchange Server 2003
- 800 MHz if using Exchange Server 2007
- any 64-bit CPU if using Exchange Server 2010 (IA64 systems are not supported)

RAM:
- At least 512 MB if using Microsoft Exchange Server 2000, 2003
- At least 2 GB if using Microsoft Exchange Server 2007
- At least 4 GB if using Microsoft Exchange Server 2010

Disk Space: At least 50 MB, with at least 30 MB on hard disk where Exchange Server Agent is installed and at least 20 MB on the system drive
Note: You must meet the basic CA ARCserve Backup product requirements before you install the agent and CA ARCserve Backup on the same machine. For updated information about these requirements, contact CA Support at ca.com.

3.7 System Requirements for the Agent for Microsoft SharePoint Server

To install the Agent for Microsoft SharePoint Server, the following hardware must be available and configured according to the version of Microsoft SharePoint Server 2007 or 2010 you are running:

The basic Microsoft SharePoint Server 2007 or 2010 hardware requirements (for information about these requirements, see the Microsoft website). The product only supports SharePoint 2010 RC version.

CPU: 2.5 GHz

RAM: 2 GB

Disk Space: At least 50 MB, with at least 30 MB on hard disk where the Agent for SharePoint Server is installed and at least 20 MB on the system drive.

Note: You must meet the basic CA ARCserve Backup product requirements before you install the Agent and CA ARCserve Backup on the same machine. For updated information about these requirements, contact CA Support.

The agent does not require the CA ARCserve Backup server component.

The Agent for Microsoft SharePoint Server requires at least one of the following:

Microsoft SharePoint Server 2007, SP1, SP2 (see Notes, below)

Microsoft SharePoint Services 3.0 SP1, SP2

Microsoft SharePoint Server 2010

Microsoft SharePoint Foundation 2010

Notes:

If running Microsoft SharePoint Server 2007 with SQL Server as database server, apply SP2 to SQL Server.

If running Microsoft SharePoint Server 2007 with SQL Server Express as database server, apply SP2 to SQL Server Express.

3.8 System Requirements for the Agent for Microsoft SQL Server

For the Agent for Microsoft SQL Server, ensure your system meets the minimum system requirements established for the CA ARCserve Backup base product.

3.9 System Requirements for the CA ARCserve Backup for Microsoft Windows Essential Business Server

To run CA ARCserve Backup for Microsoft Windows Essential Business Server, your system must meet the same requirements Microsoft sets for running Windows EBS.

3.10 System Requirements for the CA ARCserve Backup Small Business Server Editions

For the CA ARCserve Backup Small Business Server Editions, ensure your system meets the following requirements:

Small Business Server Standard Edition
- CPU: at least 750 MHz, 1 GHz recommended
- RAM: at least 512 MB, 1 GB recommended
- Disk Space: 16 GB
The following agents/options are included in the CA ARCserve Backup Small Business Server Standard Edition:
- Base Product
- Client Agent for Microsoft Windows
- Agent for Microsoft Exchange Server
- Agent for Microsoft SharePoint Server
- Agent for Open Files

Small Business Server Premium Edition
- CPU: at least 750 MHz, 1 GHz recommended
- RAM: at least 512 MB, 1 GB recommended
- Disk Space: 16 GB
The following agents/options are included in the CA ARCserve Backup Small Business Server Premium Edition:
- Base Product
- Client Agent for Microsoft Windows
- Agent for Microsoft Exchange Server
- Agent for Microsoft SQL Server
- Agent for Microsoft SharePoint Server
- Agent for Open Files

3.11 System Requirements and Oracle Database Support for the Agent for Oracle (UNIX/Linux)

The following sections provide the minimum system requirements and Oracle Database support for the Agent for Oracle on UNIX platforms.

Note: To obtain the latest patches and downloads for the CA ARCserve Backup Agent for Oracle on UNIX platforms, see the CA Support site at http://ca.com/support.

Sun Solaris SPARC:

On Sun Solaris SPARC, the agent requires the following:

Sun UltraSPARC models

256 MB RAM

250 MB disk space

Sun Solaris x86:

On Sun Solaris x86, the agent requires the following:

Sun x86 models

256 MB RAM

25 MB disk space

IBM AIX:

On IBM AIX, the agent requires the following:

IBM RISC 6000 models

256 MB RAM

250 MB disk space

HP-UX:

On HP-UX, the agent requires the following:

HP 9000 Server/Workstation

256 MB RAM

250 MB disk space

HP-UX Itanium:

On HP-UX Itanium, the agent requires the following:

HP IA64 models

256 MB RAM

250 MB disk space

HP/Compaq OSF Tru64:

On OSF Alpha, the agent requires the following:

HP/Compaq Alpha models

256 MB RAM

25 MB disk space

Database Support on UNIX platforms

You can use the agent with the following databases:

Oracle 9.0.1, 9.0.1.1, 9.2.0

Oracle 10.1.0 (10g) and 10.2 (10g R2)

Oracle 11.1 (11gR1)

Note: Oracle 11g is supported on Sun Solaris SPARC, HP-UX Itanium, HP UNIX and AIX platforms. You must install the 6800649 Oracle patch available from the Oracle Metalink website for AIX5L and AIX6L Based Systems (64-bit).

The following sections provide the minimum system requirements and Oracle Database support for the Agent for Oracle on Linux platforms:

Linux x86:

To use the Agent for Oracle on Linux x86 platforms, you must satisfy the following minimum system requirements:

x86 an compatible platform machines

500 MHz CPU

256 MB RAM

250 MB free disk space

Linux x64:

To use the Agent for Oracle on Linux x64 platforms, you must satisfy the following minimum system requirements:

AMD64 platform machines

1 GHz CPU

256 MB RAM

250 MB free disk space

Linux Itanium:

To use the Agent for Oracle on Linux Itanium platforms, you must satisfy the following minimum system requirements:

Itanium platform machines

1 GHz CPU

512 MB RAM

250 MB free disk space

Database Support on Linux platforms

You can use the agent with the following databases:

Oracle 9.0.1, 9.0.1.1, and 9.2.0

Oracle 10.1.0 (10g), 10.2 (10g R2)

RAC 9i and 10g, OCFS on Red Hat 3.0

Oracle 10g (10.1.0.3) 64 bit on Red Hat 3.0 IA64

Oracle10g (10.1.0.3.0) 64 bit on SuSE Enterprise Server 9.0 AMD64

Oracle 10g (10.2.0.1.0) on SuSE Enterprise Server 10, SuSE Enterprise Server 11

Oracle Database 11gR1 on SuSE Enterprise Server 10 SP1, RedHat 4 Update 5 and RedHat 5 Update 3

Oracle Database 11gR2 32 bit on RedHat 5 Update 3 x86

Oracle Database 11gR2 64 bit on RedHat 5 Update 3 x64

3.12 System Requirements for the Agent for Oracle (Windows)

To install the Agent for Oracle, the following hardware must be available and configured according to the version of Oracle Database you are running:

The basic hardware requirements (for information about these requirements, see the Oracle website)

CPU: 200 MHz

RAM: at least 512 MB if using Oracle 9i/10gR1/R2, and at least 1 GB if using Oracle 11g R1

Disk Space: at least 2 GB for Oracle 9i/10gR1/R2, and 5 GB for Oracle 11g R1, with at least 30 MB on hard disk where Oracle Agent is installed

Note: The CA ARCserve Backup Agent for Oracle allows you to perform backups in two modes: RMAN Mode and File-based Mode. In RMAN Mode, you can submit jobs from the interface or from the RMAN command line console. The RMAN mode of the CA ARCserve Backup Agent for Oracle supports Automatic Storage Management (ASM) for backup jobs submitted using both the CA ARCserve Backup Manager Console and the RMAN (Oracle Recovery Manager) Command Line Console. The file-based mode of the CA ARCserve Backup Agent for Oracle does not support this.

3.13 System Requirements for the Agent for Open Files

For the Agent for Open Files, ensure your system meets the CA ARCserve Backup base product requirements. In addition, you should have at least 1.5 MB of disk space available for this agent.

For NetWare operating systems, the following is required:

To manage the Agent for Open Files on NetWare servers, the Novell NetWare Client software must be installed.
Note: The agent does not support the Microsoft NetWare Client.

The Agent for Open Files NetWare Server Engine requires a server running Novell NetWare version 5.1 SP8, 6.0 SP5, 6.5 SP7, or 6.5 SP8.

3.14 System Requirements for the Agent for Sybase

For the Agent for Sybase, ensure your system meets the CA ARCserve Backup base product minimum requirements. You should also have the appropriate version of Sybase with Sybase Open Client Library and Backup Server for Sybase Adaptive Server installed, correctly configured, and working properly.

3.15 System Requirements for the Agent for Virtual Machines

For the Agent for Virtual Machines, system requirements depend upon where the Agent is installed:

If the Agent for Virtual Machines is installed on the same server as the base product, the Agent requires the same hardware specified for the base.

If the Agent is installed on a remote node, the Agent requires the same hardware specified for the Client Agent for Windows.

3.16 System Requirements for the Central Management Option

For the Central Management Option, ensure your system meets the CA ARCserve Backup base product minimum requirements.

3.17 System Requirements for the Disaster Recovery Option

For the Disaster Recovery Option, ensure your system meets the minimum requirements established for the CA ARCserve Backup base product. In addition, you should have at least 70 MB of disk space available.

3.18 System Requirements for the Enterprise Module

For the Enterprise Module, ensure your system meets the CA ARCserve Backup base product minimum requirements.

You must license the Enterprise Module for access to the following options and features:

Enterprise Option for IBM 3494--Requires the IBM LIbrary Manager Control Service version 5.4.8

Enterprise Option for StorageTek ACSLS--Requires LibAttach software

Image Option--Not supported on IA64 platforms for Windows Server 2003, 2008, 2008 R2

Multistreaming backups with more than one stream of backup data; for disk staging backups, more than two streams of backup data

Media Management Option (MMO)

Raw backup and restore of physical disks and volumes

Enterprise Option for VSS Hardware Snap-Shot
Note: For more information about the Enterprise Option for VSS Hardware Snap-Shot, see the CA ARCserve Backup Microsoft Volume Shadow Copy Service Guide.

3.19 System Requirements for the Enterprise Option for IBM 3494

The Enterprise Option for IBM 3494 is now supported by the Enterprise Module.

3.20 System Requirements for the Enterprise Option for SAP R/3 for Oracle

To install the Enterprise Option for SAP R/3 for Oracle, the following hardware must be available and configured according to the version of Oracle Database you are running:

The basic hardware requirements (for information about these requirements, see the Oracle website)

CPU: 200 MHz

RAM: at least 256 MB (512 recommended by Oracle) if using Oracle 9i/10gR1/R2

Disk Space: at least 2 GB for Oracle 9i/10gR1/R2, with at least 30 MB on hard disk where Enterprise Option for SAP R/3 for Oracle is installed.

3.21 System Requirements for the Enterprise Option for StorageTek ACSLS

The Enterprise Option for StorageTek ACSLS is now supported by the Enterprise Module.

3.22 System Requirements for the Image Option

The Image Option is now supported by the Enterprise Module.

Note: Image Option--Not supported on IA64 platforms for Windows Server 2003, 2008, 2008 R2.

3.23 System Requirements for the NDMP NAS Option

For the NDMP NAS Option, ensure your system meets the minimum requirements established for the CA ARCserve Backup base product. In addition, the following software requirements may apply, depending upon the devices you choose:

For Network Appliance devices:
- ONTAP Minimum Version 6.0.1R3
- NAS Server: Models FAS 250 series, N3700 series, F700 series, F800 series (ONTAP Version is of primary concern, not the model)

For EMC (IP4700) devices:
- Minimum firmware version R2.0 p21
- NAS Server Model: IP4700

For EMC (Celerra) devices:
- Minimum file server version 4.2.9.0
- NAS Server model: Celerra

For PROCOM devices:
- Minimum firmware version: 4.1.3
- NAS Server Model: NetForce 1000 series, 3000 series

Note: The NDMP NAS Option now supports x64 CA ARCserve Backup servers to back up NAS filers. However, Itanium platforms are not supported.

3.24 System Requirements for the Serverless Backup Option

Serverless Backup is now supported by the Enterprise Module.

3.25 System Requirements for the Storage Area Network (SAN) Option

For the Storage Area Network (SAN) option, ensure your system meets the minimum requirements established for the CA ARCserve Backup base product.

You must also install the following applications before installing the CA ARCserve Backup Storage Area Network (SAN) Option:

CA ARCserve Backup for Windows (Primary Server)

CA ARCserve Backup Central Management Option

CA ARCserve Backup Tape Library Option

3.26 System Requirements for the Tape Library Option

For the Tape Library Option, ensure your system meets the minimum requirements established for the CA ARCserve Backup base product.

CA ARCserve Backup for Windows must be installed before you install the CA ARCserve Backup Tape Library Option.

Note: The following capabilities have been incorporated into the Tape Library Option:

Optical Library Support

Tape RAID Support

3.27 System Requirements for the CA ARCserve Backup UNIX and Linux Data Mover

The CA ARCserve Backup UNIX and Linux Data Mover includes Java 1.6 technology that may require your HP-UX system to be at a specific patch level. For the most current information regarding patches, go to the HP website and apply any required patches before you install the CA ARCserve Backup Data Mover on HP-UX systems.

HP-UX PA-RISC/Itanium 11.23, the patch PHSS_37201 or higher is required

HP-UX PA-RISC/Itanium 11.31, the patch PHSS_37202 or higher is required

For AIX systems, the following are required:

For AIX 5.2, the fix package 5200-08 or higher is required

For AIX 5.3, the fix package 5300-07 or higher is required

For AIX 6.1, the base level 6100-GOLD is required

xlc.rte 9.0.0.0 or higher is needed for all AIX platforms.

For more information, go to the IBM's Fix Central website and search for the version appropriate for your operating system.

The following table describes the minimum hardware requirements for the CA ARCserve Backup UNIX and Linux Data Mover:

Platform	Architecture	RAM	Free Disk Space	Free Disk Space in /tmp
Solaris	SPARC	256 MB	250 MB	400 MB
IBM AIX	Power PC	256 MB	250 MB	400 MB
HP-UX	PA-RISC, IA64	256 MB	250 MB	400 MB
Linux	x86, IA64, and X64	256 MB	250 MB	400 MB

3.28 System Requirements for CA ARCserve Backup Dashboard

No additional hardware is required beyond the Minimum Requirements previously listed.

3.29 System Requirements for the CA ARCserve Backup Global Dashboard

The following section provides information about the minimum system requirements for CA ARCserve Backup Global Dashboard.

System Requirements for the Central Primary Server

The minimum system requirements for CA ARCserve Backup Global Dashboard to be installed as the Central Primary Server are:

CA ARCserve Backup Database

For the Central Primary Server, Global Dashboard must be installed with CA ARCserve Backup using Microsoft SQL Server as its database. (Microsoft SQL Server Express and Microsoft SQL Server 2000 is not supported for the Central Primary Server).

Microsoft SQL Server 2008

Microsoft SQL Server 2008 R2

Microsoft SQL Server 2008 R2 Express

Microsoft SQL Server 2005

Note: In addition to these requirements, you should consider the disk space necessary for the default CA ARCserve Backup database. Depending upon usage, the database can grow to several GB in size.

System/processor:

Server with at least a Dual Core Processor (2.8 GHz) or better

Memory:

4GB or more (recommended)

Disk Space:

Sufficient CA ARCserve Backup database capacity for your Global Dashboard environment:
As each branch site uploads data to the central CA ARCserve Backup database on a daily basis, it is estimated that the central CA ARCserve Backup database will increase by approximately 4 MB for every 100 nodes (assuming 4 volumes in each node) every day (or 1MB for every 100 sessions every day).

The number of sessions is calculated by multiplying the number of nodes by the average number of volumes in a node. The number of days of database retention time is determined by the branch CA ARCserve Backup setup.

You can calculate the approximate required disk space at the central site by multiplying the estimated daily CA ARCserve Backup database growth (1MB for every 100 sessions) by the number of days of database retention time.

For example:

If you have 10 branch sites with each site having 10 nodes and each node contains 4 volumes, then the central CA ARCserve Backup database will increase by 4MB every day. If the database record is retained for 180 days, then the central CA ARCserve Backup database will need to be 720MB.
- 10 branch sites x 10 nodes x 4 volumes = 400 sessions
- 400 sessions = 4MB database space growth per day (1MB per 100 sessions)
- 4MB daily growth x 180 database retention days = 720MB total database space required for the central CA ARCserve Backup database.
Note: Any database pruning that is performed at a branch CA ARCserve Backup database will be reflected in the central CA ARCserve Backup database the next time data synchronization is performed.

Adobe Reader

Adobe Reader 8 or later

Email clients

Global Dashboard supports the following email clients on the Central Primary Server:

Microsoft Outlook 2003

Microsoft Outlook 2007

Outlook Express

Windows Mail

System Requirements for a Branch Primary Server

No additional hardware or software is required beyond the Minimum Requirements for any CA ARCserve Backup primary server.

CA ARCserve Backup Database

For a Branch Primary Server, Global Dashboard must be installed with CA ARCserve Backup using Microsoft SQL Server or Microsoft SQL Server Express Edition as its database.

Microsoft SQL Server 2008

Microsoft SQL Server 2005

Microsoft SQL Server 2008 Express

Microsoft SQL Server 2000

3.30 System Requirements for CA ARCserve Backup Infrastructure Visualization

No additional hardware is required beyond the minimum requirements previously listed.

3.31 System Requirements for CA ARCserve Backup Infrastructure Global Visualization

For the CA ARCserve Backup Infrastructure Global Visualization, ensure your system meets the CA ARCserve Backup Global Dashboard requirements.

4.0 Installation Considerations

The following sections provide information about installation prerequisites, configurations, and issues to consider before installing CA ARCserve Backup and its agents and options.

4.1 Installation Considerations for the CA ARCserve Backup Base Product

The following section provides information about installation prerequisites, configurations, and issues to consider before installing the CA ARCserve Backup base product.

.NET Framework 3.5 SP1 installation may fail on computers that have .NET Framework 2.0 or 2.0 SP1 installed on Windows Server 2003 machines.

If you wish to install CA ARCserve Backup components in a custom location, you must specify separate destination folder names for each component.

CA ARCserve Backup installs its services under the Local System Account. By default, the option Allows Service to Interact with Desktop is not selected.

To install CA ARCserve Backup, you must log into your computer using an administrator account or a user account with administrator privileges.

If you are prompted to reboot your machine during the remote installation process, you must reboot the machine manually for the remote installation to be successful.

If you are installing CA ARCserve Backup agents on a machine where InoculateIT or Antivirus is running, the following driver update must be applied to both the CA ARCserve Backup server and the client machine:
http://supportconnectw.ca.com/premium/antivirus/downloads/nt/4.5/ildrvupdate.asp

When you create equivalences using ca_auth.exe, these equivalences are created for user names according to the Windows domain to which they belong. For example, the equivalence for Domain1\User1 is different from WinDomain2\User1 and from User1. By default, all command line utilities detect the domain name of the logged in user to validate access. To allow backward compatibility, existing equivalences without domain names are also accepted. However, this can introduce a security risk for your environment because a user with the same name but belonging to another Windows domain can use the command line utilities. We recommend that you delete existing equivalences and recreate them for all users to ensure that the correct domain name is included.

When upgrading to this release from previous releases of CA ARCserve Backup, decide if you wish to keep the old ARCserve Manager:
- If you wish to keep the old ARCserve GUI Manager, you must provide an upgrade installation location that is different from the previous installation.
- If you wish to install the upgrade to the same location, you cannot keep the old GUI manager.

To protect SQL Server instances in a cluster-aware environment, you must manually install the Agent for Microsoft SQL Server on all of the cluster nodes.

Effective with this release, CA ARCserve Backup installs SQL Express 2008 as the CA ARCserve Backup database when SQL Express is selected. This is listed as the "Default database" on the configuration screen during setup. SQL Express 2005 is no longer supported. You must also install Microsoft Installer 4.5, which is a prerequisite for installing SQL Express 2008. This installation requires a system reboot.
Note: For local installations, Setup continues the installation from the point of the restart. However, for remote installations and silent installations, Setup terminates your installation at the point of the restart. You must then start Setup manually after the system restarts.

Case-sensitive collation is supported only on fresh installations, or upgrades that overwrite the CA ARCserve Backup database instance. If you are upgrading over an existing SQL Server Express ASDB instance, make sure instance collation is set to case-insensitive or some functions will not work. See the Microsoft documentation or website for more information on setting collation.

During the setup process, an item for CA ARCserve Backup for Windows for Microsoft Small Business Server appears only when you install CA ARCserve Backup to the same machine on which Microsoft Small Business Server is also installed. Otherwise, you may apply the license via the CALicnse.exe program. See the Online Help for more information on the CALicnse.exe program.

Response file cannot be created on Windows Server 2008 Core system. You must create the response file on another machine and copy it to the Windows Server 2008 Core machine to run the silent install.

When you uninstall r11.5, multiple messages are recorded in the Event Viewer. You can avoid this problem by performing the following steps before upgrading or installing the current version:
1. Create a key called MessageEngine under:
  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Admin
2. Create a DWORD value called Impersonate under:
  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Admin\MessageEngine
3. Set Impersonate to 0.
4. Reboot the Windows system.

Choosing the CA ARCserve Backup Express Install option installs Microsoft SQL Express 2008 as the CA ARCserve Backup database.

When installing CA ARCserve Backup as a Member Server on Windows Server 2008 Core, you should run mastersetup.exe directly from DVD\Install. If you use setup.exe from the DVD root, you will launch DemoShield, which requires Internet Explorer 5 or later to run. Internet Explorer is not available in Windows Server 2008 Core operating systems.

When performing a local install of CA ARCserve Backup, ensure all CA ARCserve Backup products are from the same release if you are using the SDO or silent install options. You can check release information from Support Information under the Add/Remove option for CA ARCserve Backup products.

Uninstalling Agent Deployment can be achieved by deleting files from the Agent Deployment folder to free up disk space. The folder is located in the CA ARCserve Backup installation directory, in the Packages folder. If you need to launch Agent Deployment later, you will be prompted to insert the source media to copy files.

When installing CA ARCserve Backup, you will be required to reboot your system if any version of eTrust prior to 8.0 is installed.

When installing CA ARCserve Backup on Windows Server 2008 systems, ensure that you have no users named "user" in the domain or logging on to CA ARCserve Backup using Windows authentication will fail. If a user so named exists, delete the account from Windows and User Profile Management and use another Windows account to log on to CA ARCserve Backup.

When installing SQL Express 2008 as the CA ARCserve Backup database, the application Event Log shows numerous error messages. This is a known Microsoft issue and does not affect the operation of CA ARCserve Backup.

System requirements for the Disk to Disk to Tape feature: process disk staging backups using multistreaming in more than two streams of backup data, you must license the CA ARCserve Backup Enterprise Module.

Setup must restart your system when you install the CA ARCserve Backup base product and deploy Microsoft SQL Server 2008 Express Edition to support the CA ARCserve Backup database. After your system restarts, Setup continues the installation from the point of the restart. This behavior presents a problem when the installation media is mounted to a DVD drive that is configured as a network share on a remote computer. Setup cannot locate the installation media after the restart and cannot continue from the point of the restart. To complete the installation, you must run Setup and start the installation process from the Installation Browser. There is no remedy for this problem.

4.2 Installation Considerations for CA ARCserve Backup for Microsoft Windows Essential Business Server

This release of CA ARCserve Backup lets you integrate Microsoft Windows Essential Business Server 2008, English with CA ARCserve Backup. For information about Windows Essential Business Server 2008 configurations and how you can use CA ARCserve Backup to protect Windows Essential Business Server 2008 implementations, see the appendix "Using CA ARCserve Backup for Microsoft Windows Essential Business Server" in the CA ARCserve Backup for Windows Administration Guide.

This following list provides information about installation prerequisites to consider before installing CA ARCserve Backup for Microsoft Windows Essential Business Server 2008:

Ensure that your system meets the minimum system requirements to install CA ARCserve Backup.

Ensure that your Microsoft Windows Essential Business Server 2008 environment is configured properly.

Note: For more information, see your Microsoft Windows Essential Business Server 2008 documentation, the Microsoft website, and the Microsoft Windows Essential Business Server Overview in the CA ARCserve Backup for Microsoft Windows Essential Business Server online help.

4.3 Installation Considerations for the Agent for Microsoft Exchange Server

The following section provides information to consider when installing the Agent for Microsoft Exchange Server.

Microsoft Messaging API and Collaboration Data Objects 1.2.1 are required for the Document Level Agent for Microsoft ExchangeServer 2007 and 2010 to function properly. If the setup process does not detect this application, the Document Level Agent will be disabled.
To activate the Document Level Agent, perform the following:
1. Obtain Microsoft Messaging API and Collaboration Data Objects 1.2.1 from the Microsoft website and install it.
2. Stop the CA ARCserve Universal Agent Service.
  Note: Please make sure that no browse operation is performed, and no backup or restore job is running before stopping this service.
3. Run <Exchange agent home directory>\DocumentLevel\ExchDocWrapper.exe -regServer to register the Document Level Agent.
4. Start the CA ARCserve Universal Agent service.

4.4 Installation Considerations for the Agent for Microsoft SharePoint Server

The following section provides information to consider when installing the Agent for Microsoft SharePoint Server:

Microsoft Office SharePoint Server 2007, Microsoft SharePoint Server 2010, Windows SharePoint Service 3.0, or Microsoft SharePoint Foundation 2010 must be installed before you install the Agent for Microsoft SharePoint Server. The agent is supported on all operating systems on which Microsoft Office SharePoint Server 2007 or 2010 are supported.

The CA ARCserve Backup server must be able to ping all machines in the SharePoint environment by name. If you do not use DNS (Domain Name System) in your SharePoint environment, you must add all the machines in the SharePoint environment into the hosts file on the CA ARCserve Backup server.

For SharePoint Server farm environments, you must run the Microsoft SQL Server database instance with a domain account; for SharePoint Server standalone environments, you must run the Microsoft SQL Server database instance with a domain account or a local system account, depending on the configuration of the SharePoint installation. For details, see the CA ARCserve Backup Agent for Microsoft SharePoint Server Guide.

When you upgrade the Agent for SharePoint Server to this release, two active SharePoint Server Agent licenses exist in License Management dialog. To avoid this situation, launch License Management and manually release the licenses for old versions of the Agent that have been upgraded.

If the Agent for Microsoft SharePoint Server 2003, which is no longer supported, is detected during upgrade, the agent is automatically uninstalled.

4.5 Installation Considerations for the Agent for Microsoft SQL Server

The following section provides information about installation prerequisites, configurations, and issues to consider before installing the Agent for Microsoft SQL Server.

If you are installing the Agent with Microsoft SQL Server 2000, the Agent for Microsoft SQL Server requires Microsoft SQL Server 2000 with Service Pack 3, Service Pack 3a, or Service Pack 4.

Windows Small Business Server 2003 Standard Edition does not include Microsoft SQL Server 2000. However, you can install Microsoft SQL Server 2000 separately, but you must install Service Pack 3, Service Pack 3a, or Service Pack 4.
Notes:
- Windows Small Business Server 2003 Premium Edition includes Microsoft SQL Server 2000, Service Pack 3.
- Windows Small Business Server 2008 Standard Edition does not include Microsoft SQL Server 2008. However, you can install Microsoft SQL Server 2008 separately.
- Windows Small Business Server 2008 Premium Edition includes Microsoft SQL Server 2008.

In cluster environments, you may receive a Lost Connection error while installing the Agent for Microsoft SQL Server. This occurs in primary and standalone installations when you select the cluster SQL as the CA ARCserve Backup database. To avoid this error, copy the SQL Agent for CA ARCserve Backup database package to each cluster node and run setup manually.

To protect SQL Server instances in a cluster-aware environment, you must manually install the Agent for Microsoft SQL Server on all of the nodes in the cluster-aware environment.

When installing the SQL Agent for the CA ARCserve Backup database on other nodes in a cluster-aware environment, you must run SQLAgentRmtInst.exe and DBAConfig.exe after installation to input the correct cluster node name and password so that the Setup process can create ODBC communication.

After you upgrade from BrightStor ARCserve Backup r11.5 SP3 to this release of CA ARCserve Backup on a 64-bit operating system in a cluster-aware environment, you must run DBAConfig.exe located in the CA ARCserve Backup Agent for Microsoft SQL installation directory to configure the SQL Server instances that you want to protect.

When you select Windows Authentication for SQL Server, CA ARCserve Backup does not require security information to back up the SQL Server.

4.6 Installation Considerations for the Agent for Open Files

The following section provides information to consider when installing the Agent for Open Files on Vista machines and Windows Server 2008 core:

You can remotely install the Agent for Open Files on Vista machines, but may need to disable local account filtering first. User Account Control (UAC) is a Vista feature that blocks local administrative accounts from remotely accessing administrative shares (C$, Admin$).
Before you begin, determine whether the Vista machine is part of a domain or part of a workgroup. Use a Domain Administrative account if the target computer is part of a domain. Grant a domain account with administrator privileges on the Vista machine and use that domain account to log on. You may then remotely install the Agent for Open Files on the Vista machine.

If the target computer is part of a workgroup, disable the client computer's local account filtering policy by creating a new registry key, as follows:

DWORD value: LocalAccountTokenFilterPolicy

Location: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\

New Value: 1

After installation, set the LocalAccountTokenFilterPolicy setting to 0 to re-enable local account filtering.

When installing the Agent for Open Files, a reboot is recommended, but not necessary. Without rebooting, any files open before the Agent was installed may not be accessible during backup.

When installing CA ARCserve Backup as an Agent for Open Files on Windows Server 2008 Core, you should run mastersetup.exe directly from DVD\Install. If you use setup.exe from the DVD root, you will launch DemoShield, which requires Internet Explorer 5 or later to run. Internet Explorer is not available in Windows Server 2008 Core operating systems.

4.7 Installation Considerations for the Media Management Option (MMO)

The Enterprise Module is a prerequisite component for the Media Management Option (MMO) and you must install it in order to use the MMO option.

Note: MMO is not supported on ARCserve member server.

4.8 Installation Considerations for the Enterprise Module

The following section provides information about installation prerequisites, configuration, and issues to consider when installing the CA ARCserve Backup Enterprise Module.

The Image Option is included in the Enterprise Module. You must restart your computer after installing this option.

The Serverless Backup Option is included in the Enterprise Module. You must restart your computer after installing this option.

4.9 Installation Considerations for the UNIX and Linux Data Mover

Ensure that you complete the following prerequisite tasks before installing UNIX and Linux Data Mover.

Install CA ARCserve Backup for Windows on the primary server before completing this task.

Secure the host name of the CA ARCserve Backup primary server.

Secure the password for the caroot user name for the CA ARCserve Backup primary server.

Ensure that the CA ARCserve Backup primary server and the target data mover server can communicate with each other. You can verify that the servers can communicate using the ping host name command.

You do not need to uninstall the following components from the target data mover server to upgrade to this release:
- Client Agent for Linux (r11.1, r11.5, r12, and r12.5)
- Client Agent for UNIX (r11.1, r11.5, r12, and r12.5)
- Oracle Agent for Linux (r11.1, r11.5, r12, and r12.5)
- Oracle Agent for UNIX (r11.1, r11.5, r12, and r12.5)
When running on the target data mover server, the installation script detects the version of the above file system agents, if any, that already exist on that server. If the installation script detects a supported platform, you will be prompted to install the latest versions of the above file system agents.

Do not uninstall the BrightStor ARCserve Backup r11.5 base product from the target data mover server only if you plan to migrate the Ingres database information from the BrightStor ARCserve Backup r11.5 database to the CA ARCserve Backup database. For more information, see Migrate Database Information from Previous Releases to the CA ARCserve Backup Database in the UNIX and Linux Data Mover Guide.

4.10 Installation Considerations for the CA ARCserve Backup Patch Manager

The following section provides information about general considerations while installing Patch Manager r15 sp1.

When installing ARCserve r15 sp1, whether it is a new installation or an upgrade from a previous version, ARCserve will not automatically install Patch Manager r15 sp1, it will need to explicitly be installed from the r15 sp1 installation media to update the ARCserve components.

You will need to upgrade to Patch Manager r15 sp1 if you have an earlier version in order to get the patches for ARCserve r15 sp1. For more details, please refer to the CA ARCserve Backup Patch Manager Readme.

While upgrading the client and if the client is connected to the Staging server, ensure that the Staging server is also upgraded.

4.11 Installation Considerations for the CA ARCserve Backup for Virtual Machines

The following section provides information to consider when installing the CA ARCserve Backup for Virtual Machines.

VMware Systems: Install the Agent for Virtual Machines on the system intended to operate as the backup proxy system. Ensure that VMware VCB Framework/Virtual Disk Development Kit (VDDK) is installed on this system. Populate the CA ARCserve Backup database using the ARCserve VMware Configuration Tool on the backup proxy system. Deploy the Agent for Virtual Machines using Agent Deployment. For more information, see the CA ARCserve Backup Agent for Virtual Machines Guide.

Hyper-V Systems: Install the CA ARCserve Backup Server components on the system intended to operate as the primary or standalone server. Install the Agent for Virtual Machines on the Hyper-V host system. Populate the CA ARCserve Backup database using the ARCserve Hyper-V Configuration Tool on the Hyper-V host system. Deploy the Agent for Virtual Machines using Agent Deployment. For more information, see the CA ARCserve Backup Agent for Virtual Machines Guide.

When installing CA ARCserve Backup as Agent for Virtual Machines on Windows Server 2008 Core, you should run mastersetup.exe directly from DVD\Install. If you use setup.exe from the DVD root, you will launch DemoShield, which requires Internet Explorer 5 or later to run. Internet Explorer is not available in Windows Server 2008 Core operating systems.

4.12 Installation Considerations for the Client Agents

The following section provides information about installation prerequisites, configurations, and issues to consider before installing the CA ARCserve Backup Client Agents.

Agent for NetWare

You must upgrade the CA ARCserve Backup Agent for NetWare to the SP3 level for use with this release of CA ARCserve Backup.
Note: Version 9 of the CA ARCserve Backup Agent for NetWare is no longer supported and requires an upgrade to a current version. There is no backwards compatibility with this release of CA ARCserve Backup.

Agent for Windows

You can remotely install the Client Agent on Vista machines, but may need to disable local account filtering first. User Account Control (UAC) is a Vista feature that blocks local administrative accounts from remotely accessing administrative shares (C$, Admin$).
Before you begin, determine whether the Vista machine is part of a domain or part of a workgroup. Use a Domain Administrative account if the target computer is part of a domain. Grant a domain account with administrator privileges on the Vista machine and use that domain account to log on. You may then remotely install the Client Agent on the Vista machine.

If the target computer is part of a workgroup, disable the client computer's local account filtering policy by creating a new registry key, as follows:

DWORD value: LocalAccountTokenFilterPolicy

Location: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\

New Value: 1

After installation, set the LocalAccountTokenFilterPolicy setting to 0 to re-enable local account filtering.

In a clustered CA ARCserve Backup environment, the Client Agent for Windows needs to be installed on the local drive on each cluster node.

If you install the Client Agent (Windows, UNIX) on a virtual machine, you will be able to back up the data as if it were a physical machine.

When installing CA ARCserve Backup as an Agent for Windows on Windows Server 2008 Core, you should run mastersetup.exe directly from DVD\Install. If you use setup.exe from the DVD root, you will launch DemoShield, which requires Internet Explorer 5 or later to run. Internet Explorer is not available in Windows Server 2008 Core operating systems.

5.0 Upgrade Considerations

5.1 Upgrade Considerations for the CA ARCserve Backup Base Product

The following section provides information about upgrade prerequisites, configurations, and issues to consider before upgrade the CA ARCserve Backup base product.

When you upgrade CA ARCserve Backup from a previous release, consider the following scenarios:
- If the previous installation was that of a member server, you must upgrade the CA ARCserve Backup components that apply to Member server installation.
- If the previous installation was that of the CA ARCserve Backup Manager Console or CA ARCserve Backup Agents, and you did not install the CA ARCserve Backup Server components, you must upgrade the Manager Console or the CA ARCserve Backup Agents without installing the CA ARCserve Backup Server components.
  The Server Configuration Wizard lets you change the role of the server after you complete the upgrade process. Optionally, you can uninstall and then reinstall CA ARCserve Backup. However, to ensure that you do not lose records of your backup and restore data, you must not overwrite the CA ARCserve Backup database instance that is detected by the Installation Wizard.
  
  For more information on supported upgrades, please refer to the CA ARCserve Backup for Windows Implementation Guide - Supported Upgrades section.

When you customize job scripts on the primary server using the previous CA ARCserve Backup release, you will not be able to modify the job scripts after upgrading to the current release and will get an error message warning you that the job cannot be unpacked. To use job scripts created with previous versions of CA ARCserve Backup after upgrading, you must manually select the sources and then submit the jobs.

When you upgrade from a previous BrightStor ARCserve Backup release, the upgrade process uninstalls the previous release before installing this release. If the previous release was integrated with a previous version of Java Runtime Environment (JRE), the uninstall routine does not remove the directory and files associated with the JRE. The affected files are stored in the following directory:
C:\Program Files\CA\SharedComponents\Jre

If there are no other applications on your computer using these files, you can safely delete them.

Note: For more information, see Uninstall CA ARCserve Backup in the Implementation Guide.

The upgrade process does not install the drivers required by the Image Option and the Serverless Backup Option. As a result, scheduled jobs involving the Image Option and the Serverless Backup option can fail. To remedy this problem, you must install the required drivers manually using the Enterprise Module configuration utility.
Note: For more information, see Configure Devices using Enterprise Module Configuration in the Administration Guide.

Ensure the Regional and Language options for the CA ARCserve Backup Server and CA ARCserve Backup Agents are set identically to avoid browsing and encryption problems typical when operating the current version of CA ARCserve Backup with agents from previous versions.

The name of the CA ARCserve Backup home directory has changed since the previous release. If you specified the CA ARCserve Backup home directory as a parameter in the commands of any generic jobs created prior to upgrading, you need to modify those jobs and correct the path to the current CA ARCserve Backup home directory name. In this release, the default CA ARCserve Backup home directory is "CA\ARCserve Backup".

When upgrading directly from r11.5 SP3 ARCserve server that is using RAIMA as the ARCserve database to the current release, the device records list may miss inactive devices. You may need to restart the Tape Engine when devices become active again in order to view device records in DB Manager.

This release of CA ARCserve Backup installs CAPKI 4.1.1, which can cause system rebooting if CA ARCserve Backup services and back end programs are not stopped before upgrading. The setup process automatically stops these services and programs unless you are performing an SDO installation. In this case, you should stop all services and back end programs manually before you proceed.

When upgrading to this release of CA ARCserve Backup from older versions in a cluster environment and your database is SQL Server Express, perform the following steps after installation to ensure correct user profile management:
- Restart the ARCSERVE_DB service.
- Run command line: BABHOME\caauthd.exe -setupuser
- Run command line: BABHOME\cadiscovd.exe -m

6.0 General Considerations

The following section provides general information to consider when using CA ARCserve Backup:

We recommend using the Agent for Open Files when backing up the Citrix MetaFrame Presentation Server 3.0.

Before restoring information to the Citrix Access Suite, stop the CitrixXTE Service. After the restore operation is complete, run a discovery in the Access Manager.

The CA ARCserve Backup command line uses AES 256-bit encryption to communicate with the CA ARCserve Backup base product.

If you are running Microsoft SQL 2000 or VSS backup and restore jobs on any 64-bit Windows system, refer to the following articles at Microsoft and download a hotfix:
- http://support.microsoft.com/kb/904418/en
- http://support.microsoft.com/kb/913100/en
- From the Microsoft site, search for the SQL2000-KB913100-v8.00.1101-x64-ENU.exe package and run it.

When restoring folders and files, note the following:
- When Restore and Preserve Directory Attributes and Security Information is enabled, and Restore and Preserve File Attributes and Security Information is disabled, the encryption attributes of files are restored.
- When Restore and Preserve Directory Attributes and Security Information is enabled, and Restore and Preserve File Attributes and Security Information is disabled, the compression attributes of directories are not restored.
- When Restore and Preserve Directory Attributes and Security Information is disabled, and restore and Preserve File Attributes and Security Information is disabled, the encryption attributes of files are restored.

The following section provides general information to consider when using CA ARCserve Backup for Microsoft Windows EBS:

When connecting to a remote server for the first-time from CA ARCserve Backup for Microsoft Windows EBS, you need to provide equivalence for the CA ARCserve Backup user account, caroot. In the Create Equivalence dialog, complete the following field and click OK:
- CA ARCserve Backup password
  Important! You should not specify a blank password for caroot.
Note: For more information about how to add a new CA ARCserve Backup user using the User Profile utility of CA ARCserve Backup, see the CA ARCserve Backup online help.

When connecting to a new server, you must provide the CA ARCserve Backup user account, caroot.
Note: The caroot user profile controls access only to the CA ARCserve Backup Manager and backup-related functions, and should not be confused with the user credentials required to log in to the Microsoft Windows operating system. For more information regarding this user profile, see the CA ARCserve Backup Administration Guide.

Important! You should not leave the password blank for caroot.

The following information concerns the backup and restore of Hyper-V based virtual machines. Note that all configurations supported on Windows 2008 64-bit systems are still supported when Hyper-V is enabled on those systems:
- Backing up and restoring data on Virtual Machines is similar to the backup and restore of physical machines when the Agents (Agent for Open Files, Client Agent for Windows/Linux, SQL, Exchange and SharePoint) are installed in the guest OS of the Virtual Machines.
- Installing the CA ARCserve Backup base product and other options on Virtual Machines in Hyper-V is not supported, so the local Disaster Recovery Option is not supported on Virtual Machines. However, when the Client Agent is installed on a Virtual Machine, remote Disaster Recovery is supported the same as if on a physical machine.

During merge job, if there is only one session on the tape and this session spans from sequence 1 to sequence 2, you should always select sequence 1 for "Merge all sessions". If you select only sequence 2 for "Merge all sessions", the merge job fails with the error message, "Unable to find session number".

The following provides general information to consider when using the CA ARCserve Backup Global Dashboard:

You can protect your central database using the CA ARCserve Backup Agent for Microsoft SQL Server.

During a full data synchronization, the CA ARCserve Backup database engine service is stopped for several minutes. This may affect the status of any backup jobs in CA ARCserve Backup that are already running (especially jobs related to logging any information in the branch ASDB).

If you need to restart the Microsoft SQL Server, verify that all the Global Dashboard services are also restarted.

The following provides general information to consider when using the CA ARCserve Backup Agent for Virtual Machines:

CA ARCserve Agent for Virtual Machines lets you perform backup and recovery operations using ESX Server 3.5, Virtual Center server 2.5, vSphere ESX Server 4.0, vSphere ESX Server 4.1, vSphere vCenter 4.0, and vSphere vCenter 4.1.
Note: To perform backup and recovery options of this type, you must install VDDK on the backup proxy system.

CA ARCserve Agent for Virtual Machines lets you recover VMs that were backed up from an older version of either ESX Server or vCenter Server using VMware VCB Framework and CA ARCserve Backup r12, CA ARCserve Backup r12 SP1, or CA ARCserve Backup r12.5 systems. With CA ARCserve Agent for Virtual Machines, CA ARCserve Backup can recover data using VMware VDDK or VMware Converter. Using VDDK, CA ARCserve Backup can recover the VMs to ESX Server 3.5 or ESX Server 4.0 and 4.1 systems.

CA ARCserve Agent for Virtual Machines lets you back up VMs running vSphere 4.0, vSphere 4.1, and the VMs are managed by ESX Server 4.0, ESX Server 4.1, vCenter Server 4.0 or vCenter Server 4.1 using VCB Framework. VCB Framework 1.5 Update 1 lets you protect VMs running vSphere.

The following section provides general information to consider when integrating CA ARCserve Backup and CA ARCserve D2D:

When integrating CA ARCserve Backup and CA ARCserve D2D, CA ARCserve Backup skips CA ARCserve D2D destination folders from incremental/differential backup jobs. This is done to help ensure data consistency and recoverability of CA ARCserve D2D files when restoring from CA ARCserve Backup incremental/differential backup sessions.

The following are unsupported scenarios and limitations to consider when backing up CA ARCserve D2D destination files and folders:
1. For CA ARCserve Backup to skip the CA ARCserve D2D destination files and folders, you must select the CA ARCserve D2D folder at the root or shared folder level. Therefore, CA ARCserve D2D integration with CA ARCserve Backup will be supported in the following scenarios:
  - User selects the shared or root folder.
  - User selects the volume that has the CA ARCserve D2D destination.
  - User selects the entire machine.
  For example, if c:\D2D is configured as a D2D folder and it has a D2D destination under machine D2D-server1 as c:\D2D\D2D-server1, then the user has to select c:\D2D or c:\ or the entire machine as a backup source.
2. CA ARCserve Backup backs CA ARCserve D2D destination folders using VSS. If the creation of a VSS shadow copy fails, CA ARCserve Backup skips the entire CA ARCserve D2D destination folder when executing the backup.
  For example, on a Windows Server 2000 machine, where VSS is not supported, the entire CA ARCserve D2D destination folder is skipped from the backup.
3. If a shadow copy is created specifically for backing up CA ARCserve D2D destination, the backup of the CA ARCserve D2D destination will not be consistent in the following scenarios:
  - The CA ARCserve D2D destination of a machine is spread across multiple volumes.
  - The CA ARCserve D2D destination of a machine is spread across multiple root folders.
  This behavior occurs because the Client Agent for Windows deletes the VSS shadow copy after CA ARCserve Backup backs up the CA ARCserve D2D destination root folder. If the CA ARCserve D2D destination for the same machine is encountered, a new VSS shadow copy has to be created again which will not be consistent with the VSS shadow copy created previously.

7.0 Supported Upgrade Paths

If you are currently using one of the following releases of CA ARCserve Backup or BrightStor ARCserve Backup, you can upgrade to this release from the following products:

CA ARCserve Backup r15 for Windows--Includes the General Availability (GA) release and all of the latest service packs.

CA ARCserve Backup r12.5 for Windows--Includes the General Availability (GA) release and all of the latest service packs.

CA ARCserve Backup r12 for Windows--Includes the GA release and all of the latest service packs.

BrightStor ARCserve Backup for Windows r11.5--Includes the GA release and all of the latest service packs.

BrightStor ARCserve Backup for Windows r11.1--Includes the GA release and all of the latest service packs.

Note: If you want to upgrade from BrightStor ARCserve Backup v9, BrightStor Enterprise Backup v10.5, BrightStor ARCserve Backup r11.1, or BrightStor ARCserve Backup r11.5, you must uninstall the previous release and then install this release of CA ARCserve Backup. However, if you wish to retain the database information from your previous implementation, you must upgrade the previous implementation to CA ARCserve Backup r12.5 GA release (with no SP), and then upgrade from CA ARCserve Backup r12.5 to this release. To obtain CA ARCserve Backup r12.5 installation media, contact CA Support. For all other previous releases of BrightStor ARCserve Backup or BrightStor Enterprise Backup earlier than v9, you must uninstall the previous release before you install this release.

Please also note the following:

Silent or remote upgrades do not allow you to change the server or database types.

If the CA ARCserve Backup Database (ASDB) was SQL Express 2005 prior to upgrade, the upgrade installs SQL Express 2008.

7.1 Backward Compatibility

This release of the CA ARCserve Backup server component can back up data using agents from the following releases:

CA ARCserve Backup r15 (and all service packs)

CA ARCserve Backup r12.5 (and all service packs)

CA ARCserve Backup r12 (and all service packs)

BrightStor ARCserve Backup 11.5 (and all service packs)

8.0 Known Issues

The following sections provide information about issues known to exist in CA ARCserve Backup for this release.

8.1 Known Issues for the Base Product

The following issues relating to the CA ARCserve Backup base product are known to exist in this release:

Due to a NetBIOS limitation, computer names longer than 15 characters are truncated to 15 characters, including when you set up a host server.

If you install Windows Server 2003 Service Pack 1 using an Emulex Fibre Channel Card, you must download the latest Windows 2003 Storport HBA drivers from the Emulex website. A problem with the Emulex driver released with Windows 2003 SP1 prevents CA ARCserve Backup from initializing correctly unless you update the Emulex driver.

If you use the Master Setup to install CA ARCserve Backup remotely to a system in another Windows domain, you may receive a message indicating that the installation failed when it is successful. This behavior occurs because the Master Setup cannot accurately detect the activity on the remote machine in the other domain because of a firewall or due to a lost network connection. Check the installation status on the remote machine to verify that the installation succeeded.

NetWare Services no longer appear under the Network branch in the Backup and Restore Managers. CA ARCserve Backup supports only Client Agent for NetWare backups when creating NetWare sessions from a CA ARCserve Backup for Windows host.

If you import a DLTWORM-capable media into a library that has not converted to WORM, the Quick erase and Convert to WORM media option is disabled. You must perform a full inventory of tapes to enable this option because this capability can be recognized only by reading the media.

If you use WORM media as the destination for any cross-platform jobs involving the CA ARCserve Backup for UNIX Agent for Oracle or the CA ARCserve Backup for Linux Agent for Oracle, these agents may not behave as expected. Because WORM media is not supported on the UNIX or Linux agents, these jobs may use destinations other than the WORM media.

Installing 32-bit components on a 64-bit machine generates two copies of the file PortsConfig.cfg on the machine. The PortsConfig.cfg file for the 64-bit components is in c:\Program Files (x86)\CA\SharedComponents\ARCserve Backup and the PortsConfig.cfg file for the 32-bit components is in c:\Program Files \CA\SharedComponents\ARCserve Backup. If you make changes to one, you must make the same changes to the other, or the components may not be able to contact one another.

If you install agents on cluster nodes, do not back up the physical nodes (the private drives C: and D:) or non-shared disks through preferred share using the virtual server IP address, because virtual servers can be moved from one node to another. For example, if virtual server 1 resides on physical node 1 and you backed up virtual server 1 through preferred share, the non-shared drives on physical node 1 are also backed up. If you move virtual server 1 to physical node 2, and perform a Restore to Original Location, the non-shared drives from physical node 1 are restored to physical node 2.

The default TCP/IP protocol is recommended for ODBC communication. If this setting is changed to Named Pipe protocol, ODBC fails.

Special characters in media files will interfere with RMAN jobs. Avoid using special characters such as <,>,;,.

Running RMAN script to backup remote CA ARCserve Backup Agent for Oracle to CA ARCserve Backup Server may not work if the remote machine was registered to CA ARCserve Backup server with a fake name.

Job redirection is no longer supported. As an alternative, you can use the makeup job feature. Refer to the Administration Guide for more information regarding makeup jobs.

Jobs run in the previous release of BrightStor ARCserve Backup (r11.5) will not appear in the Job History of this release after upgrade.

When the Windows security policy is enabled on the machine where CA ARCserve Backup is installed, an audit log is recorded in the event log at the time of a system application startup, such as Task Manager.

If you apply the license keys for two or more different CA ARCserve Backup suites on a single ARCserve server, the license count on the ARCserve server may not be correct. To remedy this problem, apply the licenses that you require and contact CA Support at http://ca.com/support to correct the license count.

The Tape Compare utility does not support comparing tapes that were created using multiplexing or encryption.

Broadcast Alerts do not function on systems running Microsoft Windows Server 2008. This behavior is observed because Microsoft Windows Server 2008 does not support messaging service.

After you restore the ARCserve 64-bit ASDB, you must perform at least one full backup of the CA ARCserve Backup database before you perform an incremental or a differential backup. This task ensures that CA ARCserve Backup database backup sessions contain the most current data. This task ensures that CA ARCserve Backup database backup sessions are current.

A NetBIOS name resolving problem between local and remote machines may prevent you from obtaining information from the Diagnostic Wizard. Diagnostic utilities use NetBIOS names to communicate. To avoid communication problems, verify that the remote system is on the network and that the machine name is correctly mapped to the IP address. You should also purge and reload the NetBIOS Remote Cache Name and NetBIOS Remote Machine Name tables. To do so, perform the following steps:
1. Confirm that the remote machine is reachable across the network and that the IP Address matches the remote machine name. Run the following commands to confirm:
  - ping <MachineName>
  - ping <IPAddress>
  - ping –a <IPAddress>
  If the remote system can be pinged and the name matches the IP address, the Diagnostic Wizard should experience no problems. If the system cannot be pinged at all, check the network connections and ensure the system is operational. If the name does not match the IP address, continue.
2. Open a command prompt and run ipconfig /all to show the current IP configurations and other network configurations of a machine. Examine the command output for mistakes in your configurations. If mistakes exist, the network cannot communicate properly.
  1. Open Network Connections.
  2. Double-click <Connection Name>.
  3. Click the Support tab.
  4. Click Details.
  5. Note the values for "WINS Servers". The WINS Servers provide the NetBIOS name resolution for your remote servers.
  6. Ping the WINS servers using the commands in Step 1.
3. Run the following command to check the NetBIOS Remote Cache Name Table:
  nbtstat -c
  
  Using NetBIOS over TCP/IP, this command lists the cache of remote machine names and their IP addresses, and outputs statistics into four columns: Name, Type, Host Address and Life (sec). Examine the output and ensure the remote machine IP address matches its machine name for all types of the machine name specified.
  
  If the machine name matches the IP address for all types, the remote system can be accessed by its NetBIOS name.
  
  If the machine name does not match the IP address, or if no such items exist in the table, proceed to Step 4.
4. (Optional) If you find a mismatch in the mapping between a System Name and IP Address, run the following command to purge the Server Name and IP address mapping on both the local and remote machines. Otherwise, skip to Step 5.
  ipconfig /flushdns
5. Purge and reload the NetBIOS Remote Cache Name Table:
  nbtstat -R
6. Run nbtstat -c again. The table should now be empty, or contain only a few new items with lives of about 600 seconds.
7. Check the NetBIOS Remote Machine Name Table:
  nbtstat -a <RemoteName>
  
  This command lists a remote machine name table, given the machine name you specify.
  
  nbtstat -A <IPAddress>
  
  This command lists a remote machine name table, given the IP address you specify.
  
  The tables should show identical information: the name of the remote system as "Registered" for the IP Address.
  
  If the steps above do not solve your NetBIOS communication problem, you must contact your WINS server administrator to reconfigure the system.

The CA ARCserve Backup database may not contain up-to-date database information (for example, file lists and physical locations) and the Restore Manager, Restore by Tree, source directory tree may not display up-to-date information immediately after you restore the CA ARCserve Backup database to its original location (original computer or original database instance) or to a different location (different computer or different database instance).
To remedy this problem, do the following:
1. After you restore the CA ARCserve Backup database, use the Merge utility to merge the CA ARCserve Backup database backup sessions.
2. Close and then reopen the Restore Manager window to refresh the information that displays in the Restore by Tree source directory tree.

In r15, when you modify a makeup job that was automatically created after a full-node backup job has failed, you will see that the MSDEWriter, SQLServerWriter and WMIWriter objects have been selected in the Backup Manager, Source directory tree. These objects are displayed with excluded text which will not be backed up when the makeup job is submitted.

When you log off an interactive Windows session while a message (such as tape mount) is still displayed, some temporary files will remain in the CA ARCserve Backup Temp folder.

Backup jobs performed with Windows 2003, and Windows 2008 systems may include the following files that Microsoft recommends not be backed up, even if they are specified in the FilesNotToBackup registry key:
- index.dat
- MsDtc.log
- dtctrace.log
You should skip these files when restoring the database.

CA ARCserve Backup operations executed on the same tapekey after tapecopy has been executed could affect either the source or the destination tape. Job failure may also occur if a session is added to either the source or destination tape after Tapecopy because CA ARCserve Backup may not be able to restore that added session. This is because a tape is identified by three items: the tape name, the random ID, and the sequence number. The combination of these three tape identifiers is called the tapeKey. When submitting a tapecopy job with a command such as “tapecopy –s –d –t”, CA ARCserve Backup automatically assumes the tapeKey of the destination tape is the same as the source tape and views it as if only one tape exists.
If you do not want the destination tape to be the exact same as the source tape, you can include the –idr switch with the tapecopy command so that CA ARCserve Backup automatically assigns a different random ID to the destination tape and ensures that the destination tape is not exactly the same as the source tape.
- If you include the –idr switch with the tapecopy command, the random ID of the destination tape will not be the same as the source tape and as a result, the destination tape could not be used at a later time for disaster recovery purposes.
- If you do not include -idr switch with the tapecopy command, you could then use the destination tape at a later time to perform a disaster recovery operation because the destination tape will be exactly the same as the source tape.

This release of CA ARCserve Backup automatically creates a new media pool with the same name given to media in an r12 or prior environment and inventoried in an r15 environment.

When you run ca_recoverdb.exe to recover the CA ARCserve Backup database, you may receive the following warning message:
W5110 The Database is no longer available

During recovery, the CA ARCserve Backup database is offline. So any client programs trying to access the database during this period will be denied. This message does not prevent recovery from completing successfully.

If you are performing backup jobs on a Windows 2008 or Vista system and have specified Pre and Post job commands in the Global Options dialog, CA ARCserve Backup ignores the user name and password on the Pre/Post tab and executes the commands even if you enter an invalid user name and password combination. Security validation is performed only on Windows 2000, 2003 or XP systems.

In Citrix 4.5, you must enable Read/Execute privileges on the CA ARCserve Backup Home folder to publish the product.

The first job run after you successfully recover the CA ARCserve Backup database appears in the Status Manager with the same Job ID as the ASDB restore job. This is because the Job ID assigned to the ASDB restore job is lost after the ASDB is restored successfully.

When run with Microsoft Office 2003, CA ARCserve Backup Job Status Manager can experience excessive "handle leaks", too many open register keys that are no longer in use. Install the latest Microsoft Office 2003 service pack to avoid this problem.

When the Catalog database folder is changed to a long path name (greater than 140 characters) and backed up, the catalog files may not be kept in the catalog database and an E3408 error is recorded in the Activity Log.

Client Agent Password Security is only supported for the Client Agent for Windows, including the CA ARCserve Backup Agent for Open Files and VSS Writers. If Password Security is enabled and any database, application, or messaging Agent is installed on the same machine as the Client Agent, whole node backup is not supported. System Security is the default setting. If you have enabled Password Security on the CA ARCserve Backup Primary or Standalone server, the automatically-generated Database Protection Job will fail for the job queue and ARCserve Catalog Database. You must not enable Password Security in the Agent Configuration on any machine running a database, application, or messaging Agent before submitting the job.

The following issues related to SIS (single instance storage) are known to exist in this release:
- Files in the \SIS Common Store are normally excluded from jobs by the registry key, FilesNotToBackup, and should not be backed up or restored unless they are *.sis files. However:
  - when you perform a remote backup of an entire drive on which Single Instance Storage was activated as the backup source, the job fails and AW0004 is recorded. This is because CA ARCserve Backup is attempting to back up files that should have been excluded. Restoring the entire session to its original location also restored files that should have been excluded.
  - when you perform a restore of an entire session, files in the \SIS Common Store that should not have been backed up are now skipped.
  Note: If you select only the \SIS Common Store to back up, excluded files are not backed up, as expected.
- When you restore SIS links using the global option "log all activity" set to on, the Job Log shows only the links have been restored, not the data files. This is not an issue; if data files are already in the \SIS Common Store, those files will not be restored.
- When restoring the \SIS Common Store that was remotely backed up and you have deleted all the link files corresponding to the restored common store files, the common store files are not deleted. The Remote Restore Job Log shows the files as restored.

For jobs shown in the Activity Log, the Media Compression Ratio and the Media Remaining Capacity display as 0 because these parameters are not supported by the device.

CA ARCserve Backup does not support Windows passwords that are 24 characters and longer. When you add a Windows agent machine to CA ARCserve Backup, you are prompted for a hostname and password. Even though Windows supports a long password here, CA ARCserve Backup does not and login will fail.

CA ARCserve Backup does not support restoring a Job Queue session to its original location using normal data recovery processes.

Due to a known issue regarding the start up sequence of CA ARCserve Backup and Microsoft SQL Express, or SQL Server installed on the same machine as CA ARCserve Backup, the Event Log may show the following errors after a system reboot:
- Failure Audit: 18456 (Source MSSQL$ARCSERVE_DB) - The SQL Server service is not running but client programs are trying to log in, and so, fail.
- Error: 17187 (Source MSSQL$ARCSERVE_DB) - The SQL Server service is not running, so it cannot accept a client connection.
- Warning 3: (Source SQLBrowser) - This warning is recorded because service starts automatically. Although CA ARCserve Backup does not use the service setting, the installer changes it. This service should not have been changed to start up automatically. Set the SQL Server Browser service to 'disabled' to avoid this warning.
  To eliminate Warning 3, perform the following steps:
  
  1. Click Start, Control Panel, Administrative Tools, Services.
  
  2. From the list of services, double-click SQL Server Browser service to open its properties.
  
  3. Change the startup type to Disabled.
  
  4. Click OK. Rebooting should now proceed without this warning.
These errors are related to the sequence in which CA ARCserve Backup and SQL Server services are started and can be eliminated if you adjust the following CA ARCserve Backup services that depend on SQL Service to start:
- CA ARCserve Backup Database Engine
- CA ARCserve Backup Management Service
- CA ARCserve Backup Universal Agent
- CA ARCserve Backup Tape Engine
Note: If SQL Server is installed on a remote machine, rebooting CA ARCserve Backup does not affect it.

To adjust CA ARCserve Backup services

Determine SQL Server service name.

Find the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLXXXX, where XXXX is the unique name of the SQL Server and MSSQLXXXX is the SQL Server Service name.

Set CA ARCserve Backup services to depend on SQL Server service to start up by using the Microsoft sc utility (see Using Utility steps a through c, below) or by manually setting the registry keys (see Manually editing the registry, below).
Using the utility:
1. Install the Windows support tool, "SUPTOOLS.MSI" from your Windows installation CD. Go to the <CD-ROOT>\SUPPORT\TOOLS\ directory.
2. Run the Command Prompt: Start, All Programs, Windows Support Tools, Command Prompt.
3. Type the following in the open Command Prompt window:
```
sc config CASDBEngine depend= MSSQLXXXX
```
```
sc config CASMgmtSvc depend= MSSQLXXXX
sc config CASUniversalAgent depend= MSSQLXXXX
sc config CASTapeEngine depend= MSSQLXXXX
```
4. Go to step 3.
Edit the registry manually:

Create a Multi-String value named "DependOnService" under each of the following keys and set its value to your SQL service name (see step 1).

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASDBEngine

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASMgmtSvc

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASUniversalAgent

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASTapeEngine

Reboot the computer. The errors should not reappear.

To avoid problems expanding the Microsoft Network in CA ARCserve Backup Manager on Windows Server 2008 machines, ensure Computer Browser service is enabled and started. This service is disabled on Windows Server 2008 systems by default.

If you are using Windows XP, the CA ARCserve Backup Manager cannot log in with Windows Authentication. This is due to a problem with the Windows XP ForceGuest registry feature. This problem is limited to machines that are members of a workgroup; if the machine is a member of domain, log in proceeds. To avoid the problem, use regedit to set the ForceGuest registry value to 0. The key is located under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.

In an NEC CLUSTERPRO/ExpressCluster X1.0 for 32-bit Windows environment, if you submit a backup job by expanding the virtual primary or member server and selecting a file to back up, the restore of this file will fail if you select the "Restore files to their original location(s)" option. To perform a successful restore of this type of file, you must specify the restore path instead of selecting this option.

When performing failover jobs, provide blank media on Node B if the session method is Full to continue the same job.

When you install this release of CA ARCserve Backup on the cluster node of a Windows Server 2008 cluster, the CA ARCserve Backup Database is listed in the cluster virtual name on the Backup Manager.

When default collation is selected from Language Support Options, Look in Directory field on the Restore by Query screen is Kana-insensitive, Width-insensitive and Case-insensitive. When Japanese collation is selected, operations are Kana-sensitive, Width-sensitive and Case-sensitive. For the Look in Directory field on the Restore by Query screen, and the Volume field on the Search dialog, you may specify only uppercase drive letters.

Security information for the Agent for Microsoft SQL is not automatically loaded after upgrading from earlier CA ARCserve Backup versions to this release. You must retype password to continue.

CA ARCserve Backup does not support integration with the Microsoft Management Console.

If the CA ARCserve Backup database is configured to use SQL Server, the Database Protection Job may not be able to successfully backup the CA ARCserve Backup database in a clustered environment when failover happens from one node to another node. If such a situation occurs, run the Database Protection Job again to manually ensure the CA ARCserve Backup database is being successfully backed up.

When performing a full node backup, you may skip the system state by adding the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters

Value Name: SkipSystemStateBkup

Data Type: REG_DWORD

Value: 1

For 32-bit OS, local backup jobs, add the key here:

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup

Value Name: SkipSystemStateBkup

Data Type: REG_DWORD

Value: 1

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\Task\Backup

Value Name: SkipSubmitDetailEX

Data Type: REG_DWORD

Value: 1

Microsoft does not recommend backing up symbolic links on Windows Vista, Windows Server 2008, Windows Server 2008 R2, and Windows 7 systems. This approach is not recommended because the default locations for user data and system data (for example, the Documents and Settings folder) are different than that of previous Windows operating systems. As a best practice, you should back up the folders that are referenced by the symbolic link, rather than the link itself. For more information, see the Microsoft Developer Network at the following website: http://msdn.microsoft.com/en-us/library/bb968829(VS.85).aspx.

You may experience slow performance when you browse Windows Server 2003 x64 systems from the Windows Systems object in the Backup Manager directory tree. CA ARCserve Backup demonstrates this behavior due to various environmental conditions that can cause VSS writers to enumerate the VSS metadata. To remedy this problem, you can prevent the Backup Manager from enumerating VSS metadata. However, without the VSS metadata, you can browse only the disks for the specified computer. To stop the Backup Manager from enumerating VSS metadata, set the following registry key to 3: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters\VSSWriterBrowseOption.

When restoring Hyper-V virtual machines to an alternate location, CA ARCserve Backup may not be able to power on the target if the CD/DVD name is not the same as that of the original backup. To remedy this problem, ensure that the CD/DVD name of the destination is the same as the source location before you submit the restore. An alternate solution is to edit VM settings after restore is complete and change the CD/DVD location to one available on the destination server.

When restoring Hyper-V virtual machines to an alternate location, CA ARCserve Backup may not be able to power on the target if the friendly name of the network switch is not the same as that of the original backup. To remedy this problem, ensure that the friendly name of the network switch of the destination is the same as the source location before you submit the restore. An alternate solution is to edit VM settings after restore is complete and change the network switch name to one available on the destination server.

When you submit backup jobs to removable media such as RDX, avoid setting both Eject Media and Export Options. Export options override the Eject Media options but because this device does not support exporting, the device is not ejected upon job completion.

In Job History, there is no device/media information for sessions backed up to a RAID group because a RAID group typically contains multiple devices, yet appears as a single device to the application.

After you upgrade from BrightStor ARCserve Backup r11.5 to this release, CA ARCserve Backup may not be able to read from media that was created using the tapecopy command line utility. This problem occurs when the source media contains data that was backed up using multiplexing, the backup spans multiple sessions, and the tapecopy operation spans the backup sessions on the destination media. To remedy this problem, you must execute a merge job to update the backup records before you execute tapecopy, execute tapecopy, and then execute another merge job after the tapecopy operation is complete. This approach helps to ensure that CA ARCserve Backup can access the backup data from the destination media.

When saving a Data Mover backup job script from the Backup Manager console, the Data Mover's source, destination, and global options checks are not executed. Therefore, the GUI will not show any messages to warn the user or block the user from submitting the job and removing the unsupported options. If you reload the saved job script from the Job Status Manager, the job will fail.
Select one of the following options as a workaround:
- From the Backup Manager console, click the Submit button to submit your job. The Security and Agent dialog opens. Click OK and the Submit Job dialog opens. Click the Save Job button to save the job script.
- If you select the Save or Save As menu to save the job script, you can reload the job and modify this job in the Job Status Manager, and then re-submit the job. All checks will then be executed.
- If you select the Save or Save As menu to save the job script, you can click the Open menu from the Backup Manager console to open the job script and then click the Submit button to submit the job. All checks will then be executed.

CA ARCserve Backup supports only one writer (e.g., Oracle, MSDE) as a source disk in one backup job through Transportable Shadow Copies, i.e., HDVSS. If you include other types of source disks to this one backup job, the job will fail.

When you select Add Agent/Import/Export menu from CA ARCserve Backup to register a server that has multi IP addresses, CA ARCserve Backup Group View will only recognize the first IP address. CA ARCserve Backup Group View will not be able to change an IP address after a node is registered. In the case of Classic View, you can change it by selecting Agent Modification from the Context menu.

The Job Status Manager cannot display Activity Log data for data mover servers when the Group by Job option on the Activity Log tab is specified.
Important! This behavior occurs only when jobs are submitted using UNIX/Linux Data Mover backup on the Backup Manager Start tab.

If the CA ARCserve Backup uses SQL Server as its database and the SQL instance name is "ARCSERVE_DB", use ca_recoverdb.exe to recover your CA ARCserve Backup database, instead of Database Recovery wizard.

8.2 Known Issues for Upgrading to CA ARCserve Backup

When upgrading from old, unsupported versions of CA ARCserve Backup to this version, the ARCserve database (ASDB) is not retained. To retain the ASDB, you should perform interim upgrades; upgrade from an unsupported version to a supported version to the current version. For more information, see the topic, Supported Upgrade Paths.

When you upgrade from older versions of CA ARCserve Backup, tapes with lowercase letters in the tape names are listed in the Session View of the Restore Manager using all uppercase letters. You cannot expand the tape in the Session View. To address this problem, perform the following procedure:
1. In the Database Manager, expand the media Records. The tape name appears at least twice, once in uppercase letters and once in lowercase letters.
2. Delete the uppercase entry. The Restore Manager displays the tape name and details correctly.

When upgrading to this release of CA ARCserve Backup from 11.5, we recommend setting the value of key "LastObject" to empty so that restore IDS does not fail.

After upgrading to this release of CA ARCserve Backup, duplicate job records are shown in DB manager for central DB member.

If server is upgraded to this release of CA ARCserve Backup, Job History will not show Rotation or GFS jobs running prior to upgrading.

Due to differences in schema, previous CA ARCserve Backup servers cannot share the ASDB with servers from the current CA ARCserve Backup release. So if the server from this CA ARCserve Backup release is installed with the same instance, which has been used by a previous CA ARCserve Backup server, the previous CA ARCserve Backup server will not work normally, even if you choose NOT to overwrite the existing database.

Upgrade of CA ARCserve Backup components may leave a copy of the older version's files on the disk, if the components were installed in the same folder. You need to manually remove the older version's files from the disk.

When upgrading the CA ARCserve Backup Agent for SAP from 11.5.4 to this release, hold jobs are not supported.

Backup jobs submitted using BrightStor ARCserve Backup r11.5 Agents (includes all service packs) and CA ARCserve Backup r12 Agents that contain Unicode characters in their directory names and file names will fail after you upgrade to this release. To avoid this problem, specify the parent directory of the directories, files, or both that contain Unicode characters and then resubmit the job.

When upgrading using Agent Deployment, the Automated Upgrade option may be unavailable (appear dimmed or grayed out). This happens because the CA ARCserve Backup database contains no remote host information. To avoid this problem, create the remote host to the ASDB in the CA ARCserve Backup Manager, browse a remote host using a CA ARCserve Backup Agent, or run backup jobs.

You must use the Server Configuration Wizard to specify SQL Server collation settings for the CA ARCserve Backup database when you upgrade from a previous release. If you protect data that contains Unicode-based characters from East Asian languages, (for example, JIS2004) you must enable SQL collation to ensure that you can search and sort the data. This issue affects Microsoft SQL Server and Microsoft SQL Server Express 2008 Edition databases.
To specify SQL Server collation settings, do the following:
1. Upgrade to the current CA ARCserve Backup for Windows release.
  After the upgrade process is complete, from the Windows Start menu, select All Programs, CA, ARCserve Backup, and click Server Configuration Wizard.
  
  The Server Configuration Wizard opens.
2. Click Select Database and click Next
3. Follow the prompts and complete the required fields on the Check Caroot, System Account, and Select Database dialogs.
  Important! On the Select Database dialog, you must specify the type of database (Microsoft SQL Server or Microsoft SQL Server Express 2008 Edition) that is currently installed in your CA ARCserve Backup environment and then click Next.
4. Do one of the following:
  - Microsoft SQL Server 2008 Express Edition database--Clear the check mark from Overwrite the existing ARCSERVE_DB instance on the SQL Server Express Instance dialog.
  - Microsoft SQL Server database--Complete the required fields on the SQL Database System Account dialog and click Next. Clear the check mark from Overwrite DB option on the Select database installation path dialog.
5. Click Language Support Options.
  The Collation Settings dialog opens.
6. Click East Asian collation, specify the required language from the drop-down list, and then click OK.
  The Collation Settings dialog closes.
7. Click Next.
  Follow the prompts and complete the required fields on the subsequent dialogs to complete the configuration.

When upgrading from BrightStor ARCserve Backup 11.5 to the current version, SQL Express 2008 installation may fail if there is an existing SharePoint 2003 embedded SQL instance. To avoid this problem, stop the following service: MSSQL$SHAREPOINTPORTAL.

After upgrading to this release from BrightStor ARCserve Backup r11.5 or r11.1, old jobs are not listed in "Group by Job or Host" view in the Job History, or in "Group by Job" view in the Activity Log. Old jobs and host information are not available upon upgrade, so certain advanced reports based on node table will not work.

After upgrading to this release from previous versions, any NAS GFS jobs you re-run are full backups. This is due to a change in the naming method policy. This only affects the first rotation job re-run after upgrade; all subsequent runs are incremental. It is therefore suggested that you upgrade to this release on the same day your GFS rotation job runs a full backup. For example, if your NAS rotation full backup is scheduled for Fridays, perform the upgrade on a Friday.

When upgrading from CA ARCserve Backup r11.1 or r11.5 to the current version, the group name may change, such as DGROUP1 changes to a new group name, PGRP0. Since all backup jobs are fixed to be submitted to the earlier version group name (DGROUP1), all backup jobs submitted before the upgrade will fail due to the newly changed group name. To avoid this problem, you can change the group name in the current version to the old name (DGROUP1) or resubmit jobs using the new group name (PGRP0).

8.3 Known Issues for the Client Agents

The following issues relating to the Client Agents are known to exist in this release:

For the Client Agent for Windows, installing 32-bit components on a 64-bit machine generates two copies of the file PortsConfig.cfg on the machine. The PortsConfig.cfg file for the 64-bit components is in c:\Program Files\CA\SharedComponents\ARCserve Backup and the PortsConfig.cfg file for the 32-bit components is in c:\Program Files (x86)\CA\SharedComponents\ARCserve Backup. If you make changes to one, you must make the same changes to the other, or the components may not be able to contact one another.

When a full NetWare machine is selected for backup, the NDS session is not backed up. You must explicitly select the NDS session and other volumes to be backed up.

The Client Agent for NetWare handles only one job at a time. If a backup job includes the NetWare volume and NDS of the same node, it creates two nodes for the job in the job package, and because multiplexing or multistreaming jobs create two jobs for the NetWare node and the two jobs run simultaneously, the agent rejects the second job.

The NetWare Services branch has been removed from the Network tree in the Backup and Restore Managers. To back up a NetWare machine from the ARCserve Backup host, you must install the Client Agent for NetWare on the machine.

Whole node backup operations are not supported with the Client Agent for AS400.

The Client Agent for SAP does not support Server Side Encryption and Secure Migration.

Alert Messages on 64-bit machines may display several times, even after you click OK. If you disable your VMware Adapters, messages display only once.

For Citrix users who run Microsoft SQL as the Citrix database, you must restart the Citrix SQL instance before you restore the Citrix Metaframe 4.0 Server.

When backing up files on IA64 systems, note that a file's Last Access Time is not updated even when the Preserve file access time option is not selected. This problem appears limited to jobs in which the Keep Archive Bit option is selected.

When you uninstall an Agent from a remote system, you must restart the universal agent service on that system and restart the Backup Manager, otherwise, the Backup Manager can still browse that remote system.

Included in this release is test fix T245314, which corrects a problem using the "Delete source files after backup to media (use with caution)" option. However, this fix does not work as expected unless the following registry key is set. If you are performing a remote or local backup using Windows 2003 64-bit or Windows 2008 with this option enabled, you must set the following registry key to 0 to obtain the desired results:
Key:
```
DeleteDirInMigration
```
Location:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCserve Backup\ClientAgent\Parameters
```
Value:
```
0 to retain directory folders, 1 to delete them.
```

The Client Agent for Windows lets you protect files and folders that reside in virtual hard disks (VHDs) that are mounted as volumes. If the mounted VHD source data contains hard link files and folders that are not associated with the operating system's system state, CA ARCserve Backup backs up the hard link files as multiple, individual files. As a result, the amount of disk space that is required to store the backup data will exceed the actual size of the data that you are backing up.

8.4 Known Issues for CA ARCserve Backup Licensing

The following issue is known to exist in this release:

When applying trial keys, be aware that the most recent key overrides any previously-applied keys for the same component. For example, suppose you applied two keys for the Exchange Server agent. The first was for 3 users and the second was for 5 users. The permitted user count is 5 because that is the most recently applied key. This issues affects trial licenses applied on the same day.

8.5 Known Issues for CA ARCserve Backup for Microsoft Windows Essential Business Server

The following issues relating to CA ARCserve Backup for Microsoft Windows Essential Business Server are known to exist in this release:

Multiple instances of the online help can be opened at the same time.

After switching the CA ARCserve Backup server (using the Connect to a new server task), it may take a few seconds to update the data.

8.6 Known Issues for the Agent for IBM Informix

The following issues relating to the Agent for IBM Informix are known to exist in this release:

If you use Informix Backup and Restore utility, rather than the Backup Manager, you must define security information using the Informix Agent Batch Job Configuration utility dbacfg before submitting any backup or restore jobs.
Note: For more information about the dbacfg utility, see the Agent for IBM Informix Guide.

When using remote CA ARCserve Backup to back up or restore an Informix server, the real backup and restore jobs created by the Informix Server are scheduled on the CA ARCserve Backup server based on the local time from the Informix server. Therefore, time differences between the CA ARCserve Backup machine and the Informix server machine can cause backup or restore delay. To prevent this delay, synchronize the time between both machines.

When using the Client Agent with the Restore by Tree method for your restore operation, databases appear under the Microsoft Windows Network icon in the Restore Manager.

When expanding an Informix instance fails and the activity log displays "Agent function entry point not supported", the failure is likely due to dbaifmx.dll failing to load. We recommend installing Informix by GUI instead of silent install to avoid this problem.

For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up.

The Net Logon service must be started to support pass-through authentication of account logon events for computers in a domain.

The Agent for Informix does not support compression at the Agent side.

The Agent for Informix does not support Server/Agent Side Encryption and Secure Migration.

A restore job will fail if you attempt to restore multiple Informix instances on the same media because CA ARCserve Backup cannot restore them sequentially. To successfully restore multiple Informix instances, you can restore them one by one by submitting a new job for each instance after the previous one has been successfully restored.

Encryption is not supported. If server side encryption is enabled for Informix backups, the following message is displayed when the job is submitted:
Warning: Encryption will be skipped for Informix backups

Backup/restore jobs may fail if you repeat the job. In an Informix instance, Windows records the dbspace that is being backed up or restored until the job completes. If that job fails for any reason, the Windows registry does not erase the key value for that dbspace. If you wish to perform another backup/restore job of the same Informix instance, the job will fail unless you erase the registry key value after the failed backup/restore job occurs:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\DSAgent\CurrentVersion\agent\dbaifmx@<Informix_Instance_Name>\LastObject
```

When running a batch job configuration using the Agent for IBM Informix, you can enter only the machine name in the Server and Domain fields. You cannot enter machine IP addresses.

8.7 Known Issues for the Agent for Lotus Domino

The following issues relating to the Agent for Lotus Domino are known to exist in this release:

If possible, avoid server names greater than 79 characters. CA ARCserve Backup will truncate characters that exceed the 79-character-limit and replace the last two (characters 78 and 79) with a 01. If you have additional Domino Servers that exceed this limitation, CA ARCserve Backup will truncate the server name and replace the last two characters in the name using a sequence such as 02, 03, 04. For example:
- If the Domino Server name is 79 characters or more, CA ARCserve Backup will truncate the name down to 79 and modify the last 2 remaining characters as shown in the following examples:
```
Original: 	User11111111112222222222333333333344444444445555555555666666666677777777778888888888  
```
```
First Server:	User11111111112222222222333333333344444444445555555555666666666677777777778888888801
```
```
Additional: 	User11111111112222222222333333333344444444445555555555666666666677777777778888888802  
```
Note: If you are upgrading to the current version of the CA ARCserve Backup Agent for Lotus Domino, the character limitation for server names is still 30 characters. The 79-character limitation is only for new server names.

8.8 Known Issues for the Agent for Microsoft Exchange Server

The following issues relating to the Agent for Microsoft Exchange Server are known to exist in this release:

When you select Microsoft Exchange server directory as the backup source and perform file system backup with the client agent, please note the following:
- If the Exchange Information Store is running, the Exchange server files will be skipped during the backup.
- If the Exchange Information Store is NOT running, the Exchange server files will NOT be skipped during the backup.

If you are restoring an old mailbox store session backed up with the 11.5 version of the BrightStor ARCserve Backup Agent for Microsoft Exchange Server to the Recovery Storage Group, this version of the Microsoft Exchange Server Agent creates all the mailbox stores of the entire storage group to which the mailbox store you wish to restore belonged in the Recovery Storage Group before the restore operation starts actually restoring data.

A new registry key was added to CA ARCserve Backup to control how the Agent for Microsoft Exchange Server backs up storage groups/mailbox databases using multistreaming/multiplexing.
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup\SingleStreamExchangeAgent

Values:

1 means Exchange storage groups are backed up in a single stream

0 (or not set) means the behavior is unchanged (separate streams are used)

Backing up an Exchange Server that includes an empty storage group causes the backup job to fail even though all other storage groups are successfully backed up.

MAPI 6.5.8147.0 or higher should be installed at the Exchange 2010 server in order to browse or restore Exchange doc level data, otherwise it will fail.

If Windows client agent and Exchange agent are installed at the Exchange server and Windows client agent is set to use the password security option, then the Exchange Doc level is unable to browse for backup and restore.

If you browse the Exchange Document level on two different ARCserve servers using different Windows domain accounts, then browsing at the Exchange Document level will fail. If you encounter this problem, UnivAgent service will need to be restarted in order to resolve this issue.

If you choose the Encryption option for a backup job to create a session, then perform a restore job of the backed up session, the session will fail. If you do not choose the Encryption option for the backup job but perform a restore job of the backed up session anyway, the session will not fail. This scenario only happens in r12.5.1 of the Exchange Agent.

8.9 Known Issues for the Agent for Microsoft SharePoint Server

The following issues relating to the Agent for Microsoft SharePoint Server are known to exist in this release:

If you have applied test fix QO94901 to a server running the CA ARCserve Backup Agent for Microsoft SharePoint Server 2007, you may no longer see the SharePoint Farm in the CA ARCserve Backup Manager, and may see an AE9956 Initialization of the COM+ error in the activity log. To avoid this situation, perform the following steps: This came from support.ca.com TEC463588
1. On the machine on which the Agent for Microsoft SharePoint Server 2007 is installed, open Administrative Tools and select Component Services.
2. Select the SPSO12 component and delete it.
3. From the Windows Start menu, click All Programs, CA, ARCserve Backup, Backup Agent Admin.
4. From the pull down menu, choose CA ARCserve Backup for Windows Agent for Microsoft SharePoint Server 2007.
5. From the menu, click Options, Configuration.
6. Update each field and check the box to Reset Credential.
7. Close and reopen CA ARCserve Backup Manager and expand the SharePoint Server Agent to see the Microsoft SharePoint Server 2007 Farm.

If you upgrade the Agent for SharePoint Server 2007 from r12 or r12.1 to r12.5 and you choose the Server Farm Installation (Complete Installation and Web Front End Installation), use a User Name that is the same as the Farm Administrator required to create the Farm to avoid reconfiguring the Agent after installation. This restriction does not affect SharePoint Single Server Installation (standalone).

The CA ARCserve Backup Agent for SharePoint Server does not support restore operations of content databases that have multiple data files spanned across different disks.

When you restore a Wiki Page Library to its original location, the Wiki Page Library link does not appear in the Quick Launch section of the SharePoint Server portal. However, you can find the Wiki Page Library link under the View all Site Content section of the portal.
Note: This is a Microsoft SharePoint Server limitation.

Currently, the Agent for Microsoft SharePoint Server only supports SharePoint 2010 Release Candidate build.

If you restore the entire farm to an alternate farm, then the job will fail. This is a Microsoft issue.

8.10 Known Issues for the Agent for Microsoft SQL Server

The following issues relating to the Agent for Microsoft SQL Server are known to exist in this release:

If an error message appears when you restore and move a database that uses a long file name, rename the database files using shorter file names and perform the restore operation on the database.

The CA ARCserve Backup manager and the CA ARCserve Backup Client Agent must be stopped before uninstalling and reinstalling CA ARCserve Backup Agent for Microsoft SQL Server if they are installed on the same server as the agent.

If a TCP/IP connection fails, or if the Port number has changed, restart the Universal Agent Service.

To support pass-through authentication of account logon events for computers in a domain, the NetLogon service must be started.

When you log into Microsoft SQL Server using Windows authentication to perform Virtual Devices-based backup and restore operations, you must have system administrator rights for Microsoft SQL Server. This is a Microsoft requirement.

If you uninstall a Microsoft SQL Server instance, some components used by other Microsoft SQL Server instances on the machine may be deregistered, including the Virtual Devices mechanism used to perform backups. If this occurs, the agent generates Backup Agent Error 511 ("Error creating Virtual Device Interface: COM class not found") within the error AE50015 ("Backup Failed"), or AE51004 ("Restore Failed"). To address this error, perform the following procedure:
1. Locate the version of sqlvdi.dll that belongs to the newest version of Microsoft SQL Server on the machine.
2. From a command prompt, change to the directory containing the selected sqlvdi.dll, and enter the following command to re-register the Virtual Devices component and re-enable backup operations:
```
	regsvr32 sqlvdi.dll
```

On a primary server running remote SQL, backup jobs submitted via backup manager to the member server may run slowly.

Starting with release 12.0, the Agent for Microsoft SQL Server is now a push agent. To include SQL database files during a backup job, set the BackupDBFiles registry key to 1. The SkipDSAFiles registry key no longer applies to SQL database files. For more information, see the CA ARCserve Backup Implementation Guide or the CA ARCserve Backup Agent for Microsoft SQL Guide.

When restoring a SQL session, the session size shown in the Restore Manager may be larger than the size of the actual session.

The CA ARCserve Backup Agent for Microsoft SQL Server does not support backing up and restoring SQL Server databases where the sum of the characters representing the instance name, the database name, the file group name, and the data file name exceeds 170 characters.

Installing two or more instances of SQL Server concurrently on the same machine creates multiple versions of the SQLVDI.DLL file, which causes conflicts resulting in database backup job failures. To resolve any SQLVDI.DLL conflicts, ensure all instances of SQL Server are at the same Service Pack, security patch or Hotfix level. You may also restart the failed SQL Server instance to reload the new SQLVDI.DLL file or reboot the machine.

When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored. This is because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.

After upgrading Microsoft SQL Server (for example, from SQL Server 7.0 to SQL Server 2000) or installing additional instances, you must run the Account Configuration utility to update the agent with the appropriate changes. If you do not run the Account Configuration utility, CA ARCserve Backup Agent for Microsoft SQL Server will be unaware of the new or changed instances, and you may not have access to additional instances or the additional features of the updated instance. You should also perform your first backup of the upgraded or new instances immediately after running the Account Configuration utility. For information about account configuration, see the Agent for Microsoft SQL Server Guide.

In a cluster environment, run the Universal Agent as a Domain Administrator, rather than as LocalSystem. This is to prevent a conflict of access privileges between the agent and Microsoft SQL Server when backing up Microsoft SQL Server databases.

8.11 Known Issues for the Agent for Open Files

The following issues relating to the Agent for Open Files are known to exist in this release:

If you are upgrading the Agent for Open Files on a remote computer using Unicenter Software Delivery, you must reboot the target machine to complete the installation process successfully.

If you are running eTrust Antivirus 7.1.192 and the Agent for Open Files on the same machine, you must apply a patch to that machine to avoid experiencing slow performance. Contact eTrust Antivirus Customer Support to obtain this patch.

The Agent for Open Files does not provide the eTrust Real-Time scan engine with access to open files to prevent viruses from presenting the scan engine with a version of the infected file concealed as an uninfected file.

When prompted to reboot your machine during remote installation, reboot the machine manually for the remote installation to be successful.

The agent may not start if it detects that an Open File Management product from another vendor is already running on the server. Multiple Open File Management products cannot function on the same server. To resolve this problem, remove the existing Open File Management product from your server and start the agent.

Because of the way that Windows 2000, Windows Server 2003, and Windows XP provides access to encrypted files for backup applications, access to open files is never prevented, so data integrity is not guaranteed. Therefore, the Windows Server Engine does not support the use of encrypted files and their inclusion in a group specification is ignored. Ensure that all encrypted files are closed while your systems are backed up.

To uninstall the NetWare Server Engine, you must manually delete the directory you selected during installation and remove the OFA.NLM file from the SYS:SYSTEM directory. Additionally, you must undo any changes you made to the NetWare autoexec.ncf file.

The NetWare Server Engine supports NetWare 5.1 but it does not support open files on NSS (Novell Storage Services) volumes.

The NetWare Server Engine automatically excludes the default virtual memory swap file on the SYS volume from open file operations. Any swap files on additional volumes must be excluded using the Configuration dialog from the Agent for Open Files Console. Alternatively, configure your backup product to exclude these files. If the swap file is backed up, it may cause the agent to write swap file data to its Preview Data Cache.

If you install the Microsoft Cluster Service after you have installed the Agent for Open Files, you must restart the system to provide the agent with open file access to the shared storage resources of the cluster.

The Agent for Open Files does not support the Transactional NTFS (TxF) infrastructure on Windows Vista and Windows 7. Before you perform backups, make sure you close all applications that have files open in a TxF context, such as installation programs.

Do not use Unicode characters in the groupname added in the Agent for Open Files configuration file (ofant.cfg). They cannot be displayed properly and appear as question marks (?).

The Agent does not support reparse points other than mount points. All other kinds of reparse points including symbolic link files, junction points, or hard links, are treated as regular files.

If you wish to add all files under a root volume to the Agent for Open Files configuration, you must use wildcards as shown in the following example. Specifying only the volume label is not supported:
Use: C:\*.*

Do not use: C: or C:\

When you remotely upgrade the Agent for Open Files on an English System with Chinese locale, you must do the following before you upgrade to ensure Unicode characters are properly displayed:
1. Open the Control Panel and choose Regional and Language Options.
2. Click Advanced.
3. Choose the option, Apply all settings to the current user account and to the default user profile.
4. Restart the machine.

8.11.1 Microsoft Volume Shadow Copy Service (VSS)

The Agent for Open Files now includes support for Microsoft Volume Shadow Copy Service (VSS). The following issues relating to Microsoft VSS are known to exist:

Full backups of Microsoft SQL Server 2005 are possible, but not differential or incremental backups.

In Windows 2003 R2, the DFS Replication Service Writer appears when you expand the machine. In Windows Server 2008, DFS Replication is part of the system state. Therefore, if you wish to backup DFS Replication in Windows Server 2008, you must back up the system state.

If the event log shows a "VSS_E_WRITER_STATUS_NOT_AVAILABLE" error, this indicates that a writer may have reached the maximum number of available backup and restore sessions. Retrying may work when the system is less busy. For more details, see the Microsoft documentation:
http://msdn.microsoft.com/en-us/library/aa384995(VS.85).aspx

8.11.2 Oracle Volume Shadow Copy Service (VSS)

The following issues relating to the Oracle VSS are known to exist:

Instances of Oracle VSS Writer must be running and functional in order to be browsed or backed up by CA ARCserve Backup.

8.12 Known Issues for the Agent for Oracle (Windows)

The following section provides information on support for the Agent for Oracle:

Database files are excluded (skipped) from backups submitted through the Client Agent for Windows up to a limit of 2048 files. If your number of database files exceeds this limit, you must add a DWORD registry value called MaxFileFilter to make sure all database files are properly excluded from the backups made with the Client Agent for Windows:
HKEY_LOCALMACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup

Value Name: MaxFileFilter

Type: DWORD

Value: Set to a value greater than the number of database files you wish to exclude. For example, if there are 3006 DB files, a value of 4096 ensures all database files are excluded from the backup.

When performing a backup of Oracle objects with copies, such as the Oracle Tablespace or full database, the job fails if the BACKUP_TAPE_IO_SLAVES parameter is false. To set this parameter to true, perform the following steps:
1. Open a sqlplus prompt.
2. Enter the following command:
```
alter system set backup_tape_io_slaves = true deferred
```
3. Restart the database.
4. Set the Number of Copies option to a value greater than 1.
5. Submit the backup job.
Note: You may also use the "show parameter backup_tape_io_slaves" command to check the value of the parameter.

When you change the system time on the machine on which Oracle Server and the Agent for Oracle are installed, archive log backups will fail.

When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored. This is because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.

When performing an offline backup of an Oracle RAC9i database with RMAN options from the GUI, CA ARCserve Backup does not put the database into offline mode. To avoid this issue, consider the following:
- Put the database into MOUNT status before performing offline backups.
- Put the database into MOUNT status before performing full database backups without control file restore, system tablespace restore, or undo tablespace restore.
- Put the database into NOMOUNT status before performing full database plus control file restores.
- For user tablespace restores, you do not need to do anything.

When submitting RMAN backup and restore jobs, please ensure that the user is in the Administrators Group on the Oracle Server machine.

The Agent for Oracle (RMAN) does not support special characters used in passwords (for example, '@'). Backup jobs fail if used.

The User Profile feature in this release does not support RMAN command line backup for Oracle agents prior to release 12.5. (User Profile roles were introduced with the r12.5 version of CA ARCserve Backup.)

This version of the Agent is case sensitive. If one modifies the previous job or loads a previous job script before upgrading the agent from earlier versions to the current release (r15), the Oracle database instance may appear twice; once as uppercase and once as lowercase. This issue affects only display, not performance.

r15 Backup Server cannot back up r12.5 or previous releases of the Oracle agent with RMAN mode. If you want to perform RMAN backup of Oracle, please use any version after r12.5.1.

8.13 Known Issues for the Agent for Oracle (UNIX and Linux [RMAN])

The following issues relating to the Agent for Oracle (UNIX/Linux) are known to exist in this release:

If you performed backup jobs with the CA ARCserve Backup for UNIX or Linux Agent for Oracle using a version prior to r11.5 and then upgraded to r11.5 or later, you cannot restore the backup sessions using CA ARCserve Backup.

We recommend that you back up the Oracle RMAN agent using Disk to Disk to Tape feature (Disk Staging). If you chose to back up directly to tape, note you will require more storage media when doing a multichannel backup.

This release of CA ARCserve Backup supports one (1) password per Oracle encrypted backup.

When different table spaces are backed up using different passwords, you must restore them in separate jobs by providing the correct passwords.

This release of CA ARCserve Backup supports Oracle-encrypted backup and decryption restore jobs submitted from the Manager Console (GUI).

This release of CA ARCserve Backup will not show the lock icon for RMAN-encrypted sessions.

Avoid changing passwords after a full backup is done. When password must be changed, do so prior to performing a full backup.

Invalid incremental levels in Oracle 10g:
- For rotation or GFS-rotation jobs, incremental levels are assigned as follows:
  - full backup = incremental level 0 (RMAN)
  - incremental backup = incremental level 1 (RMAN)
  - differential backup = incremental level 1 cumulative (RMAN)
- For non-rotation jobs, you must set an incremental value between 0 and 1 if you are running Oracle 10g. If you are running an earlier version of Oracle, set an incremental value between 0 and 4.

You must use an RMAN Catalog to run jobs with the Oracle option Include Control File Oracle option enabled from the Oracle Restore Manager. If you enabled the control file autobackup feature for the target database before using the Agent for Oracle, use your own RMAN scripts to restore an autobackup of the control file. For more information, see the Agent for Oracle Guide.

Compare Media to Disk is not supported on Agent for Oracle sessions.

Optimize Restore functionality is not supported for the Agent for Oracle.

The Restore by Media and Restore by Session options are not supported for this release.

Encryption Oracle data during the backup phase or the migration phase only supports encrypt data at Backup Server, encrypt data at Agent is not supported.

CA ARCserve Backup does not support restoring multiple, encrypted, Oracle RMAN sessions in a single restore job. You must restore encrypted Oracle RMAN backup sessions as individual restore jobs.

The Agent can support session passwords if Encrypted data at server side is selected from Global Options during backup.

You should reboot the machine whenever you install a new Oracle database to avoid problems loading a driver (OCI.DLL).

If you experience problems expanding the Oracle database after providing the correct login credentials, collapse the machine and then re-expand the tree to refresh the cache.

You must supply the correct host name when registering the Agent for Oracle nodes in the CA ARCserve Backup database. If the Agent machine has a fully qualified name (computer name + domain name, such as NodeName.ca.com), then the full computer name must be used while registering the Agent node.

This release of CA ARCserve Backup does not support protecting Oracle 11g Release 2 data stored on computers running AIX 6.1 operating systems.

8.14 Known Issues for the Agent for Sybase

The following issues relating to the Agent for Sybase are known to exist in this release:

For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up.

To support pass-through authentication of account logon events for computers in a domain, the NetLogon service must be started.

The agent does not support table-level backup or restore operations.

We recommend that you avoid canceling restore jobs. If you cancel a restore job, your database is marked Do Not Recover or Suspect. If this happens, you must recreate the database before starting another restore job.

The Backup with Compare and Backup with Scan Tape options are not supported for agent sessions. Additionally, the Backup with Delete File option is not supported on agent sessions.

When Sybase Adaptive Server devices are mirrored, only the actual device information (the database on the device) is backed up; data in the mirror device is not backed up.

Alias names for Windows servers are not supported for database backup or restore operations using the Client Agent for Windows.

The agent does not support multiserver and cluster environment backup or restore operations.

The agent supports only the Restore by Tree and Restore by Session options.

For Sybase ASE 12.5, if the configuration parameter Enable xact coordination is set to On (the default setting), you cannot restore some Sybase system databases, such as sybsystemdb and the master database. To restore these system databases, disable this configuration parameter. To restore these databases for Sybase ASE 12.5, reset the Sybase ASE 12.5 setting Enable xact coordination or the restore fails. To reset the Enable xact coordination parameter, perform the following steps:
1. From a DOS command prompt, start isql.
2. Enter the command:
```
	1>sp_configure "enable xact coordination", 0
	2> go
```
3. Restart the Sybase server.

If you restore the master database remotely and the Sybase source instance name is the same as the remote destination instance name, the job succeeds. However, when the Sybase source instance name is different from the remote destination instance name, the job fails.
When you restore the master database, the contents of the sysservers system table of the master database in the destination instance is identical to the contents of that system table in the source instance and the row that records the Sybase backup server name is incorrect. To address this issue, update the row using the following SQL statement:
```
update sysservers set srvnetname=remote destination
Sybase backup server name where srvname="SYB_BACKUP"
```
Note: This name is case sensitive. You can find this name in the Windows registry.

To verify, use the following SQL statement:
```
select * from sysservers where srvname="SYB_BACKUP"
```

Sybase 11.9.2 is no longer supported.

If a source is missing in restore tree view, it may be a case-sensitive issue. Turn on case-sensitivity during database setup process.

Sybase database sessions backed up with BrightStor Enterprise Backup 9.01 or 10.5.1 cannot be restored to their original location. To resolve this issue, perform the following steps:
1. Open Restore Manager, choose Restore by Session at the Source tab.

2. Select the session you want to restore.

3. Choose the Destination tab and clear the checkmark next to the option, Restore files to their original location.

4. Select the destination server and then select the Sybase Server instance on the destination server.

5. Submit the restore job.

For Sybase ASE 15, after you have installed the database server, please check the system table sysservers information and ensure the "srvnetname" for "SYB_BACKUP" is not "SYB_BACKUP" or your backup and restore jobs will fail. If the "srvnetname" for "SYB_BACKUP" is "SYB_BACKUP", perform the following steps:
1. Open a command line prompt and start isql.

2. Enter the following:

1> sp_configure "allow updates to system tables",1
```
2> go
```
```
1> update sysservers set srvnetname='ServerName_BS' where srvname='SYB_BACKUP'
```
```
2> go
```
```
1> sp_configure "allow updates to system tables",0
```
```
2> go
```

8.15 Known Issues for the Agent for Virtual Machines

The following issues relating to the Agent for Virtual Machines are known to exist in this release:

On Windows Server 2008 machines with the Hyper-V role enabled, performing a full backup of Hyper-V VSS writer may sometimes cause the operating system to generate warning messages about the removal of the storage miniport driver, such as:
```
Device 'Storage miniport driver' VMBUS\{d6b9a233-a170-4602-9863-78f7c287c7df}\1&3189fc23&0&{d6b9a233-a170-4602-9863-78f7c287c7df}) has been lost from the system because the preparation for removal was not performed first.
```
```
Device 'Msft Virtual Disk SCSI Disk Device'(SCSI\Disk&Ven_Msft&Prod_Virtual_Disk\2&7aef4bc&0&000000) been lost from the system because the preparation for removal was not performed first.
```
This is a known Microsoft Hyper-V VSS writer problem that does not affect the success of the backup job. You can still successfully perform data restore jobs. When all virtual machines under Microsoft Hyper-V VSS Writer are displayed as Backup Using Saved State-virtual machine name, this problem does not occur.

On Windows Server 2008 machines with the Hyper-V role enabled, the VM backup job may fail in certain environments, and records the following errors in the CA ARCserve Backup Activity Log:
```
E12586 This VSS Writer (\\TX200S3x64\Microsoft Hyper-V VSS Writer) has reported a failure during the freeze event.
```
```
E12606 Selected Writer option cannot be obtained.
```
```
E12586 This VSS Writer (\\TX200S3x64\Microsoft Hyper-V VSS Writer) has reported a failure during the freeze event.
```
With this error, the Hyper-V VSS writer crashes. This is also a known Microsoft Hyper-V VSS writer issue.

The Recover VM job for VMware VMs fails if the backup proxy system has "VMware converter enterprise for Virtual Center" installed.

If you install CA ARCserve Backup and the CA ARCserve Backup Agent for Open Files on a virtual machine without a license for the CA ARCserve Backup Agent for Virtual Machines, license checking generates pop up messages and fills the Event Viewer with license error messages for 32VR and 3AVM.

When you perform granular restores using the Agent for Virtual Machines, the global options, Create Base Directory or Do Not Create Base Directory are not applied for internal sessions. The restored files are placed under the full path that existed at the time the backup was performed.

The Agent for Virtual Machines does not support the recovery of r12 or r12.1 backup sessions using the Overwrite global option.

Backup jobs associated with Windows Server 2008 R2 and Windows 7 VMs running on VMware ESX Server 4.0 systems may fail when VMware attempts to create snapshots of the VM. For more information, see the following Knowledge Base document on the VMware website: http://kb.vmware.com/kb/1009073

File mode backups of Windows Server 2008 R2 and Windows 7 VMs may fail when using VMware Consolidated Backup (VCB) to execute VM backup operations.
To remedy this problem, use one of the following approaches:

Rotation backups and GFS backups--Submit your rotation and GFS backups as Mixed mode backups with the Allow file level restore option and the Use Client Agent for Windows option (global backup option) specified. This approach ensures that CA ARCserve Backup processes all subsequent incremental and differential backups using the Client Agent for Windows, which is running in the VM, rather than using VCB to process the backups.

Raw backups--Submit your Raw (full VM) backups using the Raw backup mode with the Allow file level restore option specified. With this approach, CA ARCserve Backup creates a backup session for the Raw (full VM) backup and sessions for the individual volumes contained in the VM. You can then view the raw session and the sessions for the volumes contained in the VM in the Restore Manager window.

When using the VDDK approach to perform file mode backups of Windows 7 VMs, CA ARCserve Backup cannot back up Windows 7 volumes, and returns the following message in the Activity Log:
```
AW0004 Failed to open file <Mount directory path\VM name\letters\Volume> RC=2, The system cannot find the file specified.
```
There is no workaround for this problem.

The agent does not support performing file mode backups using VDDK on GUID Partition Table (GPT) disks.

After successful recovery of the VMware VM, Disk Provisioning Type of the Virtual Hard Disk will always appear as "THICK", for the recovered VM.

To recover a Hyper-V VM for an alternate server, both servers must have the same network name, otherwise the VM is unable to reboot after recovery. As a workaround, remove the network adapter from the VM settings of the recovered VM before rebooting the machine.

8.16 Known Issues for the Enterprise Option for AS400

The following issues relating to the Enterprise Option for AS400 are known to exist in this release:

The Agent uses your session password only for encryption. If you do not enable encryption at the agent side when performing a backup, the session password is not validated when you restore the agent session.

8.17 Known Issues for the Enterprise Option for IBM 3494

When using the Enterprise Option for IBM 3494 with the Storage Area Network (SAN) Option, the Tape Engine on the distributed machines may fail. To prevent this failure, ensure that the most current IBM tape driver is installed on the primary and distributed machines. To do so, perform the following procedure on each machine:

Find the type of IBM drive installed:
- Ultrium and Magstar (Windows 2003): ibmrmsst or ibmtp2k3

Find the registry key for this drive in the directory:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\type of IBM drive.
```
For example, for an Ultrium drive, find the registry key for the drive in the following directory:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmlto
```

Create the DWORD value DisableReserveUponOpen and set it to 1.

Exit regedit and restart your computer.
Note: For information on installing SAN distributed servers, see the Storage Area Network (SAN) Option Guide.

8.18 Known Issues for the Enterprise Option for SAP R/3 Oracle

The following issues relating to the Enterprise Option for SAP R/3 for Oracle are known to exist in this release:

Multistream function is supported locally only.

Because all archived redo log files must be removed after recovery is complete, all Recover Database using Backup Control File commands must be followed by the Alter Database Open Resetlogs command.

The Backup with Compare and Backup with Scan Tape options do not apply to sessions using the Serverless Backup Option when using Oracle. These apply to Windows only.

Before you shut down the Oracle Server in normal mode, you should shut down the local CA ARCserve Backup Manager and the CA ARCserve Backup Client Agent for Windows RPC Service.

When performing a remote backup from the Client Agent for Windows tree, use the Server NetBIOS name (machine name) for the agent node name. The Client Agent for Windows prompts you to specify the Use Computer Name Resolution option or the IP address to include the databases when backing up the entire machine.

The IP address and hostname of the Agent and base machines should be added to the hosts file on each system before running any backup and restore jobs.

BACKINT supports only one instance at a time. If you define multiple instances, BACKINT saves only the first instance to the BACKINT registry. The Enterprise Option for SAP R/3 for Oracle Configuration utility modifies the information for this instance. For BACKINT to support other instances, change the SID value in the BACKINT registry, and rename the initSID.utl in %ORACLE_HOME%\database to your SID.

When you use BRRESTORE to restore objects to different destinations, BACKINT restores these objects to the location on which BRRESTORE is define, if CA ARCserve Backup is not installed on the local machine.

For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up.

The NetLogon service must be started to support pass-through authentication of account logon events for computers in a domain.

For command line, only the BACKINT command interface is supported.

When submitting command line backup and restore jobs, Server Side Encryption and Secure Migration are not supported.

When submitting command line backup and restore jobs, hold jobs are not supported.

If you are running the Enterprise Option for SAP on a remote system and submitted backup jobs to a backup server having more than one NIC installed, the jobs fail due to connection problems. To avoid this situation, add a machine IP mapping in the client hosts file for the server:
1. On the remote system running the SAP option, go to the Windows\System32\drivers\etc folder.
2. Open the hosts file.
3. Add host/IP map as below:
```
<IP address> machine_name
```
  where <IP address> is the IP of the backup server machine
4. Save and close the hosts file.

When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored. This is because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.

8.19 Known Issues for the Enterprise Option for StorageTek ACSLS

The following issues relating to the Enterprise Option for StorageTek ACSLS are known to exist in this release:

If you are sharing a StorageTek ACSLS library using an AS400 system, create the following DWORD registry key and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\TapeEngine\Config\ShareWithAs400
```

8.20 Known Issues for the Disaster Recovery Option

The following issues relating to the Disaster Recovery Option are known to exist in this release:

Disaster Recovery restore jobs running on IA64 systems may display this error even though the tape library is connected and media is present: "Media not found. Insert media." The problem appears limited to IA64 systems running Windows 2003 with the Emulex LP10000 FC card.

One Button Disaster Recovery (OBDR) scans the first OBDR device found by the Tape Engine. Ensure the OBDR tape is in the first tape drive to restore successfully.

After Disaster Recovery is completed, the size of the last partition recovered can be expanded from the original size by as much as 8 MB. The problem occurs if there is free space at the end of the last partition on the disk being recovered.

For Microsoft SQL-hosted CA ARCserve Backup databases, the operating system will record numerous application errors of MSSQL$ARCSERVE_DB to the Event Log during recovery of the database, such as:
- 8355
- 17204
- 17207
Since these events are recorded by the recovery of the database, they pose no problem.

When CA ARCserve Backup server (Primary or Member) is configured in Cluster with the Disaster Recovery Option installed, the "Alternate Location for DR Information" setting may not be stored when the cluster is ready after installation. Reconfigure this setting by running the DR Book Kit Wizard Utility from Active Node and re-enter it.

Use of a Japanese USB Keyboard during floppy disk disaster recovery is not supported on Windows 2000 systems. Japanese USB keyboards may be used during bootable CD disaster recovery on such systems.

During Disaster Recovery from a bootable CD, you may be prompted to insert a disk into the floppy drive before inserting the Machine Specific Disk. It is safe to ignore this message and click OK to continue.

The database engine will not start automatically after successful recovery of the CA ARCserve Backup database. Upon the first reboot after performing Disaster Recovery of the CA ARCserve Backup server hosting the ARCserve database, you must restart the database engine. Do so through the CA ARCserve Backup Manager Console.

When performing Disaster Recovery on Microsoft Windows XP, Windows 2003 or Windows 2008 systems, the Create Folder button may not work when attempting to save logs. To save logs, create a new folder using the mkdir command with the Open Console button or save logs into an existing folder.

Before you perform Disaster Recovery on a Windows 2003 machine, use the Disaster Recovery Boot Kit Wizard to create a CD that contains the following:
- OS
- Machine-Specific Disk
- Drivers for NIC cards
- CA ARCserve Backup
Note: Use this re-mastered CD to perform Disaster Recovery on these machines to avoid Unsigned Driver errors with some NIC cards that could make USB input devices (such as keyboard or mouse) unusable during system recovery.

If your system is configured with a number of volumes mounted via mount points, Disaster Recovery cannot be performed correctly. You must format and restore data manually.

If an iSCSI LUN is being used as a shared disk by a failover cluster, that LUN cannot be restored while performing Disaster Recovery of the cluster.

Consider the following situation:
CA ARCserve Backup is installed on Server A. On Server B, two shared folders exist and are configured on Server A as remote File System or Data Deduplication devices using different Windows accounts. When using the Disaster Recovery option to restore backup data from these devices, CA ARCserve Backup will be able to connect to only one. Connection to the second device fails with Windows error 1219 because multiple connections to shared resources by the same user, using more than one user name, are not allowed.

Creating MSD on floppy disk using Windows Server 2008 IA64 systems may fail if you integrate NIC drivers at the same time because the floppy drive capacity is exceeded. To avoid this issue, use USB memory sticks (supported on Windows Server 2008).

When performing remote disaster recovery from MSD/FD that includes certified NIC drivers on Windows XP and Windows 2003 (32-bit and 64-bit platforms), an error may appear that the driver is not certified, making it impossible to use the keyboard and mouse. This is a known Microsoft issue. Using the integrated bootable CD for disaster recovery can overcome this limitation. Alternatively, you may manually modify your MSD. To do so, follow the solution described in the Microsoft Knowledge Base article, KB-887494, using the following information:
1. Manually modify the asr.sif file on MSD:
  1. Open the asr.sif file using a text editor.
  2. Locate the section [INSTALLFILES]:
    4=1,"CADRIF","\Device\Floppy0\","oem3.inf","%SystemRoot%\inf\driver.inf","CA"
    
    5=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%SystemRoot%\Driver Cache\driver.sys","CA"
    
    6=1,"CADRIF","\Device\Floppy0\","vmware-nic.cat","%SystemRoot%\Driver Cache\driver.cat","CA"
    
    7=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%SystemRoot%\Driver Cache\driver.dll","CA"
  change these files to %TEMP%:
  
  4=1,"CADRIF","\Device\Floppy0\","oem3.inf","%temp%\driver.inf","CA"
  
  5=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%temp%\driver.sys","CA"
  
  6=1,"CADRIF","\Device\Floppy0\","vmware-nic.cat","%temp%\driver.cat","CA"
  
  7=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%temp%\driver.dll","CA"
  
  Do NOT change these files or you will be unable to perform DR:
  
  1=1,"CADRIF","\Device\Floppy0\","DrLaunch.exe","%SystemRoot%\system32\DrLaunch.exe","CA"
  
  2=1,"CADRIF","\Device\Floppy0\","DrLaunchRes.dll","%SystemRoot%\system32\DrLaunchRes.dll","CA"
  
  3=1,"CADRIF","\Device\Floppy0\","DrLaunchEnu.dll","%SystemRoot%\system32\DrLaunchEnu.dll","CA"
2. Manually create a file called winnt.sif on MSD and open it in a text editor, for example, Notepad.
3. Write the following text into the winnt.sif file:
  [Data]
  
       MsDosInitiated = 0
       UnattendedInstall = Yes
  
       [Unattended]
       OemPreinstall = YES
       OemPnPDriversPath = TEMP

When recovering a Windows Server 2008 R2 server from a disaster using Disaster Recovery Option, the cmd.exe - No Disk message box appears and displays the message, "There is no disk in the drive. Please insert a disk into Drive A:." The message box appears in the following scenarios:
- You created machine-specific disks using a USB-connected device after the backup completed, and the server contains a floppy drive.
- You created machine-specific disks using a USB-connected device or a floppy disk drive on a server that contains an RD1000 drive.
To remedy this problem, click Continue on the cmd.exe and wpeinit.exe - No Disk message box. Then, press Alt + Tab or Alt + Esc to display the Disaster Recovery Option dialogs.

When recovering backup servers running Windows Server 2008 R2 IA64, CA ARCserve Backup may not be able to detect file system devices connected to remote computers running Windows Server 2003 or Windows XP. This problem also occurs on various x64-based computers running Windows Server 2008 R2 (for example, Dell GX755 desktop).
To remedy this problem, do the following:
- IA64 platforms--Use the Windows Server 2008 IA64 CD image instead of the Windows Server 2008 R2 IA64 CD image to start the disaster recovery process.
- x64 platforms--Use the Windows Server 2008 x64 CD image instead of the Windows Server 2008 R2 x64 CD image to start the disaster recovery process.

Avoid assigning drive letters A through Z to disk partitions if using the Disaster Recovery Option on Windows Server 2003 systems. When all drive letters are assigned, the CD cannot be mounted and disaster recovery fails.

When performing disaster recovery from SAN disks, all disks except for the boot disk are offline and read-only, and therefore fail to be recovered. To avoid this situation, perform the following:
1. Before you load your MSD during the DR process, go to Utilities, Run and type diskpart. Press Enter. This launches the diskpart utility.
2. Type list disk to detect all disks attached.
3. For each disk, use the following command to see if it is offline or read-only:
```
select disk 1
```
```
detail disk
```
4. If a disk is offline, use the "online disk" command to bring it online.
5. If a disk is read-only, use the "attributes disk clear readonly" command to remove the read-only flag.

You cannot log in to CA ARCserve Backup with a blue screen (error code: 000000FC) when performing disaster recovery from a Physical Machine (DELL 270) to a Virtual Hyper-V environment. To resolve this issue, log in to CA ARCserve Backup by performing the following steps:
1. Press F8 when the startup menu appears, use the arrow keys to select the safe mode option, and then press ENTER.
2. Click Start, Run, and type 'cmd', and then click OK.
3. At command prompt, type the following and then press ENTER:
```
bootcfg/raw "/noexecute=alwaysoff /fastdetect" /id 1
```

Disaster Recovery uses Windows ASR API to recover disk partition layouts. But the behavior for recovering dynamic disk is different from creating dynamic disk from disk manager, therefore the disk data offset will proceed in a different way. For this reason, only a few MB of unallocated disk space is left after Disaster Recovery.
Note: This is the behavior of Windows ASR. Since there is no data loss, you can ignore it, although you will find that the usable disk space will be different before/after Disaster Recovery.

When running disaster recovery for a member server that has an old ASDB with the CA ARCserve Backup Agent for Microsoft SQL Server (primary server demoted or ASDB uninstalled), an incorrect warning message is displayed during the the ADR process at "Choose Mode".
```
After you reboot the system, run the utility, AsRecoveryDB.exe on the primary server. You must recover the ASDB before you perform any other operations. 
```
You may also see a "Useless Session - SQL DR Element" message. This is because the ASDB is backed up and written in machine-name.ses file. Member servers use the machine-name.ses file to determine whether an ASDB session existed. If so, this message is shown. This issue and message have no impact on Disaster Recovery functionality. The system and member server can be recovered after disaster recovery.

8.21 Known Issues for Dashboard

The following issues related to Dashboard are known to exist in this release:

The Agent Distribution Report does not display OpenVMS and AS400 agent information.

Dashboard reports do not display network backup or preferred shares backup nodes.

Nodes running the CA ARCserve Backup Agent for Microsoft Exchange Server 2007 are not displayed in the SRM reports, unless you change the CA ARCserve Backup Universal Agent login account from Local System to Domain account with administrator privileges, as follows:
1. Click Start, Control Panel, Administrative Tools, Services to open the service control manager.
2. Right-click the CA ARCserve Backup Universal Agent and choose Properties from the shortcut menu.
3. On the Log On tab, click This Account and enter the domain name/user name, followed by your password. Confirm the password and click OK.
4. Click OK to clear the confirmation message.
5. Right-click the CA ARCserve Backup Universal Agent and choose Restart from the shortcut menu.

For CA ARCserve Backup running in a cluster environment, the SRM reports for virtual nodes displays the same information as that of the currently active node.

Recovery points for the following cases are listed on the Node Recovery Points Report rather than on the Virtual Machine Recovery Points Report:
1. Microsoft Hyper-V virtual machines backed up in file mode
2. VMware Consolidated Backup (VCB) jobs in file mode performed with the CA ARCserve Backup Client Agent for Windows (mixed mode VM GFS/rotation jobs)

The last backup status for the following cases are displayed on the Node Backup Status Report rather than on the Virtualization Most Recent Backup Status Report:
1. Microsoft Hyper-V virtual machines backed up in file mode
2. VMware Consolidated Backup (VCB) jobs in file mode performed with the CA ARCserve Backup Client Agent for Windows (mixed mode of VM GFS/rotation jobs)
3. Backups that failed because of incorrect credentials of VMware VCB proxy server/ ESX server/ Microsoft Hyper-V host server while submitting the backup job.

Dashboard reports may not display the VM node information when backed up through VMware VCB or Microsoft Hyper-V if you perform backup of a Virtual Machine for the first time and the backup fails because of the following reasons:
- The VMware VCB proxy server or Microsoft Hyper-V host server is unreachable over the network.
- You have supplied incorrect credentials of VMware VCB proxy server/ ESX server /Microsoft Hyper-V host server while submitting the backup job.

If you upgraded your CA ARCserve Backup server and agent nodes from a version prior to release 12.5, please note the following behavior with Dashboard reports:
- If you have run encrypted backup jobs for some nodes prior to upgrade, those nodes are displayed on the Nodes Encryption Status Report as "Nodes without encrypted sessions".
- If you have run encrypted backup jobs for some nodes prior to upgrade, those tapes are displayed on the Tape Encryption Status Report as "Tapes without encrypted sessions".
- If you have run full node backup jobs for some nodes prior to upgrade, those nodes are displayed on the Node Disaster Recovery Status Report as "Nodes not Eligible for Disaster Recovery".
- If you have run backup jobs for some remote nodes prior to upgrade, those nodes are displayed on the Agent Distribution Report as "Version undetected".
- For the Agent Distribution Report to display accurate information after upgrade, you should browse/expand the nodes one time in the Backup Manager or run another instance of the same job to correctly update and display this information.
- If you have run backup jobs for some nodes to tapes or file system devices prior to upgrade, the Data Distribution on Media Report will not display any information.
- If you have run backup job for some nodes prior to upgrade, the Deduplication Status Report will display 0 in the 'Raw Backup size' column of the drill-down report.
- If you have run backup jobs for some Virtual Machines through VMware Consolidate Backup prior to upgrade, the Virtualization Most Recent Backup Status Report and Virtual Machine Recovery Points will not display any information.
After upgrading, run another instance of the same job to correctly display this information.

The Memory Report may display slightly lesser memory size values for Virtual Machine nodes running CA ARCserve Backup Agent for Virtual Machines that are backed up through Microsoft Hyper-V. This is a known Microsoft issue because the Virtual Machine Management needs a little overhead for each virtual machine.

When you create a Dashboard email schedule on the CA ARCserve Backup primary server running on a Windows Server 2008 operating system, the scheduled email from the Dashboard may not send the reports to the recipients specified in the Dashboard email schedule. This problem occurs because of an issue with Microsoft .NET Framework 3.5 SP1 and can be resolved by applying the appropriate hot fix on the primary server machine. You can download the hot fix directly from the Microsoft downloads website. For x86 and x64 systems, search for KB959209.

During installation of this release of CA ARCserve Backup on Windows 2008 operating system, there may be cases where the automatic installation of .NET Framework 3.5 SP1 fails, resulting in a blank screen when you launch Dashboard. If this occurs, you need to manually install the .NET Framework 3.5 SP1 and also need to reboot your system. You can install a patch from Microsoft to address this problem (search for patch 947821).

If you performed a backup of a node using the command line (ca_backup), CA ARCserve Backup Dashboard may not display any data in the corresponding reports. To view the data for this node, perform the following steps:
1. Add the same node to the Backup Manager GUI by right-clicking on the Windows Systems objects and choosing Add Machine/Object from the shortcut menu.
2. Expand the node in the Source directory tree by giving administrator or equivalent user credentials.
The node now displays data in the Dashboard reports.

The Dashboard Client Node Software Report cannot retrieve the values for certain optional properties, such as install date.

Dashboard SRM cannot detect same versions of the 32-bit and 64-bit Oracle installed on the same 64-bit production server.

The Client Node Software report does not display the backup status or time for jobs submitted with the Agent for Informix. To avoid this problem, add the node to the GUI using the real host name instead of the IP address.

8.22 Known Issues for the CA ARCserve Backup Global Dashboard

The following issues are known to exist in this release:

If a branch site is in the process of performing a full/incremental data synchronization with the central site, and the network connection breaks between the branch site and the central site, the status of the branch site in the Central Manager UI will remain in the same state ("Full/Incremental synchronization in progress") until the network link is up again. When the network link is up, a synchronization retry will be attempted based on your pre-configured settings for that branch site

When you create a Dashboard email schedule on the CA ARCserve Backup Central Primary Server running on a Windows Server 2008 operating system, the scheduled email from the Dashboard may not send the reports to the recipients specified in the Dashboard email schedule.
This problem occurs because of an issue with Microsoft .NET Framework 3.5 SP1 and can be resolved by applying the appropriate hot fix on the primary server machine. You can download the hot fix directly from the Microsoft downloads website. For x86 and x64 systems, search for KB959209.

If you have an existing Global Dashboard environment, with a Central Primary Server and at least one registered Branch Primary Server, and you are upgrading CA ARCserve Backup from r12.5 or r15 to r15 SP1, we recommend that you upgrade the Central Primary Server first, and then each of the Branch Primary Servers.

For Global Dashboard, the Central Primary Server does not support being installed on a Microsoft Active Directory domain controller machine.

If a new branch site is registered and synchronized to the central site, you must re-launch CA ARCserve Backup Dashboard for the reports to display the data from the new branch site. Until CA ARCserve Backup Dashboard is re-launched, data from the new branch site will not be included in any Dashboard reports and the branch site name will not be included in the branch filter options.

8.23 Known Issues for the Image Option

The following section provides information regarding issues known to exist in this release of CA ARCserve Backup for the Image Option:

The Restore Manager window cannot display file-level details of backup sessions under the following conditions:
- The data was backed up using a previous release of BrightStor ARCserve Backup.
- Staging was enabled for the backup.
- Data migration job for the backup to the final destination media was submitted AFTER you upgraded to this release.
To remedy this condition, open the Restore Manager and browse to the sessions that migrated after you upgraded to this release of CA ARCserve Backup. You must then execute a Merge job on the migrated sessions.

8.24 Known Issues for the NDMP NAS Option

The following issues relating to the NDMP NAS Option are known to exist in this release:

The EMC Celerra NDMP daemon has a maximum of eight (DART 5.4) concurrent connections. The NDMP NAS Option uses concurrent and persistent device connections. Each tape drive and TLU managed by the EMC data mover counts as a separate connection. Each backup, restore, or browse function also counts as a separate connection. If you exceed eight connections, you may encounter problems. We recommend that you keep this in mind when planning and implementing your storage topography.

If you have multiple NIC cards on the backup server, you cannot connect to the option. To connect to the option, you must add the loop back address for the backup server to the hosts file (the entry should be similar to the following):
```
127.0.0.1	HOSTNAME
```

Network Appliance Filers with OnTap 6.2.x and 6.3.x require a Network Appliance patch to fix a known Direct Access Restore (DAR) issue with spanned DAR recovery operations.

Sessions backed up with <BEB> 10.0 Service Pack 3 or earlier must have the following registry key set to 1 before starting a restore operation:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\ARCserve Backup\NASAgent
```

The option does not support installation on the Member server.

The option does not support Job failover.

The option does not support encryption. If server side encryption is enabled for NAS backup, the following message is displayed when the job is submitted:
```
Warning: Encryption will be skipped for NAS backups.  Click OK to continue.
```

You can use Direct Access Restore for files only. If you restore at least one folder, the restore operation reverts to scanning the session. This limitation does not apply to Network Appliance.

Procom does not support multiple backup filters.

When configuring the agent and the NAS device, you must use either an IP address or host name for both. Using a mixed configuration can result in a 3-way backup.

Dynamic Device sharing (DDS) configuration in a SAN environment with NAS is not supported on a cross-platform Windows SAN environment.

To use DDS on EMC Celerra, you must set the NDMP.scsiReserve parameter to 0 on the data mover. This parameter is available starting with release 5.2.15.0. For more information about this issue, see EMC's Celerra documentation.

To allow CA ARCserve Backup to connect to Network Appliance filers through Preferred Shares, you must create an ADMIN$ share for the volume containing the /ETC folder on the NAS server.
Note: Do not back up NAS devices through Preferred Shares, as it does not utilize the NAS-attached backup device or the NDMP protocol for proper NAS operating system backup procedures.

Before you restore a differential or incremental NAS session, ensure that the previous full backup has been restored:
1. Perform Restore by Session.
2. Submit a job to restore the full session
3. Submit another job to restore the differential session to the same directory as the previous restore.

Filters are not supported on restores.

8.25 Known Issues for the Storage Area Network (SAN) Option

The following issues relating to the SAN Option are known to exist in this release:

Mixed SAN environments are no longer supported. This is to say that in ONE CA ARCserve Backup Domain, there can only be ONE Primary server. So if there are to be multiple SAN's in your environment, they either need to be in separate CA ARCserve Backup domains or they have to share the same Primary server, with devices from both SAN's zoned to the same Primary server.

8.26 Known Issues for the Tape Library Option

The following issues relating to the Tape Library Option are known to exist in this release:

Optical Library Option command line commands are not supported for the Device Manager.

The option does not support multistreaming. If you enable multistreaming, you must install the Enterprise Module Option.

If you receive the error message "Windows - No Disk, There is no disk in the drive. Please insert a disk into drive \Device\HardDiskx\DRx," you must exclude the tapeeng.exe process from scanning by eTrust. To exclude the tapeeng.exe process from scanning, perform the following procedure:
1. In the Realtime Monitor Options dialog of eTrust, click the Filters tab.
2. On the Filters tab, in the Exclusions group box, click the Process button. The Exclude Processes dialog opens.
3. In the Exclude Processes dialog, enter tapeeng.exe in the Enter a process name field and click Add. The tapeeng.exe process appears in the List of Excluded Processes.
4. Click OK to close the Exclude Processes dialog and click OK to exit the Realtime Monitor Options dialog.

Tape Engine may corrupt the device view structure of RSM. Some storage devices cannot be used by the Tape Engine and RSM simultaneously. To restore the device view structure of the removable storage service, stop the Tape Engine and restart the removable storage service.

If you want to import a cleaning tape with a barcode prefix that is not CLN, or has no barcode, choose one of the following tasks to avoid unrecognized media errors:
- Open Library Properties, select Clean by Slot, add a slot into Clean Slots. Import the cleaning tape into the Clean Slot.
- Open Library Properties, select Clean by Barcode, enter the barcode prefix or whole barcode of the cleaning tape. Import the cleaning tape into any slot of the tape library.

CA ARCserve Backup cannot automatically disable Removable Storage Manager (RSM) devices on 64-bit systems. The Tape Engine is automatically started after CA ARCserve Backup is installed and the Tape Engine Auto Configuration cannot configure RSM devices correctly. Warning message W6978 appears in the Activity Log. If you are running CA ARCserve Backup on a 64-bit system, you must manually disable backup devices in RSM to avoid this problem. On a 64-bit system, you will not be able to do this using the CA ARCserve Backup Manager Console because it cannot display any RSM-controlled devices for enabling or disabling.
If you are running the CA ARCserve Backup Manager Console on a 64-bit system, you must disable RSM so that CA ARCserve Backup can use the device. To disable RSM, perform one of the following:
- If CA ARCserve Backup has already been installed:
  - Stop the Tape Engine. Disable RSM-controlled devices using the RSM Computer Management utility. Restart the Tape Engine.
- If CA ARCserve Backup has not yet been installed:
  - Attach the library to the server. Reboot the server. Disable RSM-controlled devices using the RSM Computer Management utility. Install CA ARCserve Backup.

8.27 Known Issues for Central Agent Admin

The following issues regarding CA ARCserve Backup Central Agent Admin are known to exist in this release:

When viewing event logs using the Central Agent Admin on Windows Server 2008 and Windows Server 2008 R2 systems, you may receive a "Can't parse this event log" error. This is a known Microsoft problem.

8.28 Known Issues for Displaying Non-English Characters

The following issues are known to exist in this release:

You must set Regional and Language Options identically on primary and member server machines to avoid garbled text or characters replaced by question marks (?).

In the Submit Job dialog, Destination Node is displayed with 'garbage' characters when you submit a job to a Unicode surrogate pair destination. Multilingual characters that cannot be represented by a one double-byte code can usually be represented in Unicode using its surrogate pair feature. The Submit Job dialog cannot display surrogate pairs. This is a display issue and does not impact the job itself.

When setting the caroot password using the CA ARCserve Backup Configuration Wizard, do not use Unicode characters. Unicode characters are interpreted as "?" and because the question mark is an acceptable character in the caroot password, log in succeeds with any Unicode character entered. Once set, you will not be able to change it using the CA ARCserve Backup Manager Console.

Do not use Unicode characters in the groupname in the Agent for Open Files configuration file (ofant.cfg).

The Agent for Virtual Machines does not support the use of non-English characters in VM names.

If you used JIS2004 characters in a file or directory name that was backed up prior to installing this version of CA ARCserve Backup, Restore Manager will not be able to display or restore the file or directory name correctly. However, the file or directory contents can be correctly restored.

Scan Engine does not support Unicode. Therefore, you cannot use the Enable Virus Scanning option when backing up or restoring files and folders that contain Unicode characters in their names.

As of the r12 SP1 version of CA ARCserve Backup, Unicode is supported. Diagnostic reports created in this version of CA ARCserve Backup can be opened only with versions of CA ARCserve Backup at r12 SP1 and later.

Backup jobs submitted using BrightStor ARCserve Backup r11.5 Agents (includes all service packs) and CA ARCserve Backup r12 Agents that contain Unicode characters in their directory names and file names will fail after you upgrade to this release. To avoid this problem, specify the parent directory of the directories, files, or both that contain Unicode characters and then resubmit the job.

Microsoft Windows does not support Unicode characters in the command line interface, therefore, you cannot use the Windows command line to enter CA ARCserve Backup commands containing Unicode characters. Use the Windows Powershell instead of cmd.exe, or use the -f switch to save text files as Unicode files.

The DBAconfig.exe module does not support Unicode.

8.29 Known Issues for Documentation

The following section provides information about issues relating to the documentation for CA ARCserve Backup that are known to exist in this release.

Note: You can access the most up-to-date product documentation (PDFs) from the CA ARCserve Backup website at https://support.ca.com/prodinfo/arcserve

Alert Manager Help

Step 3 in the Adding Broadcast Recipients help topic should include the following:
Important! If you add an independent recipient machine manually, you must add "\\" in front of the machine name.

Device Configuration Help

The Help button on the Device Configuration dialog for the UNIX/Linux Data Mover Configuration does not display the online help. To view the help topic, open the CA ARCserve Backup Help and locate or search for the topic Register the Data Mover Server with the Primary Server Using Device Configuration.

8.30 Known Issues for the CA ARCserve Backup Infrastructure Visualization

The following issues related to Infrastructure Visualization are known to exist in this release:

The Agents view does not display OpenVMS and AS400 agent information.

Visualization views do not display network backup or preferred shares backup nodes.

When a VM is backed up through VMware VCB or Microsoft Hyper-V for the first time and backup failed due to network error or incorrect credentials then the backup status of the VM node may not be displayed in Virtual Machines view.

If VMware or Hyper-V VMs are backed up in file mode using client agent for Windows, the last backup status of the VM would be shown in Subnet view and this backup status would be omitted from display in Virtual Machines view.

If you performed a backup of a node using the command line (ca_backup), CA ARCserve Backup Infrastructure Visualization may not display any data in the Subnet and Agent views.

To view the node in visualization, add the node to the Backup Manager GUI and provide the credentials.

If you try to access CA ARCserve Backup Infrastructure Visualization in Global mode, from a remote Manager console, the following message appears:
```
"Cannot switch to global mode.  Cannot load Dashboard Agent for Global Dashboard.  Please contact your system administrator."
```
This indicates that you have not installed the Global Dashboard component on to your machine that is running the remote Manager console. To remedy this problem, install the Global Dashboard component on to the remote Manager console machine and then launch CA ARCserve Backup Infrastructure Visualization in Global mode.

Additionally, when you click OK in the above message, Infrastructure Visualization would open in Local mode where you can observe the Visualization views for the Central primary server alone.

9.0 Included Fixes

The following table list the fixes included in the current release of CA ARCserve Backup. If you do not see a specific fix listed in this section, please contact CA Support for more information.

RO18539	T16C896	T245655	T31A554	T36A656	T5E5086	T5K7090	T5KM064	T5OV055
RO18795	T16C897	T245659	T31A556	T36A668	T5E5087	T5K7091	T5KM066	T5OV058
RO18833	T16C902	T245667	T31A557	T46B305	T5E5088	T5K7092	T5KZ041	T5PY016
RO19357	T16C905	T2D2769	T31A558	T46B307	T5E5089	T5K7095	T5KZ042	T5PY018
RO19358	T16C908	T2D2771	T31A559	T46B308	T5E5090	T5K7098	T5KZ043	T5PY019
RO19359	T16C910	T2D2773	T36A624	T46B309	T5E5093	T5KC029	T5KZ045	T5PY020
RO19360	T16C911	T2D2775	T36A625	T46B311	T5E5094	T5KC030	T5KZ047	T5PY021
RO20007	T16C915	T2D2777	T36A626	T46B312	T5E5096	T5KC031	T5KZ048	T5PY022
RO21889	T16C918	T2D2780	T36A627	T46B314	T5E5104	T5KC033	T5KZ050	T5PY023
RO24357	T16C923	T2D2781	T36A628	T46B315	T5E5105	T5KC034	T5KZ051	T5PY026
RO24705	T16C924	T2D2782	T36A629	T46B316	T5HP050	T5KC035	T5KZ054	T5PY027
T146531	T245627	T2D2783	T36A630	T46B317	T5HP051	T5KC036	T5KZ055	T5PY028
T146532	T245628	T2D2784	T36A631	T46B322	T5HP052	T5KC038	T5LD048	T5PY031
T146536	T245629	T2D2785	T36A632	T46B323	T5JS059	T5KC044	T5LD050	T5PY032
T146537	T245632	T2D2786	T36A633	T46B324	T5JS060	T5KF064	T5LD051	T5PY033
T16C878	T245633	T2D2787	T36A634	T46B325	T5JS061	T5KF066	T5LD053	T5PY034
T16C879	T245634	T2D2788	T36A635	T46B326	T5JS062	T5KF068	T5LD054	T5PY037
T16C882	T245635	T2D2789	T36A636	T46B332	T5JS063	T5KF072	T5LD055	T5PY038
T16C883	T245636	T2D2790	T36A637	T46B334	T5JS065	T5KF073	T5OV033	T5PY042
T16C884	T245637	T2D2791	T36A638	T46B336	T5JS066	T5KF076	T5OV037	T5PY045
T16C886	T245638	T2D2792	T36A639	T4C4078	T5K7071	T5KF077	T5OV038	T5PY054
T16C887	T245639	T2D2793	T36A640	T512162	T5K7079	T5KF080	T5OV039	T5QO003
T16C888	T245640	T2D2796	T36A642	T5E5071	T5K7080	T5KM052	T5OV040	T5QO004
T16C889	T245641	T2D2800	T36A644	T5E5075	T5K7081	T5KM053	T5OV041	T5QO007
T16C890	T245642	T2D2801	T36A648	T5E5078	T5K7082	T5KM054	T5OV042	T5QO009
T16C891	T245643	T2D2802	T36A649	T5E5080	T5K7083	T5KM055	T5OV043	T5QO022
T16C892	T245644	T2D2806	T36A650	T5E5081	T5K7084	T5KM057	T5OV044	T5R3001
T16C893	T245645	T2D2810	T36A652	T5E5082	T5K7086	T5KM058	T5OV046
T16C894	T245649	T31A551	T36A653	T5E5083	T5K7088	T5KM061	T5OV048
T16C895	T245652	T31A553	T36A655	T5E5084	T5K7089	T5KM062	T5OV054

Note: The following included fixes contain details specified in the Additional Information for Included Fixes topic.

T16C878

T16C882

T16C897

T16C915

T245638

T2D2773

T31A558

T31A559

T36A625

T36A626

T36A628

T36A637

T36A638

T36A639

T46B314

T46B324

T46B326

T46B332

T5JS059

T5JS060

T5KZ042

T5KZ054

T5OV041

T5OV046

T5PY022

T5PY026

9.1 Additional Information for Included Fixes

The following table contains additional information about included fixes.

Fix Number	Registry Key changes
T16C878	Set this registry for the fix on Server KEY:"Hkey_Local_Machine\Software\ComputerAssociates\CAARCServeBackup\base\Tapeengine\CHANGER_CFG" Value Name (DWORD):UseLogonInteractive Value: 1
T16C882	Set this registry for the fix on Server KEY:"Hkey_Local_Machine\Software\ComputerAssociates\CAARCServeBackup\base\Tapeengine\CHANGER_CFG" Value Name (DWORD): FileMarksToSpace Value: 1
T16C897	Set this registry for the fix on Server KEY:"Hkey_Local_Machine\Software\ComputerAssociates\CA ARCServe Backup\Base\tapeengine\CONFIG" Value Name (DWORD): FSDNOBUFFER Value : 2
T16C915	Set this registry for the fix on Server Key: Hkey_Local_Machine\Software\ComputerAssociates\CAARCServe Backup\Base\Tapeengine\Mux Value Name: RestoreFromMuxCopiedTape Value: before applying this fix set the value as 1.After restor is done for those old tapes,reset the value as 0.
T245638	Set this registry for the fix on the Client Agent machine: Key : HKEY_LOCAL_MACHINE\Software\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters Value Name (DWORD) : LogSkipPF Value : 1
T2D2773	Set this registry for the fix on Server side Key: CA ARCserve Backup\Base\Task\Backup VALUE Name (DWORD) : AppendMediaFormatWithinDay or AppendMediaFormatWithinHour Value : number of days or number of hours (in decimal)
T31A558	Add below registry Key on Server Key : HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\Task\Common\ShowFailedNAS
T31A559	Set this registry for the fix on Exchange Agent machine Key: HKEY_LOCALMACHINE_SOFTWARE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\ExchangeDBAgent\Parameters Value Name (String): ServerName
T36A625	Set this registry for the fix on Server Side Key : "HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\ASMgr\Report" Value Name (DWORD) : "SkipReportEmptyFolder" Value: 1
T36A626	Set this registry for the fix on the machine with Oracle Agent Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\OraPAAdp\Common Value Name: RecoveryCatalogDBName Value: Recovery Catalog Database name
T36A628	Remove below registry values for the fix on the machines with SQL Agent Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\SQLPAAdp\Instances\dbasql@<<SQL instance>> Value Name: VirtualNTServerPassword VirtualNTServerUser VirtualSQLServerName Value: Remove these registry values of each instance
T36A637	Set this registry for the fix on Server KEY:”HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\Admin\DatabaseEngine” Value Name (DWORD): UpdateInterval Value: timeout value in milliseconds (decimal). Example: 5000 (5 seconds)
T36A638	Set this registry for the fix on the machine with Oracle Agent Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\OraPAAdp\Common Value Name: CreateOrgPath? Value: 1 or 0 or delete this value
T36A639	Set this registry for the fix on Server Key: HKEY_LOCAL_MACHINE\SOFTWARE\ ComputerAssociates\CA ARCServe Backup\Base\Database Value Name: "JobLogPruningDays" Value: number of days (in decimal) Value Name: "ActiveLogPruningDays" Value: number of days (in decimal)
T46B314	Set this registry for the fix on Server Key : HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\Task\Backup Value Name (DWORD) : 2ND_MAKEUP_READY Value : 1
T46B324	Set this registry for the fix on Server Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\ CA ARCServe Backup\ Base\Asmgr\Common Value Name (DWORD) : DefaultRestoreOriginal Value : 0
T46B326	Set this registry for the fix on Server Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\ CA ARCServe Backup\Base\Task\Backup Value Name (DWORD): AllowFirstDayAppend Value: 1
T46B332	Set this registry for the fix on Server Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Common Value Name (DWORD) : 'PurgeRetry' Value: 1
T5JS059	Set this registry for the fix on the Client Agent machine: Key : HKEY_LOCAL_MACHINE \ SOFTWARE \ ComputerAssociates \ CA ARCserve Backup \ UniversalClientAgent \ Parameters Value Name (DWORD): AW0050_On_Compare Value: 1
T5JS060	Set this registry for the fix on Server Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCServe Backup\Base\Task\Restore Value Name: SkipSetShortName Value: 1
T5KZ042	Set this registry for the fix on the machine with Oracle Agent Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\OraPAAdp\ Value Name: LogPurge Value: 1
T5KZ054	Set this registry for the fix on Vmware Proxy Server Key : HKEY_LOCAL_MACHINE \ SOFTWARE \ ComputerAssociates \ CA ARCserve Backup \ ClientAgent \ Parameters Value name (DWORD): DisableFallBack Value: 1
T5OV041	Set this registry for the fix on Vmware Proxy Server Key : HKEY_LOCAL_MACHINE \Software\ComputerAssociates\CA ARCServe Backup\ClientAgent\Parameters Value Name (DWORD): DisableRetainVMInDB Value: 1
T5OV046	Set this registry for the fix: Key : HKEY_LOCAL_MACHINE\Software\ComputerAssociates\CA ARCServe Backup\ClientAgent\Parameters Value Name (DWORD) : DisableRetainVMInDB Value : 1
T5PY022	Set this registry for the fix on Server KEY:"HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\TapeEngine\CONFIG" Value Name (DWORD): WaitTimeForOpenDeviceInGroup Value: the value is in second, and the value must longer than 3600 (1 Hour), and shorter than 432000(5 days)
T5PY026	Set this registry for the fix on Server KEY:"HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\Database" Value Name (DWORD): EnableFormatAlert Value : 1

10.0 Language Certifications

An internationalized product is an English product that runs correctly on local language versions of the required operating system and required third-party products and supports local language data for input and output. Internationalized products also support the ability to specify local language conventions for date, time, currency, and number formats.

A translated product (sometimes referred to as a localized product) is an internationalized product that includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.

For CA ARCserve Backup for Windows, this release has been internationalized and translated into the following languages, in addition to the English release:

Brazilian-Portuguese

French

German

Italian

Japanese

Simplified Chinese

Spanish

Traditional Chinese

If you run this product on a language environment not included in the list, you may experience problems.

11.0 Contact CA

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At CA ARCserve Backup Support, you can access the following:

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

Provide Feedback

If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.

If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs.