Arcserve

Arcserve® Backup for Windows r17 Release Notes

2.0 New Features, Enhancements, General Updates

3.0 Considerations for Unix Agent and Datamovers

7.0 Upgrade Considerations

8.0 General Considerations

9.0 Backward Compatibility

11.0 Limitations

12.0 Issues Fixed
12.1 Agent for Hyper-V
12.2 Agent for Lotus Domino
12.3 Agent for Microsoft Sharepoint
12.4 Agent for Microsoft SQL Server
12.5 Agent for Open Files for Windows
12.6 Agent for Oracle
12.7 Agent for Oracle on UNIX and Linux
12.8 Agent for VMware
12.9 Arcserve Backup Integration with UDP and D2D
12.10 Base
12.11 Client Agent for Linux
12.12 Client Agent for Windows
12.13 Dashboard
12.14 Disaster Recovery Option
12.15 Enterprise Option for SAP on UNIX and Linux
12.16 Global Dashboard
12.17 Image Option
12.18 Microsoft Exchange Server
12.19 NAS Option
12.20 SAN Option
12.21 Tape Library Option

13.0 Language Certifications

14.0 Contact Arcserve

1.0 Welcome

Welcome to the Arcserve Backup for Windows r17 Release Notes. This document contains the following information related to the use of Arcserve Backup:

High-level description of the major features.

System information and other requirements you must know before installation of this product.

A list of considerations, known issues, included fixes, and any limitations to be aware of before you use this product.

You can access the most up-to-date released product documentation (Online Help and PDFs) from the Arcserve Backup website at https://www.arcserve.com/support.

2.0 New Features, Enhancements, General Updates

This section describes the new features, functional enhancements, general updates, and dropped features in Arcserve Backup r17 release.

FEATURES:

With this release, the following features are included:

Exchange Granular Restore Utility Support for Microsoft Exchange Email
With this release, Arcserve Backup offers the use of an Exchange Granular Restore utility to restore Microsoft Exchange email and non-email objects.

The utility includes the injection capability for items, such as emails, from offline databases (*.EDB) and log files to the original live Exchange databases, as well as granular data extraction to Personal Storage File (.pst) files.

For details to restore Microsoft Exchange Email, see Exchange Granular Restore Utility in the Agent for Microsoft Exchange Server Guide.

ENHANCEMENTS:

With this release, the following enhancements are supported:

Support for VMware Servers 6.0, Update 1 Versions
Arcserve Backup can now discover and protect virtual machines running on the following VMware servers:
- vSphere ESXi 6.0, Update 1
- vSphere vCenter Server 6.0, Update 1

Support for VMware VDDK 6.0, Update 1
Arcserve Backup ships VDDK 6.0, Update 1 with every Agent for Virtual Machine installation.

Support for JRE 1.8
Arcserve Backup ships JRE 1.8 by default during installation.

Support for SQLE 2014 SP1
The Arcserve Backup default database is changed to SQL Express 2014 SP1.

Support for SAP HANA database
A new Agent is provided to protect SAP HANA databases on Linux platforms.

Support for backup of Arcserve UDP RPS data store data to tape
A new option: Backup deduplication device data/UDP RPS Datastore data is now provided in the Operation tab of the Global Options dialog in the Backup Manager. This option lets you back up deduplication device data or Arcserve UDP RPS data store files.

Support for Microsoft Exchange Server 2016 - Arcserve Backup supports DB level Backup and Restores. For Document level support, use the "Exchange Granular Restore Utility".

Support for LTO-7 drives
Arcserve Backup adds support for LTO-7 as Backup destination device. LTO-7 drives provide higher capacity and improved performance as compared to the previous drives, such as LTO-6.

GENERAL UPDATES

With this release, Simulate –ca is changed to Simulate –arcserve
- Simulate.exe
  Allows Arcserve Backup configure fictitious SCSI devices (for example, tape drives and tape libraries) based on their file system. This Arcserve Backup component is a command line utility.
  
  Usage: Simulate –arcserve
- Signer type override
  For S3 Compatible/S3 sub-vendors, who use the V3/V2 authentication type to get certified with Arcserve CCI, it works fine as the default Signer type override flag is set to True. But, sub-vendors using the V4 authentication need to change the flag to False in the AmazonPlugin.properties file and restart services.
  
  SIGNER_OVERRIDE=false

DROPPED SUPPORT:

The following features are not supported in this release:

AS400

S390

IBM 3494

StorageTek ACSLS

Agent for OpenVMS

Microsoft Exchange 2003

Windows 32-bit proxy is not supported for Agent for Virtual Machine backups.

Lotus Domino 7.x and 8.0

Arcserve D2D Integration

3.0 Considerations for Unix Agent and Datamovers

For Unix Agent and Datamovers there is no update in r17. You can download the r16.5SP1 agents and datamovers using the links provided below.

Agents	Cksum	Size	File name
AS400 client agent	1013877566	1450725	arc_clnt_AS400_165sp1.tar.gz
FreeBSD client agent	2089002480	928945	arc_clnt_FreeBSD_165sp1.tar.gz
MAC client agent	3979189753	807420	arc_clnt_IntelMac_165sp1.tar.gz
VMS client agent	1274601609	7257864	arc_clnt_VMS_165sp1.tar.gz
S390 client agent	1587404879	1183833	arc_clnt_s390_165sp1.tar.gz
Solaris s86 client agent	1183572546	6499147	arc_clnt_s86_165sp1.tar.gz
Solaris s86.amd64 client agent	4037427938	3150493	arc_clnt_s86_amd64_165sp1.tar.gz
AIX datamover	8285361	151081323	arc_dm_Aix_165sp1.tar.gz
HPUX datamover	572080950	77291397	arc_dm_Hp_165sp1.tar.gz
Solaris sparc datamover	1953442744	144296585	arc_dm_Solaris_165sp1.tar.gz

To extract files from tar.gz:

Copy the file to tmp folder /tmp

Run commands:
- Tar xvzf file_name.tar.gz OR Gunzip file_name.tar.gz
- Tar xvf file_name.tar

Follow the procedures in the Arcserve document to install the agent and datamovers.

4.0 Operating System Support

For a complete list of all supported server operating systems, see the Compatibility Matrix.

5.0 System Requirements

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

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

Monitor: 1280 x 1024 or 1440 x 900 video adapter and monitor for Windows Server 2008 R2 and Windows Server 2012 R2 systems.

Disk Space:
- Primary Server: 1.6 GB, plus 1.3 GB for Agent Deployment Packages
- Member Server: 1.2 GB, 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

Microsoft .NET Framework 3.5 SP1 and 4.5 SP1 on Windows Server 2008, and Windows Server 2012 systems

Arcserve Backup Database

Arcserve Backup supports the following applications to host the Arcserve Backup database (ASDB):

The default Arcserve Backup database application is the Microsoft SQL Server 2014 Express Edition with Service Pack 1.
Notes:
1. To install Microsoft SQL Server 2014 Express Edition on Windows Server 2008 systems, SP2 is required and to install Microsoft SQL Server 2014 Express edition on Windows Server 2008 R2, SP1 is required. Otherwise, you must install a supported version of Microsoft SQL Server to host the Arcserve Backup database.
2. The default database (SQL Express 2014 SP1) is not supported by Microsoft for Windows 2003 server. As a workaround, use a remote SQL server as the Arcserve database.

For SQL Server support, refer to the Arcserve Backup r17 Compatibility Matrix site.

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

Internet Explorer 10.0

Internet Explorer 11.0

5.2 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

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

5.3 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

5.4 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

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

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

CPU:
- 800 MHz if using Exchange Server 2007
- any 64-bit CPU if using Exchange Server 2010, 2013, or 2016

RAM:
- At least 2 GB if using Microsoft Exchange Server 2007
- At least 4 GB if using Microsoft Exchange Server 2010
- At least 8 GB if using Microsoft Exchange Server 2013
- At least 8 GB if using Microsoft Exchange Server 2016

Disk Space: At least 100 MB, with at least 60 MB on hard disk where Exchange Server Agent is installed and at least 40 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 Customer Support.

5.6 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, 2010, or 2013 that you are running:

The basic Microsoft SharePoint Server 2007, 2010, or 2013 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.

Note:

If running Microsoft SharePoint Server products, apply the latest service package to the SQL Server or SQL-Express.

5.7 System Requirements for the Agent for Microsoft SQL Server

The Agent for Microsoft SQL Server contains the following system requirements:

CPU:

At least 600 MHz, 1GHz recommended for SQL Server 2005

At least 1GHz, 2GHz recommended for SQL Server 2008

At least 1GHz, 2GHz recommended for SQL Server 2012

At least 1GHz, 2GHz recommended for SQL Server 2014

RAM:

At least 512 MB, 1 GB recommended for SQL Server 2005

At least 512 MB, 2 GB recommended for SQL Server 2008

At least 512 MB, 4 GB recommended for SQL Server 2012

At least 1 GB, 4 GB recommended for SQL Server 2014

DISK SPACE:

At least 350 MB on the hard disk where the agent is installed.

5.8 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

5.9 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 site.

Sun Solaris SPARC:

On Sun Solaris SPARC, the agent requires the following:

Sun UltraSPARC models

256 MB RAM

400 MB disk space

Sun Solaris x86:

On Sun Solaris x86, the agent requires the following:

Sun x86 models

256 MB RAM

400 MB disk space

IBM AIX (Physical machine and LPAR):

On IBM AIX, the agent requires the following:

IBM RISC 6000 models

256 MB RAM

700 MB disk space

HP-UX:

On HP-UX, the agent requires the following:

HP 9000 Server/Workstation

256 MB RAM

400 MB disk space

Database Support on UNIX 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

5.10 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
- at least 1 GB if using Oracle 11g R1/R2
- at least 2 GB if using Oracle 12c

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.

5.11 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 10 MB of disk space available for this agent.

5.12 System Requirements for the Agent for Sybase

To install the agent, verify that the following requirements are satisfied:

Your system meets the Arcserve Backup base product minimum requirements.

You should also have the appropriate version of Sybase with Sybase Open Client Library and Backup Server for Sybase Adaptive Server installed, correctly configured, and working properly.

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

5.14 System Requirements for the Central Management Option

For the Central Management Option, ensure your system meets the Arcserve Backup base product minimum requirements.

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

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

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

5.17 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

5.18 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	256 MB	250 MB	400 MB
Linux	x86 and x64	256 MB	250 MB	400 MB

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

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

Note: The NDMP NAS Option supports both x64 and x86 Arcserve Backup servers to back up NAS filers.

5.21 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

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

5.23 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 11.23, the patch PHSS_37201 or higher is required

HP-UX PA-RISC 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	256 MB	250 MB	400 MB
Linux	x86 and x64	256 MB	250 MB	400 MB

5.24 System Requirements for Arcserve Backup Dashboard

No additional hardware is required beyond the Minimum Requirements listed for Arcserve Backup base product.

5.25 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 2005

Microsoft SQL Server 2008

Microsoft SQL Server 2008 R2

Microsoft SQL Server 2012

Microsoft SQL Server 2014

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

Adobe Reader 8 or later

Email clients

Global Dashboard supports the following email clients on the Central Primary Server:

Microsoft Outlook 2003, 2007, 2010, and 2013

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 2005

Microsoft SQL Server 2008

