CA ARCserve® Backup r12.5 Readme

5.0 General Considerations

6.0 Supported Upgrade Paths
6.1 Backward Compatibility

8.0 Included Fixes
8.1 Fixes Included in CA ARCserve Backup r12.5
8.2 Fixes Included in CA ARCserve Backup r12 SP1
8.3 Fixes Included in CA ARCserve Backup r12

9.0 Language Certifications

10.0 Contact CA

1.0 Welcome

Welcome to the CA ARCserve Backup 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 (PDFs) from the CA ARCserve Backup website at https://support.ca.com/prodinfo/arcserve.

CA ARCserve Backup supports the following suites:

CA ARCserve Backup r12.5 File Server Suite (Base)

CA ARCserve Backup r12.5 File Server Suite (Client)

CA ARCserve Backup r12.5 File Server Suite for Virtual Machines

CA ARCserve Backup r12.5 Email Suite

CA ARCserve Backup r12.5 Database Suite

CA ARCserve Backup r12.5 Application Suite

2.0 Operating System Support

CA ARCserve Backup is supported on the following operating systems:

Windows Server 2008 SP1, SP2

Enterprise (x86, x64)

Standard (x86, x64)

Datacenter (x86, x64)

Web Server (x86, x64)

Itanium Based systems

Core (x86, x64) (CA ARCserve Backup Member Server, CA ARCserve Backup 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: Support is for NEC cluster only; MSCS cluster is not supported.

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, CA ARCserve Backup Agent for Microsoft SQL)

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, CA ARCserve Backup Agent for Microsoft SQL)

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)

Windows 2000

Advanced Server (x86) Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1

Server (x86) Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1

Datacenter (x86) Service Pack 4 Rollup 1

Professional (x86) Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1

Windows Powered NAS Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1

Windows Small Business Server (SBS) Service Pack 1a

Failover Cluster Server (x86) Advanced

Windows XP

Professional (x86) (CA ARCserve Backup Server, CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files, Disk to Disk to Tape Option, Tape Library Option, Bootable CD DR, Bootable Tape DR) at minimum Service Pack 1a, or Service Pack 2, or Service Pack 3

Professional (x64) (CA ARCserve Backup Server, CA ARCserve Backup Manager Console, CA ARCserve Backup Client Agent for Windows, CA ARCserve Backup Agent for Open Files, Disk to Disk to Tape Option, Tape Library Option, Bootable CD DR) at minimum Service Pack 1a or Service Pack 2

Windows Vista (x86 and x64) SP1, or SP2

CA ARCserve Backup Manager Console, CA ARCserve Backup Agent for Windows, CA ARCserve Backup Agent for Open Files

Support for Virtualization Software

Virtualization Platform Guest OS Support	Win 2008 x86	Win 2008 x64	Win 2003 x86	Win 2003 x64	Win 2000 Server x86	Win 2000 AS x86	Win XP x86	Win XP x64	Win Vista x86	Win Vista x64
VMware ESX Server (x86 and x64) version 3.0, 3.0.1, 3.0.2	No	No	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes
VMware ESX Server 3.0.3, 3.5, 3.5 Update 2, 3.5 Update 3, 3.5 Update 4	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
VMware ESX Server version 2.5, 2.5.4	No	No	Yes	Yes	Yes	Yes	Yes	No	No	No
VMware ESXi (x86 and x64) version 3.5, 3.5 Update 2, 3.5 Update 3, 3.5 Update 4	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
VMware GSX Server version 3.0, 3.1	No	No	Yes	No	Yes	Yes	Yes	No	Yes	No
VMware Server version 1.0.4, 1.0.1, 2.0	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
VMware Workstation version 4.0, 4.5, 5.0	No	No	Yes	No	Yes	Yes	Yes	No	Yes	No
VMware Workstation version 5.5, 6.0	No	No	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Microsoft Virtual PC 2007 (x86 only)	Yes	No	Yes	No	Yes	Yes	Yes	No	Yes	No
Microsoft Virtual Server 2005 R2 Service Pack 1 (x86, x64)	Yes	No	Yes	No	Yes	Yes	Yes	No	Yes	No

Note: CA ARCserve Backup Dashboard is not supported on Windows 2000 and all Windows operating systems running on Itanium based platforms because the required Microsoft .NET Framework v3.5 SP1 is not supported by these systems.

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.
  Note: Systems running Windows 2000 cannot install .NET 3.5 SP1. Refer to the Microsoft website for more information on .NET Framework requirements.

Microsoft .NET Framework

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

Microsoft .NET Framework 2.0 on Windows 2000 Server systems

Microsoft .NET Framework 3.5 SP1 on Windows XP, 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:

Microsoft SQL Server 2008 Express Edition

Microsoft SQL Server 2008 Enterprise Edition

Microsoft SQL Server 2005 Express Edition with Service Pack 3
Note: Microsoft SQL Server 2005 Express Edition Service Pack 2 is included on the CA ARCserve Backup installation media.

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 SP2, at minimum

3.2 System Requirements for CA ARCserve Backup and CA XOsoft Integration

3.2.1 Hardware Requirements

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

3.2.2 Additional Software Requirements

To integrate CA ARCserve Backup with CA XOsoft, you must be running CA XOsoft, version 4.0, r12, r12 SP1 or r12.5.

The Master servers are supported on the following operating systems:

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 XOsoft r12.5, r12 SP1)

The Replica servers are supported on the following operating systems:

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

Microsoft Windows Server 2008 (CA XOsoft r12.5, r12 SP1)

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

Microsoft Exchange 2000 Standard SP4

Microsoft Exchange 2003 Standard SP1 and SP2

Microsoft Exchange 2007 SP1

Microsoft SQL 7.0 Standard Edition and Enterprise Edition SP4

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

Microsoft SQL 2005

Microsoft SQL 2005 SP1

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

3.3 System Requirements for the CA ARCserve Backup Client Agents

The following sections provide hardware and software requirements for CA ARCserve Backup Client Agents.

Note: Refer to the appropriate Agent section for additional requirements, if any.

3.3.1 Hardware Requirements

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: 10 MB on the client agent installation file system, 25 MB (temporary) on /var/tmp file system

Linux-based platforms:
- RAM: 128 MB
- Disk Space: 10 MB

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

3.3.2 Software Requirements

You can install the CA ARCserve Backup Client Agents on the following platforms:

CA ARCserve Backup Client Agent for Windows:
- 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 Server, 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 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 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)

CA ARCserve Backup Client Agent for NetWare:
- NetWare 5.1, 6.0 and 6.5

CA ARCserve Backup Client Agent for UNIX:
- Solaris 8, 9, and 10 SPARC
- Solaris 9 and 10 (x86 32-bit)
- Solaris 10 AMD64
- IBM AIX 5L v5.2, v5.3, and v6.1
- HP-UX 11.11, and 11.23 PA RISC
- HP-UX 11.22 and 11.23 Itanium (IA64)
- Tru64 v4.0E, v4.0F, v4.0G, v5.0, v5.1, v5.1a, and v5.1b
- FreeBSD version 4.11, 5.3, 5.4, 6.x, and 7.x

