BrightStor® ARCserve® Backup for Windows r11.5 Readme
D01192-1E

10.0 Contact Customer Support

1.0 Welcome

Welcome to BrightStor® ARCserve® Backup for Windows r11.5. This Readme file contains important information to help you with your implementation of the product, including installation considerations, operating system information, known issues, and how to contact Computer Associates Customer Support.

2.0 Operating System Support

BrightStor ARCserve Backup for Windows is supported on the following operating systems:

• Windows XP Professional 32-bit (Server, Manager, and Client Agent) and 64-bit (Client Agent only) (at minimum, Service Pack 1 and Service Pack 2)

• Windows Server 2003 Web Edition (32-bit only)

• Windows Server 2003 Standard Edition (32-bit, x64, and IA-64)

• Windows Server 2003 Enterprise Edition (32-bit, x64, and IA-64)

• Windows 2000 Professional 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)

• Windows 2000 Server 32-bit (Service Pack 3 Service Pack 4, or Service Pack 4 Rollup 1)

• Windows 2000 Advanced Server 32-bit (Service Pack 3 Service Pack 4, or Service Pack 4 Rollup 1)

• Windows 2000 Cluster Server (2 node Advanced Edition)

• Windows Server 2003 Cluster 32-bit, x64, and IA-64

• Windows 2000 and Windows 2003 Datacenter 32-bit and 64-bit

• Windows Powered NAS (2000)

• Windows Storage Server 2003

• Windows Small Business Server 2000

• Windows Small Business Server 2003 and Windows Small Business Server 2003 plus Service Pack 1

• Microsoft Virtual PC 2004, Microsoft Virtual Server 2005 (BrightStor ARCserve Backup base product, BrightStor® ARCserve® Backup Client Agent for Windows, and BrightStor® ARCserve® Backup Agent for Open Files only)

• VMware GSX Server version 3.0 and 3.1, VMware ESX Server 2.5 and 2.51, VMware Workstation 4.0, 4.5, and 5.0 (BrightStor ARCserve Backup base product, BrightStor ARCserve Backup Client Agent for Windows, and BrightStor ARCserve Backup Agent for Open Files only)

Note: BrightStor ARCserve Backup supports Windows NT using the BrightStor® ARCserve® Backup Client Agent for Windows NT only. Windows NT is not supported on the server.

2.1 Support for 64-bit Windows Platforms

You can install BrightStor ARCserve Backup on the following 64-bit Windows platforms:

• Intel Itanium (IA-64) family
• x64-based systems including AMD Athlon64 and Opteron and Intel Xeon EM64T

Due to differences between 64-bit and 32-bit Windows platforms, the following elements of 64-bit operating systems cannot be accessed by 32-bit applications:

• Areas of the Windows System Registry
• System settings files included in a System State backup
• Volume Shadow Copy Service (VSS) writers

To perform backup and restore operations on 64-bit machines, the 64-bit version of the BrightStor® ARCserve® Backup Client Agent for Windows must be installed with the server.

3.0 System Requirements

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

3.1 BrightStor ARCserve Backup Base Product

The minimum system requirements for BrightStor ARCserve Backup are:

• CPU: 350 MHz

• RAM: 512 MB

• Disk Space: 500 MB free disk space

• Internet Explorer: Version 6.0

In addition to these requirements, you should consider the disk space necessary for the Raima or Very Large Database (VLDB), the default BrightStor ARCserve Backup database. Depending upon usage, the BrightStor ARCserve Backup database can grow to several GB in size.

3.2 Disk Staging Option

BrightStor ARCserve Backup for Windows must be installed before you install the BrightStor® ARCserve® Backup Disk Staging Option.

The following are the minimum platform requirements for the Disk Staging Option:

• Windows 2000

• Windows XP Professional

• Windows 2003

• Windows Storage Server 2003

3.3 Client Agents

The following sections provide hardware and software requirements for the BrightStor® ARCserve® Backup Client Agents.

Hardware Requirements

To install the agent, your system must meet the following minimum hardware requirements:

• Windows-based platforms:

  • CPU: 200 MHz

  • Memory: 256 MB RAM

  • Disk space: 100 MB

• NetWare-based platforms:

  • CPU: NetWare version 4.2 requires an 80586 processor with 128 MB RAM; NetWare versions 5.1, 6.0 and 6.5 require a Pentium-class processor with at least 512 MB RAM

  • Disk space: 20 MB

• UNIX-based platforms:

  • Memory: 128 MB RAM

  • Disk space: 16 MB

• Linux-based platforms:

  • Memory: 128 MB RAM

  • Disk space: 10 MB

To install the Client Agent for Mac OS X, your system must meet the following minimum hardware requirements:

• Minimum 10 MB hard disk space

• Minimum 128 MB RAM

Software Requirements

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

• BrightStor® ARCserve® Backup Client Agent for Windows:

  • Windows XP Professional 32-bit (Server, Manager, and Client Agent) and 64-bit (Client Agent only) (at minimum, Service Pack 1 and Service Pack 2)

  • Windows Server 2003 Web Edition (32-bit only)

  • Windows Server 2003 Standard Edition (32-bit, x64, and IA-64)

  • Windows Server 2003 Enterprise Edition (32-bit, x64, and IA-64)

  • Windows 2000 Professional 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)

  • Windows 2000 Server 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)

  • Windows 2000 Advanced Server 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)

  • Windows 2000 Cluster Server (2 node Advanced Edition)

  • Windows Server 2003 Cluster 32-bit, x64, and IA-64

  • Windows 2000 and Windows 2003 Datacenter

  • Windows Powered NAS (2000)

  • Windows Storage Server 2003

  • Windows Small Business Server 2000

  • Windows Small Business Server 2003 and Windows Small Business Server 2003 plus Service Pack 1

  • Windows NT

• BrightStor® ARCserve® Backup Client Agent for NetWare:

  • Novell NetWare version 4.2

  • Novell NetWare version 5.1

  • Novell NetWare version 6.0 or 6.5 SP1, SP2, or SP3

• BrightStor® ARCserve® Backup Client Agent for UNIX:

  • Solaris 2.6, 7, 8, 9, and 10 SPARC

  • Solaris 9 and 10 (x86 32-bit)

  • Solaris 10 AMD64

  • IBM AIX 4.3.3, 5L v5.1, v5.2, and v5.3

  • HP-UX 11.0, 11.11, and 11.23 PA RISC

  • HP-UX 11.22 and 11.23 Itanium (IA-64)

  • Tru64 v4.0E, v4.0F, v4.0G, v5.0, v5.1, v5.1a, v5.1b

