CA ARCserve® Backup r12 SP1 Readme
1.0 Welcome
2.0 Operating System Support
3.0 System Requirements
3.1 System Requirements for the CA ARCserve Backup Base Product
3.2 System Requirements for CA ARCserve Backup and <CAWAN> Integration
3.3 System Requirements for the CA ARCserve Backup Client Agents
3.4 System Requirements for the Agent for IBM Informix
3.5 System Requirements for the Agent for Lotus Domino
3.6 System Requirements for the Agent for Microsoft Exchange
3.7 System Requirements for the Agent for Microsoft SharePoint
3.8 System Requirements for the Agent for Microsoft SQL Server
3.9 System Requirements for the Agent for Oracle (UNIX/Linux)
3.10 System Requirements for the Agent for Oracle (Windows)
3.11 System Requirements for the Agent for Open Files
3.12 System Requirements for the Agent for Microsoft Data Protection Manager
3.13 System Requirements for the Agent for VMware
3.14 System Requirements for the Agent for Sybase
3.15 System Requirements for the Content Management Option
3.16 System Requirements for the Disaster Recovery Option
3.17 System Requirements for the Enterprise Module
3.18 System Requirements for the Disk to Disk to Tape Option
3.19 System Requirements for the Enterprise Option for IBM 3494
3.20 System Requirements for the Enterprise Option for SAP R/3 for Oracle
3.21 System Requirements for the Enterprise Option for StorageTek ACSLS
3.22 System Requirements for the Image Option
3.23 System Requirements for the NDMP NAS Option
3.24 System Requirements for the Tape Library Option
3.25 System Requirements for the Serverless Backup Option
3.26 System Requirements for the Storage Area Network (SAN) Option
3.27 System Requirements for the CA ARCserve Backup Small Business Server Editions
3.28 System Requirements for the CA ARCserve Backup for Microsoft Windows Essential Business Server
4.0 Installation Considerations
4.1 Installation Considerations for the CA ARCserve Backup Base Product
4.2 Upgrade Considerations for the CA ARCserve Backup Base Product
4.3 Installation Considerations for the Client Agents
4.4 Installation Considerations for the Agent for Microsoft Exchange
4.5 Installation Considerations for the Agent for Microsoft SharePoint 2003
4.6 Installation Considerations for the Agent for Microsoft SharePoint 2007
4.7 Installation Considerations for the Agent for Microsoft SQL Server
4.8 Installation Considerations for the Agent for Open Files
4.9 Installation Considerations for the Enterprise Module
4.10 Installation Considerations for the Media Management Option (MMO)
4.11 Installation Considerations for CA ARCserve Backup for Microsoft Windows Essential Business Server
5.0 General Considerations
6.0 Supported Upgrade Paths
6.1 Backward Compatibility
7.0 Known Issues
7.1 Known Issues for the Base Product
7.2 Known Issues When Upgrading to CA ARCserve Backup
7.3 Known Issues for Integration
7.4 Known Issues for the Client Agents
7.5 Known Issues for the Agent for IBM Informix
7.6 Known Issues for the Agent for Microsoft Data Protection Manager
7.7 Known Issues for the Agent for Microsoft Exchange
7.8 Known Issues for the Agent for Microsoft SharePoint
7.9 Known Issues for the Agent for Microsoft SQL Server
7.10 Known Issues for the Agent for Open Files
7.11 Known Issues for the Agent for Oracle (Windows)
7.12 Known Issues for the Agent for Oracle (UNIX and Linux [RMAN])
7.13 Known Issues for the Agent for Sybase
7.14 Known Issues for the Agent for VMware
7.15 Known Issues for the Disaster Recovery Option
7.16 Known Issues for the Image Option
7.17 Known Issues for the NDMP NAS Option
7.18 Known Issues for the Tape Library Option
7.19 Known Issues for the Storage Area Network (SAN) Option
7.20 Known Issues for the Enterprise Option for AS400
7.21 Known Issues for the Enterprise Option for IBM 3494
7.22 Known Issues for the Agent for Lotus Domino
7.23 Known Issues for the Enterprise Option for SAP R/3 Oracle
7.24 Known Issues for the Enterprise Option for StorageTek ACSLS
7.25 Known Issues for Displaying Non-English Characters
7.26 Known Issues for CA ARCserve Backup for Microsoft Windows Essential Business Server
7.27 Known Issues for CA ARCserve Backup Licensing
7.28 Known Issues for Documentation
7.29 Portmapper Conflicts with CA ARCserve Backup
8.0 Included Fixes
9.0 Security Related Enhancements
10.0 Language Certifications
Welcome to the CA ARCserve Backup Readme. This readme
contains issues and other information discovered after
publication. For a complete list of the known issues for
this release and details about how the features and
enhancements for this release might affect you, see the CA
ARCserve Backup Release Summary.
CA ARCserve Backup supports the following suites:
- CA ARCserve Backup r12 File Server Suite (Base)
- CA ARCserve Backup r12 File Server Suite (Client)
- CA ARCserve Backup r12 Email Suite
- CA ARCserve Backup r12 Database Suite
- CA ARCserve Backup r12 Application Suite
CA ARCserve Backup is supported on the following operating
systems:
Windows Server 2008
Windows Server 2003
- R2 Enterprise Edition (x86, x64) or R2 Service Pack 2
- R2 Standard Edition (x86, x64) or R2 Service Pack 2
- 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
- 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
- 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)
- CA ARCserve Backup Manager Console, CA ARCserve Backup
Agent for Windows, CA ARCserve Backup Agent for Open Files
Windows Essential Business Server Operating System Support
- 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
Support for Guest OS for Virtualization Software
The following sections provide information about the
minimum system requirements for each CA ARCserve Backup
component.
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
- Member Server: 450 MB
CA ARCserve Backup Database
CA ARCserve Backup supports the following applications to
host the CA ARCserve Backup database:
- Microsoft SQL Server 2005 Express 2005 Edition with Service
Pack 2
Note: Microsoft SQL Server 2005 Express 2005 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 or Service
Pack 2
- Microsoft SQL Server 2008
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.
Other Hardware
- DVD-ROM Drive
- Super VGA (1,024 x 768) or higher-resolution video adapter
and monitor
Internet Browser
- Internet Explorer Version 6.0 SP2 or later
Adobe Reader
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
To integrate CA ARCserve Backup with <CAWAN>, you must be
running <CAWAN>, version 4.0, starting with Build 69.
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
The Replica servers are supported on the following
operating systems:
- Microsoft Windows Server 2003 SP1
- Microsoft Windows Server 2003 R2 Enterprise Edition and
Standard Edition SP1 (32-bit and x64)
In addition to the file protection, CA ARCserve Backup and
<CAWAN> integration supports data protection for the
following:
- Microsoft Exchange 2000 Standard SP4
- Microsoft Exchange 2003 Standard SP1 and SP2
- Microsoft Exchange 2007
- 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.
Note: <CAWAN> does not support Microsoft Windows Server
2008.
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.
Hardware Requirements
To install the agents, your system must meet the following
minimum hardware requirements:
- 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 version 4.2 requires a Pentium 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:
- UNIX-based platforms should run CA ARCserve Backup r11.5 SP3
- Linux-based platforms:
- Linux-based platforms should run CA ARCserve Backup r11.5
SP3
- RAM: 128 MB
- Disk Space: 10 MB
To install the Client Agent for Mac OS X, your system must
meet the following minimum hardware requirements:
- RAM: 128 MB
- Disk Space 10 MB
Software Requirements
You can install the CA ARCserve Backup Client Agents on the
following platforms:
- CA ARCserve Backup Client Agent for Windows:
- Microsoft Vista™ (32-bit and x64) at minimum Service Pack 1
(CA ARCserve Backup Manager Console, CA ARCserve Backup
Client Agent for Windows, and CA ARCserve Backup Agent for
Open Files)
- Windows XP Professional 32-bit (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 64-bit (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 (32-bit only)
- Windows Server 2003 Standard Edition (32-bit only)
- Windows Server 2003 Enterprise Edition (32-bit and 64-bit)
- Windows 2000 Professional 32-bit (Service Packs 3 and 4)
- Windows 2000 Server 32-bit (Service Packs 3 and 4)
- Windows 2000 Advanced Server 32-bit (Service Packs 3 and 4)
- Windows 2000 Cluster Server (2 node Advanced Edition)
- Windows 2003 32-bit, x64, and IA64
- Windows Server 2003 R2, 32-bit and IA64
- Windows Server 2003 Cluster 32-bit, x64, and IA64
- Windows 2000 and Windows 2003 Datacenter
- Windows Powered NAS (2000)
- Windows Storage Server 2003
- Windows Server 2008 Enterprise Edition (32-bit, x64, and
IA64)
- Windows Server 2008 Standard Edition (32-bit, x64, and IA64)
- Windows Server 2008 Enterprise Core (32-bit, and x64)
- CA ARCserve Backup Client Agent for NetWare:
- Novell NetWare version 4.2
- Novell NetWare version 5.1
- Novell NetWare version 6.0 or 6.5
- CA ARCserve Backup Client Agent for UNIX:
- Solaris SPARC 7, 8, 9 (x86 32-bit), and 10 SPARC (x86
32-bit and AMD 64)
- IBM AIX 5L v5.2, v5.3, v6.1
- HP-UX PA RISC 11.11, 11.23
- HP-UX Itanium 11.22 and 11.23
- HP Compaq Tru 64 4.0F, 4.0G, 5.0, 5.1, 5.1A, and 5.1B
- FreeBSD versions 4.11, 5.3, and 5.4
- CA ARCserve Backup Client Agent for Linux:
- Red Hat Enterprise Linux 3, 4, and 5 (ES, AS) (x86)
- SUSE Linux Enterprise Server 8, 9 (x86), and 10
- SUSE Standard Server 8
- SUSE Professional 9, 9.1, and 9.2
- Turbo Linux Enterprise Server 8
- Turbo Linux Server 10
- Miracle Linux 3.0
- Red Flag Advanced Server 4.0 and 4.1
- Red Flag Data Center Server 4.1
- Asianux 1.0
- CA 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)
- 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)
- CA ARCserve Backup Client Agent for Microsoft Data
Protection Manager:
- Windows Server 2003 Standard Edition SP1
- Windows Server 2003 Enterprise Edition SP1
- Windows Server 2003 R2 Standard Edition (32-bit)
- Windows Server 2003 R2 Enterprise Edition (32-bit)
- Windows 2003 Storage Server SP1
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
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
Hardware Requirements
- CPU: 512 MHz
- RAM: 512 MB
- Disk Space: 1.5 GB
The CA ARCserve Backup Agent for Lotus Domino supports the
following:
Note: The Agent now installs the Exchange Database Level
Agent with the Exchange Document Level Agent.
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:
Additional Software Requirements for the Agent for
Microsoft Exchange
- For Microsoft Exchange Server 2000:
- Microsoft Windows 2000 Service Pack 3 or Service Pack 4
- For Microsoft Exchange Server 2003, you need the following
applications:
- Microsoft Windows 2003, Windows 2003 Service Pack 1, or
Windows 2003 Service Pack 2
- Microsoft Exchange Server 2003, Exchange Server 2003
Service Pack 1, or Exchange Server 2003 Service Pack 2
- For Microsoft Exchange Server 2007 or Exchange Server 2007
SP1, you need the following applications:
- Microsoft Windows 2003 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)
- Microsoft Messaging API and Collaboration Data Objects
1.2.1 (required for the Document Level Agent)
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
The CA ARCserve Backup Agent for Microsoft Office
SharePoint supports the following:
- Windows 2003 Standard
- Windows 2003 Enterprise
- Windows 2003 Web
- Windows 2008 Enterprise
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 Note,
below)
- Microsoft Office SharePoint Services 3.0, 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.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
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 or Service
Pack 2
- Microsoft SQL Server 2008
- Microsoft SQL Server Desktop Engine (MSDE) 2000 with
Service Pack 3 or Service Pack 3a
Microsoft SQL Server 2005 Support
The Agent for Microsoft SQL Server supports Microsoft SQL
Server 2005 Service Pack 1 and Service Pack 2 on the
following operating systems:
- Windows 2003 SP2 or Windows 2003 R2
- Windows Server 2008
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
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, and Service Pack 3a on the following
operating systems:
- Windows 2000 Service Pack 4
- Windows Server 2003
The following section provides the system requirements for
the CA ARCserve Backup Agent for Oracle (UNIX/Linux):
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:
- CPU: 500 MHz
- RAM: 256 MB
- Disk Space: 15 MB
Additional Hardware Requirements
- For Linux x86 platforms
- CPU: 500 MHz
- RAM: 256 MB
- Disk Space: 25 MB
- For Linux AMD64 platforms
- CPU: 1 GHz
- RAM: 256 MB
- Disk Space: 25 MB
- For Linux itanium platforms
- CPU: 1 GHz
- RAM: 512 MB
- Disk Space: 25 MB
The following section provides the system requirements for
the CA ARCserve Backup Agent for Oracle:
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
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
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.
Additional Software Requirements
The Agent for Open Files requires one of the following
operating systems:
- Windows 2000
- Microsoft Vista™
- Windows XP x86, x64, and IA64
- Windows Server 2003 Web Edition, Standard Edition, or
Enterprise Edition x86, x64, and IA64
- Windows Server 2008 Enterprise Edition (x86, x64, and IA64)
- Windows Server 2008 Standard Edition (x86, x64, and IA64)
- Windows Server 2008 Enterprise Core (x86 and x64)
The following is also required:
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).
Hardware Requirements
- CPU: 550 MHz
- RAM: 512 MB
- Disk Space: 2.1 MB
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Note: When the Agent for VMware is installed on the same
server as the base product, the agent requires the same
hardware specified for the base product. When the Agent for
VMware is installed on a remote node, the agent requires
the same hardware specified for the Client Agent for
Windows.
Additional Software Requirements
The CA ARCserve Backup Agent for VMware supports the
following:
- Windows 2003 Server
- VMware ESX Server release 3.0.2 systems
- VMware ESX Server release 3.5 systems
- VMware ESX Server 3i systems
- VirtualCenter Server 2.02 systems
- VirtualCenter Server 2.5 systems
- VCB 1.0.3
- VCB 1.1.0
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
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.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
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.
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)
- The following versions of Windows are supported for
bootable tape disaster recovery: (Only 32-bit supported)
- The following versions of Windows are supported for
bootable media imaging recovery:
- 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 (x86 and x64)
- Windows 2003 Web Edition
- Windows 2003 Enterprise Edition (x86, x64, and IA64)
- Windows 2003 SBS Edition
Note: The bootable CD method to protect local and remote
64-bit systems is supported on the following platforms:
- Windows 2003 IA64
- Windows 2003 x64
- Windows XP x64 only. Windows XP IA64 is not supported.
- The OS CD + MSD (Machine Specific Data) method of Disaster
Recovery is supported on the following:
- Windows 2003
- Windows XP
- Windows 2008 (x86, x64, 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. 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.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
The Enterprise Module is a prerequisite component for the
following options:
- Enterprise Option for IBM 3494
- Enterprise Option for StorageTek ACSLS
- Image Option
- Media Management Option (MMO)
- Serverless Backup Option
Note: 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.
Software Requirements
The minimum operating system requirements for the
Enterprise Module are:
- Windows 2000
- Windows 2003
- 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.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
CA ARCserve Backup must be installed before you install the
CA ARCserve Backup Disk to Disk to Tape Option.
Disk to Disk to Tape Option supports the following
operating systems:
- Windows 2000
- Windows XP Professional
- Windows 2003
- Windows Server 2008
The Enterprise Option for IBM 3494 is now supported by the
Enterprise Module.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
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 7.0 for Oracle 10g
- Windows 2003 Enterprise Edition IA64 Service Pack 1,
Service Pack 2 with 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.
The Enterprise Option for StorageTek ACSLS is now supported
by the Enterprise Module.
Image Option support is now supported by the Enterprise
Module.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
- Operating System: Windows 2000 or Windows 2003
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
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
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
- Windows 2003
Note: The following capabilities have been incorporated
into the Tape Library Option:
- Optical Library Support
- Tape RAID Support
Serverless Backup is now supported by the Enterprise
Module.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
The CA ARCserve Backup Storage Area Network (SAN) Option
may be installed on the following operating systems:
- Windows 2000
- Windows 2003
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
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
- Client Agent for Microsoft Exchange
- Client 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
- Client Agent for Microsoft Exchange
- Client Agent for Microsoft SQL
- Client Agent for Microsoft SharePoint.
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.
Software Requirements
To access CA ARCserve Backup Backup for Microsoft Windows
EBS, you must meet the following prerequisites:
- Windows Server 2008
- Microsoft Windows EBS
- CA ARCserve Backup
The following sections provide information about
installation prerequisites, configurations, and issues to
consider before installing CA ARCserve Backup and its
agents and options.
The following section provides information about
installation prerequisites, configurations, and issues to
consider before installing the CA ARCserve Backup base
product.
- 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:
- Create a key called MessageEngine under:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\Base\Admin
- Create a DWORD valued called Impersonate under:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\Base\Admin\MessageEngine
- Set Impersonate to 0.
- Reboot the Windows system.
- The CA ARCserve Backup Dashboard for Windows is not
translated. The product is only available in English.
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 to r12 SP1, 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 CA
ARCserve Backup 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".
The following section provides information about
installation prerequisites, configurations, and issues to
consider before installing the CA ARCserve Backup Client
Agents.
Agent for NetWare
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 r11.5 SP3 to
apply the ErgoGroup A.S. Patch.
- The Agent for Oracle on UNIX/Linux platforms requires
patches if running on a UNIX/Linux system. See ca.com/support for the latest software
updates to the BrightStor ARCserve Backup Agent for Oracle
on UNIX 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.
Virtual Machines
The following section provides information to consider when
installing the Agent for Microsoft Exchange.
The following section provides information to consider when
installing the Agent for Microsoft SharePoint 2003:
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.
The following section provides information about
installation prerequisites, configurations, and issues to
consider before installing the Agent for Microsoft SQL
Server.
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.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
The Enterprise Module is a prerequisite component for the
following options:
- Enterprise Option for IBM 3494
- Enterprise Option for StorageTek ACSLS
- Image Option
- Media Management Option (MMO)
- Serverless Backup Option
Note: 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.
Software Requirements
The minimum operating system requirements for the
Enterprise Module are:
- Windows 2000
- Windows 2003
- 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.
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.
This release of CA ARCserve Backup lets you integrate
Microsoft Windows Essential Business Server 2008, English -
Release Candidate 1, 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.
- Modify the Forefront TMG firewall policy to ensure proper
communication between the CA ARCserve Backup Client Agent
on the security server and CA ARCserve Backup.
To modify the Forefront TMG firewall policy, perform the
following procedure to create a new access rule that
enables port 6050:
- From the Windows Start menu, choose Programs, Microsoft
Forefront TMG, Forefront TMG Management.
Forefront TMG opens.
- In the Threat Management Gateway list, right-click Firewall
Policy and choose New, Access Rule from the shortcut menu.
- Follow the prompts on the wizard screen to create a new
access rule with a rule action of 'Allow'.
- Create two new protocols, one that allows for TCP incoming,
UDP send, and UDP send receive for port 6050.
- Add another protocol for TCP outgoing, UDP receive, and UDP
receive send for port 6050.
- Add the new protocols to the access rule you are creating.
- Complete the remaining wizard steps as required. Ensure the
sources and destinations include All Networks.
- Apply the new rule.
- In the Threat Management Gateway list, click Monitoring.
- Click the Configuration tab and ensure the status for the
new rule is synched.
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.
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.
- In the CA 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 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.
- If the ASDBBackups.txt file cannot be opened correctly,
perform the following:
- Open the ASDBBackups.txt file with Word 2003 or later
version.
- In the file conversion dialog, select other encoding and
UNICODE in the list box, and click OK.
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 a CA ARCserve Backup user, for
example, caroot. In the Create Equivalence dialog, complete
the following fields and click OK:
- When connecting to a new server, you need to provide a
valid CA ARCserve Backup user name, for example, 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:
- CA ARCserve Backup supports Virtual Systems back up and
restore jobs on Hyper-V such as VHD and Snapshot on the
Host machine via the VSS agent. Backing up and restoring as
individual files via the Client Agent on the Host OS is not
supported, but backing up and restoring individual files is
supported when the Client Agent is installed on Virtual
Machines.
- 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
on the Virtual Machines.
- Installing the CA ARCserve Backup base product and other
options on Virtual Machines is not supported, so the
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.
You can upgrade to this release of CA ARCserve Backup from
the following products:
For all other releases, you must uninstall the existing
software version before you install CA ARCserve Backup.
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)
- BrightStor ARCserve Backup r11.1 (and all service packs )
- CA ARCserve Backup r12
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)
This release of CA ARCserve Backup Manager can view and
manage r12 CA ARCserve Backup Servers.
The following sections provide information about issues
known to exist in CA ARCserve Backup for this release.
The following issues relating to the CA ARCserve Backup
base product are known to exist in this release:
- 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:
- 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.
- 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.
- Open Network Connections.
- Double-click <Connection Name>.
- Click the Support tab.
- Click Details.
- Note the values for "WINS Servers". The WINS Servers
provide the NetBIOS name resolution for your remote
servers.
- Ping the WINS servers using the commands in Step 1.
- 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.
- (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
- Purge and reload the NetBIOS Remote Cache Name Table:
nbtstat -R
- Run nbtstat -c again. The table should now be empty, or
contain only a few new items with lives of about 600
seconds.
- 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.
- 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: Client\Agent Parameters
Value: 0 to retain directory folders, 1 to delete them.
- 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:
- After you restore the ARCserve database, use the Merge
utility to merge the ARCserve database backup sessions.
- 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 and Windows 2003
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
inventoried and used in a media pool in an r11.5
environment.
- If you disable Catalog Browsing when performing a backup
job, please note that the catalog files of all sessions
after the CA ARCserve Backup database session (C drive
session, Job session) remain in the TEMP folder and are not
deleted by Mergecat. This problem does not affect merge or
restore processes. All merge and restore processes are
still normal, but it does consume disk space. You may
delete catalog files manually.
- 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/Execuite 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.
- Local backup sessions performed with 32-bit operating
systems (including Windows XP, Windows 2000 and Windows
2003) cannot be restored by 64-bit operating systems.
- 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 backup by selecting link files as the
backup source, the paths to common store files are not
displayed properly in the Restore Manager when using
Restore by Session or Restore by Tree. Some files may be
missing.
- When you restore the \SIS Common Store session to its
original location, the restore path is not recorded in the
Job Log and may be restored to a different location.
- 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.
- When the CA ARCserve Backup Agent for Open Files is
installed, a restore job for SIS-managed files runs
indefinitely without completing and cannot be stopped using
the Stop button from the job status queue. To force a job
stop, you must find the carunjob.exe process associated
with the job in Task Manager and click End Process. Because
the restore job is incomplete, the link files cannot be
deleted. This affects only files managed by SIS. Files not
managed by SIS on a drive on which SIS is activated can be
successfully restored.
- Server backups performed locally cannot be restored to a
remote client agent and record a AE0040 error, "Invalid
file signature".
- If you have demoted a Primary Server to a Member Server,
wait for approximately five minutes before you start
migration for the new equivalence to take effect on the
Member Server.
- 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:
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:
- Install the Windows support tool, "SUPTOOLS.MSI" from your
Windows installation CD. Go to the <CD-ROOT>\SUPPORT\TOOLS\
directory.
- Run the Command Prompt: Start, All Programs, Windows
Support Tools, Command Prompt.
- Type the following in the open Command Prompt window:
sc config CASDBEngine depend= MSSQLXXXX
sc config CASUniversalAgent depend= MSSQLXXXX
sc config CASTapeEngine depend= MSSQLXXXX
- 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.
- 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:
- In the Database Manager, expand the media Records. The tape
name appears at least twice, once in uppercase letters and
once in lowercase letters.
- 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.
- Effective with this CA ARCserve Backup release, there are
now two registry keys, SkipDSAFiles and BackupDBFiles, that
specify the files to include or skip during backup jobs.
(In r11.5, only SkipDSAFiles was used for this purpose.) In
this release, use of these keys is determined by the type
of database agent you are running. Refer to the following
list, which shows the database agents by registry key and
what files are affected:
Use SkipDSAFiles
Set the SkipDSAFiles registry key to 0 to include these
files and 1 to skip them.
Value Name: SkipDSAFiles
Type: DWORD
Value: 0 to back up and 1 to skip
Agent for Oracle, Agent for SAP R/3
- *.dbf
- Control*.*
- Red*.log
- Arc*.001
Agent for Domino
Agent for Sybase
- Physical file of Master device
- Physical file of non-Master device
- Physical file of Mirror device
Agent for Informix
Use BackupDBFiles
Set the BackupDBFiles registry key to 0 to skip these files
and 1 to include them:
Value Name: BackupDBFiles
Type: DWORD
Value: 0 to skip and 1 to back up (1 is default)
Agent for Microsoft SQL
The list of data and transaction log files that are part of
online databases is retrieved from Microsoft SQL Server at
the start of a file backup. This list typically includes,
but not exclusively:
Except distmdl.mdf, distmdl.ldf, mssqlsystemresource.mdf,
mssqlsystemresource.ldf, which cannot be skipped. Also, if
a SQL Server instance is shut down, the database files will
not be skipped.
Exchange Database Level Agent/Exchange Document Level Agent
- *.chk
- *.log
- Res1.log
- Res2.log
- *.edb
- *.stm
Note: The Exchange Brick Level Agent is no longer
supported, but in r11.5 used the SkipDSAFiles registry key.
- Backup jobs submitted using BrightStor ARCserve Backup
r11.5 Agents (includes all service packes) 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.
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.
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 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 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.
The following issues relating to the Agent for IBM Informix
are known to exist in this release:
- Your Informix server should be installed on a Windows 2000
machine in a Windows domain. Windows NT 4.0 is no longer
supported. You must use the Backup and Restore Managers to
submit the backup and restore jobs.
- 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
The following issues relating to the Agent for Microsoft
Data Protection Manager are known to exist in this release:
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.
- CA ARCserve Backup incorrectly displays the Exchange
instance name instead of the agent hostname in Agent
Options on the Security and Agent Information dialog.
- Do not disable Catalog DB when performing backup and
restore jobs with this release.
- 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.
The following issues relating to the Agent for Microsoft
SharePoint are known to exist in this release:
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.
- 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.
- 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 SQL database, the
SendTimeOut and ReceiveTimeOut parameters define how long
the CA 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 expires, 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 SendTimeOut and ReceiveTimeOut keys can be found on the
CA ARCserve Backup Server machine under:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\Base\Task\Remote
Note: These settings apply to all agents which operate
under the Universal Agent service.
- The Microsoft Windows Small Business Server 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 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:
- Open the Registry Editor and find the following registry
key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\
- In this registry key, add a DWORD Value called
DBLocalAsRemote and set its value to 1.
- 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.
- Backup with Compare and Backup with Scan Tape are not
performed on agent sessions.
- 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 the current version of CA ARCserve Backup
and CA ARCserve Backup Agent for Microsoft SQL Server to
restore a backup made using 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:
- Open the Registry Editor and select the key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\Base\Task\Common\DBAgentsSettings
- In the Edit menu, select New> DWORD value. Set the name of
this value to SQLProtocol and its value to 0.
- Resubmit the restore job.
- After all restore operations using these backups are
completed, return to the Registry Editor and delete the
SQLProtocol value.
- 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 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:
- Locate the version of sqlvdi.dll that belongs to the newest
version of Microsoft SQL Server or MSDE on the machine.
- 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
- 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.
Note: MSDE 1.0 storing a SQL Server CA ARCserve Backup
database is not supported.
- 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. See the Known Issues for Upgrading to CA
ARCserve Backup section of this document for further
information.
- 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.
- 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.
- Microsoft SQL Server 2008 introduces a data type called
FILESTREAM, which stores large blocks of binary data in
files on disk. FILESTREAM data is stored in logical SQL
Server files that exist as directories on disk. SQL Server
does not properly report the size of FILESTREAM data, and
the size of this data will not be included in backup or
restore estimates, nor will it be reported correctly in the
backup session's file list.
- 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.
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:
- Open the Control Panel and choose Regional and Language
Options.
- Click Advanced.
- Choose the option, Apply all settings to the current user
account and to the default user profile.
- Restart the machine.
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:
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.
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:
- Open a sqlplus prompt.
- Enter the following command:
alter system set backup_tape_io_slaves = true deferred
- Restart the database.
- Set the Number of Copies option to a value greater than 1.
- 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.
The following issues relating to the Agent for UNIX/Linux
are known to exist in this release:
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:
- From a DOS command prompt, start isql.
- Enter the command:
1>sp_configure "enable xact coordination", 0
2> go
- 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 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
The following issues relating to the Agent for VMware are
known to exist in this release:
- The Agent does not support jobs using Backup/Restore
Wizard.
- Backed up Linux VM images appear in the Restore by Tree
list under Windows Systems as well as under UNIX/Linux
systems. Backed up Windows raw mode images also appear in
the UNIX/Linux Systems and Windows Systems lists.
The following issues relating to the Disaster Recovery
Option are known to exist in this release:
The following section provides information regarding issues
known to exist in this release of CA ARCserve Backup for
the Image 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.
- 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 member servers.
- CA 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 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:
- Perform Restore by Session.
- Submit a job to restore the full session
- Submit another job to restore the differential session to
the same directory as the previous restore.
- To restore data relating to a qtree that was backed up as a
whole volume using the NDMP NAS Option, you must set the
following registry key to restore the qtree information
properly.
Note: For more information, see the QI89170 Knowledge Base
document.
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\NASAgent\Parameters
Value Name: bForceSelectiveFileRestore
Type: DWORD
Value: 1 (Default is 0)
Note: After you set the above registry key, CA ARCserve
Backup records the following message in the Activity Log
when the restore job runs:
At least one of the source files or directories selected does not support direct positioning, using Selective file restore instead.
The following issues relating to the Tape Library Option
are known to exist in this release:
The following issues relating to the SAN Option are known
to exist in this release:
- Mixed SAN environments are no longer supported.
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.
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.
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.
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:
- On the remote system running the SAP option, go to the
Windows\System32\drivers\etc folder.
- Open the hosts file.
- Add host/IP map as below:
<IP address> machine_name
where <IP address> is the IP of the backup server machine
- Save and close the hosts file.
The following issues relating to the Enterprise Option for
StorageTek ACSLS are known to exist in this release:
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 VMware 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.
- Only this version of CA ARCserve Backup supports Unicode.
Diagnostic Reports created with this version of CA ARCserve
Backup cannot be opened in previous versions.
- Backup jobs submitted using BrightStor ARCserve Backup
r11.5 Agents (includes all service packes) and CA ARCserve
Backup r12 Agents that contain Unicode characters in their
directory names and file names will fail after you upgrade
to this release. To avoid this problem, specify the parent
directory of the directories, files, or both that contain
Unicode characters and then resubmit the job.
- Microsoft Windows does not support Unicode characters in
the command line interface, therefore, you cannot use the
Windows command line to enter CA ARCserve Backup commands
containing Unicode characters. Use the Windows Powershell
instead of cmd.exe, or use the -f switch to save text files
as Unicode files.
The 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.
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.
The following section provides information about issues
relating to the documentation for CA ARCserve Backup that
are known to exist in this release:
Administration Guide
- The topic, Change the Computer Name of the Primary Server
on the Primary Server contains incorrect URLs. The
corrected sentences are as follows:
- How to Rename a Computer that Hosts a Stand-Alone Instance
of SQL Server 2005 at
http://msdn.microsoft.com/en-us/library/ms143799.aspx
- Installing SQL Server (SQL Server 2000) Renaming a Server
at http://msdn.microsoft.com/en-us/library/aa197071.aspx
- The topic, Files and Objects that CA ARCserve Backup Does
Not Back Up, the following procedure to modify the CA
ARCserve Universal Agent service was omitted:
- From the Control Panel, choose Administrative Tools and
then choose Services.
- Click the CA ARCserve Universal Agent service from the
Services list to select it.
- Click Action, Stop to stop the service from running.
- Right-click the service and click Properties.
- On the Log On tab of the Properties dialog, click This
Account and provide the required credentials.
- Click OK.
- Restart the CA ARCserve Universal Agent service.
Agent for Microsoft Exchange Guide
- The topic Configure the Agent for Database Level Backup and
Restore defines the following options:
- The topic Configure the Agent for Document Level Backup and
Restore defines the following options:
Agent for Open Files Guide
- In the topic, NetWare Engine Installation, Step 1 should
state:
1. Select Programs, CA, ARCserve Backup, and Agent for Open
Files from the Start Menu.
- The topic, The Console shows an out-dated screen for the
Backup Agent for Open Files Console. The screen is from the
previous CA ARCserve Backup version and should be from this
release.
- In the topic Agent for Open Files Status dialog appears to
be corrupted, the Frequently Asked Questions Appendix of
the Japanese version of this guide is missing the following
information regarding RCONSOLE.
RCONSOLE is the DOS-based Remote Console utility used to
log in to NetWare machines remotely and is available at
\\<ServerName>>\SYS\PUBLIC.
Agent for Lotus Guide
- A field name is incorrectly labeled in the Guide. In the
topic, Perform a Backup, the field shown in the screen
capture as Media Pool Used is incorrectly described in the
text as "Media Pool Name Prefix".
- Also in the Perform a Backup topic, the Job Monitor screen
is incorrectly referred to as "Job Properties."
- In the Perform a Restore topic, several options are
mislabeled. The correct options are as follows:
Agent for Microsoft SharePoint Guide
- The following troubleshooting information was omitted from
the Guide:
If you receive an AE9972 Object <Component Name> failed
error in event OnRestore, perform the following tasks:
- Start the Windows Service, SPAdmin, displayed as Windows
SharePoint Services Administration.
- Go to the SharePoint 3.0 Central Administration website and
select Operations, Topology and Services, Services on
Server.
- Choose the agent machine server and select the Custom radio
box.
- Click Central Administration
- Click Start.
- Run the job that previously failed again.
- The graphics used in the following sections of this Guide
may be old or unclear and will be updated:
- Configure the Agent on SharePoint 2003 Systems
- Dynamic and Explict Job Packaging
- The topic, Restore Database to Alternate Microsoft SQL
Systems, contains two backslashes (\\) in the destination
path. The correct path has only one backslash (\) as
follows:
\\<DatabaseServerMachineName>\dbasql@<SQLServerInstanceName>\<DatabaseName>
- The following bullet was omitted from the topic,
Database-Level Restore Prerequisites:
For stand-alone installations, please add the following
accounts into the Local Administrators Group before
performing the restore job. Once the restore is completed,
delete the accounts:
- Open Control Panel and expand Administration Tools,
Computer Management, System Tools, Local Users and Groups,
Groups, Administrators.
- Click Add.
- Enter NETWORK SERVICE and LOCAL SERVICE.
- Click OK.
Agent for Oracle (Windows) Guide
Agent for Oracle (UNIX) Guide
- The following new features, found on the Advanced Oracle
Backup Options tab, were omitted from the Guide:
- Fail the job if number of copies is more than 1 and so many
drives are not available -- When selected, the backup job
fails whenever the number of copies is greater than one and
the job cannot gain access to a number of devices
sufficient to support them. When not selected, the backup
job continues to run even when the number of devices is
insufficient for the number of copies. However, the number
of copies is reduced.
- Device availability waiting time (minutes) -- Specify how
long a backup job should wait if it is unable to access the
number of devices required. Use with the "Continue backup
even if some requested devices are not available" option.
- Continue backup even if some requested devices are not
available -- When selected, a backup job continues to run
as long as at least one device is assigned. When not
selected, the job fails when it cannot access enough
devices within the time specified in the "Device
availability waiting time" field.
- The following information was also omitted from the Guide:
When you register the Agent for Oracle as a user on a UNIX
server, you must have caroot equivalence on the Windows
server on which the base CA ARCserve Backup product is
installed. You also need to add a caroot equivalence for
that user on the Oracle Agent server machine. Use the
following commands:
- Run the following command on the CA ARCserve Backup base
machine
ca_auth [-cahost HostName] -equiv add <Oracle user><OracleHostName> caroot [caroot_username][caroot_password]
Example:
Oracle Host Name: abc123
ca_auth -cahost ARCserve -equiv add oracle abc123 caroot caroot caroot_password
ca_auth -cahost ARCserve -equiv getquiv oracle abc123
- Run the following command on the Agent for Oracle machine,
abc123
[root@abc123 BABoraagt]# ./ca_auth -cahost babserver -equiv add oracle abc123 caroot caroot caroot_password
[root@abc123 Baboraagt]#./ca_auth -cahost babserver -equiv getquiv oracle abc123
Equivalent BrightStor user for oracle@abc123:caroot
Agent for VMware Guide
- In the Agent for VMware Guide, the topics that follow apply
to performing backup and restore operations on local
disk-based virtual machines (VMs) and SAN-based VMs.
- Back Up Data
- Restore File-Level Data
- Restore Raw (Full VM) Level Data to ESX Server 3.0.x and
ESX Server 3.5 Systems
- Restore Raw (Full VM) Level Data to ESX Server 3.5 and ESX
Server 3i Systems Using the VMware Converter
Client Agents Guide
- The topic, Use the Backup Agent Admin to Set Windows
Parameters should state:
Log--The Log file is stored in the following path:
<ARCserve_HOME>\ARCserve Backup Client Agent for
Windows\ntagent.log
The log for every job that runs is stored in this log file.
- The topic, Supported Client Systems contains incorrect
information:
CA ARCserve Backup Client Agent for Windows. This client
agent supports the following: Windows Server 2008 (Core
Operating System only).
"Core Operating System only" should be deleted.
- The topic, Supported Client Systems, contains incorrect
platform information. The correct content is as follows:
- CA ARCserve Backup Client Agent for Mainframe Linux. This
client agent also supports the following:
- Red Hat Enterprise Server 3, 4 (32-bit and 64-bit)
operating on zSeries and S/390
- SLES 8 and 9 (32-bit and 64-bit) operating on zSeries and
S/390
Disaster Recovery Option Guide
- The keyboard shortcuts for the Install, Refresh and Reboot
buttons on the Disaster Recovery Using USB Backup Devices
dialogs do not function as indicated. Use Shift+<key> to
execute those commands instead of Alt+<key>.
Microsoft Volume Shadow Copy Service Guide
- In the topic, VSS Support in CA ARCserve Backup, the
location specified for CALicnse.exe is not correct. The
correct location is as follows:
C:\Program Files\CA\SharedComponents\CA_LIC
Note: CALicnse.exe will reside in C:\CA_LIC only if there
are other CA products installed on your system, and the
other products were installed before you installed CA
ARCserve Backup r12.
- In the topic Restore Methods, information was omitted from
the Note. The Note should read:
Note: Not all Components can be restored individually. The
Writer decides whether a Component can be restored
individually. When SQL Server instance is stopped,
restoring only one individual custom database is not
supported, even though the restore job is successful.
NDMP NAS Option Guide
Online Help
- For the Japanese version of CA ARCserve Backup, the Alert
Manager Online Help displays in English.
- The CA ARCserve Backup Agent for Microsoft SharePoint Help
incorrectly displays the SQL Server Online Help when you
click Help from the SharePoint 2003 Agent Backup Options
dialog. To find an explanation of the fields on this
dialog, see the Agent for Microsoft SharePoint Guide.
- The topic, Task Engine Messages 3701 through 3764 should be
Task Engine Messages 3701 through 3800.
- The topic, Task Engine Messages 3951 through 3880 should
not include the message Warning W3981. This message already
exists in the topic, Task Engine Messages 3981 through 4000.
- The topic All Windows Messages incorrectly states the
message ranges for VSS Messages and for Domain Server
Messages. The correction is as follows:
VSS Messages (12502-12612, 65535)
Domain Server Messages (50064-50065, 61176-61177)
- The topic, Clean Tape Drive Heads Option incorrectly states
steps 1 and 2. The correction is as follows:
- Click Clean Tape Head.
The Clean Tape head dialog appears.
- The topic, Tape Library Option Summary incorrectly states
the first bullet. The corrected bullet is as follows:
- If yes, click Next or Exit to complete the configuration of
your libraries.
Documentation Changes
The following CA ARCserve Backup documents have been
updated for this release:
Note: You can access the most current documents from the
product installation media.
- Administration Guide
- Agent for Oracle Guide
- Agent for Open Files Guide
- Agent for IBM Informix Guide
- Agent for VMware Guide
- Client Agents Guide
- Client Agent and Enterprise Options Readme
- Command Line Reference 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
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.
The following tables list the fixes included in the current
and prior releases of CA ARCserve Backup. If you discover
that a specific release is not included in this section,
please contact Technical Support.
Fixes added to CA ARCserve Backup with this release:
| QO94901 |
T245445 |
T2D2639 |
T36A460 |
T512082 |
T5E5009 |
| QO95065 |
T245447 |
T2D2640 |
T36A461 |
T512083 |
T5GT008 |
| QO95275 |
T245448 |
T2D2641 |
T36A462 |
T56D014 |
T5GT010 |
| QO99390 |
T245450 |
T2D2642 |
T36A474 |
T56D015 |
T5GT011 |
| QO99421 |
T245451 |
T2D2643 |
T36A476 |
T58E057 |
T5GT013 |
| QO99452 |
T245452 |
T2D2644 |
T36A477 |
T58E060 |
T5GT016 |
| QO9974 |
T245453 |
T2D2649 |
T36A478 |
T58E062 |
T5GT023 |
| QO99844 |
T245454 |
T2D2649 |
T36B273 |
T58E063 |
T5GT026 |
| T146472 |
T245457 |
T2D2651 |
T36B275 |
T58E064 |
T5JS001 |
| T146473 |
T245457_1 |
T2D2654 |
T439082 |
T58E069 |
TF68236 |
| T146479 |
T245458 |
T31A444 |
T439090 |
T58E077 |
|
| T146480 |
T245460 |
T31A474 |
T46B174 |
T59E022 |
|
| T16C729 |
T245461 |
T31A480 |
T46B199 |
T59E024 |
|
| T16C732 |
T245476 |
T31A481 |
T46B200 |
T5A0023 |
|
| T16C733 |
T245480 |
T36A409 |
T46B201 |
T5A6060 |
|
| T16C734 |
T245482 |
T36A423 |
T46B205 |
T5A6061 |
|
| T16C735 |
T245483 |
T36A423-2 |
T46B206 |
T5A6064 |
|
| T16C739 |
T2D2632 |
T36A448 |
T46B209 |
T5A6067 |
|
| T16C748 |
T2D2633 |
T36A449 |
T46B211 |
T5A6069 |
|
| T16C751 |
T2D2636 |
T36A450 |
T46B214 |
T5A6070 |
|
| T16C753 |
T2D2637 |
T36A454 |
T46B217 |
T5A6071 |
|
| T16C754 |
T2D2637 |
T36A455 |
T46B218 |
T5A6072 |
|
| T245435 |
T2D2638 |
T36A456 |
T512082 |
T5A6076 |
|
| T245440 |
T2D2638_2 |
T36A457 |
T512082 |
T5A6077 |
|
| T245444 |
T2D2638_2 |
T36A459 |
T512082 |
T5A6079 |
|
Fixes added to CA ARCserve Backup with the previous
release:
| T146434 |
T16C664 |
T245302 |
T245377 |
T2D2548 |
T31A458 |
T36A407 |
T46B162 |
T58E037 |
T59E012 |
T5GT005 |
| T146434 |
T16C666 |
T245303 |
T245378 |
T2D2579 |
T31A459 |
T36A410 |
T46B162 |
T58E043 |
T59E012 |
T245386 |
| T146435 |
T16C674 |
T245304 |
T245380 |
T2D2580 |
T31A460 |
T36A414 |
T46B164 |
T58E044 |
T59E013 |
T146419 |
| T146435 |
T16C676 |
T245305 |
T245381 |
T2D2581 |
T31A461 |
T36A415 |
T46B167 |
T58E046 |
T59E014 |
T245386 |
| T146437 |
T16C677 |
T245306 |
T245384 |
T2D2582 |
T31A462 |
T36A416 |
T46B168 |
T58E049 |
T59E015 |
|
| T146441 |
T16C678 |
T245307 |
T245387 |
T2D2583 |
T31A463 |
T36A417 |
T46B171 |
T58E050 |
T59E017 |
|
| T146443 |
T16C679 |
T245308 |
T245388 |
T2D2586 |
T31A464 |
T36A418 |
T46B174 |
T58E050 |
T5A0018 |
|
| T146445 |
T16C680 |
T245309 |
T245390 |
T2D2587 |
T31A465 |
T36A421 |
T46B175 |
T58E051 |
T5A0019 |
|
| T146450 |
T16C681 |
T245311 |
T245392 |
T2D2587 |
T31A466 |
T36A422 |
T46B176 |
T58E052 |
T5A0019 |
|
| T146451 |
T16C693 |
T245312 |
T245393 |
T2D2589 |
T31A467 |
T36A423 |
T46B177 |
T58E053 |
T5A0020 |
|
| T146452 |
T16C694 |
T245313 |
T245396 |
T2D2590 |
T31A468 |
T36A423 |
T46B179 |
T58E054 |
T5A0021 |
|
| T146453 |
T16C695 |
T245314 |
T245397 |
T2D2591 |
T31A469 |
T36A423 |
T46B180 |
T58E055 |
T5A0021 |
|
| T146454 |
T16C696 |
T245315 |
T245398 |
T2D2592 |
T31A470 |
T36A426 |
T46B181 |
T58E058 |
T5A0021 |
|
| T146455 |
T16C697 |
T245317 |
T245399 |
T2D2594 |
T31A472 |
T36A428 |
T46B181 |
T58E060 |
T5A6020 |
|
| T146457 |
T16C698 |
T245318 |
T245400 |
T2D2595 |
T354201 |
T36A429 |
T46B182 |
T58E061 |
T5A6022 |
|
| T146458 |
T16C701 |
T245319 |
T245401 |
T2D2596 |
T36A345 |
T36A430 |
T46B183 |
T58E065 |
T5A6025 |
|
| T146459 |
T16C702 |
T245320 |
T245402 |
T2D2597 |
T36A359 |
T36A432 |
T46B184 |
T58F016 |
T5A6026 |
|
| T146460 |
T16C703 |
T245322 |
T245403 |
T2D2599 |
T36A360 |
T36A433 |
T46B185 |
T58F017 |
T5A6027 |
|
| T146461 |
T16C704 |
T245323 |
T245404 |
T2D2606 |
T36A361 |
T36A435 |
T46B186 |
T58F018 |
T5A6029 |
|
| T146462 |
T16C705 |
T245324 |
T245405 |
T2D2616 |
T36A363 |
T36A436 |
T46B187 |
T58F019 |
T5A6031 |
|
| T146463 |
T16C706 |
T245325 |
T245406 |
T2D2619 |
T36A364 |
T36A437 |
T46B188 |
T58F020 |
T5A6031 |
|
| T146464 |
T16C707 |
T245327 |
T245407 |
T2D2620 |
T36A365 |
T36A438 |
T46B189 |
T58F021 |
T5A6032 |
|
| T146465 |
T16C709 |
T245328 |
T245408 |
T2D2621 |
T36A367 |
T36A439 |
T46B190 |
T58F023 |
T5A6033 |
|
| T146466 |
T16C710 |
T245329 |
T245410 |
T2D2622 |
T36A368 |
T36A441 |
T46B191 |
T58F025 |
T5A6034 |
|
| T146468 |
T16C711 |
T245330 |
T245411 |
T2D2623 |
T36A369 |
T36A443 |
T46B192 |
T595008 |
T5A6035 |
|
| T146468 |
T16C713 |
T245330 |
T245412 |
T2D2624 |
T36A372 |
T36A444 |
T46B193 |
T595009 |
T5A6037 |
|
| T146471 |
T16C714 |
T245332 |
T245415 |
T2D2625 |
T36A375 |
T36A445 |
T46B193 |
T595010 |
T5A6042 |
|
| T146471 |
T16C715 |
T245334 |
T245416 |
T2D2628 |
T36A378 |
T36A446 |
T46B197 |
T595012 |
T5A6043 |
|
| T16C630 |
T16C717 |
T245335 |
T245417 |
T2D2629 |
T36A379 |
T36A447 |
T56D002 |
T595013 |
T5A6044 |
|
| T16C631 |
T16C719 |
T245336 |
T245418 |
T2D2629 |
T36A380 |
T36B231 |
T56D004 |
T595014 |
T5A6045 |
|
| T16C633 |
T16C720 |
T245342 |
T245419 |
T2D2630 |
T36A381 |
T36B255 |
T56D004 |
T595015 |
T5A6046 |
|
| T16C633 |
T16C722 |
T245344 |
T245420 |
T2D2631 |
T36A382 |
T36B258 |
T56D005 |
T595016 |
T5A6047 |
|
| T16C642 |
T16C724 |
T245345 |
T245421 |
T2D2634 |
T36A383 |
T36B259 |
T56D010 |
T595017 |
T5A6049 |
|
| T16C643 |
T16C725 |
T245346 |
T245422 |
T2D2635 |
T36A383 |
T36B262 |
T577010 |
T595018 |
T5A6051 |
|
| T16C645 |
T16C727 |
T245347 |
T245423 |
T2D2637 |
T36A384 |
T36B263 |
T577011 |
T595019 |
T5A6052 |
|
| T16C646 |
T16C728 |
T245349 |
T245424 |
T31A345 |
T36A385 |
T36B266 |
T577015 |
T596005 |
T5A6052 |
|
| T16C646 |
T16C730 |
T245354 |
T245425 |
T31A402 |
T36A386 |
T36B268 |
T58E018 |
T596006 |
T5A6053 |
|
| T16C647 |
T1A5335 |
T245355 |
T245426 |
T31A403 |
T36A388 |
T36B270 |
T58E019 |
T596007 |
T5A6054 |
|
| T16C648 |
T1A5356 |
T245356 |
T245427 |
T31A405 |
T36A389 |
T36B271 |
T58E020 |
T596008 |
T5A6055 |
|
| T16C649 |
T1A5358 |
T245363 |
T245429 |
T31A411 |
T36A390 |
T36B272 |
T58E020 |
T596009 |
T5A6056 |
|
| T16C649 |
T1A5359 |
T245365 |
T245432 |
T31A412 |
T36A390 |
T46B144 |
T58E021 |
T596010 |
T5A6057 |
|
| T16C651 |
T1A5360 |
T245366 |
T245433 |
T31A421 |
T36A391 |
T46B147 |
T58E022 |
T596012 |
T5A6058 |
|
| T16C653 |
T1A5362 |
T245367 |
T245433 |
T31A438 |
T36A393 |
T46B150 |
T58E023 |
T596014 |
T5A6059 |
|
| T16C655 |
T1A5363 |
T245368 |
T245435 |
T31A443 |
T36A394 |
T46B152 |
T58E025 |
T596015 |
T5E5003 |
|
| T16C656 |
T1A5364 |
T245369 |
T245436 |
T31A449 |
T36A395 |
T46B154 |
T58E026 |
T596016 |
T5E5004 |
|
| T16C657 |
T1A5367 |
T245370 |
T245438 |
T31A450 |
T36A396 |
T46B155 |
T58E027 |
T596017 |
T5E5005 |
|
| T16C658 |
T1A5367 |
T245371 |
T245441 |
T31A452 |
T36A397 |
T46B156 |
T58E029 |
T59E008 |
T5E5006 |
|
| T16C661 |
T245284 |
T245372 |
T245443 |
T31A453 |
T36A398 |
T46B157 |
T58E030 |
T59E009 |
T5GT003 |
|
| T16C662 |
T245293 |
T245373 |
T245450 |
T31A456 |
T36A399 |
T46B158 |
T58E031 |
T59E010 |
T5GT004 |
|
| T16C663 |
T245301 |
T245374 |
T2D2536 |
T31A457 |
T36A400 |
T46B159 |
T58E032 |
T59E011 |
T5GT006 |
|
This release of CA ARCserve Backup includes the following
security-related fixes:
QO99574
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.
Copyright © 2008 CA.
All rights reserved.