CA ARCserve Backup Client Agent for Linux:
- Red Hat 8 and 9
- Red Hat Advanced Server 2.1
- Red Hat Enterprise Linux 2.1 (AS, ES, WS)
- Red Hat Enterprise Linux 3 (AS, ES, WS) (x86, AMD64, and Intel EM64T)
- Red Hat Enterprise Linux 3 Update 4 (AS, ES, WS) (IA64)
- Red Hat Enterprise Linux 4 (AS, ES, WS) (x86, AMD64, Intel EM64T, and IA64)
- Red Hat Enterprise Linux 5 (ES) (Intel EM64T)
- SuSE Linux Enterprise Server 7 (x86, AMD64, Intel EM64T, and IA64)
- SuSE Linux Enterprise Server 8 (x86, AMD64, Intel EM64T)
- SuSE Linux Enterprise Server 9 (x86, AMD64, Intel EM64T, and IA64)
- SuSE Linux Enterprise Server 10 (x86, AMD64, Intel EM64T, and IA64)
- SuSE Linux Enterprise Server 10 SP2 (AMD64, Intel EM64T)
- SuSE Standard Server 8 (x86)
- SuSE Professional 8, 9, 9.1, 9.2. and 9.3 (x86)
- SuSE Linux Desktop 10 (x86, AMD64, and Intel EM64T)
- Novell Linux Desktop 9
- Turbolinux Enterprise Server 8
- Turbolinux Workstation 8
- Turbolinux 8 for AMD64
- Turbolinux 10 Server
- Turbolinux 10F
- Turbolinux 10 Desktop
- Miracle Linux 2.1
- Miracle Linux 3.0 (x86, AMD64, and Intel EM64T)
- Red Flag Desktop 3.0 and 3.2
- Red Flag Advanced Server 4.0 and 4.1
- Red Flag Data Center Server 4.0
- Red Flag Data Center Server 4.1 (x86, AMD64, Intel EM64T, and IA64)
- Asianux 1.0
- SCO Linux Server 4.0
- Debian 3.0, 3.11, 4.0 (x86)
- Novell Open Enterprise Server for Linux 2 SP1 (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.

CA ARCserve Backup Client Agent for Oracle (Linux)
- Red Hat Enterprise Linux 2.1, 3.0, 4.0, 4.5, and 5.0
- Red Hat Advanced Server 2.1, 3.0
- SuSE Enterprise Server 7, 8, 9, and 10
- Red Flag Linux 3.0 and 3.2
- Red Flag Linux Data Center Server 4.0, 4.1

CA ARCserve Backup Client Agent for Linux on OS/390
- Red Hat Enterprise Server 3.0 and 4.0 (32-bit and 64-bit) including SMP
- SuSE Enterprise Server 8 and 9 (32-bit and 64-bit) including SMP

CA ARCserve Backup Client Agent for Mac OS X:
- Apple PowerMac G4/G5--Mac OS X 10.2, 10.3, and 10.4
- Apple X Server--Mac OS X 10.2, 10.3, and 10.4 (PowerPC only)
- Apple OS X 10.5 (both Intel and PowerPC)

CA ARCserve Backup Client Agent for OpenVMS:
- VAX 6.2, 7.1, 7.2, 7.3
- AXP 6.2, 7.1, 7.2, 7.3

CA ARCserve Backup Enterprise Option for AS400:
- AS400 V5 R2 (5.2), V5 R3 (5.3), and V5 R4 (5.4)

3.4 System Requirements for the Agent for IBM Informix

3.4.1 Hardware Requirements

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

3.4.2 Additional Software Requirements

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

Informix Dynamic Server 9.40, 10.0, or 11.1

IBM Informix-Connect is installed and working properly

3.5 System Requirements for the Agent for Lotus Domino

3.5.1 Hardware Requirements

CPU: 512 MHz

RAM: 512 MB

Disk Space: 1.5 GB

The CA ARCserve Backup Agent for Lotus Domino supports the following:

Windows 2000 Server or Adv. Server SP4 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.02, 7.03, 8, 8.0.1, 8.0.2, 8.5 (without db2 enabled)
Note: The Agent for Lotus/Domino supports only 32-bit Windows systems and does not support Domino Attachment and Object Services (DAOS).

3.6 System Requirements for the Agent for Microsoft Exchange

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

3.6.1 Hardware Requirements

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

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

CPU: 133 MHz (Exchange 2003), 800 MHz (Exchange 2007)

RAM: At least 512 MB if using Microsoft Exchange 2000, 2003 and at least 2 GB if using Microsoft Exchange 2007

Disk Space: At least 50 MB, with at least 30 MB on hard disk where Exchange 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 Customer Support at ca.com.

3.6.2 Additional Software Requirements for the Agent for Microsoft Exchange

For Microsoft Exchange Server 2000, you need the following applications:
- Microsoft Windows 2000 Server Standard Edition Service Pack 3 or Service Pack 4
- Microsoft Windows 2000 Server Enterprise Edition Service Pack 3 or Service Pack 4
- Microsoft Windows 2000 Server Datacenter Edition Service Pack 3 or Service Pack 4

For Microsoft Exchange Server 2003, you need the following applications:
- Microsoft Windows 2000 Server Standard Edition Service Pack 3 or Service Pack 4
- Microsoft Windows 2000 Server Enterprise Edition Service Pack 3 or Service Pack 4
- Microsoft Windows 2000 Server Datacenter Edition Service Pack 3 or Service Pack 4
- Microsoft Windows 2003 Server Standard Edition for x86, Windows 2003 Service Pack 1, or Service Pack 2
- Microsoft Windows 2003 Server Enterprise Edition for x86, Windows 2003 Service Pack 1, or Service Pack 2
- Microsoft Windows 2003 Server Datacenter Edition for x86, Windows 2003 Service Pack 1, or Service Pack 2
- Microsoft Exchange Standard Server 2003, Exchange Server 2003 Service Pack 1, or Service Pack 2
- Microsoft Exchange Enterprise Server 2003, Exchange Server 2003 Service Pack 1, or Service Pack 2

For Microsoft Exchange Server 2007 or Exchange Server 2007 SP1, you need the following applications:
- Microsoft Windows 2003 Server Standard Edition for x64, 2003 for x64 Service Pack 1 or 2003 for x64 Service Pack 2
- Microsoft Windows 2003 Server Enterprise Edition for x64, 2003 for x64 Service Pack 1, or 2003 for x64 Service Pack 2
- Microsoft Windows Server 2008 for x64 (only Microsoft Exchange Server Version 2007 Service Pack 1 is supported) Windows 2008 Service Pack 1, Service Pack 2
- Microsoft Messaging API and Collaboration Data Objects 1.2.1 (required for the Document Level Agent)

3.7 System Requirements for the Agent for Microsoft SharePoint 2003

3.7.1 Hardware Requirements

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

The basic Microsoft Office SharePoint 2003 hardware requirements (for information about these requirements, see the Microsoft website)

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 2003 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 technical support.

3.7.2 Additional Software Requirements

CA ARCserve Backup Manager must be installed before you install the Agent for Microsoft SharePoint Configuration Wizard. The Configuration Wizard is supported on all operating systems on which CA ARCserve Backup is supported.

The Agent for Microsoft SharePoint requires at least one of the following:
- Microsoft SharePoint Portal Server 2003, SP1, SP2, or SP3
- Microsoft Office SharePoint Services 3.0 SP1, 2.0 SP1, SP2, or SP3

3.8 System Requirements for the Agent for Microsoft SharePoint 2007

3.8.1 Hardware Requirements

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

The basic Microsoft Office SharePoint 2007 hardware requirements (for information about these requirements, see the Microsoft website)

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 2007 is installed and at least 20 MB on the system drive.

3.8.2 Additional Software Requirements

The CA ARCserve Backup Agent for Microsoft Office SharePoint supports the following:

Windows 2003 Standard SP1, SP2, R2, R2 SP2

Windows 2003 Enterprise SP1, SP2, R2, R2 SP2

Windows 2003 Web Server (x86 only) SP1, SP2

Windows 2008 Enterprise, SP2

Microsoft SQL Server 2005 SP2, SP3

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

CA ARCserve Backup Manager must be installed before you install the Agent for Microsoft SharePoint Configuration Wizard. The Configuration Wizard is supported on all operating systems on which CA ARCserve Backup is supported.

The Agent for Microsoft SharePoint requires at least one of the following:
- Microsoft SharePoint Portal Server 2003, SP1, SP2, or SP3
- Microsoft Office SharePoint Server 2007, SP1 (see Notes, below)
- Microsoft Office SharePoint Services 3.0 SP1, 2.0 SP1, SP2, or SP3

Notes:

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

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

3.9 System Requirements for the Agent for Microsoft SQL Server

3.9.1 Hardware Requirements

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

3.9.2 Additional Software Requirements

The CA ARCserve Backup Agent for Microsoft SQL Server requires one of the following versions of Microsoft SQL Server:

Microsoft SQL Server 7.0 with Service Pack 2, Service Pack 3, or Service Pack 4

Microsoft SQL Server 2000 with Service Pack 4

Microsoft SQL Server 2005 with Service Pack 1, Service Pack 2, or Service Pack 3

Microsoft SQL Server 2008 with Service Pack 1

Microsoft SQL Server Desktop Engine (MSDE) 2000 with Service Pack 3, Service Pack 3a, or Service Pack 4

Microsoft SQL Server 2005 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 2005 Service Pack 1, Service Pack 2, or Service Pack 3 on the following operating systems:

Windows 2003 SP2 or Windows 2003 R2

Windows Server 2008 SP1, SP2

Microsoft SQL Server 7.0 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 7.0 Service Pack 2, Service Pack 3, or Service Pack 4, on the following operating system:

Microsoft Windows 2000 Service Pack 4

Microsoft SQL Server 2000 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 2000, Service Pack 3, Service Pack 3a, and Service Pack 4 on the following operating systems:

Windows 2000 Service Pack 4

Windows 2003 SP2 or Windows 2003 R2

Microsoft SQL Server 2008 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 2008 on the following operating systems:

Windows 2003 SP2 or Windows 2003 R2

Windows Server 2008 SP1, SP2

Support for 64-bit Systems

The Agent for Microsoft SQL Server supports Microsoft SQL on the following 64-bit editions of Windows:

Microsoft SQL 2000 64-bit Edition for IA64 on Windows 2003 for Itanium-based systems

Microsoft SQL 2000 for x86 (32-bit) on Windows 2003 SP 2 or Windows 2003 R2 for x64-based systems

Microsoft SQL 2005 for IA64 and x64-based systems on Windows 2003 SP2 or Windows 2003 R2

Microsoft SQL 2005 SP2 64-bit Edition on Windows Server 2008 for x64-based systems

Microsoft SQL 2005 SP2 IA64 Edition on Windows Server 2008 for IA64-based systems

Microsoft SQL 2008 x64 Edition on Windows 2003 SP2 or R2 x64-based systems

Microsoft SQL 2008 x64 Edition on Windows Server 2008 for x64-based systems

Microsoft SQL 2008 IA64 Edition on Windows 2003 SP2 or Windows 2003 R2 Itanium-based systems

Microsoft SQL Server Desktop Engine (MSDE) 2000 Support

The Agent for Microsoft SQL Server supports MSDE 2000, Service Pack 3, Service Pack 3a, and Service Pack 4 on the following operating systems:

Windows 2000 Service Pack 4

Windows Server 2003

3.10 System Requirements for the Agent for Oracle (UNIX/Linux)

The following section provides the system requirements for the CA ARCserve Backup Agent for Oracle (UNIX/Linux):

3.10.1 Hardware Requirements

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

Disk Space: 15 MB

3.10.2 Additional Hardware Requirements

For Linux x86 platforms
- Disk Space: 25 MB

For Linux AMD64 platforms
- Disk Space: 25 MB

For Linux Itanium platforms
- Disk Space: 25 MB

Note: Oracle 11g is supported on Sun Solaris SPARC, HP-UX Itanium, HP-UX and AIX platforms. Please ensure that the Oracle patch 6800649 is installed for AIX5L Based Systems (64-bit).

3.11 System Requirements for the Agent for Oracle (Windows)

The following section provides the system requirements for the CA ARCserve Backup Agent for Oracle:

3.11.1 Hardware Requirements

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 256 MB (512 recommended by Oracle) if using Oracle 9i/10gR1/R2, and at least 1 GB if using Oracle 11g

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

3.11.2 Additional Software Requirements for the Agent for Oracle

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

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

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

For Microsoft Windows 2003 Service Pack 2:
- Oracle Server version 9i, 10g R1 or R2, or 11g
- Oracle Fail Safe (OFS) version 3.3.4 on 10g, 3.4.1 on 11g
- Oracle RAC 10g, 11g

For Microsoft Windows Server 2008:
- Oracle Server version 10g R2
- Oracle Fail Safe (OFS) version 3.3.4 on 10g
- Oracle RAC 10g
  Note: Oracle 11g is not supported on Windows Server 2008 systems.

For Microsoft Windows Server 2008 SP2:
- Oracle Server version 10g R2
- Oracle Fail Safe (OFS) version 3.3.4 on 10g
- Oracle RAC 10g
  Note: Oracle 11g is not supported on Windows Server 2008 SP2 systems

For 64-bit Systems:
- Oracle 9i IA64 on Windows 2003 SP2 or Windows 2003 R2 for Itanium-based systems
- Oracle 10g x86 (32-bit) on Windows 2003 SP2 or Windows 2003 R2 for x64-based systems
- Oracle 10g x64 on Windows 2003 SP2 or Windows 2003 R2 for x64-based systems
- Oracle 10g IA64 on Windows 2003 SP2 or Windows 2003 R2 for IA64-based systems
- Oracle 10g x64 on Windows 2008 SP2 systems
- Oracle 11g x86 (32-bit) on Windows 2003 Sp2, Windows 2003 R2 for x64-based systems
- Oracle 11g x64 on Windows 2003 SP2 or Windows 2003 R2 for x64-based systems

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.12 System Requirements for the Agent for Open Files

3.12.1 Hardware Requirements

In addition to the Minimum Requirements previously listed, you should have at least 1.5 MB of disk space available for this agent.

3.12.2 Additional Software Requirements

The Agent for Open Files requires one of the following operating systems:

Windows 2000 x86, SP4, SP4 Rollup 1

Windows Vista (x86, x64) SP1, SP2

Windows XP Professional (x86) SP2, SP3 (x64) SP1a, 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

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.

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).