• BrightStor® 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) (IA-64)

  • Red Hat Enterprise Linux 4 (AS, ES, WS) (x86, AMD64, Intel EM64T, and IA-64)

  • SuSE Linux Enterprise Server 7

  • SuSE Linux Enterprise Server 8 (x86, AMD64, Intel EM64T, and IA-64)

  • SuSE Linux Enterprise Server 9 (x86, AMD64, Intel EM64T, and IA-64)

  • SuSE Standard Server 8

  • SuSE Professional 8, 9, 9.1, 9.2. and 9.3

  • SuSE Linux Desktop 1

  • 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 IA-64)

  • Asianux 1.0

  • SCO Linux Server 4.0

  • Debian 3.0

• BrightStor® ARCserve® Backup Client Agent for Mac OS X:

  • Apple Power Mac G4/G5 (Mac OS X 10.2, 10.3, 10.4)

  • Apple X Server (Mac OS X 10.2, 10.3, 10.4)

• BrightStor® ARCserve® Backup Client Agent for OpenVMS

  • VAX 6.2, 7.1, 7.2, 7.3

  • AXP 6.2, 7.1, 7.2, 7.3

• BrightStor^® ARCserve^® Backup Enterprise Option for AS400:

  • AS400 V3 R7 M0 to V4 R5 M0

  • AS400 V5 R1 (5.1) V5R2 (5.2)

3.4 Agent for IBM Informix

The BrightStor® ARCserve® Backup Agent for IBM Informix requires the following:

• Informix Dynamic Server 9.21 or 9.40

• Agent for IBM Informix

• BrightStor ARCserve Backup for Windows

3.5 Agent for Lotus Domino

The BrightStor® ARCserve® Backup Agent for Lotus Domino has been tested with the following:

• Lotus Domino Server version 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 6.0 for Windows NT 4.0 Service Pack 6a

• Lotus Domino Server version 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 5.0.12, 5.0.13, 5.0.13a, 5.0.14, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.5, 6.5.1, 6.5.2, 6.5.3, 6.5.4 for Windows 2000 and Windows Server 2003 Standard Edition, and Enterprise Edition.

3.6 Agent for Microsoft Exchange Server

The following sections provide the hardware and software requirements for installing and running the BrightStor® ARCserve® Backup Agent for Microsoft Exchange Server.

Hardware Requirements

To install the agent, the following hardware must be available and configured:

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

• At least 512 MB RAM

• At least 100 MB of free disk space

Note: You must meet the base BrightStor ARCserve Backup product requirements before you install the agent and BrightStor ARCserve Backup on the same machine. For updated information about these requirements, contact Computer Associates Customer Support at http://ca.com.

Software Requirements

The Agent for Microsoft Exchange Server requires at least one of the following Windows operating systems:

• Microsoft Windows NT 4.0 Service Pack 6a

• Microsoft Windows 2000 Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1

• Microsoft Windows 2003

The Agent for Microsoft Exchange Server requires at least one of the following Windows Exchange versions:

• Microsoft Exchange Server Version 5.5 Service Pack 4

• Microsoft Exchange Server Version 2000 Service Pack 3

• Microsoft Exchange Server Version 2003 Service Pack 1

3.7 Agent for Microsoft Exchange Server Premium Add-on

The following sections provide hardware and software requirements for installing and running the BrightStor® ARCserve® Backup Agent for Microsoft Exchange Server Premium Add-on.

Hardware Requirements

To install the agent, the following hardware must be available and configured:

• The base Microsoft Exchange Server hardware requirements (For information about these requirements, see the Microsoft website)

• At least 512 MB RAM

• At least 200 MB of free disk space

Note: You must meet the base BrightStor ARCserve Backup product requirements before you install the agent and BrightStor ARCserve Backup on the same machine. Contact Computer Associates Customer Support at http://ca.com for any updates to these requirements.

Software Requirements

The Agent for Microsoft Exchange Server Premium Add-on requires at least one of the following Windows operating systems:

• Microsoft Windows NT 4.0 Service Pack 6a

• Microsoft Windows 2000 Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1

• Microsoft Windows 2003

• Microsoft Exchange Server Version 5.5 Service Pack 4

• Microsoft Exchange Server Version 2000 Service Pack 3

• Microsoft Exchange Server Version 2003 Service Pack 1

3.8 Agent for Microsoft SharePoint

The BrightStor® ARCserve® Backup Agent for Microsoft SharePoint requires the following:

• The Agent for Microsoft SharePoint is supported on the following:

  • Windows 2003 Standard

  • Windows 2003 Enterprise

  • Windows 2003 Web

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

• BrightStor 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 BrightStor ARCserve Backup is supported.

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

  • Microsoft SharePoint Portal Server 2003 SP1

  • Microsoft Windows SharePoint Services 2.0 SP1

• The agent is supported on Windows Small Business Server 2003 and has been tested on Windows 2003 Service Pack 1 and Windows Small Business Server 2003 Service Pack 1.

3.9 Agent for Microsoft SQL Server

The BrightStor® ARCserve® Backup Agent for Microsoft SQL Server requires at least one of the following Microsoft SQL Server platforms:

• Microsoft SQL Server 7.0 with Service Pack 4

• Microsoft SQL Server 2000 (32-bit and 64-bit) with Service Pack 3, Service Pack 3a, and Service Pack 4

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

• Microsoft SQL Server 2005 Beta 2 (x86) and the March 3, 2005, April 18, 2005, and June 7, 2005 Community Technology Previews (x86, x64, IA-64)

BrightStor ARCserve Backup is also required.

Note: If you are using Microsoft SQL Server 2000 64-bit Edition Service Pack 4, you should be aware that the service pack is missing a 32-bit DLL. Without this DLL, you cannot perform virtual device-based backups. Contact Microsoft to obtain help with this issue.

Microsoft SQL Server 2005 Support

The Agent for Microsoft SQL Server is compatible with the following versions of Microsoft SQL Server 2005:

• The agent is compatible with Microsoft SQL Server 2005 Beta 2 and the March 3, 2005, April 18, 2005, and June 7, 2005 Community Technology Preview for x86-based (32-bit) systems on Windows 2000 SP3 and SP4 and on Windows 2003.

• The agent is compatible with the Microsoft SQL Server 2005 March 3, 2005, April 18, 2005, and June 7, 2005 Community Technology Preview for x64-based (Athlon64, Opteron, Xeon EM64T) and IA-64 (Itanium) systems on Windows 2003 SP1.

• The agent is expected to be compatible with future beta and CTP builds of Microsoft SQL Server 2005 and with the final product when released.

Microsoft SQL Server 7.0 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 7.0 Service Pack 4 on the following operating systems:

• Windows NT Server 4.0 Service Pack 6a

• Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1

• Windows 2003 and Windows 2003 with Service Pack 1

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 NT 4.0 Service Pack 6a

• Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1

• Windows 2003 and Windows 2003 with Service Pack 1

Support for 64-bit Systems

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

• Microsoft SQL Server 2000 64-bit Edition for IA-64 on Windows 2003 for Itanium systems

  Note: If you are using Microsoft SQL Server 2000 64-bit Edition Service Pack 4, you should be aware that the service pack is missing a 32-bit DLL. Without this DLL, you cannot perform virtual device-based backups. Contact Microsoft to obtain help with this issue.