Microsoft SQL Server 2008 R2

Microsoft SQL Server 2012

Microsoft SQL Server 2014

Microsoft SQL Server 2014 Express Edition

5.26 System Requirements for Arcserve Backup Infrastructure Visualization

No additional hardware is required beyond the minimum requirements previously listed.

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

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

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

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.

Arcserve Backup installs SQL Express 2014 SP1 as the Arcserve Backup database when SQL Express is selected. This is listed as the "Default database" on the configuration screen during setup.
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.

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 installing Arcserve Backup as a Member Server on Windows Server 2008 Core and Windows Server 2012 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 and Windows Server 2012 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 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 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 2014 SP1 as the Arcserve Backup database, the application Event Log displays a number of informational messages for Event IDs 17137 and 5084. This is a known Microsoft behavior and does not affect the operation of Arcserve Backup.

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

Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 are required for the Document Level Agent for Microsoft Exchange Server 2007, 2010, and 2013 to function properly. If the setup process does not detect this application, the Document Level Agent will be disabled.
To activate the Document Level Agent, perform the following:
1. Obtain Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 from the Microsoft website and install it.
2. Stop the Arcserve Backup Universal Agent Service.
  Note: Please make sure that no browse operation is performed, and no backup or restore job is running before stopping this service.
3. Run <Exchange agent home directory>\DocumentLevel\ExchDocWrapper.exe -regServer to register the Document Level Agent.
4. Start the Arcserve Backup Universal Agent service.

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

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

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

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

6.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 for operating systems prior to Windows Server 2012.