The Agent is not supported on Windows XP systems.

3.13 System Requirements for the Agent for Virtual Machines

3.13.1 Hardware Requirements

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

Note: When 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. When the Agent is installed on a remote node, the Agent requires the same hardware specified for the Client Agent for Windows.

3.13.2 Additional Software Requirements

The CA ARCserve Backup Agent for Virtual Machines supports the following platforms:

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

VMware:

ESX Server Version	VCB Framework Version	Virtual Center 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	2.0.2
3.0.3	1.1, 1.1 Update 1, 1.5, 1.5 Update 1	2.5
ESX 3.5, Update 1, Update 2, Update 3, Update 4 ESXi 3.5, Update 1, Update 2, Update 3, Update 4	1.1, 1.1 Update 1, 1.5, 1.5 Update 1	2.5 Update 1, Update 2, Update 3 and Update 4

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 OS supported by Microsoft Hyper-V.

3.14 System Requirements for the Agent for Sybase

3.14.1 Hardware Requirements

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

3.14.2 Additional Software Requirements

The CA ARCserve Backup Agent for Sybase requires Sybase Adaptive Server 12.0, 12.5, or 15.0.

The Agent for Sybase supports Windows as the host server platform.

3.15 System Requirements for the Central Management Option

3.15.1 Hardware Requirements

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

3.16 System Requirements for the Disaster Recovery Option

3.16.1 Hardware Requirements

In addition to the Minimum Requirements previously listed, you should have at least 70 MB of disk space available for the Disaster Recovery Option.

3.16.2 Additional Software Requirements

The CA ARCserve Backup Disaster Recovery Option supports several methods of disaster recovery, depending on operating system.

The following versions of Windows are supported for 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.

The following versions of Windows are supported for bootable tape disaster recovery: (Only 32-bit supported)
- 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 SP2, SP3
- 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.

The following versions of Windows are supported for bootable media image recovery:
- Windows XP Professional Edition SP2, SP3
- 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: The version of Windows you use to generate the boot media should be the version of Windows installed on your machine.

The following versions of Windows are supported for 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, SP3
- Windows 2003 Web Edition SP1, SP2, R2, R2 SP2
- Windows 2003 Enterprise 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)
  The 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.
  
  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.

3.17 System Requirements for the Enterprise Module

3.17.1 Hardware Requirements

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

The Enterprise Module is a prerequisite component for the following options and features:

Enterprise Option for IBM 3494

Enterprise Option for StorageTek ACSLS

Serverless Backup Option

Encryption at the server

Disk to Disk to Tape backups (with greater than two streams)

Disk to Tape to Tape backups

Note: The Enterprise Option for StorageTekACSLS and IBM 3494 are not supported on 64-bit platforms. The Image Option and Serverless Backup Option are not supported on Windows 2008 systems. In addition to the above options, the Enterprise Module must be installed to access CA ARCserve Backup advanced features and enhanced functionality. For more information, see the Administration Guide.

The CA ARCserve Backup Enterprise Module includes the following CA ARCserve Backup options:

Image Option

Serverless Backup Option

Encryption at the server

Media Management Option (MMO)

Enterprise Option for IBM 3494

Enterprise Option for StorageTek ACSLS

Enterprise Option for VSS Hardware Snap-Shot

User Profiles

Password Management
Note: For more information about the Enterprise Option for VSS Hardware Snap-Shot, see the Agent for Microsoft Volume Shadow Copy Service Guide. For more information about the Role Management and Password Management, see the online help.

3.17.2 Software Requirements

The minimum operating system requirements for the Enterprise Module are:

Windows 2000 SP3, SP4, SP4 with Rollup 1

Windows 2000 SBS SP1a

Windows Server 2003 SP1, SP2, R2, R2 SP2

Windows Server 2008 SP1, SP2

The StorageTek ACSLS Library Attach (LibAttach) software version 1.2 is required for the StorageTek ACSLS Enterprise Option.

The IBM Library Manager Control service version 5.4.8 is required for the IBM 3494 Enterprise Option.

3.18 System Requirements for CA ARCserve Backup Dashboard

3.18.1 Hardware Requirements

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

3.18.2 Additional Software Requirements

No additional software is required beyond the requirements previously listed.

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. If an email message contains images or charts, they are attached to the email, and appear in the report display in sequential order. For Windows Mail running on Windows Vista systems, formatting is retained because the default setting is HTML format. If an email message contains images or charts, the images are attached to the email, and appear in the report display in sequential order. We recommend specifying up to 4 reports in the Dashboard email schedule if you are using Outlook Express or Windows Mail as the mail client.

For local mail (mail sent by clicking the email icon from a Dashboard report), data is correctly shown in Windows Mail and Outlook Express (in HTML format) if the report contains tabular information only. If images or charts exist, they appear at the bottom of the email.

Note: CA ARCserve Backup Dashboard is not supported on Windows 2000 and all Windows operating systems running on Itanium-based platforms because the required Microsoft .NET Framework v3.5 SP1 is not supported by these systems. CA ARCserve Backup Dashboard is not supported on IA64 systems running Windows 2008 because WPF is not supported on IA64 machines.

3.19 System Requirements for the Disk to Disk to Tape Option

The Disk to Disk to Tape Option is now supported by the Enterprise Module. If you are upgrading from a previous version of CA ARCserve Backup and have a valid Disk to Disk to Tape license, contact CA Support to obtain a new Enterprise Module license.

3.20 System Requirements for the Enterprise Option for IBM 3494

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

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

3.21.1 Hardware Requirements

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

3.21.2 Additional Software Requirements

The CA ARCserve Backup Enterprise Option for SAP R/3 for Oracle supports the following:

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).

3.22 System Requirements for the Enterprise Option for StorageTek ACSLS

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

3.23 System Requirements for the Image Option

The Image Option is now supported by the Enterprise Module.

3.24 System Requirements for the NDMP NAS Option

3.24.1 Hardware Requirements

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

3.24.2 Additional Software Requirements

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

Operating Systems:
- Windows 2000 SP4, SP4 Rollup 1
- Windows 2000 SBS SP1a
- Windows Server 2003 SP1, SP2, R2, R2 SP2 (x86 and x64)
- Windows Server 2008 SP1, SP2 (x86 and x64)

In addition, you must meet the following requirements, 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

3.25 System Requirements for the Tape Library Option

3.25.1 Hardware Requirements

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

3.25.2 Additional Software Requirements

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

The minimum operating system requirements for the Tape Library Option are:

Windows 2000 SP4, SP4 Rollup 1

Windows 2000 SBS SP1a

Windows Server 2003 SP1, SP2, R2, R2 SP2

Windows Server 2008 SP1, SP2

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

Optical Library Support

Tape RAID Support

3.26 System Requirements for the Serverless Backup Option

Serverless Backup is now supported by the Enterprise Module.

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

3.27.1 Hardware Requirements

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

3.27.2 Additional Software Requirements

The CA ARCserve Backup Storage Area Network (SAN) Option may be installed on the following operating systems:

Windows 2000 SP4, SP4 Rollup 1

Windows 2000 SBS SP1a

Windows Server 2003 SP1, SP2, R2, R2 SP2

Windows Server 2008 SP1, SP2

You must 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.28 System Requirements for the CA ARCserve Backup Small Business Server Editions

3.28.1 Hardware 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
- Agent for Microsoft SharePoint

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
- Agent for Microsoft SQL
- Agent for Microsoft SharePoint.

3.28.2 Software Requirements

Windows Server 2003 SP1, SP2

Windows Server 2008 SP2

CA ARCserve Backup

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

3.29.1 Hardware Requirements

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.29.2 Software Requirements

To access CA ARCserve Backup for Microsoft Windows EBS, you must meet the following prerequisites:

Windows Server 2008 SP2

Microsoft Windows EBS

CA ARCserve Backup

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.

During installation, CA ARCserve Backup installs Microsoft .NET Framework v3.5 SP1, except on Windows 2000 systems, which are installed with .NET Framework v2.0 SP2.

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 with a Microsoft SQL Server database, Microsoft SQL 7.0 cannot be used as the CA ARCserve Backup database. The System Data Source "ASNT" under System DSN, in the ODBC Data Source Administrator should have the Client Configuration set to utilize TCP/IP if the version of the driver you are using is configurable.

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.

When upgrading from Microsoft Windows XP SP2 or above to Microsoft Vista, existing installations of CA ARCserve Backup will not work. You must uninstall CA ARCserve Backup.

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.

CA ARCserve Backup installs SQL Express 2005 SP2 as the CA ARCserve Backup database when SQL Express is selected.

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 performing a remote CA ARCserve Backup installation on Windows XP systems, make the following modification to avoid unknown user errors:
1. Open Control Panel, Administrative Tools, Local Security Policy, Local Policies, Security Options.
2. Select Network access: Sharing and security model for local accounts.
3. Change setting to Classic - local users authenticate as themselves.
4. Click OK.

When you uninstall r11.5 or upgrade from r11.5 to r12 or r12 SP1, 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 2005 SP2 as the ARCserve database, except on IA64 machines.

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.

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

When installing Microsoft SQL Server 2008 Express as the CA ARCserve Backup database, do not change the default instance name (ARCSERVE_DB). Changing the default instance name prevents the CA ARCserve Backup database from expanding larger than 4 GB when necessary. To use Microsoft SQL Server 2008 Express Edition as the CA ARCserve Backup database, select Microsoft SQL Server from the Database Settings dialog when you are installing CA ARCserve Backup.

4.2 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, for example, upgrading from r12 SP1 to r12.5, the Installation Wizard lets you install only the CA ARCserve Backup components that were installed in the 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.

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".

If you are upgrading the CA ARCserve Backup Agent for Sybase from BrightStor Enterprise Backup 10.5 or ARCserve 9 to this release, you must re-configure the Sybase instance because configuration information cannot be saved during upgrades.

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:
1. Restart the ARCSERVE_DB service.
2. Run command line: BABHOME\caauthd.exe -setupuser
3. Run command line: BABHOME\cadiscovd.exe -m

4.3 Components that Require Reboot

The following CA ARCserve Backup components may require rebooting at installation:

When installing the CA ARCserve Backup base product on systems on which any version of eTrust prior to 8.0 is installed, you will be required to reboot your system.

When installing the following options included in the Enterprise Module, you must restart your system:
- Image Option
- Serverless Backup Option

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.

4.4 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 Oracle UNIX/Linux (RMAN)

You must upgrade the BrightStor ARCserve Backup for UNIX and Linux Agent for Oracle r11.5 SP1 and r11.5 SP2 to the BrightStor ARCserve Backup Agent for UNIX and Linux Agent for Oracle r11.5 SP3 to apply the latest patch.