• Microsoft SQL Server 2000 for x86 (32-bit) on Windows 2003 SP1 for x64-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 NT 4.0 Service Pack 6a

• Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1

• Windows XP Service Pack 1 and Service Pack 2

• Windows Server 2003 and Windows 2003 with Service Pack 1

3.10 Agent for Open Files

The following section provides the minimum system requirements for the BrightStor® ARCserve® Backup Agent for Open Files:

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

  • Windows NT 4.0

  • Windows 2000

  • Windows XP x86, x64, and IA-64

  • Windows Server 2003 Web Edition, Standard Edition, or Enterprise Edition x86, x64, and IA-64

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

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

3.11 Agent for Oracle

The following section provides the minimum system requirements for the BrightStor® ARCserve® Backup Agent for Oracle:

• Oracle Server version 8, 8i, 9, 9i, or 10g

• Oracle Fail Safe (OFS) Cluster version 3.3.1, 3.3.2 and 3.3.3 on 9.2.0.11

• Windows NT 4.0 Service Pack 6a, Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1, or Windows 2003 Service Pack 1

The Agent for Oracle supports Oracle Real Application Clusters (RAC) architecture through the use of the Oracle Recovery Manager (RMAN) utility.

3.12 Agent for Sybase

The BrightStor® ARCserve® Backup Agent for Sybase requires Sybase Adaptive Server 11.9.2, 12.0, or 12.5.

The Agent for Sybase supports Windows as the host server platform. For Sybase Version 11.9.2, contact Sybase for the necessary bcksrvr.exe and sybmuf.exe files.

3.13 Disaster Recovery Option

The BrightStor® ARCserve® Backup Disaster Recovery Option supports the following:

• The following versions of Windows are supported for floppy-based disaster recovery:

  • Windows NT 4.0 Server with Service Pack 6a (remote only)

  • Windows NT 4.0 Workstation with Service Pack 6a (remote only)

  • Windows 2000 Professional Edition

  • Windows 2000 Server Edition

  • Windows 2000 Advanced Server Edition

• The following versions of Windows are supported for bootable tape disaster recovery:

  • Windows 2000 Professional Edition

  • Windows 2000 Server Edition

  • Windows 2000 Advanced Server Edition

  • Windows XP Professional Edition

  • Windows 2003 Web Edition

  • Windows 2003 Standard Edition

  • Windows 2003 Enterprise Edition

  • Windows 2003 Datacenter Edition SP1

  • Windows 2003 SBS Edition

• The following versions of Windows are supported for bootable CD disaster recovery:

  • Windows 2000 Professional Edition

  • Windows 2000 Server Edition

  • Windows 2000 Advanced Server Edition

  • Windows XP Professional Edition

  • Windows 2003 Web Edition

  • Windows 2003 Standard Edition

  • Windows 2003 Enterprise Edition

  • Windows 2003 SBS Edition

Note: Windows XP and Windows 2003 disaster recovery are supported with the Microsoft Windows CD.

The version of Windows you use to generate the boot media should be the version of Windows installed on your machine.

The Disaster Recovery Option is not supported on 64-bit machines.

3.14 Image Option

You can install BrightStor® ARCserve® Backup Image Option on Windows 2000 or Windows 2003.

3.15 NDMP NAS Option

The following section provides the minimum system requirements for the BrightStor® ARCserve® Backup NDMP NAS Option.

To use the NDMP NAS Option, you must meet the following requirements:

• Operating System: Windows 2000 or Windows 2003

• Memory: Minimum 128MB RAM

• Disk Space: Minimum 95 MB

In addition to these requirements, 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 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.16 Tape and Optical Library Option

BrightStor ARCserve Backup for Windows must be installed before you install the BrightStor® ARCserve® Backup Tape and Optical Library Option.

The minimum platform requirements for the Tape Library Option are as follows:

• Windows 2000

• Windows XP Professional

• Windows 2003

The minimum platform requirements for the Optical Library Option are as follows:

• Windows 2000

• Windows 2003

3.17 Serverless Backup Option

You must install the following applications before installing the BrightStor® ARCserve® Backup Serverless Backup Option:

• BrightStor ARCserve Backup for Windows

• Tape Library Option

• Storage Area Network (SAN) Option

You can install the Serverless Backup Option on Windows 2000 or Windows 2003.

3.18 Tape RAID Option

BrightStor ARCserve Backup for Windows must be installed before installing the BrightStor® ARCserve® Backup Tape RAID Option.

You can install the Tape RAID Option on Windows 2000 or Windows 2003.

3.19 Storage Area Network (SAN) Option

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

• BrightStor ARCserve Backup for Windows

• Tape Library Option for Windows

You can install the Storage Area Network (SAN) Option on the following Windows platforms:

• Windows 2000

• Windows 2003

3.20 Enterprise Option for StorageTek ACSLS

The BrightStor® ARCserve® Backup Enterprise Option for StorageTek ACSLS requires, at minimum, the StorageTek ACSLS Library Attach (LibAttach) software version 1.2.

The option is supported on Windows 2000 and Windows 2003.

3.21 Enterprise Option for IBM 3494

The BrightStor® ARCserve® Backup Enterprise Option for IBM 3494 requires the IBM Library Manager Control service version 5.4.8.

The option is supported on Windows 2000 and Windows 2003.

3.22 Enterprise Option for SAP R/3 for Oracle

The BrightStor® ARCserve® Backup Enterprise Option for SAP R/3 for Oracle requires one of the following versions of Oracle Server:

• Oracle 8, Oracle 8i

• Oracle 9, Oracle 9i

SAPDBA should be installed on the same server to use the agent BACKINT option.

SAP R/3 for Windows version 4.6, 4.7, 6.2, or 6.4 is also required.

The option is supported on 64-bit editions (IA-64) of Windows 2003 Service Pack 1 and of Oracle 9i in this release. However, the Agent for Oracle is not supported with 64-bit editions of Oracle. Therefore, only those components of the Enterprise Option for SAP R/3 for Oracle which are not part of the Agent for Oracle are enabled on 64-bit editions of Windows. During installation (and when you run it from the Start menu) an alternate dialog appears, rather than the standard Oracle Agent Account Configuration, which requests only the information needed to perform backup and restore operations using the BR*Tools provided by SAP.

Additionally, the Client Agent for Windows does not obtain an Excluded Files List from Oracle databases under this configuration. File system backups performed through the Client Agent for Windows may try to back up Oracle database files, but the Oracle data files in those backups do not represent a consistent copy of the database unless they have been taken when the Oracle database is offline.

3.23 Enterprise Option for Advantage Ingres

The following section provides the minimum system requirements for the BrightStor® ARCserve® Backup Enterprise Option for Advantage™ Ingres®:

• Microsoft Windows NT 4.0 Service Pack 6a

