CA ARCserve® Backup r12 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 CA XOsoft 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 Open Files
3.10 System Requirements for the Agent for Oracle
3.11 System Requirements for the Agent for VMware
3.12 System Requirements for the Agent for Sybase
3.13 System Requirements for the Disaster Recovery Option
3.14 System Requirements for the Disk to Disk to Tape Option
3.15 System Requirements for the Enterprise Module
3.16 System Requirements for the Enterprise Option for IBM 3494
3.17 System Requirements for the Enterprise Option for Microsoft SQL-HDS and HP-XP Snap-shot
3.18 System Requirements for the Enterprise Option for SAP R/3 for Oracle
3.19 System Requirements for the Enterprise Option for StorageTek ACSLS
3.20 System Requirements for the Image Option
3.21 System Requirements for the NDMP NAS Option
3.22 System Requirements for the Tape Library Option
3.23 System Requirements for the Serverless Backup Option
3.24 System Requirements for the Storage Area Network (SAN) Option
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
4.6 Installation Considerations for the Agent for Microsoft SQL Server
4.7 Installation Considerations for the Agent for Open Files
4.8 Installation Considerations for the Enterprise Module
4.9 Installation Considerations for the Media Management Option (MMO)
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 r12
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 Lotus Domino
7.7 Known Issues for the Agent for Microsoft Data Protection Manager
7.8 Known Issues for the Agent for Microsoft Exchange
7.9 Known Issues for the Agent for Microsoft SharePoint
7.10 Known Issues for the Agent for Microsoft SQL Server
7.11 Known Issues for Microsoft Windows Server 2008 (Longhorn Support) - Unsigned Binaries
7.12 Known Issues for the Agent for Open Files
7.13 Known Issues for the Agent for Oracle (Windows)
7.14 Known Issues for the Agent for Oracle (UNIX and Linux [RMAN])
7.15 Known Issues for the Agent for Sybase
7.16 Known Issues for the Agent for VMware
7.17 Known Issues for the Disaster Recovery Option
7.18 Known Issues for the Image Option
7.19 Known Issues for the NDMP NAS Option
7.20 Known Issues for the Tape Library Option
7.21 Known Issues for the Storage Area Network (SAN) Option
7.22 Known Issues for the Enterprise Option for IBM 3494
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 Portmapper Conflicts with CA ARCserve Backup
7.26 Known Issues for Documentation
8.0 Included Fixes
9.0 Security Related Enhancements
10.0 Language Certifications
11.0 Contact Technical Support
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:
- Microsoft Virtual PC 2007 (32-bit and x64), Microsoft
Virtual Server 2005 R2 SP1 (32-bit) (CA ARCserve Backup
base product, CA ARCserve Backup Client Agent for Windows)
- Windows Vista (32-bit and x64) (CA ARCserve Backup Manager,
CA ARCserve Backup for Open Files, CA ARCserve Backup Agent
for Windows )
- VMware ESX Server version 3.0 (32-bit only), 3.0.1 (32-bit
and 64-bit, x64 only) and 3.0.2 (32-bit and 64-bit, x64
only)
- VMware Server 1.0.4 and 1.0.1, VMware GSX Server 3.0 and
3.1, VMware ESX Server 2.5 and 2.5.4, VMware Workstation
4.0, 4.5, and 5.0 (CA ARCserve Backup base product, CA
ARCserve Backup Client Agent for Windows, CA ARCserve
Backup for Open Files Only)
- Windows XP Professional 32-bit (CA ARCserve Backup Server,
CA ARCserve Backup Manager, CA ARCserve Backup for Open
Files, CA ARCserve Backup Client Agent for Windows) (at
minimum SP1, SP2, and SP3) and 64-bit (CA ARCserve Backup
Client Agent for Windows, CA ARCserve Backup for Open Files
) (at minimum SP1 and SP2)
- Windows Server 2003 Web Edition (32-bit only) (at minimum
SP1 or SP2)
- Windows Server 2003 Standard Edition (32-bit, x64) (at
minimum SP1 or SP2)
- Windows Server 2003 Enterprise Edition (32-bit, x64 and
IA64) (at minimum SP1 or SP2)
- Windows Server 2003 R2 Standard Edition (32-bit, x64) or R2
SP2
- Windows Server 2003 R2 Enterprise Edition (32-bit, x64) or
R2 SP2
- Windows 2000 Professional 32-bit (Service Pack, Service
Pack 4, or Service Pack 4 Rollup 1)
- Windows 2000 Server 32 bit (Service Pack 3, Service Pack 4,
or Service Pack 4 Rollup 1)
- Windows 2000 Advanced Server 32-bit (Service Pack 3,
Service Pack 4, or Service Pack 4 Rollup 2)
- Windows 2000 Cluster Server (2 node Advanced Edition)
- Windows Server 2003 Cluster 32-bit, x64, and IA64
- Windows 2000 and Windows 2003 Datacenter 32-bit and 64-bit
- Windows Powered NAS (2000)
- Windows Storage Server 2003
- Windows Small Business Server 2000
- Windows Small Business Server 2003 and Windows Small
Business Server 2003 R2 plus SP1
- Windows Server 2008 (X86, x64, and IA64)
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
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
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. CA ARCserve Backup
r12 does not support Microsoft SQL 7.0 as the CA ARCserve
Backup database.
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
To integrate CA ARCserve Backup r12 with CA XOsoft, you
must be running CA XOsoft, 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
CA XOsoft 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 XOsoft Integration Guide.
Note: CA XOsoft does not support Microsoft Windows 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
- 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:
- Windows Vista (32-bit and x64) (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
- 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
The CA ARCserve Backup Agent for Lotus Domino supports the
following:
Note: The Agent now installs the Exchange 2007 Database
Level Agent with the Exchange 2007 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:
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
The CA ARCserve Backup Agent for Microsoft SharePoint
supports the following:
- Windows 2003 Standard
- Windows 2003 Enterprise
- Windows 2003 Web
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 SharePoint Portal Server 2007 (see Note, below)
- Microsoft Windows SharePoint Services 3.0, 2.0 SP1
Note: If running Microsoft SharePoint Server 2007 with SQL
Server as database server, apply SP2 to SQL Server.
If running Microsoft SharePoint Server 2007 with SQL Server
Express as database server, apply SP2 to SQL Server
Express.
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 CTP
- 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 2008 (Longhorn)
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 CTP Support
The Agent for Microsoft SQL Server supports Microsoft SQL
Server 2008 CTP on the following operating systems:
- Windows 2003 SP2 or Windows 2003 R2
- Windows 2008 (Longhorn)
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
- Microsoft SQL 2005 for IA64 and x64-based systems on
Windows 2003 SP2 or Windows 2003 R2
- Microsoft SQL 2005 x64-bit Edition on Windows 2008
(Longhorn) for x64-based systems
- Microsoft SQL 2008 x64-bit Edition on for Windows 2003 SP2
or R2 x64-based systems
- Microsoft SQL 2008 x64-bit Edition on Windows 2008
(Longhorn) for x64-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
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
The Agent for Open Files requires one of the following
operating systems:
- Windows 2000
- Windows Vista
- Windows XP x86, x64, and IA64
- 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)
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).
The following section provides the system requirements for
the CA ARCserve Backup Agent for Oracle:
- Microsoft Windows 2003 Service Pack 1, Service Pack 2, and
R2
- Microsoft Windows 2000 Service Pack 4 Rollup 1
Hardware Requirements
No additional hardware is required beyond the Minimum
Requirements previously listed.
Additional Software Requirements
The CA ARCserve Backup Agent for VMware supports the
following:
- Windows 2003 Server (32-bit)
- VMware VirtualCenter Server release 2.0.2 with VMware
Consolidated Backup (VCB) Framework 1.0.3
- VMware ESX Server release 3.0.2 with VCB 1.0.3
- VMware ESX Server release 3.0.1 with VCB 1.0.2/1.0.1/1.0
- VMware ESX Server release 3.0 with VCB 1.0.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.
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 (32-bit and x64)
- Windows 2003 Web Edition
- Windows 2003 Enterprise Edition (32-bit, x64, and IA64)
- Windows 2003 SBS Edition
- Windows Server 2008 Enterprise (32-bit)
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 2000
- Windows 2003
- Windows XP
Machine Specific Data 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. 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.
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
In CA ARCserve Backup r12, 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 Option for IBM 3494 is now supported by the
Enterprise Module.
The CA ARCserve Backup Enterprise Option for Microsoft SQL
using HDS and HP-XP Snap-shot is no longer supported.
A manual upgrade path is available so that existing users
can reconfigure jobs around the CA ARCserve Backup VSS
Option using the SQL/MSDE writer.
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 R2 Enterprise Edition Service Pack 1 with SAP
6.2,6.4 for Oracle 9i or SAP 7.0 for Oracle 10g
- Windows 2000 Service Pack 4 with SAP 6.2 for Oracle 9i
- Windows 2003 R2 Enterprise x64 Edition Service Pack 1 with
SAP 7.0 for Oracle 10g
- Windows 2003 Enterprise Edition Service Pack 1 (IA64) with
SAP 7.0 for Oracle10g
Notes:
- SAPDBA should be installed on the same server to use the
agent BACKINT option.
- SAP R/3 for Windows is required.
- SAP 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
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.
- If you wish to install CA ARCserve Backup components in a
custom location, you must specify separate destination
folder names for each component.
- CA ARCserve Backup installs its services under the Local
System Account. By default, the option Allows Service to
Interact with Desktop is not selected.
- To install CA ARCserve Backup, you must log into your
computer using an administrator account or a user account
with administrator privileges.
- If you are prompted to reboot your machine during the
remote installation process, you must reboot the machine
manually for the remote installation to be successful.
- For successful integration with this release of CA ARCserve
Backup, you must use BrightStor ARCserve Backup for Laptops
& Desktops r11.1 SP 1 or SP 2 or r11.5.
- If you are using CA High Availability (formerly SurviveIT
2000), and CA ARCserve Backup, the High Availability
manager must be installed before you install CA ARCserve
Backup. If CA ARCserve Backup is already installed, Contact
CA Customer Support.
- If you are using CA High Availability, you must ensure that
you have applied the latest patches for High Availability
before installing CA ARCserve Backup.
- If you are installing CA ARCserve Backup on a system where
CA High Availability is installed and running, you must
stop all replication tasks before restarting your system to
allow CA ARCserve Backup to update shared files. Because of
this requirement, you should be aware that your system is
unprotected by CA High Availability while it is restarting.
- If you are installing CA ARCserve Backup with a Microsoft
SQL Server database, you must ensure that you have upgraded
to the correct version of the ODBC driver, as follows:
Change the ODBC Network Libraries setting to TCP/IP, if
necessary.
- Run ARCserveCfg.exe from \CA\ARCserve Backup\ or install
Microsoft SQL 2000, or Microsoft SQL 2005 server or client.
- Enter Microsoft SQL security, or upgrade your ODBC driver
from the web site, or install Microsoft SQL 2000, or SQL
2005 server or client.
Important! Microsoft SQL 7.0 cannot be used as the CA
ARCserve Backup database.
- If you are installing CA ARCserve Backup agents on a
machine where InoculateIT or Antivirus is running, the
following driver update must be applied to both the CA
ARCserve Backup server and the client machine:
http://supportconnectw.ca.com/premium/antivirus/downloads/nt/4.5/ildrvupdate.asp
- When you create equivalences using ca_auth.exe, these
equivalences are created for user names according to the
Windows domain to which they belong. For example, the
equivalence for Domain1\User1 is different from
WinDomain2\User1 and from User1. By default, all command
line utilities detect the domain name of the logged in user
to validate access. To allow backward compatibility,
existing equivalences without domain names are also
accepted. However, this can introduce a security risk for
your environment because a user with the same name but
belonging to another Windows domain can use the command
line utilities. We recommend that you delete existing
equivalences and recreate them for all users to ensure that
the correct domain name is included.
- If you are upgrading to this release, the iSponsor cannot
immediately communicate with CA ARCserve Backup due to the
change in the way in which equivalences are created. To
allow the iSponsor to communicate with CA ARCserve Backup,
execute the following command:
\CA\ARCserve Backup\Authsetup.exe /p <caroot_password>
This command creates the equivalence for the CA ARCserve
Backup system account to allow the iSponsor to work
correctly.
- When upgrading to r12 from previous releases of CA ARCserve
Backup, decide if you wish to keep the old ARCserve Manager:
- If you wish to keep the old ARCserve GUI Manager, you must
provide an upgrade installation location that is different
from the previous installation.
- If you wish to install the upgrade to the same location,
you cannot keep the old GUI manager.
- When upgrading from Microsoft Windows XP SP2 or above to
Microsoft Vista, existing installations of CA ARCserve
Backup will not work. You must uninstall CA ARCserve Backup.
- To protect SQL Server instances in a cluster-aware
environment, you must manually install the Agent for
Microsoft SQL Server on all of the cluster nodes.
- CA ARCserve Backup r12 installs SQL Express SP2 as the CA
ARCserve Backup database when SQL Express is selected.
- During the setup process, an item for CA ARCserve Backup
r12 for Windows for Microsoft Small Business Server appears
only when you install CA ARCserve Backup to the same
machine on which Microsoft Small Business Server is also
installed. Otherwise, you may apply the license via the
CALicnse.exe program. See the Online Help for more
information on the CALicnse.exe program.
The following section provides information about upgrade
prerequisites, configurations, and issues to consider
before upgrade the CA ARCserve Backup base product.
- When you upgrade from a previous BrightStor ARCserve Backup
release, the upgrade process uninstalls the previous
release before installing this CA ARCserve Backup r12. If
the previous ARCserve release was integrated with a
previous version of Java Runtime Environment (JRE), the
uninstallation routine does not remove the directory and
files associated JRE 1.4.2_16 and any previous versions of
JRE from your system. 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.
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 Agent for Windows on Vista
machines. Do one of the following:
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:
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. Do one of the following:
In CA ARCserve Backup r12, 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.
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 following files are not backed up during backup jobs:
- DOS System Files
- The following Windows Files:
- 386SPART.PAR
- 386SPART.TMP
- SPART.PAR
- WIN386.SWP
- DoubleSpace Files (DBLSPACE with any extension)
- DriveSpace Files (DRVSPACE with any extension)
- Stacker Files (STACVOL.DSK)
- BTrieve delta files
- The following Win32System Files:
- PAGEFILE.SYS
- NETLOGON.CHG
- NTUSER.DAT.LOG
- CPL.CFG
- EA DATA.SF
- The following ARCServe Backup Files:
- The following Registry Keys:
- \\HKEY_LOCAL_MACHINE\SYSTEM\CLONE
- \\HKEY_LOCAL_MACHINE\HARDWARE
- \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup
(and all files specified)
- Registry files with the extensions *.ALT and *.LOG
- Cluster installation directory files (typically, the
WINNT\cluster folder), files with no extensions, and files
with the extension *.LOG
- \RECYCLER folder
- \Document and Settings\Administrator\Local Settings\Temp
folder
- %systemroot%\Temp (all files and subfolders inside)
- Folder for file system devices
- If database agents are installed, all files backed up by
the agents are skipped
- Database folders in the CA ARCserve Backup home directory
are skipped during regular file backup operations
- The CA ARCserve Backup r12 command line supports AES128-bit
encryption.
- 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, the
compression/encryption attribute of a folder is not
restored when the Restore and Preserve File Attributes and
Security option is enabled. For files under a folder, all
attributes are restored.
- Use the Server Configuration Wizard to re-initialize the CA
ARCserve Backup database. To re-initialize the database,
perform the following steps:
- Launch the Server Configuration Wizard on primary server.
- Choose Select Database.
- Click Next.
- Enter the caroot password.
- Click Next.
- Enter system account information.
- Click Next.
- In the Select Database screen, accept the defaults.
- Click Next.
A message appears warning you that certain information will
not be migrated.
- Click OK to clear the message.
- If the CA ARCserve Backup database is SQL Server, the SQL
Database System Account screen will appear. Accept the
defaults on this screen.
- Click Next.
- In the Select database installation path screen, make sure
the Overwrite DB option is enabled. Enabling this option is
essential for re-initializing the database.
- Click Next.
- Click Finish when database re-initialization completes.
- For Windows Vista and Windows 2008 operating systems, as a
security feature you are prompted to provide or confirm
administrator credentials (user name and password) each
time you attempt to launch an executable application. To
bypass this continuous prompting you can specify to run
each executable application as an administrator.
Note: This needs to be performed for all CA ARCserve Backup
executable applications (ARCserveMgr, ARCserveCfg, ca_auth
, ca_backup, ca_restore, cabatch, etc.)
To run an application as an administrator, perform the
following:
- Locate and right-click the icon or file name that you use
to run the application and from the pop-up menu, select the
"Run as administrator" option.
- When you are prompted for administrator credentials:
- If you are not logged in as an administrator, enter the
administrator credentials.
- If you are logged in as an administrator, click Continue.
Note: If you want to run the Command Line Interface (CLI),
you can locate the Command Prompt icon (from the Start
menu), right-click the icon, and select the "Run as
administrator" option. After your administrator privileges
have been established for the Command Prompt console, all
subsequent CLI invocations can be launched without any
further prompts until you close the Command Prompt console.
- 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.
- When restoring the CA ARCserve Backup database in a disk
staging environment, CA ARCserve Backup may attempt to
purge data that had already been purged from the staging
device. You will receive a warning message, but note that
the purge job will complete successfully.
You can upgrade to CA ARCserve Backup r12 from the
following products:
- BrightStor ARCserve Backup for Windows r11.5 and all of the
latest service packs.
- BrightStor ARCserve Backup for Windows r11.1 and all of the
latest service packs.
Note: CA ARCserve Backup does not support upgrading
BrightStor ARCserve Backup for Windows r11.1 in a
cluster-aware environment to this release. You must
uninstall BrightStor ARCserve Backup for Windows r11.1 and
then install this release into a cluster-aware environment.
- BrightStor ARCserve Backup Version 9.01 and all of the
latest service packs.
Note: CA ARCserve Backup does not support upgrading
BrightStor ARCserve Backup Version 9.01 in a cluster-aware
environment to this release. To upgrade to this release,
you must uninstall BrightStor ARCserve Backup for Windows
Version 9.01 and then install this release into a
cluster-aware environment.
- BrightStor Enterprise Backup Version 10.5 Service Pack 1
Note: CA ARCserve Backup does not support upgrading
BrightStor Enterprise Backup Version 10.5 Service Pack 1 in
a cluster-aware environment to this release. You must
uninstall BrightStor Enterprise Backup Version 10.5 Service
Pack 1 and then install this release into a cluster-aware
environment.
For all other releases, you must uninstall the existing
software version before you install CA ARCserve Backup r12.
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 the latest service
packs
- BrightStor ARCserve Backup r11.1, Service Pack 2
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 of the latest
service packs.
- BrightStor ARCserve Backup r11.1 and all of the latest
service packs.
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:
- When configuring the primary and member servers in a
domain, the CA ARCserve Backup domain name must be the same
on all machines in the domain. You must define the CA
ARCserve Backup domain name when you install the primary
server. You can reconfigure the domain name using the
Server Configuration Wizard to change the domain
membership. This wizard configures the CA ARCserve Backup
domain name for all of the domain.
- The Server Configuration Wizard also re-initializes the CA
ARCserve Backup database.
- When a standalone server is demoted to a member server in
the CA ARCserve Backup domain using the Server
Configuration Wizard, Job Status on the new member server
still shows the Database Protection Job, even though the
demotion succeeds. You must manually delete the Database
Protection Job.
- If you select a non-default IP address for a client agent
node, you must perform the following procedure to update
the IP address to the new address to allow you to add
machines using AutoDiscovery:
- On the agent machine, restart the discovery service.
- From the Backup Manager of the base server, delete the old
machine object.
- On the base server, restart the discovery service or launch
AutoDiscovery using dsconfig.exe.
- From the Backup Manager, add the machine with the new IP
address using AutoDiscovery.
- If you have a scheduled job in the queue, delete that job
and recreate it to ensure that it runs properly.
- Due to a NetBIOS limitation, computer names longer than 15
characters are truncated to 15 characters, including when
you set up a host server.
- If you install Windows Server 2003 Service Pack 1 using an
Emulex Fibre Channel Card, you must download the latest
Windows 2003 Storport HBA drivers from the Emulex website.
A problem with the Emulex driver released with Windows 2003
SP1 prevents CA ARCserve Backup from initializing correctly
unless you update the Emulex driver.
- If you use the Master Setup to install CA ARCserve Backup
remotely to a system in another Windows domain, you may
receive a message indicating that the installation failed
even when it is successful because the Master Setup cannot
accurately detect the activity on the remote machine in the
other domain because of a firewall or due to a lost network
connection. Check the installation status on the remote
machine to verify that the installation succeeded.
- If you enable both Success and Failure for Audit object
access under Local Security Policy, Local Policies, Local
Audit Policy, you may receive multiple Success Audit
messages under Security Events in the Event Viewer. To
avoid receiving multiple Success Audit messages, perform
the following procedure:
- Create a key called MessageEngine under the following
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\ARCserve
Backup\Base\Admin
- Create a DWORD value called Impersonate under the following
key and set it to 0:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\ARCserve
Backup\Base\Admin\MessageEngine
- Reboot the Windows system.
- NetWare Services no longer appear under the Network branch
in the Backup and Restore Managers and CA ARCserve Backup
only supports Client Agent for NetWare backups when
creating NetWare sessions from a CA ARCserve Backup for
Windows host.
- If you import a DLTWORM-capable media into a library that
has not converted to WORM yet, the Quick erase and Convert
to WORM media option is disabled. You must perform a full
inventory of tapes to enable this option.
- If you use WORM media as the destination for any
cross-platform jobs involving the CA ARCserve Backup for
UNIX Agent for Oracle or the CA ARCserve Backup for Linux
Agent for Oracle, these agents may not behave as expected.
Child jobs are submitted by the agent and because WORM
media is not supported on the UNIX or Linux agents, these
child jobs may use destinations other than the WORM media.
- Installing 32-bit components on a 64-bit machine generates
two copies of the file PortsConfig.cfg on the machine. The
PortsConfig.cfg file for the 64-bit components is in
c:\Program Files (x86)\CA\SharedComponents\ARCserve Backup
and the PortsConfig.cfg file for the 32-bit components is
in c:\Program Files \CA\SharedComponents\ARCserve Backup.
If you make changes to one, you must make the same changes
to the other, or the components may not be able to contact
one another.
- If you install agents on cluster nodes, do not back up the
physical nodes (the private drives C: and D:) or non-shared
disks through preferred share using the virtual server IP
address, because virtual servers can be moved from one node
to another. For example, if virtual server 1 resides on
physical node 1 and you backed up virtual server 1 through
preferred share, the non-shared drives on physical node 1
are also backed up. If you move virtual server 1 to
physical node 2, and perform a Restore to Original
Location, the non-shared drives from physical node 1 are
restored to physical node 2.
- The default TCP/IP protocol is recommended for ODBC
communication. If this setting is changed to Named Pipe
protocol, ODBC fails.
- Special characters in media files will interfere with RMAN
jobs. Avoid using special characters such as <,>,;,.
- Running RMAN script to backup remote CA ARCserve Backup
Agent for Oracle to CA ARCserve Backup Server may not work
if the remote machine was registered to CA ARCserve Backup
server with a fake name.
- Job redirection is no longer supported.
- When installing a SQL database, use case-sensitive
collation, as some sources may be missing in restore tree
view. For example, DB01, Db01 and db01 may not all show up
in restore tree view unless case-sensitivity is enabled.
- If you attempt to restore multiple tape items in a UNIX
session to your local Windows server, the restore job may
fail. To avoid this problem, select a full UNIX session or
just one tape item in a UNIX session to restore to your
local Windows server.
- The CA ARCserve Backup Manager Console may run very slowly
on some systems due to host name resolution problems. This
poor performance could be due to a NetBIOS and WINS Server
configuration problem. To remedy this problem, perform one
of the following corrective actions:
- Check Network Connections, TCP/IP Settings, WINS
Configuration first to ensure the Primary and Secondary
Servers are listed. If you cannot see the WINS settings,
enable one of the following registry switches on every CA
ARCserve Backup machine to use the DNS method of resolving
host names directly:
For 32-bit platforms:
HKLM\Software\ComputerAssociates\ARCServe
Backup\DisableNameResolveOptimize[DWORD]
For 64-bit platforms:
HKLM\Software\Wow6432Node\ComputerAssociates\CA ARCServe
Backup\DisableNameResolveOptimize [DWORD]
- If NetBIOS cannot be configured, add the primary server
line in the member's host file. The host file location is
%win%\system32\drivers\etc\hosts.
- Jobs run in the previous release of CA ARCserve Backup
(r11.5) will not appear in the Job History of r12 after
upgrade.
- When the Windows security policy is enabled on the machine
where CA ARCserve Backup is installed, an audit log is
recorded in the event log at the time of a system
application startup, such as Task Manager.
- If you are running the CA ARCserve Backup Manager Console
on a 64-bit system, you will be unable to view any
Removable Storage Manager (RSM) controlled devices for
enabling or disabling, because the Manager Console is a
32-bit application. To enable RSM controlled devices, do so
through the RSM Computer Management utility.
- When generating reports using the Report Manager, you must
store all Create now-based reports and all Schedule-based
reports in the default storage location. The default
storage location is in the following directory:
<ARCserve_HOME>/Reports.
- If you apply the license keys for two or more different CA
ARCserve Backup suites on a single ARCserve server, the
license count on the ARCserve server may not be correct. To
remedy this problem, apply the licenses that you require
and contact Technical Support at http://ca.com/support to
correct the license count.
- Effective with this release, the Tape Compare utility is no
longer supported.
- Broadcast Alerts do not function on systems running
Microsoft Server 2008 (Longhorn). This behavior is observed
because Microsoft Windows Server 2008 does not support
messaging service.
- In a NEC ClusterPro/ExpressCluster X1.0 for Windows
environment, if a backup was performed on a file in a
shared disk the restore of this file will fail if you
select the "Restore files to their original location(s)"
option. To perform a successful restore of this type of
file, you must specify the restore path instead of
selecting this option.
- CA ARCserve Backup does not support restoring a Job Queue
session to its original location using normal data recovery
processes.
To remedy this problem, you must perform a full disaster
recovery on the ARCserve server. CA ARCserve Backup lets
you perform a full disaster recovery of an ARCserve server
without installing the Disaster Recovery Option. To enable
this capability, you must complete the steps described in
Step 2 below. If the ARCserve server that you are
recovering is a primary server, you must complete the steps
in Step 3 below.
Important! You must restore the Job Queue to the ARCserve
primary or stand-alone server. Do not restore the Job Queue
to a member server of any ARCserve domain.
To restore an ARCserve server
- Back up the ARCserve Server
Perform full backup of the ARCserve server that you want to
restore.
Note: Ensure that the CA ARCserve Backup database and Job
scripts options are checked on the Operation tab of the
Backup Manager, Options dialog.
- Recover the ARCserve Server
- Reinstall the operating system on the ARCserve backup
server.
Note: Ensure that the hard disk partitions, hardware, and
the operating system (version, edition, and service pack)
configurations are identical to the configurations that you
backed up.
- Reinstall CA ARCserve Backup, agents, and options into the
same directory path as the original installation.
- After you install CA ARCserve Backup, open the Merge
utility and merge the media used for the full backup.
- After the merge is complete, open the Restore Manager and
locate the full backup sessions.
Select all backup sessions, excluding Disaster recovery
elements and the Job Queue.
Note: Ensure that the Restore files to their original
location(s) option is checked.
- From the Operation tab on the Restore Manager, Options
dialog, specify the Restore Registry Files and Event logs
and Disable Database Recording options.
- Right-click the ARCserve database object and select Agent
Option from the pop-up menu.
Click the Restore Options tab, check the Force Restore over
existing files option, and click OK.
- Start the restore job.
- When the restore job is complete, restart the ARCserve
server.
- Recover the Job Queue Session
- After the ARCserve server starts, open the Restore Manager,
locate, and select the Job Queue session.
- From the Destination tab, specify an alternate location to
restore the Job Queue session.
- Submit the restore job to restore the Job Queue session to
an alternate location.
Note: Ensure that the alternate location is an empty
directory.
- After the Job Queue session is restored to the alternate
location, open the Server Admin and stop all ARCserve
services.
- Access the alternate location and copy all Job Queue files
under the folder that you restored to the following
directory:
BAB_HOME\00000001.qsd
- From the Server Admin, restart all ARCserve services.
- If you are experiencing problems with media, consider the
following troubleshooting tasks:
- If you are using Library Quick Initialization, run Device
Configuration and disable this option when troubleshooting
CA ARCserve Backup hardware or device issues. This option
can be reconfigured after troubleshooting has been
completed.
- If your drives are inside a library, and you want to try
your tape in a different drive, the problem drive must be
in an OFF-LINE state. If CA ARCserve Backup did not
automatically status the drive to OFF-LINE when it detected
the media error, follow the instructions in Configuring
Library Devices to manually set the drive to OFF-LINE.
- After you restore the ARCserve database, you must perform
at least one full backup of the ARCserve database before
you perform an incremental or a differential backup. This
task ensures that ARCserve database backup sessions contain
the most current data. This task ensures that ARCserve
database backup sessions are current.
- 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 CA ARCserve Backup r12 from 11.5, we
recommend setting the value of key "LastObject" to empty so
that restore IDS does not fail.
- After upgrading to CA ARCserve Backup r12, the activity log
for completed jobs is not displayed if using Group by Job
or Group by Weeks options.
- After upgrading to CA ARCserve Backup r12, duplicate job
records are shown in DB manager for central DB member.
- If server is upgraded to CA ARCserve Backup r12, Job
History will not show Rotation or GFS jobs running prior to
upgrading.
- After upgrading to CA ARCserve Backup r12 from BrightStor
Enterprise Backup r10.5 or r11.1, and from CA ARCserve
Backup r11.5, 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 CA ARCserve Backup R12
servers. So if a CA ARCserve Backup R12 server 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 CA ARCserve Backup r12, Sybase databases
backed up in BrightStor Enterprise Backup 10.5.1 cannot be
restored.
- Effective with CA ARCserve Backup r12, the SkipDSAFiles
registry key is no longer applicable for SQL, Oracle or
Exchange database files.
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.
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 backing up 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 NetLogon 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 Lotus Domino
are known to exist in this release:
- If possible, avoid server names greater than 30 characters.
CA ARCserve Backup will truncate characters that exceed the
30-character-limit and replace the last two (characters 29
and 30) 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
"User1223334444555556666667777777" (32 characters), CA
ARCserve Backup will truncate the name down to 30 and
modify the last 2 remaining characters to
"User12233344445555566666677701" (30 characters).
- If you create another Domino Server with the same name as
the previous one, then CA ARCserve Backup will modify the
name to "User12233344445555566666677702 (30 characters).
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.
- The default installation path for the Agent for Microsoft
Exchange 2007 is different for local and remote
installations when the CA ARCserve Backup setup program is
run on Windows Server 2003 for x86 machines and the remote
installation is on the target Exchange 2007 Server:
- Local: C:\Program Files\CA\ARCserve Backup Agent for
Microsoft Exchange
- Remote: C:\Program Files (x86)\CA\ARCserve Backup Agent for
Microsoft Exchange
The following issues relating to the Agent for Microsoft
SharePoint are known to exist in this release:
- If a Microsoft SQL database is backed up using both the
Agent for Microsoft SQL Server and the Agent for Microsoft
SharePoint, the backup history for the database in the
SharePoint branch of Restore by Tree will only include
backups performed using the Agent for Microsoft SharePoint,
while the backup history for the database in the Microsoft
SQL Server branch of Restore by Tree lists all backups
performed using both agents. This issue also applies to the
Agent for Microsoft SQL Server.
- If the Agent for Microsoft SQL Server and the database
component of the Agent for Microsoft SharePoint are both
deployed on the same machine, the SharePoint databases are
included in whole-instance backups performed by the Agent
for Microsoft SQL Server. This issue also applies to the
Agent for Microsoft SQL Server.
- The username entered in the Agent for Microsoft SharePoint
Configuration Wizard must have administrative access to all
machines in the SharePoint Server farm.
- Performance may be slowed when backing up or restoring
search indexes, as these operations may consume 100% of
your CPU resources if the SharePoint server used satisfies
only the minimum hardware requirements for Microsoft
SharePoint Portal Server. See the Microsoft SharePoint
Portal Server Administrator's Guide for more information
about hardware requirements.
- Encryption is not supported on the CA ARCserve Backup r12
Agent for SharePoint 2007. Server side encryption only is
supported.
The following issues relating to the Agent for Microsoft
SQL Server are known to exist in this release:
- If a Microsoft SQL database is backed up using both the
Agent for Microsoft SQL Server and the Agent for Microsoft
SharePoint, the backup history for the database in the
SharePoint branch of Restore by Tree will only include
backups performed using the Agent for Microsoft SharePoint,
while the backup history for the database in the Microsoft
SQL Server branch of Restore by Tree lists all backups
performed using both agents. This issue also applies to the
Agent for Microsoft SharePoint.
- If the Agent for Microsoft SQL Server and the database
component of the Agent for Microsoft SharePoint are both
deployed on the same machine, the SharePoint databases are
included in whole-instance backups performed by the Agent
for Microsoft SQL Server. This issue also applies to the
Agent for Microsoft SharePoint.
- Installing 32-bit components on a 64-bit machine generates
two copies of the file PortsConfig.cfg on the machine. The
PortsConfig.cfg file for the 64-bit components is in
c:\Program Files\CA\SharedComponents\CA 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.
- 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 remote SQL database using
the TCP/IP protocol, the TCPtimeout parameter defines 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 SQL Agent TCPtimeout key can be found on the CA
ARCserve Backup Server machine under:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\Base\Task\Common\DBAgentsSettings
- The Microsoft Windows 2003 SharePoint database is stored in
a Microsoft SQL Server Desktop Engine (MSDE) instance. The
SharePoint instance does not support SQL-native
authentication. You must use Windows authentication for
this database instance.
- Several MSDE-based applications do not include a System
Administrator account. The application vendor may provide a
backup user with only Backup Operator rights. These MSDE
instances must be backed up using Named Pipes. If you are
not certain whether your MSDE instance has this
restriction, contact your application vendor.
If 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 Backup Agent Remote Service.
- If you are performing a remote backup, File and Printer
Sharing for Microsoft Networks must be enabled on the agent
machine you are backing up.
- To support pass-through authentication of account logon
events for computers in a domain, the NetLogon service must
be started.
- If you are using the current version of CA ARCserve Backup
and CA ARCserve Backup Agent for Microsoft SQL Server to
restore a backup made using BrightStor ARCserve 2000 or an
older version of BrightStor ARCserve Backup, and you are
using the Named Pipes protocol, perform the following
procedure on the computer running the BrightStor ARCserve
Backup Server:
- Open the Registry Editor and select the key:
KEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\
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 local or TCP-based backup and
restore operations, you must have system administrator
rights for Microsoft SQL Server. This is a Microsoft
requirement.
- If you uninstall a Microsoft SQL Server or MSDE instance,
some components used by other Microsoft SQL Server or MSDE
instances on the machine may be deregistered, including the
Virtual Devices mechanism used to perform backups. If this
occurs, the agent generates Backup Agent Error 511 ("Error
creating Virtual Device Interface: COM class not found")
within the error E8604 ("Failed to Start Backup"), or E8605
("Failed to Start Restore"). To address this error, perform
the following procedure:
- 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.
- Effective with this release, database files are skipped
during a backup job. In the previous release, the
SkipDSAFiles registry value could be set to include skipped
files, but in CA ARCserve Backup r12, this key no longer
controls the backup of database files. Instead, you may set
the BackupDBFiles registry key to backup only SQL server
database files:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA
ARCServeBackup\Base\Task\Backup
Value Name: BackupDBFiles
Type: DWORD
Value: 0 to skip, 1 to backup (0 is default)
- 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.
The following issues relating to Longhorn Support -
Unsigned Binaries are known to exist in this release:
- The following CA binaries have not been signed for this
release:
- \ Shared Components \ ca_lic \ lic98upg.dll
- \ ARCserve Backup Client Agent for Windows \ ws_backup.dll
- \ ARCserve Backup Client Agent for Windows \ xoctl.dll
- \ ARCserve Backup Diagnostic \ Cazipxp.exe
- \ Shared Components \ ETPKI \
- \ Shared Components \ Scan Engine \
- The following Non-CA binaries are installed with CA
ARCserve Backup. These have not been signed for this
release:
- \ Shared Components \ JRE
- \ ARCserve Backup \ CFX2032.DLL (Software FX, Inc.)
- \ ARCserve Backup \ GX1142R.dll (ClassWorks)
- \ ARCserve Backup \ roboex32.dll (Blue Sky Software
Corporation)
- \ ARCserve Backup \ zlib1.dll
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.
Microsoft Volume Shadow Copy Service (VSS)
In CA ARCserve Backup r12, the Agent for Open Files now
includes support for Microsoft Volume Shadow Copy Service
(VSS). The following issues relating to Microsoft VSS are
known to exist:
- Full backups of Microsoft SQL Server 2005 are possible, but
not differential or incremental backups.
- In Windows 2003 R2, the DFS Replication Service Writer
appears when you expand the machine. In Windows 2008
(Longhorn), DFS Replication is part of the system state.
Therefore, if you wish to backup DFS Replication in
Longhorn, you must back up the system state.
Oracle Volume Shadow Copy Service (VSS)
In CA ARCserve Backup r12, 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:
- Backups (of older version) will fail if you have more than
one version of Oracle installed on the same machine. If you
need to protect an older version instance, make sure that
the "PATH" environment does not contain the new version bin
directory at %ORACLE_HOME%\bin.
- Archive log backup will fail if you use the default Archive
Log path, %ORACLE_HOME\RDBMS. Oracle does not recommend
using the default path.
- 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.
- Effective with this release, the SkipDSAFiles registry key
is no longer applicable.
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.
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.
The following issues relating to the Disaster Recovery
Option are known to exist in this release:
- When you run a remote recovery and the base is Windows XP
with SP2, you must use different configurations depending
on the version of CA ARCserve Backup used to create your
full backup:
- When performing Disaster Recovery on primary server, CA
ARCserve Backup may fail to recover the database if the
backup server is the member server. When ca_recoverdb
submits the job to the member server, the job engine of the
primary server is unable to launch it because the member
server is not a member of the domain at the moment. We
recommend using a cahost switch to move tape from the
member server to the primary server and then submit the
recover command.
- Disaster Recovery restore jobs running on IA64 systems may
display this error even though the tape library is
connected and media is present: "Media not found. Insert
media." The problem appears limited to IA64 systems running
Windows 2003 with the Emulex LP10000 FC card.
- One Button Disaster Recovery (OBDR) scans the first OBDR
device found by the Tape Engine. Ensure the OBDR tape is in
the first tape drive to restore successfully.
- After Disaster Recovery is completed, the size of the last
partition recovered can be expanded from the original size
by as much as 8 MB. The problem occurs if there is free
space at the end of the last partition on the disk being
recovered.
- Disaster Recovery does not support Scan and Replace
functionality for CA ARCserve Backup database sessions.
- For Microsoft SQL-hosted CA ARCserve Backup databases, you
may find error messages recorded in event log after
performing a Disaster Recovery, even though no problems
exist in the Disaster Recovery process.
- When CA ARCserve Backup server (Primary or Member) is
configured in Cluster with the Disaster Recovery Option
installed, the "Alternate Location for DR Information"
setting may not be stored when the cluster is ready after
installation. Reconfigure this setting by running the DR
Book Kit Wizard Utility from Active Node and re-enter it.
- Use of a Japanese USB Keyboard during floppy disk disaster
recovery is not supported on Windows 2000 systems. Japanese
USB keyboards may be used during bootable CD disaster
recovery on such systems.
- During Disaster Recovery from a bootable CD, you may be
prompted to insert a disk into the floppy drive before
inserting the Machine Specific Disk. It is safe to ignore
this message and click OK to continue.
- The database engine will not start automatically after
successful recovery of the CA ARCserve Backup database.
Upon the first reboot after performing Disaster Recovery of
the CA ARCserve Backup server hosting the ARCserve
database, you must restart the database engine. Do so
through the CA ARCserve Backup Manager Console.
- When performing Disaster Recovery on Microsoft Windows XP,
Windows 2003 or Windows 2008 systems, the Create Folder
button may not work when attempting to save logs. To save
logs, create a new folder using the mkdir command with the
Open Console button or save logs into an existing folder.
- Before you perform Disaster Recovery on a Windows 2003
machine, use the Disaster Recovery Boot Kit Wizard to
create a CD that contains the following:
- A password created in the Global Options screen applies to
all sessions backed up at that time. When performing
Disaster Recovery, you must enter that password for each
session you are restoring. No "global" method of entering
this password exists at Disaster Recovery time.
- Tape device names may not appear correctly when executing
DRSCANSESSION.EXE. DRSCANSESSION.EXE is only for Windows
2000 systems.
- When using DRSCANSESSION.EXE to update machine specific
data by scanning tape, note that Disaster Recovery will not
restore the job queue session, the SQL DR Element session,
or the CA ARCserve Backup database to older versions.
- If your system is configured with a number of volumes
mounted via mount points, Disaster Recovery cannot be
performed correctly. You must format and restore data
manually.
- When a local backup of 32-bit Windows 2000, Windows XP, or
Windows 2003 systems is performed with the Encryption at
agent side option selected, please note that the system
state session is not actually encrypted. Instead, it is
password protected. At Disaster Recovery time, the system
state session is not considered an encrypted session and
also will not have an enabled password button. You will be
prompted for session password at data recovery time and
given three opportunities to enter the correct password.
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 NAS tapecopy sessions
via NDMP connection. NAS tapecopy sessions work only in NAS
SAN DDS environment.
- To use DDS on EMC Celerra, you must set the
NDMP.scsiReserve parameter to 0 on the data mover. This
parameter is available starting with release 5.2.15.0. For
more information about this issue, see EMC's Celerra
documentation.
- To allow CA ARCserve Backup to connect to Network Appliance
filers through Preferred Shares, you must create an ADMIN$
share for the volume containing the /ETC folder on the NAS
server.
Note: Do not back up NAS devices through Preferred Shares,
as it does not utilize the NAS-attached backup device or
the NDMP protocol for proper NAS operating system backup
procedures.
- Before you restore a differential or incremental NAS
session, ensure that the previous full backup has been
restored:
- 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:
- Optical Library Option command line commands are not
supported for the Device Manager.
- The option does not support multistreaming. If you enable
multistreaming, you must install the Enterprise Module
Option.
- If you receive the error message "Windows - No Disk, There
is no disk in the drive. Please insert a disk into drive
\Device\HardDiskx\DRx," you must exclude the tapeeng.exe
process from scanning by eTrust. To exclude the tapeeng.exe
process from scanning, perform the following procedure:
- In the Realtime Monitor Options dialog of eTrust, click the
Filters tab.
- On the Filters tab, in the Exclusions group box, click the
Process button. The Exclude Processes dialog opens.
- In the Exclude Processes dialog, enter tapeeng.exe in the
Enter a process name field and click Add. The tapeeng.exe
process appears in the List of Excluded Processes.
- Click OK to close the Exclude Processes dialog and click OK
to exit the Realtime Monitor Options dialog.
- Tape Engine may corrupt the device view structure of RSM.
Some storage devices cannot be used by the Tape Engine and
RSM simultaneously. To restore the device view structure of
the removable storage service, stop the Tape Engine and
restart the removable storage service.
- 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 will automatically
assume the tapeKey of the destination tape is the same as
the source tape and view it as if only one tape exists. As
a result, any subsequent operation on the source tape will
also take effect on the destination tape.
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 will
automatically assign a different random ID to the
destination tape and ensure 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.
- If you want to import a cleaning tape, you must import it
to the cleaning slot you specified during Device
Configuration. If you import it to a different slot, you
will receive unrecognized media errors.
- If you are experiencing problems with media, consider the
following troubleshooting tasks:
- If you are using Library Quick Initialization, run Device
Configuration and disable this option when troubleshooting
CA ARCserve Backup hardware or device issues. This option
can be reconfigured after troubleshooting has been
completed.
- If your drives are inside a library, and you want to try
your tape in a different drive, the problem drive must be
in an OFF-LINE state. If CA ARCserve Backup did not
automatically status the drive to OFF-LINE when it detected
the media error, follow the instructions in Configuring
Library Devices to manually set the drive to OFF-LINE.
The following issues relating to the SAN Option are known
to exist in this release:
- Mixed SAN environments are no longer supported.
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\CurrentControSet\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 Enterprise Option for
SAP R/3 for Oracle are known to exist in this release:
- SAP 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.
- Add the IP address of the Agent and base machines to the
hosts file.
- BACKINT supports only 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.
- The option only supports the BACKINT command interface.
- The option does not support server Side Encryption and
Secure Migration.
The following issues relating to the Enterprise Option for
StorageTek ACSLS are known to exist in this release:
If CA ARCserve Backup detects port 111 conflicts,
indicating that it is using the same port number for the CA
Remote Procedure Call server service as a previously
installed portmapper, 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 Remote
Procedure Call server service to Manual. If you have
installed CA ARCserve Backup in a Microsoft Cluster
Services environment, change the Automatic status of the CA
Remote Procedure Call server service to Disabled. This
enables you to avoid similar port conflicts after the
system has completed the boot process.
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 section provides information about issues
relating to the documentation for CA ARCserve Backup that
are known to exist in this release:
Administration Guide
- In the topic Merge Utility - Database Global Options, the
Administration Guide contains incorrect descriptions of the
database options.
Note: This issue also applies to the online help.
The correct descriptions are as follows:
- Merge Detail Information--Lets you merge all details,
including job and session information.
- Merge Session Headers Only--Lets you merge only header
information, such as job and session data.
- In the topic Microsoft SQL Server Backup Options, the
Administration Guide contains a description of option that
was not implemented in this release.
Note: This issue also applies to the online help.
- The option Do not automatically upgrade Microsoft SQL
Server Partial Backup to Database Full Backup if Database
Full not found is not functional.
- In the topic Job Engine Configuration, the Administration
Guide contains an incomplete description of the Buffer Size
(K Bytes) option.
Note: This issue also applies to the online help.
The complete description of the Buffer Size (K Bytes)
option is as follows:
- Buffer Size (K Bytes)--Defines the buffer size used by CA
ARCserve Backup. All computers behave differently. Factors
affecting their behavior can be related to backup server
hardware, the total size of the backup job, and the number
child jobs that a backup job spawns. You can increase or
decrease the size of the buffer to optimize your system's
performance while performing a backup.
Default value: 256 KB
Increasing or decreasing the buffer size does not necessary
improve backup and restore performance. For example, if the
backup server has abundant system resources, such as a
large amount memory, access to a fast network, fast disk
I/O, increasing the buffer size can increase the system's
backup and restore performance. Conversely, if the backup
server has limited system resources, reducing the buffer
size can increase the system's backup and restore
performance.
Note: For a typical server, the best practice is to apply
the default value of the buffer size.
- In the topic Restore a Remote Agent on a System without the
Disaster Recovery Option, the Administration Guide contains
incorrect procedural information.
Note: This issue also applies to the online help.
The correct procedure to Restore a Remote Agent on a System
without the Disaster Recovery Option is as follows:
Important! This procedure does not apply to ARCserve backup
servers.
- Start the computer you want to recover, using the Windows
operating system CD.
- Create the partitions that are necessary for installing the
operating system. Other disk partitions/volumes can be
restored manually after the operating system is installed.
For dynamic disk configuration, it must be restored after
the operating system is installed.
- Install the operating system and verify that the host name
is the same as the original system.
- Restore the remaining disk/volume configuration, disk
partition layout, dynamic disk volumes, and so on.
Note: The volume drive letter should be the same as the
original system.
- Install the device drivers which are not included on the
operating system CD. This includes SCSI/RAID/FC drivers and
network adapter drivers.
- Configure the network and verify that all configurations
are the same as the original system.
- Apply the operating system patch.
Note: This step is necessary when the system is going to be
connected to the network.
- Install the same antivirus software that was running when
the last backup completed and update to the latest patch.
Note: This step is necessary when the system is going to be
connected to the network.
- Install all applications same as original system.
- Install the CA ARCserve Backup Client Agent for Windows.
- Install all CA ARCserve Backup database agents, application
agents, or both.
- If the restored system does not display in the Backup
Manager Source directory tree, add the restored system to
the proper source node list.
- From the Restore Manager, specify the Restore by tree
restore method and submit the restore job to restore the
system.
- The following topics in the Administration Guide contain
incomplete information:
After you complete the steps in the above procedures, you
must also perform the following additional steps:
- Run the Microsoft SQL Agent Account Configuration utility
to update the ODBC communication settings if any of the
following conditions are met:
- The server is the primary server with a locally installed
CA ARCserve Backup database,
- The server is a standalone server with a locally installed
CA ARCserve Backup database,
- The server is the primary server, a standalone server, or a
member server AND CA ARCserve Backup database or the Agent
for Microsoft SQL Server is installed on the same machine.
To start the Microsoft SQL Agent Account Configuration
utility, click Start from the Windows Taskbar, choose All
Programs, CA, ARCserve Backup, Microsoft SQL Agent Account
Configuration.
After you start the utility, follow the prompts and accept
all recalled settings.
- Open the Job Status Manager and complete the following
tasks:
- Delete and re-create the Database Pruning Job.
For information on re-creating the Database Pruning Job,
see the Online Help.
- Modify the Database Protection Job and any other backup
jobs that are set to run on the renamed server, to update
the Staging and Destination locations.
For information on modifying the Database Protection Job,
see the Online Help.
- Perform a new Full Backup of the CA ARCserve Backup
Database.
For more information about renaming systems hosting
Microsoft SQL Server databases, see the following topics on
the Microsoft Developer Network:
Agent for Open Files Guide
Client Agents Guide
Command Line Reference Guide
Implementation Guide
- In the topic Backward Compatibility, the Implementation
Guide incorrectly states that this release of the CA
ARCserve Backup server component can back up data using
agents from BrightStor ARCserve Backup r9.0, Service Pack 1.
This should state:
This release of the CA ARCserve Backup server component can
back up data using agents from BrightStor ARCserve Backup
r9.0, Service Pack 2.
Note: This issue also applies to the online help.
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.
Online Help
- Error E1002, Error E1003, Error E1004, Error E1005, Error
E1006, E1007, Error E1008, Error E1009, Error E1010, Error
E1201, Error E1202, Error E1203, Error E1204, Error E1205,
Error E1206, and Error E1207 should state the action as the
following:
Wait a few minutes and then execute the CSTOP command to
stop all CA ARCserve Backup services, and then execute the
CSTART command to restart all CA ARCserve Backup services.
If the problem persists, contact Technical Support at http://ca.com/support for online technical
assistance and a complete list of locations, primary
service hours, and telephone numbers.
- Error E1208, Error E1209, and Error E1210 should state the
action as the following:
Check that the DLL file mentioned exists in the
ARCserve_HOME directory.
If the problem persists, contact Technical Support at http://ca.com/support for online technical
assistance and a complete list of locations, primary
service hours, and telephone numbers.
- Error E1516, Warning W1519, Warning W1520, Error E1524,
Error E1527, Error E1529, Error E1530, Error E1532, Error
E1533, and Error E2239 incorrectly states "Ensure the
following logs are available from the CA ARCserve Backup
installation path \ LOG directory:"
This should state:
Use the Diagnostic Wizard to gather information for the
following logs, which are located in the CA ARCserve Backup
installation path \ LOG directory:
- Error E3302 should be Warning W3302.
- Error E3555 should be included in the online help and state
the following:
All licenses for <agent type> used up on ARCserve server
<primary server name>. Please get new licenses for <agent
type> for machine <agent node name>.
Module:
Task Engine
Reason:
The license for the specified agent expired or usage
limitation exceeded.
Action:
Ensure that you have obtained and installed the appropriate
license information on the system.
- Error E8058 should be included in the online help and state
the following:
Mapping with a tape failed. Use Device Configuration Wizard
to manually assign the drives to the library.
Module:
Tape Engine
Reason:
This error occurs when you fail to map all the drives in a
library using a tape. Either the tape is incompatible with
the drives, or the tape was misplaced somewhere in the
library.
Action:
For online technical assistance and a complete list of
locations, primary service hours, and telephone numbers,
contact Technical Support at http://ca.com/support.
- Error E8059 should be included in the online help and state
the following:
Library failed to get element addresses during
initialization. [Device Number] [Library inquiry] [Library
serial number]
Module:
Tape Engine
Reason:
This error occurs when the library fails to return the
element addresses of the drives, slots, library robotics
and import/export slots (if applicable to the library).
Action:
Ensure that the library is online and working properly. The
library may need to be reset.
- Error E4102 should state the action as the following:
- Check the Database Error Codes (db_error_code).
- Make sure that the SQLE or SQL service is running on the
Primary server.
- Check the network connection to the primary server.
- Verify the ARCserve system account and ARCserve database
are properly configured. Otherwise, correct them using the
ARCservecfg.exe utility from the ARCserve installed folder.
- Send the cadblog.log from ARCserve Home\Log folder to
support.
- Error E5110 should be Warning W5110.
- Error E12002 should state the action as the following:
Ensure that you have obtained and installed the appropriate
license information on the system. For information on
licensing your product, see Licensing and Registration.
- In the topic Schedule Custom Reports, Step 3 should state:
3. Specify the name and format type (.xml, .csv and .txt)
for the report.
You can view the .xml file from the Report Manager. You can
view the .csv and .txt files from the Reports directory
located at ARCserve_HOME\Reports.
- In the topic Session User Name and Password, the following
sentence should be removed:
To view all media sequences for a session, select the
session and click Show All Media.
The following section provides information regarding fixes
included in previous releases of CA ARCserve Backup that
are now included in r12.
The complete list of published bug fixes for CA ARCserve
Backup r12 can be found through published solutions on
SupportConnect.
| 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 |
|
CA ARCserve Backup r12 includes all the security
vulnerability enhancements related to Vulnerability Note
VU#953860.
Access to CA ARCserve Backup r12 is restricted to Windows
Administrators and Backup Operators only to prevent such
problems.
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, r12 has been
internationalized and translated into the following
languages, in addition to the English release:
- Brazilian-Portuguese
- French
- German
- Italian
- Japanese (JIS2004 is not supported)
- Simplified Chinese
- Spanish
- Traditional Chinese
If you run this product on a language environment not
included in the list, you may experience problems.
For online technical assistance and a complete list of
locations, primary service hours, and telephone numbers,
contact Technical Support at http://ca.com/support.
Copyright © 2008 CA.
All rights reserved.