The Agent for Oracle on UNIX/Linux platforms requires patches if running Oracle 11g. See ca.com/support for the latest software updates to the BrightStor ARCserve Backup Agent for Oracle on UNIX/Linux platforms.

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.

Agent for Virtual Machines

VMware Systems: Install the agent on the system intended to operate as the backup proxy system. Ensure the VMware VCB Framework 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.

4.5 Installation Considerations for the Agent for Microsoft Exchange

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

Microsoft Messaging API and Collaboration Data Objects 1.2.1 are required for the Document Level Agent for Microsoft Exchange 2007 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.6 Installation Considerations for the Agent for Microsoft SharePoint 2003

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

CA ARCserve Backup must be installed before you install the Agent for Microsoft SharePoint Configuration Wizard. The Configuration Wizard is supported on all operating systems on which CA ARCserve Backup is supported.

When upgrading from previous release to this release of CA ARCserve Backup, use the Agent for Microsoft SharePoint Configuration Wizard to upgrade all CA ARCserve Backup SharePoint agents, including the Router Agent, External Data Agent, and Embedded SQL Agent. Uninstall all previous agents first, then install the Agent for Microsoft SharePoint.

If the Agent for Microsoft SQL Server and the database component of the Agent for Microsoft SharePoint are both deployed on the same machine, the SharePoint databases are included in whole-instance backups performed by the Agent for Microsoft SQL Server. This issue also applies to the Agent for Microsoft SQL Server.

To install and configure the Agent for Microsoft SharePoint in an environment with a firewall provided by Windows Server 2003 Service Pack 1 enabled, you must perform the following procedure:
Note: This procedure refers only to ports for the Agent for Microsoft SharePoint. You may have to open other ports to allow Microsoft SharePoint Portal to work properly. Verify that the Microsoft SharePoint Portal is working correctly before performing the following procedure.
1. Ensure that the firewalls on any remote computers hosting the SharePoint installation are configured to allow exceptions.
2. Install the Agent for Microsoft SharePoint from the CA ARCserve Backup installation media. The Agent for Microsoft SharePoint Configuration wizard starts automatically.
3. Complete the Server Selection information and click Next. Although the SharePoint Router Agent is installed, you may receive the following error message, indicating that the firewall is blocking access to the SharePoint Router Agent:
```
The router was not found on the selected machine. Check that the router is running. 
```
4. Add the UnivAgent.exe executable to the Windows Firewall exception list on the machine on which the SharePoint Router Agent has been installed. This executable is found in the following directory:
```
	c:\Program Files\CA\SharedComponents\ARCserve Backup\UniAgent
```
5. In the wizard, clear the Install router onto machine checkbox and click Next. The wizard obtains the SharePoint topology information, allowing you to proceed with either an Automatic or Custom installation type. Proceed to the Install screen of the wizard and click Next to install the required agents.
6. A list of computers and the agents installed on them appears. Before you can use the Agent for Microsoft SharePoint, these agents must be added to the Windows Firewall exception list on those machines.
7. If you have the CA ARCserve Backup External Data Agent installed on any computers, add the UnivAgent.exe executable to the Windows exception list. This executable is found in the following directory:
```
	c:\Program Files\CA\SharedComponents\ARCserve Backup\UniAgent
```
8. If you have the Agent for Microsoft SQL Server installed on any computers, add the following to the Windows Firewall exception list:
  - Select File and Printer Sharing and choose TCP 139
  - dbasvr.exe, found in the following directory:
```
	c:\Program Files\CA\SharedComponents\ARCserve Backup\DBACommon 
```
    The Agent for Microsoft SharePoint can now be used successfully from the CA ARCserve Backup server.

4.7 Installation Considerations for the Agent for Microsoft SharePoint 2007

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

Microsoft Office SharePoint Server 2007 or Microsoft Windows Shared Service 3.0 must be installed before you install the Agent for Microsoft SharePoint 2007. The agent is supported on all operating systems on which Microsoft Office SharePoint Server 2007 is 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.

You must run the Microsoft SQL Server Windows service as a domain account or a local system account.

When you upgrade the Agent for SharePoint 2007 to this release, two active SharePoint 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.

4.8 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.9 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.

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.

4.10 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.11 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.12 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.13 CA ARCserve Backup Custom Actions

The following list describes the CA ARCserve Backup custom actions in this release:

ASChangeFolder.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Changes the installation folder.

auth_setup
Launches AuthSetup.exe.

BaofDeleteLeftOvers
Lets the installation program delete folders under the Start Menu group.

BaofDisableChangeFolder
Reserved.

BaofGUIMergePostInstallFinalize.34700913_E51E_11D3_89E3_00B0D0152B6B
Lets the installation program delete the old Agent for Open Files shortcut, common resources, and decreases the reference count when installing the Agent for Open Files GUI.

BaofGUIMergePostInstallInitialize.34700913_E51E_11D3_89E3_00B0D0152B6B
Lets the installation program set the installation path and retrieve the reference count when installing the Agent for Open Files GUI.

BaofGUIMergePreInstallFinalize.34700913_E51E_11D3_89E3_00B0D0152B6B
Lets the installation program set the suite information into the registry when installing the Agent for Open Files GUI.

BaofInitUsers
Initializes all users and Application Users.

BaofLaunchReadMe
Reserved.

BaofLaunchSilentBat
Launches silent.bat executable for licensing.

BaofMessageInstall
Lets the installation program write warning and abort messages.

BaofNameLicense
Reserved.

BaofNameReadMe
Resolves the name of the Read Me file from the language and the file format.

BaofNothingToInstall
Reserved.

BaofNovellClientInstalled
Verifies the Novell client is installed.

BaofNTMergePostInstallFinalize.35716D43_DFD2_11D3_89DC_00B0D0152B6B
Lets the installation program delete the old shortcut for the Agent for Open Files, common resource and decreases the reference count when installing the Agent for Open Files server.

BaofNTMergePostInstallInitialize.35716D43_DFD2_11D3_89DC_00B0D0152B6B
Lets the installation program set the installation path and retrieves the reference count information when installing the Agent for Open Files server.

BaofNTMergePostLaunchConditions.35716D43_DFD2_11D3_89DC_00B0D0152B6B
Verifies that the Agent for Open Files server can be installed.

BaofNTMergePreInstallExecute.35716D43_DFD2_11D3_89DC_00B0D0152B6B
Reserved.

BaofNTMergePreInstallFinalize.35716D43_DFD2_11D3_89DC_00B0D0152B6B
Lets the installation program set the suite information into the registry when installing the Agent for Open Files GUI.

BaofNTSetProducts.35716D43_DFD2_11D3_89DC_00B0D0152B6B
Lets the installation program set the registry value for the Agent for Open Files feature.

BaofReadIcfFile
Reads information from ICF file.

BaofReadInfFile
Reads information from ICF file.

BaofReadMeLicenseInstall
Reserved.

BaofRegisterComponent
Invokes the register dialog when performing a FULL product installation of the Server while NOT in silent mode.

BaofRemoveLicense
Reserved.

BaofScheduleReboot
Lets the installation program schedule reboots.

BaofSetARPReadMe
Reserved.

BaofSetSelectedComponents
Selects or clears selected components based on parameters passed by MasterSetup in the ICF file.

BAOFSetSelectedFeatureState
Sets the Feature state as selected or cleared when performing installation using MasterSetup.

BaofTerminateSetup
Reserved.

BaofWarning
Reserved.

Call64BitBDelObj
Used for removing the configuration files for RMAN Agent on 64-bit operating systems.

CallAfterUpgrade
Reserved.

CallAllowInstall
InstallShield custom action that lets the installation program check for conditions relating to the current CA ARCserve Backup installation.

CallAllowUninstall
Lets the uninstallation program check for conditions relating the current CA ARCserve Backup installation.

CallBDelObj
Used for removing the configuration files for RMAN Agent.

CallBeforeUpgrade
Reserved.

CallCloseSetupWindows
Closes setup window.

CallDRAlternateInfo
Changes Disaster Recovery information.

CallInstallAlert
Installs the Alert package.

CallInstallETPK
Reserved.

CallInstallScanEng
Installs CA Scan Engine.

CallInstScanEng
Installs CA Scan Engine.

CallLicenseValidation
Used for license validation.

CallPostConfig
Restores old product settings, files, registry keys and so on.

CallPostInstall
Lets the installation program perform various tasks relating to installation. For example, registering CA ARCserve Backup into the Windows Registry.

CallPostUninstall
Reserved.

CallPreInstall
Lets the installation program read and write MSI properties. For example, reads the CA ARCserve Backup installation path from the MSI.

CallPreUninstall
Lets the uninstallation program perform various tasks relating to uninstallation. For example, un-registers CA ARCserve Backup from the Windows Registry.

CallRegisterComponent
Reserved.

CallSetAfterUpgrade
Reserved.

CallSetARCserveDatabaseType
Uses SetARCserveDatabaseType to get MSI property "SELECTDBTYPE" and then set MSI properties "VLDB" and "SQL".

CallSetASDomainSecurity
Sets CA ARCserve Backup domain security information in registry.

CallSetBeforeUpgrade
Reserved.

CallSetDiscoveryCfg
Updates discovery.cfg with value from MSI properties "DSNAME", "PRIDSNAME" and "SECDSNAME".

CallSetNotesDatabaseType
Sets Notes database type.

CallSystemAccount
Calls CreateSystemAccount to validate the system account.

CallUninstallAlert
Uninstalls Alert package.

CallUninstallETPK
Reserved.

CheckForProductUpdates
InstallShield custom action that uses FLEXnet Connect to check for product updates. This custom action launches an executable file called Agent.exe, and it passes the following: /au[ProductCode] /EndOfInstall.

CheckForProductUpdatesOnReboot
InstallShield custom action that uses FLEXnet Connect to check for product updates on reboot. This custom action launches an executable file called Agent.exe, and it passes the following: /au[ProductCode] /EndOfInstall /Reboot.

CheckTextLength
Uses CheckTextLength to verify the validity of the installation path and domain path lengths. It also determines if the domain name contains invalid characters.

ClearWarningText
Reserved.

CloseSetupWindow
Closes setup window.

CostFinalize
InstallShield custom action. The Calculate Disk Space action determines the total amount of disk space required by the installation in its current configuration. This action also verifies that all target directories are writable. The actions Initialize Disk Space Calculations and Initialize Dynamic Disk Space Calculations must be called before the Calculate Disk Space action; otherwise, the action will fail.

DeleteNASKey
Deletes the NAS product registry keys.

DeleteNTKey
Deletes NT Agent Common Key.

DoNotReboot
Disables the system reboot.

Install32CADS
Uninstalls 32-bit CADS package.

InstallDS.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Installs CADS package.

InstalliGateway
Reserved.

InstalliSponsor
Reserved.

InstallSAK
Uninstalls SAK package.