• Microsoft Windows 2000 Service Pack 1 or Service Pack 2

• Microsoft Windows XP or Windows 2003

• Advantage Ingres Database Server 2.0, 2.5, 2.6 SP2, or 3.0

Before using the option, ensure that the following privileges are assigned to the Windows user who owns the Advantage Ingres installation (for version 2.0, 2.5, or 2.6 SP2, this user is ingres; for version 3.0, it can be any user):

• Access this computer from network

• Act as part of the operating system

• Logon as a service

• Replace a process level token

If your Windows system is a workgroup member, perform the privilege verification and updates in Local Security Policy. If your Windows system is a primary or secondary domain controller, perform the privilege verification and updates in Domain Controller Security Policy. If your Windows system is a domain member, perform the privilege verification and updates in Domain Security Policy.

3.24 Enterprise Option for VSS Hardware Snap-Shot

The following section provides the minimum systems requirements for the BrightStor® ARCserve® Backup Enterprise Option for VSS Hardware Snap-Shot:

• On the Production Server

  • Microsoft Windows Server 2003 Enterprise Edition or Datacenter Edition

  • Microsoft Exchange Server 2003 Service Pack 1 (if Microsoft Exchange 2003 Server is installed)

  • Microsoft SQL Server 2000 Service Pack 3a (if Microsoft SQL 2000 Server is installed)

  • BrightStor ARCserve Backup Client Agent for Windows r11.5

  • BrightStor ARCserve Backup Enterprise Option for VSS Software Snap-Shot

  • VSS Hardware Provider for your disk array, obtained from your disk array vendor

• On the Backup Server

  • Microsoft Windows Server 2003 Enterprise Edition or Datacenter Edition

  • Microsoft Exchange System Management Tools (if you are using the option to protect Microsoft Exchange 2003 Server on the Production Server)

  • Microsoft Exchange Server 2003 Service Pack 1 (if Microsoft Exchange Server 2003 Service Pack 1 is installed on the Production Server)

  • BrightStor ARCserve Backup for Windows r11.5

  • BrightStor ARCserve Backup for Windows r11.5 Enterprise Module

  • License for BrightStor ARCserve Backup Enterprise Option for VSS Hardware Snap-Shot

  • VSS Hardware Provider for your disk array, obtained from your disk array vendor

3.25 Client for VSS Software Snap-Shot

The following versions of Windows are supported for BrightStor® ARCserve® Backup Client for VSS Software Snap-Shot:

• Microsoft Windows XP Professional (BrightStor ARCserve Backup does not support VSS Writers under Windows XP Professional)

• Windows Server 2003

To use the Client for VSS Software Snap-Shot, you must have created at least one NTFS volume.

If you are using VSS with Microsoft Exchange Server 2003, you must have installed Microsoft Exchange Server 2003 Service Pack 1 on both the Production Server and the Backup Server (for transportable snap-shot).

4.0 Installation Considerations

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

4.1 BrightStor ARCserve Backup Base Product

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

• BrightStor ARCserve Backup installs its services under the Local System Account. By default, the option Allow service to interact with desktop is not selected.

• To install BrightStor ARCserve Backup, you must log in to 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.

• For successful integration with this release of BrightStor ARCserve Backup, you must use BrightStor® ARCserve® Backup for Laptops & Desktops r11.1 SP1.

• If you are using BrightStor® High Availability (formerly SurviveIT^™2000), and BrightStor ARCserve Backup, the BrightStor High Availability manager must be installed before you install BrightStor ARCserve Backup. If BrightStor ARCserve Backup is already installed, contact Computer Associates Customer Support.

• If you are using BrightStor High Availability, you must ensure that you applied the latest patches for BrightStor High Availability before installing BrightStor ARCserve Backup.

• If you are installing BrightStor ARCserve Backup on a system where BrightStor High Availability is installed and running, you must stop all replication tasks before restarting your system to allow BrightStor ARCserve Backup to update shared files. Because of this requirement, you should be aware that your system is unprotected by BrightStor High Availability while it is restarting.

• If you are installing BrightStor ARCserve Backup with a Microsoft SQL Server database, you must ensure that you have upgraded to the correct version of the ODBC driver:

  1. Change the ODBC Network Libraries setting to TCP/IP, if necessary.

  2. Run SetupSQL.exe from BAB_HOME, or install Microsoft SQL 2000 or Microsoft SQL 7.0 server or client.

  3. Enter Microsoft SQL security, or upgrade your ODBC driver from the web site, or install Microsoft SQL 2000 7.0 server or client.

• If you are installing BrightStor ARCserve Backup agents on a machine where eTrust® InoculateIT® or eTrust® Antivirus is running, the following driver update must be applied to both the BrightStor 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.

• If you are upgrading to this release, the iSponsor cannot immediately communicate with BrightStor ARCserve Backup due to the change in the way in which equivalences are created. To allow the iSponsor to communicate with BrightStor ARCserve Backup, execute the following command

  BAB_HOME\Authsetup.exe /p <caroot_password>

  This command creates the equivalence for the BrightStor ARCserve Backup System account to allow the iSponsor to work correctly.

4.2 Enterprise Module

The following section provides information about installation prerequisites, configurations, and issues to consider before installing the BrightStor® ARCserve® Backup Enterprise Module:

• The Enterprise Module must be installed to access BrightStor ARCserve Backup advanced features and all the Enterprise Options except the Enterprise Option for Advantage Ingres, the Enterprise Option for SAP/R3 for Oracle, and the Enterprise Option for VSS Hardware Snap-Shot.

4.3 Client Agents

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

• Remote installation and response file installation of the Client Agents for Windows 98 and Windows Me are not supported in the Master Setup.

4.4 Agent for Lotus Domino

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

• To upgrade from BrightStor® ARCserve® 2000 to BrightStor ARCserve Backup, you must first uninstall the BrightStor ARCserve 2000 agent. However, if the BrightStor ARCserve 2000 agent is for Lotus Notes for Windows (BAOF Version), you must first uninstall the BrightStor ARCserve 2000 agent, and then uninstall the embedded BAOF manually using the following procedure:

  1. Uninstall the BrightStor ARCserve 2000 Agent for Lotus Notes for Windows (BAOF Version).

  2. Insert the original BrightStor ARCserve 2000 CD, or ensure that an image of the CD is available.

  3. From the Windows command prompt, run the following command:

     msiexec.exe /x FULL PATH TO BAOFNTAG.MSI PRODUCTS=2
     

     For example, where the original CD is used and inserted in drive F, enter the following at the prompt:

     msiexec.exe /x f:\IntelNT\Notes.DBA\baofntag.msi PRODUCTS=2
     

4.5 Agent for Microsoft SharePoint

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

• BrightStor 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 BrightStor ARCserve Backup is supported.

