Arcserve® Backup r16 Readme
1.0 Welcome
1.1 Arcserve Backup r16 Service Pack 1
2.0 Operating System Support
2.1 Supported Operating Systems for the Base Product
2.1.1 Supported Virtualization Platforms for Arcserve Backup
2.1.2 Supported Cloud Vendors for the Arcserve Backup Base Product
2.2 Supported Operating Systems for Arcserve Backup and Arcserve Replication (formerly, CA XOsoft) Integration-r16
2.3 Supported Operating Systems for the Arcserve Backup Client Agents
2.4 Supported Operating Systems for the Agent for Informix
2.5 Supported Operating Systems for the Agent for Lotus Domino
2.6 Supported Operating Systems for the Agent for Microsoft Exchange Server
2.7 Supported Operating Systems for the Agent for Microsoft SharePoint Server
2.8 Supported Operating Systems for the Agent for Microsoft SQL Server
2.9 Supported Operating Systems for Arcserve Backup for Small Business Server Editions
2.10 Supported Operating Systems for the Agent for Oracle (UNIX/Linux)
2.11 Supported Operating Systems for the Agent for Oracle (Windows)
2.12 Supported Operating Systems for the Agent for Open Files
2.13 Supported Operating Systems for the Agent for Sybase
2.14 Supported Operating Systems for the Agent for Virtual Machines
2.15 Supported Operating Systems for the Disaster Recovery Option
2.16 Supported Operating Systems for the Enterprise Module
2.17 Supported Operating Systems for the Enterprise Option for SAP R/3 for Oracle (Windows)
2.18 Supported Operating Systems for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
2.19 Supported Operating Systems for the Image Option
2.20 Supported Operating Systems for the NDMP NAS Option
2.21 Supported Operating Systems for the Storage Area Network (SAN) Option
2.22 Supported Operating Systems for SRM
2.23 Supported Operating Systems for the Tape Library Option
2.24 Supported Operating Systems for Arcserve Backup UNIX and Linux Data Mover
2.25 Supported Operating Systems for Arcserve Backup Dashboard
2.26 Supported Operating Systems for the Arcserve Backup Global Dashboard
2.27 Supported Operating Systems for Arcserve Backup Infrastructure Visualization
3.0 System Requirements
3.1 System Requirements for the Arcserve Backup Base Product
3.2 System Requirements for Arcserve Backup and Arcserve Replication Integration-r16
3.3 System Requirements for the Arcserve Backup Client Agents
3.4 System Requirements for the Agent for Informix
3.5 System Requirements for the Agent for Lotus Domino
3.6 System Requirements for the Agent for Microsoft Exchange Server
3.7 System Requirements for the Agent for Microsoft SharePoint Server
3.8 System Requirements for the Agent for Microsoft SQL Server
3.9 System Requirements for the Arcserve Backup Small Business Server Editions
3.10 System Requirements and Oracle Database Support for the Agent for Oracle (UNIX/Linux)
3.11 System Requirements for the Agent for Oracle (Windows)
3.12 System Requirements for the Agent for Open Files
3.13 System Requirements for the Agent for Sybase
3.14 System Requirements for the Agent for Virtual Machines
3.15 System Requirements for the Central Management Option
3.16 System Requirements for the Disaster Recovery Option
3.17 System Requirements for the Enterprise Module
3.18 System Requirements for the Enterprise Option for IBM 3494
3.19 System Requirements for the Enterprise Option for SAP R/3 for Oracle (Windows)
3.20 System Requirements for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
3.21 System Requirements for the Enterprise Option for StorageTek ACSLS
3.22 System Requirements for the Image Option
3.23 System Requirements for the NDMP NAS Option
3.24 System Requirements for the Storage Area Network (SAN) Option
3.25 System Requirements for the Tape Library Option
3.26 System Requirements for the Arcserve Backup UNIX and Linux Data Mover
3.27 System Requirements for Arcserve Backup Dashboard
3.28 System Requirements for the Arcserve Backup Global Dashboard
3.29 System Requirements for Arcserve Backup Infrastructure Visualization
3.30 System Requirements for Arcserve Backup Infrastructure Global Visualization
4.0 Installation Considerations
4.1 Installation Considerations for the Arcserve Backup Base Product
4.2 Installation Considerations for the Agent for Microsoft Exchange Server
4.3 Installation Considerations for the Agent for Microsoft SharePoint Server
4.4 Installation Considerations for the Agent for Microsoft SQL Server
4.5 Installation Considerations for the Agent for Open Files
4.6 Installation Considerations for the Media Management Option (MMO)
4.7 Installation Considerations for the Enterprise Module
4.8 Installation Considerations for the UNIX and Linux Data Mover
4.9 Installation Considerations for the Arcserve Backup Patch Manager
4.10 Installation Considerations for the Arcserve Backup Agent for Virtual Machines
4.11 Installation Considerations for the Client Agents
4.12 Installation Considerations for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
5.0 Upgrade Considerations
5.1 Upgrade Considerations for the Arcserve Backup Base Product
6.0 General Considerations
7.0 Supported Upgrade Paths
7.1 Backward Compatibility
8.0 Known Issues
8.1 Known Issues for the Base Product
8.2 Known Issues for Upgrading to Arcserve Backup
8.3 Known Issues for the Client Agents
8.4 Known Issues for Arcserve Backup Licensing
8.5 Known Issues for the Agent for Informix
8.6 Known Issues for the Agent for Lotus Domino
8.7 Known Issues for the Agent for Microsoft Exchange Server
8.8 Known Issues for the Agent for Microsoft SharePoint Server
8.9 Known Issues for the Agent for Microsoft SQL Server
8.10 Known Issues for the Agent for Open Files
8.10.1 Microsoft Volume Shadow Copy Service (VSS)
8.10.2 Oracle Volume Shadow Copy Service (VSS)
8.11 Known Issues for the Agent for Oracle (Windows)
8.12 Known Issues for the Agent for Oracle on UNIX and Linux Platforms
8.13 Known Issues for the Agent for Sybase
8.14 Known Issues for the Agent for Virtual Machines
8.15 Known Issues for the Enterprise Option for AS400
8.16 Known Issues for the Enterprise Option for IBM 3494
8.17 Known Issues for the Enterprise Option for SAP R/3 for Oracle (Windows)
8.18 Known Issues for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
8.19 Known Issues for the Enterprise Option for StorageTek ACSLS
8.20 Known Issues for the Disaster Recovery Option
8.21 Known Issues for Dashboard
8.22 Known Issues for the Arcserve Backup Global Dashboard
8.23 Known Issues for the Image Option
8.24 Known Issues for the NDMP NAS Option
8.25 Known Issues for the Storage Area Network (SAN) Option
8.26 Known Issues for the Tape Library Option
8.27 Known Issues for Central Agent Admin
8.28 Known Issues for Displaying Non-English Characters
8.29 Known Issues for Documentation
8.30 Known Issues for the Arcserve Backup Infrastructure Visualization
8.31 Known Issues for the Microsoft Hyper-V VSS Writer
9.0 Included Fixes
10.0 Arcserve Backup r16 SP1
10.1 Supported Operating Systems
10.2 Installation Considerations
10.3 Known Issues
10.4 Arcserve Backup r16 Service Pack 1
10.4.1 Additional Information for Included Fixes
10.5 Document Changes
11.0 Language Certifications
1.0 Welcome
Welcome to the Arcserve Backup for Windows r16 Readme. This
readme contains issues and other information discovered
after publication including a complete list of the known
issues for this release.
For details about how the features and enhancements for
this release might affect you, see the Arcserve Backup
Release Summary. You can access the most up-to-date
released product documentation (Online Help and PDFs) from
the Arcserve Backup website at Arcserve Support.
Arcserve Backup supports the following suites:
- Arcserve Backup for Windows Essentials Module
- Arcserve Backup Guest Based Virtual Machines Agent Bundle
- Arcserve Backup for Windows Advanced Module
- Arcserve Backup for Windows Standard Module
- Arcserve Backup for Windows Enterprise plus Module
1.1 Arcserve Backup r16 Service Pack 1
This Readme file contains information about Arcserve Backup
r16 Service Pack 1. For information about Supported
Operating Systems, Installation Considerations, Known
Issues, Included Fixes, and Documentation Changes that
affect only Arcserve Backup r16 SP 1, see Arcserve Backup
r16 SP1.
2.0 Operating System Support
The following topics provide information about the
supported operating systems for the Arcserve Backup base
product, agents and options. For the most current
information regarding supported operating systems, see the
compatibility matrix on Arcserve Support.
2.1 Supported Operating Systems for the Base Product
You can install the Arcserve Backup base product on the
following operating systems. For the most current
information regarding supported operating systems, see the
compatibility matrix on Arcserve Support.
Windows Server 2008 R2
- R2 Standard (x64)
- R2 Enterprise (x64), R2 Enterprise (x64) with Service Pack 1
- R2 Data Center (x64)
- Windows Web Server 2008 R2
- R2 Core (x64) (Arcserve Backup Member Server, Arcserve
Backup Disaster Recovery Option, Arcserve Backup Enterprise
Module with ACSLS and IBM 3494 installation disabled,
Arcserve Backup Agent for Open Files, Arcserve Backup Agent
for Virtual Machines, Arcserve Backup Client Agent for
Windows)
- Failover Cluster support (Windows Server 2008 Enterprise,
Windows Server 2008 Standard only). Install locally and
follow instructions for cluster environment.
Windows Server 2008 SP1, SP2
- R2 Standard and Core Editions (x64) (Arcserve Backup Member
Server, Arcserve Backup Disaster Recovery Option, Arcserve
Backup Enterprise Module with ACSLS and IBM 3494
installation disabled, Arcserve Backup Agent for Open
Files, Arcserve Backup Agent for Virtual Machines, Arcserve
Backup Client Agent for Windows)
- Enterprise (x86, x64)
- Standard (x86, x64)
- Data Center (x86, x64)
- Web Server (x86, x64)
- Itanium Based systems
- Core (x86, x64) (Arcserve Backup Member Server, Arcserve
Backup Client Agent for Windows, Arcserve Backup Agent for
Open Files, Arcserve Backup Agent for Virtual Machines)
- Failover Cluster support (Windows Server 2008 Enterprise,
Windows Server 2008 Standard only). Install locally and
follow instructions for cluster environment.
Windows Server 2008 Foundation
- x64 systems: (Arcserve Backup Server, Arcserve Backup
Enterprise Option, Arcserve Backup Tape Library Option,
Arcserve Backup Storage Area Network Option, Arcserve
Backup Agent for Open Files, Arcserve Backup Disaster
Recovery Option)
- R2 (x64) systems: (Arcserve Backup Server, Arcserve Backup
Enterprise Option, Arcserve Backup Tape Library Option,
Arcserve Backup Storage Area Network Option, Arcserve
Backup Agent for Open Files, Arcserve Backup Disaster
Recovery Option)
Windows Small Business Server (SBS) 2003
Windows Small Business Server (SBS) 2008
- Standard Edition (x64 only) (Arcserve Backup Server,
Arcserve Backup Manager Console, Arcserve Backup Client
Agent for Windows, Arcserve Backup Agent for Open Files,
Arcserve Backup Agent for Microsoft Exchange Server, and
Arcserve Backup Agent for Microsoft SharePoint Server)
- Premium Edition (x64 only) (Arcserve Backup Server,
Arcserve Backup Manager Console, Arcserve Backup Client
Agent for Windows, Arcserve Backup Agent for Open Files,
Arcserve Backup Agent for Microsoft Exchange Server,
Arcserve Backup Agent for Microsoft SharePoint Server, and
Arcserve Backup Agent for Microsoft SQL Server)
Windows Small Business Server (SBS) 2011
Windows Storage Server 2008
- x86 and x64: (Arcserve Backup Server, Arcserve Backup Tape
Library Option, Arcserve Backup Storage Area Network
Option, Arcserve Backup Network Attached Storage Option,
Arcserve Backup Agent for Open Files, Arcserve Backup
Disaster Recovery Option)
Windows Server 2003
- R2 Standard Edition (x86, x64) or R2 Service Pack 2
- R2 Enterprise Edition (x86, x64, IA64) at minimum Service
Pack 1 or Service Pack 2
- Standard Edition (x86, x64) at minimum Service Pack 1 or
Service Pack 2
- Web Edition (x86 only) at minimum Service Pack 1 or Service
Pack 2
- Datacenter (x86, x64)
- Storage Server R2 Service Pack 1 or Service Pack 2
- Small Business Server (SBS) R2 Service Pack 1 or Service
Pack 2
- Failover Cluster Server (x86, x64, and IA64)
The Arcserve Backup base product is not supported on
Windows Vista, Windows 7, and Windows XP systems. However,
the following Arcserve Backup components are supported:
Windows Vista (x86 and x64) SP1, or SP2
- Arcserve Backup Client Agent for Windows
- Arcserve Backup Agent for Virtual Machines
- Arcserve Backup Agent for Open Files
- Arcserve Backup Manager Console only (the Arcserve Backup
Server is not supported)
- Arcserve Backup Agent Deployment
Windows 7 Professional, Ultimate and Enterprise Editions
(x86 and x64)
- Arcserve Backup Manager Console only (the Arcserve Backup
Server is not supported)
- Arcserve Backup Client Agent for Windows
- Arcserve Backup Agent for Virtual Machines
- Arcserve Backup Agent for Open Files
- Arcserve Backup Agent Deployment
2.1.1 Supported Virtualization Platforms for Arcserve Backup
Arcserve Backup base product lets you protect virtual
machines running on the following virtualization platforms:
- VMware ESX Server (x86 and x64) version 3.0, 3.0.1, 3.0.2,
3.0.3
- VMware ESX Server 3.5, Update 1, Update 2, Update 3, Update
4, Update 5
- VMware ESXi version 3.5, Update 1, Update 2, Update 3,
Update 4, Update 5
- VMware ESX Server 4.0 (vSphere), Update 1, Update 2
- VMware ESX Server 4.1 (vSphere)
- VMware ESX Server 2.5, 2.5.4
- VMware GSX Server version 3.0, 3.1
- VMware Server version 1.0.1, 1.0.4, 2.0
- VMware Workstation version 4.0, 4.5, 5.0, 5.5, 6.0, 7.0
- Microsoft Virtual PC 2007 (x86 only)
- Microsoft Virtual Server 2005 R2 SP1 (x86 and x64)
- Microsoft Hyper-V Server 2008, 2008 R2
- Windows Server 2008 R2 SP1 Hyper-V
- Citrix XenServer 5.0, 5.5, 5.6
Note: All Arcserve Backup products that can be installed on
physical computers can be installed on the guest operating
systems running on the above virtualization platforms.
2.1.2 Supported Cloud Vendors for the Arcserve Backup Base Product
The Arcserve Backup base product lets you archive data to
the following cloud vendor products:
- Amazon S3
- Eucalyptus 2.0 and 2.0.2
2.2 Supported Operating Systems for Arcserve Backup and Arcserve Replication (formerly, CA XOsoft) Integration-r16
To integrate Arcserve Backup with Arcserve Replication,
install the following:
- Arcserve Replication version r12, r12 SP1, r12.5 SP1, SP2,
r15, r15.1, r15.2, r16, or r16 SP2
Master servers
- Microsoft Windows Server 2003 SP1, SP2 or R2 (32-bit and
64-bit)
- Microsoft Windows Server 2008 (Arcserve Replication r12.5,
r12 SP1, r15, r15.1, r15.2, or r16)
- Microsoft Windows Server 2008 R2 (Arcserve Replication
r12.5 SP2, r15, r15.1, r15.2, or r16)
Replica servers
- Microsoft Windows Server 2003 SP1, SP2 or R2 (32-bit and
64-bit)
- Microsoft Windows Server 2008 (Arcserve Replication r12.5,
r12 SP1, r15, r15.1, r15.2, or r16)
- Microsoft Windows Server 2008 R2 (Arcserve Replication
r12.5 SP2, r15, r15.1, r15.2, or r16)
For more information about integration, refer to the
Arcserve Backup for Windows Arcserve Replication
Integration Guide.
2.3 Supported Operating Systems for the Arcserve Backup Client Agents
You can install the Arcserve Backup Client Agent for
Windows on the following operating systems:
- <Vista> (x86 and x64) (SP1, SP2)
- Windows XP Professional x86 (SP2, SP3), x64 (SP1 and SP2)
- Windows Server 2003 Web Edition (x86 only) (SP1, SP2)
- Windows Server 2003 Standard Edition (x86 and x64) (SP1,
SP2, R2, R2 SP2)
- Windows Server 2003 Enterprise Edition (x86, x64, and IA64)
(SP1, SP2, R2, R2 SP2)
- Windows Server 2003 Cluster x86 (SP1, SP2, R2, R2 SP2) x64
(SP1, SP2, R2, R2 SP2) and IA64 (SP1, SP2)
- Windows Storage Server 2003 (WSS) x86 (SP1, SP2, R2, R2
SP2), x64 (R2, R2 SP2)
- Windows Storage Server 2008 (WSS) x86 (SP1, SP2) and x64
(SP1, SP2)
- Windows Server 2003 Datacenter (x86 and x64) (SP1, SP2, R2
SP2)
- Windows Server 2008 Enterprise Edition (x86, x64, and IA64)
(SP1, SP2)
- Windows Server 2008 Standard Edition (x86, x64, and IA64)
(SP1, SP2)
- Windows Server 2008 Web Edition (x86 and x64) (SP1, SP2)
- Windows Server 2008 Data Center (x86 and x64) (SP1, SP2)
- Windows Server 2008 Core (x86 and x64) (SP1, SP2)
- Windows Server 2008 R2 (SP1)
- Windows Server 2008 R2 Core (x64)
- Windows Storage Server 2008 R2 (x64)
- Windows 7 (x64, x86) (SP1)
- Windows Small Business Server (SBS) 2003
- Windows Small Business Server (SBS) 2008
- Windows Small Business Server (SBS) 2011
You can install the Arcserve Backup Client Agent for UNIX
on the following operating systems:
- Solaris 8, 9 and 10 SPARC
- Solaris 10 (x86 32-bit)
- Solaris 10 x64
- IBM AIX (Physical machine and LPAR) 5.2, v5.3, and v6.1
- HP-UX 11.23 and 11.31 PA-RISC
- HP-UX 11.23 and 11.31 Itanium (IA64)
- Tru64 v5.1b
- FreeBSD version 7.2, 8.x (x86 and x64)
- Non-global zone on Solaris 10 SPARC
- Non-global zone on Solaris 10 (x86, x64)
You can install the Arcserve Backup Client Agent for Linux
on the following operating systems:
You can install the Arcserve Backup Client Agent for
Mainframe Linux OS/390 on the following operating systems:
- Red Hat Enterprise Server 3.x, 4.x and 5.x (32-bit and
64-bit) including SMP
- SUSE Linux Enterprise Server 9.x, 10.x, and 11.x (32-bit
and 64-bit) including SMP
You can install the Arcserve Backup Client Agent for Mac OS
X on the following operating systems:
You can install the Arcserve Backup Client Agent for
OpenVMS on the following operating systems:
- VAX 6.2, 7.1, 7.2, 7.3
- AXP 6.2, 7.1, 7.2, 7.3
You can install the Arcserve Backup Enterprise Option for
AS400 on the following operating systems:
- AS400 V5 R2 (5.2), V5 R3 (5.3), and V5 R4 (5.4)
2.4 Supported Operating Systems for the Agent for Informix
You can install the Arcserve Backup Agent for Informix on
the following operating systems:
- Windows 2003 Enterprise, Standard, Data Center SP2 (x86)
- Windows 2003 R2 Enterprise, Standard, Data Center SP2 (x86)
- Windows 2003 R2 Enterprise, Standard, Data Center SP2 (x64)
- Windows Server 2008 Enterprise, Standard, Data Center SP2
(x86)
- Windows Server 2008 Enterprise, Standard, Data Center SP2
(x64)
- Windows Server 2008 R2 Enterprise, Standard, Data Center SP1
2.5 Supported Operating Systems for the Agent for Lotus Domino
You can install the Arcserve Backup Agent for Lotus Domino
on the following operating systems:
- Windows 2003 Standard or Enterprise Server, SP1, SP2, or
R2, R2 SP2 with Lotus Domino 7.0, 7.0.2, 7.0.3, 8.0, 8.0.1,
8.0.2, 8.5, 8.5.1, or 8.5.2 (without db2 enabled), 8.5,
8.5.1, or 8.5.2 (with DAOS enabled).
- Windows 2003 Standard or Enterprise Server (x64) SP2, R2,
R2 SP2 with Lotus Domino 7.0.2, 7.0.3, 8.0, 8.0.1, 8.0.2,
8.5, 8.5.1, or 8.5.2 WOW (Windows on Windows), (without db2
enabled), 8.5, 8.5.1, or 8.5.2 (with DAOS enabled)
- Windows Server 2008 Standard or Enterprise SP1, SP2 with
Lotus Domino 8.5, 8.5.1, or 8.5.2 (without db2 enabled and
with DAOS enabled)
- Windows Server 2008 Standard or Enterprise (x64) SP1, SP2
with Lotus Domino 8.5, 8.5.1, or 8.5.2 WOW (without db2
enabled and with DAOS enabled)
- Windows Server 2008 R2, R2 SP1 with Lotus Domino 8.5.2
(without db2 enabled and with DAOS enabled)
Note: The Agent for Lotus Domino supports x86 and x64
systems, but not on IA64 systems. When installing on x64
systems, the default installation path is:
C:\Program Files (x86)\CA\ARCserve Backup Agent for Lotus
Domino\
2.6 Supported Operating Systems for the Agent for Microsoft Exchange Server
You can install the Arcserve Backup Agent for Microsoft
Exchange Server on the following operating systems:
- For Microsoft Exchange Server 2003,Exchange Server 2003 SP1
or SP2
- Microsoft Windows 2003 Server Standard Edition for x86,
Windows Server 2003 SP1, SP2, R2, or R2 SP2
- Microsoft Windows 2003 Server Enterprise Edition for x86,
Windows Server 2003 SP1, SP2, R2, or R2 SP2
- Microsoft Windows 2003 Server Datacenter Edition for x86,
Windows Server 2003 SP1, SP2, R2, or R2 SP2
- For Microsoft Exchange Server 2007, Exchange Server 2007
SP1, SP2, or SP3
- Microsoft Windows 2003 Server Standard Edition for x64,
Windows Server 2003 SP1, SP2, R2, or R2 SP2
- Microsoft Windows 2003 Server Enterprise Edition for x64,
Windows Server 2003 SP1, SP2, R2, or R2 SP2
- Microsoft Windows Server 2008 for x64 (only Microsoft
Exchange Server Version 2007 SP1, SP2, or SP3 are
supported), Windows Server 2008 SP1 or SP2
- Microsoft Windows Server 2008 R2 (only Microsoft Exchange
Server Version 2007 SP3 is supported), Windows Server 2008
R2 SP1.
- For Microsoft Exchange Server 2010, Exchange Server 2010
SP1, Exchange Server 2010 SP2
- Microsoft Windows Server 2008 Standard Edition x64 SP2
- Microsoft Windows Server 2008 Enterprise Edition x64 SP2
- Microsoft Windows Server 2008 R2 Standard Edition x64,
Windows Server 2008 R2 SP1
- Microsoft Windows Server 2008 R2 Enterprise Edition x64,
Windows Server 2008 R2 SP1
2.7 Supported Operating Systems for the Agent for Microsoft SharePoint Server
You can install the Arcserve Backup Agent for Microsoft
SharePoint Server on the following operating systems:
For Microsoft Office SharePoint Server 2007
- Microsoft Windows Server 2003 Standard Edition SP1, SP2,
- Microsoft Windows Server 2003 Enterprise Edition SP1, SP2
- Microsoft Windows Server 2003 Datacenter Edition SP1, SP2
- Microsoft Windows Server 2003 Web Edition SP1, SP2
- Microsoft Windows Server 2003 R2 SP2 Standard Edition
- Microsoft Windows Server 2003 R2 SP2 Enterprise Edition
- Microsoft Windows Server 2003 R2 SP2 Datacenter Edition
- Microsoft Windows Server 2003 R2 SP2 Web Edition
- Microsoft Windows Server 2008 Standard Edition SP1, SP2
(Only for SharePoint Server 2007 with SP1)
- Microsoft Windows Server 2008 Enterprise Edition SP1, SP2
(Only for SharePoint Server 2007 with SP1)
- Microsoft Windows Server 2008 Datacenter Edition SP1, SP2
(Only for SharePoint Server 2007 with SP1)
- Microsoft Windows Server 2008 Web Edition SP1, SP2 (Only
for SharePoint Server 2007 with SP1)
- Microsoft Windows Server 2008 R2 Standard Edition (Only for
SharePoint Server 2007 x64 with SP2)
- Microsoft Windows Server 2008 R2 Enterprise Edition (Only
for SharePoint Server 2007 x64 with SP2)
- Microsoft Windows Server 2008 R2 Datacenter Edition (Only
for SharePoint Server 2007 x64 with SP2)
- Microsoft Windows Server 2008 R2 Web Edition (Only for
SharePoint Server 2007 x64 with SP2)
- Microsoft Windows Server 2008 Foundation Server Edition
(Only for SharePoint Server 2007 x64 with SP2)
- Microsoft Windows Server 2008 Foundation Server R2 Edition
(Only for SharePoint Server 2007 x64 with SP2)
- Microsoft Windows Server 2008 R2 SP1
For Microsoft Office SharePoint Server 2010
- Microsoft Windows Server 2008 Standard Edition SP2
- Microsoft Windows Server 2008 Enterprise Edition SP2
- Microsoft Windows Server 2008 Datacenter Edition SP2
- Microsoft Windows Server 2008 R2 Standard Edition
- Microsoft Windows Server 2008 R2 Enterprise Edition
- Microsoft Windows Server 2008 R2 Datacenter Edition
- Microsoft Windows Server 2008 R2 SP1
2.8 Supported Operating Systems for the Agent for Microsoft SQL Server
You can install the Arcserve Backup Agent for Microsoft SQL
Server on the following operating systems:
For 32-bit Systems:
- Microsoft SQL Server 2000 (SP3, SP3a, or SP4) Support
- Windows Server 2003 SP1, SP2 or Windows 2003 R2 SP2
- Microsoft SQL Server 2005 (SP1, SP2, SP3, SP4) Support
- Windows Server 2003 SP1, SP2 or Windows 2003 R2 SP2
- Microsoft SQL Server 2005 (SP2, SP3, SP4 only) Support
- Windows Server 2008 SP1, SP2
- Microsoft SQL Server 2008 (SP1, SP2) Support
- Windows Server 2003 SP2 or Windows Server 2003 R2 SP2
- Windows Server 2008 SP1, SP2
- Microsoft SQL Server 2008 R2 Support
- Windows Server 2003 SP2 or Windows Server 2003 R2 SP2
- Windows Server 2008 SP2
For 64-bit Systems:
- Microsoft SQL Server 2000 for IA64 Support
- Windows Server 2003 SP1, SP2, for IA64-based systems
- Microsoft SQL Server 2000 for x86 Support
- Windows Server 2003 SP1, SP2 or Windows Server 2003 R2 SP2
for x64-based systems
- Microsoft SQL Server 2005 (SP1, SP2, SP3, SP4) for x64
Support
- Windows Server 2003 SP1, SP2, or Windows Server 2003 R2 SP2
for x64-based systems
- Microsoft SQL Server 2005 (SP1, SP2, SP3, SP4) for IA64
Support
- Windows Server 2003 SP1, SP2 for IA64-based systems
- Microsoft SQL Server 2005 (SP2, SP3, SP4 only) for x64
Support
- Windows Server 2008 SP1, SP2 for x64-based systems
- Microsoft SQL Server 2005 (SP3, SP4 only) for x64 Support
- Windows Server 2008 R2, R2 SP1 for x64-based systems
- Microsoft SQL Server 2005 (SP2, SP3, SP4 only) for IA64
Support
- Windows Server 2008 SP1, SP2 for IA64-based systems
- Microsoft SQL Server 2005 (SP3, SP4 only) for IA64 Support
- Windows Server 2008 R2, R2 SP1 for IA64-based systems
- Microsoft SQL Server 2008 (SP1, SP2) for x64 Support
- Windows Server 2003 SP2, or Windows Server 2003 R2 SP2 for
x64 based-systems
- Windows Server 2008 SP1, SP2 for x64-based systems
- Microsoft SQL Server 2008 (SP1, SP2 only) for x64 Support
- Windows Server 2008 R2, R2 SP1 for x64-based systems
- Microsoft SQL Server 2008 (SP1, SP2) for IA64 Support
- Windows Server 2003 SP2 for IA64-based systems
- Windows Server 2008 SP1, SP2 for IA64-based systems
- Microsoft SQL Server 2008 (SP1, SP2 only) for IA64 Support
- Windows Server 2008 R2, R2 SP1 for IA64-based systems
- Microsoft SQL Server 2008 R2 for x64 Support
- Windows Server 2003 SP2 or Windows Server 2003 R2 SP2 for
x64-based systems
- Windows Server 2008 SP2, R2, R2 SP1 for x64-based systems
- Microsoft SQL Server 2008 R2 for IA64 Support
- Windows Server 2003 SP2 for IA64-based systems
- Windows Server 2008 SP2 ,R2, R2 SP1 for IA64-based systems
2.9 Supported Operating Systems for Arcserve Backup for Small Business Server Editions
You can install Arcserve Backup for Small Business Server
(SBS) Editions on the following operating systems:
- Windows Small Business Server (SBS) 2003 SP1, SP2 (x86)
- Windows Small Business Server (SBS) 2008 SP1, SP2 (x64)
- Windows Small Business Server (SBS) 2011
2.10 Supported Operating Systems for the Agent for Oracle (UNIX/Linux)
You can install the Arcserve Backup Agent for Oracle on the
following UNIX operating systems:
- Solaris 9 and 10 SPARC
- Solaris 10 (x86)
- IBM AIX (Physical machine and LPAR) v5.2, v5.3, and v6.1
- HP-UX 11.23, 11.31 PA-RISC
- HP-UX Itanium 11.23, 11.31, IA64
- Tru64 v5.1b
- non-global zone on Solaris 10 SPARC
- non-global zone on Solaris 10 (x86)
You can install the Agent for Oracle on the following Linux
operating systems:
- Red Hat Enterprise Linux 4.x and 5.x (x86/x64/IA64)
- Red Hat Enterprise Linux 6 (x86/x64)
- SUSE Linux Enterprise Server 9.x, 10.x, and 11.x
(x86/x64/IA64)
2.11 Supported Operating Systems for the Agent for Oracle (Windows)
You can install the Arcserve Backup Agent for Oracle
(Windows) on the following operating systems, running the
following versions of Oracle:
- For Microsoft Windows Server 2003 (32-bit), Windows Server
2003 SP1 (32-bit), Windows Server 2003 SP2 (32-bit):
- Oracle Server version 9i, 10g R1, 10g R2, 11g R1, or 11g R2
- Oracle Fail Safe (OFS):
- Version 3.3.3 on 9i and 10g R2
- Version 3.3.4 on 10g R2
- Version 3.4.1 on 11g R1
- Oracle RAC 9i, 10g R1, 10g R2, and 11g R1
- For Microsoft Windows Server 2003 R2 SP2 (32-bit):
- Oracle Server version 9i, 10g R1, 10g R2, 11g R1, or 11g R2
- Oracle Fail Safe (OFS):
- Version 3.3.3 on 9i, 10g R1, 10g R2
- Version 3.3.4 on 10g R1, 10g R2
- Version 3.4.1 on 11g R1
- Oracle RAC 9i, 10g R1, 10g R2, and 11g R1
- For Microsoft Windows Server 2008 (32-bit), Windows Server
2008 SP1 (32-bit), Windows Server 2008 SP2 (32-bit):
- Oracle Server version 10g R2, 11g R1, and 11g R2
- Oracle Fail Safe (OFS) version 3.3.4 on 10g R2
- Oracle Fail Safe (OFS) version 3.4.1 on 11g R1
- Oracle RAC 10g R2 and RAC 11g R1
- For Microsoft Windows 2003 (64-bit), Windows Server 2003
SP1 (64-bit), Windows Server 2003 SP2 (64-bit):
- Oracle Server version 10g R1, 10g R2, 11g R1, or 11g R2
- Oracle Fail Safe (OFS):
- Version 3.3.4 on 10g R1, 10g R2
- Version 3.4.1.2 on 11g R1
- Version 3.4.1.4 on 11g R1
- Oracle RAC 10g R1, 10g R2, 11g R1, 11g R2
- Oracle 10g R2, 11g R1 WOW
- Oracle Fail Safe WOW
- Oracle RAC 10g R2 WOW
- For Microsoft Windows Server 2003 R2 (64-bit), Microsoft
Windows Server 2003 R2 SP2 (64-bit)
- Oracle Server version 10g R1, 10g R2, 11g R1, or 11g R2
- Oracle Fail Safe (OFS):
- Version 3.3.3. on 10g R1, 10g R2
- Version 3.3.4. on 10g R1, 10g R2
- Version 3.4.1. on 11g R1
- Version 3.4.1.4 on 11g R1
- Oracle RAC 10g R1, 10g R2, 11g R1, 11g R2
- Oracle 10g R2, 11g R1 WOW
- Oracle Fail Safe (OFS) WOW
- Oracle RAC 10g R2 WOW
- For Microsoft Windows Server 2008 (64-bit), Microsoft
Windows 2008 SP1 (64-bit), Microsoft Windows Server 2008
SP2 (64-bit):
- Oracle Server version 10g R2, 11g R1, 11g R2
- Oracle Fail Safe (OFS) version 3.4.1 on 10g R2, 11g R1
- Oracle RAC 10g R2, RAC 11g R2
- Oracle RAC 10g R2 WOW
- For Microsoft Windows Server 2008 R2 (64-bit):
- Oracle Server version 11g R1, 11g R2
- Oracle Fail Safe (OFS) versions 3.4.2 on 11g R2
- Oracle RAC 11g R2
- For Microsoft Windows Server 2008 R2 SP1 (64-bit):
- Oracle Server version 11g R2
- For Microsoft Windows Server 2003 SP2 (IA64):
- Oracle Server version 9i, 10g R1, 10g R2
- Oracle Fail Safe (OFS) version 3.3.2., 3.3.3., or 3.3.4. on
9i
- Oracle Fail Safe (OFS) version 3.3.3. on 10g R1 or 10g R2
- Oracle Fail Safe (OFS) version 3.3.4. on 10g R1 or 10g R2
- Oracle RAC 9i, 10g R1, 10g R2
- Oracle RAC 9i 10g R2 WOW
2.12 Supported Operating Systems for the Agent for Open Files
You can install the Agent for Open Files on the following
operating systems:
- <Vista> (x86, x64) SP1, SP2
- Windows XP Professional (x86) SP2, SP3 (x64) SP1, SP2
- Windows Server 2003 Standard Edition (x86, x64,) SP1, SP2,
R2, R2 SP2
- Windows Server 2003 Enterprise Edition (x86, x64) SP1, SP2,
R2, R2 SP2 (IA64) SP1, SP2
- Windows Server 2003 Small Business Server (SBS) (x86) SP1,
SP2, R2, R2 SP2
- Windows Server 2003 Web Edition (x86) SP1, SP2
- Windows Server 2003 Datacenter (x86, IA64) SP1, SP2 (x64)
SP1, SP2, R2, R2 SP2
- Windows Server 2003 Storage Server (x86) SP1, SP2, R2, R2
SP2 (x64) R2, R2 SP2
- Windows Server 2003 Cluster Server (x86, x64) SP1, SP2, R2,
R2 SP2 (IA64) SP1, SP2
- Windows Server 2008 Enterprise Edition (x86, x64, and IA64)
SP1, SP2
- Windows Server 2008 Standard Edition (x86, x64, and IA64)
SP1, SP2
- Windows Server 2008 Web Server Edition (x86, x64) SP1, SP2
- Windows Server 2008 Core Server Edition (x86, x64) SP1, SP2
- Windows Server 2008 Datacenter (x86, x64) SP1, SP2
- Windows Server 2008 R2, R2 SP1
- Windows Server 2008 R2 Core (x64)
- Windows 7 (x86, x64) SP1
- Windows Storage Server 2008 R2 (x64)
- Windows Storage Server 2008 (WSS) (x86) SP1, SP2 and (x64)
SP1, SP2
- Windows Small Business Server (SBS) 2003
- Windows Small Business Server (SBS) 2008
- Windows Small Business Server (SBS) 2011
Agent for Microsoft Volume Shadow Copy Service (VSS)
The Arcserve Backup Agent for Open Files now includes
functionality for the Arcserve Backup Agent for Microsoft
Volume Shadow Copy Service (VSS). This agent is not
supported on Windows XP.
2.13 Supported Operating Systems for the Agent for Sybase
You can install the Arcserve Backup Agent for Sybase on the
following operating systems:
For Sybase ASE 15.0
- Windows 2003 Enterprise, Standard, Data Center SP1, SP2
(x86)
- Windows 2003 R2 Enterprise, Standard, Data Center SP2 (x86)
For Sybase ASE 15.5
- Windows 2003 Enterprise, Standard, Data Center SP1, SP2
(x86)
- Windows 2003 R2 Enterprise, Standard, Data Center SP2 (x86)
2.14 Supported Operating Systems for the Agent for Virtual Machines
You can install the Agent for Virtual Machines on the
following operating systems:
- Windows Server 2008 R2:
- Windows Server 2008 R2 Standard, Enterprise, Datacenter and
Web Server editions
- Windows Server 2008 R2 with Service Pack 1 Standard,
Enterprise, Datacenter and Web Server editions
- Windows Server 2008:
- Windows Server 2008 x64 Standard, Enterprise, Datacenter,
Web Server, HPC editions
- Windows Server 2008 x64 without Hyper-V Standard,
Enterprise, Datacenter editions
- Windows Server 2008 x86 Standard, Enterprise, Datacenter,
Web Server, HPC editions
- Windows Server 2008 x86 without Hyper-V Standard,
Enterprise, Datacenter editions
- Windows Server 2008 x64 Service Pack 2 Standard,
Enterprise, Datacenter, Web Server, HPC editions
- Windows Server 2008 x64 Service Pack 2 without Hyper-V
Standard, Enterprise, Datacenter editions
- Windows Server 2008 x86 Service Pack 2 Standard,
Enterprise, Datacenter, Web Server, HPC editions
- Windows Server 2003:
- Windows Server 2003 x86 with Service Pack 2 Standard,
Enterprise, Datacenter, Web Server editions
- Windows Server 2003 x64 with Service Pack 2 Standard,
Enterprise, Datacenter editions
- Windows Server 2003 R2:
- Windows Server 2003 R2 x86 with Service Pack 2 Standard,
Enterprise, Datacenter, Web Server editions
- Windows Server 2003 R2 x64 with Service Pack 2 Standard,
Enterprise, Datacenter editions
- Windows 7:
- Windows 7 x86 Professional, Enterprise, Ultimate editions
- Windows 7 x64 Professional, Enterprise, Ultimate editions
- Windows 7 x86 with Service Pack 1 Professional, Enterprise,
Ultimate editions
- Windows 7 x64 with Service Pack 1 Professional, Enterprise,
Ultimate editions
- Windows Vista:
- Windows Vista x86 with Service Pack 1 Business, Enterprise,
Ultimate editions
- Windows Vista x64 with Service Pack 1 Business, Enterprise,
Ultimate editions
- Windows Vista x86 with Service Pack 2 Business, Enterprise,
Ultimate editions
- Windows Vista x64 with Service Pack 2 Business, Enterprise,
Ultimate editions
- Windows XP Professional:
- Windows XP Professional x86 Edition with Service Pack 3
(for VMs configured with 1 or 2 virtual processors)
- Windows XP Professional x86 Edition with Service Pack 2
(for VMs configured with 1 virtual processor)
- Windows XP Professional x64 with Service Pack 2 (for VMs
configured with 1 or 2 virtual processors)
- Windows Server 2008 Hyper-V:
- Windows Server 2008 Standard x64 SP1, SP2
- Windows Server 2008 Enterprise x64 SP1, SP2
- Windows Server 2008 Data Center x64 SP1, SP2
- Windows Server 2008 R2 Hyper-V:
- Windows Server 2008 R2 Standard, Enterprise, Datacenter and
Web Server editions
- Windows Server 2008 R2 SP1 Standard, Enterprise, Datacenter
and Web Server editions
- Windows Small Business Server (SBS) 2003
- Windows Small Business Server (SBS) 2008
- Windows Small Business Server (SBS) 2011
- VMware -- VMware Virtual Disk Development Kit (VDDK) and
VCB Framework are independent software products provided by
VMware. The Agent for Virtual Machines requires VDDK, VCB
Framework, or both, to back up VMs hosted on ESX Server
systems running the following applications:
VMware ESX/ESXi Server Version |
VMware VCB Framework Version |
VDDK Version |
VMware vCenter Server Version |
ESX/ESXi 3.5, Update 1, Update 2, Update 3, Update 4, Update 5 |
1.1, 1.1 Update 1, 1.5, 1.5 Update 1
|
1.1, 1.1.1
|
2.5 Update 1, Update 2, Update 3 and Update 4, and VMware vCenter Server 4.0 |
ESX/ESXi Server 4.0 (vSphere), Update 1, Update 2 |
1.5 Update 1, Update 2 |
1.1, 1.1.1, 1.2, 1.2.1 |
VMware vCenter Server 4.0, Update 1, Update 2 |
ESX/ESXi Server 4.1 (vSphere) |
1.5 Update 1, Update 2 |
1.1, 1.1.1, 1.2, 1.2.1 |
VMware vCenter Server 4.1 |
You can install Agent for Virtual Machines on all operating
systems supported by VMware for VCB/VDDK proxy server, on
all Windows guest operating systems supported by VMware
(except Windows NT 4.0), on Microsoft Hyper-V host server,
and on all Windows guest operating systems supported by
Microsoft Hyper-V.
Notes:
Arcserve Backup supports Agent for Virtual Machines on all
OS supported by VMware for VCB/VDDK proxy server.
Arcserve Backup supports Agent for Virtual Machines on all
Windows Guest Operating Systems supported by VMware, except
Windows NT 4.0.
Arcserve Backup supports Agent for Virtual Machines on all
Windows guest operating systems supported by Microsoft
Hyper-V.
2.15 Supported Operating Systems for the Disaster Recovery Option
The Disaster Recovery Option supports the following
methods:
- Bootable tape disaster recovery (only 32-bit supported)
- Windows 2003 Web Edition SP1, SP2
- Windows 2003 Standard Edition SP1, SP2, R2, R2 SP2
- Windows 2003 Enterprise Edition SP1, SP2, R2, R2 SP2
- Windows 2003 SBS Edition SP1, SP2, R2, R2 SP2
Note: Bootable tape disaster recovery from a USB tape drive
is not supported on Windows XP.
- Bootable media image disaster recovery
- Windows XP Professional Edition (x86 and x64)SP2, (x86) SP3
- Windows 2003 Web Edition SP1, SP2
- Windows 2003 Standard Edition (x86, x64, and IA64) SP1,
SP2, R2, R2 SP2
- Windows 2003 Enterprise Edition (x86, x64, and IA64) SP1,
SP2, R2, R2 SP2
- Windows 2003 SBS Edition SP1, SP2, R2, R2 SP2
Note: The version of Windows you use to generate the boot
media should be the version of Windows installed on your
machine.
The Arcserve bootable CD is a CD containing OS, Arcserve
Backup, Machine-Specific Disk, Drivers for NIC and Mass
Storage (SCSI/Fibre/RAID). For Windows 2008 systems only,
the creation of a unified CD is not supported, but a
bootable CD is supported. Machine-Specific Data may reside
on a USB drive.
- Bootable CD disaster recovery
Create a Machine Specific Disk that contains network
drivers if you need to perform disaster recovery remotely,
on a member server of a SAN, or from a remote File System
Device because you will likely face network connection
problems at the time of a disaster recovery. You may
re-create a Machine Specific Disk using the Disaster
Recovery Create Boot Kit Wizard, if you realize later that
you do not have network drivers. The procedure is the same
as for initial creation.
Bootable CD DR is also supported on UEFI:
- Windows 2003 IA64
- Windows 2003 R2 IA64
- Windows Server 2008 x64
- Windows Server 2008 IA64
- Windows Server 2008 R2
- Windows Server 2008 R2 IA64
Note: Windows XP and Windows 7 does not support Disaster
Recovery Option but does support Remote Disaster Recovery.
- Windows PE recovery CD
Note: Windows 7 does not support Disaster Recovery Option
but does support Remote Disaster Recovery.
2.16 Supported Operating Systems for the Enterprise Module
You can install the Enterprise Module on the following
operating systems:
- Windows Server 2003 x64, x86, IA64
- Windows Server 2008 x64, x86, R2 x64, IA64
The Enterprise Module includes the following Arcserve
Backup components, some of which may not be supported on
all operating systems:
- Image Option
This component is supported on the following operating
systems:
- Windows Server 2003 x64 and x86
- Windows Server 2008 x64, x86, and R2 x64
This component is not supported on the following operating
systems:
- Windows Server 2003 Intel Itanium (IA64)
- Windows Server 2008 IA64
- Windows Server 2008 R2 IA64
Note: The Enterprise Option does not support using the
Image Option to recover system volumes from a disaster on
all Windows Server 2008 operating systems (for example,
drive C:\). This limitation applies when the backup
includes only the system volume and you try to recover the
system volume.
- Enterprise Option for IBM 3494--Disaster Recovery is not
supported with this option. In addition, this option is
not supported on x64 systems
- Enterprise Option for StorageTek ACSLS
- Windows Server 2003 x86
- Windows Server 2003 x64
- Windows Server 2008 x86
- Windows Server 2008 x64
Note: Disaster Recovery (DR) is supported for StorageTek
ACSLS only on the following operating systems:
- Windows 2003 x86 (Traditional DR and WinPE DR)
- Windows 2008 x86 (Traditional DR and WinPE DR)
- Windows 2003 x64 (Traditional DR)
- Enterprise Option for VSS Hardware Snap-Shot--For more
information about the Enterprise Option for VSS Hardware
Snap-Shot, see the Arcserve Backup Microsoft Volume Shadow
Copy Service Guide.
2.17 Supported Operating Systems for the Enterprise Option for SAP R/3 for Oracle (Windows)
You can install the Enterprise Option for SAP R/3 for
Oracle on the following operating systems:
- Windows 2003 Enterprise Edition Service Pack 1, Service
Pack 2, R2 Service Pack 2 with BR*TOOLS 6.2, 6.4 for Oracle
9i or BR*TOOLS 7.0 for Oracle 10g
- Windows 2003 Enterprise x64 Edition Service Pack 1, Service
Pack 2, R2 Service Pack 2 with BR*TOOLS 6.4 for Oracle 9i
32-bit or BR*TOOLS 7.0 for Oracle 10g 32-bit, 64-bit
- Windows 2003 Enterprise Edition IA64 Service Pack 1,
Service Pack 2 with BR*TOOLS 6.4 for Oracle 9i or BR*TOOLS
7.0 for Oracle 10g
- Windows Server 2008 Service Pack 1 x86 with BR*TOOLS 7.2
for Oracle 11gr1
- Windows Server 2008 Service Pack 1 x64 with BR*TOOLS 7.2
for Oracle 11gr1
- Windows Server 2008 R2 Service Pack 1 x64 with BR*TOOLS 7.2
for Oracle 11gr2
- Windows Server 2008 R2 x64 with BR*TOOLS 7.2 for Oracle
11gr2
Notes:
- SAPDBA or BR*TOOLS should be installed on the same machine
as the agent BACKINT option.
- SAP R/3 for Windows is required.
- BR*TOOLS 4.6X is no longer supported.
- For use with the Agent for SAP, BR*TOOLS 6.4 for Oracle 9i
32-bit on Windows 2003 Enterprise x64 Edition systems,
ensure the Oracle release is 9.2.0.8 or later (32-bit).
2.18 Supported Operating Systems for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
The following table describes the operating system
requirements for the Enterprise Option for SAP R/3 for
Oracle:
Oracle Version |
Operating System |
SAP BR* Tools |
9i |
AIX v5.2, RHEL4.x |
SAP R/3 6.4, 7.0 |
10g |
AIX (Physical machine and LPAR) v5.2, v5.3, and v6.1
Solaris (SPARC) 9 and 10
HP-UX (PA-RISC, IA64) 11.23 and 11.31
Red Hat Enterprise Linux 4.x and 5.x (x86/x64/IA64)
SUSE Linux Enterprise Server 9.x, 10.x and 11.x |
SAP R/3 7.0, 7.1, 7.2 |
11gR1, R2 |
AIX (Physical machine and LPAR) v5.3 and v6.1
Solaris (SPARC) 10
HP-UX (PA-RISC, IA64) 11.23 and 11.31
Red Hat Enterprise Linux 4.x and 5.x (x86/x64/IA64)
Red Hat Enterprise Linux 6 (x86/x64)
SUSE Linux Enterprise Server 10.x and 11.x |
SAP R/3 7.2 |
Required Patches
- AIX Platforms:
The following patches are required for AIX platforms:
- All platforms--xlc.rte 9.0.0.0 or higher is required
- AIX 5.2--Fix package 5200-08 or higher is required
- AIX 5.3--Fix package 5300-07 or higher is required
- AIX 6.1--Base level 6100-GOLD is required
Note: For more information, see the IBM Fix Central website
and search for the version of your operating system.
- HP-UX Platforms:
The following patches are required for HP-UX platforms:
- PA-RISC/Itanium 11.23--Patch PHSS_37201 or higher is
required
- PA-RISC/Itanium 11.31--Patch PHSS_37202 or higher is
required
Note: For more information, see the HP website and search
for the version of your operating system.
2.19 Supported Operating Systems for the Image Option
The Image Option is now supported by the Enterprise Module.
For more information, see Supported Operating Systems for
the Enterprise Module.
2.20 Supported Operating Systems for the NDMP NAS Option
You can install the NDMP NAS Option on the following
operating systems:
- Windows Server 2003 SP1, SP2, R2, R2 SP2 (x86 and x64)
- Windows Server 2008 SP1, SP2 (x86 and x64)
- Windows Server 2008 R2, R2 SP1 (x64 only)
- Windows Server 2012 x64
2.21 Supported Operating Systems for the Storage Area Network (SAN) Option
You can install the Storage Area Network (SAN) Option on
the following operating systems:
- Windows Server 2003 SP1, SP2, R2, R2 SP2
- Windows Server 2008 SP1, SP2, R2
- Windows Server 2012 x64
2.22 Supported Operating Systems for SRM
The Storage Resource Management features are supported on
Windows XP and later.
Note: The Alert when PKI is Reaching Threshold feature is
supported on x64 and x86 systems only; it is not supported
on IA64 systems.
2.23 Supported Operating Systems for the Tape Library Option
You can install the Tape Library Option on the following
operating systems:
- Windows Server 2003 SP1, SP2, R2, R2 SP2
- Windows Server 2008 SP1, SP2, R2, R2 SP1
- Windows Server 2012 x64
2.24 Supported Operating Systems for Arcserve Backup UNIX and Linux Data Mover
The Arcserve Backup UNIX and Linux Data Mover is supported
on the following operating systems:
2.25 Supported Operating Systems for Arcserve Backup Dashboard
Arcserve Backup Dashboard supports all operating systems
listed for the base product and the following email clients:
- Microsoft Outlook 2003, 2007, 2010, and 2013.
- For Outlook Express running on Windows 2003 systems, email
formatting is not retained with default view settings. To
retain formatting, enable the Message in HTML option from
the Outlook Express View menu while the email is open.
2.26 Supported Operating Systems for the Arcserve Backup Global Dashboard
Arcserve Backup Global Dashboard is supported on the
following operating systems:
Central Primary Server:
The requirements for a Arcserve Backup primary/standalone
server to be designated and configured as a Central Primary
Server are as follows:
- Arcserve Backup must be configured to use SQL Server
2005/2008/2008 R2 as the Arcserve Backup database.
- Arcserve Backup Global Dashboard can be installed on any of
the Windows operating system versions supported by Arcserve
Backup Dashboard.
Branch Primary Server:
The requirements for a Arcserve Backup primary/standalone
server to be designated and configured as a Branch Primary
Server are as follows:
- Arcserve Backup Global Dashboard can be installed on any of
the Windows operating system versions supported by Arcserve
Backup Dashboard.
Global Dashboard Console:
The requirements for a machine to be designated and
configured as a Global Dashboard Console are as follows:
- Arcserve Backup Global Dashboard Console can be installed
on any of the Windows operating system versions supported
by Arcserve Backup Manager except Itanium-based systems.
2.27 Supported Operating Systems for Arcserve Backup Infrastructure Visualization
Arcserve Backup Infrastructure Visualization supports all
operating systems listed for the base product.
3.0 System Requirements
The following sections provide information about the
minimum system requirements for each Arcserve Backup
component.
3.1 System Requirements for the Arcserve Backup Base Product
The minimum system requirements for Arcserve Backup are:
- CPU: 600 MHz Pentium III-compatible or faster processor; 1
gigahertz (GHz) or faster processor recommended
- RAM: 512 MB, 1 GB or more recommended
- Disk Space:
- Primary Server: 800 MB, plus 1.3 GB for Agent Deployment
Packages
- Member Server: 450 MB, plus 1.3 GB for Agent Deployment
Packages
- This version of Arcserve Backup installs the following .NET
components:
- .NET 2.0 SP2 up to 500 MB of available disk space may be
required
- .NET 3.0 SP1 up to 500 MB of available disk space may be
required
- .NET 3.5 SP1 up to 500 MB of available disk space may be
required.
- To perform backup jobs for Transportable Shadow Copies
using the Microsoft Exchange Server writer, you must have
Microsoft Exchange Server installed on your Arcserve Backup
server. Backups of this type will fail if the Microsoft
Exchange Server is not installed on the Arcserve Backup
server.
Microsoft .NET Framework
Arcserve Backup requires the following versions of
Microsoft .NET Framework.
- Microsoft .NET Framework 3.5 SP1 on Windows Server 2003,
and Windows Server 2008 systems
Arcserve Backup Database
Arcserve Backup supports the following applications to host
the Arcserve Backup database (ASDB):
- Microsoft SQL Server 2008 Express Edition with Service Pack
1, Service Pack 2. The default Arcserve Backup database
application is the Microsoft SQL Server 2008 Express
Edition with Service Pack 1.
Note: To install Microsoft SQL Server 2008 Express Edition
on Windows Server 2003 systems, SP2 is required. Otherwise,
you must install a supported version of Microsoft SQL
Server to host the Arcserve Backup database.
- Microsoft SQL Server 2008 Enterprise/Standard Edition with
Service Pack 1, Service Pack 2
- Microsoft SQL Server 2000 with Service Pack 4
- Microsoft SQL Server 2005 with Service Pack 1, Service Pack
2, Service Pack 3, or Service Pack 4
Note: In addition to these requirements, you should
consider the disk space necessary for the default Arcserve
Backup database. Depending upon usage, the database can
grow to several GB in size.
- Microsoft SQL Server 2008 R2
Adobe Reader
- Adobe Acrobat Reader 8 and later
Internet Browser
- Internet Explorer 6.0 SP1
- Internet Explorer 7.0
- Internet Explorer 8.0 (all rendering modes)
- Internet Explorer 9.0
3.2 System Requirements for Arcserve Backup and Arcserve Replication Integration-r16
No additional hardware is required beyond the Minimum
Requirements previously listed.
In addition to the file protection, Arcserve Backup and
Arcserve Replication integration supports data protection
for the following:
- Microsoft Exchange Server 2003, SP1 and SP2
- Microsoft Exchange Server 2007, SP1, SP2 and SP3
- Microsoft Exchange Server 2010, SP1, SP2
- Microsoft SQL Server 2005, SP1, SP2, SP3, SP4
- Microsoft SQL Server 2008, SP1, SP2, SP3
- Microsoft SQL Server 2008 R2, SP1
- Microsoft SQL Server 2012, SP1
For more information about integration, refer to the
Arcserve Backup for Windows Arcserve Replication
Integration Guide.
3.3 System Requirements for the Arcserve Backup Client Agents
No additional hardware is required beyond the Minimum
Requirements previously listed.
To install the agents, your system must meet the following
minimum hardware requirements. For more details, see the
Arcserve Backup Client Agents Readme.
- Windows-based platforms:
- CPU: 200 MHz
- RAM: 256 MB
- Disk Space: 100 MB
- Windows IA64 platforms:
- CPU: 200 MHz
- RAM: 256 MB
- Disk Space: 100 MB
- UNIX-based platforms:
- CPU: 1 GHz
- RAM: 256 MB
- Disk Space: 25 MB on the client agent installation file
system, 25 MB (temporary) on /var/tmp file system
- Linux-based platforms:
- CPU: 500 MHz
- RAM: 256 MB
- Disk Space: 25 MB
- Mac OS X
- RAM: 128 MB
- Disk Space 10 MB
3.4 System Requirements for the Agent for Informix
The Arcserve Backup Agent for Informix requires the
following:
- Informix Dynamic Server 11.10, 11.50, or 11.70
- Informix-Connect is installed and working properly
- CPU: 1GHz
- RAM: 1GB
- Disk Space: 100 MB
3.5 System Requirements for the Agent for Lotus Domino
The Agent for Lotus Domino requires the following:
- CPU: 512 MHz
- RAM: 512 MB
- Disk Space: 50 MB
3.6 System Requirements for the Agent for Microsoft Exchange Server
Note: The Agent now installs the Exchange Database Level
Agent with the Exchange Document Level Agent.
To install the Agent for Microsoft Exchange Server, the
following hardware must be available and configured
according to the version of Microsoft Exchange Server you
are running:
3.7 System Requirements for the Agent for Microsoft SharePoint Server
To install the Agent for Microsoft SharePoint Server, the
following hardware must be available and configured
according to the version of Microsoft SharePoint Server
2007 or 2010 you are running:
- The basic Microsoft SharePoint Server 2007 or 2010 hardware
requirements (for information about these requirements, see
the Microsoft website).
- CPU: 2.5 GHz
- RAM: 2 GB
- Disk Space: At least 50 MB, with at least 30 MB on hard
disk where the Agent for SharePoint Server is installed and
at least 20 MB on the system drive.
Note: You must meet the basic Arcserve Backup product
requirements before you install the Agent and Arcserve
Backup on the same machine. For updated information about
these requirements, contact Arcserve Support.
The agent does not require the Arcserve Backup server
component.
The Agent for Microsoft SharePoint Server requires at least
one of the following:
- Microsoft SharePoint Server 2007, SP1, SP2 (see Notes,
below)
- Microsoft SharePoint Services 3.0 SP1, SP2
- Microsoft SharePoint Server 2010
- Microsoft SharePoint Foundation 2010
Note:
If running Microsoft SharePoint Server products, apply the
latest service package to the SQL Server or SQL-Express.
3.8 System Requirements for the Agent for Microsoft SQL Server
For the Agent for Microsoft SQL Server, ensure your system
meets the minimum system requirements established for the
Arcserve Backup base product.
3.9 System Requirements for the Arcserve Backup Small Business Server Editions
For the Arcserve Backup Small Business Server (SBS)
Editions, ensure your system meets the following
requirements:
- Small Business Server (SBS) Standard Edition
- CPU: at least 750 MHz, 1 GHz recommended
- RAM: at least 512 MB, 1 GB recommended
- Disk Space: 16 GB
The following agents/options are included in the Arcserve
Backup Small Business Server (SBS) Standard Edition:
- Base Product
- Client Agent for Microsoft Windows
- Agent for Microsoft Exchange Server
- Agent for Microsoft SharePoint Server
- Agent for Open Files
- Small Business Server (SBS) Premium Edition
- CPU: at least 750 MHz, 1 GHz recommended
- RAM: at least 512 MB, 1 GB recommended
- Disk Space: 16 GB
The following agents/options are included in the Arcserve
Backup Small Business Server (SBS) Premium Edition:
- Base Product
- Client Agent for Microsoft Windows
- Agent for Microsoft Exchange Server
- Agent for Microsoft SQL Server
- Agent for Microsoft SharePoint Server
- Agent for Open Files
3.10 System Requirements and Oracle Database Support for the Agent for Oracle (UNIX/Linux)
The following sections provide the minimum system
requirements and Oracle Database support for the Agent for
Oracle on UNIX platforms.
Note: To obtain the latest patches and downloads for the
Arcserve Backup Agent for Oracle on UNIX platforms, see the
Arcserve Technical Support.
Sun Solaris SPARC:
On Sun Solaris SPARC, the agent requires the following:
- Sun UltraSPARC models
- 256 MB RAM
- 250 MB disk space
Sun Solaris x86:
On Sun Solaris x86, the agent requires the following:
- Sun x86 models
- 256 MB RAM
- 25 MB disk space
IBM AIX (Physical machine and LPAR):
On IBM AIX, the agent requires the following:
- IBM RISC 6000 models
- 256 MB RAM
- 250 MB disk space
HP-UX:
On HP-UX, the agent requires the following:
- HP 9000 Server/Workstation
- 256 MB RAM
- 250 MB disk space
HP-UX Itanium:
On HP-UX Itanium, the agent requires the following:
- HP IA64 models
- 256 MB RAM
- 250 MB disk space
HP/Compaq OSF Tru64:
On OSF Alpha, the agent requires the following:
- HP/Compaq Alpha models
- 256 MB RAM
- 25 MB disk space
Database Support on UNIX platforms
You can use the agent with the following databases:
- Oracle 9.0.1, 9.0.1.1, 9.2.0
- Oracle 10.1.0 (10g) and 10.2 (10g R2)
- Oracle 11.1 (11gR1) and 11.2 (11gR2)
Note: Oracle 11gR1 is supported on Sun Solaris SPARC, HP-UX
Itanium, HP-UX and AIX platforms. Oracle 11gR2 is supported
on Sun Solaris SPARC, HP-UX Itanium, and HP-UX platforms.
You must install the 6800649 Oracle patch available from
the Oracle Metalink website for AIX5L and AIX6L Based
Systems (64-bit).
The following sections provide the minimum system
requirements and Oracle Database support for the Agent for
Oracle on Linux platforms:
Linux x86:
To use the Agent for Oracle on Linux x86 platforms, you
must satisfy the following minimum system requirements:
- x86 an compatible platform machines
- 500 MHz CPU
- 256 MB RAM
- 250 MB free disk space
Linux x64:
To use the Agent for Oracle on Linux x64 platforms, you
must satisfy the following minimum system requirements:
- AMD64 platform machines
- 1 GHz CPU
- 256 MB RAM
- 250 MB free disk space
Linux Itanium:
To use the Agent for Oracle on Linux Itanium platforms, you
must satisfy the following minimum system requirements:
- Itanium platform machines
- 1 GHz CPU
- 512 MB RAM
- 250 MB free disk space
Database Support on Linux platforms
You can use the agent with the following databases:
- Oracle 9.0.1, 9.0.1.1, and 9.2.0
- Oracle 10.1.0 (10g), 10.2 (10g R2)
- RAC 9i and 10g, OCFS on Red Hat Enterprise Server 4.x x86
and x64
- Oracle 10g (10.1.0.3.0) 64 bit on SUSE Linux Enterprise
Server 9.0 AMD64
- Oracle 10g (10.2.0.1.0) on SUSE Linux Enterprise Server 10,
SUSE Linux Enterprise Server 11
- Oracle Database 11gR1 on SUSE Linux Enterprise Server 10
SP2, Red Hat Enterprise Linux 4.x and Red Hat Enterprise
Linux 5.x
- Oracle Database 11gR2 32 bit on Red Hat Enterprise Linux
5.x x86 and SUSE Linux Enterprise Server 11 SP1 x86
- Oracle Database 11gR2 64 bit on Red Hat Enterprise Linux
5.x x64 and SUSE Linux Enterprise Server 11 SP1 x64
3.11 System Requirements for the Agent for Oracle (Windows)
To install the Agent for Oracle, the following hardware
must be available and configured according to the version
of Oracle Database you are running:
- The basic hardware requirements (for information about
these requirements, see the Oracle website)
- CPU: 200 MHz
- RAM: at least 512 MB if using Oracle 9i/10gR1/R2, and at
least 1 GB if using Oracle 11g R1/R2
- Disk Space: at least 100 MB on the hard disk where the
agent is installed
Note: The Arcserve Backup Agent for Oracle allows you to
perform backups in two modes: RMAN Mode and File-based
Mode. In RMAN Mode, you can submit jobs from the interface
or from the RMAN command line console. The RMAN mode of the
Arcserve Backup Agent for Oracle supports Automatic Storage
Management (ASM) for backup jobs submitted using both the
Arcserve Backup Manager Console and the RMAN (Oracle
Recovery Manager) Command Line Console. The file-based mode
of the Arcserve Backup Agent for Oracle does not support
this.
3.12 System Requirements for the Agent for Open Files
For the Agent for Open Files, ensure your system meets the
Arcserve Backup base product requirements. In addition, you
should have at least 1.5 MB of disk space available for
this agent.
3.13 System Requirements for the Agent for Sybase
To install the agent, verify that the following
requirements are satisfied:
3.14 System Requirements for the Agent for Virtual Machines
For the Agent for Virtual Machines, system requirements
depend upon where the Agent is installed:
- If the Agent for Virtual Machines is installed on the same
server as the base product, the Agent requires the same
hardware specified for the base.
- If the Agent is installed on a remote node, the Agent
requires the same hardware specified for the Client Agent
for Windows.
3.15 System Requirements for the Central Management Option
For the Central Management Option, ensure your system meets
the Arcserve Backup base product minimum requirements.
3.16 System Requirements for the Disaster Recovery Option
For the Disaster Recovery Option, ensure your system meets
the minimum requirements established for the Arcserve
Backup base product. In addition, you should have at least
70 MB of disk space available.
Note: If you are performing Disaster Recovery using Windows
PE Recovery CD, the machine should have a minimum of 1 GB
of RAM.
3.17 System Requirements for the Enterprise Module
For the Enterprise Module, ensure that your system meets
the Arcserve Backup base product minimum requirements.
You must license the Enterprise Module for access to the
following options and features:
- Enterprise Option for IBM 3494--Requires the IBM Library
Manager Control Service version 5.4.8
- Enterprise Option for StorageTek ACSLS--Requires LibAttach
software
- Image Option
For more information on what operating systems Image Option
supports, see Supported Operating Systems for the
Enterprise Module.
- Multistreaming backups with more than one stream of backup
data; for disk staging backups, more than two streams of
backup data
- Media Management Option (MMO)
- Raw backup and restore of physical disks and volumes
- Enterprise Option for VSS Hardware Snap-Shot
Note: For more information about the Enterprise Option for
VSS Hardware Snap-Shot, see the Arcserve Backup Microsoft
Volume Shadow Copy Service Guide.
3.18 System Requirements for the Enterprise Option for IBM 3494
The Enterprise Option for IBM 3494 is now supported by the
Enterprise Module.
3.19 System Requirements for the Enterprise Option for SAP R/3 for Oracle (Windows)
To install the Enterprise Option for SAP R/3 for Oracle,
the following hardware must be available and configured
according to the version of Oracle Database you are
running:
- CPU: 200 MHz
- RAM: at least 256 MB (512 recommended by Oracle) if using
Oracle 9i/10gR1/R2, and 11gR1/R2
- Disk Space: at least 100 MB on the hard disk where the
option is installed
3.20 System Requirements for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
The following table describes the minimum hardware
requirements for the Enterprise Option for SAP R/3 for
Oracle:
Platform |
Architecture |
RAM |
Free Disk Space |
Free Disk Space in /tmp |
Solaris |
SPARC |
256 MB |
250 MB |
400 MB |
IBM AIX |
Power PC |
256 MB |
250 MB |
400 MB |
HP-UX |
PA-RISC, IA64 |
256 MB |
250 MB |
400 MB |
Linux |
x86, IA64, and x64 |
256 MB |
250 MB |
400 MB |
3.21 System Requirements for the Enterprise Option for StorageTek ACSLS
The Enterprise Option for StorageTek ACSLS is now supported
by the Enterprise Module.
3.22 System Requirements for the Image Option
The Image Option is now supported by the Enterprise Module.
For more information, see System Requirements for the
Enterprise Module.
3.23 System Requirements for the NDMP NAS Option
For the NDMP NAS Option, ensure your system meets the
minimum requirements established for the Arcserve Backup
base product. In addition, the following software
requirements may apply, depending upon the devices you
choose:
- For Network Appliance devices:
- ONTAP Minimum Version 6.0.1R3
- NAS Server: Models FAS 250 series, N3700 series, F700
series, F800 series (ONTAP Version is of primary concern,
not the model)
- For EMC (IP4700) devices:
- Minimum firmware version R2.0 p21
- NAS Server Model: IP4700
- For EMC (Celerra) devices:
- Minimum file server version 4.2.9.0
- NAS Server model: Celerra
- For PROCOM devices:
- Minimum firmware version: 4.1.3
- NAS Server Model: NetForce 1000 series, 3000 series
Note: The NDMP NAS Option supports both x64 and x86
Arcserve Backup servers to back up NAS filers.
3.24 System Requirements for the Storage Area Network (SAN) Option
For the Storage Area Network (SAN) option, ensure your
system meets the minimum requirements established for the
Arcserve Backup base product.
You must also install the following applications before
installing the Arcserve Backup Storage Area Network (SAN)
Option:
- Arcserve Backup for Windows (Primary Server)
- Arcserve Backup Central Management Option
- Arcserve Backup Tape Library Option
3.25 System Requirements for the Tape Library Option
For the Tape Library Option, ensure your system meets the
minimum requirements established for the Arcserve Backup
base product.
Arcserve Backup for Windows must be installed before you
install the Arcserve Backup Tape Library Option.
Note: The Tape Library Option includes support for Tape
RAID.
3.26 System Requirements for the Arcserve Backup UNIX and Linux Data Mover
The Arcserve Backup UNIX and Linux Data Mover includes Java
1.6 technology that may require your HP-UX system to be at
a specific patch level. For the most current information
regarding patches, go to the HP website and apply any
required patches before you install the Arcserve Backup
Data Mover on HP-UX systems.
- HP-UX PA-RISC/Itanium 11.23, the patch PHSS_37201 or higher
is required
- HP-UX PA-RISC/Itanium 11.31, the patch PHSS_37202 or higher
is required
For AIX systems, the following are required:
- For AIX 5.2, the fix package 5200-08 or higher is required
- For AIX 5.3, the fix package 5300-07 or higher is required
- For AIX 6.1, the base level 6100-GOLD is required
- xlc.rte 9.0.0.0 or higher is needed for all AIX platforms.
For more information, go to the IBM's Fix Central website
and search for the version appropriate for your operating
system.
The following table describes the minimum hardware
requirements for the Arcserve Backup UNIX and Linux Data
Mover:
Platform |
Architecture |
RAM |
Free Disk Space |
Free Disk Space in /tmp |
Solaris |
SPARC |
256 MB |
250 MB |
400 MB |
IBM AIX |
Power PC |
256 MB |
250 MB |
400 MB |
HP-UX |
PA-RISC, IA64 |
256 MB |
250 MB |
400 MB |
Linux |
x86, IA64, and x64 |
256 MB |
250 MB |
400 MB |
3.27 System Requirements for Arcserve Backup Dashboard
No additional hardware is required beyond the Minimum
Requirements listed for Arcserve Backup base product.
3.28 System Requirements for the Arcserve Backup Global Dashboard
The following section provides information about the
minimum system requirements for Arcserve Backup Global
Dashboard.
System Requirements for the Central Primary Server
The minimum system requirements for Arcserve Backup Global
Dashboard to be installed as the Central Primary Server
are:
Arcserve Backup Database
For the Central Primary Server, Global Dashboard must be
installed with Arcserve Backup using Microsoft SQL Server
as its database. (Microsoft SQL Server Express and
Microsoft SQL Server 2000 is not supported for the Central
Primary Server).
- Microsoft SQL Server 2008
- Microsoft SQL Server 2008 R2
- Microsoft SQL Server 2005
Note: In addition to these requirements, you should
consider the disk space necessary for the default Arcserve
Backup database. Depending upon usage, the database can
grow to several GB in size.
System/processor:
- Server with at least a Dual Core Processor (2.8 GHz) or
better
Memory:
- 4GB or more (recommended)
Disk Space:
- Sufficient Arcserve Backup database capacity for your
Global Dashboard environment:
As each branch site uploads data to the central Arcserve
Backup database on a daily basis, it is estimated that the
central Arcserve Backup database will increase by
approximately 4 MB for every 100 nodes (assuming 4 volumes
in each node) every day (or 1MB for every 100 sessions
every day).
The number of sessions is calculated by multiplying the
number of nodes by the average number of volumes in a node.
The number of days of database retention time is determined
by the branch Arcserve Backup setup.
You can calculate the approximate required disk space at
the central site by multiplying the estimated daily
Arcserve Backup database growth (1MB for every 100
sessions) by the number of days of database retention time.
For example:
If you have 10 branch sites with each site having 10 nodes
and each node contains 4 volumes, then the central Arcserve
Backup database will increase by 4MB every day. If the
database record is retained for 180 days, then the central
Arcserve Backup database will need to be 720MB.
- 10 branch sites x 10 nodes x 4 volumes = 400 sessions
- 400 sessions = 4MB database space growth per day (1MB per
100 sessions)
- 4MB daily growth x 180 database retention days = 720MB
total database space required for the central Arcserve
Backup database.
Note: Any database pruning that is performed at a branch
Arcserve Backup database will be reflected in the central
Arcserve Backup database the next time data synchronization
is performed.
Adobe Reader
Email clients
Global Dashboard supports the following email clients on
the Central Primary Server:
- Microsoft Outlook 2003, 2007, and 2010
- Outlook Express
- Windows Mail
System Requirements for a Branch Primary Server
No additional hardware or software is required beyond the
Minimum Requirements for any Arcserve Backup primary server.
Arcserve Backup Database
For a Branch Primary Server, Global Dashboard must be
installed with Arcserve Backup using Microsoft SQL Server
or Microsoft SQL Server Express Edition as its database.
- Microsoft SQL Server 2008
- Microsoft SQL Server 2005
- Microsoft SQL Server 2008 Express
- Microsoft SQL Server 2000
- Microsoft SQL Server 2008 R2
3.29 System Requirements for Arcserve Backup Infrastructure Visualization
No additional hardware is required beyond the minimum
requirements previously listed.
3.30 System Requirements for Arcserve Backup Infrastructure Global Visualization
For the Arcserve Backup Infrastructure Global
Visualization, ensure your system meets the Arcserve Backup
Global Dashboard requirements.
4.0 Installation Considerations
The following sections provide information about
installation prerequisites, configurations, and issues to
consider before installing Arcserve Backup and its agents
and options.
4.1 Installation Considerations for the Arcserve Backup Base Product
The following section provides information about
installation prerequisites, configurations, and issues to
consider before installing the Arcserve Backup base
product.
- You should not remove the Arcserve Backup installation DVD
from the option drive while the installation process is in
progress. This action causes the Arcserve installation
process to fail. For example, when installing Arcserve
Backup on Windows Server 2012 systems, do not remove the
Arcserve installation DVD from the optical drive to insert
the Windows Server 2012 media to install .Net Framework 3.5.
- .NET Framework 3.5 SP1 installation may fail on computers
that have .NET Framework 2.0 or 2.0 SP1 installed on
Windows Server 2003 machines.
- If you wish to install Arcserve Backup components in a
custom location, you must specify separate destination
folder names for each component.
- 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 Arcserve Backup, you must log into your computer
using an administrator account or a user account with
administrator privileges.
- If you are prompted to reboot your machine during the
remote installation process, you must reboot the machine
manually for the remote installation to be successful.
- If you are installing Arcserve Backup agents on a machine
where InoculateIT or Antivirus is running, the following
driver update must be applied to both the 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.
- 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.
- Arcserve Backup installs SQL Express 2008 as the Arcserve
Backup database when SQL Express is selected. This is
listed as the "Default database" on the configuration
screen during setup. You must also install Microsoft
Installer 4.5, which is a prerequisite for installing SQL
Express 2008. This installation requires a system reboot.
Note: For local installations, Setup continues the
installation from the point of the restart. However, for
remote installations and silent installations, Setup
terminates your installation at the point of the restart.
You must then start Setup manually after the system
restarts.
- Case-sensitive collation is supported only on fresh
installations, or upgrades that overwrite the Arcserve
Backup database instance. If you are upgrading over an
existing SQL Server Express ASDB instance, make sure
instance collation is set to case-insensitive or some
functions will not work. See the Microsoft documentation or
website for more information on setting collation.
- During the setup process, an item for Arcserve Backup for
Windows for Microsoft Small Business Server (SBS) appears
only when you install Arcserve Backup to the same machine
on which Microsoft Small Business Server (SBS) is also
installed. Otherwise, you may apply the license via the
CALicnse.exe program. See the Online Help for more
information on the CALicnse.exe program.
- Response files cannot be created on computers running
Windows Server 2008 Core and Windows Server 2012 Core. You
must create the response file on another computer and copy
it to the computer running Windows Server 2008/2012 Core to
run the silent installation.
- When you uninstall r11.5, multiple messages are recorded in
the Event Viewer. You can avoid this problem by performing
the following steps before upgrading or installing the
current version:
- Create a key called MessageEngine under:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Admin
- Create a DWORD value called Impersonate under:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Admin\MessageEngine
- Set Impersonate to 0.
- Reboot the Windows system.
- Choosing the Arcserve Backup Express Install option
installs Microsoft SQL Express 2008 SP1 as the Arcserve
Backup database.
- When installing Arcserve Backup as a Member Server on
Windows Server 2008 Core, you should run mastersetup.exe
directly from DVD\Install. If you use setup.exe from the
DVD root, you will launch DemoShield, which requires
Internet Explorer to run. Internet Explorer is not
available in Windows Server 2008 Core operating systems.
- When performing a local install of Arcserve Backup, ensure
all Arcserve Backup products are from the same release if
you are using the SDO or silent install options. You can
check release information from Support Information under
the Add/Remove option for Arcserve Backup products.
- Uninstalling Agent Deployment can be achieved by deleting
files from the Agent Deployment folder to free up disk
space. The folder is located in the Arcserve Backup
installation directory, in the Packages folder. If you need
to launch Agent Deployment later, you will be prompted to
insert the source media to copy files.
- When installing Arcserve Backup, you will be required to
reboot your system if any version of eTrust prior to 8.0 is
installed.
- When installing Arcserve Backup on Windows Server 2008
systems, ensure that you have no users named "user" in the
domain or logging on to Arcserve Backup using Windows
authentication will fail. If a user so named exists, delete
the account from Windows and User Profile Management and
use another Windows account to log on to Arcserve Backup.
- When installing SQL Express 2008 as the Arcserve Backup
database, the application Event Log shows numerous error
messages. This is a known Microsoft issue and does not
affect the operation of Arcserve Backup.
- System requirements for the Disk to Disk to Tape feature:
process disk staging backups using multistreaming in more
than two streams of backup data, you must license the
Arcserve Backup Enterprise Module.
- Setup must restart your system when you install the
Arcserve Backup base product and deploy Microsoft SQL
Server 2008 Express Edition to support the Arcserve Backup
database. After your system restarts, Setup continues the
installation from the point of the restart. This behavior
presents a problem when the installation media is mounted
to a DVD drive that is configured as a network share on a
remote computer. Setup cannot locate the installation
media after the restart and cannot continue from the point
of the restart. To complete the installation, you must run
Setup and start the installation process from the
Installation Browser. There is no remedy for this problem.
- When you perform a remote upgrade from Arcserve Backup r12
or Arcserve Backup r12.5 to this release, the upgrade
process can stop responding after Setup installs Windows
Installer. This behavior affects only computers running
Windows 7. This problem does not occur on all remote
upgrades to computers running Windows 7. If you encounter
this problem, log in to the computer directly to perform
the upgrade.
4.2 Installation Considerations for the Agent for Microsoft Exchange Server
The following section provides information to consider when
installing the Agent for Microsoft Exchange Server.
4.3 Installation Considerations for the Agent for Microsoft SharePoint Server
The following section provides information to consider when
installing the Agent for Microsoft SharePoint Server:
- Microsoft Office SharePoint Server 2007, Microsoft
SharePoint Server 2010, Microsoft SharePoint Server 2013,
Windows SharePoint Service 3.0, Microsoft SharePoint
Foundation 2010, or Microsoft SharePoint Foundation 2013
must be installed before you install the Agent for
Microsoft SharePoint Server. The agent is supported on all
operating systems where Microsoft Office SharePoint Server
2007, 2010 or 2013 are supported.
- The Arcserve Backup server must be able to ping all
machines in the SharePoint environment by name. If you do
not use DNS (Domain Name System) in your SharePoint
environment, you must add all the machines in the
SharePoint environment into the hosts file on the Arcserve
Backup server.
- For SharePoint Server farm environments, you must run the
Microsoft SQL Server database instance with a domain
account; for SharePoint Server standalone environments, you
must run the Microsoft SQL Server database instance with a
domain account or a local system account, depending on the
configuration of the SharePoint installation. For details,
see the Arcserve Backup Agent for Microsoft SharePoint
Server Guide.
- When you upgrade the Agent for SharePoint Server to this
release, two active SharePoint Server Agent licenses exist
in License Management dialog. To avoid this situation,
launch License Management and manually release the licenses
for old versions of the Agent that have been upgraded.
- If the Agent for Microsoft SharePoint Server 2003, which is
no longer supported, is detected during upgrade, the agent
is automatically uninstalled.
4.4 Installation Considerations for the Agent for Microsoft SQL Server
The following section provides information about
installation prerequisites, configurations, and issues to
consider before installing the Agent for Microsoft SQL
Server.
- In cluster environments, you may receive a Lost Connection
error while installing the Agent for Microsoft SQL Server.
This occurs in primary and standalone installations when
you select the cluster SQL as the Arcserve Backup database.
To avoid this error, copy the SQL Agent for Arcserve Backup
database package to each cluster node and run setup
manually.
- To protect SQL Server instances in a cluster-aware
environment, you must manually install the Agent for
Microsoft SQL Server on all of the nodes in the
cluster-aware environment.
- When installing the SQL Agent for the Arcserve Backup
database on other nodes in a cluster-aware environment, you
must run SQLAgentRmtInst.exe and DBAConfig.exe after
installation to input the correct cluster node name and
password so that the Setup process can create ODBC
communication.
- When you select Windows Authentication for SQL Server,
Arcserve Backup does not require security information to
back up the SQL Server.
4.5 Installation Considerations for the Agent for Open Files
The following section provides information to consider when
installing the Agent for Open Files on Vista machines,
Windows Server 2008 Core and Windows 2012 Core:
- You can remotely install the Agent for Open Files on Vista
machines, but may need to disable local account filtering
first. User Account Control (UAC) is a Vista feature that
blocks local administrative accounts from remotely
accessing administrative shares (C$, Admin$).
Before you begin, determine whether the Vista machine is
part of a domain or part of a workgroup. Use a Domain
Administrative account if the target computer is part of a
domain. Grant a domain account with administrator
privileges on the Vista machine and use that domain account
to log on. You may then remotely install the Agent for Open
Files on the Vista machine.
If the target computer is part of a workgroup, disable the
client computer's local account filtering policy by
creating a new registry key, as follows:
DWORD value: LocalAccountTokenFilterPolicy
Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\
New Value: 1
After installation, set the LocalAccountTokenFilterPolicy
setting to 0 to re-enable local account filtering.
- When installing the Agent for Open Files, a reboot is
recommended, but not necessary. Without rebooting, any
files open before the Agent was installed may not be
accessible during backup.
- When installing Arcserve Backup as an Agent for Open Files
on Windows Server 2008 Core and Windows Server 2012, you
should run mastersetup.exe directly from DVD\Install. If
you use setup.exe from the DVD root, you will launch
DemoShield, which requires Internet Explorer to run.
Internet Explorer is not available in Windows Server 2008
Core and Windows Server 2012 operating systems.
4.6 Installation Considerations for the Media Management Option (MMO)
The Enterprise Module is a prerequisite component for the
Media Management Option (MMO) and you must install it in
order to use the MMO option.
Note: MMO is not supported on Arcserve member server.
4.7 Installation Considerations for the Enterprise Module
The following section provides information about
installation prerequisites, configuration, and issues to
consider when installing the Arcserve Backup Enterprise
Module.
- The Image Option is included in the Enterprise Module. You
must restart your computer after installing this option.
4.8 Installation Considerations for the UNIX and Linux Data Mover
Ensure that you complete the following prerequisite tasks
before installing UNIX and Linux Data Mover.
- Install Arcserve Backup for Windows on the primary server
before completing this task.
- Secure the host name of the Arcserve Backup primary server.
- Secure the password for the caroot user name for the
Arcserve Backup primary server.
- Ensure that the Arcserve Backup primary server and the
target data mover server can communicate with each other.
You can verify that the servers can communicate using the
ping host name command.
- You do not need to uninstall the following components from
the target data mover server to upgrade to this release:
- Client Agent for Linux (r12.5, r15, r16 and r16 sp1)
- Client Agent for UNIX (r12.5, r15, r16 and r16 sp1)
- Oracle Agent for Linux (r12.5, r15, r16 and r16 sp1)
- Oracle Agent for UNIX (r12.5, r15, r16 and r16 sp1)
- Enterprise Option for SAP R/3 for Oracle for Linux (r16
and r16 sp1)
- Enterprise Option for SAP R/3 for Oracle for UNIX (r16 and
r16 sp1)
- Data Mover for Linux (r15, r16 and r16 sp1)
- Data Mover for UNIX (r15, r16 and r16 sp1)
When running on the target data mover server, the
installation script detects the version of the above file
system agents, if any, that already exist on that server.
If the installation script detects a supported platform,
you will be prompted to install the latest versions of the
above file system agents.
4.9 Installation Considerations for the Arcserve Backup Patch Manager
The following section provides information about general
considerations while installing the current release for
Patch Manager.
- When installing the current release for Arcserve Backup,
whether it is a new installation or an upgrade from a
previous version, Arcserve Backup will not automatically
install the current release of Patch Manager, it will need
to explicitly be installed from the current installation
media to update the Arcserve Backup components.
- You will need to upgrade to current release of Patch
Manager if you have an earlier version in order to get the
patches for the current release of Arcserve Backup. For
more details, please refer to the Arcserve Backup Patch
Manager Readme.
- While upgrading the client and if the client is connected
to the Staging server, ensure that the Staging server is
also upgraded.
4.10 Installation Considerations for the Arcserve Backup Agent for Virtual Machines
The following section provides information to consider when
installing the Arcserve Backup Agent for Virtual Machines.
4.11 Installation Considerations for the Client Agents
The following section provides information about
installation prerequisites, configurations, and issues to
consider before installing the Arcserve Backup Client
Agents.
Agent for Windows
- You can remotely install the Client Agent on Vista
machines, but may need to disable local account filtering
first. User Account Control (UAC) is a Vista feature that
blocks local administrative accounts from remotely
accessing administrative shares (C$, Admin$).
Before you begin, determine whether the Vista machine is
part of a domain or part of a workgroup. Use a Domain
Administrative account if the target computer is part of a
domain. Grant a domain account with administrator
privileges on the Vista machine and use that domain account
to log on. You may then remotely install the Client Agent
on the Vista machine.
If the target computer is part of a workgroup, disable the
client computer's local account filtering policy by
creating a new registry key, as follows:
DWORD value: LocalAccountTokenFilterPolicy
Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\
New Value: 1
After installation, set the LocalAccountTokenFilterPolicy
setting to 0 to re-enable local account filtering.
- In a clustered Arcserve Backup environment, the Client
Agent for Windows needs to be installed on the local drive
on each cluster node.
- If you install the Client Agent (Windows, UNIX) on a
virtual machine, you will be able to back up the data as if
it were a physical machine.
- When installing Arcserve Backup as an Agent for Windows on
Windows Server 2008 Core, you should run mastersetup.exe
directly from DVD\Install. If you use setup.exe from the
DVD root, you will launch DemoShield, which requires
Internet Explorer to run. Internet Explorer is not
available in Windows Server 2008 Core operating systems.
4.12 Installation Considerations for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
To back up and restore SAP R/3 for Oracle data on UNIX and
Linux Data Mover, consider the following:
- The Arcserve Backup for UNIX and Linux Data Mover option is
required.
5.0 Upgrade Considerations
The following section provides information about upgrade
prerequisites, configurations, and issues to consider
before upgrade the Arcserve Backup base product.
5.1 Upgrade Considerations for the Arcserve Backup Base Product
The following section provides information about upgrade
prerequisites, configurations, and issues to consider
before upgrade the Arcserve Backup base product.
6.0 General Considerations
The following section provides general information to
consider when using Arcserve Backup:
- We recommend using the Agent for Open Files when backing up
the Citrix MetaFrame Presentation Server 3.0.
- Before restoring information to the Citrix Access Suite,
stop the CitrixXTE Service. After the restore operation is
complete, run a discovery in the Access Manager.
- The Arcserve Backup command line uses AES 256-bit
encryption to communicate with the Arcserve Backup base
product.
- If you are running Microsoft SQL 2000 or VSS backup and
restore jobs on any 64-bit Windows system, refer to the
following articles at Microsoft and download a hotfix:
- When restoring folders and files, note the following:
- When Restore and Preserve Directory Attributes and Security
Information is enabled, and Restore and Preserve File
Attributes and Security Information is disabled, the
encryption attributes of files are restored.
- When Restore and Preserve Directory Attributes and Security
Information is enabled, and Restore and Preserve File
Attributes and Security Information is disabled, the
compression attributes of directories are not restored.
- When Restore and Preserve Directory Attributes and Security
Information is disabled, and restore and Preserve File
Attributes and Security Information is disabled, the
encryption attributes of files are restored.
- When connecting to a new server, you must provide the
Arcserve Backup user account, caroot.
Note: The caroot user profile controls access only to the
Arcserve Backup Manager and backup-related functions, and
should not be confused with the user credentials required
to log in to the Microsoft Windows operating system. For
more information regarding this user profile, see the
Arcserve Backup Administration Guide.
Important! You should not leave the password blank for
caroot.
- The following information concerns the backup and restore
of Hyper-V based virtual machines. Note that all
configurations supported on Windows 2008 64-bit systems are
still supported when Hyper-V is enabled on those systems:
- Backing up and restoring data on Virtual Machines is
similar to the backup and restore of physical machines when
the Agents (Agent for Open Files, Client Agent for
Windows/Linux, SQL, Exchange and SharePoint) are installed
in the guest OS of the Virtual Machines.
- Installing the Arcserve Backup base product and other
options on Virtual Machines in Hyper-V is not supported, so
the local Disaster Recovery Option is not supported on
Virtual Machines. However, when the Client Agent is
installed on a Virtual Machine, remote Disaster Recovery is
supported the same as if on a physical machine.
The following provides general information to consider when
using the Arcserve Backup Global Dashboard:
- You can protect your central database using the Arcserve
Backup Agent for Microsoft SQL Server.
- During a full data synchronization, the Arcserve Backup
database engine service is stopped for a few minutes. This
may affect the status of any backup jobs in Arcserve Backup
that are already running (especially jobs related to
logging any information in the branch ASDB).
- If you need to restart the Microsoft SQL Server, verify
that all the Global Dashboard services are also restarted.
The following provides general information to consider when
using the Arcserve Backup Agent for Virtual Machines:
The following section provides general information to
consider when integrating Arcserve Backup and Arcserve D2D:
- When integrating Arcserve Backup and Arcserve D2D, Arcserve
Backup skips Arcserve D2D destination folders from
incremental/differential backup jobs. This is done to help
ensure data consistency and recoverability of Arcserve D2D
files when restoring from Arcserve Backup
incremental/differential backup sessions.
- The following are unsupported scenarios and limitations to
consider when backing up Arcserve D2D destination files and
folders:
- For Arcserve Backup to skip the Arcserve D2D destination
files and folders, you must select the Arcserve D2D folder
at the root or shared folder level. Therefore, Arcserve D2D
integration with Arcserve Backup will be supported in the
following scenarios:
- User selects the shared or root folder.
- User selects the volume that has the Arcserve D2D
destination.
- User selects the entire machine.
For example, if c:\D2D is configured as a D2D folder and it
has a D2D destination under machine D2D-server1 as
c:\D2D\D2D-server1, then the user has to select c:\D2D or
c:\ or the entire machine as a backup source.
- Arcserve Backup backs Arcserve D2D destination folders
using VSS. If the creation of a VSS shadow copy fails,
Arcserve Backup skips the entire Arcserve D2D destination
folder when executing the backup.
- If a shadow copy is created specifically for backing up
Arcserve D2D destination, the backup of the Arcserve D2D
destination will not be consistent in the following
scenarios:
- The Arcserve D2D destination of a machine is spread across
multiple volumes.
- The Arcserve D2D destination of a machine is spread across
multiple root folders.
This behavior occurs because the Client Agent for Windows
deletes the VSS shadow copy after Arcserve Backup backs up
the Arcserve D2D destination root folder. If the Arcserve
D2D destination for the same machine is encountered, a new
VSS shadow copy has to be created again which will not be
consistent with the VSS shadow copy created previously.
7.0 Supported Upgrade Paths
If you are currently using one of the following releases of
Arcserve Backup, you can upgrade to this release from the
following products:
- Arcserve Backup r16 for Windows--Includes the General
Availability (GA) release and all of the latest service
packs.
- Arcserve Backup r15 for Windows--Includes the General
Availability (GA) release and all of the latest service
packs.
- Arcserve Backup r12.5 for Windows--Includes the General
Availability (GA) release and all of the latest service
packs.
Important! If you want to upgrade from BrightStor ARCserve
Backup v9, BrightStor Enterprise Backup v10.5, BrightStor
ARCserve Backup r11.1, or BrightStor ARCserve Backup r11.5,
you must uninstall the previous release and then install
this release of Arcserve Backup. However, if you wish to
retain the database information from your previous
implementation, you must upgrade the previous
implementation to Arcserve Backup r12.5 GA release (with no
SP), and then upgrade from Arcserve Backup r12.5 to this
release. To obtain Arcserve Backup r12.5 installation
media, contact Arcserve Support. For all other previous
releases of BrightStor ARCserve Backup or BrightStor
Enterprise Backup earlier than v9, you must uninstall the
previous release before you install this release.
Please also note the following:
- Silent or remote upgrades do not allow you to change the
server or database types.
- If the Arcserve Backup Database (ASDB) was SQL Express 2005
prior to upgrade, the upgrade installs SQL Express 2008.
7.1 Backward Compatibility
This release of the Arcserve Backup server component can
back up data using agents from the following releases:
- Arcserve Backup r15 (and all service packs)
- Arcserve Backup r12.5 (and all service packs)
- Arcserve Backup r12 (and all service packs)
8.0 Known Issues
The following sections provide information about issues
known to exist in Arcserve Backup for this release.
8.1 Known Issues for the Base Product
The following issues relating to the Arcserve Backup base
product are known to exist in this release:
- Due to a NetBIOS limitation, computer names longer than 15
characters are truncated to 15 characters, including when
you set up a host server.
- If you install Windows Server 2003 Service Pack 1 using an
Emulex Fibre Channel Card, download the latest Windows 2003
Storport HBA drivers from the Emulex website. A problem
with the Emulex driver released with Windows 2003 SP1
prevents Arcserve Backup from initializing correctly unless
you update the Emulex driver.
- If you use the Master Setup to install Arcserve Backup
remotely to a system in another Windows domain, you may
receive a message indicating that the installation failed
when it is successful. This behavior occurs because the
Master Setup cannot accurately detect the activity on the
remote machine in the other domain because of a firewall or
due to a lost network connection. Check the installation
status on the remote machine to verify that the
installation succeeded.
- If you import a DLTWORM-capable media into a library that
has not converted to WORM, the Quick erase and Convert to
WORM media option is disabled. You must perform a full
inventory of tapes to enable this option because this
capability can be recognized only by reading the media.
- If you use WORM media as the destination for any
cross-platform jobs involving the Arcserve Backup for UNIX
Agent for Oracle or the Arcserve Backup for Linux Agent for
Oracle, these agents may not behave as expected. Because
WORM media is not supported on the UNIX or Linux agents,
these jobs may use destinations other than the WORM media.
- Installing 32-bit components on a 64-bit machine generates
two copies of the file PortsConfig.cfg on the machine. The
PortsConfig.cfg file for the 32-bit components is in
c:\Program Files (x86)\CA\SharedComponents\ARCserve Backup
and the PortsConfig.cfg file for the 64-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 scripts to back up remote installations of
Arcserve Backup Agent for Oracle to the Arcserve Backup
Server may fail if the remote machine was registered to
Arcserve Backup server with a fake name.
- Job redirection is no longer supported. As an alternative,
you can use the makeup job feature. Refer to the
Administration Guide for more information regarding makeup
jobs.
- When the Windows security policy is enabled on the machine
where Arcserve Backup is installed, an audit log is
recorded in the event log at the time of a system
application startup, such as Task Manager.
- If you apply the license keys for two or more different
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 Arcserve Technical Support to correct the
license count.
- The Tape Compare utility does not support comparing tapes
that were created using multiplexing or encryption.
- Broadcast Alerts do not function on systems running
Microsoft Windows Server 2008. This behavior is observed
because Microsoft Windows Server 2008 does not support
messaging service.
- After you restore the Arcserve 64-bit ASDB, you must
perform at least one full backup of the Arcserve Backup
database before you perform an incremental or a
differential backup. This task helps ensure that Arcserve
Backup database backup sessions contain the most current
data. This task helps ensure that Arcserve Backup database
backup sessions are current.
- A NetBIOS name resolving problem between local and remote
machines may prevent you from obtaining information from
the Diagnostic Wizard. Diagnostic utilities use NetBIOS
names to communicate. To avoid communication problems,
verify that the remote system is on the network and that
the machine name is correctly mapped to the IP address. You
should also purge and reload the NetBIOS Remote Cache Name
and NetBIOS Remote Machine Name tables. To do so, perform
the following steps:
- Confirm that the remote machine is reachable across the
network and that the IP Address matches the remote machine
name. Run the following commands to confirm:
- ping <MachineName>
- ping <IPAddress>
- ping –a <IPAddress>
If the remote system can be pinged and the name matches the
IP address, the Diagnostic Wizard should experience no
problems. If the system cannot be pinged at all, check the
network connections and ensure the system is operational.
If the name does not match the IP address, continue.
- Open a command prompt and run ipconfig /all to show the
current IP configurations and other network configurations
of a machine. Examine the command output for mistakes in
your configurations. If mistakes exist, the network cannot
communicate properly.
- Open Network Connections.
- Double-click <Connection Name>.
- Click the Support tab.
- Click Details.
- Note the values for "WINS Servers". The WINS Servers
provide the NetBIOS name resolution for your remote
servers.
- Ping the WINS servers using the commands in Step 1.
- Run the following command to check the NetBIOS Remote Cache
Name Table:
nbtstat -c
Using NetBIOS over TCP/IP, this command lists the cache of
remote machine names and their IP addresses, and outputs
statistics into four columns: Name, Type, Host Address and
Life (sec). Examine the output and verify the remote
machine IP address matches its machine name for all types
of the machine name specified.
If the machine name matches the IP address for all types,
the remote system can be accessed by its NetBIOS name.
If the machine name does not match the IP address, or if no
such items exist in the table, proceed to Step 4.
- (Optional) If you find a mismatch in the mapping between a
System Name and IP Address, run the following command to
purge the Server Name and IP address mapping on both the
local and remote machines. Otherwise, skip to Step 5.
ipconfig /flushdns
- Purge and reload the NetBIOS Remote Cache Name Table:
nbtstat -R
- Run nbtstat -c again. The table should now be empty, or
contain only a few new items with lives of about 600
seconds.
- Check the NetBIOS Remote Machine Name Table:
nbtstat -a <RemoteName>
This command lists a remote machine name table, given the
machine name you specify.
nbtstat -A <IPAddress>
This command lists a remote machine name table, given the
IP address you specify.
The tables should show identical information: the name of
the remote system as "Registered" for the IP Address.
If the steps above do not solve your NetBIOS communication
problem, you must contact your WINS server administrator to
reconfigure the system.
- The Arcserve Backup database may not contain up-to-date
database information (for example, file lists and physical
locations) and the Restore Manager, Restore by Tree, source
directory tree may not display up-to-date information
immediately after you restore the Arcserve Backup database
to its original location (original computer or original
database instance) or to a different location (different
computer or different database instance).
To remedy this problem, do the following:
- After you restore the Arcserve Backup database, use the
Merge utility to merge the Arcserve Backup database backup
sessions.
- Close and then reopen the Restore Manager window to refresh
the information that displays in the Restore by Tree source
directory tree.
- When you modify a makeup job that was automatically created
after a full-node backup job has failed, you will see that
the MSDEWriter, SQLServerWriter and WMIWriter objects have
been selected in the Backup Manager, Source directory tree.
These objects are displayed with excluded text which will
not be backed up when the makeup job is submitted.
- When you log off an interactive Windows session while a
message (such as tape mount) is still displayed, some
temporary files will remain in the Arcserve Backup Temp
folder.
- Backup jobs performed with Windows 2003, and Windows 2008
systems may include the following files that Microsoft
recommends not be backed up, even if they are specified in
the FilesNotToBackup registry key:
- index.dat
- MsDtc.log
- dtctrace.log
You should skip these files when restoring the database.
- Arcserve Backup operations executed on the same tapekey
after tapecopy has been executed could affect either the
source or the destination tape. Job failure may also occur
if a session is added to either the source or destination
tape after Tapecopy because Arcserve Backup may not be able
to restore that added session. This is because a tape is
identified by three items: the tape name, the random ID,
and the sequence number. The combination of these three
tape identifiers is called the tapeKey. When submitting a
tapecopy job with a command such as “tapecopy –s –d –t”,
Arcserve Backup automatically assumes the tapeKey of the
destination tape is the same as the source tape and views
it as if only one tape exists.
If you do not want the destination tape to be the exact
same as the source tape, you can include the –idr switch
with the tapecopy command so that Arcserve Backup
automatically assigns a different random ID to the
destination tape and ensures that the destination tape is
not exactly the same as the source tape.
- If you include the –idr switch with the tapecopy command,
the random ID of the destination tape will not be the same
as the source tape and as a result, the destination tape
could not be used at a later time for disaster recovery
purposes.
- If you do not include -idr switch with the tapecopy
command, you could then use the destination tape at a later
time to perform a disaster recovery operation because the
destination tape will be exactly the same as the source
tape.
- This release of Arcserve Backup automatically creates a new
media pool with the same name given to media in an r12 or
prior environment and inventoried in the current
environment.
- When you run ca_recoverdb.exe to recover the Arcserve
Backup database, you may receive the following warning
message:
W5110 The Database is no longer available
During recovery, the Arcserve Backup database is offline.
So any client programs trying to access the database during
this period will be denied. This message does not prevent
recovery from completing successfully.
- If you are performing backup jobs on a Windows 2008 or
Vista system and have specified Pre and Post job commands
in the Global Options dialog, Arcserve Backup ignores the
user name and password on the Pre/Post tab and executes the
commands even if you enter an invalid user name and
password combination. Security validation is performed only
on Windows 2003 or XP systems.
- In Citrix 4.5, you must enable Read/Execute privileges on
the Arcserve Backup Home folder to publish the product.
- The first job run after you successfully recover the
Arcserve Backup database appears in the Status Manager with
the same Job ID as the ASDB restore job. This is because
the Job ID assigned to the ASDB restore job is lost after
the ASDB is restored successfully.
- When run with Microsoft Office 2003, Arcserve Backup Job
Status Manager can experience excessive "handle leaks", too
many open register keys that are no longer in use. Install
the latest Microsoft Office 2003 service pack to avoid this
problem.
- When the Catalog database folder is changed to a long path
name (greater than 140 characters) and backed up, the
catalog files may not be kept in the catalog database and
an E3408 error is recorded in the Activity Log.
- Client Agent Password Security is only supported for the
Client Agent for Windows, including the Arcserve Backup
Agent for Open Files and VSS Writers. If Password Security
is enabled and any database, application, or messaging
Agent is installed on the same machine as the Client Agent,
whole node backup is not supported. System Security is the
default setting. If you have enabled Password Security on
the Arcserve Backup Primary or Standalone server, the
automatically-generated Database Protection Job will fail
for the job queue and Arcserve Catalog Database. You must
not enable Password Security in the Agent Configuration on
any machine running a database, application, or messaging
Agent before submitting the job.
- The following issues related to SIS (single instance
storage) are known to exist in this release:
- For jobs shown in the Activity Log, the Media Compression
Ratio and the Media Remaining Capacity display as 0 because
these parameters are not supported by the device.
- Arcserve Backup does not support Windows passwords that are
24 characters and longer. When you add a Windows agent
machine to Arcserve Backup, you are prompted for a hostname
and password. Even though Windows supports a long password
here, Arcserve Backup does not and login will fail.
- Arcserve Backup does not support restoring a Job Queue
session to its original location using normal data recovery
processes.
- Due to a known issue regarding the start up sequence of
Arcserve Backup and Microsoft SQL Express, or SQL Server
installed on the same machine as Arcserve Backup, the Event
Log may show the following errors after a system reboot:
- Failure Audit: 18456 (Source MSSQL$ARCSERVE_DB) - The SQL
Server service is not running but client programs are
trying to log in, and so, fail.
- Error: 17187 (Source MSSQL$ARCSERVE_DB) - The SQL Server
service is not running, so it cannot accept a client
connection.
- Warning 3: (Source SQLBrowser) - This warning is recorded
because service starts automatically. Although Arcserve
Backup does not use the service setting, the installer
changes it. This service should not have been changed to
start up automatically. Set the SQL Server Browser service
to 'disabled' to avoid this warning.
To eliminate Warning 3, perform the following steps:
1. Click Start, Control Panel, Administrative Tools,
Services.
2. From the list of services, double-click SQL Server
Browser service to open its properties.
3. Change the startup type to Disabled.
4. Click OK. Rebooting should now proceed without this
warning.
These errors are related to the sequence in which Arcserve
Backup and SQL Server services are started and can be
eliminated if you adjust the following Arcserve Backup
services that depend on SQL Service to start:
- Arcserve Backup Database Engine
- Arcserve Backup Management Service
- Arcserve Backup Universal Agent
- Arcserve Backup Tape Engine
Note: If SQL Server is installed on a remote machine,
rebooting Arcserve Backup does not affect it.
To adjust Arcserve Backup services
- Determine SQL Server service name.
Find the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLXXXX, where XXXX is the unique name of the SQL Server and MSSQLXXXX is the SQL Server Service name.
- Set Arcserve Backup services to depend on SQL Server
service to start up by using the Microsoft sc utility (see
Using Utility steps a through c, below) or by manually
setting the registry keys (see Manually editing the
registry, below).
Using the utility:
- Install the Windows support tool, "SUPTOOLS.MSI" from your
Windows installation CD. Go to the <CD-ROOT>\SUPPORT\TOOLS\
directory.
- Run the Command Prompt: Start, All Programs, Windows
Support Tools, Command Prompt.
- Type the following in the open Command Prompt window:
sc config CASDBEngine depend= MSSQLXXXX
sc config CASMgmtSvc depend= MSSQLXXXX
sc config CASUniversalAgent depend= MSSQLXXXX
sc config CASTapeEngine depend= MSSQLXXXX
- Go to step 3.
Edit the registry manually:
Create a Multi-String value named "DependOnService" under
each of the following keys and set its value to your SQL
service name (see step 1).
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASDBEngine
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASMgmtSvc
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASUniversalAgent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASTapeEngine
- Reboot the computer. The errors should not reappear.
- To avoid problems expanding the Microsoft Network in
Arcserve Backup Manager on Windows Server 2008 machines,
ensure Computer Browser service is enabled and started.
This service is disabled on Windows Server 2008 systems by
default.
- If you are using Windows XP, the Arcserve Backup Manager
cannot log in with Windows Authentication. This is due to a
problem with the Windows XP ForceGuest registry feature.
This problem is limited to machines that are members of a
workgroup; if the machine is a member of domain, log in
proceeds. To avoid the problem, use regedit to set the
ForceGuest registry value to 0. The key is located under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.
- When you install this release of Arcserve Backup on the
cluster node of a Windows Server 2008 cluster, the Arcserve
Backup Database is listed in the cluster virtual name on
the Backup Manager.
- When default collation is selected from Language Support
Options, Look in Directory field on the Restore by Query
screen is Kana-insensitive, Width-insensitive and
Case-insensitive. When Japanese collation is selected,
operations are Kana-sensitive, Width-sensitive and
Case-sensitive. For the Look in Directory field on the
Restore by Query screen, and the Volume field on the Search
dialog, you may specify only uppercase drive letters.
- Security information for the Agent for Microsoft SQL is not
automatically loaded after upgrading from earlier Arcserve
Backup versions to this release. You must retype password
to continue.
- Arcserve Backup does not support integration with the
Microsoft Management Console.
- If the Arcserve Backup database is configured to use SQL
Server, the Database Protection Job may not be able to
successfully back up the Arcserve Backup database in a
clustered environment when failover happens from one node
to another node. If such a situation occurs, run the
Database Protection Job again manually to verify the
Arcserve Backup database is being successfully backed up.
- When performing a full node backup, you may skip the system
state by adding the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\ClientAgent\Parameters
Value Name: SkipSystemStateBkup
Data Type: REG_DWORD
Value: 1
For 32-bit OS, local backup jobs, add the key here:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Task\Backup
Value Name: SkipSystemStateBkup
Data Type: REG_DWORD
Value: 1
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe
Backup\Base\Task\Backup
Value Name: SkipSubmitDetailEX
Data Type: REG_DWORD
Value: 1
- Microsoft does not recommend backing up symbolic links on
Windows Vista, Windows Server 2008, Windows Server 2008 R2,
and Windows 7 systems. This approach is not recommended
because the default locations for user data and system data
(for example, the Documents and Settings folder) are
different than that of previous Windows operating systems.
As a best practice, you should back up the folders that are
referenced by the symbolic link, rather than the link
itself.
- You may experience slow performance when you browse Windows
Server 2003 x64 systems from the Windows Systems object in
the Backup Manager directory tree. Arcserve Backup
demonstrates this behavior due to various environmental
conditions that can cause VSS writers to enumerate the VSS
metadata. To remedy this problem, you can prevent the
Backup Manager from enumerating VSS metadata. However,
without the VSS metadata, you can browse only the disks for
the specified computer. To stop the Backup Manager from
enumerating VSS metadata, set the following registry key to
3: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\ClientAgent\Parameters\VSSWriterBrowseOption.
- When restoring Hyper-V virtual machines to an alternate
location, Arcserve Backup may not be able to power on the
target if the CD/DVD name is not the same as that of the
original backup. To remedy this problem, verify that the
CD/DVD name of the destination is the same as the source
location before you submit the restore. An alternate
solution is to edit VM settings after restore is complete
and change the CD/DVD location to one available on the
destination server.
- When restoring Hyper-V virtual machines to an alternate
location, Arcserve Backup may not be able to power on the
target if the friendly name of the network switch is not
the same as that of the original backup. To remedy this
problem, verify that the friendly name of the network
switch of the destination is the same as the source
location before you submit the restore. An alternate
solution is to edit VM settings after restore is complete
and change the network switch name to one available on the
destination server.
- When you submit backup jobs to removable media such as RDX,
avoid setting both Eject Media and Export Options. Export
options override the Eject Media options but because this
device does not support exporting, the device is not
ejected upon job completion.
- In Job History, there is no device/media information for
sessions backed up to a RAID group because a RAID group
typically contains multiple devices, yet appears as a
single device to the application.
- When saving a Data Mover backup job script from the Backup
Manager console, the Data Mover's source, destination, and
global options checks are not executed. Therefore, the GUI
will not show any messages to warn the user or block the
user from submitting the job and removing the unsupported
options. If you reload the saved job script from the Job
Status Manager, the job will fail.
Select one of the following options as a workaround:
- From the Backup Manager console, click the Submit button to
submit your job. The Security and Agent dialog opens.
Click OK and the Submit Job dialog opens. Click the Save
Job button to save the job script.
- If you select the Save or Save As menu to save the job
script, you can reload the job and modify this job in the
Job Status Manager, and then re-submit the job. All checks
will then be executed.
- If you select the Save or Save As menu to save the job
script, you can click the Open menu from the Backup Manager
console to open the job script and then click the Submit
button to submit the job. All checks will then be executed.
- Arcserve Backup supports only one writer (e.g., Oracle,
MSDE) as a source disk in one backup job through
Transportable Shadow Copies, i.e., HDVSS. If you include
other types of source disks to this one backup job, the job
will fail.
- When you select Add Agent/Import/Export menu from Arcserve
Backup to register a server that has multi IP addresses,
Arcserve Backup Group View will only recognize the first IP
address. Arcserve Backup Group View will not be able to
change an IP address after a node is registered. In the
case of Classic View, you can change it by selecting Agent
Modification from the Context menu.
- The Job Status Manager cannot display Activity Log data for
data mover servers when the Group by Job option on the
Activity Log tab is specified.
Important! This behavior occurs only when jobs are
submitted using UNIX/Linux Data Mover backup on the Backup
Manager Start tab.
- If the Arcserve Backup uses SQL Server as its database and
the SQL instance name is "ARCSERVE_DB", use
ca_recoverdb.exe to recover your Arcserve Backup database,
instead of Database Recovery wizard.
- When adding a cloud connection from the Device Manager and
you enter the domain password and proxy credentials, the
system caches the credentials. If you add another
connection and specify incorrect domain password and proxy
credentials or leave it blank, the system picks up the
cached credentials and successfully adds the cloud
connection.
As a workaround, you can delete the cookies from the
computer you are working from or reboot. This will cancel
out the cached credentials.
- After migration job completes for a disk staging job, the
restore by session method searches for the specific file in
two sessions (staging session and migration session), while
the restore by query method searches the file in only one
session (staging session or migration session, not both).
Note: Creating a vault after migration completes specifies
the requested file in only one session (staging session or
migration session, not both) which places only one tape
into the vault.
- If your computer credentials have changed, you cannot open
the Copy, Purge, or Count Utilities from Arcserve Backup
Manager. This is a Windows restriction stating that if you
use an existing user name to create a connection to a
shared resource, then any other user name will fail to
create the connection to the same resource.
- When you submit a staging job with FSD as the staging
location and Cloud Device as its destination, the migration
job does not resume after an unplanned cluster failover
occurs as the tape engine needs time to initialize the
cloud device.
As a workaround, Arcserve Backup creates a makeup job for
the failed migration job to continue the migration process.
- For the reason that Windows cannot access binary files
after a failover on a cluster environment due to the
back-end process of a failed caauthd.exe file, you will not
be able to log into Arcserve Backup with a valid user name
and password.
As a workaround, restart the Arcserve Backup Domain Server
Service.
- To recover data from backup sessions that were migrated to
Eucalyptus Cloud devices using a prerelease version of
Arcserve Backup r16, add the following property to the
CCIConfig initialization file.
File location:
<BAB_HOME>\CCI\Config\CCIConfig.ini
Property:
[Eucalyptus_Config]
UseOldDecode=1
Note: Set the value of the UseOldDecode property to 0 to
use the new devices. By default, the UseOldDecode property
is not present in the CCIConfig initialization file. The
default value of UseOldDecode is 0.
8.2 Known Issues for Upgrading to Arcserve Backup
- When upgrading from old, unsupported versions of Arcserve
Backup to this version, the Arcserve database (ASDB) is not
retained. To retain the ASDB, you should perform interim
upgrades; upgrade from an unsupported version to a
supported version to the current version. For more
information, see the topic, Supported Upgrade Paths.
- When you upgrade from older versions of 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.
- If server is upgraded to this release of Arcserve Backup,
Job History will not show Rotation or GFS jobs running
prior to upgrading.
- Due to differences in schema, previous Arcserve Backup
servers cannot share the ASDB with servers from the current
Arcserve Backup release. So if the server from this
Arcserve Backup release is installed with the same
instance, which has been used by a previous Arcserve Backup
server, the previous Arcserve Backup server will not work
normally, even if you choose NOT to overwrite the existing
database.
- Upgrade of 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 using Agent Deployment, the Automated
Upgrade option may be unavailable (appear dimmed or grayed
out). This happens because the Arcserve Backup database
contains no remote host information. To avoid this problem,
create the remote host to the ASDB in the Arcserve Backup
Manager, browse a remote host using a Arcserve Backup
Agent, or run backup jobs.
8.3 Known Issues for the Client Agents
The following issues relating to the Client Agents are
known to exist in this release:
- For the Client Agent for Windows, installing 32-bit
components on a 64-bit machine generates two copies of the
file PortsConfig.cfg on the machine. The PortsConfig.cfg
file for the 64-bit components is in c:\Program
Files\CA\SharedComponents\ARCserve Backup and the
PortsConfig.cfg file for the 32-bit components is in
c:\Program Files (x86)\CA\SharedComponents\ARCserve Backup.
If you make changes to one, you must make the same changes
to the other, or the components may not be able to contact
one another.
- Whole node backup operations are not supported with the
Client Agent for AS400.
- The Client Agent for SAP does not support Server Side
Encryption and Secure Migration.
- Alert Messages on 64-bit machines may display several
times, even after you click OK. If you disable your VMware
Adapters, messages display only once.
- For Citrix users who run Microsoft SQL as the Citrix
database, you must restart the Citrix SQL instance before
you restore the Citrix Metaframe 4.0 Server.
- When backing up files on IA64 systems, note that a file's
Last Access Time is not updated even when the Preserve file
access time option is not selected. This problem appears
limited to jobs in which the Keep Archive Bit option is
selected.
- When you uninstall an Agent from a remote system, you must
restart the universal agent service on that system and
restart the Backup Manager, otherwise, the Backup Manager
can still browse that remote system.
- If you are performing a remote or local backup using
Windows 2003 64-bit or Windows 2008 with the Delete source
files after backup to media (use with caution) option
enabled, you may need to set the following registry key to
0 to obtain the desired results:
Key:
DeleteDirInMigration
Location:
HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCserve Backup\ClientAgent\Parameters
Value:
0 to retain directory folders, 1 to delete them.
- The Client Agent for Windows lets you protect files and
folders that reside in virtual hard disks (VHDs) that are
mounted as volumes. If the mounted VHD source data contains
hard link files and folders that are not associated with
the operating system's system state, Arcserve Backup backs
up the hard link files as multiple, individual files. As a
result, the amount of disk space that is required to store
the backup data will exceed the actual size of the data
that you are backing up.
- When you submit a restore job and it fails due to extended
time against the default timeout session, the connection
breaks and the agent fails. This scenario is based on
restoring files from a session which is spanned across
several tapes.
As a workaround, you can increase the ReceiveTimeout value
where it gives the job enough time to complete and achieve
the expected results. You can do this by going to the
following registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCServe Backup\ClientAgent\Parameters\ReceiveTimeout
To change the ReceiveTimeout value, right-click
ReceiveTimeout and select Modify. Change the Value data
field to a value that prevents the restore job from failing.
Note: The ReceiveTimeout value is in seconds. For example,
7200 seconds = 2 hours, if the restore job continues to
fail at 7200, you can increase the value data to a higher
value.
8.4 Known Issues for Arcserve Backup Licensing
The following issue is known to exist in this release:
- When applying trial keys, be aware that the most recent key
overrides any previously-applied keys for the same
component. For example, suppose you applied two keys for
the Exchange Server agent. The first was for 3 users and
the second was for 5 users. The permitted user count is 5
because that is the most recently applied key. This issues
affects trial licenses applied on the same day.
8.5 Known Issues for the Agent for Informix
The following issues relating to the Agent for Informix are
known to exist in this release:
- If you use Informix Backup and Restore utility, rather than
the Backup Manager, you must define security information
using the Informix Agent Batch Job Configuration utility
dbacfg before submitting any backup or restore jobs.
Note: For more information about the dbacfg utility, see
the Agent for Informix Guide.
- When using remote 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 Arcserve Backup
server based on the local time from the Informix server.
Therefore, time differences between the Arcserve Backup
machine and the Informix server machine can cause backup or
restore delay. To prevent this delay, synchronize the time
between both machines.
- When using the Client Agent with the Restore by Tree method
for your restore operation, databases appear under the
Microsoft Windows Network icon in the Restore Manager.
- When expanding an Informix instance fails and the activity
log displays "Agent function entry point not supported",
the failure is likely due to dbaifmx.dll failing to load.
We recommend installing Informix by GUI instead of silent
install to avoid this problem.
- For remote backups, you must enable File and Printer
Sharing for Microsoft Networks on the agent machine you are
backing up.
- The Net Logon service must be started to support
pass-through authentication of account logon events for
computers in a domain.
- The Agent for Informix does not support compression at the
Agent side.
- The Agent for Informix does not support Server/Agent Side
Encryption and Secure Migration.
- A restore job will fail if you attempt to restore multiple
Informix instances on the same media because Arcserve
Backup cannot restore them sequentially. To successfully
restore multiple Informix instances, you can restore them
one by one by submitting a new job for each instance after
the previous one has been successfully restored.
- Encryption is not supported. If server side encryption is
enabled for Informix backups, the following message is
displayed when the job is submitted:
Warning: Encryption will be skipped for Informix backups
- Backup/restore jobs may fail if you repeat the job. In an
Informix instance, Windows records the dbspace that is
being backed up or restored until the job completes. If
that job fails for any reason, the Windows registry does
not erase the key value for that dbspace. If you wish to
perform another backup/restore job of the same Informix
instance, the job will fail unless you erase the registry
key value after the failed backup/restore job occurs:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\DSAgent\CurrentVersion\agent\dbaifmx@<Informix_Instance_Name>\LastObject
- When running a batch job configuration using the Agent for
Informix, you can enter only the machine name in the Server
and Domain fields. You cannot enter machine IP addresses.
8.6 Known Issues for the Agent for Lotus Domino
The following issues relating to the Agent for Lotus Domino
are known to exist in this release:
- If possible, avoid server names greater than 79 characters.
Arcserve Backup will truncate characters that exceed the
79-character-limit and replace the last two (characters 78
and 79) with a 01. If you have additional Domino Servers
that exceed this limitation, Arcserve Backup will truncate
the server name and replace the last two characters in the
name using a sequence such as 02, 03, 04. For example:
- If the Domino Server name is 79 characters or more,
Arcserve Backup will truncate the name down to 79 and
modify the last 2 remaining characters as shown in the
following examples:
Original: User11111111112222222222333333333344444444445555555555666666666677777777778888888888
First Server: User11111111112222222222333333333344444444445555555555666666666677777777778888888801
Additional: User11111111112222222222333333333344444444445555555555666666666677777777778888888802
Note: If you are upgrading to the current version of the
Arcserve Backup Agent for Lotus Domino, the character
limitation for server names is still 30 characters. The
79-character limitation is only for new server names.
- If you use Arcserve Backup to back up Lotus Domino 8.5.1
x32, the Domino Server task window displays a list of
unknown tasks, such as, Task name: 5B740001:0001, Status:
[. To prevent this from happening, apply the latest fix
packs. You can download the packs from the IBM Support
Portal and click Notes/Domino 8.5.1 Fix Pack 5 Release
Notice & Fix List.
Note: This issue applies to the following environment:
Domino Agent: Lotus Domino Agent r15 or r16 on Windows
Server 2003 x86
Application: IBM Lotus Domino 8.5.1 x86 (DAOS enabled)
8.7 Known Issues for the Agent for Microsoft Exchange Server
The following issues relating to the Agent for Microsoft
Exchange Server are known to exist in this release:
- The agent does not support recovering database level
backups of older versions of Microsoft Exchange Server (for
example, Exchange Server 2007, Exchange Server 2010) to
Exchange Server 2013 databases.
- The r16.5 version of the agent does not support document
level backups of Exchange Server 2013 data.
- When you select Microsoft Exchange server directory as the
backup source and perform file system backup with the
client agent, please note the following:
- If the Exchange Information Store is running, the Exchange
server files will be skipped during the backup.
- If the Exchange Information Store is NOT running, the
Exchange server files will NOT be skipped during the backup.
- If you are restoring an old mailbox store session backed up
with the 11.5 version of the BrightStor ARCserve Backup
Agent for Microsoft Exchange Server to the Recovery Storage
Group, this version of the Microsoft Exchange Server Agent
creates all the mailbox stores of the entire storage group
to which the mailbox store you wish to restore belonged in
the Recovery Storage Group before the restore operation
starts actually restoring data.
- A new registry key was added to Arcserve Backup to control
how the Agent for Microsoft Exchange Server backs up
storage groups/mailbox databases using
multistreaming/multiplexing.
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Task\Backup\SingleStreamExchangeAgent
Values:
1 means Exchange storage groups are backed up in a single
stream
0 (or not set) means the behavior is unchanged (separate
streams are used)
- MAPI 6.5.8147.0 or higher should be installed at the
Exchange 2010 server in order to browse or restore Exchange
doc level data, otherwise it will fail.
- If Windows client agent and Exchange agent are installed at
the Exchange server and Windows client agent is set to use
the password security option, then the Exchange Doc level
is unable to browse for backup and restore.
- If you browse the Exchange Document level on two different
Arcserve servers using different Windows domain accounts,
then browsing at the Exchange Document level will fail. If
you encounter this problem, UnivAgent service will need to
be restarted in order to resolve this issue.
- If you choose the Encryption option for a backup job to
create a session, then perform a restore job of the backed
up session, the session will fail. If you do not choose
the Encryption option for the backup job but perform a
restore job of the backed up session anyway, the session
will not fail. This scenario only happens in r12.5.1 of the
Exchange Agent.
- For Microsoft Exchange Server 2013, when you restore a
mailbox database to a new Recovery Database and then fail,
verify that the Event Log of the application specifies the
following message:
"Exchange Replication Service VSS Writer failed restoring a
backup because the target database is online."
The message results to a known issue. Resubmit the restore
job to an existing Recovery Database.
8.8 Known Issues for the Agent for Microsoft SharePoint Server
The following issues relating to the Agent for Microsoft
SharePoint Server are known to exist in this release:
8.9 Known Issues for the Agent for Microsoft SQL Server
The following issues relating to the Agent for Microsoft
SQL Server are known to exist in this release:
- If an error message appears when you restore and move a
database that uses a long file name, rename the database
files using shorter file names and perform the restore
operation on the database.
- The Arcserve Backup manager and the Arcserve Backup Client
Agent must be stopped before uninstalling and reinstalling
Arcserve Backup Agent for Microsoft SQL Server if they are
installed on the same server as the agent.
- If a TCP/IP connection fails, or if the Port number has
changed, restart the Universal Agent Service.
- To support pass-through authentication of account logon
events for computers in a domain, the NetLogon service must
be started.
- When you log into Microsoft SQL Server using Windows
authentication to perform Virtual Devices-based backup and
restore operations, you must have system administrator
rights for Microsoft SQL Server. This is a Microsoft
requirement.
- If you uninstall a Microsoft SQL Server instance, some
components used by other Microsoft SQL Server instances on
the machine may be deregistered, including the Virtual
Devices mechanism used to perform backups. If this occurs,
the agent generates Backup Agent Error 511 ("Error creating
Virtual Device Interface: COM class not found") within the
error AE50015 ("Backup Failed"), or AE51004 ("Restore
Failed"). To address this error, perform the following
procedure:
- Locate the version of sqlvdi.dll that belongs to the newest
version of Microsoft SQL Server 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
- On a primary server running remote SQL, backup jobs
submitted via backup manager to the member server may run
slowly.
- Starting with release 12.0, the Agent for Microsoft SQL
Server is now a push agent. To include SQL database files
during a backup job, set the BackupDBFiles registry key to
1. The SkipDSAFiles registry key no longer applies to SQL
database files. For more information, see the Arcserve
Backup Implementation Guide or the Arcserve Backup Agent
for Microsoft SQL Guide.
- When restoring a SQL session, the session size shown in the
Restore Manager may be larger than the size of the actual
session.
- The Arcserve Backup Agent for Microsoft SQL Server does not
support backing up and restoring SQL Server databases where
the sum of the characters representing the instance name,
the database name, the file group name, and the data file
name exceeds 170 characters.
- Installing two or more instances of SQL Server concurrently
on the same machine creates multiple versions of the
SQLVDI.DLL file, which causes conflicts resulting in
database backup job failures. To resolve any SQLVDI.DLL
conflicts, ensure all instances of SQL Server are at the
same Service Pack, security patch or Hotfix level. You may
also restart the failed SQL Server instance to reload the
new SQLVDI.DLL file or reboot the machine.
- When performing a database restore job that fails, the job
continues after the error only if you are restoring by
session. If you are restoring by tree, subsequent sessions
will not be restored. This is because Restore by Tree
packages all sessions into a single node, while Restore by
Session packages all sessions into different nodes.
- After upgrading Microsoft SQL Server 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, Arcserve Backup Agent for Microsoft
SQL Server will be unaware of the new or changed instances,
and you may not have access to additional instances or the
additional features of the updated instance. You should
also perform your first backup of the upgraded or new
instances immediately after running the Account
Configuration utility. For information about account
configuration, see the Agent for Microsoft SQL Server
Guide.
- In a cluster environment, run the Universal Agent as a
Domain Administrator, rather than as LocalSystem. This is
to prevent a conflict of access privileges between the
agent and Microsoft SQL Server when backing up Microsoft
SQL Server databases.
- When you restore databases to an alternative location, the
restore operation can fail and return the following
messages:
Failed to restore backup session. (EC=VDI message: An abort request is preventing anything except termination actions.)
Or
Failed to restore backup session. (EC=Microsoft SQL Server Error 3634 (ODBC State = "37000"): [Microsoft][ODBC SQL Server Driver][SQL Server]The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\test2.mdf'.)
To prevent this behavior from occurring, perform one of the
following actions and then resubmit the restore job:
- When you perform full backups of data on SQL Server AAGs,
the secondary replica server uses the copy_only backup
option when processing the job. The copy_only option cannot
record the backup operation on the secondary replica SQL
server because secondary replica servers do not have write
permission to the databases. When the next differential
backup starts, SQL Server searches for and locates the most
recent full backup data on the primary replica server. At
such time, SQL Server dumps the differential backup data to
the most recent full backup data on the primary replica
server. Therefore, when you need to restore data from
differential sessions of secondary replica servers, restore
the full backup from the primary replica server before you
restore the differential backup from the secondary replica
server.
8.10 Known Issues for the Agent for Open Files
The following issues relating to the Agent for Open Files
are known to exist in this release:
- If you are upgrading the Agent for Open Files on a remote
computer using Unicenter Software Delivery, you must reboot
the target machine to complete the installation process
successfully.
- If you are running eTrust Antivirus 7.1.192 and the Agent
for Open Files on the same machine, you must apply a patch
to that machine to avoid experiencing slow performance.
Contact eTrust Antivirus Customer Support to obtain this
patch.
- The Agent for Open Files does not provide the eTrust
Real-Time scan engine with access to open files to prevent
viruses from presenting the scan engine with a version of
the infected file concealed as an uninfected file.
- When prompted to reboot your machine during remote
installation, reboot the machine manually for the remote
installation to be successful.
- The agent may not start if it detects that an Open File
Management product from another vendor is already running
on the server. Multiple Open File Management products
cannot function on the same server. To resolve this
problem, remove the existing Open File Management product
from your server and start the agent.
- Because of the way that Windows 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.
- If you install the Microsoft Cluster Service after you have
installed the Agent for Open Files, you must restart the
system to provide the agent with open file access to the
shared storage resources of the cluster.
- The Agent for Open Files does not support the Transactional
NTFS (TxF) infrastructure on Windows Vista and Windows 7.
Before you perform backups, make sure you close all
applications that have files open in a TxF context, such as
installation programs.
- The Agent does not support reparse points other than mount
points. All other kinds of reparse points including
symbolic link files, junction points, or hard links, are
treated as regular files.
- If you wish to add all files under a root volume to the
Agent for Open Files configuration, you must use wildcards
as shown in the following example. Specifying only the
volume label is not supported:
Use: C:\*.*
Do not use: C: or C:\
- When you remotely upgrade the Agent for Open Files on an
English System with Chinese locale, you must do the
following before you upgrade to ensure Unicode characters
are properly displayed:
- Open the Control Panel and choose Regional and Language
Options.
- Click Advanced.
- Choose the option, Apply all settings to the current user
account and to the default user profile.
- Restart the machine.
8.10.1 Microsoft Volume Shadow Copy Service (VSS)
The Agent for Open Files now includes support for Microsoft
Volume Shadow Copy Service (VSS). The following issues
relating to Microsoft VSS are known to exist:
- Full backups of Microsoft SQL Server 2005 are possible, but
not differential or incremental backups.
- In Windows 2003 R2, the DFS Replication Service Writer
appears when you expand the machine. In Windows Server
2008, DFS Replication is part of the system state.
Therefore, if you wish to backup DFS Replication in Windows
Server 2008, you must back up the system state.
- If the event log shows a
"VSS_E_WRITER_STATUS_NOT_AVAILABLE" error, this indicates
that a writer may have reached the maximum number of
available backup and restore sessions. Retrying may work
when the system is less busy. For more details, see the
Microsoft documentation:
http://msdn.microsoft.com/en-us/library/aa384995(VS.85).aspx
- VSS backups using the SQL Server writer fail when the
following Arcserve Backup VSS backup options are enabled:
- Use Transportable snapshot
- Retain Shadow Copy after Backup
The solution to this problem is to offline the shadow copy
destination disk before you submit the backup. After the
backup is complete, return the shadow copy destination disk
to an online status.
8.10.2 Oracle Volume Shadow Copy Service (VSS)
The following issues relating to the Oracle VSS are known
to exist:
- Instances of Oracle VSS Writer must be running and
functional in order to be browsed or backed up by Arcserve
Backup.
8.11 Known Issues for the Agent for Oracle (Windows)
The following section provides information on support for
the Agent for Oracle:
- Database files are excluded (skipped) from backups
submitted through the Client Agent for Windows up to a
limit of 2048 files. If your number of database files
exceeds this limit, you must add a DWORD registry value
called MaxFileFilter to make sure all database files are
properly excluded from the backups made with the Client
Agent for Windows:
HKEY_LOCALMACHINE\SOFTWARE\ComputerAssociates\CA ARCserve
Backup\Base\Task\Backup
Value Name: MaxFileFilter
Type: DWORD
Value: Set to a value greater than the number of database
files you wish to exclude. For example, if there are 3006
DB files, a value of 4096 ensures all database files are
excluded from the backup.
- When performing a backup of Oracle objects with copies,
such as the Oracle Tablespace or full database, the job
fails if the BACKUP_TAPE_IO_SLAVES parameter is false. To
set this parameter to true, perform the following steps:
- Open a sqlplus prompt.
- Enter the following command:
alter system set backup_tape_io_slaves = true deferred
- Restart the database.
- Set the Number of Copies option to a value greater than 1.
- Submit the backup job.
Note: You may also use the "show parameter
backup_tape_io_slaves" command to check the value of the
parameter.
- When you change the system time on the machine on which
Oracle Server and the Agent for Oracle are installed,
archive log backups will fail.
- When performing a database restore job that fails, the job
continues after the error only if you are restoring by
session. If you are restoring by tree, subsequent sessions
will not be restored. This is because Restore by Tree
packages all sessions into a single node, while Restore by
Session packages all sessions into different nodes.
- When performing an offline backup of an Oracle RAC9i
database with RMAN options from the GUI, Arcserve Backup
does not put the database into offline mode. To avoid this
issue, consider the following:
- Put the database into MOUNT status before performing
offline backups.
- Put the database into MOUNT status before performing full
database backups without control file restore, system
tablespace restore, or undo tablespace restore.
- Put the database into NOMOUNT status before performing full
database plus control file restores.
- For user tablespace restores, you do not need to do
anything.
- When submitting RMAN backup and restore jobs, please ensure
that the user is in the Administrators Group on the Oracle
Server machine.
- The Agent for Oracle (RMAN) does not support special
characters used in passwords (for example, '@'). Backup
jobs fail if used.
- The User Profile feature in this release does not support
RMAN command line backup for Oracle agents prior to release
12.5. (User Profile roles were introduced with the r12.5
version of Arcserve Backup.)
- This version of the Agent is case sensitive. If one
modifies the previous job or loads a previous job script
before upgrading the agent from earlier versions to the
current release, the Oracle database instance may appear
twice; once as uppercase and once as lowercase. This issue
affects only display, not performance.
- The current release of the Backup Server cannot back up
r12.5 or previous releases of the Oracle agent with RMAN
mode. If you want to perform RMAN backup of Oracle, please
use any version after r12.5.1.
8.12 Known Issues for the Agent for Oracle on UNIX and Linux Platforms
The following issues relating to the Agent for Oracle
(UNIX/Linux) are known to exist in this release:
- If you performed backup jobs with the Arcserve Backup for
UNIX or Linux Agent for Oracle using a version prior to
r11.5 and then upgraded to r11.5 or later, you cannot
restore the backup sessions using Arcserve Backup.
- We recommend that you back up the Oracle RMAN agent using
Disk to Disk to Tape feature (Disk Staging). If you chose
to back up directly to tape, note you will require more
storage media when doing a multichannel backup.
- This release of Arcserve Backup supports one (1) password
per Oracle encrypted backup.
- When different table spaces are backed up using different
passwords, you must restore them in separate jobs by
providing the correct passwords.
- This release of Arcserve Backup supports Oracle-encrypted
backup and decryption restore jobs submitted from the
Manager Console (GUI).
- This release of Arcserve Backup will not show the lock icon
for RMAN-encrypted sessions.
- Avoid changing passwords after a full backup is done. When
password must be changed, do so prior to performing a full
backup.
- Invalid incremental levels in Oracle 10g:
- For rotation or GFS-rotation jobs, incremental levels are
assigned as follows:
- full backup = incremental level 0 (RMAN)
- incremental backup = incremental level 1 (RMAN)
- differential backup = incremental level 1 cumulative (RMAN)
- For non-rotation jobs, you must set an incremental value
between 0 and 1 if you are running Oracle 10g. If you are
running an earlier version of Oracle, set an incremental
value between 0 and 4.
- You must use an RMAN Catalog to run jobs with the Oracle
option Include Control File Oracle option enabled from the
Oracle Restore Manager. If you enabled the control file
autobackup feature for the target database before using the
Agent for Oracle, use your own RMAN scripts to restore an
autobackup of the control file. For more information, see
the Arcserve Backup Agent for Oracle Guide.
- Compare Media to Disk is not supported on Agent for Oracle
sessions.
- Optimize Restore functionality is not supported for the
Agent for Oracle.
- The Restore by Media and Restore by Session options are not
supported for this release.
- Encryption Oracle data during the backup phase or the
migration phase only supports encrypt data at Backup
Server, encrypt data at Agent is not supported.
- Arcserve Backup does not support restoring multiple,
encrypted, Oracle RMAN sessions in a single restore job.
You must restore encrypted Oracle RMAN backup sessions as
individual restore jobs.
- The Agent can support session passwords if Encrypted data
at server side is selected from Global Options during
backup.
- You should reboot the machine whenever you install a new
Oracle database to avoid problems loading a driver
(OCI.DLL).
- If you experience problems expanding the Oracle database
after providing the correct login credentials, collapse the
machine and then re-expand the tree to refresh the cache.
- You must supply the correct host name when registering the
Agent for Oracle nodes in the Arcserve Backup database. If
the Agent machine has a fully qualified name (computer name
+ domain name, such as NodeName.arcserve.com), then the
full computer name must be used while registering the Agent
node.
- This release of Arcserve Backup does not support protecting
Oracle 11g Release 2 data stored on computers running AIX
6.1 operating systems.
- For the Agent for Oracle on non-global zones on Solaris 10
(SPARC, x86):
- If the common agent is not installed in global zones, you
must complete the following steps before you install the
Oracle Agent in non-global zones:
- global# mkdir -p /opt/CA/ABcmagt; touch
/opt/CA/ABcmagt/caagent
- global# ln -sf /opt/CA/ABcmagt/caagent /usr/bin/caagent
8.13 Known Issues for the Agent for Sybase
The following issues relating to the Agent for Sybase are
known to exist in this release:
- For remote backups, you must enable File and Printer
Sharing for Microsoft Networks on the agent machine you are
backing up.
- To support pass-through authentication of account logon
events for computers in a domain, the NetLogon service must
be started.
- The agent does not support table-level backup or restore
operations.
- We recommend that you avoid canceling restore jobs. If you
cancel a restore job, your database is marked Do Not
Recover or Suspect. If this happens, you must recreate the
database before starting another restore job.
- The Backup with Compare and Backup with Scan Tape options
are not supported for agent sessions. Additionally, the
Backup with Delete File option is not supported on agent
sessions.
- When Sybase Adaptive Server devices are mirrored, only the
actual device information (the database on the device) is
backed up; data in the mirror device is not backed up.
- The agent does not support cluster environment backup or
restore operations.
- The agent supports only the Restore by Tree and Restore by
Session options.
- 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"
- If a source is missing in restore tree view, it may be a
case-sensitive issue. Turn on case-sensitivity during
database setup process.
- Sybase database sessions backed up with BrightStor
Enterprise Backup 9.01 or 10.5.1 cannot be restored to
their original location. To resolve this issue, perform the
following steps:
1. Open Restore Manager, choose Restore by Session at the
Source tab.
2. Select the session you want to restore.
3. Choose the Destination tab and clear the checkmark next
to the option, Restore files to their original location.
4. Select the destination server and then select the Sybase
Server instance on the destination server.
5. Submit the restore job.
- For Sybase ASE 15, after you have installed the database
server, please check the system table sysservers
information and ensure the "srvnetname" for "SYB_BACKUP" is
not "SYB_BACKUP" or your backup and restore jobs will fail.
If the "srvnetname" for "SYB_BACKUP" is "SYB_BACKUP",
perform the following steps:
1. Open a command line prompt and start isql.
2. Enter the following:
1> sp_configure "allow updates to system tables",1
2> go
1> update sysservers set srvnetname='ServerName_BS' where srvname='SYB_BACKUP'
2> go
1> sp_configure "allow updates to system tables",0
2> go
8.14 Known Issues for the Agent for Virtual Machines
The following issues relating to the Agent for Virtual
Machines are known to exist in this release:
- When you use the VMware Converter tool to recover backup
sessions that were backed up using VMware Virtual
Consolidated Backup (VCB), the recovery operation fails and
the following message appears in the Activity Log:
Failed to recover the virtual machine.
To remedy this problem, use the VMware Virtual Disk
Development Kit (VDDK) tools to recover the backup sessions.
- On Windows Server 2008 systems with the Hyper-V role
enabled, performing a full backup of Hyper-V VSS writer may
sometimes cause the operating system to generate warning
messages about the removal of the storage miniport driver,
such as:
Device 'Storage miniport driver' VMBUS\{d6b9a233-a170-4602-9863-78f7c287c7df}\1&3189fc23&0&{d6b9a233-a170-4602-9863-78f7c287c7df}) has been lost from the system because the preparation for removal was not performed first.
Device 'Msft Virtual Disk SCSI Disk Device'(SCSI\Disk&Ven_Msft&Prod_Virtual_Disk\2&7aef4bc&0&000000) been lost from the system because the preparation for removal was not performed first.
This is a known problem with the Microsoft Hyper-V VSS
writer that does not affect the success of backup jobs. You
can still successfully perform data restore jobs. When all
virtual machines under Microsoft Hyper-V VSS Writer are
displayed as Backup Using Saved State-virtual machine name,
this problem does not occur.
- On Windows Server 2008 systems with the Hyper-V role
enabled, the VM backup job may fail in certain
environments, and records the following errors in the
Activity Log:
E12586 This VSS Writer (\\TX200S3x64\Microsoft Hyper-V VSS Writer) has reported a failure during the freeze event.
E12606 Selected Writer option cannot be obtained.
E12586 This VSS Writer (\\TX200S3x64\Microsoft Hyper-V VSS Writer) has reported a failure during the freeze event.
With this error, the Hyper-V VSS writer crashes. This is
also a known problem with the Microsoft Hyper-V VSS writer.
- The Recover VM job for VMware VMs fails if the backup proxy
system has "VMware converter enterprise for Virtual Center"
installed.
- The Agent for Virtual Machines does not support recovering
Arcserve Backup r12 and Arcserve Backup r12.1 backup
sessions using the Overwrite global option.
- Backup jobs associated with Windows Server 2008 R2 and
Windows 7 VMs running on VMware ESX Server 4.0 systems may
fail when VMware attempts to create snapshots of the VM.
For more information, see the following Knowledge Base
document on the VMware website: http://kb.vmware.com/kb/1009073
- File mode backups of Windows Server 2008 R2 and Windows 7
VMs may fail when using VMware Consolidated Backup (VCB) to
execute VM backup operations.
To remedy this problem, use one of the following
approaches:
Rotation backups and GFS backups--Submit your rotation and
GFS backups as Mixed mode backups with the Allow file level
restore option and the Use Client Agent for Windows option
(global backup option) specified. This approach helps
ensure that Arcserve Backup processes all subsequent
incremental and differential backups using the Client Agent
for Windows, which is running in the VM, rather than using
VCB to process the backups.
Raw backups--Submit your Raw (full VM) backups using the
Raw backup mode with the Allow file level restore option
specified. With this approach, Arcserve Backup creates a
backup session for the Raw (full VM) backup and sessions
for the individual volumes contained in the VM. You can
then view the raw session and the sessions for the volumes
contained in the VM in the Restore Manager window.
- The agent does not support performing file mode backups
using VDDK on GUID Partition Table (GPT) disks.
- When you select VM on ESX server 4.1 to run a backup job in
File mode using VDDK 1.1.1 on guest operating systems of
Windows 2008 or later, the backup job fails. To prevent
this from happening, use VDDK 1.2.
- When you restore from an internal session of a nameless
volume to an original location, it fails with an invalid
drive specification (error code AE0060).
- After successful recovery of the VMware VM, Disk
Provisioning Type of the Virtual Hard Disk depends on the
backup approach you use.
- If you back up a thin disk using VCB, you can recover it as
a thick disk if a converter approach or VDDK approach is
used.
- If you back up a thin disk using VDDK, and that backup is
not an active block backup, you can recover that disk as a
thick disk.
- If you back up a thin disk using VDDK, and that backup is
an active block backup, then you can only recover that disk
as a thin disk.
- Using VDDK approach, the agent for virtual machines do not
support backup of a virtual machine which itself is a
backup proxy server. To back up this virtual machine, you
must use a different backup proxy server.
- Restore operations fail when you recover virtual machines
on vNetwork Distributed Switch (vDS) environments using
VDDK. To correct this problem, do the following:
- Disable the VDDK Power on after recovery option.
- Recover the virtual machines using VDDK.
- From the vSphere Client, add the NIC to the configuration
for the virtual machine. The name of the NIC should be the
same as the original name of the NIC.
- Power on the virtual machine.
- (Optional) Configure the network.
Be aware of the following:
- As a best practice, you should keep a manual record of the
configuration of all NICs associated with vNetwork
Distributed Switch (vDS) environments. Arcserve Backup does
not retain this information.
- If you specify the default behavior of Arcserve Backup to
power on the virtual machines after the recovery is
complete, the corrective actions described above may
prevent you from configuring the network properly.
- This release of the agent does not support recovering
virtual machines to multiple data stores using VDDK. This
behavior lets the agent recover the VMDK files for a
virtual machine to only one database on an ESX Server
system. The solution to this behavior is to use Recover VM
to recover the data stores to a specified data store using
VDDK. After the Recover VM operation is complete, move the
virtual machines to their original data store. Note that
before you perform the move operation, verify that there is
a sufficient amount of free disk space on the original data
store to support the move operation.
8.15 Known Issues for the Enterprise Option for AS400
The following issues relating to the Enterprise Option for
AS400 are known to exist in this release:
- The Agent uses your session password only for encryption.
If you do not enable encryption at the agent side when
performing a backup, the session password is not validated
when you restore the agent session.
8.16 Known Issues for the Enterprise Option for IBM 3494
When using the Enterprise Option for IBM 3494 with the
Storage Area Network (SAN) Option, the Tape Engine on the
distributed machines may fail. To prevent this failure,
ensure that the most current IBM tape driver is installed
on the primary and distributed machines. To do so, perform
the following procedure on each machine:
- Find the type of IBM drive installed:
- Ultrium and Magstar (Windows 2003): ibmrmsst or ibmtp2k3
- Find the registry key for this drive in the directory:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\type of IBM drive.
For example, for an Ultrium drive, find the registry key
for the drive in the following directory:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmlto
- Create the DWORD value DisableReserveUponOpen and set it to
1.
- Exit regedit and restart your computer.
Note: For information on installing SAN distributed
servers, see the Storage Area Network (SAN) Option Guide.
8.17 Known Issues for the Enterprise Option for SAP R/3 for Oracle (Windows)
The following issues relating to the Enterprise Option for
SAP R/3 for Oracle (Windows) are known to exist in this
release:
- Multistream function is supported locally only for BACKINT
backup/restore.
- Before you shut down the Oracle Server in normal mode, you
should shut down the local Arcserve Backup Manager and the
Arcserve Backup Client Agent for Windows RPC Service.
- When performing a remote backup from the Client Agent for
Windows tree, use the Server NetBIOS name (machine name)
for the agent node name. The Client Agent for Windows
prompts you to specify the Use Computer Name Resolution
option or the IP address to include the databases when
backing up the entire machine.
- The IP address and hostname of the Agent and base machines
should be added to the hosts file on each system before
running any backup and restore jobs.
- BACKINT supports only one instance at a time. If you define
multiple instances, BACKINT saves only the first instance
to the BACKINT registry. The Enterprise Option for SAP R/3
for Oracle Configuration utility modifies the information
for this instance. For BACKINT to support other instances,
change the SID value in the BACKINT registry, and rename
the initSID.utl in %ORACLE_HOME%\database to your SID.
- For remote backups, you must enable File and Printer
Sharing for Microsoft Networks on the agent machine you are
backing up.
- The NetLogon service must be started to support
pass-through authentication of account logon events for
computers in a domain.
- For command line, only the BACKINT command interface is
supported.
- When submitting BACKINT command line backup and restore
jobs, Server Side Encryption and Secure Migration are not
supported.
- When submitting BACKINT command line backup and restore
jobs, hold jobs are not supported.
- If you are running the Enterprise Option for SAP on a
remote system and submitted backup jobs to a backup server
having more than one NIC installed, the jobs fail due to
connection problems. To avoid this situation, add a machine
IP mapping in the client hosts file for the server:
- On the remote system running the SAP option, go to the
Windows\System32\drivers\etc folder.
- Open the hosts file.
- Add host/IP map as below:
<IP address> machine_name
where <IP address> is the IP of the backup server machine
- Save and close the hosts file.
- When performing a database restore job that fails, the job
continues after the error only if you are restoring by
session. If you are restoring by tree, subsequent sessions
will not be restored. This is because Restore by Tree
packages all sessions into a single node, while Restore by
Session packages all sessions into different nodes.
- The option does not support the following:
- Submitting restore jobs using the Restore by Query restore
method.
- Using multistreaming when backing up SAP data to data
deduplication devices.
With multistreaming, Arcserve Backup backs up SAP data to
multiple devices that reside in different device groups
simultaneously. This behavior causes Arcserve Backup to
ignore the value of DESTGROUP specified in the
util_par_file configuration file. As a result, Arcserve
Backup backs up SAP data to device groups that do not
contain deduplication devices.
- Using the Optimize Restore functionality.
- Using Compare Media to Disk functionality.
8.18 Known Issues for the Enterprise Option for SAP R/3 for Oracle (UNIX and Linux)
The following issues relating to the Enterprise Option for
SAP R/3 for Oracle (UNIX and Linux) are known to exist in
this release:
8.19 Known Issues for the Enterprise Option for StorageTek ACSLS
The following issues relating to the Enterprise Option for
StorageTek ACSLS are known to exist in this release:
8.20 Known Issues for the Disaster Recovery Option
The following issues relating to the Disaster Recovery
Option are known to exist in this release:
- Disaster Recovery restore jobs running on IA64 systems may
display this error even though the tape library is
connected and media is present: "Media not found. Insert
media." The problem appears limited to IA64 systems running
Windows 2003 with the Emulex LP10000 FC card.
- One Button Disaster Recovery (OBDR) scans the first OBDR
device found by the Tape Engine. Ensure the OBDR tape is in
the first tape drive to restore successfully.
- After Disaster Recovery is completed, the size of the last
partition recovered can be expanded from the original size
by as much as 8 MB. The problem occurs if there is free
space at the end of the last partition on the disk being
recovered.
- For Microsoft SQL-hosted Arcserve Backup databases, the
operating system will record numerous application errors of
MSSQL$ARCSERVE_DB to the Event Log during recovery of the
database, such as:
Since these events are recorded by the recovery of the
database, they pose no problem.
- When 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.
- 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 Arcserve Backup database. Upon
the first reboot after performing Disaster Recovery of the
Arcserve Backup server hosting the Arcserve database, you
must restart the database engine. Do so through the
Arcserve Backup Manager Console.
- When performing Disaster Recovery on Microsoft Windows XP,
Windows 2003 or Windows 2008 systems, the Create Folder
button may not work when attempting to save logs. To save
logs, create a new folder using the mkdir command with the
Open Console button or save logs into an existing folder.
- Before you perform Disaster Recovery on a Windows 2003
machine, use the Disaster Recovery Boot Kit Wizard to
create a CD that contains the following:
- OS
- Machine-Specific Disk
- Drivers for NIC cards
- Arcserve Backup
Note: Use this re-mastered CD to perform Disaster Recovery
on these machines to avoid Unsigned Driver errors with some
NIC cards that could make USB input devices (such as
keyboard or mouse) unusable during system recovery.
- If your system is configured with a number of volumes
mounted via mount points, Disaster Recovery cannot be
performed correctly. You must format and restore data
manually.
- If an iSCSI LUN is being used as a shared disk by a
failover cluster, that LUN cannot be restored while
performing Disaster Recovery of the cluster.
- Consider the following situation:
Arcserve Backup is installed on Server A. On Server B, two
shared folders exist and are configured on Server A as
remote File System or Data Deduplication devices using
different Windows accounts. When using the Disaster
Recovery option to restore backup data from these devices,
Arcserve Backup will be able to connect to only one.
Connection to the second device fails with Windows error
1219 because multiple connections to shared resources by
the same user, using more than one user name, are not
allowed.
- Creating MSD on floppy disk using Windows Server 2008 IA64
systems may fail if you integrate NIC drivers at the same
time because the floppy drive capacity is exceeded. To
avoid this issue, use USB memory sticks (supported on
Windows Server 2008).
- When performing remote disaster recovery from MSD/FD that
includes certified NIC drivers on Windows XP and Windows
2003 (32-bit and 64-bit platforms), an error may appear
that the driver is not certified, making it impossible to
use the keyboard and mouse. This is a known Microsoft
issue. Using the integrated bootable CD for disaster
recovery can overcome this limitation. Alternatively, you
may manually modify your MSD. To do so, follow the solution
described in the Microsoft Knowledge Base article,
KB-887494, using the following information:
- Manually modify the asr.sif file on MSD:
- Open the asr.sif file using a text editor.
- Locate the section [INSTALLFILES]:
4=1,"CADRIF","\Device\Floppy0\","oem3.inf","%SystemRoot%\inf\driver.inf","CA"
5=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%SystemRoot%\Driver
Cache\driver.sys","CA"
6=1,"CADRIF","\Device\Floppy0\","vmware-nic.cat","%SystemRoot%\Driver
Cache\driver.cat","CA"
7=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%SystemRoot%\Driver
Cache\driver.dll","CA"
change these files to %TEMP%:
4=1,"CADRIF","\Device\Floppy0\","oem3.inf","%temp%\driver.inf","CA"
5=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%temp%\driver.sys","CA"
6=1,"CADRIF","\Device\Floppy0\","vmware-nic.cat","%temp%\driver.cat","CA"
7=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%temp%\driver.dll","CA"
Do NOT change these files or you will be unable to perform
DR:
1=1,"CADRIF","\Device\Floppy0\","DrLaunch.exe","%SystemRoot%\system32\DrLaunch.exe","CA"
2=1,"CADRIF","\Device\Floppy0\","DrLaunchRes.dll","%SystemRoot%\system32\DrLaunchRes.dll","CA"
3=1,"CADRIF","\Device\Floppy0\","DrLaunchEnu.dll","%SystemRoot%\system32\DrLaunchEnu.dll","CA"
- Manually create a file called winnt.sif on MSD and open it
in a text editor, for example, Notepad.
- Write the following text into the winnt.sif file:
[Data]
MsDosInitiated = 0
UnattendedInstall = Yes
[Unattended]
OemPreinstall = YES
OemPnPDriversPath = TEMP
- When recovering a Windows Server 2008 R2 server from a
disaster using Disaster Recovery Option, the cmd.exe - No
Disk message box appears and displays the message, "There
is no disk in the drive. Please insert a disk into Drive
A:." The message box appears in the following scenarios:
- You created machine-specific disks using a USB-connected
device after the backup completed, and the server contains
a floppy drive.
- You created machine-specific disks using a USB-connected
device or a floppy disk drive on a server that contains an
RD1000 drive.
To remedy this problem, click Continue on the cmd.exe and
wpeinit.exe - No Disk message box. Then, press Alt + Tab
or Alt + Esc to display the Disaster Recovery Option
dialogs.
- When recovering backup servers running Windows Server 2008
R2 IA64, Arcserve Backup may not be able to detect file
system devices connected to remote computers running
Windows Server 2003 or Windows XP. This problem also occurs
on various x64-based computers running Windows Server 2008
R2 (for example, Dell GX755 desktop).
To remedy this problem, do the following:
- IA64 platforms--Use the Windows Server 2008 IA64 CD image
instead of the Windows Server 2008 R2 IA64 CD image to
start the disaster recovery process.
- x64 platforms--Use the Windows Server 2008 x64 CD image
instead of the Windows Server 2008 R2 CD image to start the
disaster recovery process.
- When performing disaster recovery from SAN disks, all disks
except for the boot disk are offline and read-only, and
therefore fail to be recovered. To avoid this situation,
perform the following:
- Before you load your MSD during the DR process, go to
Utilities, Run and type diskpart. Press Enter. This
launches the diskpart utility.
- Type list disk to detect all disks attached.
- For each disk, use the following command to see if it is
offline or read-only:
select disk 1
detail disk
- If a disk is offline, use the "online disk" command to
bring it online.
- If a disk is read-only, use the "attributes disk clear
readonly" command to remove the read-only flag.
- You cannot log in to Arcserve Backup with a blue screen
(error code: 000000FC) when performing disaster recovery
from a Physical Machine (DELL 270) to a Virtual Hyper-V
environment. To resolve this issue, log in to Arcserve
Backup by performing the following steps:
- Press F8 when the startup menu appears, use the arrow keys
to select the safe mode option, and then press ENTER.
- Click Start, Run, and type 'cmd', and then click OK.
- At command prompt, type the following and then press ENTER:
bootcfg/raw "/noexecute=alwaysoff /fastdetect" /id 1
- Disaster Recovery uses Windows ASR API to recover disk
partition layouts. But the behavior for recovering dynamic
disk is different from creating dynamic disk from disk
manager, therefore the disk data offset will proceed in a
different way. For this reason, only a few MB of
unallocated disk space is left after Disaster Recovery.
Note: This is the behavior of Windows ASR. Since there is
no data loss, you can ignore it, although you will find
that the usable disk space will be different before/after
Disaster Recovery.
- When performing disaster recovery on a cluster environment
that has Arcserve Backup installed on an iSCSI connected
shared disk, the Arcserve Backup database recovery utility
fails to launch automatically after the disaster recovery
completes and the machine reboots. The reason for this is
because of the iSCSI Initiator which needs time to
re-establish the connection.
As a workaround, you can manually run the Arcserve Backup
database recovery utility after logging into Windows and
connecting to the cluster shared disk.
- You cannot open the online help for the iSCSI Initiator
Properties screen on a WinPE Disaster Recovery environment.
- During the Disaster Recovery process, if the cluster shared
disk is not ready when the client agent begins, the cluster
volumes on the shared disk will become inaccessible, the
disk quota cannot be restored, and the diskquota.inf file
cannot be deleted.
As a workaround, once all shared disks become available,
you can perform the following operations to restore the
disk quota:
- Add a DWORD key: IsResDskQuota to the following registry:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServeBackup\ClientAgent\Parameters
- Set parameter to 1
- Restart the Universal Agent Service
- Windows Server 2008 R2 fails to reboot after running WinPE
Disaster Recovery on uEFI systems with MBR (Master Boot
Record) disks attached and logical volume that exists on an
extended partition. This is a Windows limitation.
- It is a known issue for a staging backup job to be marked
as "Crashed" in the Job Queue after the Disaster Recovery
process completes from the staging device.
- When you perform a remote backup from one primary server
(A) to another primary server (B) with Arcserve Backup
Database (ASDB) locally installed and then perform disaster
recovery, the ASDB will not restore automatically.
As a workaround, you need to manually perform the following
in order to restore the server containing ASDB:
- From server A, submit a restore job to recover the SQL
Disaster Recovery Element Session.
This ensures that the SQL Service operates successfully on
server B.
- From server B, manually start the SQL Service.
- From server A, submit a restore job to recover the ASDB
session from server B.
- With Global Dashboard configured and Disaster Recovery is
run, the Global Dashboard becomes unavailable. The reason
being is that the Global Dashboard maintains its own
database called "asdb_central" where Disaster Recovery does
not recover.
To recover the Global Dashboard, you need to restore the
"asdb_central" database from the Arcserve Backup Restore
Manager after Disaster Recovery completes.
- When creating a Disaster Recovery MSD (Machine Specific
Disk) with multiple devices attached, such as an RDX device
and a USB stick, to the Arcserve Backup server, the RDX
device may be selected as the default destination. To
ensure that the default destination is the destination you
want, you must manually verify it. If it is not the
destination expected, you can manually change it to the
desired destination.
- WinPE Disaster recovery does not support ISCSI binary files
on a Windows Server 2003 environment. As a workaround, you
would have to manually copy the ISCSI binaries from a
Windows Server 2008 system to a Windows Server 2003 WinPE
environment. For example, for Windows Server 2003 x64
machines, you would need to copy the ISCSI binaries from a
Windows Server 2008 x64 machine and for Windows Server 2003
x86 machine, you would need to copy the ISCSI binaries from
a Windows Server 2008 x86 machine.
The following ISCSI binary files you would have to manually
copy and replace are:
- Files
("iscsicli.exe","iscsicpl.exe","iscsicpl.dll","iscsidsc.dll","iscsied.dll","iscsiexe.dll","iscsium.dll","iscsiwmi.dll")
from the C:\windows\system32\ folder of the Windows Server
2008 machine to the x:\windows\system32\ folder of the
Windows Server 2003 machine under Disaster Recovery, in a
WinPE environment.
- Files
("iscsicli.exe.mui","iscsicpl.dll.mui","iscsicpl.exe.mui","iscsidsc.dll.mui","iscsiexe.dll.mui")
from the C:\windows\system32\en-us folder of the Windows
Server 2008 machine to the x:\windows\system32\en-us folder
of the Windows Server 2003 machine under Disaster Recovery,
in a WinPE environment.
- With Disaster Recovery, the "Express Mode" does not let you
assign specific IP addresses to physical Network Interface
Cards (NIC) but selecting the "Advanced Mode" will. This is
beneficial when you are recovering a teaming environment
and disaster recovery cannot access the network.
With WinPE Disaster Recovery, the "Network Configuration"
utility lets you assign specific IP addresses to physical
NIC cards.
Note: You can only restore the original machine on a
teaming environment. You cannot make any changes to the
physical NIC cards, otherwise you will have to reconfigure
the teaming environment after disaster recovery.
- If you perform Disaster Recovery on an environment with
StorageTek ACSLS configured and upgrade Arcserve Backup
from r15 to r16, disaster recovery will fail.
The reason why disaster recovery fails is because the file
"ACSLSRDC.dll" is not the latest version.
As a workaround, you can perform one of the two options:
- Replace the old file with the latest version located in the
Arcserve home directory.
OR
- Regenerate the disaster recovery information by running a
full or incremental backup again and then perform the
disaster recovery with the new information.
Note: The old file is located in the following directory:
"DR\[Backup Server]\[Agent Machine]\Acsls\" or if your MSD
(Machine Specific Disk) has already been created, you can
locate the old file on your MSD and replace it with the
latest version.
8.21 Known Issues for Dashboard
The following issues related to Dashboard are known to
exist in this release:
- The Agent Distribution Report does not display OpenVMS and
AS400 agent information.
- Dashboard reports do not display network backup or
preferred shares backup nodes.
- Nodes running the Arcserve Backup Agent for Microsoft
Exchange Server 2007 are not displayed in the SRM reports,
unless you change the Arcserve Backup Universal Agent login
account from Local System to Domain account with
administrator privileges, as follows:
- Click Start, Control Panel, Administrative Tools, Services
to open the service control manager.
- Right-click the Arcserve Backup Universal Agent and choose
Properties from the shortcut menu.
- On the Log On tab, click This Account and enter the domain
name/user name, followed by your password. Confirm the
password and click OK.
- Click OK to clear the confirmation message.
- Right-click the Arcserve Backup Universal Agent and choose
Restart from the shortcut menu.
- For Arcserve Backup running in a cluster environment, the
SRM reports for virtual nodes displays the same information
as that of the currently active node.
- Recovery points for the following cases are listed on the
Node Recovery Points Report rather than on the Virtual
Machine Recovery Points Report:
- Microsoft Hyper-V virtual machines backed up in file mode
- VMware Consolidated Backup (VCB) jobs in file mode
performed with the Arcserve Backup Client Agent for Windows
(mixed mode VM GFS/rotation jobs)
8.22 Known Issues for the Arcserve Backup Global Dashboard
The following issues are known to exist in this release:
8.23 Known Issues for the Image Option
The following section provides information regarding issues
known to exist in this release of Arcserve Backup for the
Image Option:
8.24 Known Issues for the NDMP NAS Option
The following issues relating to the NDMP NAS Option are
known to exist in this release:
- The EMC Celerra NDMP daemon has a maximum of eight (DART
5.4) concurrent connections. The NDMP NAS Option uses
concurrent and persistent device connections. Each tape
drive and TLU managed by the EMC data mover counts as a
separate connection. Each backup, restore, or browse
function also counts as a separate connection. If you
exceed eight connections, you may encounter problems. We
recommend that you keep this in mind when planning and
implementing your storage topography.
- If you have multiple NIC cards on the backup server, you
cannot connect to the option. To connect to the option, you
must add the loop back address for the backup server to the
hosts file (the entry should be similar to the following):
127.0.0.1 HOSTNAME
- Network Appliance Filers with OnTap 6.2.x and 6.3.x require
a Network Appliance patch to fix a known Direct Access
Restore (DAR) issue with spanned DAR recovery operations.
- Sessions backed up with <BEB> 10.0 Service Pack 3 or
earlier must have the following registry key set to 1
before starting a restore operation:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\ARCserve Backup\NASAgent
- The option does not support installation on the Member
server.
- The option does not support Job failover.
- The option does not support encryption. If server side
encryption is enabled for NAS backup, the following message
is displayed when the job is submitted:
Warning: Encryption will be skipped for NAS backups. Click OK to continue.
- You can use Direct Access Restore for files only. If you
restore at least one folder, the restore operation reverts
to scanning the session. This limitation does not apply to
Network Appliance.
- Procom does not support multiple backup filters.
- When configuring the agent and the NAS device, you must use
either an IP address or host name for both. Using a mixed
configuration can result in a 3-way backup.
- Dynamic Device sharing (DDS) configuration in a SAN
environment with NAS is not supported on a cross-platform
Windows SAN environment.
- To use DDS on EMC Celerra, you must set the
NDMP.scsiReserve parameter to 0 on the data mover. This
parameter is available starting with release 5.2.15.0. For
more information about this issue, see EMC's Celerra
documentation.
- To allow 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.
- Filters are not supported on restores.
The following items relating to the NAS Restore backup
sessions are not supported in this release:
8.25 Known Issues for the Storage Area Network (SAN) Option
The following issues relating to the SAN Option are known
to exist in this release:
- Mixed SAN environments are no longer supported. This is to
say that in ONE Arcserve Backup Domain, there can only be
ONE Primary server. So if there are to be multiple SAN's
in your environment, they either need to be in separate
Arcserve Backup domains or they have to share the same
Primary server, with devices from both SAN's zoned to the
same Primary server.
8.26 Known Issues for the Tape Library Option
The following issues relating to the Tape Library Option
are known to exist in this release:
8.27 Known Issues for Central Agent Admin
The following issues regarding Arcserve Backup Central
Agent Admin are known to exist in this release:
- When viewing event logs using the Central Agent Admin on
Windows Server 2008 and Windows Server 2008 R2 systems, you
may receive a "Can't parse this event log" error. This is a
known Microsoft problem.
8.28 Known Issues for Displaying Non-English Characters
The following issues are known to exist in this release:
- You must set Regional and Language Options identically on
primary and member server machines to avoid garbled text or
characters replaced by question marks (?).
- In the Submit Job dialog, Destination Node is displayed
with 'garbage' characters when you submit a job to a
Unicode surrogate pair destination. Multilingual characters
that cannot be represented by a one double-byte code can
usually be represented in Unicode using its surrogate pair
feature. The Submit Job dialog cannot display surrogate
pairs. This is a display issue and does not impact the job
itself.
- When setting the caroot password using the Arcserve Backup
Configuration Wizard, do not use Unicode characters.
Unicode characters are interpreted as "?" and because the
question mark is an acceptable character in the caroot
password, log in succeeds with any Unicode character
entered. Once set, you will not be able to change it using
the Arcserve Backup Manager Console.
- Do not use Unicode characters in the groupname in the Agent
for Open Files configuration file (ofant.cfg).
- The Agent for Virtual Machines does not support the use of
non-English characters in VM names.
- If you used JIS2004 characters in a file or directory name
that was backed up prior to installing this version of
Arcserve Backup, Restore Manager will not be able to
display or restore the file or directory name correctly.
However, the file or directory contents can be correctly
restored.
- Scan Engine does not support Unicode. Therefore, you cannot
use the Enable Virus Scanning option when backing up or
restoring files and folders that contain Unicode characters
in their names.
- As of the r12 SP1 version of Arcserve Backup, Unicode is
supported. Diagnostic reports created in this version of
Arcserve Backup can be opened only with versions of
Arcserve Backup at r12 SP1 and later.
- Backup jobs submitted using Arcserve Backup r12.5 Agents
(includes all service packs) that contain Unicode
characters in their directory names and file names will
fail after you upgrade to this release. To avoid this
problem, specify the parent directory of the directories,
files, or both that contain Unicode characters and then
resubmit the job.
- Microsoft Windows does not support Unicode characters in
the command line interface, therefore, you cannot use the
Windows command line to enter Arcserve Backup commands
containing Unicode characters. Use the Windows Powershell
instead of cmd.exe, or use the -f switch to save text files
as Unicode files.
- The DBAconfig.exe module does not support Unicode.
8.29 Known Issues for Documentation
The following section provides information about issues
relating to the documentation for Arcserve Backup that are
known to exist in this release.
Note: You can access the most up-to-date product
documentation (PDFs) from the Arcserve Backup website of
Arcserve.
Alert Manager Help
Job Scheduler Wizard
- If you enter a command in the ‘Run this program’ field and
click the Help button, an error message appears. To resolve
this issue, leave this field blank and click Help. A list
of all commands displays. Navigate to and select the
appropriate command to open the help topic for that command.
8.30 Known Issues for the Arcserve Backup Infrastructure Visualization
The following issues related to Infrastructure
Visualization are known to exist in this release:
- The Agents view does not display OpenVMS and AS400 agent
information.
- Visualization views do not display network backup or
preferred shares backup nodes.
- When a virtual machine is backed up through Microsoft
Hyper-V for the first time and backup failed due to network
error or incorrect credentials then the backup status of
the VM node may not be displayed in Virtual Machines view.
- If VMware or Hyper-V VMs are backed up in file mode using
client agent for Windows, the last backup status of the VM
would be shown in Subnet view and this backup status would
be omitted from display in Virtual Machines view.
- If you performed a backup of a node using the command line
(ca_backup), Arcserve Backup Infrastructure Visualization
may not display any data in the Subnet and Agent views.
- To view the node in visualization, add the node to the
Backup Manager GUI and provide the credentials.
- If you try to access Arcserve Backup Infrastructure
Visualization in Global mode, from a remote Manager
console, the following message appears:
"Cannot switch to global mode. Cannot load Dashboard Agent for Global Dashboard. Please contact your system administrator."
This indicates that you have not installed the Global
Dashboard component on to your machine that is running the
remote Manager console. To remedy this problem, install
the Global Dashboard component on to the remote Manager
console machine and then launch Arcserve Backup
Infrastructure Visualization in Global mode.
Additionally, when you click OK in the above message,
Infrastructure Visualization would open in Local mode where
you can observe the Visualization views for the Central
primary server alone.
- When you register for virtual clusters as a member server
using the Server Configuration wizard in a Microsoft
Cluster Server (MSCS) environment, the member server
devices do not display because the tape engine does not
register devices for virtual clusters.
8.31 Known Issues for the Microsoft Hyper-V VSS Writer
The following issues relating to the Microsoft Hyper-V VSS
Writer is known to exist in this release:
- When you configure storage spaces on Hyper-V virtual
machines, VSS writer backups of the virtual machines can
fail with a snapshot creation failure.
- Microsoft Hyper-V VSS Writer may display application error
code 12289 during a backup of a VM using a transportable
snapshot even though the backup job succeeded. This is a
known Microsoft issue.
- Microsoft Hyper-V VSS Writer may display system error code
5121 during a backup of a VM using a transportable snapshot
even though the backup job succeeded. This is a known
Microsoft issue.
9.0 Included Fixes
The following topics display lists of included fixes for
each Arcserve Backup release. If you do not see a specific
fix listed in the respective section, contact Arcserve
Technical Support for more information.
10.0 Arcserve Backup r16 SP1
The following sections provide information for the Arcserve
Backup r16 Service Pack 1 release.
10.1 Supported Operating Systems
This section provides the added supported operating systems
for Arcserve Backup r16 SP1:
Arcserve Backup UNIX and Linux Data Mover:
Client Agent (UNIX and Linux):
Agent for Oracle (UNIX and Linux):
Agent for Lotus Domino:
- Windows Server 2008 R2, R2 SP1 with Lotus Domino 8.5.3
(without db2 enabled and with DAOS enabled)
Enterprise Option for SAP R/3 for Oracle 11gR1/R2 (UNIX and
Linux):
This section provides the added supported operating systems
for Agents for Virtual Machines:
VMware ESX/ESXi Server Version |
VMware VCB Framework Version |
VDDK Version |
VMware vCenter Server Version |
vSphere 5.0 (ESXi) |
N/A |
5.0 |
VMware vCenter Server 5.0 |
This section provides the added virtualization platforms
that Arcserve Backup supports:
10.2 Installation Considerations
The following installation considerations are included in
the Arcserve Backup r16 SP1 release:
This section provides information about general
considerations while installing Patch Manager.
- When installing Arcserve Backup r16 SP1, whether it is a
new installation or an upgrade from a previous version,
Arcserve Backup will NOT automatically install Patch
Manager r16 SP1. You are required to install it from the
r16 SP1 installation media to update the components.
- Upgrade to Patch Manager r16 SP1 if you have an earlier
version to obtain the patches. For more details, refer to
the Arcserve Backup Patch Manager Readme.
- While upgrading the client and if the client is connected
to the Staging server, verify that the Staging server is
also upgraded.
10.3 Known Issues
The following sections provide information about issues for
Arcserve Backup r16 SP1:
Issues relating to Arcserve Backup Agent for Virtual
Machines:
- Arcserve Backup Agent for Virtual Machines does not support
backing up data using VCB Framework for VMs that runs on
vSphere 5.0.
Issues relating to the Arcserve Backup Base Product:
- Backward Compatibility is not supported for proxy servers
and agents running on virtual machines with different
versions of Arcserve Backup.
Issues relating to the Disaster Recovery Option:
- When performing disaster recovery for Windows Server 2003
in HyperV with Machine-Specific Disk (MSD), the following
warning message appears:
The driver software you are installing for Virtual Machine Bus has not been properly signed with Authenticode(TM) technology. Therefore, Windows cannot tell if the software has been modified since it was published. The publisher's identity cannot be verified because of a problem: The installed INF file does not contain digital signature information.
Do you still want to install this driver software?
To resolve this problem, do the following:
Click Yes and select the path where the MSD is located to
install the driver.
10.4 Arcserve Backup r16 Service Pack 1
The following fixes were included in Arcserve Backup r16
Service Pack.1. If you do not see a specific fix listed in
this section, contact Arcserve Technical Support for more
information.
RO24705 |
T16C945 |
T245693 |
T2D2840 |
T36A687 |
T5DY074 |
T5KC047 |
T5KZ062 |
T5OV079 |
T5SO004 |
RO28635 |
T16C946 |
T245694 |
T2D2844 |
T36A691 |
T5DY077 |
T5KC050 |
T5KZ064 |
T5OV082 |
T5SO005 |
RO28850 |
T16C947 |
T245695 |
T31A566 |
T36A692 |
T5DY080 |
T5KC051 |
T5KZ065 |
T5OV083 |
T5SO006 |
RO31295 |
T16C949 |
T245696 |
T31A568 |
T36A694 |
T5DY084 |
T5KC052 |
T5KZ066 |
T5OV084 |
T5SO009 |
RO31571 |
T16C951 |
T245699 |
T31A570 |
T36A696 |
T5DY086 |
T5KC053 |
T5KZ067 |
T5PY038 |
T5SO010 |
RO31785 |
T16C952 |
T245701 |
T31A571 |
T36A700 |
T5DY087 |
T5KC054 |
T5KZ068 |
T5PY055 |
T5SO012 |
RO33528 |
T16C953 |
T245702 |
T31A572 |
T36A703 |
T5DY088 |
T5KC055 |
T5KZ069 |
T5QO022 |
T5SO013 |
RO35207 |
T16C955 |
T245703 |
T31A574 |
T36A706 |
T5DY089 |
T5KC057 |
T5KZ072 |
T5QO023 |
T5SO014 |
RO35223 |
T16C956 |
T245704 |
T31A576 |
T36A707 |
T5DY093 |
T5KC058 |
T5KZ074 |
T5QO025 |
T5SO015 |
RO35289 |
T16C957 |
T245705 |
T31A577 |
T36A709 |
T5DY097 |
T5KC059 |
T5KZ075 |
T5QO026 |
T5SO016 |
T146539 |
T16C961 |
T245707 |
T31A579 |
T36A710 |
T5DY098 |
T5KF082 |
T5KZ076 |
T5QO029 |
T5SO017 |
T146543 |
T16C962 |
T245708 |
T31A580 |
T36A711 |
T5E5106 |
T5KF083 |
T5KZ077 |
T5QO041 |
|
T146544 |
T16C964 |
T245709 |
T31A581 |
T36A712 |
T5E5107 |
T5KF084 |
T5LD056 |
T5R3005 |
|
T146545 |
T16C968 |
T2D2812 |
T36A667 |
T36A713 |
T5E5108 |
T5KF085 |
T5LD059 |
T5R3006 |
|
T146547 |
T245671 |
T2D2813 |
T36A669 |
T36A714 |
T5E5111 |
T5KF086 |
T5LD061 |
T5R3009 |
|
T146551 |
T245673 |
T2D2814 |
T36A670 |
T439134 |
T5E5116 |
T5KF087 |
T5LD063 |
T5R3003 |
|
T146552 |
T245675 |
T2D2815 |
T36A671 |
T46B341 |
T5E5117 |
T5KF088 |
T5LD065 |
T5R3010 |
|
T16C898 |
T245676 |
T2D2817 |
T36A672 |
T46B342 |
T5E5119 |
T5KF091 |
T5OV059 |
T5R3011 |
|
T16C925 |
T245677 |
T2D2818 |
T2D2816 |
T46B343 |
T5E5123 |
T5KM073 |
T5OV061 |
T5R3013 |
|
T16C926 |
T245678 |
T2D2822 |
T36A664 |
T46B346 |
T5E5126 |
T5KM076 |
T5OV062 |
T5R3014 |
|
T16C928 |
T245679 |
T2D2823 |
T36A673 |
T46B347 |
T5E5128 |
T5KM077 |
T5OV063 |
T5R3015 |
|
T16C930 |
T245680 |
T2D2824 |
T36A675 |
T46B349 |
T5E5130 |
T5KM078 |
T5OV066 |
T5R3017 |
|
T16C931 |
T245682 |
T2D2826 |
T36A678 |
T46B351 |
T5HP059 |
T5KM079 |
T5OV068 |
T5R3021 |
|
T16C932 |
T245683 |
T2D2828 |
T36A679 |
T46B352 |
T5HP061 |
T5KM081 |
T5OV069 |
T5R3022 |
|
T16C934 |
T245684 |
T2D2829 |
T36A680 |
T46B353 |
T5JS061 |
T5KM082 |
T5OV070 |
T5R3024 |
|
T16C935 |
T245685 |
T2D2830 |
T36A681 |
T5DQ092 |
T5JS068 |
T5KM083 |
T5OV071 |
T5R3025 |
|
T16C936 |
T245687 |
T2D2831 |
T36A682 |
T5DQ095 |
T5JS069 |
T5KM085 |
T5OV072 |
T5R3026 |
|
T16C938 |
T245690 |
T2D2832 |
T36A683 |
T5DQ097 |
T5JS071 |
T5KM086 |
T5OV073 |
T5SO001 |
|
T16C939 |
T245691 |
T2D2834 |
T36A684 |
T5DQ094 |
T5JS073 |
T5KZ060 |
T5OV075 |
T5SO002 |
|
T16C940 |
T245692 |
T2D2836 |
T36A686 |
T5DQ098 |
T5JS074 |
T5KZ061 |
T5OV078 |
T5SO003 |
|
Note: Some test fixes require changes to the registry key.
To implement these changes for a specific test fix, see Additional Information for Included Fixes.
10.4.1 Additional Information for Included Fixes
The following table contains additional information about
specific test fixes for Arcserve Backup r16 SP1.
Fix Number |
Registry Key changes |
T16C898 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Tapeengine\Config
Value Name: (DWORD) EjectTape
Value: 1
Note: The value of 1 ejects the tape after inventory. |
T16C940 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Task\Merge
Value Name: (DWORD) RecoverCatalogSpan
Value: 1
Note: The value of 1 lets the catalog merge and span on a
standalone tape device. |
T2D2816 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Task\Common\SRMREPORTTIME
Value Name: (DWORD) Enable
Value: 0
Note: The value of 0 disables SRM Probing. |
T31A571 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\Arcserve
Backup\Base\Task\Common\PrePostAllow64
Value Name: N/A
Value: N/A |
T31A577 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\ASMgr
Value Name: (DWORD) MaxNASSessionSize
Value: The number of files displayed in the NAS session. |
T31A581 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\UniversalClientAgent
Value Name: (DWORD) RemoveRegEntry
Value: The path of the database where it is currently being
used and saved.
Note: If the 'RemoveRegEntry' exists, then the tool deletes
the restore path that is currently used after a successful
restore job. |
T36A681 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\SQLPAAdp\Instances\dbasql@<<ENTER_SQL_INSTANCE_NAME>>
Value Name: (DWORD) SkipBKSQLDRElements
Value: 0 or 1
Important! If the value is set to 1, the agent skips the
ASDB DR Element. This key is for specific use only and is
not recommended to set this value; otherwise you cannot
restore your Arcserve Backup database from Disaster
Recovery. |
T36A684 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Task\Backup
Value Name: (DWORD) BlockAllNotifyPopups
Value: 1
Note: The value of 1 displays a message. |
T36A710 |
Set this registry for the fix on the agent.
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
BackupSPS12Adp\Parameters
Value Name: (REG_SZ) AlterLogLocation
Value: The location where the new log writes to. |
T46B349 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Task\Backup
Value Name: (DWORD) AllowPreserveAccessTime
Value: 1
Note: The value of 1 lets UNIX or Linux Agent prevent the
"last access time" from being modified in a differential or
incremental rotation job. |
T46B353 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\ClientAgent\Parameters\DisableW0009
Value Name: (DWORD) DisableW0009
Value: 0 or 1
Note: If the value is set to 1, the AW0009 warning message
in the activity log is not displayed. |
T5E5106 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Tapeengine\Config
Value Name: (DWORD) UseRootDir
Value: 1
Note: The value set to 1 allow users to create devices
under specific root directories except the C drive. |
T5E5107 |
Set this registry for the fix on the server
For x86 OS = Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\Base\Tapeengine\Config
For x64 OS = Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\Arcserve
Backup\Base\Tapeengine\Config
Value Name: (DWORD) SkipDuplicateFM
Value: 1
Note: The value set to 1 skips the adjacent file marks.
When the required files have been restored then remove the
registry value. This fix is a rare case. |
T5JS068 |
Set this registry for the fix on the agent.
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\UniversalClientAgent\Options\2000\1067
Value Name: (REG_DWORD) DisabledPublicFolder
Value: 1
Note: The value set to 1 disables the public folder
database. |
T5KF083 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\Arcserve
Backup\UniversalClientAgent\Options\1060
Value Name: (DWORD) EnableCheckNullFolder
Value: 1
Note: The value of 1 lets the Exchange Doc Level Agent skip
blank public folder names during backup. |
T5KM081 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\ClientAgent\Parameters
Value Name: (DWORD) VssAsyncTimeOut
Value: The value of the timeout session of the VSS
operation.
Note: The value is in seconds. If the value does not exist
in the registry, then the default value is 20 x 60 = 1200
seconds. |
T5KZ065 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\ClientAgent\Parameters
Value Name: (DWORD) VimTimeout
Value: 60
Note: The value is set in minutes. Anything greater than 10
is advised. If the registry key is not specified, then the
default timeout value is 10 minutes. |
T5LD063 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\TapeEngine\Image
Value Name: (DWORD) SupportLargeDataSet
Value: 1
Note: The value of 1 slows down the backup performance |
T5LD065 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\Arcserve
Backup\Base\Task\Common\IgnoreNASError
Value Name: N/A
Value: N/A |
T5OV059 |
Set this registry for retaining the MAC address while recovering the VM
Key: HKEY_LOCAL_MACHINE\SOFTWARE\ ComputerAssociates\Arcserve Backup\ClientAgent\Parameters\
Value Name: (DWORD) RetainMACForVDDK
Value: 1 (to retain MAC address) |
T5PY055 |
Set this registry for the fix on the server
Key: HKEY_LOCAL_MACHINE\SOFTWARE\
ComputerAssociates\Arcserve Backup\SPS12Adp\Internal
Value Name: (DWORD) IsValid
Value: 1
Note: The value is set to 1 to allow the program to verify
other registry settings for this fix. If the value is set
to 0, the other registry settings for this fix are ignored.
Value Name: (REG_DWORD) SkipGetSQLServerServiceInfo
Value: 1
Note: The "Get SQLServer service" account name is omitted.
Value Name: (REG_SZ)
AdditionalAccountForBackupRestoreSharedFolder
Value: The account name
Note: The account name runs the SQLServer instance. |
T2D2832, T5R3003, T5R3010 |
Set this registry for the fix on the server
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve
Backup\ClientAgent\Parameters
Value Name: (DWORD) DisableRecursiveHugeSystemState
Value: 0
Note: By default, this registry key is not present.
However, if the system state backup increases to a large
amount, then create this registry with the value set to 1. |
10.5 Document Changes
This topic provides documentation changes for Arcserve
Backup r16 SP1.
Note: All document changes are noted in this service pack
and will be updated in its appropriate user guides in the
next release.
The following test fixes should have been included in
section 9.0 Included Fixes for r16:
- T4C4095
- T16C928
- T5OV068
- T5OV072
- T5OV073
Test fix T16C898 needs to be deleted from section 9.0
Included Fixes for r16 and add to r16 SP1 test fixes.
The following list describes topics in the Arcserve Backup
r16 Readme that require changes for Arcserve Backup r16 SP1:
- Installation Considerations for the Arcserve Backup Agent
for Virtual Machines:
- "Ensure that VMware Consolidated Backup (VCB)
Framework/Virtual Disk Development Kit (VDDK) is installed
on this system.", no longer applies. VDDK is now shipped
with the installation.
- Supported Operating Systems for the Agent for Microsoft SQL
Server:
- Microsoft SQL Server 2008 SP3 is now supported. (Apply SP3
to Microsoft SQL Server 2008 where specified in section 2.8
of the Readme.)
- Supported Operating Systems for the Agent for Virtual
Machines:
- The below table should be updated with the following:
VMware ESX/ESXi Server Version |
VMware VCB Framework Version |
VDDK Version |
VMware vCenter Server Version |
ESX/ESXi 3.5, Update 1, Update 2, Update 3, Update 4, Update 5 |
1.1, 1.1 Update 1, 1.5, 1.5 Update 1 |
1.1, 1.1.1, 5.0 |
2.5 Update 1, Update 2, Update 3 and Update 4, and VMware vCenter Server 4.0 |
vSphere 4.0 (ESX/ESXi) Update 1, Update 2 |
1.5 Update 1, Update 2 |
1.1, 1.1.1, 1.2, 1.2.1, 5.0 |
VMware vCenter Server 4.0, Update 1, Update 2 |
vSphere 4.1 (ESX/ESXi) |
1.5 Update 1, Update 2 |
1.1, 1.1.1, 1.2, 1.2.1, 5.0 |
VMware vCenter Server 4.1 |
The following list describes user guides and the
corresponding topics that require changes for Arcserve
Backup r16 SP1.:
The Command Line Reference Guide:
- tapecopy - Source Arguments - Replaced the source argument:
-entire with -entire_s.
- tapecopy - Examples - Replaced -entire with -entire_s where
applicable.
- ca_backup - Return Codes - Updated the following Return
Code:
- ca_backup Return Code -1 immediately
This issue is caused if ca_backup cannot reach the Arcserve
Backup Management Service when trying to execute the
command. To resolve this issue, go to the following
location and uncomment the parameters from clishell.cfg and
rerun ca_backup to apply the retry mechanism:
Location: C:\Program Files
(x86)\CA\SharedComponents\ARCserve Backup\jcli\conf
jcli.client.RetryTimes=5
jcli.client.RetryInterval=5000
- ca_restore - Return Codes - Updated the following Return
Code:
- ca_restore Return Code -1 immediately
This issue is caused if ca_restore cannot reach the
Arcserve Backup Management Service when trying to execute
the command. To resolve this issue, go to the following
location and uncomment the parameters from clishell.cfg and
rerun ca_restore to apply the retry mechanism:
Location: C:\Program Files
(x86)\CA\SharedComponents\ARCserve Backup\jcli\conf
jcli.client.RetryTimes=5
jcli.client.RetryInterval=5000
The Administration Guide:
- Using the Alert Manager/SMTP Notification - The Security
Information SMTP Setting from the Alert Manager dialog is a
new feature. The new setting gives you the ability to
authenticate the SMTP setting where you would need to input
a user name and password.
- Configure Cloud Connections - Replaced 'Amazon S3' with
'cloud connection' in the following Note:
Note: To eliminate potential clock skew errors when
connecting to the cloud, verify that your computer has the
correct time zone specified, and the clock is synchronized
with the global time. As a best practice, you should always
check the time of your computer against the GMT time. If
the time of your computer is not synchronized with the
global clock time (within 5 to 10 minutes), cloud
connection will not work. If necessary, reset the correct
time for your computer and then resubmit the archive job.
The Agent for Virtual Machines Guide:
- Troubleshooting/Backup and Recovery Operations - NEW
troubleshooting topic named "Recover VM Job Fails When Disk
Share Levels Were Backed Up From an ESX Server 4.0 to 4.1"
Valid on Windows operating systems.
Symptom
When you recover a virtual machine that contains disk share
levels that were backed up from an ESX server 4.0 to 4.1,
the recovery fails.
Solution
To remedy this problem, do the following:
- Open the registry.
- Navigate to the following location:
HKEY_LOCAL_MACHINE\Computer Associates\Arcserve
Backup\Client Agent\Parameters
- Specify RetainDiskResourceForVDDK as the Value Name.
- Specify one of the following DWORD values for the key:
- 1--Retain the disk resource allocation
- 0--Do not retain the disk resource allocation
- Save the key and close Windows Registry Editor.
The registry is updated and you can successfully recover
the VM job.
- Troubleshooting/Backup and Recovery Operations - NEW
troubleshooting topic named "Using Different Versions of
VDDK for VMware Backups"
Valid on Windows operating systems.
Symptom
Arcserve Backup is packaged with the default VDDK 5.0
binaries. If you install a later version of VDDK, then you
need to change the VDDK installed location in the registry
manually. Otherwise, the VMware backups will always use
VDDK 5.0 instead of the latest version you have.
Solution
To remedy this problem, do the following:
- Open the registry.
- Navigate to the following location:
HKEY_LOCAL_MACHINE\Software\ComputerAssociates\Arcserve
Backup\ClientAgent\Parameters
- Specify VDDKDirectory as the Value Name.
- Change the "ValueData" field to the location where the
latest VDDK version is installed.
The location in the registry is updated.
Online Help:
- NEW Agent Warning Message AW0223:
Warning AW0223
Virus detected - File restored, AV action on the file
skipped. (FILE=<File Name>)
Module:
NT Client Agent
Reason:
Antivirus scan operation is skipped on the file, but file
is restored.
Action:
Verify the importance of the file where the virus was found
on the restored file.
If the problem persists, contact Arcserve Support for
online technical assistance and a complete list of
locations, primary service hours, and telephone numbers.
- NEW Agent Warning Message AW0550:
Warning AW0550
Unable to connect to the VM agent. File-level restore will
not be available. (VM agent = [VM name])
Module:
Agent for Virtual Machines
Reasons:
- The proxy and virtual machine running different versions of
the VM agent.
- The Universal Agent service on the VM stopped.
- The virtual machine is powered off or unavailable.
- The IP address of the VM may have changed since the last
Arcserve Backup database update.
Actions:
To help ensure that you have connection to the VM Agent, do
one of the following:
- Confirm that the agents running on the virtual machines and
the proxy server are of the same build.
- Specify the Arcserve Backup server using the Agent Admin
and restart the CA Universal Agent service.
- Confirm that the virtual machine is powered on and restart
the CA Universal Agent service.
- NEW Agent Error Message AE9799:
Error AE9799
Receive certain types of incorrect configuration, like
network or Active Directory configuration or bad
performance.
Module:
Agent for Microsoft Exchange Server
Reasons:
The Exchange Server does not run in a normal state.
Actions:
Go to the Event Log and search for specific errors or
warnings that indicates the problems of the Exchange Server
and fix accordingly.
- Licensing Information (Update):
Arcserve Backup licenses are installed and managed
centrally on the Arcserve Backup primary server. However,
the following agents must be licensed on the servers where
you are installing the agents:
- Arcserve Backup for Windows Agent for Sybase
- Arcserve Backup for Windows Agent for Informix
- Arcserve Backup for Windows Enterprise Option for SAP R/3
for Oracle
With the exception of the following two agents, which are
centrally licensed by Arcserve Backup:
- Arcserve Backup for Windows Agent for Oracle
- Arcserve Backup for Windows Agent for Lotus Domino
The Client Agents Guide:
- An HTTP link for the AD Object Level Restore Utility option
is missing from the Access the Backup Agent topic. The
hypertext link should link to the same information stated
in the How Arcserve Backup Protects Active Directory Data
on Domain Controller Servers topic from the Arcserve Backup
Administration Guide.
Arcserve Backup r16 for Windows Compatibility Matrix
- Include support for SharePoint Server 2010 SP1 for the
Agent for Microsoft SharePoint.
The Implementation Guide:
- Acknowledgments/VMware VDDK (Update):
This Arcserve product contains certain VDDK technology
licensed by Arcserve from VMware, Inc. and its licensors
(the "VDDK Software"). The VDDK Software contains certain
third party information and terms which identifies various
third-party components that may be used with the VDDK
Software and sets out certain notices, attributions and/or
terms that VMware is required to provide to you by the
third party licensors of those components. Such information
is provided in the file
open_source_license_VMware_Virtual_Disk_Development_Kit_5.0.txt,
which accompanies the VDDK Software. In addition, Arcserve
makes the source code of certain of these third party
components available under their respective open source
licenses at http://opensrcd.ca.com/ips/08384_6/.
11.0 Language Certifications
An internationalized product is an English product that
runs correctly on local language versions of the required
operating system and required third-party products and
supports local language data for input and output.
Internationalized products also support the ability to
specify local language conventions for date, time,
currency, and number formats.
A translated product (sometimes referred to as a localized
product) is an internationalized product that includes
local language support for the product's user interface,
online help and other documentation, as well as local
language default settings for date, time, currency, and
number formats.
For Arcserve Backup for Windows, this release has been
internationalized and translated into the following
languages, in addition to the English release:
- Brazilian-Portuguese
- French
- German
- Italian
- Japanese
- Simplified Chinese
- Spanish
- Traditional Chinese
If you run this product on a language environment not
included in the list, you may experience problems.
Copyright © 2014 Arcserve. All rights reserved. All
trademarks, trade names, service marks, and logos
referenced herein belong to their respective companies.