InstallScanEng
Installs CA Scan Engine.

ISPreventDowngrade
InstallShield custom action - The Custom Actions and Sequences view contains a custom action called ISPreventDowngrade, a type 19 custom action that Windows Installer launches when you install the current version of your product over a later major version.

ISPrint
InstallShield custom action that prints the contents of a ScrollableText control on a dialog.

ISSelfRegisterCosting
InstallShield custom action that extracts operations to a temporary file for self-registration. This is a Windows Installer .dll custom action. The name of the .dll file is isregsvr.dll, and its entry point is ISSelfRegisterCosting.

ISSelfRegisterFiles
InstallShield custom action that registers self-registering files. This is a Windows Installer .dll custom action. The name of the .dll file is isregsvr.dll, and its entry point is ISSelfRegisterFiles.

ISSelfRegisterFinalize
InstallShield custom action that cleans up temporary file from self-registration. This is a Windows Installer .dll custom action. The name of the .dll file is isregsvr.dll, and its entry point is ISSelfRegisterFinalize.

ISSetAllUsers
InstallShield custom action that sets ALLUSERS per upgrade or initial installation requirements.

ISUnSelfRegisterFiles
InstallShield custom action that unregisters self-registering files.

Launch32BSDelObj
Removes the configuration files.

Launch64BSDelObj
Removes the configuration files on 64-bit operating systems.

LaunchAADRConfig
Launches DR configuration tool.

LaunchBDDelObj64
Launches 64-bit BDelObj.exe.

LaunchBdelobj64
Launches 64-bit binary BSDelobj.exe

LaunchBSDelObj
Launches BSDelObj.exe

LaunchBSdelobj32
Launches 32-bit binary BSDelobj.exe

LaunchDBAConfig
LaunchDBAConfig_AB

LaunchDBAConfig_AB_Silent
Launches DBAconfig Tool with silent mode.

LaunchDBAConfig_Silent
Launches DBAconfig Tool with silent mode.

LaunchDBAConfigAB
Launches the DBAConfig.exe to finish the DB Agent configuration.

LaunchDBAConfigABSilent
Launches the DBAConfig.exe to finish the DB Agent configuration in silent mode.

LaunchDBAConfigSILENT
Launches DBAConfig in SILENT mode.

LaunchDBAConfigSILENT_AB
Launches the DBAConfig.exe to finish the DB Agent configuration in silent mode.

LaunchDBAConfigSilent_EB
Launches DBAConfig in SILENT mode.

LaunchDBAConfigSILENT64
Launches DBAConfig.exe in silent mode for 64-bit.

LaunchDBAConfigSILENTX64
Launches DBAconfig in silent mode on x64 platform.

LaunchDBAConfigUI
Launches DBAConfig in USER mode.

LaunchDBAConfigUI_AB
Reserved.

LaunchDBAConfigUI_EB
Launches DBAConfig in USER mode if ARCserve version is BEB.

LaunchDBAConfigUI64
Launches DBAConfig.exe in USER mode for 64-bit.

LaunchDBAConfigUIX64
Launches DBAconfig.exe in UI mode on x64 platform.

LaunchDelAgentAddOn
Reserved.

LaunchDelAgentDir
Removes the agent home directory at the end of uninstallation process.

LaunchDeleteAgentDir
Removes the SQL agent home directory at the end of uninstallation process.

LaunchDeleteOpt
Launches deleteopt.exe to remove VSS at the end of uninstallation process.

LaunchDeleteOptions
Launches DeleteOpt.exe of ENG language.

LaunchDeleteOptionsCHS
Launches DeleteOpt.exe in CHS language.

LaunchDeleteOptionsCHT
Launches DeleteOpt.exe in CHT language.

LaunchDeleteOptionsCSY
Reserved

LaunchDeleteOptionsDAN
Reserved

LaunchDeleteOptionsELL
Reserved

LaunchDeleteOptionsFIN
Reserved

LaunchDeleteOptionsFRN
Launches DeleteOpt.exe in FRN language.

LaunchDeleteOptionsGRM
Launches DeleteOpt.exe in GRM language.

LaunchDeleteOptionsHUN
Reserved.

LaunchDeleteOptionsITA
Launches DeleteOpt.exe in ITA language.

LaunchDeleteOptionsJPN
Launches DeleteOpt.exe in JPN language.

LaunchDeleteOptionsKRN
Reserved.

LaunchDeleteOptionsNLD
Reserved.

LaunchDeleteOptionsNOR
Reserved.

LaunchDeleteOptionsPLK
Reserved.

LaunchDeleteOptionsPRB
Launches DeleteOpt.exe in PRB language.

LaunchDeleteOptionsRUS
Reserved.

LaunchDeleteOptionsSPA
Launches DeleteOpt.exe in SPA language.

LaunchDeleteOptionsSVE
Reserved.

LaunchDeleteOptionsTUR
Reserved.

LaunchDRCreate
Launches DR configuration tool.

LaunchDVConfig
Launches Device configuration tool.

LaunchMoveFilesAMD64
Launches MoveFiles64.exe process to move files for X64 platform.

LaunchMoveFilesIA64
Launches MoveFiles64.exe process to move files for IA64 platform.

LaunchProductSetup
Installs related products.

LaunchRemoveFilesAMD64
Launches RemoveFiles64.exe process to remove files for X64 platform.

LaunchRemoveFilesIA64
Launches RemoveFiles64.exe process to remove files for IA64 platform.

LaunchSetupSQL
Launches SetupSQL.exe to install and configure CA ARCserve Backup SQL Database.

LaunchSetupSQL_Exp
Reserved.

LaunchShutDown
Reserved.

LaunchSilentSQL
Launches setupsql_exp.exe to install and configure CA ARCserve Backup SQL Database in silent mode.

LaunchSilentSQL_Exp
Launches setupsql_exp.exe to install and configure CA ARCserve Backup SQL Database in silent mode.

LaunchToKillService.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Kills discovery service.

LicenseValidation
Validates license.

NoReboot
Suppresses reboot.

ProtectService.09CAF474_3310_11D5_A7C4_00B0D03F6BF4
Adds Access Permission control on Universal Agent Service.

ProtectService.35716D43_DFD2_11D3_89DC_00B0D0152B6B
Adds Access Permission control on CADS Services.

ProtectService.7B79CDF6_3F71_4FC5_94E4_3E350E1DD38C
Adds the service recover option for DBARpc service.

ProtectService.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Adds Access Permission control on CADS Services.

QuitMSI
Reserved.

RebootAction
Reboots system.

RegisterCom
Launches DBBAFAgentWrapper.exe to register com.

RegisterComponent
Registers the product descriptor in registry.

RegisterDiscoveryPorts
Launches RegisterDiscoveryPorts.exe to register Discovery Ports.

RegisterMonadComWrapper
Launches MonadComWrapper.exe to register DLLs.

Remove32CADS
Uninstalls CA ARCserve Backup Discovery Service package.

RemoveCPMO
Removes old version of the Cross-platform Management Option.

RemoveDS.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Removes CADS package.

RemoveOldDBAgent
Uninstalls old SQL agent.

RemoveOptions
Removes Option products.

RemoveScanEng
Removes CA Scan Engine during uninstallation.

RemoveScanEngine
Removes Scan Engine during uninstallation.

RestartDS.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Restarts discovery service.

setAllUsersProfile2K
InstallShield custom action that initializes the ALLUSERSPROFILE directory identifier for Windows 2000 or later.

SetAllUsersProfileNT
InstallShield custom action that initializes the ALLUSERSPROFILE directory identifier for Windows NT 4.

SetARPINSTALLLOCATION
Installshield custom action that sets the value of the ARPINSTALLLOCATION property to the fully qualified path for the application's primary folder.

SetASDomainFilePath
Uses SetASDomainFilePath to get properties "INSTALLDIR" and "DSNAME" from MSI and then generate the ARCserve domain path. Set this path to MSI property, "ASDomainFolder".

SetCommonFolderInstall
Sets the SOURCEDIR and INSTALLDIR during installation.

SetCommonFoldersUninstall
Sets the SOURCEDIR and INSTALLDIR during installation.

SetDBQuoteForSrvPath
Sets double quotes for service image path.

SetPACKAGESELECTED
Sets the package select status.

SetProductNameStr
Reserved.

setUserProfileNT
InstallShield custom action that initializes the USERPROFILE directory identifier.

SetWARNINGMSGtoNONE
Cleans up all MSI warning messages.

ShowMsiLog
Installshield custom action that displays the Windows Installer log file in Notepad if you select the Show the Windows Installer log check box in the SetupCompleteSuccess, SetupCompleteError, or SetupInterrupted dialogs and then click Finish. (This works only with Windows Installer 4.0.)

StartDS.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Starts discovery service.

StopDS.EA2AA82D_E7CF_4024_8E18_6FF4B7D7B26D
Stops discovery service.

SystemFolder.35210702_493B_42CA_BA13_865C5A8BDAC1
Sets the property, SystemFolder for Merge module.

TerminateSetup
Terminates setup when error is detected.

TerminateSetup1
Terminates setup when error is detected.

TerminateSetup2
Terminates setup when error is detected.

TerminateSetup3
Terminates setup when error is detected.

TerminateSetup4
Terminates setup when error is detected.

Uninstall32CADS
Uninstalls 32-bit CADS package.

UninstallSAK
Uninstalls BrightStor SAK package.

UnRegisterCom
Launches DBBAFAgentWrapper.exe to unregister com.

UnregisterDiscoveryPorts
Launches RegisterDiscoveryPorts.exe to unregister Discovery Ports.

unRegisterMonadComWrapper
Launches MonadComWrapper.exe to unregister DLLs.

UpdateInoculateITSignature
Launches fi_nt86.exe to update vet signature.

UpdateVetSignature
Launch fv_nt86.exe to update vet signature.

WarningSystemRequirements
Shows warning for system requirements.

5.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 AES128-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:

When restoring folders and files, please 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 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".

6.0 Supported Upgrade Paths

You can upgrade to this release of CA ARCserve Backup from the following products:

BrightStor ARCserve Backup for Windows r11.5 (and all service packs)

BrightStor ARCserve Backup for Windows r11.1 (and all service packs)

CA ARCserve Backup for Windows r12

CA ARCserve Backup for Windows r12 SP1
Note: CA ARCserve Backup does not support upgrading BrightStor ARCserve Backup for Windows r11.1 in a cluster-aware environment to this release. You must uninstall BrightStor ARCserve Backup for Windows r11.1 and then install this release into a cluster-aware environment.

BrightStor ARCserve Backup Versions 9.01 and 10.5 (latest service packs only)--The ability to upgrade from 9.01 and 10.5 is maintained. However, a full product license is required.

For all other releases, you must uninstall the existing software version before you install CA ARCserve Backup.