• When upgrading from a beta version of BrightStor ARCserve Backup r11.5, use the Agent for Microsoft SharePoint Configuration Wizard to upgrade all BrightStor ARCserve Backup SharePoint agents, including the Router Agent, External Data Agent, and Embedded SQL Agent.

• To install and configure the Agent for Microsoft SharePoint in an environment with a firewall provided by Windows 2003 Server 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. Configure the firewall for the BrightStor ARCserve Backup base product using the instructions in the section Known Issues for the Base Product in this Readme document.

  2. Ensure that the firewalls on any remote computers hosting the SharePoint installation are configured to allow exceptions.

  3. Install the Agent for Microsoft SharePoint from the BrightStor ARCserve Backup installation CD. The Agent for Microsoft SharePoint Configuration wizard starts automatically.

  4. Complete the Server Selection information and click Next. Although the SharePoint Router Agent is installed, you 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 correctly or install a router by selecting install.
     

  5. 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\BrightStor\UniAgent
     

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

  7. 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 Window Firewall exception list on those machines.

  8. If you have the BrightStor External Data Agent installed on any computers, add the UnivAgent.exe executable to the Windows Firewall exception list. This executable is found in the following directory

     C:\Program Files\CA\SharedComponents\BrightStor\UniAgent
     

  9. 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\BrightStor\DBACommon
       

  The Agent for Microsoft SharePoint can now be used successfully from the BrightStor ARCserve Backup server.

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

  Note: Windows Small Business Server 2003 Premium Edition includes Microsoft SQL Server 2000, Service Pack 3.

4.7 Agent for Open Files

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.

4.8 Disaster Recovery Option

The following section provides information about installation prerequisites, configurations, and issues to consider before installing the Disaster Recovery Option:

• When upgrading to BrightStor ARCserve Backup r11.5, you should recreate the machine-specific disk for all protected machines. This ensures that you are using the option's latest executables. For more information about how to update machine-specific disks, see the Disaster Recovery Option Guide.

• When you upgrade to BrightStor ARCserve Backup r11.5, a directory, called OldDR, is created to store information from old backup operations. If you want to create a machine-specific disk from an old backup, you must do one of the following:

  • Rename the OldDR directory to DR

  • Copy the machine_name directories to the DR directory and create the machine-specific disks.

5.0 General Considerations

The following section provides general information to consider when using BrightStor 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.

• In the BrightStor® ARCserve® Backup Unicenter® Integration Option, the Unicenter® component previously called Workload Management is now the Job Management Option in Unicenter Network and Systems Management r11.

• The following files are not backed up during backup jobs:
  • DOS System Files

    • The following Windows Files:

      • 386SPART.PAR
      • 386SPART.TMP
      • SPART.PAR
      • WIN386.SWP

    • DoubleSpace Files (DBLSPACE with any extension)
    • DriveSpace Files (DRVSPACE with any extension)
    • Stacker Files (STACVOL.DSK)
    • BTrieve delta files

  • The following Win32System Files:

• PAGEFILE.SYS
• NETLOGON.CHG
• NTUSER.DAT.LOG
• CPL.CFG
• EA DATA. SF

• The following Registry Keys:

  • \\HKEY_LOCAL_MACHINE\SYSTEM\CLONE
  • \\HKEY_LOCAL_MACHINE\HARDWARE

• Registry files with the extensions *.ALT and *.LOG
• Cluster installation directory files (typically, the WINNT\cluster folder), files with no extensions, and files with the extension *.LOG
• \RECYCLER folder
• Folder for file system devices

• You can manage BrightStor ARCserve Backup for NetWare r11.1 with the BrightStor ARCserve Backup for Windows r11.5 Manager.

6.0 Known Issues

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

6.1 Portmapper Conflicts with BrightStor ARCserve Backup

If BrightStor ARCserve Backup detects port 111 conflicts, indicating that it is using the same port number for the CA Remote Procedure Call server service as a previously installed portmapper, BrightStor 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 Remote Procedure Call server service to Manual. If you have installed BrightStor ARCserve Backup in a Microsoft Cluster Services environment, change the Automatic status of the CA Remote Procedure Call server service to Disabled. This enables you to avoid similar port conflicts after the system has completed the boot process.

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

1. Create the DWORD DelayedRegistration in the following:

   HKEY_LOCAL_MACHINE\Software\ComputerAssociates\BrightStor ARCserve Backup\Base\Portmap
   

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

6.2 Known Issues for the Base Product

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

• If you select a non-default IP address for a client agent node, 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, launch Discovery Environment configuration (dsconfig.exe).

  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 BrightStor ARCserve Backup from initializing correctly unless you update the Emulex driver.

• If you upgrade your Windows XP system with Windows XP Service Pack 2, the upgrade to Service Pack 2 enables the firewall and blocks all ports by default. You must perform one of the following procedures to use BrightStor ARCserve Backup with Windows XP Service Pack 2.

  Note: These methods can be applied to Windows 2003 Server systems with Service Pack 1 and the firewall enabled.

  Method 1 (recommended):

  1. In the Start menu, click Run, enter gpedit.msc, and press Enter.

     Note: This step does not apply to Windows 2003 Server SP1.

  2. The Group Policy configuration GUI appears. In the Group Policy Configuration GUI, select Local Computer Policy, Computer Configuration, Windows Setting, Security Setting, Local Policy, Security Option.

     Note: This step does not apply to Windows 2003 Server SP1.

  3. Change the setting Network access:Sharing and security model for local accounts to Classic - local users authenticate as themselves.

     Note: This step does not apply to Windows 2003 Server SP1.

  4. The following key RPC and subkey RestrictRemoteClients must be created manually and the value set to 0:

     [DWORD]HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\RPC\RestrictRemoteClients
     

     Note: This step does not apply to Windows 2003 Server SP1.

  5. Access the Security Center (on Windows XP SP2) or Windows Firewall (on Windows 2003 Server SP1) and enable the firewall.

  6. Add the following executables (if applicable) to the Security Center exception list (these can be found in the CA BrightStor ARCserve home directory):

     • caauthd.exe

     • cadiscovd.exe

     • caloggerd.exe

     • casdscsvc.exe

     • caserved.exe

     • casmrtbk.exe

     • catirpc.exe

     • dbeng.exe

     • jobeng.exe

     • ldbserver.exe

     • lqserver.exe

     • mediasvr.exe

     • msgeng.exe

     • tapeeng.exe

     • univagent.exe (if the Client Agent is installed)

     • carunjob.exe

     • dbasvr.exe (if any database agents are installed)

     • dbasqlr.exe (if the Agent for Microsoft SQL Server is installed)

     • dbaexchr.exe (if the Agent for Microsoft Exchange Server is installed)

  7. If you have the Client Agent or any database agent installed, on the Exceptions tab, select File and Printer Sharing.

  8. Restart the Windows XP Service Pack 2 machine and start BrightStor ARCserve Backup services.

  Method 2:

  1. In the Start menu, click Run, enter gpedit.msc, and press Enter.

  2. The Group Policy configuration GUI appears. In the Group Policy Configuration GUI, select Local Computer Policy, Computer Configuration, Windows Setting, Security Setting, Local Policy, Security Option.

  3. Change the setting Network access:Sharing and security model for local accounts to Classic - local users authenticate as themselves.

     Note: This is the default setting on Windows 2003 Server SP1.

  4. The following key RPC and subkey RestrictRemoteClients must be created manually and the value set to 0:

     HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\RPC\RestrictRemoteClients
     

  5. Access the Security Center and turn the firewall off.

  6. Restart the Windows XP Service Pack 2 machine and start the BrightStor ARCserve Backup services.