6.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, r16 SP1, r16.5, and r16.5 SP1)
- Client Agent for UNIX (r12.5, r15, r16, r16 SP1, r16.5, and r16.5 SP1)
- Oracle Agent for Linux (r12.5, r15, r16, r16 SP1, r16.5, and r16.5 SP1)
- Oracle Agent for UNIX (r12.5, r15, r16, r16 SP1, r16.5, and r16.5 SP1)
- Enterprise Option for SAP R/3 for Oracle for Linux (r16, r16 SP1, r16.5, and r16.5 SP1)
- Enterprise Option for SAP R/3 for Oracle for UNIX (r16, r16 SP1, r16.5, and r16.5 SP1)
- Data Mover for Linux (r15, r16, r16 SP1, r16.5, and r16.5 SP1)
- Data Mover for UNIX (r15, r16, r16 SP1, r16.5, and r16.5 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.

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

VMware Systems: Install the Agent for Virtual Machines on the system that is intended to operate as the backup proxy system. Populate the Arcserve Backup database using the Arcserve VMware Configuration Tool on the backup proxy system. Deploy the Agent for Virtual Machines using Agent Deployment. For more information, see the Arcserve Backup Agent for Virtual Machines Guide.

Hyper-V Systems: Install the Arcserve Backup Server components on the system that is intended to operate as the primary or standalone server. Install the Agent for Virtual Machines on the Hyper-V host system. Populate the Arcserve Backup database using the Arcserve Hyper-V Configuration Tool on the Hyper-V host system. Deploy the Agent for Virtual Machines using Agent Deployment. For more information, see the Arcserve Backup Agent for Virtual Machines Guide.

When installing Arcserve Backup Agent for Virtual Machines on Windows Server 2008 Core, run mastersetup.exe directly from DVD\Install. When you use setup.exe from the DVD root, the DemoShield launches requiring Internet Explorer to run. Internet Explorer is not available in Windows Server 2008 Core operating systems.

When installing Arcserve Backup agent for virtual machines on a Windows operating system, create SMB (Server Message Block) shares by adding the IPV6 (Internet Protocol Version 6) address to the host file and the backup job runs successfully.
Note: Adding the IPV6 address to the host file applies to both Hyper-V Virtual Machines and Writer Backups on the SMB shares.

When installing Arcserve Backup agent for virtual machines on a Windows operating system, VDDK 6.0.1 for an x64 machine. Ensure that all VMware ESX Servers have the latest updates installed. VDDK 6.0.1 does not support VMware ESX Server 5.0\4.x\3.5, however if you have this version, you need to download VDDK 5.0/5.1 Update 2 manually and then follow the instructions in the troubleshooting topic: "Using Different Versions of VDDK for VMware Backups" from the Agent for Virtual Machines user guide.

6.10 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 and Windows Server 2012 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 and Windows Server 2012 Core operating systems.

6.11 Installation Considerations for Oracle (UNIX and Linux)

To back up and restore Oracle data on UNIX and Linux Data Mover, consider the following:

The Arcserve Backup for UNIX and Linux Data Mover option is required.

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

7.0 Upgrade Considerations

The following section provides information about upgrade prerequisites, configurations, and issues to consider before upgrading the Arcserve Backup base product.

When you upgrade Arcserve Backup from a previous release, consider the following scenarios:
- If the previous installation was that of a member server, you must upgrade the Arcserve Backup components that apply to Member server installation.
- If the previous installation was that of the Arcserve Backup Manager Console or Arcserve Backup Agents, and you did not install the Arcserve Backup Server components, you must upgrade the Manager Console or the Arcserve Backup Agents without installing the Arcserve Backup Server components.
  The Server Configuration Wizard lets you change the role of the server after you complete the upgrade process. Optionally, you can uninstall and then reinstall Arcserve Backup. However, to ensure that you do not lose records of your backup and restore data, you must not overwrite the Arcserve Backup database instance that is detected by the Installation Wizard.
  
  For more information about supported upgrades, refer to the Arcserve Backup for Windows Implementation Guide - Supported Upgrades section.
- If the client agent was installed and the base product was not, then you cannot install the base product and can only upgrade the client agent first.
- If you want to install the base product after the client agent was installed, then launch the setup again and install the base product.
- After or during the processing of upgrading Arcserve Backup to the latest r17 release, you are required to reboot the server.

When you customize job scripts on the primary server using the previous Arcserve Backup release, you will not be able to modify the job scripts after upgrading to the current release and will get an error message warning you that the job cannot be unpacked. To use job scripts created with previous versions of Arcserve Backup after upgrading, you must manually select the sources and then submit the jobs.

The upgrade process does not install the drivers required by the Image Option. As a result, scheduled jobs involving the Image Option can fail. To remedy this problem, you must install the required drivers manually using the Enterprise Module configuration utility.
Note: For more information, see Configure Devices using Enterprise Module Configuration in the Administration Guide.

Ensure the Regional and Language options for the Arcserve Backup Server and Arcserve Backup Agents are set identically to avoid browsing and encryption problems typical when operating the current version of Arcserve Backup with agents from previous versions.

The name of the Arcserve Backup home directory has changed since the previous release. If you specified the Arcserve Backup home directory as a parameter in the commands of any generic jobs created prior to upgrading, you are required to modify those jobs and correct the path to the current Arcserve Backup home directory name. In this release, the default Arcserve Backup home directory is "CA\ARCserve Backup".

This release of Arcserve Backup installs CAPKI 4.2.8, which can cause system rebooting if Arcserve Backup services and back-end programs are not stopped before upgrading. The setup process automatically stops these services and programs unless you are performing an SDO installation. In this case, you should stop all services and back-end programs manually before you proceed.

When upgrading to this release of Arcserve Backup from older versions in a cluster environment and your database is SQL Server Express, perform the following steps after installation to ensure correct user profile management:
- Restart the ARCSERVE_DB service.
- Run command line: BABHOME\caauthd.exe -setupuser
- Run command line: BABHOME\cadiscovd.exe -m

In this release, Microsoft Exchange Agent entails the following backward compatibility limitations:
- For Arcserve Backup r15.0 and r16.0 - Upgrade the Microsoft Exchange Agent the same time as the server if both versions have the Exchange Doc Level Agent for Microsoft Exchange 2010 or 2013.
- For Arcserve Backup r16.5 SP1 - Apply RO70938 to the agent side if r16.5 SP1 has the Exchange Doc Level Agent for Microsoft Exchange 2010 or 2013.

8.0 General Considerations

The following section provides general information to consider when using Arcserve Backup:

The Arcserve Backup command line uses AES 256-bit encryption to communicate with the Arcserve Backup base product.

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:

Arcserve Backup Agent for Virtual Machines lets you perform backup and recovery operations using ESX Server 3.5, Virtual Center server 2.5, vSphere ESX/ESXi Server 4.0, 4.1, 5.0, 5.1, 5.5, 5.5 Update 1 and vSphere vCenter 4.0, 4.1, 5.0, 5.1, 5,5, 5.5 Update 1.
Note: To perform backup and recovery options of this type, you must install VDDK on the backup proxy system.

Arcserve Agent for Virtual Machines provides Writer Backup for remote shares. When you add a node to the client agent; it is required that you provide your domain credentials to allow access to the file share that hosts the application data. Some of the requirements for the backup agent to run successfully are as follows:
- Run in a security context that contains backup operators and administrator privileges on the application server and the file server.
- Run in a security context that contains at least Read permissions on the file share data that is being backed up.
- Run in a security context that contains at least Write permissions on the file server that is being restored.

Arcserve Agent for Virtual Machines provides Hyper-V Backup for remote shares. When you submit the virtual machine for backup on the proxy server; it is required that you provide your domain credentials to allow access to the file share that hosts the application data. Some of the requirements for the backup agent to run successfully are as follows:
- Run in a security context that contains backup operators and administrator privileges on the application server and the file server.
- Run in a security context that contains at least Read permissions on the file share data that is being backed up.
- Run in a security context that contains at least Write permissions on the file server that is being restored.

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:
1. 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.
2. 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.
3. 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.

9.0 Backward Compatibility

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

Arcserve Backup r16 (and all service packs)

Arcserve Backup r15 (and all service packs)

Arcserve Backup r16.5 (and all service packs)

10.0 Known Issues

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

10.1 Known Issues for the Base Product

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

Backup jobs from backup servers running on Windows Server 2008 or Windows Vista can fail when the source data resides on remote shares and the operating system running on the share is not Windows Server 2008 or Windows Vista. This behavior affects x86 and x64 operating systems.
To correct this behavior, apply the hotfix that is required for the operating system. You can download the hotfix from Article ID: 973278 on the Microsoft website.

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 Technical Support at https://www.arcserve.com/support to correct the license count.

The Tape Compare utility does not support comparing tapes that were created using multiplexing or encryption.

Broadcast Alerts do not function on systems running Microsoft Windows Server 2008. This behavior is observed because Microsoft Windows Server 2008 does not support messaging service.

After you restore the Arcserve 64-bit 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:
1. Confirm that the remote machine is reachable across the network and that the IP Address matches the remote machine name. Run the following commands to confirm:
  - ping <MachineName>
  - ping <IPAddress>
  - ping –a <IPAddress>
  If the remote system can be pinged and the name matches the IP address, the Diagnostic Wizard should experience no problems. If the system cannot be pinged at all, check the network connections and ensure the system is operational. If the name does not match the IP address, continue.
2. Open a command prompt and run ipconfig /all to show the current IP configurations and other network configurations of a machine. Examine the command output for mistakes in your configurations. If mistakes exist, the network cannot communicate properly.
  1. Open Network Connections.
  2. Double-click <Connection Name>.
  3. Click the Support tab.
  4. Click Details.
  5. Note the values for "WINS Servers". The WINS Servers provide the NetBIOS name resolution for your remote servers.
  6. Ping the WINS servers using the commands in Step 1.
3. Run the following command to check the NetBIOS Remote Cache Name Table:
  nbtstat -c
  
  Using NetBIOS over TCP/IP, this command lists the cache of remote machine names and their IP addresses, and outputs statistics into four columns: Name, Type, Host Address and Life (sec). Examine the output and 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.
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
5. Purge and reload the NetBIOS Remote Cache Name Table:
  nbtstat -R
6. Run nbtstat -c again. The table should now be empty, or contain only a few new items with lives of about 600 seconds.
7. Check the NetBIOS Remote Machine Name Table:
  nbtstat -a <RemoteName>
  
  This command lists a remote machine name table, given the machine name you specify.
  
  nbtstat -A <IPAddress>
  
  This command lists a remote machine name table, given the IP address you specify.
  
  The tables should show identical information: the name of the remote system as "Registered" for the IP Address.
  
  If the steps above do not solve your NetBIOS communication problem, you must contact your WINS server administrator to reconfigure the system.

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:
1. After you restore the Arcserve Backup database, use the Merge utility to merge the Arcserve Backup database backup sessions.
2. Close and then reopen the Restore Manager window to refresh the information that displays in the Restore by Tree source directory tree.

When you modify a makeup job that was automatically created after a full-node backup job 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:
- Files in the \SIS Common Store are normally excluded from jobs by the registry key, FilesNotToBackup, and should not be backed up or restored unless they are *.sis files. However:
  - when you perform a remote backup of an entire drive on which Single Instance Storage was activated as the backup source, the job fails and AW0004 is recorded. This is because Arcserve Backup is attempting to back up files that should have been excluded. Restoring the entire session to its original location also restored files that should have been excluded.
  - when you perform a restore of an entire session, files in the \SIS Common Store that should not have been backed up are now skipped.
  Note: If you select only the \SIS Common Store to back up, excluded files are not backed up, as expected.
- When you restore SIS links using the global option "log all activity" set to on, the Job Log shows only the links have been restored, not the data files. This is not an issue; if data files are already in the \SIS Common Store, those files will not be restored.
- When restoring the \SIS Common Store that was remotely backed up and you have deleted all the link files corresponding to the restored common store files, the common store files are not deleted. The Remote Restore Job Log shows the files as restored.

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
1. 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.
```
2. 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
3. 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.

When you install this release of Arcserve Backup on the cluster node of a Windows Server 2008 cluster or a Windows Server 2012 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\CA ARCserve Backup\ClientAgent\Parameters

Value Name: SkipSystemStateBkup

Data Type: REG_DWORD

Value: 1

For 32-bit OS, local backup jobs, add the key here:

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup

Value Name: SkipSystemStateBkup

Data Type: REG_DWORD

Value: 1

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\CA 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.

Backward Compatibility is not supported for proxy servers and agents running on virtual machines with different versions of Arcserve Backup.

Thin Provisioning in the Windows 8 and Windows Server 2012 operating system requires you to have the physical disk space equivalent to the size of the volume that is being backed up for Raw Volume/Disk restores.

To browse and back up drives that are protected by BitLocker Drive Encryption, log in to the operating system to unlock the volume before you submit the backup job. With BitLocker Drive Encryption, the Backup Manager cannot display the individual directories and files contained in the drive, which prevents you from submitting backups. This behavior also applies to the process of restoring data to BitLocker protected drives: Log in to the operating system to unlock the volume before you submit the restore job.

When you back up optimized NTFS Deduplication Volumes, the Job Monitor displays false results. This behavior occurs because Arcserve Backup calculates the logical sizes rather than the physical sizes of the files from the Job Monitor. You can find the accurate data at the end of the job in the activity log.

On Windows Server 2008 R2 or Windows Server 2008 R2 SP1 systems, Hyper-V VSS writer backups can fail when the state of Cluster Shared Volumes are set to the Redirected mode. To correct this behavior, install Windows Server hotfix 2674551. With the hotfix applied to the server, you can set the state to online and Hyper-V VSS Writer backup jobs will complete successfully.

When you restore physical disk/volume backup sessions of a specific sector size (4k) to another physical disk/volume of a different sector size (512 bytes) the restore job fails because the geometry of disk devices and media in the backup session does not match the destination device where the files and folders are being restored to.

Scan backup media contents and compare backup media contents to disk are not supported for Raw backups.

After restoring NTFS Deduplication optimized sessions, the quantity of bytes restored to the disk are not the actual size of the file that were restored. This behavior occurs when the data for the user files are spread across multiple NTFS Deduplication metadata files.

Due to a known SQL Server Management Studio 2012 SP1 issue; when you first install Arcserve Backup or upgrade to the latest release using Setup, Silent, Agent Deployment, or Remote installation; uninstalling the application may fail when SQL Server Management Studio 2012 SP1 is installed on the target machine. For more information, see Article 770630 on the Microsoft website.
To correct this behavior, uninstall the Management Tools feature for both Basic and Complete versions only if the article specified in the link applies to you.

When you submit backups for Arcserve D2D nodes with the (global backup) Compare backup media to disk option specified, the job completes successfully, however, the job status displays failed and the following message appears in the Activity Log:
```
The Client Agent does not support comparing Arcserve D2D sessions.
```
This is expected behavior. The Compare option is not supported for Arcserve D2D sessions.

The Arcserve Backup installation screens may stop responding when the installation media (ISO image or DVD) is mounted on a remote location. When you encounter this behavior, mount the installation media on a local location.

While backup jobs of virtual machines are running from backup servers running Windows Server 2012, the status for all virtual machines always appears as Backing Up. This behavior occurs only when you perform full node backups of Hyper-V servers using the Client Agent for Windows, or using the Hyper-V VSS writer to back up the virtual machines. In addition, you cannot perform various tasks on the virtual machines such as power on, power off, save, pause, reset, rename, and enable replication.

When using tapecopy to copy the sessions from a source tape to a destination tape where the destination tape is a blank media, use the -idr parameter to generate a new random ID on the destination tape to avoid any errors during spanning of tapes. For more details, see the related Arcserve Backup KB article.

When installing Arcserve Backup for the first time on a Windows Server 2012 R2 machine, whether it is a local or remote installation, a delay in warning messages for the Configuration process occurs. It is recommended to wait for these messages to appear before canceling the install. In the meantime, we are working to resolve this problem.

Arcserve Backup does not support multi-byte characters and unicode characters when specifying the Duplicate Media Prefix in the Backup Manager Destination tab.

Microsoft Windows 10 Edge browser is not supported to view Arcserve Backup reports.

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

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

When you back up application-based writer data (for example, SQL Server data or Hyper-V virtual machines) that resides on remote shares, verify that the remote share is present before you start the recovery job. Use this approach when you perform Client Agent for Windows recoveries and Agent for Virtual Machine recoveries.
Note: You cannot access application based writers when performing disaster recoveries. The solution to this behavior is to recover the system state and the volumes, bring the computer online, and then recover the writers. You can then access the application data on remote shares after the application writer recovery starts.

Client Agent (for Windows) backup jobs that consist of the full system, any volume, any writer, or system state that run using Volume Shadow Copy (VSS) and multistreaming do not complete successfully when the Enable physical disk\volume backup & restore option is specified and selected for backup. You specify the Enable physical disk\volume backup & restore option on the Configuration dialog in the Arcserve Backup Agent Admin. To prevent this behavior from occurring, do not specify the Enable physical disk\volume backup & restore option for backups of these types.

Client Agent backup jobs can fail when using the agent to back up virtual machines running on Windows Server 2012 operating systems with the iSCSI Target Storage Provider (VDS and VSS hardware providers) feature enabled. The following message appears in the Activity Log:
```
The volume shadow service provider had an unexpected error. The error code is logged in the error log.  
```
To correct this behavior, configure the iSCSI storage provider identity credentials on the Windows Server 2012. For more information, see Step 4 of the following article in the Microsoft Windows Server TechNet Library: http://technet.microsoft.com/en-us/library/hh848268.

Arcserve Backup will not traverse the system junction points as they are created by the system for the purpose of compatibility. The agent ignores the junction points and continues to back up the system.

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

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

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

10.6 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 agent supports document level backups for Exchange Server 2013 data in the r16.5 Update 3 release.

When you select Microsoft Exchange server directory as the backup source and perform file system backup with the client agent, please note the following:
- If the Exchange Information Store is running, the Exchange server files will be skipped during the backup.
- If the Exchange Information Store is NOT running, the Exchange server files will NOT be skipped during the backup.

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 needs to be created for 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)

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.

Arcserve Backup does not support backing up Microsoft Exchange Server 2013 Inbox rules when performing document level backups. Microsoft is aware of this problem and is working to provide an alternative solution.

When you back up Exchange Server 2013 data at the document level, the backup job may not respond after some data has been copied. If you encounter this problem, then it is recommended to perform a backup at the database level. Microsoft is aware of this problem and is working to provide an alternative solution.

When using Arcserve Exchange Granular Restore Utility, all the items are not getting restored to the live server.
Symptom

After a restore job, the following item properties may not be properly restored:
- InternetHeaders
- RTFCompressed
- Codepage
- DateCompleted
- TaskRecurrence
- RecurrencePattern
- AppointmentTimeZoneDefinitionEndDisplay
- ReminderTime
- CommonEnd
- AppointmentStartWhole
- AppointmentEndWhole
- BusyStatus
- Meeting Owner
- Company Name of Task
Solution

Use Export to PST option to restore the missing items.

When you search an email and restore the email from the search result, the email fails to restore to the mailbox. If you browse the mailbox and then select an email for restore, the email successfully restores.

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

If you have applied test fix QO94901 to a server running the Arcserve Backup Agent for Microsoft SharePoint Server 2007, you may no longer see the SharePoint Farm in the Arcserve Backup Manager, and may see an AE9956 Initialization of the COM+ error in the activity log. To avoid this situation, perform the following steps:
1. On the machine on which the Agent for Microsoft SharePoint Server 2007 is installed, open Administrative Tools and select Component Services.
2. Select the SPSO12 component and delete it.
3. From the Windows Start menu, click All Programs, Arcserve, Arcserve Backup, Backup Agent Admin.
4. From the pull down menu, choose Arcserve Backup for Windows Agent for Microsoft SharePoint Server 2007.
5. From the menu, click Options, Configuration.
6. Update each field and check the box to Reset Credential.
7. Close and reopen Arcserve Backup Manager and expand the SharePoint Server Agent to see the Microsoft SharePoint Server 2007 Farm.

If you upgrade the Agent for Microsoft SharePoint Server 2007 from previous releases to current release and you choose the Server Farm Installation (Complete Installation and Web Front End Installation), use a User Name that is the same as the Farm Administrator required to create the Farm to avoid reconfiguring the Agent after installation. This restriction does not affect SharePoint Single Server Installation (standalone).

The Arcserve Backup Agent for SharePoint Server does not support restore operations of content databases that have multiple data files spanned across different disks.

When you restore a Wiki Page Library to its original location, the Wiki Page Library link does not appear in the Quick Launch section of the SharePoint Server portal. However, you can find the Wiki Page Library link under the View all Site Content section of the portal.
Note: This is a Microsoft SharePoint Server limitation.

Restore jobs fail when restoring site collections using the Community Site and eDiscovery templates. The following message generates when the restore jobs fail:
```
The element 'Field' in namespace 'urn:deployment-manifest-schema' cannot contain text. List of possible elements expected: any element in namespace '##any'
```
When using the Community Site template to restore site collections, the first restore job completes successfully. However, subsequent restores using this template fail. When using the eDiscovery template to restore site collections, the first restore using the template, and all subsequent restores using this template fail.

Note: This is a Microsoft SharePoint Server limitation.

Due to a Microsoft SharePoint Server limitation, performing a full farm restore fails with the following error messages:
Component (590/998)Farm\Microsoft SharePoint Foundation Web Application\XXXXXXXXX Failed, Failure Message: Object XXXXXXXXX failed in event OnRestore.

For more information, see the spbackup.log or sprestore.log file located in the backup directory:

FileLoadException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config

Error: Cannot write the configuration file.

To prevent this behavior from occurring, perform one of the following actions and then resubmit the restore job:
- Stop the Application Host Helper Service Windows service, perform the full farm restore, and then restart the Application Host Helper Service.
- Restore only the "Farm\Microsoft SharePoint Foundation Web Application\XXXXXXXXX" object again.
Note: "XXXXXXXXX" is the web application name.

10.8 Known Issues for the Agent for Microsoft SQL Server

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

If 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:
1. Locate the version of sqlvdi.dll that belongs to the newest version of Microsoft SQL Server on the machine.
2. From a command prompt, change to the directory containing the selected sqlvdi.dll, and enter the following command to re-register the Virtual Devices component and re-enable backup operations:
```
	regsvr32 sqlvdi.dll
```

On a primary server running remote SQL, backup jobs submitted via backup manager to the member server may run slowly.

Starting with release 12.0, the Agent for Microsoft SQL Server is now a push agent. To include SQL database files during a backup job, set the BackupDBFiles registry key to 1. The SkipDSAFiles registry key no longer applies to SQL database files. For more information, see the 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.)

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:

Provide full control permissions when you access the following path:

C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\test2.md

Open the SQL Server Agent service, apply the local system account, and then restart the SQL Server service.

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.

10.9 Known Issues for the Agent for Oracle (Windows)

The following section provides information on support for the Agent for Oracle:

Database files are excluded (skipped) from backups submitted through the Client Agent for Windows up to a limit of 2048 files. If your number of database files exceeds this limit, you must add a DWORD registry value called MaxFileFilter to make sure all database files are properly excluded from the backups made with the Client Agent for Windows:
HKEY_LOCALMACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup

Value Name: MaxFileFilter

Type: DWORD

Value: Set to a value greater than the number of database files you wish to exclude. For example, if there are 3006 DB files, a value of 4096 ensures all database files are excluded from the backup.

When performing a backup of Oracle objects with copies, such as the Oracle Tablespace or full database, the job fails if the BACKUP_TAPE_IO_SLAVES parameter is false. To set this parameter to true, perform the following steps:
1. Open a sqlplus prompt.
2. Enter the following command:
```
alter system set backup_tape_io_slaves = true deferred
```
3. Restart the database.
4. Set the Number of Copies option to a value greater than 1.
5. Submit the backup job.
Note: You may also use the "show parameter backup_tape_io_slaves" command to check the value of the parameter.

When you change the system time on the machine on which Oracle Server and the Agent for Oracle are installed, archive log backups will fail.

When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored. This is because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.

When performing an offline backup of an Oracle RAC9i database with RMAN options from the GUI, 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.

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

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 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:
1. Open the Control Panel and choose Regional and Language Options.
2. Click Advanced.
3. Choose the option, Apply all settings to the current user account and to the default user profile.
4. Restart the machine.

When you attempt to log in remotely to the server where Arcserve Backup Agent for Open Files is installed; the login fails. In addition, you cannot view the node properties from Arcserve Backup Manager for the following options:
- Configure Agent for Open Files
- View Agent for Open File Status
- View Agent for Open File Log Files
The login fails because the server contains a network logon security permission that is set to "Guest Only"; where you can only log in as a guest. This issue applies to all Windows operating systems.

As a work-around, perform the following steps:
1. Go to Start, Control Panel, Administrative Tools, and open the Local Security Policy folder.
  The Local Security Policy dialog opens.
2. From the Security Settings hierarchy tree, click Local Policies and then Security Options.
3. Double-click Network access: Sharing and security model for local accounts from the Security Options Policy list.
  The selected policy dialog opens.
4. From the Local Security Setting tab, select Classic - local users authenticate as themselves from the drop-down list.
5. Click OK.
You can now log in remotely to the server.

If you select “Use BAOF for Open Files Backup” in the OFA, the backup continues to go through VSS only. To disable VSS for the backup, add the “UseVssForOpenFiles” registry key and set it to zero in the below path:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\ClientAgent\Parameters

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

To prevent Volume Shadow Copy (VSS) issues, it is recommended not to submit a multistreaming backup job when the "Enable physical disk\volume backup & restore" option is selected from the Arcserve Backup Agent Admin screen.

VSS backup will fail for the second level VHD (Nested VHD) volume because Microsoft cannot back up the nested VHD volume. For more information, see https://msdn.microsoft.com/en-us/library/aa382650(v=vs.85).aspx.

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

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

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.

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/Arcserve/ABcmagt; touch /opt/Arcserve/ABcmagt/caagent
  - global# ln -sf /opt/Arcserve/ABcmagt/caagent /usr/bin/caagent

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

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

The agent does not support recovering virtual machines to data stores that are named using the special characters asterisk, the at symbol, and the German umlaut character. Backup jobs for virtual machines named using these characters may fail.

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

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 a successful recovery of VMware virtual machines, the Disk Provisioning Type of the Virtual Hard Disk depends on the backup approach that you use.
- When you back up thin disks using VDDK, and that backup is not an active block backup, you can recover that disk as a thick disk.
- When you back up thin disks 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.

When multiple Hyper-V virtual machines contain multiple disks that are sharing a common parent disk; the process of recovering any of the machines in a running state can fail. This behavior is expected when the process of recovering Hyper-V virtual machines tries to overwrite the parent disk where another virtual machine is using it. Under this condition, the job appears to complete successfully, however, the Hyper-V virtual machine is not going to start.

When you back up a virtual machine using the agent and the virtual machine name on the Hyper-V manager is more than 64 characters, the backup job fails.

When a Hyper-V virtual machine contains data (VHD/configuration files) residing on remote SMB shares, verify that the remote share is present before you start the VM recovery job to the original location.
Note: You cannot access application-based writers when performing disaster recoveries. The solution to this behavior is to recover the system state and the volumes, bring the computer online, and then recover the writers. You can then access the application data on remote shares after the application writer recovery starts.

When you back up a VMware or Hyper-V virtual machine with application-based writer data that resides on SMB shares, the backup job fails.

The agent does not support restoring the data from the VHDX transaction log, when recovering virtual machines. The agent behaves in this manner because the Hyper-V VSS writer snapshot does not quiesce or commit the transaction log data. In addition, the Hyper-V VSS does not provide a provision in the VSS snapshot API.

Hyper-V VSS Writer backup jobs can fail when using the agent to back up virtual machines running on Windows Server 2012 operating systems with the iSCSI Target Storage Provider (VDS and VSS hardware providers) feature enabled. The following message appears in the Activity Log:
```
The volume shadow service provider had an unexpected error. The error code is logged in the error log.  
```
To correct this behavior, configure the iSCSI storage provider identity credentials on the Hyper-V server. For more information, see Step 4 of the following article in the Microsoft Windows Server TechNet Library:
```
http://technet.microsoft.com/en-us/library/hh848268
```

RAW backup with file level restore is not supported for ReFS file systems; therefore file level restore is not available with RAW backup.

Due to a Microsoft known issue, when you configure storage space on a VMware or Hyper-V virtual machine, backing up the virtual machine fails with a snapshot creation error.

The version of Windows Hyper-V that is running on the target server is older than the version of Windows Hyper-V that is running on the server that was backed up. To resolve this issue, restore the virtual machine that was backed up on the Windows Hyper-V server to an equal or later version of a Windows Hyper-V server.

The agent does not support backing up Hyper-V virtual machines that contain disks that are equal to 64 terabytes.

VMware VDDK does not support file mode backups with NTFS Deduplication volumes, therefore the volumes are skipped from the file mode backup.

By default, VMware VDDK 6.0.1 is packaged with the Arcserve Backup r17 release. VDDK 6.0.1 does not support ESX Server 5.0/4.x/3.5 and vCenter Server 4.x\2.5, therefore backing up or restoring virtual machines on these servers may fail. To resolve this issue, you can download and install VDDK 5.0\VDDK 5.1 Update 2 and change the VDDKDirectory registry key to the location where VDDK 6.0.1 is installed.

When VMware vSphere High Availability (HA) or VMware vMotion is in progress during a backup job, the backup job fails. Once VMware vSphere HA or VMware vMotion completes, run the backup job again and it will complete successfully.

When recovering data from NTFS Deduplication volumes that are optimized and a volume contains a very large quantity of files (1 million or more files), the throughput calculation in the Activity Log and the Job Monitor is incorrect.

When VMware-based virtual machines contain independent disks and raw device mappings that are configured in the physical mode, Arcserve skips these volumes during backup jobs. However, the fact that the volumes were skipped during backup jobs is not recorded in the Activity Log.

When the process of retrieving the used data blocks on VMware-based virtual machines using VMware changed block tracking (CBT) fails, the agent currently cannot reset CBT when the virtual machine contains snapshots. To correct this behavior, remove the snapshot manually so that you can reset CBT. VMware is a aware of this problem and is working to provide a solution to this behavior.

File mode backup is not supported if a VM contains the basic disks on the UEFI partitioned disks.
This is a limitation of VMware VDDK. Convert to dynamic disks.

Restorimg C:\ volume from rawif session to the original location fails for Windows 2012 and 2012 R2. Use Recover VM to restore.

VMAgent installation is not supported on x86 servers with the Arcserve Backup r17 release. However if you choose any other agent and perform a remote installation or create a response file, the local installation option is enabled. Close the setup windows and try again.

10.14 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:
1. On the remote system running the SAP option, go to the Windows\System32\drivers\etc folder.
2. Open the hosts file.
3. Add host/IP map as below:
```
<IP address> machine_name
```
  where <IP address> is the IP of the backup server machine
4. Save and close the hosts file.

When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored. This is because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.

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.

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

If a SAP backup job fails on the Arcserve Backup server (for example, a media error occurs), the SAP backup utility (for example, brbackup) will stop responding and eventually time out. The backup utility behaves in this manner because it cannot detect the status jobs on the backup server. When you encounter this problem, terminate the SAP backup manually, correct the problem, and then resubmit the backup.

This option does not support 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.

If you register a data mover server with a different primary server after you install and configure option, you must reconfigure the option using the sapsetup script. If you do not reconfigure the option, jobs submitted through the affected data mover server will fail.

Optimize Restore functionality is not supported for the Enterprise Option for SAP R/3 for Oracle.

Compare Media to Disk functionality is not supported on Enterprise Option for SAP R/3 for Oracle sessions.

With this option you can back up data stored on UNIX and Linux agents to deduplication devices. However, the option does not support compressing the data during the backup.

The restoration of SAP R/3 agent databases from the Arcserve Backup Restore Manager is not supported. However, you can perform this restoration by using the "brrestore" module from the Command Line. The brrestore module is used to restore database data files, control files, and offline redo log files.

By default, the network option parameter "tcp_nodelayack" on AIX platforms is set to 0. This default setting may cause restoring SAP data from primary and member server to be slow (less than 10MB/min).
To remedy this problem, change the setting of tcp_nodelayack to 1 using the following command:
```
no -o tcp_nodelayack=1
```

10.16 Known Issues for the Disaster Recovery Option

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

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:
- 8355
- 17204
- 17207
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 Boot 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 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.

When performing remote disaster recovery from MSD/FD that includes certified NIC drivers on 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:
1. Manually modify the asr.sif file on MSD:
  1. Open the asr.sif file using a text editor.
  2. Locate the section [INSTALLFILES]:
    4=1,"CADRIF","\Device\Floppy0\","oem3.inf","%SystemRoot%\inf\driver.inf","CA"
    
    5=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%SystemRoot%\Driver Cache\driver.sys","CA"
    
    6=1,"CADRIF","\Device\Floppy0\","vmware-nic.cat","%SystemRoot%\Driver Cache\driver.cat","CA"
    
    7=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%SystemRoot%\Driver Cache\driver.dll","CA"
  change these files to %TEMP%:
  
  4=1,"CADRIF","\Device\Floppy0\","oem3.inf","%temp%\driver.inf","CA"
  
  5=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%temp%\driver.sys","CA"
  
  6=1,"CADRIF","\Device\Floppy0\","vmware-nic.cat","%temp%\driver.cat","CA"
  
  7=1,"CADRIF","\Device\Floppy0\","vmxnet.sys","%temp%\driver.dll","CA"
  
  Do NOT change these files or you will be unable to perform DR:
  
  1=1,"CADRIF","\Device\Floppy0\","DrLaunch.exe","%SystemRoot%\system32\DrLaunch.exe","CA"
  
  2=1,"CADRIF","\Device\Floppy0\","DrLaunchRes.dll","%SystemRoot%\system32\DrLaunchRes.dll","CA"
  
  3=1,"CADRIF","\Device\Floppy0\","DrLaunchEnu.dll","%SystemRoot%\system32\DrLaunchEnu.dll","CA"
2. Manually create a file called winnt.sif on MSD and open it in a text editor, for example, Notepad.
3. Write the following text into the winnt.sif file:
  [Data]
  
       MsDosInitiated = 0
       UnattendedInstall = Yes
  
       [Unattended]
       OemPreinstall = YES
       OemPnPDriversPath = TEMP

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 on various x64-based computers running Windows Server 2008 R2 (for example, Dell GX755 desktop), Arcserve Backup may not be able to detect file system devices connected to remote computers running Windows Server 2003.
  To remedy this problem, 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:
1. Before you load your MSD during the DR process, go to Utilities, Run and type diskpart. Press Enter. This launches the diskpart utility.
2. Type list disk to detect all disks attached.
3. For each disk, use the following command to see if it is offline or read-only:
```
select disk 1
```
```
detail disk
```
4. If a disk is offline, use the "online disk" command to bring it online.
5. 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:
1. Press F8 when the startup menu appears, use the arrow keys to select the safe mode option, and then press ENTER.
2. Click Start, Run, and type 'cmd', and then click OK.
3. 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:
1. Add a DWORD key: IsResDskQuota to the following registry:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServeBackup\ClientAgent\Parameters
```
2. Set parameter to 1
3. 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:
1. 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.
2. From server B, manually start the SQL Service.
3. 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.

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.

Arcserve Backup does not support restoring 4KB sector disk data to 512 bytes of disk when you use the traditional disaster recovery method. As a workaround, you can generate a bootable CD image to restore the disk from the WinPE system.

Arcserve Backup r17 does not support the traditional Disaster Recovery method on Windows 8 and Windows Server 2012. Some traditional Disaster Recovery methods are Machine Specific Disk (MSD) and bootable Arcserve CD. When you create MSD on a Windows Server 2012 computer, you are blocked from the utility. By default, WinPE is used to perform a disaster recovery.
When you use WinPE to perform a disaster recovery, there is a possibility that you cannot connect the backup server or the disaster recovery information (DRIF) location through the network. As a work-around, perform one of the following options:
- Copy the ASBU_Home\DR\PrimaryServerName\AgentName folder from the primary server to a USB drive. Run Disaster Recovery and select DRIF from the USB drive.
- Copy the ASBU_Home\DR\PrimaryServerName\AgentName folder from the primary server to an MSD. If the MSD does not have enough space (1.44 MB) to save the files, do not copy the DRV folder.

When Disaster Recovery completes and the system restarts, if the Disk Quota is not applied to the volumes correctly or the file "diskquota_info.inf" exists then it is required that you set the following registry key and restart the Arcserve Universal Agent service.
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Arcserve Backup\ClientAgent\Parameters
Create a new key (IsResDskquota) of type DWORD and set the value to 1.
Name: IsResDskquota
Type: DWORD
Value: 1

10.17 Known Issues for Dashboard

The following issues related to Dashboard are known to exist in this release:

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:
1. Click Start, Control Panel, Administrative Tools, Services to open the service control manager.
2. Right-click the Arcserve Backup Universal Agent and choose Properties from the shortcut menu.
3. On the Log On tab, click This Account and enter the domain name/user name, followed by your password. Confirm the password and click OK.
4. Click OK to clear the confirmation message.
5. Right-click the 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.

If you upgraded your Arcserve Backup server and agent nodes from a version prior to release 12.5, please note the following behavior with Dashboard reports:
- If you have run encrypted backup jobs for some nodes prior to upgrade, those nodes are displayed on the Nodes Encryption Status Report as "Nodes without encrypted sessions".
- If you have run encrypted backup jobs for some nodes prior to upgrade, those tapes are displayed on the Tape Encryption Status Report as "Tapes without encrypted sessions".
- If you have run full node backup jobs for some nodes prior to upgrade, those nodes are displayed on the Node Disaster Recovery Status Report as "Nodes not Eligible for Disaster Recovery".
- If you have run backup jobs for some remote nodes prior to upgrade, those nodes are displayed on the Agent Distribution Report as "Version undetected".
- For the Agent Distribution Report to display accurate information after upgrade, you should browse/expand the nodes one time in the Backup Manager or run another instance of the same job to correctly update and display this information.
- If you have run backup jobs for some nodes to tapes or file system devices prior to upgrade, the Data Distribution on Media Report will not display any information.
- If you have run backup job for some nodes prior to upgrade, the Deduplication Status Report will display 0 in the 'Raw Backup size' column of the drill-down report.
- If you have run backup jobs for some Virtual Machines through VMware Consolidate Backup prior to upgrade, the Virtualization Most Recent Backup Status Report and Virtual Machine Recovery Points will not display any information.
After upgrading, run another instance of the same job to correctly display this information.

The Memory Report may display slightly lesser memory size values for Virtual Machine nodes running Arcserve Backup Agent for Virtual Machines that are backed up through Microsoft Hyper-V. This is a known Microsoft issue because the Virtual Machine Management needs a little overhead for each virtual machine.

When you create a Dashboard email schedule on the Arcserve Backup primary server running on a Windows Server 2008 operating system, the scheduled email from the Dashboard may not send the reports to the recipients specified in the Dashboard email schedule. This problem occurs because of an issue with Microsoft .NET Framework 3.5 SP1 and can be resolved by applying the appropriate hot fix on the primary server machine. You can download the hot fix directly from the Microsoft downloads website. For x86 and x64 systems, search for KB959209.

During installation of this release of Arcserve Backup on Windows 2008 operating system, there may be cases where the automatic installation of .NET Framework 3.5 SP1 fails, resulting in a blank screen when you launch Dashboard. If this occurs, you need to manually install the .NET Framework 3.5 SP1 and also need to reboot your system. You can install a patch from Microsoft to address this problem (search for patch 947821).

If you performed a backup of a node using the command line (ca_backup), Arcserve Backup Dashboard may not display any data in the corresponding reports. To view the data for this node, perform the following steps:
1. Add the same node to the Backup Manager GUI by right-clicking on the Windows Systems objects and choosing Add Machine/Object from the shortcut menu.
2. Expand the node in the Source directory tree by giving administrator or equivalent user credentials.
The node now displays data in the Dashboard reports.

The Dashboard Client Node Software Report cannot retrieve the values for certain optional properties, such as install date.

Dashboard SRM cannot detect same versions of the 32-bit and 64-bit Oracle installed on the same 64-bit production server.

The Client Node Software report does not display the backup status or time for jobs submitted with the Agent for Informix. To avoid this problem, add the node to the GUI using the real host name instead of the IP address.

The Dashboard reports that contain line charts may display discontinued lines because of no action occurring to produce data for that specific time period.

When you perform a Disk Level Backup on the Client Agent; the Client Agent locks the disk and the volumes that are related to that disk. This results in the dashboard and other applications with having no ability to access the disk level details for that specific disk. The Dashboard can run the probing and can display the data after the backup completes.

When you perform a Physical Disk/Volume Level backup of a node using the client agent, the client agent applies a lock on that particular disk/volume. This results in the SRM Probe with no access to the disk/volume level details for that specific disk. Therefore the dashboard does not display data for that node. When the backup completes, manually run the SRM Probe from the Dashboard to display the data.

Currently in this release, Dashboard Reports do not support Microsoft Exchange Server 2013 and Microsoft SharePoint Server 2013 applications.

10.18 Known Issues for the Arcserve Backup Global Dashboard

The following issues are known to exist in this release:

If a branch site is in the process of performing a full/incremental data synchronization with the central site, and the network connection breaks between the branch site and the central site, the status of the branch site in the Central Manager UI will remain in the same state ("Full/Incremental synchronization in progress") until the network link is up again. When the network link is up, a synchronization retry will be attempted based on your pre-configured settings for that branch site

When you create a Dashboard email schedule on the Arcserve Backup Central Primary Server running on a Windows Server 2008 operating system, the scheduled email from the Dashboard may not send the reports to the recipients specified in the Dashboard email schedule.
This problem occurs because of an issue with Microsoft .NET Framework 3.5 SP1 and can be resolved by applying the appropriate hot fix on the primary server machine. You can download the hot fix directly from the Microsoft downloads website. For x86 and x64 systems, search for KB959209.

If you have an existing Global Dashboard environment, with a Central Primary Server and at least one remote Branch Primary Server, and you are upgrading Arcserve Backup from r15, r16\r16.5 SP1, to r17, we recommend that you upgrade the Central Primary Server first, and then each of the Branch Primary Servers.

For Global Dashboard, the Central Primary Server does not support being installed on a Microsoft Active Directory domain controller machine.

If a new branch site is registered and synchronized to the central site, you must re-launch Arcserve Backup Dashboard for the reports to display the data from the new branch site. Until Arcserve Backup Dashboard is re-launched, data from the new branch site will not be included in any Dashboard reports and the branch site name will not be included in the branch filter options.

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

Restore jobs fail and do not report a message in the Activity Log when you use the Restore by Backup Media restore method. Use the Restore by Image method to restore the data.

The Restore Manager window cannot display file-level details of backup sessions under the following conditions:
- The data was backed up using a previous release of Arcserve Backup.
- Staging was enabled for the backup.
- Data migration job for the backup to the final destination media was submitted AFTER you upgraded to this release.
To remedy this condition, open the Restore Manager and browse to the sessions that migrated after you upgraded to this release of Arcserve Backup. You must then execute a Merge job on the migrated sessions.

When you submit more than one Image Option restore job using Restore by Session, only one job can complete successfully.

The Image Backup job fails with E11114 error when a nested VHD volume exists. The reason why the job fails is because VSS is not supported for the nested VHD volume. Microsoft is aware of this issue, see the following link for more details: https://msdn.microsoft.com/en-us/library/aa382650(v=vs.85).aspx.

10.20 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:
1. Perform Restore by Session.
2. Submit a job to restore the full session
3. Submit another job to restore the differential session to the same directory as the previous restore.

Filters are not supported on restores.

The following items relating to the NAS Restore backup sessions are not supported in this release:

Restore by Query

Restore by Tree - 'Go to' function only
Note: To get to the 'go to' button, select Search to search for a file and click 'go to'.

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

10.22 Known Issues for the Tape Library Option

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

The option does not support multistreaming. If you enable multistreaming, you must install the Enterprise Module Option.

If you receive the error message "Windows - No Disk, There is no disk in the drive. Please insert a disk into drive \Device\HardDiskx\DRx," you must exclude the tapeeng.exe process from scanning by eTrust. To exclude the tapeeng.exe process from scanning, perform the following procedure:
1. In the Realtime Monitor Options dialog of eTrust, click the Filters tab.
2. On the Filters tab, in the Exclusions group box, click the Process button. The Exclude Processes dialog opens.
3. In the Exclude Processes dialog, enter tapeeng.exe in the Enter a process name field and click Add. The tapeeng.exe process appears in the List of Excluded Processes.
4. Click OK to close the Exclude Processes dialog and click OK to exit the Realtime Monitor Options dialog.

Tape Engine may corrupt the device view structure of RSM. Some storage devices cannot be used by the Tape Engine and RSM simultaneously. To restore the device view structure of the removable storage service, stop the Tape Engine and restart the removable storage service.

If you want to import a cleaning tape with a barcode prefix that is not CLN, or has no barcode, choose one of the following tasks to avoid unrecognized media errors:
- Open Library Properties, select Clean by Slot, add a slot into Clean Slots. Import the cleaning tape into the Clean Slot.
- Open Library Properties, select Clean by Barcode, enter the barcode prefix or whole barcode of the cleaning tape. Import the cleaning tape into any slot of the tape library.

Arcserve Backup cannot automatically disable Removable Storage Manager (RSM) devices on 64-bit systems. The Tape Engine is automatically started after Arcserve Backup is installed and the Tape Engine Auto Configuration cannot configure RSM devices correctly. Warning message W6978 appears in the Activity Log. If you are running Arcserve Backup on a 64-bit system, you must manually disable backup devices in RSM to avoid this problem. On a 64-bit system, you will not be able to do this using the Arcserve Backup Manager Console because it cannot display any RSM-controlled devices for enabling or disabling.
If you are running the Arcserve Backup Manager Console on a 64-bit system, you must disable RSM so that Arcserve Backup can use the device. To disable RSM, perform one of the following:
- If Arcserve Backup has already been installed:
  - Stop the Tape Engine. Disable RSM-controlled devices using the RSM Computer Management utility. Restart the Tape Engine.
- If Arcserve Backup has not yet been installed:
  - Attach the library to the server. Reboot the server. Disable RSM-controlled devices using the RSM Computer Management utility. Install Arcserve Backup.

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

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

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.

10.25 Known Issues for the Arcserve Backup Infrastructure Visualization

The following issues related to Infrastructure Visualization are known to exist in this release:

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.

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

10.27 Known Issues for Agent for Mac

Issue observed in lower versions from: Mac 10.9.x. After successfully installing the Mac agent, caagent services are in the Stop state. You need to start the services manually using the command "caagent start".

11.0 Limitations

The following limitations are known to exist in this release:

Arcserve Base Component Related

Synthetic backup job fails to run on single device when the session number exceeds 6,5535. This limitation is caused due to design and implementation considerations.

As a workaround, create a new device for subsequent synthetic jobs when the session number exceeds 6,5535.

Arcserve Exchange Granular Restore (GRT) Utility Related

The current version of the Exchange GRT Utility has the following limitations:
- While processing dirty shutdown, database storages may not be restored to the topical condition.
- Messages in the Outbox folder are not restored if they are not synchronized with the server.
- Simultaneous recoveries are not supported.
- Simultaneous running of more than one instance of the product is not supported.
- Encrypted emails are not restored.
- Messages larger than 64MB are not supported.
- Windows 2000, 98, ME, and 95 are not supported.
- Recovery of delivery receipts and non-delivery reports is not supported.
- The Exchange GRT Utility does not support the Run as different user mode.
- Using wild cards at the beginning of a word in search is not supported

Limitation and boundaries for optimal recovery and search
- Usage of the Exchange GRT Utility is optimal for datasets that do not exceed:
- Database size: 2TB
- Mailbox size: 100GB
- Number of messages in the database: 2,000,000
- Number of mailboxes in the database: 2,000
- Number of messages in one mailbox: 100,000

Limitations for search in attachments content
- Search in attachments does not work for:
  - Text contained in embedded OLE objects, WordArt, smart objects, charts, documents metadata (author, comments, tags, and others)
  - Marker symbols in lists (numbered or bulleted)
  - Text in a header/footer
  - XLS/XLSX: number values

Injection limitations
- Injection will not be supported for Exchange Server 2003 and earlier versions. These versions do not support EWS.
- Archived mailboxes (and items from such mailboxes) are not exported to a live Exchange Server.
- Photos of contacts are not exported to original live mailbox in Exchange Server 2007.
- Emails with embedded images are displayed with an attachments icon after exporting to a live Exchange Server 2007.
- Creation time and modified time are not restored.
- Attached items inside attached messages are not restored to a live Exchange Server 2007.
- Cross-domain export into original mailbox is not supported.
- Contact groups and meeting requests cannot be exported to a live Exchange Server 2007 instances. Use export through PST for such items.
- Missing sent date is exported as current date/time to a live Exchange Server.
- Mailboxes cannot be created from Exchange GRT, i.e. automatically at restore time. To restore a mailbox, an empty mailbox must be created in advance using the standard Exchange Server administration tools. In existing mailboxes folders and individual messages can be created without any additional administrative actions.
- It is possible to rename/delete folders in the attached mailbox only within one program session.

Arcserve High Availability Integration with Arcserve Backup

Arcserve Backup r17 only supports adding Arcserve Replication and High Availability of the r16.5 release under the Protection and Recovery menu from the Arcserve Backup Manager.

Arcserve Backup Web Service

After installing Arcserve Backup r17, the Arcserve Backup Web Service cannot be modified on the member server when using “Bconfig –C”. This feature is not implemented on the member server. However, you can run the following command to update the Arcserve Backup Web Service configuration:
X64: C:\Program Files (x86)\CA\ARCserve Backup\Bin

X86: C:\Program Files\CA\ARCserve Backup\Bin

ChangeProtocol.bat https <<port number for Web Service>>

12.0 Issues Fixed

This section describes the test fixes included in the current release of Arcserve Backup.

12.1 Agent for Hyper-V

The following table lists the test fixes for the Agent for Hyper-V:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000089	AE0605 DiskItem Microsoft Hyper-V VSS Writer is spread across multiple volumes.
T245871	AW0004 for System Files if there is CSV Volume
T245911	Snapshot files remain after RecoverVM Raw/If
T245914	Dump is created in Hyper-V Backup of Cluster
T245917	Hyper-V Restore Links AVHDX File to Drive
T36A834	Excessive Active Ports SQL Server
T36A846	SQL Log Shipping Issue
T4C4128	E3987 Child Job Crash
T4C4136	Hyper-V Backup Fails With No Error
T4C4138	E3392 AW0002 for Huper-V VM
T51H077	IN-E3392-Tcp Reconnection Timeout This fixes the following registry key: PATH: [HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters Key Name: BackupVHDUsingVHDRead Key Type: DWORD Value: 0
T51H096	HYPER-V VM Not Populated in DB
T51H116	HYPERV Makeup Job Problem Wrong System Backup
T51H141	VM not reboot after restore
T56P024	Agent crashed for backup of Hyper-V VHD VM
T58E234	HYPER-V Restore AVHDX
T5OV088	Remove AW0550 for non-Windows VMs on Hyper-V
P00000160	HyperV VM boot fails after recoverVM if VM had checkpoint when backed up

12.2 Agent for Lotus Domino

The following table lists the test fixes for the Agent for Lotus Domino:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T245878	Transaction Log Files Not Displayed In Restore By Session
T36A872	Disable Backing Up DAOS Files The following registry changes are required for this fix: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CAARCserveBackup\DSAgent\CurrentVersion\agent\dbanotes@<<DOMINO INSTANCE NAME HERE>> Key Name: SkipBackupDaosObjects Key Type: DWORD Value: 1
T58E194	Arcserve Manager GUI will crash when submitting a Lotus Notes Backup Job.
T58E237	Domino Agent is not Restoring

12.3 Agent for Microsoft Sharepoint

The following table lists the test fixes for the Agent for Microsoft Sharepoint:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T36A803	WIN-Sharepoint RESTORE ORIGINAL DATE
T36A831-T36A842	Sharepoint Backup Fail
T36A873	WIN-SQL DEADLOCK CAUSES SHAREPOINT BACKUP
T36A876	SHAREPOINT WIN-INCLUDE SECURITY OPTIONS MISMATCH
T5Y4027	SHAREPOINT BACKUP NOT WORKING

12.4 Agent for Microsoft SQL Server

The following table lists the test fixes for the Agent for Microsoft SQL Server:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T36A845	Exclusive Access to SQL Account
T36A867	VIRTUAL SQL NODE DISPLAYS WRONG SQL INSTANCES
T36A871	Support for Microsoft SQL 2014
T36A879	SKIP TLOG BACKUP WHEN DB IN SIMPLE MODE

12.5 Agent for Open Files for Windows

The following table lists the test fixes for the Agent for Open Files for Windows:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #

Description

T5Y4029

WIN-E12502 HAPPENS WITHOUT CHOOSING VSS

This fix requires the following registry changes:

PATH: [HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCSERVE BACKUP\ClientAgent\Parameters]

Key Name: UseVssForOpenFiles

Key Type: DWORD

Value: 0 if user does not want to use VSS

1 if the product uses the VSS for the backup

T5Y4034

WIN-OFA BUGCHECK

12.6 Agent for Oracle

The following table lists the test fixes for the Agent for Oracle:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T245952	Oracle Agent Backup sometimes fails with E8535
T36A864	Skipping Archive Log Backup
T51H086	Recovery of Oracle Database

12.7 Agent for Oracle on UNIX and Linux

The following table lists the test fixes for the Agent for Oracle on UNIX and Linux:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T245842	AE360144 If client is connected by only alias
T58E193	Oracle Incremental Backup Fail Large DB
T5DQ154	AIX-Cannot Browse Oracle
T5DQ161	LNX-Oracle Restore Failed

12.8 Agent for VMware

The following table lists the test fixes for the Agent for VMware:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000018	Disk sequence is not correct when VMware Agent Raw-IF Backup with same VMDK name (VM Agent)
T00000022	VMware VM file level restore fails with error AE0559
T245880	AE0060 for File Level Restore of UEFI VM requires the following registry change: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters Key Name: StopIfVolumeMapFail Key Type: DWORD Value: 0 (default is I: Job fails with AE0521 in this case)
T4C4124	Missing "Local Option" menu after executing "Microsoft Hyper-V Configuration Tool"
T4C4143	AE0312 during restore from Raw-IF Backup
T4C4149	VM not listed in recovery VM window
T51H076	VM-Restored failed
T51H085	Arcserve Backup of VM failed with error message "AW0551 Unable to map the VM volume to a VM disk image file." If the password of backup user in vCenter or ESX server has a character that is not ANSI.
T51H089	Recovery of VM failed - AE0579
T51H091	VDs Port Group Displayed Wrong
T51H092	Make up job does not back up all VM systems
T51H118	Populate VM with new UUID not updated
T51H147	VM not seen in restored GUI
T51H151	VM not seen in restored GUI
T55W005	Disable Overwrite VM
T57M002	Crash in VMware VM Population Tool
T57M005	Failed to clear archive bit in VM Inc Backup
T57M006	Snapshot not deleted
T57M007	Windows\Temp path is filled up with temp files after Raw-IF Backup
T58E209	Hyper-V VM cannot boot after Recover for Raw-IF Backup with snapshot for Windows Server 2012 R2
T5Y4038	CAAGSTAR.EXE crashes

12.9 Arcserve Backup Integration with UDP and D2D

The following table lists the test fixes for the Arcserve Backup Integration with UDP and D2D:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
P00000059	E3392 with caagstart.exe crash in UDP lite integration backup
P00000107	E3392 with caagstart.exe crashes in UDP lite integration backup
T00000078	Disable VSS Backup when "Use VSS" unchecked in global option
T00000120	File Timestamps are GMT in restore manager for lite integration backup data
T00000146	Backup job fails after OnDemand Catalogs generation for UDP/D2D session
T245894	WIN-RESTORE FROM UDP/D2D OR VM AGENT CORRUPTED
T245896	WIN-RESTORED FILES CORRUPTED FROM D2D AGENT BACKUP
T245907	E12002 for UDP Lite Integration Backup
T245923	UDP LITE INTEGRATION: RESTORE RAW SESSION FAIL
T245927	ASDB Prune and Protect Jobs License Error
T245934	License Error Starting UDP Integration Job
T245940	UDP Raw Session Restore Fails with AE0069
T245943	LICENSE ERROR FOR 3OL5 IN UDP INTEGRATION BACKUP
T4C4140	Security dialog is not shown for RPS job
T4C4122	CONFIGURABLE TEMP PATH FOR D2D LITE INT BKP.
T55Z050	Unable to add D2D Node under D2D Proxy Node
T55Z059	Universal Agent crashes when one HBBU VM name exceeds 34 characters
T55Z064	Universal Agent crashes while browsing RPS server
T55Z065	UDP Lite Integration backup crash on agent
T55Z066	Restore D2D raw session job crashed on agent side
T55Z069	LIGHT INTEGRATION BACKUP DATA CORRUPTION
T55Z078	Job History Detail as NA for Lite Integration
T55Z079	LITE INTEGRATION JOB FAILED WITH E3392 ERROR
T55Z081	LITE INTEGRATION BACKUP FAIL WITH HTTPS
T55Z082	BROWSE UDP RPS SERVER FAILED
T55Z083	Browse or Backup RPS Server Failed
T55Z086	Lite Integration Backup failed
T56P003	Generate Catalog on Demand failed
T56P019	FAILED TO LOGIN TO RPS SERVER
T56P020	BACKUP D2D INTEGRATION REQUIRE UDP LICENSE
T56P022	Restore UDP Virtual Machines fail
T56P026	INCR/DIFF INTEGRATION BACKUP NO SKIP RPS FILES The following registry is required: PATH: HKEY_LOCAL_MACHINE\SOFTWRE\ComputerAssociates\CA\ARCserve Backup\ClientAgent\Parameters\IncrDiffNoSkip RPSFiles = 1
T56P028	UDP SESSION SKIPPED BY DIFF BACKUP.
T56P034	ASBU-RPS DUPLICATE NETBIOS NAME.
T56P036	UNIVERSAL AGENT SERVICE CRASHED.
T58E206	D2DLITE LITE INTEGRATION FAIL E3392
T58E217	WIN-D2DLITE LITE INTEGRATION FAIL E3392
T58E235	UDP File Level Restore Failed-E8522
T58E236	Unable to submit Lite Integration Mux Job
T5OV090	ASBU LITE INTEGRATION BACKUP JOB FAILS.
T5OV092	ARCSERVE UDP LICENSE SUPPORT IN ARCSERVE BACKUP

12.10 Base

The following table lists the test fixes for the Arcserve Backup Base Product:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000006	Want to see staging time in "Backup Time" of DM Session. The following registry is required: PATH: HKEY_LOCAL_MACHINE\Software\ComputerAssociates\CA ARCserve Backup\Base\Database Key Name: CopyDSTimeToDMRecord Key Type: DWORD Value: 1
T00000010	The fix corrects the crash problem of UDP RPS integration with Multiplex backup jobs
T00000014	Manager GUI crashes when trying to submit a restore job.
T00000015	Job history shows incorrect MB size for non unicode agent
T00000016	Need to run delayed reclamation through expedited reclamation is selected. This fix requires the following changes: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\ComputerAssociates\CA ARCserve Backup\Base\TapeEngine\CONFIG Key Name: ForceDelayedReclaim Key Type: DWORD Value: 1
T00000026	preflight check is failing
T00000028	Data migration job failed with dedupe internal error 16647
T0000054	Master job will show as failed, even all the child jobs shown succeed.
T00000073	AD restore utility does not display objects in AD database file
T00000101	Tapecopy Span Tape problem
T00000109	Need to run delayed reclamation through expedited reclamation is selected. This fix requires the following changes: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\ComputerAssociates\CA ARCserve Backup\Base\TapeEngine\CONFIG Key Name: ForceDelayedReclaim Key Type: DWORD Value: 1
T00000111	Catalog .Db always back up when Arcserve install Dir included in Backup Source
T00000122	Tape engine crashes when restore data from a dedupe device
T245873	Migration jobs starts soon after staging even scheduled to run at a specific time
T245874	Disks are deselected when opening copy job
T245888	Rotation job ignores Exception day
T245895	Media Records Remain After Pruning
T245898	Tapecopy -Q Records E63638 to Activity Log
T245903	Force job status complete when W29893 occurs. To finish the synthetic job in the complete status when W29893 occurs and run the next job as a synthetic full backup job, the following changes to the registry is required: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup Key Name: ForceCompleteAfterW29893 Key Type: DWORD Value: 1 or greater (default is 0)
T245915	W29879 occurs after changing Dedup Purge Policy
T245916	Tape engine crash when multistream job running
T245921	CA_DEVMGR fails to create remote FSD
T245924	Backup succeeds through DDD data is truncated
T245925	WIN-JOB DESCRIPTION IS TRUNCATED
T245928	ca_devmgr fails to create remote FSD
T245929	Backup succeeds through DDD data is truncated
T245942	Group is unusable if one FSD is offline
T245945	ca_restore doesn't stop after job finished
T245953	Backup size is logged wrongly to 1.10 GB
T36A838	Media is not picked up from scratch set
T36A840	Error message for make up job include in successful alert message
T36A843	Manager crash on job history
T36A861	Dirwatcher cannot change archive attribute
T36A878	Backup hangs when trying to get disk quota user info in MS Dskquota.dll. Even disk quota is disabled on the volume.
T4C4131	Incorrect backup scheme picture for staging and dedup will be shown if you modify an existing backup job.
T4C4134	Catalog files not created
T4C4135	Driectory Structure Browse Gets into Loop for "Application Data" folder
T4C4141	Arcserve Dedupe reclaim ratio set to 10
T4C4144	Data migration to the cloud device fails with inaccessible device
T4C4145	E3392 on million files access
T4C4148	Fail to create cloud device for Eu_Ireland
T51H088	VTL Eject source tape in Tapecopy
T51H093	Makeup job always generated
T51H097	Job waiting for target
T51H112	Tape engine crash on Sis.Dll
T51H115	Arcserve Data Migration job is slow
T51H121	Dedup Purge Policy not updated
T51H122	Media not assigned to save set pool
T51H123	Data migration job fails with E3843
T51H127	E3404 - unable to open catalog file
T51H129	Job hangs waiting for target
T51H132	Media error with data migration make up job new tape. The following registry requires changes: PATH: [HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Tasks\Backup] Key Name: MakeUpJobNoExcludeOfTape Key Type: DWORD
T51H133	MUX job not eject tape
T51H135	Tape drives are not released
T51H146	DM-Double Tapecopy Problems
T51H157	WIN-LIBRARY NOT SEEN IN VIRTUAL SERVER
T55W002	Displays wrong results when searches folders from Restore by Tree and Restore by Query
T55W004	ca_backup does not return and lost response with port conflict
T55Z005	System state backup fails
T55Z037	Master job crashed on spanning tape
T55Z041	Rotation job skip 1 day
T55Z042	Overwrite media name date/time After applying this fix, Arcserve Backup will revert back to formatting the tape with the original name. If you want the media to be formatted with date/time, set the following registry: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup X86: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup Key Name: UseBlankMediaName Key Type: DWORD Value: 1
T55Z061	Custom schedule double tape copy name incorrect
T55Z073	Duplicated Migration Jobs are created for a Multistream - GFS-Staging Job.
T55Z075	Restore by Tree view display empty calendar
T55Z077	Alert not process attachment greater than 1 MB
T55Z080	Mergecat crash on stack overflow
T55Z088	Tape format to date time for custom rotation
T56P001	Media records display limited from GUI
T56P012	Member Server Agent Deploy Problem
T56P023	Tape Management Label Problem
T56P030	Agent deploy limits hosts name to 15 characters
T56P033	Incorrect job history in GFS job
T57M003	ca_backup run forever
T57M004	Global Options Screen shows bigger in size not displaying OK\Cancel buttons
T58E166	Advanced Report Error
T58E177	Duplicate serial numbers in the Arcserve database with spanned multiplexing jobs
T58E184	Staging job issue multistream
T58E185	E8535 Backup Windows issue
T58E192	Do not save session password in DB
T58E210	E3555 All licenses used up during backup
T58E219	Migrate to Amazon S3 get E6008
T58E221	Multistream not selectable and grayed out
T58E226	Error code W29900. The following changes to the registry is required: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup Key Name: KeepStatusForIncJob Key Type: DWORD Value: 1
T58E239	Add more options for ca_dbmgr
T58M001	Staging job rotation scheme fail - E53533
T58M004	Utilities Specific Filter Invalid
T5Y4016	Dedup.Cat files are purged
T5Y4020	Command Line Command - Cherase not working
T5Y4021	Alert - job log garbled
T5Y4031	CA_DEVMGR - CREATEFSD Fails 8 Char for label
T5Y4040	File is not selected when performing a search in Restore by Tree

12.11 Client Agent for Linux

The following table lists the test fixes for the Client Agent for Linux:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T5DQ130	Lnx-Backup Failed on AE280285
T5DQ138	Login Failed on FreeBSD 9.2
T5DQ145	Lnx-Filter Logging: When a filter is set to exclude lost and found and debug value to more than 2, "Use supplied Regular Expression Disabled" is printed for each folder. With this fix applied, the above message will be logged in the beginning of the job once.
T5DQ156	NSS Support No Atime
T5DQ157	Lnx-Diff_Incr Use Ctime
T5DQ164	CENTOS 7 Support
T5DQ166	Oracle Enterprise Linux and SLES SUPPORT

12.12 Client Agent for Windows

The following table lists the test fixes for the Client Agent for Windows:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000017	Merge failures when the catalog size is greater than 4GB
T00000032	Backup failures with Errors E8535
T00000074	Creating dump files in Universal Agent installation folder after completion of backup job.
T00000154	E3987-A child job is detected, crashed
T245866	File system corrupted by restoring raw backup
T245875	AW0004 for junction points on Windows2008. The following registry requires changes: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters Key Name: IgnoreW0224 Key Type: DWORD Value: 1 (default is 0)
T245936	W29893 for a file which is filtered out.
T245892	Backup is slow, if lots of files filtered out
T4C4121	Universal Agent crash on primary server
T55Z026	Modify job get buffer too small error
T58E182	Error E3987 a child job crash
T58M002	Client Agent Crashes During DiskEnum Using WMMI
T58M007	Remote restore fail with E8522
T5OV087	Disable crash dumps or configure dump location This fix provides the following registry options: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\UniversalClientAgent\Parameters Key Name: DisableCrashDump Key Type: DWORD Value: 1 Configure crash dump location: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\UniversalClientAgent\Parameters Key Name: CrashDumpPath Key Type: String
T5OV091	WIN-UNIVERSAL AGENT PROC CRASH DUMP CONFIGURATIONS This fix provides options to configure alternate path for crash dumps and to disable crash dump generation. PATH: HKEY_LCOAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\UniversalClientAgent\Parameters Key Name: DisableCrashDump Key Type: DWORD Value: 1
T5Y4005	Restore dynamic disk offline
T5Y4010	File size set to 0 Hard Link
T5Y4041	Restore with incorrect hardlink

12.13 Dashboard

The following table lists the test fixes for the Dashboard:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000052	Unable to generate reports when field "media.media location"
T00000085	Dashboard report shows service pack as 0 for SP1 agent.
T36A863	Total protection size report do not show all full backup server list.
T55Z008	Universal Agent Crash on SRM Probe
T55Z070	Arcserve Central Protection management auto incremental synchronization hangs.
T58E183	The Volume Trend Report in the Dashboard is displaying incorrect information about the drive sizes.
T58E212	Dashboard communication foundation ends
T58E215	Dashboard sync not working

12.14 Disaster Recovery Option

The following table lists the test fixes for the Disaster Recovery Option:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
P00000060	This fix corrects the problem where netstat does not work after recovering from DR.
T00000108	DR fails to read data from IBM USB3 RDX device
T245883	RECOVERY PARTITION DISAPPEARS AFTER DR
T245919	PEDR DOESN'T RECOVER [EFI PARITION]\EFI\BOOT
T245935	PEDR denies to replace Refs sessions
T36A862	WINPE BOOT KIT ADD DRIVERS
T36A868	After upgrading ADK from 8.0 to 8.1, user cannot inject driver files to WinPE DR image via "Create Boot Kit Wizard".
T36A877	DR Information is not updated correctly
T56P002	BOOT KIT WIZARD ERROR IN EXECUTE MODE
T5LE237	Arcserve Backup Supports Disaster Recovery with 4K Disk
T5Y4018	WINPE BOOT KIT ADD DRIVERS
P00000106	Supports Disaster Recovery with 4K DISK

12.15 Enterprise Option for SAP on UNIX and Linux

The following table lists the test fixes for the Enterprise Option for SAP on UNIX and Linux:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T36A850	SAP Linux DB Restore Fail

12.16 Global Dashboard

The following table lists the test fixes for the Global Dashboard:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #

Description

T55Z035

Command line argument for Full Sync

Use "Scheduled Tasks" to set up a schedule for auto synchronization from C:\Program Files (x86)\CA\ARCserve Backup\GlobalDashboard\BranchCFG.exe.

The following registry requires changes:

PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\GlobalDashboard

Key Name: DWORD

Key Type: DWORD

Value: 1 (runs full sync when you open Branch Manager)

0 (will not run full sync when you open Branch Manager)

T55Z036

Add registry value to disable incremental sync.

The following registry requires changes:

PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\GlobalDashboard

Key Name: DisableIncSync

Key Type: DWORD

Value: 1 to disable incremental sync to run

0 delete the value, the incremental sync will run as scheduled

12.17 Image Option

The following table lists the test fixes for the Image Option:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000063	Image Backup Job crashes

12.18 Microsoft Exchange Server

The following table lists the test fixes for the Microsoft Exchange Server:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T55Z014	Backup fails randomly on any database on Exchange Server with the following error "AE9724 Read data failed (err=2147467259)."
T55Z018	Cannot expand Document Level Agent
T55Z024	Unable to browse Exchange 2013 Document Level
T55Z027	Doc level backup SKIPS public folders but status shows as successful
T55Z032	Exchange 2013 Document Level Backup Hangs
T55Z040	Error "E3579 fail to obtain Exchange DB copy status" randomly occurs when the initialization of the powershell command fails. This fix will extend the powershell connection time out to a 4 minutes.
T55Z044	Backup exchange document level incomplete. The following registry requires changes for this fix: PATH: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA ARCserve Backup\ExchangeDocumentAgent\Parameters Key Name: SkipAsInfo Key Type: DWORD Value: 1
T55Z045	Error "AE9725 - Failed to create snapshot" during Arcserve Backup Exchange DB level backup when backing up from replica server during the create snapshot process.
T55Z056	WIN-CREATE SNAPSHOT TIME OUT Backup of exchange database level failed with following errors: "AE9725 D3MBXSRVPD5 create snapshot failed (err=0x80042316)" In exchange database backup log, the following message is logged: "Terminate the VSS create snapshot thread, time out."
T55Z062	Unable to browse Microsoft Exchange Document level, when the mailbox is on the parent domain, but user account is on the child domain.
T55Z084	Backup Exchange DB GETDAGNAME Exception The following registry requires changes for this fix: PATH; HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ExchangeDBAgent\Parameters Key Name: "DAGName" - Give the real DAG name of servers on all servers in DAG. Key Type: String
T55Z089	Exchange Document Level agent job always run full. even when the option is set to run incremental on a global option and the agent option set to use global.
T56P014	Unable to find mailbox during backup
T56P027	GUI crashes while modifying job
T58E214	After applying this fix, it will be possible to skip the integrity check for exchange DB before doing the backup.
T58E216	Universal agent crashes and generates a dump file during backup exchange DB.
T58E218	The Arcserve Agent for Exchange crashes approximately 1 minute only after the disk optimizer starts.
T5Y4003	Arcserve Manager will freeze/hang when we try to browse Microsoft Exchange Document Level
T5Y4017	Exchange document level backup crashes immediately with "E1311 xxxx job has crashed in tskept.log"
T5Y4023	Exchange 2007 DB level backup failing with E8535 - Failed to receive data from the agent.
T5Y4026	Backup exchange DB level get error "E3579 fail to obtain Exchange DB copy status" randomly.
T5Y4028	WIN-TAPECOPY unable to identify exchange doc level
T5Y4035	Document level backups are failing and unable to expand doc level nodes in DAG Exchange 2013.
T5Y4037	Doc level sub folder is unable to expand
T5Y4039	WIN-EXC 2013 Backup job crash

12.19 NAS Option

The following table lists the test fixes for the NAS Option:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000134	NDMP backup using two ISCSI cards for SUN Solaris ZFS
T00000155	NETAPP NAS OnTap 8.3 support
T245845	Estimated backup size is recorded wrongly
T245881	Fail to restore NAS session by Filer to Server
T245947	Clustered OnTap 8.2 backup
T245951	FILER TO SERVER RESTORE REQUESTS EXCESS TAPE
T51H094	NAS Backup job failed
T51H113	NAS backup failed AE0407
T51H117	Job history shows wrong size
T51H126	NETAPP Cluster Aware Backup
T51H139	Unable to perform NAS file restore
T51H140	Data migration not working with VTL Tape
T51H143	Unable to launch NDMP backup
T51H150	Catalog merge failed
T56P013	Slowdown during NAS Restore
P00000155	Provides support for NETAPP NAS OnTap 8.3 support

12.20 SAN Option

The following table lists the test fixes for the SAN Option:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000077	Mount Magazine leads to NT SCSI Port Error
T51H114	E3703 Unable to open media

12.21 Tape Library Option

The following table lists the test fixes for the Tape Library Option:

If you do not see a specific fix listed in this table, contact Arcserve Support for more information.

Test Fix #	Description
T00000144	This fix corrects the problem of Arcserve message engine service terminated unexpectedly.
T245938	Next tape is formatted after span timeout
T36A835	Tape engine fails to check license
T51H082	Catalog merge fails
T51H087	Tape engine crash during initialization of STK L700 on ISCSI
T51H095	Tape library power on reset To enable this fix, registry change is required. PATH: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Tapeengine\CHANGE_CFG Key Name: LBP Key Type: DWORD Value: 0
T51H111	E6300-NT SCSI Port Error with Mount Magazine
T51H131	Library inventory problem on HP EML E-SERIES
T51H134	Unable to connect to group with data migration to tape raid device
T51H153	Job hanges on spanning tape
T51H155	CAS-Library Support
T51H158	Slow data migration throughput with RAID 6 SAS Disk to Tape
T51H164	Data migration job failed in spanning tape
T55Z071	RESTORE BY SESSION NOT SHOW SECOND TAPE with UNIX Sessions
T58E196	Base E6300 (Ec=183) occurs
T58E233	Tape inventory failed
T58E238	Import fails slot is occupied
T5Y4001	Device lock after merge
T5Y4007	Eject media for RAID 1 devices

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

14.0 Contact Arcserve

The Arcserve Support team offers a rich set of resources for resolving your technical issues and provides easy access to important product information.

https://www.arcserve.com/support

With Arcserve Support:

You can get in direct touch with the same library of information that is shared internally by our Arcserve Support experts. This site provides you with access to our knowledge-base (KB) documents. From here you easily search for and find the product-related KB articles which contain field-tested solutions for many top issues and common problems.

You can use our Live Chat link to instantly launch a real-time conversation between you and the Arcserve Support team. With Live Chat, you can get immediate answers to your concerns and questions, while still maintaining access to the product.

You can participate in the Arcserve Global User Community to ask and answer questions, share tips and tricks, discuss best practices and participate in conversations with your peers.

You can open a support ticket. By opening a support ticket online, you can expect a callback from one of our experts in the product area you are inquiring about.

You can access other helpful resources appropriate for your Arcserve product.

Providing Feedback About Product Documentation

If you have comments or questions about Arcserve product documentation, please contact us at techpubs@arcserve.com.