6.1 Backward Compatibility

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

BrightStor ARCserve Backup r11.5 (and all service packs)

CA ARCserve Backup r12 (and all service packs)

You must retain the previous BrightStor ARCserve Backup Manager to view and manage ARCserve servers that are running the following releases:

BrightStor ARCserve Backup r11.5 (and all service packs)

BrightStor ARCserve Backup r11.1 (and all service packs)

7.0 Known Issues

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

7.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:

If you select to use an IP address for a client agent node that is not associated to the first bound network interface on that machine, you must perform the following procedure to update the IP address to the new address to allow you to add machines using AutoDiscovery:
1. On the agent machine, restart the discovery service.
2. From the Backup Manager of the base server, delete the old machine object.
3. On the base server, restart the discovery service or launch AutoDiscovery using dsconfig.exe.
4. From the Backup Manager, add the machine with the new IP address using AutoDiscovery.
5. If you have a scheduled job in the queue, delete that job and recreate it to ensure that it runs properly.

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 even when it is successful 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 and CA ARCserve Backup only supports 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.

If you attempt to restore multiple tape items in a UNIX session to your local Windows server, the restore job may fail. To avoid this problem, select a full UNIX session or just one tape item in a UNIX session to restore to your local Windows server.

Jobs run in the previous release of CA 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.

When generating reports using the Report Manager, you must store all Create now-based reports and all Schedule-based reports in the default storage location. The default storage location is in the following directory: <ARCserve_HOME>/Reports.

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 Technical 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 database, you must perform at least one full backup of the ARCserve database before you perform an incremental or a differential backup. This task ensures that ARCserve database backup sessions contain the most current data. This task ensures that ARCserve 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 /flushdsn
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.

Restore jobs cannot be submitted using the Restore by Session option of the Restore Wizard when using GFS staging backup jobs.

The ARCserve 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 ARCserve 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 ARCserve database, use the Merge utility to merge the ARCserve 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.

When you modify a makeup job that was automatically created after a full-node backup job failed, you will see that the MSDEWriter and the SQLServerWriter objects have been incorrectly selected in the Backup Manager, Source directory tree. This is only a display issue. These objects 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 XP, 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 r12.5 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 you wish to Restore by Session from either a member or primary server, submit your job using Restore Manager instead of the Restore Wizard. Restore Wizard cannot access the session media.

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.

When submitting multistream backup jobs from Backup Manager, "Use Any Group" should be selected in the Destination tab, and "Run on" should be selected in "Submit Job" window.

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 local backup of an entire drive on which Single Instance Storage was activated as the backup source, the job fails and W3404 is recorded because "database.mdb" is in use by another process. This is because CA ARCserve Backup is attempting to back up files that should have been excluded.
  - 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. However, when restoring the \SIS Common Store that was locally backed up, the common files are deleted with their links. The Job Log shows these files as skipped.

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:

Click Start, Control Panel, Administrative Tools, Services.

From the list of services, double-click SQL Server Browser service to open its properties.

Change the startup type to Disabled.

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 CASUniversalAgent depend= MSSQLXXXX
sc config CASTapeEngine depend= MSSQLXXXX
```
4. Go to step 3.
  Manually editing the registry:
  
  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 ARCserve database is configured to use SQL Server, the Database Protection Job may not be able to successfully backup the ARCserve 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 ARCserve database is being successfully backed up.

When performing a full node backup, you may skip 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

In the CA ARCserve Backup Manager Console, the CA XOsoft link under the Protection and Recovery menu does not work.

7.2 Known Issues When Upgrading to CA ARCserve Backup

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.

After upgrading to CA ARCserve Backup from BrightStor Enterprise Backup r10.5, and from CA 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.

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 from Microsoft Windows XP SP2 or above to Microsoft Vista, existing installations of CA ARCserve Backup will not work. You must uninstall CA ARCserve Backup.

After upgrading to this release of CA ARCserve Backup, Sybase databases backed up in BrightStor Enterprise Backup 10.5.1 cannot be restored.

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 2005 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 2005 Edition) that is currently installed in your CA ARCserve Backup environment and then click Next.
4. Do one of the following:
  - Microsoft SQL Server 2005 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.

7.3 Known Issues for Integration

The following issues relating to CA Desktop Management Suite Backup and CA ARCserve Backup integration are known to exist in this release:

To be integrated with CA ARCserve Backup, you must install patch T578101 with CA Desktop Management Suite Backup r11.5.

7.4 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.

Whenever you disable or enable the CA Client Agent for CA ARCserve Backup, you should also disable or enable the CA Client Agent for ARCserve Helper service.

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.
```

7.5 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.

7.6 Known Issues for the Agent for Microsoft Exchange

The following issues relating to the Agent for Microsoft Exchange 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.

The backup job will fail if a full machine backup is selected, but Microsoft Exchange is offline. The Makeup job which runs after the original job failed will also fail if Microsoft Exchange is offline when the makeup job runs.

When you uninstall the 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 the remote system.

If you are restoring an old mailbox store session backed up with the 11.5 version of the CA ARCserve Backup Agent for Microsoft Exchange to the Recovery Storage Group, this version of the Microsoft Exchange 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.

7.7 Known Issues for the Agent for Microsoft SharePoint

The following issues relating to the Agent for Microsoft SharePoint 2007 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 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 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 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 Agent to see the Microsoft SharePoint 2007 Farm.

If you upgrade the Agent for SharePoint 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).

7.8 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 a Microsoft SQL database is backed up using both the Agent for Microsoft SQL Server 2003 and the Agent for Microsoft SharePoint, the backup history for the database in the SharePoint branch of Restore by Tree will only include backups performed using the Agent for Microsoft SharePoint, while the backup history for the database in the Microsoft SQL Server branch of Restore by Tree lists all backups performed using both agents. This issue also applies to the Agent for Microsoft SharePoint.

If the Agent for Microsoft SQL Server and the database component of the Agent for Microsoft SharePoint 2003 are both deployed on the same machine, the SharePoint databases are included in whole-instance backups performed by the Agent for Microsoft SQL Server. This issue also applies to the Agent for Microsoft SharePoint.

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\CA ARCserve Backup, and the PortsConfig.cfg file for the 32-bit components is in c:\Program Files (x86)\CA\SharedComponents\CA 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 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 Microsoft Windows Small Business Server SharePoint database is stored in a Microsoft SQL Server Desktop Engine (MSDE) instance. The SharePoint instance does not support SQL-native authentication. You must use Windows authentication for this database instance.

Several MSDE-based applications do not include a System Administrator account. The application vendor may provide a backup user with only Backup Operator rights. These MSDE instances must be backed up using Named Pipes. If you are not certain whether your MSDE instance has this restriction, contact your application vendor.
If CA ARCserve Backup and the MSDE application with this requirement are installed on separate computers, you must specify the Named Pipes backup method. To specify the Named Pipes backup method, go to the Backup Manager, right-click the MSDE database, select Remote Protocol and choose Named Pipes.

If CA ARCserve Backup and the MSDE application are installed on the same computer, you must direct CA ARCserve Backup to consider the MSDE database as if it were on a different machine. To do this, perform the following steps:
1. Open the Registry Editor and find the following registry key:
  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\
2. In this registry key, add a DWORD Value called DBLocalAsRemote and set its value to 1.
3. In the Backup Manager, add a second entry for the local computer in either the Windows 2000/Windows XP/Windows 2003 Systems or Preferred Shares folder. Expand this new entry to find the MSDE database. Right-click the MSDE database, select Remote Protocol, and choose Named Pipes.
  Note: For ODBC communication, we recommend the default TCP/IP protocol. Named Pipes makes ODBC fail.

If using the CA ARCserve Backup Client Agent and the Restore by Tree method for your restore operation, databases are displayed under the Microsoft Windows Network icon in the Restore Manager.

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.

If you are using an agent from a version of BrightStor ARCserve Backup before r11.1, or any version of BrightStor Enterprise Backup, differential and incremental backup jobs cannot automatically identify new databases that require full backup rather than differential or transaction log backup.

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 or MSDE instance, some components used by other Microsoft SQL Server or MSDE 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 or MSDE 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.

CA ARCserve Backup incorrectly displays the SQL instance name instead of the agent hostname in Agent Options on the Security and Agent Information dialog.

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.

MSDE 2000 instances storing SQL Server CA ARCserve Backup database are supported like any other edition of SQL Server 2000, but MSDE 2000 limits the size of the database to just 2 GB and is therefore not recommended for storing the CA ARCserve Backup database.

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.

7.9 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 partially supports the Transactional NTFS (TxF) infrastructure on Windows Vista. 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.

7.9.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

7.9.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.

7.10 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.

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.

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

When restoring RMAN backup sessions that had been backed up using the Agent for Oracle, jobs cancelled after you insert the wrong media may remain active until you kill the RMAN.exe process on the Agent machine. To determine which RMAN process on the agent node to kill when multiple processes are running, download and install the Microsoft Process Explorer utility from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx.
1. Start the Process Explorer utility.
2. Go to View, Show Process Tree to display a list of processes.
3. Find the RMAN process initiated by CA ARCserve Backup. Look for rman.exe under the node "UnivAgent.exe, caagstart.exe" (in x86 and x64 native mode environments) and "DBBAFAgentWrapper.exe" (in x64 WOW mode environments).
4. Press Delete to kill the process.

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

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