• If you use the Master Setup to install BrightStor 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.

• If you enable both Success and Failure for Audit object access under Local Security Policy, Local Policies, Local Audit Policy, you may receive multiple Success Audit messages under Security Events in the Event Viewer. To avoid receiving multiple Success Audit messages, perform the following procedure:

  1. Create a key called MessageEngine Under the following registry key:

  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Admin

  2. Create a DWORD value called Impersonate under the following key and set it to 0:

  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Admin\MessageEngine

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

• If you import a DLTWORM-capable media into a library which has not converted to WORM yet, the Quick erase and Convert to WORM media option is disabled. You must perform a full inventory of tapes to enable this option.

• If you use WORM media as the destination for any cross-platform jobs involving the BrightStor ARCserve Backup for UNIX Agent for Oracle or the BrightStor ARCserve Backup for Linux Agent for Oracle, these agents may not behave as expected. Child jobs are submitted by the agent, and, because WORM media is not supported on the UNIX or Linux agents, these child jobs may use destinations other than the WORM media.

• When configuring the primary and secondary servers in a domain, the configuration must be same on all machines in the domain. You must define the secondary name when you install the primary to allow the secondary server information to be validated for security reasons. You can reconfigure the secondary name using the command line utility ca_conf.exe or edit the config\discovery.cfg file in the BrightStor ARCserve Backup installation folder.

• 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\BrightStor and the PortsConfig.cfg file for the 32-bit components is in C:\Program Files (x86)\CA\SharedComponents\BrightStor. 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.

• Media checks using the Preflight Check are not supported for Disk Staging jobs.

• In database agent backup operations using the Staging option, the backup method is set as a local option but copy and purge policies are set as global options.

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

• When you upgrade from older versions of BrightStor ARCserve Backup, tapes with lowercase letters in the tape names are listed in the Session View of the Restore Manager using all uppercase letters. In addition, 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 at least once in lowercase letters.

  2. Delete the uppercase entry. The Restore Manager displays the tape name and details correctly.

• During uninstallation of BrightStor ARCserve Backup from non-primary cluster nodes, perform the following procedure:

  1. In the base home directory, run the following command to unregister the ashell.dll file from non-primary cluster nodes:

  RegSvr32 /u (original full installation path of ashell.dll) 

  2. Log off from all login sessions, both local and remote (you do not have to reboot).
  3. Uninstall BrightStor ARCserve Backup from the primary cluster node.
  4. Log back in to each non-primary cluster node, copy the required modules for uninstallation, and continue with the uninstallation procedure.

• When you uninstall BrightStor ARCserve Backup from secondary cluster nodes, some files may be left in the BrightStor ARCserve Backup home directory and some registry keys may be left in the following:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs

You must remove the files and clean up the registry manually.

• If you use the ca_conf command line utility to change the BrightStor ARCserve Backup domain name to a new domain name, you will encounter the following problems:

  • The caroot password is reset to blank
  • Equivalences are reset for all users
  • The caroot password cannot be reset using the bconfig.exe utility

To correct these problems, run the ca_conf utility and perform the following procedure:

1. Set the password for the caroot user using the authsetup command line utility with the following syntax:

authsetup /p <new carootPassword> 

This command also creates equivalence for the user currently logged into BrightStor ARCserve Backup.

2. Recreate the equivalences for all users manually.

For more information, see the ca_auth Command section of the Using Command Line Utilities appendix of the Administrator Guide.

6.3 Known Issues for the Client Agent

The following issues related to the Client Agent 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\BrightStor and the PortsConfig.cfg file for the 32-bit components is in C:\Program Files (x86)\CA\SharedComponents\BrightStor. 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.

• You cannot use the Client Agent for NetWare included in this release with the BrightStor ARCserve Backup for NetWare r11.1 Manager. The Client Agent for NetWare included in this release requires the BrightStor ARCserve Backup for Windows r11.5 Manager GUI.

• When running the Client Agent for NetWare on NetWare 4.2, the agent requires the clibaux.nlm enhancement module provided by Novell (refer to Novell Technical Information Document 2955000).

• 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 BrightStor 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.

6.4 Known Issues for the Agent for IBM Informix

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

• Your Informix server should be installed on a Windows NT 4.0 or Windows 2000 machine in a Windows Domain. If you install Informix on a standalone Windows NT 4.0 server or a Windows NT workstation, the Informix backup utility does not allow you to back up your database to a remote BrightStor ARCserve Backup server. You must use the Backup and Restore Managers from BrightStor ARCserve Backup to submit the backup and restore jobs.

• If you use the Informix Backup and Restore utility, rather than the Backup Manager, you must define security information using the Informix Agent Configuration utility dbacfg before submitting any backup or restore jobs.

• When using remote BrightStor ARCserve Backup to back up or restore Informix server, the real backup and restore jobs created by the Informix Server are scheduled on the BrightStor ARCserve Backup server based on the local time from the Informix server. Therefore, time differences between the BrightStor 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.

• The agent supports only the Restore by Tree method in the Restore Manager.

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

6.5 Known Issues for the Agent for Microsoft SharePoint

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

• If a Microsoft SQL database is backed up using both the Agent for Microsoft SQL Server 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 SQL Server.

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

• The username entered in the Agent for Microsoft SharePoint Configuration Wizard must have administrative access to all machines in the SharePoint server farm.

• Performance may be slowed when backing up or restoring search indexes, as these operations may consume 100% of your CPU resources if the SharePoint server used satisfies only the minimum hardware requirements for Microsoft SharePoint Portal Server. See the Microsoft SharePoint Portal Server Administrator's Guide for more information about hardware requirements.

6.6 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 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 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\BrightStor and the PortsConfig.cfg file for the 32-bit components is in C:\Program Files (x86)\CA\SharedComponents\BrightStor. 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.

• 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, BrightStor 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.

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