This release of CA ARCserve Backup will not support restore of OLD Oracle agent sessions using RMAN agent. 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 (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.

Smart 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.

Merge operations on file system devices containing Oracle backup sessions are not supported for this release.

To encrypt Oracle data during the backup phase or the migration phase of a staging backup, you must specify one of the following options:
- Encrypt data at Backup Server during backup
- Encrypt data at Backup Server during migration
  You can specify these options by doing the following:
1. Open the Backup Manager and click the Options toolbar button.
  The Options dialog opens.
2. Click the Backup Media tab.
  The Backup Media options appear.
3. From the Encrypt data drop-down list, select the at Backup Server during backup option or the Encrypt data at Backup Server during migration option and click OK.

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.

7.12 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.

7.13 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.

When you use the Client Agent with the Restore by Tree method, databases appear under the Microsoft Windows Network icon in the Restore Manager.

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 10.5.1 or 9.01 cannot be restored with CA ARCserve Backup after the 11.1.2 version.

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:

Open a command line prompt and start isql.

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

7.14 Known Issues for the Disaster Recovery Option

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

When you run a remote recovery and the base is Windows XP with SP2, you must use different configurations depending on the version of CA ARCserve Backup used to create your full backup:
- If your full backup was made using CA ARCserve Backup r11.1, when you recover the machine, you must change the Share and security model for local account option in the Local security settings on the base Windows XP SP2 machine from the default setting of Guest only to Classic.
- If your full backup was made with CA ARCserve Backup r11.5, on the base Windows XP SP2 machine, set the following registry key value to 0:
```
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\RPC\RestrictRemote
```
  You do not need to change the Share and security model for local account setting

When performing Disaster Recovery on primary server, CA ARCserve Backup may fail to recover the database if the backup server is the member server. When ca_recoverdb submits the job to the member server, the job engine of the primary server is unable to launch it because the member server is not a member of the domain at the moment. We recommend using a cahost switch to move tape from the member server to the primary server and then submit the recover command.

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.

Disaster Recovery does not support Scan and Replace functionality for CA ARCserve Backup database sessions.

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.

A password created in the Global Options screen applies to all sessions backed up at that time. When performing Disaster Recovery, you must enter that password for each session you are restoring. No "global" method of entering this password exists at Disaster Recovery time.

Tape device names may not appear correctly when executing DRSCANSESSION.EXE. DRSCANSESSION.EXE is only for Windows 2000 systems.

When using DRSCANSESSION.EXE to update machine specific data by scanning tape, note that Disaster Recovery will restore the job queue session, the SQL DR Element session, and the CA ARCserve Backup database to a session one version earlier than other sessions such as system state or volume sessions. This is because these sessions are backed up after a Disaster Recovery session, therefore the sessions recorded in DR session are from the previous backup. If the first backup is selected for DR restore using this utility these sessions will not be restored during Disaster 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.

When a local backup of 32-bit Windows 2000, Windows XP, or Windows 2003 systems is performed with the Encryption at agent side option selected, please note that the system state session is not actually encrypted. Instead, it is password protected. In this version of CA ARCserve Backup, at Disaster Recovery time, the system state session is not considered an encrypted session but will have a key icon with a question mark (?). Click this icon to enter your system state password. You won't need to input the password during Recovery.

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). Alternatively, you may create two floppy disks and manually copy disaster recovery files to them, as follows:
1. Create MSD to a folder, such as C:\MSD\
2. Manually copy the following files under C:\MSD\ to floppy disk #1:
  - DRLaunch.exe
  - DRLaunchres.dll
  - AutoUnattend.xml
3. Under the C:\MSD directory, find a subfolder called machine_DRIF(datetime). Copy this folder to floppy disk #2.
4. During Disaster Recovery, use floppy disk #1 and your Windows 2008 CD to boot Windows. When the Disaster Recovery Wizard requests the MSD, insert floppy disk #2 and select MSD from it. Disaster recovery should proceed normally at this point.

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-960863, 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

7.15 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. This is because the Dashboard reports only display the nodes in your backup environment running the CA ARCserve Backup agents at the current version of CA ARCserve Backup for primary/standalone servers.

Nodes running the CA ARCserve Backup Agent for Microsoft Exchange 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 an older version to this release, 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 the Dashboard does not display any data after you have restored an older version of the CA ARCserve Backup database, use the Server Configuration Wizard to enter the CA ARCserve Backup Database credentials after the restore and re-launch Dashboard. For more information about using the Server Configuration Wizard, see the Administration Guide.

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.

7.16 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.

7.17 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.
```

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.

DDS configuration is supported in SAN environments with NAS on Windows SAN primary servers. This configuration is not supported on Windows SAN member servers.

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.

7.18 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.

7.19 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.

7.20 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.

7.21 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 (Windows 2000): ibmlto
- Magstar (Windows 2000): magstar
- 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.

7.22 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.

7.23 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.

7.24 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\ARCserve Backup\Base\Tape
```

7.25 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 r12 SP1.

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.

7.26 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.

7.27 Known Issues for CA ARCserve Backup Licensing

The following issues are known to exist in this release:

When you are applying CA ARCserve Backup licenses on machines running Windows Server 2008, use the Manager License Verification dialog. On Windows Server 2008 systems, the calicnse.exe application runs with minimal privileges, even if you log on as Administrator. Therefore, it lacks sufficient privileges to write license information to the ca.olf file. If you are applying old license keys that can only be applied through the calicnse.exe application, right-click calicnse.exe and select Run as Administrator from the shortcut menu. You will then be able to apply license keys correctly.

A License Message Notification is written to the Event Viewer every hour and pops up when you use licenses for the Agent for Open Files originally purchased for physical machines and then converted to virtual machines. Close the message to continue using your physical licenses in a virtual environment. To stop the message from appearing every hour, enable the option, Do not show this dialog again. A similar problem occurs when you install CA ARCserve Backup and the CA ARCserve Backup Agent for Open Files on a virtual machine without the CA ARCserve Backup Agent for Virtual Machines. For more information, refer to the topic, Known Issues for the Agent for Virtual Machines.

If you are upgrading from a previous version of CA ARCserve Backup for which you have a valid Disk to Disk to Tape license, you may contact CA Support to obtain a new Enterprise Module license. The Enterprise Module is now required in order to access the Disk to Disk to Tape option.

7.28 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

Agent for Virtual Machines Guide

Removed the following items from the topic Backup and Restore Limitations on Virtual Machines because they are not pertinent:

There is no application level consistency support when backing up data using a backup proxy system.
To protect application level data, you can create custom prescripts and postscripts that let you keep application level data in a consistent state. You can use the custom scripts as pre-freeze and post-thaw scripts. For more information about pre-freeze and post-thaw scripts, see the VMware Virtual Machine Backup Guide.

You must run ARCserve VMware Configuration Tool (ca_vcbpopulatedb.exe) and ARCserve Hyper-V Configuration Tool (ca_msvmpopulatedb.exe) after you add, remove, or change volumes in a VM or a VM in the host system.
Failure to do so can result in inaccurate VM volume data in the CA ARCserve Backup database, and failed backup jobs will occur at runtime.

Online Help

The Database option has been removed from the Operation tab in Global Options. The following topics should be deleted from Online Help:
- Database Operation Option - Record Job and Session Information Only
- Configure Job - Level Merge Options (Windows Servers)
- Database Operation Option - Record Detail Information
  The following topics should be modified to reflect the removal of this option in Online Help:
- Catalog Database

The following topics should be modified so that users are now instructed to license the Enterprise Module, instead of the Disk to Disk to Tape Option.
- Specify Tape Copy Policies - Miscellaneous Options
- Specify Miscellaneous Options for Disk Staging Backups
- Staging Group Configuration Dialog
- Group Configuration File System Device Page

The following information was omitted from the CA ARCserve Backup and CA XOsoft Integration Guide:
From CA XOsoft r12 SP1, the Replica server can also be a Windows Server 2008 server.

The following note should be added to E3742 in the Online Help:
- Note: This message appears as an error if the backup job cannot start because of a license problem and appears as a warning in cases where the backup job just has to limit the number of streams, but the backup can continue.

Error AE0566 should be changed in the Online Help as follows:
CA ARCserve Backup will not be able to recover the VM if the WMware converter enterprise for VirtualCenter is installed on the proxy.

Error E63526 is missing from the Online Help, and should appear as follows:
Failed to export the media from the slot (Slot=[slot number], Device=[device number] [vendor ID])

Module:

Tape Engine

Reason:

This is an indication of a hardware error. The mail slot may have failed, all mail slots may be full, or the SCSI command execution may have failed.

Action:

See the file tape.log

The Error Message AE0430 Failed to restore SYSVOL, should be changed in the Online Help to include the definition for the abbreviation, FRS and should appear as follows:
Failed to restore SYSVOL

Module:

Client Agent

Reason:

The File Replication Service (FRS) component is not installed on the agent machine. This problem will occur while restoring the System State.

Action:

To remedy this condition, complete the following steps:

1. Install File Replication Service (FRS) on the target Windows machine.

2. Restart the machine after you install FRS.

3. Resubmit the restore job.

The topic, Media Assurance Report, incorrectly links to the topic, Media Assurance Report - Report Benefits. The topic should display the following:
This report shows the number of nodes that have/have not been scanned to ensure that the sessions on the media are restorable. This report can be used to determine if the data from your nodes is properly protected on the media and provides a means to quickly identify and resolve potential problem areas with restoring your backups.

The Error Message, E3560 Failed to perform Hyper-V VM file mode backup, should be changed in the Online Help as follows:
Module:

Task

Reason:

CA ARCserve Backup is unable to retrieve VM information from the database.

Action:

Please specify the CA ARCserve Backup server name on the Agent for Virtual Machines tab of the Backup Agent Admin Configuration dialog.

The topic, Backup Operations Options, shows an incorrect description for the "Delete Source Files After Backup to Media" option, and should read as follows:
On Windows computers, protected system files and files that are excluded from the backup by other filters are not deleted. For a remote backup job, a 64-bit operating system local backup job, or a Windows Server 2008 local backup job, the Windows Client Agent backs up the files. After the backup, this option deletes only the files from the specified unprotected folder. It does not delete the empty folder itself. Boot files, however, are not protected and can be deleted.

Command Line Interface

In the topic, ca_backup Operation Options, the command line help contains an incorrect description for the "-deletefiles" option, and should read as follows:
On Windows computers, protected system files and files that are excluded from the backup by other filters are not deleted. For a remote backup job, a 64-bit operating system local backup job, or a Windows Server 2008 local backup job, the Windows Client Agent backs up the files. After the backup, this option deletes only the files from the specified unprotected folder. It does not delete the empty folder itself. Boot files, however, are not protected and can be deleted.

Documentation Changes

The following CA ARCserve Backup documents have been updated for this release:

Administration Guide

Agent for Lotus Domino Guide

Agent for Oracle Guide

Agent for Open Files Guide

Agent for IBM Informix Guide

Agent for Virtual Machines Guide

Client Agents Guide

Client Agent and Enterprise Options Readme

Command Line Reference Guide

Dashboard User Guide

Disaster Recovery Options Guide

Enterprise Option for SAP R/3 for Oracle Guide

Implementation Guide

Online Help

NDMP NAS Option Guide

Tape Library Option Guide

Readme

Release Summary

Note: You can access the most current documents from the product installation media.

7.29 Portmapper Conflicts with CA ARCserve Backup

If CA ARCserve Backup detects port 111 conflicts, indicating that it is using the same port number for the CA ARCserve PortMapper service as a previously installed portmapper, CA ARCserve Backup automatically switches to another port number.

To avoid having other software affected by a similar problem, change the Automatic status of the CA ARCserve PortMapper service to Manual. If you have installed CA ARCserve Backup in a Microsoft Cluster Services environment, change the Automatic status of the CA ARCserve PortMapper service to Disabled. This enables you to avoid similar port conflicts after the system has completed the boot process. It is not necessary to restart this service every time the system reboots.

CA ARCserve Backup can work with external Portmappers (SFU 3.0, Noblenet Portmapper, StorageTek, Libattach etc.). However, during the machine boot up sequence, CA ARCserve Backup services may try to initialize before the external portmapper has fully initialized. Under these circumstances, CA ARCserve Backup services then fail to initialize. To avoid this problem, perform the following steps:

Create the DWORD DelayedRegistration in the following:

HKEY_LOCAL_MACHINE\Software\ComputerAssociates\ARCserve Backup\Base\

Assign a decimal value for this key, indicating the number of minutes CA ARCserve Backup services wait before initializing portmapper registration. For example, DelayedRegistration=2 causes all CA ARCserve Backup services to start, but not register with the portmapper for two minutes after startup.

8.0 Included Fixes

The following tables list the fixes included in the current and prior releases of CA ARCserve Backup. If you do not see a specific fix listed in this section, please contact CA Technical Support for more information.

8.1 Fixes Included in CA ARCserve Backup r12.5

The following fixes were included in CA ARCserve Backup r12.5:

T146490	T245547	T46B238	T5E5022	T5K8001	T5KM001
T146491	T2D2676	T4C4052	T5E5023	T5K8002	T5KM002
T146494	T2D2679	T4C4053	T5E5024	T5K8003	T5KM003
T146495	T2D2680	T512092	T5E5025	T5K8005	T5KM004
T146496	T2D2683	T512093	T5E5026	T5K8006	T5KM005
T16C766	T2D2688	T512099	T5E5027	T5K8007	T5KM006
T16C768	T2D2690	T58E090	T5GT033	T5K8008	T5KM007
T16C769	T31A503	T58E092	T5GT034	T5K8009	T5KM008
T16C770	T31A504	T58E095	T5GT035	T5K8010	T5KM009
T16C772	T31A505	T596030	T5GT036	T5K8012	T5KM010
T16C776	T31A507	T596032	T5GT039	T5K8013	T5KM011
T16C779	T31A508	T596034	T5JS006	T5K8014	T5KM012
T245506	T31A510	T596036	T5JS008	T5K8015	T5KM013
T245510	T36A493	T59E033	T5K7001	T5K8016	T5KM014
T245517	T36A496	T59E034	T5K7003	T5K8019	T5KM015
T245519	T36A498	T59E036	T5K7004	T5K8020	T5KM016
T245520	T36A500	T59E038	T5K7005	T5K8021	T5KM017
T245523	T36A501	T59E039	T5K7006	T5K8022	T5KM018
T245525	T36A502	T5A0026	T5K7007	T5K8023	T5KM019
T245527	T36A503	T5A0027	T5K7008	T5K8025	T5KM020
T245528	T36A504	T5A6085	T5K7009	T5K8026	T5LD001
T245530	T36A505	T5A6086	T5K7010	T5K8027	T5LD004
T245532	T36A506	T5A6089	T5K7011	T5KC003	T5LD005
T245533	T36A508	T5A6090	T5K7012	T5KC004	T5LD006
T245534	T36A513	T5A6091	T5K7014	T5KF006
T245535	T46B229	T5E5014	T5K7015	T5KF007
T245537	T46B231	T5E5016	T5K7016	T5KF008
T245538	T46B234	T5E5017	T5K7017	T5KF009
T245540	T46B235	T5E5021	T5K7018	T5KF013

8.2 Fixes Included in CA ARCserve Backup r12 SP1

The following fixes were included in CA ARCserve Backup r12 SP1:

QO94901	T245435	T2D2637	T36A455	T46B211	T5A6069
QO95065	T245440	T2D2638	T36A456	T46B214	T5A6070
QO95275	T245444	T2D2639	T36A457	T46B217	T5A6071
QO99390	T245445	T2D2640	T36A459	T46B218	T5A6072
QO99421	T245447	T2D2641	T36A460	T512082	T5A6076
QO99452	T245448	T2D2642	T36A461	T512083	T5A6077
QO9974	T245450	T2D2643	T36A462	T56D014	T5A6079
QO99844	T245451	T2D2644	T36A474	T56D015	T5E5009
T146472	T245452	T2D2649	T36A476	T58E057	T5GT008
T146473	T245453	T2D2649	T36A477	T58E060	T5GT010
T146479	T245454	T2D2651	T36A478	T58E062	T5GT011
T146480	T245457	T2D2654	T36B273	T58E063	T5GT013
T16C729	T245458	T31A444	T36B275	T58E064	T5GT016
T16C732	T245460	T31A474	T439082	T58E069	T5GT023
T16C733	T245461	T31A480	T439090	T58E077	T5GT026
T16C734	T245476	T31A481	T46B174	T59E022	T5JS001
T16C735	T245480	T36A409	T46B199	T59E024	TF68236
T16C739	T245482	T36A423	T46B200	T5A0023
T16C748	T245483	T36A448	T46B201	T5A6060
T16C751	T2D2632	T36A449	T46B205	T5A6061
T16C753	T2D2633	T36A450	T46B206	T5A6064
T16C754	T2D2636	T36A454	T46B209	T5A6067

8.3 Fixes Included in CA ARCserve Backup r12

The following fixes were included in CA ARCserve Backup r12:

T146419	T16C730	T245402	T31A457	T36B262	T58F020
T146434	T1A5335	T245403	T31A458	T36B263	T58F021
T146435	T1A5356	T245404	T31A459	T36B266	T58F023
T146437	T1A5358	T245405	T31A460	T36B268	T58F025
T146441	T1A5359	T245406	T31A461	T36B270	T595008
T146443	T1A5360	T245407	T31A462	T36B271	T595009
T146445	T1A5362	T245408	T31A463	T36B272	T595010
T146450	T1A5363	T245410	T31A464	T46B144	T595012
T146451	T1A5364	T245411	T31A465	T46B147	T595013
T146452	T1A5367	T245412	T31A466	T46B150	T595014
T146453	T245284	T245415	T31A467	T46B152	T595015
T146454	T245293	T245416	T31A468	T46B154	T595016
T146455	T245301	T245417	T31A469	T46B155	T595017
T146457	T245302	T245418	T31A470	T46B156	T595018
T146458	T245303	T245419	T31A472	T46B157	T595019
T146459	T245304	T245420	T354201	T46B158	T596005
T146460	T245305	T245421	T36A345	T46B159	T596006
T146461	T245306	T245422	T36A359	T46B162	T596007
T146462	T245307	T245423	T36A360	T46B164	T596008
T146463	T245308	T245424	T36A361	T46B167	T596009
T146464	T245309	T245425	T36A363	T46B168	T596010
T146465	T245311	T245426	T36A364	T46B171	T596012
T146466	T245312	T245427	T36A365	T46B174	T596014
T146468	T245313	T245429	T36A367	T46B175	T596015
T146471	T245314	T245432	T36A368	T46B176	T596016
T16C630	T245315	T245433	T36A369	T46B177	T596017
T16C631	T245317	T245435	T36A372	T46B179	T59E008
T16C633	T245318	T245436	T36A375	T46B180	T59E009
T16C642	T245319	T245438	T36A378	T46B181	T59E010
T16C643	T245320	T245441	T36A379	T46B182	T59E011
T16C645	T245322	T245443	T36A380	T46B183	T59E012
T16C646	T245323	T245450	T36A381	T46B184	T59E013
T16C647	T245324	T2D2536	T36A382	T46B185	T59E014
T16C648	T245325	T2D2548	T36A383	T46B186	T59E015
T16C649	T245327	T2D2579	T36A384	T46B187	T59E017
T16C651	T245328	T2D2580	T36A385	T46B188	T5A0018
T16C653	T245329	T2D2581	T36A386	T46B189	T5A0019
T16C655	T245330	T2D2582	T36A388	T46B190	T5A0020
T16C656	T245330	T2D2583	T36A389	T46B191	T5A0021
T16C657	T245332	T2D2586	T36A390	T46B192	T5A6020
T16C658	T245334	T2D2587	T36A391	T46B193	T5A6022
T16C661	T245335	T2D2589	T36A393	T46B197	T5A6025
T16C662	T245336	T2D2590	T36A394	T56D002	T5A6026
T16C663	T245342	T2D2591	T36A395	T56D004	T5A6027
T16C664	T245344	T2D2592	T36A396	T56D005	T5A6029
T16C666	T245345	T2D2594	T36A397	T56D010	T5A6031
T16C674	T245346	T2D2595	T36A398	T577011	T5A6032
T16C676	T245347	T2D2596	T36A399	T577015	T5A6033
T16C677	T245349	T2D2597	T36A400	T58E018	T5A6034
T16C678	T245354	T2D2599	T36A407	T58E019	T5A6035
T16C679	T245355	T2D2606	T36A410	T58E020	T5A6037
T16C680	T245356	T2D2616	T36A414	T58E021	T5A6042
T16C681	T245363	T2D2619	T36A415	T58E022	T5A6043
T16C693	T245365	T2D2620	T36A416	T58E023	T5A6044
T16C694	T245366	T2D2621	T36A417	T58E025	T5A6045
T16C695	T245367	T2D2622	T36A418	T58E026	T5A6046
T16C696	T245368	T2D2623	T36A421	T58E027	T5A6047
T16C697	T245369	T2D2624	T36A422	T58E029	T5A6049
T16C698	T245370	T2D2625	T36A423	T58E030	T5A6051
T16C701	T245371	T2D2628	T36A426	T58E031	T5A6052
T16C702	T245372	T2D2629	T36A428	T58E032	T5A6053
T16C703	T245373	T2D2630	T36A429	T58E037	T5A6054
T16C704	T245374	T2D2631	T36A430	T58E043	T5A6055
T16C705	T245377	T2D2634	T36A432	T58E044	T5A6056
T16C706	T245378	T2D2635	T36A433	T58E046	T5A6057
T16C707	T245380	T2D2637	T36A435	T58E049	T5A6058
T16C709	T245381	T31A345	T36A436	T58E050	T5A6059
T16C710	T245384	T31A402	T36A437	T58E051	T5E5003
T16C711	T245386	T31A403	T36A438	T58E052	T5E5004
T16C713	T245387	T31A405	T36A439	T58E053	T5E5005
T16C714	T245388	T31A411	T36A441	T58E054	T5E5006
T16C715	T245390	T31A412	T36A443	T58E055	T5GT003
T16C717	T245392	T31A421	T36A444	T58E058	T5GT004
T16C719	T245393	T31A438	T36A445	T58E060	T5GT005
T16C720	T245396	T31A443	T36A446	T58E061	T5GT006
T16C722	T245397	T31A449	T36A447	T58E065
T16C724	T245398	T31A450	T36B231	T58F016
T16C725	T245399	T31A452	T36B255	T58F017
T16C727	T245400	T31A453	T36B258	T58F018
T16C728	T245401	T31A456	T36B259	T58F019

9.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.

10.0 Contact CA

Contact Technical Support

For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.com/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 product documentation, you can send a message to techpubs@ca.com.

If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA support website, found at http://ca.com/support.