• When backing up or restoring a remote SQL database using the TCP/IP protocol, the TCPtimeout parameter defines how long the BrightStor ARCserve Backup Server waits for a response from the agent. This prevents problems such as network errors from causing jobs to wait forever for a response that might not come. Once this time-out period is expired, the waiting job fails with a network error.

  However, when a large remote SQL database is restored, particularly when it involves creation of SQL data files, such as when you restore to a different SQL Server, the agent for SQL cannot reply immediately because SQL Server takes some time to create the files, and the agent must wait for this to complete before it can respond.

  The default timeout value is set to 1200 seconds (20 minutes). This should be extended when you restore a large SQL database involving large data file creations. A large SQL database (60 GB) might require the value to be as long as 7200 seconds (120 minutes). In general, the default value (1200) can handle most SQL database restores, as well as network errors. However, if you have a network error on a large SQL database restore operation, you should increase the time-out value. After the restore is done, reset the value to 1200.

  The SQL Agent TCPtimeout key can be found on the BrightStor ARCserve Backup Server machine under:

  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Common\DBAgentsettings

• The Microsoft Windows 2003 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 BrightStor 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, in the Backup Manager, right-click the MSDE database, select Remote Protocol, and choose Named Pipes.

  If BrightStor ARCserve Backup and the MSDE application are installed on the same computer, you must direct BrightStor 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\BrightStor ARCserve Backup\Base\Task\Common\DBAgentsettings
     

  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.

• Backup with Compare and Backup with Scan Tape are not performed on agent sessions.

• If using the BrightStor 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 BrightStor ARCserve Backup manager and the BrightStor ARCserve Backup Client Agent must be stopped before uninstalling and reinstalling BrightStor 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 Backup Agent Remote Service.

• If you are performing a remote backup, File and Printer Sharing for Microsoft Networks must be enabled 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.

• If you are using the current version of BrightStor ARCserve Backup and BrightStor ARCserve Backup Agent for Microsoft SQL Server to restore a backup made using BrightStor ARCserve 2000 or an older version of BrightStor ARCserve Backup, and you are using the Named Pipes protocol, perform the following procedure on the computer running the BrightStor ARCserve Backup Server:

  1. Open the Registry Editor and select the key

     KEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\
     BrightStor ARCserve

     Backup\Base\Task\Common\DBAgentsSettings

  2. In the Edit menu, select New> DWORD Value. Set the name of this value to SQLProtocol and its value to 0.

  3. Resubmit the restore job.

  4. After all restore operations using these backups are completed, return to the Registry Editor and delete the SQLProtocol value.

• When using Multistriping to back up databases from Microsoft SQL Server 7.0, the child jobs cannot obtain size estimates. While you can view progress in terms of the amount of data backed up, there is no accurate display of the total size of the database, nor of the percentage of the backup completed.

• If you are using an agent from a version of BrightStor ARCserve Backup prior to r11 or from a version of BrightStor Enterprise Backup prior to Version 10.5 Service Pack 1, incremental backup jobs cannot determine if a transaction log backup is permitted. Therefore, differential backups are performed.

• 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 local or TCP-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 E8604 (“Failed to Start Backup”), or E8605 (“Failed to Start Restore”). 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 reregister the Virtual Devices component and re-enable backup operations:

  regsvr32 sqlvdi.dll 

6.7 Known Issues for Agent for Open Files

The following issues related 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 the 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 provide 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.

• When running the Agent for Open Files Console on Windows 98 and Windows Me, you cannot access the Status, Logfile, or Configure dialogs for an IPX-only NetWare server, even though the agent may be indicated as active on that server. If you try to access these dialogs, you receive an Error Message stating that the agent is not available.

6.8 Known Issues for the Agent for Sybase

The following issues related 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" 

6.9 Known Issues for the Disaster Recovery Option

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

• The option does not support local backup server recovery using file system devices located on another remote machine. In addition, support for using file system devices on local disks is very restricted. For more information, see the Disaster Recovery Option Guide.

• When you run a remote recovery and the base is Windows XP with SP2, you must use different configurations depending on the version of BrightStor ARCserve Backup used to create your full backup:

  • If your full backup was made using BrightStor 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 BrightStor ARCserve Backup r11.5, on the base Windows XP SP2 machine, set the following registry key value to 0:

    HKEY _LOCAL_MACHINE\Software\Polices\Microsoft\Windows NT\RPC\RestrictRemoteClients
    

    You do not need to change the Share and security model for local account setting.

6.10 Known Issues for the NDMP NAS Option

The following issues related 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 BrightStor Enterprise Backup 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\BrightStor ARCserve Backup\NASAgent\Parameters\Use16kBlockonRestore
  

• The option does not support Job failover.

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

• The Backup filter is supported at the volume and folder level.

• 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 distributed servers.

• BrightStor ARCserve Backup does not support copying NAS sessions using tapecopy.

• 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 BrightStor 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.

6.11 Known Issues for the Optical Library Option

The following issues relating to the Optical 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 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.

6.12 Known Issues for the SAN Option

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

• In cross-platform SAN environments, UNIX and NetWare do not support WORM media.

6.13 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\BrightStor ARCserve Backup\Base\TapeEngine\CONFIG\ShareWithAS400
  

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

1. Find the type of IBM drive installed:

   • Ultrium (Windows 2000): ibmlto

   • Magstar (Windows 2000): magstar

   • Ultrium and Magstar (Windows 2003): ibmrmsst or ibmtp2k3

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

3. Create the DWORD value DisableReserveUponOpen and set it to 1.

4. Exit regedit and restart your computer.

Note: For information on installing SAN distributed servers, see the Storage Area Network (SAN) Option Guide.

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

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

• The following conditions apply if you are upgrading from BrightStor ARCserve Backup 2000 to BrightStor ARCserve Backup for Windows r11.5:

  • You must upgrade the option and the base product during the same installation session.

  • If the option is installed on a remote server, use the following procedure to reconfigure the option installation on the remote server:

    1. From the remote server, select Start, select Programs, Computer Associates, BrightStor ARCserve Backup Agents, and SAP R/3 Oracle Agent BACKINT Configuration.

    2. On the Security Information tab, reenter the security information for the remote server.

    3. Repeat the previous step as necessary, for all backup or restore jobs.

• 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 options apply to Windows only.

• Before you shut down the Oracle Server in normal mode, you should shut down the local BrightStor ARCserve Backup Manager and the BrightStor 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 you to specify the Use Computer Name Resolution option or the IP address to include the databases when backing up the entire machine.

• 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, if BrightStor ARCserve Backup is not installed on the local machine, BACKINT restores these objects to the remote server on which BrightStor ARCserve Backup is located.

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

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

• The option only supports the BACKINT command interface.

6.16 Known Issues for the Client for VSS Software Snap-shot

The following issues related to the Client for VSS Software Snap-shot are known to exist in this release:

• Incremental and differential backups are supported for the Exchange Writer only.

6.17 Known Issues for BrightStor Portal Integration

The following section provides information regarding issues relating to the integration of BrightStor ARCserve Backup r11.5 with BrightStor® Portal r11.1 known to exist in this release:

• If you plan to use the BrightStor Portal to manage and report on BrightStor ARCserve Backup, you must ensure that you have applied the latest patches for BrightStor Portal r11.1. These patches are available at http://supportconnect.ca.com. For more information, see the iGateway and iSponsor readme documentation included with this release.

6.18 Known Issues for Documentation

The following section provides information regarding issues relating to the documentation for BrightStor ARCserve Backup known to exist in this release:

• You may experience problems when using the browse buttons to move from topic to topic in the Windows Online Help System.

• When viewing a Windows Online Help System, if you select Home from the Options toolbar drop-down menu, the message "The page cannot be displayed" appears.  To display the Home page, you must navigate the Contents pane and select the first topic in the help system.

7.0 Documentation Changes

Updated guides will be available at http://ca.com/support.

The following section provides information about items that have not yet been changed in the product documentation, but that affect the information in that documentation:

• The Release Summary should contain the following test fixes:

  [T2D2395] [T352124]: BrightStor ARCserve Backup has been enhanced to ensure that the DHCP database is backed up by local backup jobs when run on a Windows 2003 server, or when a local backup job includes a remote Windows 2003 server. In addition, the activity log no longer reports that the dhcp.mdb file is not found.

• The Administrator Guide states that you can define staging policies that direct BrightStor ARCserve Backup to create a makeup job on Hold or back up directly to tape if an exceeds threshold condition occurs. This statement should indicate that you can define staging policies that direct BrightStor ARCserve Backup to create a makeup job to back up directly to tape if an exceeds threshold condition occurs or to create a makeup job on Hold if a data migration failure occurs.

• In the appendix Supporting NEC CLUSTERPRO/ExpressCluster Clusters, the Administrator Guide states that, if you are installing BrightStor ARCserve Backup in an Active/Passive cluster set that acts as the primary SAN server, you should add the following registry keys after you have assigned SAN distributed servers to the primary SAN server:

  SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\ELODistributedServers

  SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\ProductsConfigInfo

  This statement should indicate that you should add these registry keys if you are installing BrightStor ARCserve Backup in an Active/Passive cluster set that acts as either a primary or distributed SAN server.

• In the Advantage Ingres Server Configuration section of the Enterprise Option for Advantage Ingres, the guide states the following:

  To allow the option to function properly, you must assign the Advantage Ingres user the following user rights:

  • Act as part of the operating system
  • Replace a process level token

  This section should state the following:

  To allow the option to function properly, you must assign the Advantage Ingres user the following user rights:

  • Access this computer from network
  • Act as part of the operating system
  • Logon as a service
  • Replace a process level token

  After you assign the rights the agent requires, log off and log in again to Windows to activate the rights.

8.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 BrightStor ARCserve Backup for Windows r11.5 has been internationalized and translated into the following languages, in addition to the English release:

• Brazilian-Portuguese

• French

• German

• Italian

• Japanese

• Korean

• Simplified Chinese

• Spanish

• Traditional Chinese

If you run this product on a language environment not included in the list, you may experience problems.

9.0 Documentation

Each guide in a documentation set has a unique Document Identification (DID) designation that appears on the title page of the guide. The DID uses six characters to identify the guide, a hyphen, then two characters at the end to identify the edition and the language in which it is written. For example, D01167-1E identifies the first edition of the English version of the BrightStor ARCserve Backup for Windows Release Summary. When the second edition of this guide is published, the DID is incremented to D01167-2E.

The DID appears on the title page of PDF files. The DID without the hyphen is also used for the eight-character file name for PDF files on product media and on SupportConnect.

The DIDs and file names for this product's guides are:

Guide Name	DID	Filename
BrightStor® ARCserve® Backup for Windows Release Summary	D01167-1E	D011671E.PDF
BrightStor® ARCserve® Backup for Windows Getting Started	D01168-1E	D011681E.PDF
BrightStor® ARCserve® Backup for Windows Administrator Guide	D01169-1E	D011691E.PDF
BrightStor® ARCserve® Backup Client Agents Guide	D01165-1E	D011651E.PDF
BrightStor® ARCserve® Backup for Windows Agent for IBM Informix Guide	D01170-1E	D011701E.PDF
BrightStor® ARCserve® Backup for Windows Agent for Lotus Domino Guide	D01171-1E	D011711E.PDF
BrightStor® ARCserve® Backup for Windows Agent for Microsoft Exchange Guide	D01172-1E	D011721E.PDF
BrightStor® ARCserve® Backup for Windows Agent for Microsoft SharePoint Guide	D01184-1E	D011841E.PDF
BrightStor® ARCserve® Backup for Windows Agent for Microsoft SQL Server Guide	D01173-1E	D011731E.PDF
BrightStor® ARCserve® Backup for Windows Agent for Open Files Guide	D01174-1E	D011741E.PDF
BrightStor® ARCserve® Backup for Windows Agent for Oracle Guide	D01175-1E	D011751E.PDF
BrightStor® ARCserve® Backup for Windows Agent for Sybase Guide	D01176-1E	D011761E.PDF
BrightStor® ARCserve® Backup for Windows Disaster Recovery Option Guide	D01178-1E	D011781E.PDF
BrightStor® ARCserve® Backup for Windows Image Option Guide	D01179-1E	D011791E.PDF
BrightStor® ARCserve® Backup for Windows NDMP NAS Option Guide	D01180-1E	D011801E.PDF
BrightStor® ARCserve® Backup for Windows Tape and Optical Library Option Guide	D01181-1E	D011811E.PDF
BrightStor® ARCserve® Backup for Windows Serverless Backup Option Guide	D01182-1E	D011821E.PDF
BrightStor® ARCserve® Backup for Windows Tape RAID Option Guide	D01183-1E	D011831E.PDF
BrightStor® ARCserve® Backup Storage Area Network (SAN) Option Guide	D01166-1E	D011661E.PDF
BrightStor® ARCserve® Backup for Windows Enterprise Option for StorageTek ACSLS Guide	D01185-1E	D011851E.PDF
BrightStor® ARCserve® Backup for Windows Enterprise Option for IBM 3494 Guide	D01186-1E	D011861E.PDF
BrightStor® ARCserve® Backup for Windows Enterprise Option for SAP R/3 for Oracle Guide	D01187-1E	D011871E.PDF
BrightStor® ARCserve® Backup for Windows Enterprise Option for Advantage™ Ingres® Guide	D01188-1E	D011881E.PDF
BrightStor® ARCserve® Backup for Windows Enterprise Option for Microsoft SQL Using HDS Snap-Shot Guide	D01189-1E	D011891E.PDF
BrightStor® ARCserve® Backup for Windows Enterprise Option for Microsoft SQL Using HP-XP Snap-Shot Guide	D01190-1E	D011901E.PDF
BrightStor® ARCserve® Backup for Windows Microsoft Volume Shadow Copy Service Guide	D01191-1E	D011911E.PDF

The DID for this Readme file appears under the Readme title; the DID without the hyphen is used for the Readme file name on SupportConnect.

10.0 Contact Customer Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Customer Support at http://ca.com/support.