BrightStor® ARCserve® Backup for Windows r11.5 SP3 Readme

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

This service pack is cumulative, as is this readme. Information related specifically to this service pack has been identified separately from information originally included in the release of BrightStor ARCserve Backup for Windows r11.5, BrightStor ARCserve Backup for Windows r11.5 SP1 and the release of BrightStor ARCserve Backup for Windows r11.5 SP2. For information included in the release of BrightStor ARCserve Backup for Windows r11.5 SP2, see the sections following the BrightStor ARCserve Backup for Windows r11.5 SP2 Readme section. For information included in the release of BrightStor ARCserve Backup for Windows r11.5 SP1, see the sections following the BrightStor ARCserve Backup for Windows r11.5 SP1 Readme section. For information included in the release of BrightStor ARCserve Backup for Windows r11.5, see the sections following the BrightStor ARCserve Backup for Windows r11.5 Readme section.

2.0 Operating System Support

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP2, BrightStor ARCserve Backup for Windows r11.5 SP1 or BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Operating System Support for BrightStor ARCserve Backup r11.5 SP2 , Operating System Support for BrightStor ARCserve Backup r11.5 SP1 and Operating System Support for BrightStor ARCserve Backup r11.5.

Support for the following operating systems has been added to the BrightStor ARCserve Backup for Windows base product, BrightStor® ARCserve® Backup Client Agent for Windows, and BrightStor® ARCserve® Backup Agent for Open Files:

Microsoft Windows Vista (32-bit and x64) (Agent only)
VMware ESX Server version 3.0 and 3.0.1 (32-bit)

2.1 Windows Vista Support for Agent for Open Files

The following sections provide information on Windows Vista support for Agent for Open Files:

The Agent for Open Files partially supports the Transactional NTFS (TXF) infrastructure on Windows Vista. Due to this reason, before performing backups ensure to close all the applications which have the files open in the context of TXF transaction, for example, installation programs.
To manage the Agent for Open Files Server installed on a Windows Vista machine remotely, perform one of the following:
- If the Vista machine is part of a domain, grant a domain account with administrator privileges on the Windows Vista machine and use that domain account to logon to manage the Agent for Open Files server.
- Add the DWORD value LocalAccountTokenFilterPolicy to the following registry key and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system
```

2.2 Agent for Microsoft Exchange

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Microsoft Exchange Server 2007 and the BrightStor® ARCserve® Backup Agent for Microsoft Exchange Server 2007 Premium Add-on:

Microsoft Windows Server 2003 x64, Standard or Enterprise Editions with optional Multilingual User Interface (MUI).
Microsoft Windows Server 2003 R2 x64, Standard or Enterprise Editions with optional Multilingual User Interface (MUI).

2.3 Enterprise Option for SAP R3 for Oracle

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Enterprise Option for SAP R3 for Oracle:

Microsoft Windows 2003 64-bit (IA-64, x64)

2.4 BrightStor ARCserve Backup and CA XOsoft WANSync Integration

The integration between BrightStor ARCserve Backup and CA XOsoft WANSync provides the dual benefit of continuous data protection (CDP) and backup of this protected data. Through this integration, WANSync continues to provide real-time, continuous data replication from the Production server (Master server) to the Replica server, while BrightStor ARCserve Backup then backs up this replicated data from the Replica server to the BrightStor ARCserve Backup server for archiving and compliance, and long term retention.

To integrate BrightStor ARCserve Backup r11.5 SP3 with CA XOsoft WANSync, you must be running WANSync, Version 4.0, starting with Build 69.

The Master servers are supported on the following operating systems:

Microsoft Windows 2000 Server and Advanced Server (32-bit)
Microsoft Windows Server 2003 R2 Enterprise Edition and Standard Edition SP1 (32-bit and x64)

The Replica servers are supported on the following operating systems:

Microsoft Windows Server 2003 R2 Enterprise Edition and Standard Edition SP1 (32-bit and x64)

In addition to the file protection, BrightStor ARCserve Backup and CA XOsoft WANSync integration supports data protection for the following:

Microsoft Exchange 2000 Standard SP4
Microsoft Exchange 2003 Standard SP1 and SP2
Microsoft SQL 7.0 Standard Edition and Enterprise Edition SP4
Microsoft SQL 2000 Standard Edition SP2, SP3, SP3A, and SP4
Microsoft SQL 2005
Microsoft SQL 2005 SP1
For more information about the integration, refer to the BrightStor ARCserve Backup for Windows WANSync Integration Guide.

Note: BrightStor ARCserve Backup and CA XOsoft WANSync integration supports WANSync running on English version and the BrightStor ARCserve Backup running on English and other languages supported by CA.

3.0 System Requirements

The following section provides system requirements for BrightStor ARCserve Backup.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP2, BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections System Requirements for BrightStor ARCserve Backup for Windows r11.5 SP2 , System Requirements for BrightStor ARCserve Backup r11.5 SP1 and System Requirements for BrightStor ARCserve Backup r11.5.

3.1 BrightStor ARCserve Backup Base Product

BrightStor ARCserve Backup is updated to support Internet Explorer Version 7.0 on both 32-bit and 64-bit machines.

3.2 Agent for Microsoft Exchange

BrightStor ARCserve Backup Agent for Microsoft Exchange is updated to support Microsoft Exchange 2007.

The agent includes the following options:

BrightStor® ARCserve® Backup Agent for Microsoft Exchange Server 2007 – A Database Level agent to backup and restore Microsoft Exchange server databases.
BrightStor® ARCserve® Backup Agent for Microsoft Exchange 2007 Premium Add-on – A Document Level agent to backup and restore Microsoft Exchange folders and messages.

3.3 Agent for Microsoft Exchange Server 2007

The following section provides information relating to the system requirements for the Agent for Microsoft Exchange Server 2007 for this service pack release:

The following are the minimum system requirements for the agent:

Hardware requirements for the base Microsoft Exchange Server.
For information about these requirements, see the Microsoft website.
512 MB RAM
100 MB free disk space

3.4 Agent for Microsoft Exchange Server 2007 Premium Add-on

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

The following are the minimum hardware requirements for the agent:

Hardware requirements for the base Microsoft Exchange Server.
For information about these requirements, see the Microsoft website.
512 MB RAM
200 MB free disk space

Note: This agent requires Microsoft Messaging API and Collaboration Data Objects 1.2.1 to be installed on your machine. This is available as a web download from the Microsoft web site and is not a part of the Microsoft Exchange 2007 server installation.

3.5 Enterprise Option for SAP R/3 for Oracle

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

Oracle 8, Oracle 8i (SAP R/3 4.x)
Oracle 9, Oracle 9i (SAP R/3 6.x)
Oracle 10, Oracle 10g (SAP R/3 7.0)

Note: SAPDBA should be installed on the same server to use the agent BACKINT option. SAPDBA is not available for the later versions of SAP R/3 6.4.

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

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

3.6 BrightStor ARCserve Backup and CA XOsoft WANSync Integration

Note: You must meet the BrightStor ARCserve Backup Base product and Client Agent for Windows requirements to use CA XOsoft WANSync features. Contact CA Technical Support for any updates to these requirements.

4.0 Installation Considerations

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

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP2, BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Installation Considerations for BrightStor ARCserve Backup r11.5 SP2 , Installation Considerations for BrightStor ARCserve Backup r11.5 SP1 and Installation Considerations for BrightStor ARCserve Backup r11.5.

You can remotely install the Agent for Open Files or the Client Agent for Windows on Vista machines. To do this, you can do one of the following:
- If the Vista machine is part of a domain, grant a domain account with administrator privileges on the vista machine and use that domain account to logon to remotely install the components on the Vista machine.
- Add the DWORD value LocalAccountTokenFilterPolicy to the following registry key:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system
```
You can now automatically perform silent upgrade of the existing components on the target machine by using the following command line option:
```
mastersetup.exe /au
```

5.0 General Considerations

The following section provides general information to consider when using BrightStor ARCserve Backup for Windows.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP2, BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections General Considerations for BrightStor ARCserve Backup r11.5 SP2 , General Considerations for BrightStor ARCserve Backup r11.5 SP1 and General Considerations for BrightStor ARCserve Backup r11.5.

The BrightStor ARCserve Backup Exchange VSS Writer option is not supported for Exchange Server 2007, as the BrightStor ARCserve Backup Agent for Microsoft Exchange Server 2007 uses the Volume Shadow Copy Services (VSS) technology internally.
BrightStor ARCserve Backup provides cross-platform support that allows you to use BrightStor ARCserve Backup for Windows r11.5 and later versions to browse, back up, restore, and protect GroupWise databases running on the NetWare servers.
Unicenter Software Delivery does not currently support remote deployment of the agents to the machines running Microsoft Windows Vista.
The BrightStor ARCserve Backup GUI has been updated to refer Windows NT/2000/XP/2003 node generically as Windows Systems. The Windows Systems include the following:
- Windows NT
- Windows 2000
- Windows XP
- Windows 2003
- Windows Vista
- Windows Powered NAS
- Windows Storage Server 2003
BrightStor ARCserve Backup for Windows Disaster Recovery Option has been updated to allow you to recover a physical server to a virtual server. The following scenarios are supported:
- Local backup of the physical server and local restore to the virtual server
- Remote backup of the physical server and remote restore to the virtual server
- Local backup of the physical server and remote restore to the virtual server
BrightStor ARCserve Backup Disaster Recovery Option has been enhanced to support floppy-less Disaster Recovery on Windows 2003 and Windows XP machines.
For information about the Disaster Recovery Option enhancements and the best practices for using VMware® ESX Server™ Backup, see the online technical documents available at http://supportconnectw.ca.com/public/storage/infodocs/basb115win/basb115win-tecdoc.asp.
BrightStor® ARCserve® Backup Client for VSS Software Snap-Shot is no longer supported on Microsoft Windows XP Professional.
You must have the BrightStor ARCserve Backup Client for VSS Software Snap-Shot installed on your machine to use the Volume Shadow Copy Service option in the Global Options.
BrightStor ARCserve Backup Agent Admin Window has been enhanced to display up to 32 connections simultaneously.

5.1 Security Updates

This service pack includes all the security vulnerability updates released for BrightStor ARCserve Backup r11.5 SP2. In addition, this service pack includes many bug fixes and solutions to previously discovered known issues. CA recommends that you upgrade to this service pack at your earliest convenience.

6.0 Known Issues

The following section provides information regarding issues known to exist in BrightStor ARCserve Backup r11.5 SP3.

For information originally identified during the release of BrightStor ARCserve Backup for Windows r11.5 SP2, BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Known Issues for BrightStor ARCserve Backup r11.5 SP2 , Known Issues for BrightStor ARCserve Backup r11.5 SP1 and Known Issues for BrightStor ARCserve Backup r11.5.

When you register BrightStor ARCserve Backup with Unicenter Software Delivery Version 11.1, you must specify security provider credentials in the User ID field on the Unicenter Software Delivery User Details dialog. The security provider credentials must be in the following format:
```
Winnt://server/administrator
```
Where server represents the name of the USD Server on the Unicenter Software Delivery User Details dialog.
Note: Failure to use this format may result in session establishment failure.
For the CA XOsoft WANSync Integration, any BrightStor ARCserve Backup generated Error and Warning messages that appear in the Activity Log and are not linked to a related Help topic, see the BrightStor ARCserve Backup for Windows CA XOsoft WANSync Integration Guide.
For the Agent for Microsoft Exchange, several Error and Warning messages that appear in the Activity Log and the dialogs that relate to Microsoft Exchange 2007 Server functionality are not linked to the online help topic. For more information about the Agent for Microsoft Exchange error messages and Exchange 2007 Server functionality, see the BrightStor ARCserve Backup Agent for Microsoft Exchange Guide.
Restore job fails with error messages when you use Enterprise Option for SAP R/3 for Oracle to restore database objects located under root of the system partition (example: c:\). To avoid this problem, do not save the database objects in the root directory.
In this release, BrightStor ARCserve Backup partially supports SQL Writer service for SQL Server 2005. Due to this limitation, BrightStor ARCserve Backup uses Microsoft SQL Server Desktop Engine Writer (MSDE Writer) as the default Writer for SQL Server 2005.
To enable this functionality, set the following registry key to 0, start the SQL Server VSS Writer service manually and restart your machine:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Settings\MSDEVersionChecking
```
The iSponsor installation is not supported when you install the BrightStor ARCserve Backup using Unicenter Software Delivery.
The Virtual Library configuration is not supported on 64-bit machines.
The Agent for Microsoft Exchange skips backing up the attachments which exceeds 100MB and reports the appropriate message in the activity log.
You must assign only one staging device to a staging group. Staging jobs use the first staging device and fails to use other staging devices even if they do not exceed the threshold.
Restore jobs fail when you restore SharePoint Portal Services database to an alternate location on a different machine. To avoid this, you must manually map the virtual destination path of the SharePoint Portal Services database you want to restore to its physical path. To find the SharePoint Portal Services database physical path, select the specific session from the Restore By Session view of the Restore Manager. The format of the physical path should be the following:
```
\\<machine name>\dbasql@<SQL server instance name>\<SQL server database name>
```
Backup jobs may fail when the source files, directories, or both contain special characters in their name (for example, Ω, È, Ǽ, and Ø). To remedy this problem, select the parent directory to the files that contain special characters as the source for your backup job. Ensure that the parent directory contains no special characters and then submit the job.
BrightStor ARCserve Backup Enterprise Option for SAP R/3 does not support remote Silent upgrade using the following parameter on the 64-bit operating systems:
```
/AU
```
When you install the SharePoint External Data Agent or the SharePoint Database Agent on a Server machine running the router, regardless of the new path you specify BrightStor ARCserve Backup installs these subagents in the router's home directory.
Restoring the backward-compatible Document Library to an alternative location on a remote machine running a different version of Exchange Storage Engine than the Source machine causes SharePoint Portal Server Document Management service on the remote machine to fail. To avoid this, you must ensure that the version of the Exchange Storage Engine running on the remote machine is same as the version running on the source machine.
In this service pack, to enhance the performance of the backup jobs to the physical devices, the FILE_FLAG_NO_BUFFERING flag is enabled by default. This can cause performance issues while backing up to File System Devices (FSDs). To avoid this, add the DWORD value FSDNOBUFFER to the following registry key and set it to 0:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\TapeEngine\CONFIG
```
When you install the Client Agent for Windows on Windows 98 or Windows Me machines, garbage characters or untranslated content may be displayed in the End User License Agreement (EULA). You can view the correct EULA on other platforms.
Restore jobs may fail when you backup the data from the replica database immediately when the replica is enabled.
This is because when you perform backup from the replica database as soon as the replica is enabled, the checkpoint files and the log files may not be replicated to the Local Continuous Replication (LCR) location. When you restore this backup set to the original location, the backup set may not contain the checkpoint file and the restore job fails. To avoid this, remove all the log files from the original storage group location before you submit the restore job.
When you restore Microsoft Exchange mailboxes to a target folder, the powershell may crash if the target folder has a lengthy folder name. This is because the folder name in the Microsoft Exchange Server is limited to 255 characters. You must ensure not to use lengthy target folder names while restoring the mailboxes.
The backup jobs may fail when you restore the previous full backup session and submit the incremental backup job without performing full backup. Also, the subsequent full backup jobs fail with the error message "Event 206, "****.edb" cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup." in the Windows Application Event viewer. To resolve this, restart the Exchange Server Information Store Service from the Service Manager.
Note: To avoid this scenario, ensure to perform a full backup before you submit incremental jobs.
Multiplexing backup jobs may fail if your BrightStor ARCserve Backup server machine is having insufficient memory to handle the maximum number of streams (32) with the maximum chunk size (16 MB). The BrightStor ARCserve Backup server requires approximately 150 MB per job on the server side and 40 MB per job on the client side. For example, if you submit a backup job to back up 10 machines, you must ensure that 1.5 GB (150*10) is available on the BrightStor ARCserve Backup server machine.
When you submit a tapecopy operation in non-query mode to copy data from a tape that was created using multiplexing to a non-multiplexing tape, BrightStor ARCserve Backup may not copy all sessions from the source tape to the destination tape.
To remedy this problem, submit a tapecopy operation using the –n and –nTotal switches. These options let you copy the remaining sessions from the source tape to the destination tape, starting with the first missing session.
When you merge the older system state backups that were backed up with the Disable File Estimate option enabled, the server name in the Restore Manager is displayed as 0.0.0.0. To restore the backups with the server name 0.0.0.0, you must ensure that the system state belongs to the local server and add the DWORD value ForceRestoreSS to the following registry key and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Restore
```
Note: Ensure to delete this value after the system restore is complete.
When you submit a backup job to back up Microsoft Exchange 2007, the Agent for Microsoft Exchange and the Client Agent for Windows fails to back up the IpFilters.edb file.
The IpFilters.edb file is part of the Transport Role and can be located in different locations depending on your Microsoft Exchange topology. This file stores manually configured IP allow/block entries which are used by the connection filtering agent in the anti-spam filters to allow or block the specified IP connections. It is also used by the Sender Reputation Agent (SRA) to add the IP addresses to automatically block the list entries during runtime. When you perform disaster recovery of a server machine which has the Transport Role installed, you will lose these entries. In addition, the Exchange Server will create an empty IpFilters.edb file when the exchange services are restarted.
To avoid the loss of this configuration data, you are highly recommended to install the Agent for Open Files which allows access to this file for the backup job.

7.0 Documentation Changes

The following section provides information about items that have not yet been changed in the product documentation for BrightStor ARCserve Backup for Windows r11.5 SP3, but that affect the information in that documentation:

When you back up the Macintosh machine, the error code AW280080 in the Job Status Activity Log incorrectly displays the information about UNIX. This information is applicable to Macintosh.
For this release BrightStor ARCserve Backup for Windows adds support for Microsoft Exchange 2007 Server and CA XOsoft WANSync Integration. You can download the most current versions of these guides at the CA SupportConnect web site.

In the BrightStor ARCserve Backup for Windows r11.5 Administrator Guide, the Set Up Dependencies Between ARCserve Backup Groups section states the information which is partially correct. Use the following information to set up dependencies between resources in the BrightStor AB Groups:

Group Member Dependency

BrightStor AB BrightStorAB Shared ( FileShare Resource)
Cluster Name
Cluster IP Address

BrightStor BKP Registry BrightStorAB Shared ( FileShare Resource)
BrightStor AB

BrightStorAB Shared BrightStor ARCserve Backup installation disk
Cluster Name
Cluster IP Address

Cluster Name BrightStor ARCserve Backup installation disk
Cluster IP Address

Cluster IP Address BrightStor ARCserve Backup installation disk

Group Member	Dependency
BrightStor AB	BrightStorAB Shared ( FileShare Resource) Cluster Name Cluster IP Address
BrightStor BKP Registry	BrightStorAB Shared ( FileShare Resource) BrightStor AB
BrightStorAB Shared	BrightStor ARCserve Backup installation disk Cluster Name Cluster IP Address
Cluster Name	BrightStor ARCserve Backup installation disk Cluster IP Address
Cluster IP Address	BrightStor ARCserve Backup installation disk

For information originally identified during the release of BrightStor ARCserve Backup for Windows r11.5 SP2, BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Documentation Changes for BrightStor ARCserve Backup r11.5 SP2 , Documentation Changes for BrightStor ARCserve Backup r11.5 SP1 and Documentation Changes for BrightStor ARCserve Backup r11.5.

8.0 Published Fixes

The complete list of published bug fixes for this product can be found through Published Solutions on SupportConnect.

8.1 Included Fixes

The following section provides information regarding fixes included in this release of BrightStor ARCserve Backup r11.5 SP3.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP2, BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Included Fixes for BrightStor ARCserve Backup r11.5 SP2 , Included Fixes for BrightStor ARCserve Backup r11.5 SP1 and Included Fixes for BrightStor ARCserve Backup r11.5.

[T596014] [T245286] The BrightStor® ARCserve® Backup Disaster Recovery Option has been updated to ensure that the DRScanSession utility now properly locates the backup tapes in the slot. In addition, when the Tape Engine is started, the library reliably loads the backup tape to a drive from the slot.
[T596015] [T245287] DRScanSession utility now reliably creates Machine Specific Disk (MSD) when you enter the following in the drscans file:
```
FDUPDATE=TRUE
```
In addition, DRScanSession now works reliably when you enter the index number of the tape device to select the tape which has the Disaster Recovery session.
[T596016] [T245293] You can now reliably backup Oracle databases with large tablespaces when the total length of the path names of backup files is more than 32 KB and data files are not included in the backup.
[T596017] [T245295] [T245305] [QO84016] Backup jobs no longer fail after saving the Disaster Recovery information in the adrnet.ini file on Microsoft Cluster Server environment if the tape devices support One Button Disaster Recovery (OBDR).
[T596005] [T2D2576] BrightStor ARCserve Backup now records the errors properly in the Activity log when the incremental backup jobs are completed with the failed status.
[T596006] [T2D2577] Backup jobs no longer fail when the Client Agent for Windows backs up the following directory:
```
%systemroot%system32\wbem\Repository
```
[T596007] [T31A401] BrightStor ARCserve Backup no longer reports excessive DoAdvanceWrite() messages in the dbaxchg2.log file.
[T596008] [T31A399] BrightStor ARCserve Backup has been updated so that SQL Full Text Catalogs are now properly displayed in the Restore Manager.
[T596009] [T31A398] Document Level backup jobs now properly restore the entire folder when the folder has more than 100 items and you have Microsoft SQL as the database.
[T596018] [T31A396] Microsoft Exchange backup jobs now retain the transfer protocol settings that you specify.
[T596010] [T31A395] BrightStor ARCserve Backup server no longer abends on reboot when you uninstall BrightStor ARCserve Backup Agent for Microsoft SQL on a cluster server. Previously, this caused registry to get corrupted.
[T596011] [T46B144] The Backup Manager no longer displays the error message “Failed to authenticate the user caroot (EC=-1).”
[T596012] [T46B145] Multiplexing master jobs now reliably back up Disaster Recovery and BrightStor ARCserve Backup databases.
[T596013] [T46B147] BrightStor ARCserve Backup has been updated to ensure that the Activity log reflects the correct timestamp of modified files when scanning a Linux backup job.
[T58E026] [T2D2568] BrightStor ARCserve Backup now reliably connects virtual cluster to the Client Agent for Windows when you use GeoCluster Replicated Disk as resource type.
[T58E031] [T2D2574] BrightStor ARCserve Backup now reliably backs up all the available shared disks on the remote server when you submit full remote server backup job.
[T58E029] [T2D2571] Tapes used by the tapecopy command are now correctly moved to the save set.
[T58E027] [T2D2569] The complete First Storage Group is no longer automatically selected when you modify Microsoft Exchange backup jobs that have only one mail box selected.
[T58E025] [T2D2566] The Backup Alert feature now works reliably when you modify email attachments and displays the entire list properly.
[T58E024] [T2D2563] Igateway Service now properly upgrades to 4.x when you upgrade to BrightStor ARCserve Backup for Windows.
[T58E023] [T2D2562] Tapecopy jobs no longer fail with the message “Connect To Target Tape Failed..239.” when you use the entire switch with WORM tapes.
[T58E022] [T2D2561] Source priority is now retained when you run Microsoft Exchange Document Level backups.
[T58E021] [T2D2560] Microsoft Exchange backup jobs no longer select the Brick Level and Document Level databases when you select the entire folder.
[T58E020] [T2D2559] GFS rotation sub-jobs now reliably append backup data to the master jobs' tape when you back up BrightStor ARCserve Backup for UNIX Agent for Oracle.
[T58E019] [T2D2557] BrightStor ARCserve Backup now correctly displays the Server name in the Restore by Tree view when you back up the entire local server and the system state.
[T58E018] [T2D2556] You can now reliably use the ca_backup command to back up the remote node that does not have Client Agent for Windows installed.
[T58E032] [T146419] You no longer receive E6300 Windows NT SCSI Port error when you use VXA 3 drive connected to host adapter having the transfer rate set to less than 128K.
[T58E037] [T245298] BrightStor ARCserve Backup has been updated to ensure that Oracle database files are no longer backed up when you do not set SkipDSA to 0 and you have Agent for Oracle running on your machine. In addition, you no longer receive failure to connect messages in the dbaora7.log.
[T58E030] [T2D2573] You can now reliably connect to the Cluster server of a group using the cluster IP address even if you do not have shared disk in the group.
[T58F026] [T36B245] BrightStor ARCserve Backup has been updated to ensure that username and password verification no longer fails when you modify the user name.
[T58F025] [T36B243] BrightStor ARCserve Backup has been updated to ensure that makeup jobs no longer overwrite the primary backup job log.
[T58F016] [T16C626] Multiplexing tapecopy jobs to multiplexing media no longer fail with the error “Error creating a tsi handle, make sure your tape engine is turned on. rc[38]” when you have more than 1000 sessions on a source tape.
[T58F017] [T16C629] Multiplexing tapecopy command now reliably copies multiplexed backup jobs that span several tapes. In addition, you no longer receive the messages “Failed to goto session 61166 on source tape session skipped, rc[169]", and "MTC_ReadDaemon:: MUX_ERROR::Did not hit data while reading. SHOULD NOT have happened. error = 0x8700fff5" in the tapecopy log.
[T58F018] [T16C630] BrightStor ARCserve Backup has been updated to ensure that you no longer receive the following warnings and error messages when multiple append jobs are running at the same time:
- W3851 Media is full.
- E63638 Buffer under run occurred during backup at Drive [xx].
- E8003 Media manually ejected from Drive [xx].
- E6500 Client connect to tape failed.
[T58F019] [T16C631] BrightStor ARCserve Backup no longer erroneously reports jobs as successful when these jobs fail with the error message “E63638 Buffer under run occurred.”
[T58F020] [T16C633] Rotation jobs now use RAID 1 sets properly. Previously, if only one tape of a two tape RAID set was found, BrightStor ARCserve Backup backed up only the one tape. This fix ensures that, if only one tape is found (for example, if the other tape was exported from the library), BrightStor ARCserve Backup erases the tape in the Scratch set and creates a new RAID set for the rotation backup job. To enable this fix, you must add the DWORD value RaidForceToUseBlankSet to the following registry key and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCServe Backup\Base\Tapeengine\CONFIG
```
[T58F021] [T16C635] Scan jobs are no longer reported as successful if there are errors.
[T58F022] [T16C636] In cluster environments, after you successfully configure your SAN environment, the configuration is properly retained when you close and reopen the SAN Configuration dialog. In addition, physical server names added to clusters are also retained properly.
To display mixed nodes, add the key DisplayMixedNodes to the following registry:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\ Base\Tapeengine\DisplayMixedNodes
```
To display only physical nodes, add the key DisplayPhysicalNodes to the following registry:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Tapeengine\DisplayPhysicalNodes
```
[T58F023] [T36B240] The Report Manager no longer reports incorrect NetWare sessions information when you use tapecopy command to copy the back up tape to another tape.
[T58F024] [T36B241] BrightStor ARCserve Backup now works reliably when you select the Format option from the Device Manager.
[T595009] [T1A5348] BrightStor ARCserve Backup has been updated to ensure the following:
- Multiplexing jobs no longer fail with the error “E2246 multiplexing device error, abort the job.”
- Multiplexing backup jobs no longer fail intermittently.
- You no longer receive C3702 error message when you run a Multiplexing backup job.
[T595008] [T1A5349] Backup jobs submitted to File System Devices no longer fail with the error “E3705 Unable to format media (MEDIA=tapename, EC=FAILED TO WRITE VOLUME).”
[T595010] [T1A5347] You can now reliably restore data from the disk staging devices when the size is more than 32 GB. In addition, you no longer receive the error “W3823 Unable to find media. (MEDIA=STAGE1-1, ID=0686, SEQ=2).”
[T595011] [T1A5345] The error “Check Device Group(group name)/Media(media name) availability” is no longer logged in the Activity log when you schedule backup jobs in a cross platform SAN environment and the jobs fail to start.
[T595014] [T5A6015] The Client Agent for Windows now logs the warning message “AW0004 Failed to open file” in the Activity Log file.
[T595018] [T36A357] You can now reliably restore very large Microsoft SQL databases.
[T595012] [T245283] Tapes with similar tape names using the Overwrite Same Media Name, or Blank Media option are now successfully formatted by backup jobs.
[T595013] [T245285] BrightStor ARCserve Backup has been updated to ensure that hardware compression is now properly disabled when you add the DWORD value FormatWithoutHardwareCompression to the following key and set the value to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\base\TapeEngine\CONFIG
```
[T595016] [T36A355] You can now successfully perform Disaster Recovery on Windows XP and Windows 2003 machines that have no external drives connected. Previously, the agent failed to format such machines and the Disaster Recovery process was unsuccessful.
[T595017] [T36A356] BrightStor ARCserve Backup Disaster Recovery Option is now updated to correctly identify the number of disks in the Text Mode Setup and the Disaster Recovery Wizard when you load third party drivers during Disaster Recovery.
[T595019] [T36A358] You can now reliably use Oracle RMAN to restore Oracle databases without generating the E8605 error message.
[T595015] [T36A352] [T36A385] The Microsoft SQL Agent Account Configuration utility now works reliably on machines which have multiple versions of Microsoft SQL installed (example: Microsoft SQL 2000 and SQL 2005). Previously, the utility failed to load and verify multiple virtual SQL server names.
[T5A6020] The ca_mgr command displays the list of migration jobs properly.
[T31A405] You can now restore Brick Level backup jobs to alternate locations without any errors.
[T31A402] [T31A408] BrightStor ARCserve Backup has been updated to ensure Document Level jobs do not display the message “connecting to media” for long time before starting a staging job.
[T245302] The Exclude Directory filter now works properly when you submit restore jobs using Client Agent for Windows and the directory pattern you specify includes the drive name.
[T245301] Backup jobs now record the warning messages related to skipped .edb files in the Activity log.
[T245304] BrightStor ARCserve Backup has been updated to ensure that DRScanSession utility reliably creates Machine Specific Disk (MSD) without any errors.
[T245306] Backup jobs now exclude the database files when you have BrightStor ARCserve Backup Agent for Oracle running on your machine and you submit a backup job to back up the entire folder which contains more than 2048 database files. To enable this functionality, add the DWORD value MaxFileFilter to the following registry and set to the value more than 2048:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrigthStor ARCserve Backup\Base\Task\Backup
```
[T245307] BrightStor ARCserve Backup now properly updates the Activity log when you click the Refresh button on the Activity Log tab in the Job Status window.
[T245303] BrightStor ARCserve Backup has been updated to ensure that hard links are not restored when you set the Record Hard Links for NTFS volumes option to off on the Job Engine tab of the Server Admin utility.
[T245308] Backup jobs now reliably backs up the Oracle Archive Log using the Agent for Oracle.
[T1A5362] Restore jobs no longer fail with the errors E6603 and E6610 on a Storage Area Network (SAN) when you use RAID option.
[T1A5358] BrightStor ARCserve Backup has been updated to ensure the following:
- Direct Access Restores (DARs) no longer fails when the file to be restored is on the third sequence of the tape.
- Merge operations now properly detects the End of Media to successfully complete the merge operations.
[T1A5356] BrightStor ARCserve Backup has been updated to ensure that Agent for Open Files no longer abends with stop code 7F.
[T1A5363] Multiplexing backup jobs no longer abend the Tape Engine when you enable the Eject media upon backup job completion option.
[T1A5359] Network Attached Storage (NAS) backup jobs no longer fail when you include non-existing volumes in the backup job.
[T1A5360] Tape Engine no longer abends when you do not have a blank tape in the library.
[T1A5364] You can now successfully run the RAID option jobs on the distributed server without any errors.
[T16C642] Restore jobs no longer fail with the error E3802 when restore sessions are more than 2 TB.
[T245309] [T5A6025] Alert messages are now properly processed when you select the Job Incomplete option while configuring the Alert option.
[T46B150] Staging jobs now use the available formatted tapes to perform the migration job. Previously, migration jobs would search for a used tape and would not accept any other formatted tapes. This behavior has been corrected.
[T36A368] You can now successfully install BrightStor® ARCserve® Backup Enterprise Option for SAP R/3 for Oracle on 64-bit machines having Oracle 10G installed.
[T36A369] BrightStor ARCserve Backup has been updated to ensure that SAP R/3 Oracle Option BACKINT Configuration reliably detects the SAP environment when you have Oracle 10G and SAP installed on 64-bit machines.
[T5A6026] Bconfig.exe has been updated so that you can successfully reset the caroot password.
[T16C649] BrightStor ARCserve Backup has been updated so that you can perform a quick inventory from the Device Manager when running with the ACSLS library.
[T36A367] [QO83455] BrightStor ARCserve Backup has been updated to retain the selection criteria when you modify the job after selecting the full node to back up Microsoft SQL instance.
[T46B152] BrightStor ARCserve Backup has been updated to ensure that for staging jobs, the purge session is performed the following day when you specify the purge time earlier than the job start time.
[T36A360] Remote Disaster Recovery procedure on Windows 2000 server now properly displays and restores the dynamic disk. Previously, the dynamic disk was identified with an incorrect drive name, thus excluding the drive from being restored.
[T16C646] BrightStor ARCserve Backup has been updated so that it will not experience slow throughput while backing up to the disk staging device.
[T16C648] BrightStor ARCserve Backup has been updated to ensure that local groups on the distributed server are not deleted in the Storage Area Network (SAN) environment when the tape engine is restarted.
To enable this functionality, use the following registry key to find the group name GROUPx where x is the group number of the local group and set the value of GROUP_ATTRIBUTE to 0x100:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Tapeengine\GROUPx
```
[T16C651] BrightStor ARCserve Backup has been updated to ensure the following when BrightStor ARCserve Backup r11.5 SP2 is applied:
- Throughput of the backup jobs is not significantly reduced while backing up the data to the local file system device (FSD).
- Multiplexing staging jobs no longer terminate abnormally due to physical memory constraints.
- Tape engine no longer crashes on multiplexing, multistreaming, and disk staging jobs.
[T36A361] You can now reliably restore large Lotus Domino databases. In addition, you no longer receive the error “Invalid destination path specified. Please make a selection or enter a valid path for Destination. eg,C:\MYDIR\ \\MACHINE\SHARE\DIR" while restoring Lotus Domino databases of large size.
[T31A345] BrightStor ARCserve Backup has been updated to ensure that the Agent for Microsoft Exchange now works properly during Brick Level backup jobs.
[T31A412] BrightStor ARCserve Backup has been updated to ensure that incremental backup is performed when you package Brick Level Microsoft Exchange backup jobs within GFS rotation jobs. Previously, full backup was performed.
[T36A359] BrightStor ARCserve Backup with the Disaster Recovery Option installed, now display the warning messages if you do not select the entire node for the backup job.
[T36A363] [T36A365] BrightStor ARCserve Backup now reliably creates CA bootable CD image for the following machines when you run Create Boot Kit:
- Windows 2000 Server SP4
- Windows 2000 Professional SP3
[T36A364] BrightStor ARCserve Backup has been updated to ensure that BACKINT configuration screen does not terminate abruptly when you enter incorrect user credentials or connect to the remote backup server while configuring BrightStor ARCserve Backup Enterprise Option for SAP R/3 for Oracle.
[T16C647] BrightStor ARCserve Backup has been updated so that the message “E3854-MAXIMUM DEVICES REACHED” is displayed only when the maximum number of devices exceeds twenty-five.
[T245311] BrightStor ARCserve Backup has been updated so that you no longer receive the E8601 error message when you back up a node having two Oracle instances and the Client Agent for Oracle installed.
[T2D2578] Tapecopy jobs no longer terminate abruptly when you run the following command:
```
tapecopy –s sourceGroup –d targetGroup –entire –ex –fDstMux
```
[T2D2579] BrightStor ARCserve Backup has been updated to ensure that multiplexing tapecopy jobs no longer fails on non-multiplexing tapes after applying BrightStor ARCserve Backup r11.5 SP3.
[T2D2580] Tapecopy jobs now use the tape with the highest sequence in the set if the specified sequence tape is full.
[T31A411] BrightStor ARCserve Backup now reliably restores the fully selected mail box when you submit a Brick Level Microsoft Exchange restore job. Previously, the Activity log displayed the restore size as 0 bytes for such restore jobs.
[T5A6022] Backup jobs no longer fail when you select both passive and active nodes in a cluster environment. Previously, such backup jobs failed with the error message “AW0324 Cluster drive belongs to other nodes or it is not available."
[T1A5362] BrightStor ARCserve Backup now reliably restores the Storage Area Network (SAN) using the RAID option. In addition, the following error messages no longer appear:
- E6603 Failed positioning
- Too many drive failures, operation aborted
[T1A5358] [T1A5367] [QO84383] BrightStor ARCserve Backup has been updated to ensure the following:
- Tape Engine now works reliably without abending intermittently.
- Network Attached Storage (NAS) backup jobs no longer fails with exception caused by candmpc.dll.
- Direct Access Restores (DARs) no longer fails when the file to be restored is on the third sequence of the tape.
- Merge operations now properly detects the End of Media to successfully complete the merge operations.
- Two way backups are performed reliably.
- Restore jobs no longer fail with the invalid session header signature.
[T245320] BrightStor ARCserve Backup has been updated to encrypt the registry entry value of the File System Device (FSD) account information when you start the tape engine.
[T36A380] BrightStor ARCserve Backup Enterprise Option for Disaster Recovery now supports more than 64 devices.
[T16C662] [T16C656] BrightStor ARCserve Backup now correctly displays the number of slots per magazine of HP MSL6000 and HP MSL5000 libraries as 12 in the Dismount window.
[T31A421] You can now successfully restore local SQL databases backed up using ARCserve 2000 to SQL 2000 cluster. Previously, such jobs failed with the error messages E8617 and E8603.
[T36A382] [T36A372] BrightStor ARCserve Backup has been updated to filter the child jobs correctly when you select the Executed Within The Past option from the Job Status Manager. Previously, this problem occurred when you perform a rotation job with the Staging option enabled.
[T36A381] Parent and child backup jobs are now displayed properly in the Job Status Manager when you run cross platform RMAN Oracle rotation jobs.
[T2D2582] You can now connect to cluster and physical agents even when you have more than 16 shared disks configured in the cluster environment.
[T2D2583] BrightStor ARCserve Backup has been updated to ensure that the Keep Archive Bit option is not cleared erroneously when you run backup jobs using the Client Agent for Windows and select the Encrypt, and Preserve File Access Time options.
[T5A6027] You can now successfully run the Enterprise Job Status Report jobs involving multiple servers (more than 3) without any error messages. Previously, these jobs failed with the error message “Failed to connect to server, check the username and password” while retrieving the data.
[T2D2581] BrightStor ARCserve Backup has been updated to reliably connect to the remote SQL server when the Tape Engine is started.
[T46B158] BrightStor ARCserve Backup has been updated to ensure that the tape expiration dates does not change erroneously when the rotation jobs format the tapes.
[T16C661] Disaster Recovery no longer fails during the virtual library initialization when you perform a full backup to the stand alone tape drive on the machines having two SCSI cards, first card attached to physical library and the second card attached to a stand alone tape drive.
[T245317] [T245312] BrightStor ARCserve Backup now correctly displays the empty slots when you use the ca_devmgr –mount command. Previously, if the first slot number of the changer is 0, the command erroneously printed a wrong slot number as empty.
[T245318] BrightStor ARCserve Backup now displays the exit code of the tapecopy job as 1 if the destination blank tapes are insufficient. Previously, the exit code for these jobs erroneously displayed as 0.
[T46B157] Tape Engine now works reliably when you set the tape log size limit and you have more than 32 tape log files.
[T16C655] [T16C600] BrightStor ARCserve Backup has been updated to ensure that backup jobs no longer hang on the Move Medium SCSI command or cause system abend when you use Virtual Tape Libraries (VTLs).
[T16C658] BrightStor ARCserve Backup has been updated to ensure that inventory of all the slots does not occur when you remove a magazine from the HP UHDL library.
[T245314] BrightStor ARCserve Backup Client Agent for Windows no longer deletes the directories after the backup jobs are completed when you set the Delete Source Files After Backup To Media option. To enable this functionality, use the DWORD DeleteDirInMigration in the following registry key and set it to 0:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup \ClientAgent\DeleteDirInMigration
```
[T245315] BrightStor ARCserve Backup has been updated to reliably print the trouble ticket header string which is set for each job in the Alert tab of the Global Settings window.
[T46B156] You can now reliably submit backup jobs using the ca_backup command with scan and CRC check options.
[T36A378] BrightStor ARCserve Backup Agent for Oracle now reliably connects to the Oracle server which has multiple versions of Oracle client installed and undefined ORACLE_SID.
[T36A379] Cross platform Oracle backup jobs (from UNIX to Windows) now work reliably after formatting the media when you schedule the jobs using rotation schedule.
[T16C657] BrightStor ARCserve Backup has been updated to ensure that tapecopy jobs prompt you to insert the second tape when it reaches the end of the first tape. Previously, such tapecopy jobs failed with the error messages.
[T46B155] BrightStor ARCserve Backup now correctly displays the total average throughput of the backup job that backs up more than 2GB data to the tape.
[T146441] The tapecopy jobs now reliably export the media when database query switches are used in the tapecopy command.
[T31A403] Backup jobs now work reliably without causing the system to shutdown after the job summary is written to the Activity log.
[T245313] BrightStor ARCserve Backup has been updated so that Bar code reader installed no longer changes the status to OFF when you configure a new library using the Device Configuration wizard.
[T46B154] BrightStor ARCserve Backup now reliably executes the following command on the remote database server:
```
ca_devmgr –purge xxx –sessions all
```
[T36A375] You can now successfully run SETUPSQL.EXE to convert VLDB to Microsoft SQL database on a cluster environment which has Microsoft SQL 2005 installed. Previously, BrightStor ARCserve Backup failed to create the Microsoft SQL database ASDB with the given virtual SQL name.
[T16C653] BrightStor ARCserve Backup has been updated to ensure that Disaster Recovery no longer fails with the error code 234 and with the error message “TSICreateTSIHandle() failed, Error[234]” in the Disaster Recovery log.
[T16C645] Restore jobs no longer fails with the following error messages:
- E3802 Invalid file header signature
- E3803 Invalid file trailer signature
To implement this functionality, add the DWORD Recover to the following registry key:
```
HKEY_LOCAL_Machine\software\computerassociates\Brightstor arcserve backup\ base\tasks\restore
```
[QO84983] This service pack includes all the security vulnerability updates released for the following files that allowed arbitrary code to be executed remotely with the local system privileges:
- Tapeeng.exe
- Mediasvr.exe
- Ascore.dll
In addition, this service pack includes many bug fixes and solutions to previously discovered known issues. CA recommends that you upgrade to this service pack at your earliest convenience.
[QO85308] [T16C643] BrightStor ARCserve Backup Enterprise Option for StorageTek ACSLS now supports StorageTek Libattach 1.4.1.
[T245319] Microsoft SQL databases are now reliably backed up and restored when you specify the path of the data files and transaction logs located in the root directory and select the source from the Backup Manager window.
[T36A384] You no longer receive the error message “failed to copy initsid.utl” when you run DBAconfig.exe on 64-bit machines.
[T36A383] The NetWare objects are now displayed properly in the source tab when you modify NetWare copy jobs from BrightStor ARCserve Backup Manager running on a Windows machine. In addition, you no longer receive the error message “Network error. The parameter is incorrect” when you expand the NetWare server name.
[T2D2587] [T2D2589] Tapecopy jobs now reliably append to the Multiplexing tapes available in the save set when you run the following command:
```
tapecopy -qMediaPool -m -fDstMux
```
Also, if the multiplexing tapes are not available in the save set, the tapecopy jobs use the scratch tapes or blank tapes.
[T36B255] Windows Cross Platform Manager now works reliably when you modify a NetWare job that is created on a Linux machine.
[T2D2586] BrightStor ARCserve Backup has been updated to ensure that the backup sessions are no longer duplicated when you run the tapecopy job using the following command and submit the same tapecopy again:
```
tapecopy -dGroupname -qMediaPool -m
```
[T5A6029] The message “W3388 : pre command cannot be executed. (no user account provided)” is no longer displayed when you submit backup jobs using the NetWare Agent with the node level pre or post command and the command is successfully executed.
[T245323] Backup jobs now prompt and wait for the new tape to be inserted if the tape to which the data is appended is full. Previously, when you delay inserting the new tape these jobs used to load the first tape again.
[QO84317] [T146442] [T146433] BrightStor ARCserve Backup no longer experience data base corruption issues while backing up the databases.
[T1A5361] You can enable high density auto-selection mode for Network Appliance filers by adding the DWORD value bPreferHighDensityForNetapp to the following key before NAS device configuration and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\TapeEngine\CONFIG
```
[T36A345] Portal databases are now displayed properly after you install and configure the BrightStor ARCserve Backup Agent for Mircrosoft Sharepoint.
[T16C666] The Device Manager now properly displays the virtual libraries that are configured on a DELL PV132T library after installing BrightStor ARCserve Backup r11.5 Service Pack 2.
[T245322] BrightStor ARCserve Backup has been updated to ensure that the new tapes are properly recognized when you eject the magazine and change the tapes while using the SEAGATE DAT auto loader.
To implement this functionality, add the DWORD value DoorShutInit to the following key, set the value to 1 and restart the tape engine:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\base\tapeengine\CHANGER_CFG
```
[T245328] [T16C664] BrightStor ARCserve Backup has been updated to ensure the following:
- Copy jobs now reliably copy the files having the same long and short names to the shared folder on the remote machine.
- Multiplexing jobs now correctly display the data size and the throughput in the job log and in the pop-up window.
- Tape engine no longer improperly logs the message “Running in ATOMIC mode” in the tape.log file when you set the debug level to 1.
[T2D2588] BrightStor ARCserve Backup has been updated to improve the speed of the tapecopy jobs when you have all the sessions on the same source tape.
[QO82963] BrightStor ARCserve Backup has been updated to reliably append the backup data to the removable devices and the remote FSDs. Also, support for the following devices has been added in this release:
- STK SL500
- Sony AIT5 Drive (SDX-1100)
- Overland ARCvault
- Dell TL2000
- Quantum Ultrium 3 Drive
- Quantum Superloader 3
- IBM 33522LX
- Sony LIB-D81
[QO82900] BrightStor ARCserve Backup has been updated to provide the following:
- VM Protection on Windows 2003 Server Proxy to backup VM machines that reside on SAN attached devices using VMware Consolidated Backup (VCB). This requires BrightStor ARCserve Backup for Windows r11.5 SP2 to be installed on the VCB proxy server.
- VM Protection using VCB utilities that reside on ESX Server 3.0 Service console. This requires BrightStor ARCserve Backup r11.5 SP2 for Linux to be installed on the ESX Service console.
  Note: VM Protection on virtual machines is also supported using BrightStor ARCserve Backup r11.5.
[T36A388] Backup jobs are no longer duplicated when you have the virtual SQL server and virtual node under the same physical node and you perform dynamic backup of virtual SQL server and virtual node.
[T245324] The Restore Manager now correctly display the UNIX volumes as volumes in the session view when you mount the volume in a sub-directory of a directory other than root.
[T245327] Restore jobs now restore access control lists (ACLs) when you use the Client Agent for Windows and you have the Restore and Preserve File Attributes and Security Information option set to OFF in the Global Settings window.
[T245325] Rotation backup jobs no longer display garbled character in the job log when you enter Japanese string in the Job Description section.
[T2D2591] The Restore Manager now properly sorts the Document Level Microsoft Exchange Inbox folders by date in the Restore by Session view when the Inbox folder contains sub-folders in it.
[T577010] BrightStor ARCserve Backup no longer terminates abruptly with the code 0x1e while performing backup jobs when you have BrightStor ARCserve Backup r11.5 base version installed on your machine.
[T577011] BrightStor ARCserve Backup no longer terminates abruptly with the code 0xD1 when you have BrightStor ARCserve Backup r11.5 SP2 and the Agent for Open Files installed on your machine.
[T146443] Inventory by Vault and Inventory by Media are now reliably generated when you run Media Maximization Option (MMO) Vault cycle.
[T46B162] BrightStor ARCserve Backup has been updated to ensure that you no longer receive buffer under run related errors while performing multiplexing backup jobs of the local server.
[T5A6031] BrightStor® ARCserve® Backup Client Agent for NetWare has been updated to dynamically detect the mounted or dismounted volumes while backing up a NetWare server machine.
[T36A390] BrightStor ARCserve Backup Manager will no longer hang when you browse the Oracle instance that has several tablespaces.
[T46B159] When you use the Client Agent for Windows to submit the backup job with the Compare option enabled, the BrightStor ARCserve Backup server now performs the compare job successfully, even if source path folder name contains any special characters.

9.0 BrightStor ARCserve Backup for Windows r11.5 SP2 Readme

10.0 Welcome

The following sections provide information originally released with BrightStor ARCserve Backup for Windows r11.5 SP2 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3.

11.0 Operating System Support for BrightStor ARCserve Backup r11.5 SP2

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Operating System Support for BrightStor ARCserve Backup r11.5 SP1 and Operating System Support for BrightStor ARCserve Backup r11.5.

Support for the following operating systems has been added to the BrightStor ARCserve Backup for Windows base product, BrightStor ARCserve Backup Client Agent for Windows, and BrightStor ARCserve Backup Agent for Open Files.

VMware ESX Server version 2.5.3 on 32-bit
Windows Small Business Server 2003 R2 on 32-bit

11.1 Citrix Support for BrightStor ARCserve Backup r11.5 SP2

BrightStor ARCserve Backup for Windows base product, BrightStor ARCserve Backup Client Agent for Windows, BrightStor ARCserve Backup Agent for Open Files, and BrightStor ARCserve Backup Disaster Recovery Option support the following versions of Citrix:

Citrix Presentation Server 4.0 on x64
Citrix MetaFrame Presentation Server 4.0 Program Neighborhood on x64

Note: Disaster Recovery on Windows x64 is not supported, but you can install the Disaster Recovery Option on a 64-bit machine to perform remote disaster recovery of a 32-bit machine.

11.2 Supported Operating Systems for the Client Agent for OpenVMS for BrightStor ARCserve Backup r11.5 SP2

The BrightStor® ARCserve® Backup Client Agent for OpenVMS supports the following platforms:

VAX 6.2, 7.1, 7.2, 7.3
AXP 6.2, 7.1, 7.2, 7.3, 8.0, 8.1, 8.2

Note: For AXP versions 7.2, 7.3, 8.0, 8.1, and 8.2, the agent supports the ODS5 file system.

12.0 System Requirements for BrightStor ARCserve Backup r11.5 SP2

The following section provides system requirements for BrightStor ARCserve Backup.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5, and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections System Requirements for BrightStor ARCserve Backup r11.5 SP1 and System Requirements for BrightStor ARCserve Backup r11.5.

12.1 Agent for Oracle for BrightStor ARCserve Backup r11.5 SP2

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

Windows 2003 Service Pack 1 or Windows 2003 R2
Oracle Server version 8, 8i, 9, 9i, 10g and 10g R2
Oracle Fail Safe (OFS) version 3.3.1 on 8i, 3.3.2 on 8, 8i and 9i, 3.3.3 on 8, 8i, 9i and 10g, 3.3.4 on 9i, 10g and 10g R2
Oracle RAC 9i, 10g R1 and 10g R2

Note: BrightStor ARCserve Backup Agent for Oracle does not support Automatic Storage Management (ASM) for backup jobs submitted using the BrightStor ARCserve Backup GUI. However, ASM is supported for backup jobs that are submitted using the Oracle Recovery Manager (RMAN) command line.

13.0 Installation Considerations for BrightStor ARCserve Backup r11.5 SP2

No changes have been made to the installation considerations provided for BrightStor ARCserve Backup r11.5 SP1.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5, and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Installation Considerations for BrightStor ARCserve Backup r11.5 SP1 and Installation Considerations for BrightStor ARCserve Backup r11.5.

14.0 General Considerations for BrightStor ARCserve Backup r11.5 SP2

The following section provides general information to consider when using BrightStor ARCserve Backup for Windows.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5, and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections General Considerations for BrightStor ARCserve Backup r11.5 SP1 and General Considerations for BrightStor ARCserve Backup r11.5.

14.1 Start Storage Area Network (SAN) Server During Backup Jobs for BrightStor ARCserve Backup r11.5 SP2

BrightStor ARCserve Backup for Windows and UNIX has been enhanced to allow you to start or restart a server while jobs are running on other servers in a Cross Platform SAN with Windows and UNIX servers.

Previously, backup jobs running on one server could fail if you started or restarted a server in the same SAN.

14.2 Agent for Microsoft Exchange Server Data Encryption Support for BrightStor ARCserve Backup r11.5 SP2

The BrightStor ARCserve Backup Agent for Microsoft Exchange Server has been updated to support data encryption during backup jobs. You can protect your data so that it is not modified during transmission or while in storage. The data can only be accessed through an authenticated password that is used to encrypt and decrypt the data.

14.3 Microsoft SQL Server Support for BrightStor ARCserve Backup r11.5 SP2

BrightStor ARCserve Backup Agent for Microsoft SQL and the BrightStor ARCserve Backup database now support Microsoft SQL Server 2005 SP1.

14.4 Agent for OpenVMS V8.2 Support for BrightStor ARCserve Backup r11.5 SP2

The BrightStor ARCserve Backup Agent for OpenVMS now supports OpenVMS V8.2 for Alpha.

14.5 Support for AS/400 for BrightStor ARCserve Backup r11.5 SP2

The BrightStor ARCserve Backup for Windows r11.5 SP2 now supports AS/400 V5R2, V5R3 and V5R4.

Note: BrightStor ARCserve Backup no longer supports AS/400 V5R1 and any other older versions of AS/400.

14.6 Large File Support for AS/400 for BrightStor ARCserve Backup r11.5 SP2

BrightStor ARCserve Backup for Windows r11.5 SP2 can now back up AS/400 files larger than 2 GB.

14.7 Support for Network Data Management Protocol (NDMP) V4 for BrightStor ARCserve Backup r11.5 SP2

The BrightStor ARCserve Backup NDMP NAS Option now supports NDMP version 4 in addition to NDMP version 3.

Note: The NDMP NAS Option no longer supports NDMP version 2. If you are using NDMP version 2, contact CA Technical Support before you upgrade to BrightStor ARCserve Backup for Windows r11.5 SP2.

14.8 NDMP NAS Option for BrightStor ARCserve Backup r11.5 SP2

The following versions of NAS devices are certified for this release:

For Network Appliance devices:
- ONTAP Version 7.1

We recommend that you configure the filer to allow NDMP V4 communication by executing the following command on the filer console:

ndmpd version 4

In addition, ensure that all the filers are configured to 4.

For EMC (Celerra) devices:
- DART version 5.5
- NAS Server model: Celerra
DART 5.5 now supports exclude Filters and DDAR options. For more information on configuring EMC Celerra devices to support files and folder filters, see the EMC Celerra documentation.
To use Dynamic Device Sharing (DDS), set the value of ndmp.scsiReserve to 0. The default value of ndmp.v4oldTapeCompatible should be set to 1.

We recommend that you configure data movers to support NDMP V4 communication by setting the maxProtocolVersion parameter to 4. In addition, ensure that all data movers are configured to 4.

Note: ONStor, PROCOM, and EMC IP4700 are not certified at this time. If you have any of these uncertified devices or devices with uncertified firmware, contact CA Technical Support before you upgrade to BrightStor ARCserve Backup for Windows r11.5 SP2. For latest information on certified NAS Devices and their versions, see the Certified Device List on the product homepage.

14.9 Support for Quantum GoVault Devices for BrightStor ARCserve Backup r11.5 SP2

BrightStor ARCserve Backup for Windows r11.5 SP2 now supports Quantum GoVault devices for both FAT32 and NTFS formatted media.

14.10 Support for Additional Devices for BrightStor ARCserve Backup r11.5 SP2

BrightStor ARCserve Backup has been updated to support additional devices. For the complete list of devices supported, see the Certified Device List on the product homepage.

Note: Device Support Update 6 includes a list of device patches for the BrightStor ARCserve Backup r11.5 SP2 release.

14.11 Restore an Ingres Database for BrightStor ARCserve Backup r11.5 SP2

If you want to restore an Ingres database to the previous backed up status, you should first delete the existing journal files in the Ingres\Ingres[II]\ingres\jnl\default\<dbname> folder (where dbname is the name of the database).

14.12 Best Practices Guide for VMware® ESX Server™ Backup for BrightStor ARCserve Backup r11.5 SP2

For information about how you can leverage virtual machines to manage backup and recovery operations, see the Best Practices Guide for VMware® ESX Server™ Backup at http://supportconnect.ca.com.

15.0 Known Issues for BrightStor ARCserve Backup r11.5 SP2

The following section provides information regarding issues known to exist in BrightStor ARCserve Backup r11.5 SP2.

For information originally identified during the release of BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5, and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Known Issues for BrightStor ARCserve Backup r11.5 SP1 and Known Issues for BrightStor ARCserve Backup r11.5.

If you have licensed BrightStor ARCserve Backup using Enterprise licensing (using the ca.olf file) and you receive the error “315C component not licensed, please contact your license representative” when you run backup jobs, perform the following procedure to resolve this error:
1. Restart all of the BrightStor ARCserve Backup services. To do so, run the following (located in the BrightStor ARCserve Backup home directory):
```
cstop.bat

cstart.bat
```
2. Restart the manager.
If you have licensed the BrightStor ARCserve Backup Agent for Microsoft SQL Server using Enterprise licensing (using the ca.olf file) and you receive the error “31SQ component not licensed, please contact your license representative” when you run backup jobs, restart the CA BrightStor Backup Agent RPC Server service to resolve this error.
If you have not updated the BrightStor ARCserve Backup server Domain Name Server (DNS) record, the Disaster Recovery machine cannot connect to the BrightStor ARCserve Backup server. To avoid this problem, add the correct IP address in the hosts file.
System State restore jobs fail if you select the option Stop the Cluster if Necessary to Restore the Cluster Database.
If you press Enter, Esc, or Alt-F4 when recovering Windows XP or Windows 2003 systems, the Automated System Recovery process is interrupted and the recovery fails.
One Button Disaster Recovery (OBDR) is not supported on OEM versions of Windows XP SP2. You must have the Microsoft shipped CD in your possession to perform OBDR.
You must enter user names and passwords when using the ca_backup and ca_restore commands on 64-bit machines.
You must stop all services related to master databases when restoring master databases on Windows 2003 with Microsoft SQL Server 2005 or Microsoft SQL Server 2005 SP1. If you do not stop these services, the restore operation fails with the error “E8601 Failed to connect agent. (AGENT=\\machinename\dbasql@MSSQLSERVER, EC=Connection failed. User does not exist or does not have enough rights to connect to SQL Server. Please check and update the SQL Server user properties.)”
The BrightStor ARCserve Backup Disaster Recovery Option is not supported on 64-bit machines.
In the BrightStor ARCserve Backup for Windows r11.5 SP1 online help, the help page for the error message “E8537” is not displayed.
If you perform a disaster recovery backup using the DRSCAN session utility and copy the disk using disk staging copy policy, the copied session will contain incorrect disaster recovery information of the C drive. You cannot restore the C drive.
When you specify a Pre/Post option on a Windows NT-based system, the Windows NT Agent service may fail and cause the backup to fail. To remedy this issue, you must enable the CA Universal Agent service to interact with the desktop.
To enable interaction with the desktop
1. From the Windows Start menu open the Run dialog. In the Run field, enter services.msc and click OK.
  The Windows Component Services window opens.
2. Select the Local Services.
  Browse to and right-click CA BrightStor Universal Agent, and then select Properties from the pop-up menu.
  The CA BrightStor Universal Agent (Local Computer) dialog opens.
3. Select the Log On tab.
  Under Local System account, select the Allow service to interact with desktop option and click Apply.
  Click OK to close the CA BrightStor Universal Agent (Local Computer) dialog.
4. Restart the CA BrightStor Universal Agent service.
  The CA BrightStor Universal Agent can now interact with the desktop and the Windows NT Agent services will not fail when you execute a command that includes a –pre/post argument.
5. Close the Windows Component Services dialog.

15.1 Known Issues for the Client Agent for OpenVMS for BrightStor ARCserve Backup r11.5 SP2

The following issues relating to the Client Agent for OpenVMS are known to exist in this release:

Synonyms and Alias names are not supported for the Client Agent for OpenVMS.
The Client Agent for OpenVMS does not support backup and restore filters.
You cannot stop backup jobs before they finish. However, if you want to stop a backup job, shut down the agent process on the OpenVMS machine.
Backup sessions are not password protected. You can restore backed up sessions without providing the correct session password.

15.2 Known Issues for the Client Agent for AS/400 for BrightStor ARCserve Backup r11.5 SP2

The following issues relating to the Client Agent for AS/400 are known to exist in this release:

For large backup jobs, disable the File Estimate option in the Backup Manager.
You cannot browse the Client Agent for AS/400 tree when backup jobs are running.
When there has been no activity for ten or more minutes and you want to browse the Client Agent for AS/400 tree, a message that the connection is lost is displayed. Click the OK button to continue browsing.

16.0 Documentation Changes for BrightStor ARCserve Backup r11.5 SP2

The following section provides information about items that have not yet been changed in the product documentation for BrightStor ARCserve Backup for Windows r11.5 SP2, but that affect the information in that documentation.

For information originally identified during the release of BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5, and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Documentation Changes for BrightStor ARCserve Backup r11.5 SP1 and Documentation Changes for BrightStor ARCserve Backup r11.5.

In the BrightStor ARCserve Backup for Windows r11.5 SP1 readme, the Disaster Recovery Option for BrightStor ARCserve Backup r11.5 SP1 section states that Windows 2003 R2 x64 and Windows 2003 Itanium SP1 (Remote Disaster Recovery only) are supported. This should have stated that disaster recovery on Windows 2003 R2 x64 is not supported, but you can install the Disaster Recovery Option on a 64-bit machine to perform remote disaster recovery of a 32-bit machine.
In the BrightStor ARCserve Backup for Windows r11.5 SP1 Getting Started Guide, the Backward Compatibility section states that the BrightStor ARCserve Backup r11.5 server can back up data using agents from BrightStor ARCserve Backup r11.1, BrightStor ARCserve Backup r11, BrightStor ARCserve Backup Version 9.01, BrightStor Enterprise Backup Version 10.5 Service Pack 1, and BrightStor Enterprise Backup 10.0 Service Pack 5.
This should have stated that the BrightStor ARCserve Backup r11.5 server can back up data using agents from BrightStor ARCserve Backup r11.1, BrightStor ARCserve Backup r11, BrightStor ARCserve Backup Version 9.01, BrightStor Enterprise Backup 10.5 Service Pack 1. BrightStor Enterprise Backup 10.0 Service Pack 5 should not have been mentioned because it is no longer supported.
The Restore Destination Tab section of the BrightStor ARCserve Backup for Windows NDMP NAS Option Guide for r11.5 SP1 states that you can restore NAS server data only to another NAS server. This should have stated that you can restore NAS server data to the original or a different NAS server.
In the BrightStor ARCserve Backup for Windows Microsoft Volume Shadow Copy Service Guide for r11.5 SP1 the Backup Wizard section states the following:
Use the Backup Manager to perform more customized backups using filters, options, and scheduling.
This should have stated:
Use the Backup Manager to perform more customized backups using options and scheduling. Using filters should not have been mentioned because the use of filters is not supported.
In the BrightStor ARCserve Backup for Windows Microsoft Volume Shadow Copy Service Guide for r11.5 SP1 the Restore Wizard section states the following:
Use the Restore Manager to perform more customized restores using filters, options, and scheduling.
This should have stated:
Use the Restore Manager to perform more customized restores using options and scheduling. Using filters should not have been mentioned because the use of filters is not supported.

The W6698 section of the BrightStor ARCserve Backup for Windows r11.5 SP1 online help states the following

MUX: Session = %u hit SPAN condition during restore. Current TAPE: name = %s, randomID = %u, sequence = %u

This should be:

MUX: Session = %u hit SPAN condition during restore/scan/merge. Current TAPE: name = %s, randomID = %u, sequence = %u

The W6698 section of the BrightStor ARCserve Backup for Windows r11.5 SP1 online help states the following
This indicates that the session which is getting backed up hit Early Warning on tape.
This should be:
This indicates that the session which is getting processed hit Early Warning on tape.
The Update eTrust® Antivirus Signature section of the BrightStor ARCserve Backup for Windows r11.5 SP1 online help states the following
The path from where the Inodist.exe is to be executed is
```
C:\Program Files\CA\Sharedcomponents>inodist /cfg inodist.ini
```
This should be:
The path from where the Inodist.exe is to be executed is
```
C:\Program Files\CA\Sharedcomponents\ScanEngine>inodist /cfg inodist.in
```

17.0 Published Fixes for BrightStor ARCserve Backup r11.5 SP2

The complete list of published bug fixes for this product can be found through Published Solutions on SupportConnect.

17.1 Included Fixes for BrightStor ARCserve Backup r11.5 SP2

The following section provides information regarding fixes included in this release of BrightStor ARCserve Backup r11.5 SP2.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 SP1 and BrightStor ARCserve Backup for Windows r11.5, and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the sections Included Fixes for BrightStor ARCserve Backup r11.5 SP1 and Included Fixes for BrightStor ARCserve Backup r11.5.

[T46B080] [T46B104] Multiplexed Grandfather-Father-Son (GFS) jobs that back up NDS and your local machine now properly back up the BrightStor ARCserve Backup database and Disaster Recovery machine.
[T36B189] System state backup jobs no longer generate erroneous warning messages.
[T46B081] [T46B077] [T46B106] Copy jobs in a cluster environment where both the source and destination of the local machine use the cluster virtual server name no longer appear to stall at the beginning of the job.
[T367173] [T46B083] [T46B125] Executing prune jobs no longer truncates Microsoft SQL logs.
[T46B069] [T46B072] [T46B102] You can now disable The Delete Files After Backup option. To implement this fix set the value of the following key to 1:
```
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Backup\DisableDeleteSource
```
[T46B071] You can now restore database sessions backed up using global encryption without erroneously generating the message “the session password is invalid.”
[T46B074] [T5A6003] Backup jobs now no longer erroneously create cst*.tmp files in the c:\root and BAB Home\Temp directories.
[T46B076] [T46B087] [T46B111] Server backup jobs now properly log information about the ntuser.dat.log files.
[T36B195] The German language version of BrightStor ARCserve Backup now properly sorts files displayed in the Database Manager by size.
[T36B204] You can now successfully run backup jobs on servers with names containing _IP.
[T36B205] When you modify and resubmit backup jobs, earlier results for the jobs are now properly cleared.
[T36B209] Specified options are now properly retained when you modify Microsoft SQL Server backup jobs.
[T36B210] You no longer receive error messages for backup jobs when the C:\Documents and Settings folder was not selected on the default drive during the BrightStor ARCserve Backup installation.
[T46B026] Backup jobs containing more than 10 nodes no longer fail at the end of node when it clears up the used memory.
[T46B035] Multiplexing master jobs now reliably back up Disaster Recovery and BrightStor ARCserve Backup databases.
[T46B036] [T46B092] [T46B126] The Job Engine now runs reliably when 30 or more IP addresses are specified.
[T46B047] Events are now properly identified and logged when you enable messaging logging to the Windows Event viewer from the Server Admin. To implement this fix, add the DWORD value KeepEventID to the following key and set the value to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\base\log
```
[T36A285] [T36A301] [T36A328] BrightStor ARCserve Backup no longer copies SYS and INF files of disabled Network Interface Cards (NIC) to the Machine Specific Disk (MSD) folder after full backups of systems with multiple NICs. This allows the size of the MSD to be less than 1.4 MB and you can successfully copy all the files to your floppy disk.
[T36A306] [T36A330] The Backup Manager now supports passwords with more than 20 characters.
[T367182] The cabatch command now reliably executes PRECOMMAND, POSTCOMMAND, PREPOSTUSER, and PREPOSTPWD job scripts.
[T1A5298] Multiplexing backup jobs no longer stall during execution.
[T367170] Remote Sybase database backup jobs now correctly unpackage the options for the database.
[T367172] All of the columns in the Job Status/Job Queue list now sort automatically when the list is refreshed.
[T36A261] The option Distinguish Media by Name Only is now properly retained when you modify backup jobs with that option enabled.
[T31A342] [T31A367] You can now reschedule backup jobs to occur in the past using the command line.
[T31A353] [T31A339] BrightStor ARCserve Backup has been updated with the following:
- The correct icon now appears when you restore BrightStor ARCserve Backup Agent for Lotus Domino or BrightStor ARCserve Backup Agent for Oracle files larger than 500 MB backed up using database agents.
- You can now restore files to alternate locations without generating invalid destination messages.
- You can now reliably restore selected files rather than entire sessions.
[T1A5312] [T1A5309] [T1A5322] The BrightStor ARCserve Backup Agent for Open Files no longer causes systems to fail with stop codes D1, C2, or 44.
[T2AC192] The Job Status Manager now displays the correct time when you use ca_qmgr to reschedule job times for machines with Daylight Savings time enabled in the Sydney, Australia time zone.
[T2AC199] BrightStor ARCserve Backup now correctly prompts for the full backup tape when you restore files from five-day GFS rotation schemes with one full backup job and four incremental backup jobs.
[T2D2462] Pre-node commands now skip nodes with errors and continue backing up the remaining nodes.
[T2D2494] [T2D2523] Jobs restoring multiple sessions to remote machines are no longer reported as successful if there are errors.
[T2D2496] [T2D2524] Backup rotation schedules now allow you to use the character * in media names. To implement this fix, add the DWORD value ShowStarName to the following key and set the value to 1:
```
HKEY_LOCAL_MACHINE\Software\ComputerAssociates\BrightStor ARCserve Backup\ASMgr
```
[T31A346] [T31A347] GFS rotation schedules no longer allow you to use hyphens (-) in media pool prefixes using the Num Lock key.
[T146378] Tapes are now properly identified in the Restore by Session view when you use the default VLDB database.
[T146381] BrightStor ARCserve Backup has been enhanced to ensure that tapes are now properly added to the scratch set when you format new blank media and specify a media pool. To implement this fix, add the DWORD value FormatToScratch to the following key and set the value to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Database
```
[T146383] By default, BrightStor ARCserve Backup now designates a three year expiration date for new sequence one tapes and a one year expiration date for all other new tapes without expiration dates used for backup jobs.
[T146398] You can now reliably run Catalog merge or scan operations with CRC check enabled on multiplexed tapes. Previously, these jobs failed with the error message “W3896 Unable to position session trailer (MEDIA=XXXXX, SESSION=X, EC=FFFFFFFF).”
[T16C531] The Tape engine no longer fails randomly.
[T16C540] Backup jobs are no longer reported as successful when no files are backed up.
[T16C542] Backup jobs using Exabyte VAX-2A tape drives now run reliably without generating errors.
[T16C546] The Backup Manager no longer fails when you format blank tapes in the Alaska time zone.
[T2D2450] You can now restore the system states for remote Client Agents without causing the IIS service on the server to stop.
[T16C551] [T16C598] You can now run multiplexed backup jobs using Microsoft Internet Small Computer System Interface (ISCSI).
[T16C558] You can now reliably run incremental multiplexed backup jobs to tape and use the tapecopy command to copy the data to file system devices.
[T16C562] The tapecopy command now reliably copies multiplexed backup jobs that span several tapes.
[T16C565] File system devices and groups are now properly retained when you restart your machine. To implement this fix, add the DWORD value BootDelay to the following key and set the value to 1:
```
Hkey_Local_Machine\Software\ComputerAssociates\base\tapeengine\CHANGER_CFG
```
[T16C578] BrightStor ARCserve Backup has been updated to ensure that the Tape Random ID format in the BrightStor.log is now consistent.
[T16C588] Using the tapecopy command –fDstMux switch, you can now copy data from multiplexed source tapes to normal tapes or file system devices.
[T16C590] The Tape engine no longer fails randomly when multiplexed backup jobs are submitted.
[T1A5241] The BrightStor Domain Server service now starts reliably when the Windows system is configured with 200 or more IP addresses.
[T146368] BrightStor ARCserve Backup has been enhanced to ensure that databases are not updated with incorrect information after inventories are performed if the tape barcodes do not match the internal serial numbers of the tapes and if valid database records do not exist for both the internal serial numbers and the barcodes. To implement this fix, add the DWORD value BarcodeCompare to the following key and set the value to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\TapeEngine
```
[T146371] BrightStor ARCserve Backup has been updated to change the debug message Found Non-Cheyenne Tape to Found Non-ARCserve Tape in the Tape log.
[T146372] The Vlibmrg.log file is no longer improperly filled up with the messages “Checking if ABSL xxxx device is regular library” and “Found matching VIRTUAL device\chatn \chatn .”
[T1A5267] [T1A5302] [T1A5319] You can now reliably restore individual mailboxes from multiplexed backup jobs.
[T1A5269] The ca_devmgr -force -erase 3 0 0 command now runs reliably.
[T1A5283] The Tape Engine service no longer fails at startup.
[T1A5303] [T1A5304] [T1A5318] The tapecopy command now reliably copies all sessions for multiplexed backup jobs.
[T1A5305] [T1A5301] [T1A5321] You can now use the tapecopy command to copy multiplexed backup jobs without causing the Tape Engine service to fail.
[T367153] You can now reliably run Client Agent for Windows system state backups on Windows Server 2003 machines with registry entries larger than 524284 bytes.
[T46B058] Full node backup jobs no longer incorrectly generate the error messages “E9001 Unable to allocate memory. (SIZE=2116) and E2244 Unable to numerate agent disk items. (AGENT=XXXXXXXXXX (XXX.XXX.XX.XXX).”
[T367176] Backup jobs now run properly when you use the cabatch command on remote machines.
[T46B053] You can now browse and back up directories from the Backup Manager using the BrightStor ARCserve Backup Client Agent for Windows if you do not have access rights to the directory.
[T36B194] BrightStor ARCserve Backup Client Agent for Windows system state backup jobs are now performed reliably and no longer generate the error messages W3422 Unable to save registry key. (KEY=SYSTEM, EC=NO SYSTEM RESOURCES) and W3404 Unable to open file (FILE=C:\windows\system32\config\SYSTEM, EC=SHARING VIOLATION).
[T46B078] [T46B111] BrightStor ARCserve Backup Client Agent for Windows System State backup jobs now reliably open and back up the ntuser.dat file.
[T46B051] BrightStor ARCserve Backup now reports source drive or directory information in the Activity log when you use BrightStor ARCserve Backup for NetWare to backup the Client Agent for Windows.
[T36B200] BrightStor ARCserve Backup has been updated to ensure that changes made to whole node backup jobs backing up UNIX machines using the Client Agent are properly retained.
[T46B045] The Job Log now properly records the elapsed time for Client Agent for NetWare backup jobs.
[T46B052] [T46B063] [T46B122] The Pre-Flight Check now runs properly when you back up NetWare servers over the network.
[T46B095] The Pre-Flight Check now runs properly when you back up mailboxes without generating the message “Failed to connect to the client agent.”
[T31A350] The Restore by Query option now properly displays files containing non-English characters backed up by the Client Agent for NetWare.
[T2D2485] You can now successfully back up mounted volumes when one of the volumes is unmounted on NetWare servers using Client Agent for NetWare.
[T2D2492] [T2D2521] The Backup Manager now properly displays the NetWare Service item under Network when the Client Agent for NetWare is installed on Windows.
[T1A5296] File names with Japanese characters now display properly in the BrightStor ARCserve Backup Agent for Open Files Settings dialog when you add them to Groups.
[T367168] Brick Level Microsoft Exchange backup jobs packaged as Full Backups in rotation jobs now run properly as full backup jobs. Previously, despite the settings in the Agent Options dialog, if the rotation job ran as an incremental job, the Brick-Level backup job also ran as an incremental job.
[T367158] Backups of Microsoft Exchange databases now run properly without receiving unrecognized commands.
[T36A284] [T36A293] You can now properly browse the BrightStor ARCserve Backup Agent for Lotus Notes from the Backup Manager without the error message “E8601 Failed to connect agent. (AGENT=\\XXX\dbanotes, EC=Cannot load agent DLL module.)”
[T367183] BrightStor ARCserve Backup has been updated so that the Job Property Status no longer incorrectly indicates that BrightStor ARCserve Backup is stopping the Information Store service.
[T367166] You can now reliably configure the Microsoft Exchange server with the name “server.”
[T31A333] The registry value of ExchangeFullBackup now works reliably on local backup jobs or backup jobs that use Named Pipes.
[T36A278] You can now reliably perform Restore by Session operations for Lotus Notes servers containing the character / in the name.
[T367155] Multiplexing backup jobs now reliably back up Lotus Domino data files only once.
[T36A251] Oracle agent backup jobs now run successfully on machines with SAP ITS Web Application 6.20 SAP portal installed.
[T36A280] You can now properly view all active Agents for Oracle when browsing the physical nodes in cluster environments.
[T36A270] BrightStor ARCserve Backup has been updated to ensure that the Agent for Oracle reliably backs up archive logs when the ARCHIVELOG has multiple directories.
[T36A291] [T36A296] You can now reliably back up archive logs using the Agent for Oracle if you specify sequence numbers with more than 5 digits.
[T46B030] BrightStor ARCserve Backup has been updated to ensure that Oracle databases on UNIX machines are reliably backed up during full node backup jobs.
[T46B034] You can now reliably use Oracle RMAN for backup jobs with control files with names of more than 20 characters.
[T36A252] [T36A257] BrightStor ARCserve Backup has been updated to ensure that you no longer see incorrect Agent for Oracle volume named dbaora7@sid, in the Client Agent source view.
[T2D2449] [T2D2500] [T2D2525] The Purge Log After Backup Oracle database option is now properly retained when you modify jobs backing up Oracle databases using the Client Agent for UNIX.
[T36A309] [T36A331] The Multistreaming option can now be enabled or disabled manually.
[T36A310] [T36A333] You can now reliably initiate command line On-Bar jobs.
[T36A259] BrightStor ARCserve Backup now reliably copies disaster recovery information to specified alternate locations.
[T36A308] [T36A332] [T36A311] The Disaster Recovery Option has been updated to ensure that Machine-specific Disk files are properly copied to the alternate location for disaster recovery information without specifying the domain name of the alternate location.
[T36A303] [T36A304] [T36A329] The BrightStor ARCserve Backup Disaster Recovery Option has been updated to ensure that, when you generate CD Bootable images for Windows 2000 on servers running Windows 2003 or Windows XP, SCSI files for the Windows 2003 or Windows XP operating system are no longer included in the boot kit.
[T2D2461] You can now reliably back up disaster recovery sessions.
[T1A5275] You can now reliably add Ontap 7.0 NAS Filers to your device configuration.
[T1A5310] You no longer receive erroneous prompts for additional tapes when restoring Network Attached Storage (NAS) backups.
[T1A5287] You can now reliably back up the Network Attached Storage (NAS) data without receiving the error “E8511 when running a NDMP Backup”. In addition, you no longer receive the error “E8511 – Failed to connect with client agent” during file estimation.
[T1A5291] [T1A5320] The BrightStor ARCserve Backup Network Attached Storage (NAS) Option has been updated to connect reliably to the client agent. Previously, during the file estimation phase of NDMP backup jobs, the option would fail to connect to the client agent, generating errors.
[T1A5272] You can now reliably configure NAS servers.
[T146374] New blank tapes are now properly formatted with barcodes when you update the database during GFS rotation jobs using the BrightStor ARCserve Backup Tape RAID Option.
[T16C547] RAID jobs submitted from distributed servers in SAN environments with StorageTek L700 or LTO IBM Ultrium drives on QLogic Fibre Controllers now run properly. Previously, these jobs failed with the error “E6300 NT SCSI PORT ERROR.”
[T1A5252] All GFS rotation jobs now run as scheduled when backing up to RAID 1 devices.
[T1A5273] BrightStor ARCserve Backup has been enhanced to improve performance for tapecopy jobs using multiplexing tapes.
[T1A5284] Full library inventories are no longer performed after BrightStor ARCserve Backup fails over to another node in cluster environments.
[T16C523] BrightStor ARCserve Backup has been updated to ensure that full inventories are no longer performed when a single tape is exported or imported on ADIC FastStor and HP SSL1016 libraries.
[T16C528] Tape information for HP SSL1016 auto loader is now updated reliably when a tape is exported or imported.
[T16C538] [T16C569] [T245222] BrightStor ARCserve Backup has been updated to ensure that the Tape engine no longer fails randomly and that auto-inventories are no longer started when magazines are changed on the following autoloaders:
- HP DAT 20/40
- SEAGATE DAT
- HP SSL1016
- COMPAQ 20/40G
- COMPAQ 12/24G
- SONY TSL-11000
- HP C5713A
- DELL PV-132
- DELL PV-122
To implement these updates, add the DWORD value DoorShutInit to the following key and set the value to 1:
```
Hkey_Local_Machine\Software\ComputerAssociates\base\tapeengine\CHANGER_CFG
```
[T16C559] You can now replace physical drives in StorageTek ACSLS libraries (for example, StorageTek 9310) shared by two platforms without causing drives to go off line after auto-configuration and tape engine startup.
[T16C560] BrightStor ARCserve Backup has been updated to ensure that, if backup jobs span more than 13 tapes, the slots no longer keep updating after the backup job is complete.
[T16C561] BrightStor ARCserve Backup has been updated to ensure that the Device Manager properly displays SCSI devices on Windows machines with IBM Raid controllers installed.
[T16C566] You can now reliably copy multiplexing tapes to file system devices using the –g switch. Previously, these tapecopy jobs failed with the error “W3884 Unable to position catalog file.”
[T16C582] BrightStor ARCserve Backup has been updated to ensure that the following libraries are properly detected and can be configured:
- Tape drive 40GB DLT1
- BNCHMARKDLT1 in HP C7145
[T16C563] [T16C530] BrightStor ARCserve Backup has been updated to ensure that you can reliably configure standalone libraries on distributed servers with multiple Host Bus Adapters.
To configure standalone tape libraries, add the DWORD value Shared to the following registry key and set the value to 0 for NOT- Shared:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\TapeEngine\Scsi<n>
```
Where:
n indicates the adapter number of the library.
[T16C592] [T16C609] You can now configure locally attached tape libraries on distributed servers in SAN environments.
[T16C593] [T16C530] [T16C607] [T16C596] You can now reliably run multistreaming jobs launched from different servers in SAN environments sharing the same device groups.
[T36B235] You can now reliably modify jobs backing up multiple agent machines.
[T36B233] Modified jobs now retain the option settings you specified for BrightStor ARCserve Backup Agent for Sybase.
[T36B231] BrightStor ARCserve Backup has been updated to ensure that server group Scan jobs now continue when one of the servers has no backup jobs.
[T36B229] BrightStor ARCserve Backup has been updated to ensure that the Append Media option is now retained when you modify GFS rotation jobs.
[T36B226] Filter options set on node level are now properly retained when you modify job sources.
[T46B143] You can now set more than 32 file filters for backup jobs.
[T46B142] Restore jobs now skip corrupt data in backup sessions and continue with the next valid session.
[T58F010] You can now use the Import function on the Device Manager for IBM 3584 configured with more than 100 mail slots.
[T46B134] The ca_restore command now properly restores the most recent Microsoft SQL database backup sessions.
[T2D2540] You can now use regular tapes on WORM-capable standalone drives for backup jobs with the global Overwrite Media option enabled.
[T2D2539] You can now browse NAS devices on UNIX machines.
[T2D2536] [T2D2535] BrightStor ARCserve Backup now displays localized media names in the Calendar view.
[T2D2470] UNIX Oracle database backup jobs now properly save passwords in the job scripts.
[T16C627] BrightStor ARCserve Backup has been updated to ensure that backup jobs now run properly on VXA-3 tape drives. Previously, after installing BrightStor ARCserve Backup r11.5 Device Patch 4, these jobs failed with NT SCSI port errors.
[T146407] BrightStor ARCserve Backup has been updated to ensure that restore jobs now work reliably when you select specific files that are located at the end of very large sessions.
[T146410] BrightStor ARCserve Backup now correctly displays pool names in the Activity log when you submit Custom backup jobs using media pools.
[T146413] You can now submit tapecopy job from distributed Storage Area Network (SAN) servers without causing Tape Engine problems.
[T1A5325] BrightStor ARCserve Backup has been updated to ensure that the BrightStor® ARCserve® Backup Agent for Open Files uses CPU appropriately when you install it on cluster servers.
[T5A6003] [T46B116] BrightStor ARCserve Backup no longer retains .cst files in the TEMP directory after all jobs have been completed.
[T1A5338] BrightStor ARCserve Backup has been updated to ensure that hardware compression is now properly disabled when you add the DWORD value FormatWithoutHardwareCompression to the following key and set the value to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\base\TapeEngine\CONFIG
```
[T1A5341] Tape Engine no longer fails intermittently while running on tapeeg.dll or raid.dll.
[T146417] You can now reliably convert the BrightStor ARCserve Backup default VLDB database to Microsoft SQL.
[T5A6009] You can now use the ca_log command –yes switch properly.
[T58E014] System state restore jobs no longer change protected folders in the following registry:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
```
[T5A6007] BrightStor ARCserve Backup now correctly displays File System Devices status when you restart the tape engine.
[T146416] [T146412] BrightStor ARCserve Backup is updated to export tapes after tapecopy jobs are completed for Enterprise Option for IBM 3494. To implement this, you can do one of the following:
- Specify the –ex flag in the tapecopy command.
- Select the Export option from the Backup Options window in the Backup Manager when you create or modify a backup job.
[T146414] BrightStor ARCserve Backup has been updated to ensure that, when you erase RAID tapes with barcode labels, the tapes are now properly identified as destroyed and no longer display their original tape names after the Tape Engine restarts. However, for RAID tapes with barcode labels that were erased before you applied this fix, you must reformat the tapes or use the Database Manager to manually delete the original media records from the database.
[T245280] BrightStor ARCserve Backup has been updated to ensure that software compression continues to be enabled when you disable hardware compression.
[T2D2558] [T245265] BrightStor ARCserve Backup has been updated to ensure that tapecopy jobs no longer fail when you use standalone tape drives and the target tapes span multiple drives. You are now properly prompted to mount a blank tape to continue the job.
[T5A6008] BrightStor ARCserve Backup no longer displays your password in the log when you run backup jobs from the Job Scheduler.
[T2D2554] You can now reliably restore encrypted backup data.
[T2D2553] BrightStor ARCserve Backup no longer duplicates serial and sequence numbers of multiplexing tapes when you merge tapes to another server. In addition, all sessions are now displayed accurately in the Restore by Session view.
[T245278] BrightStor ARCserve Backup now properly updates the Job Progress meter in the Job Status window.
[T245279] The Full Node flag is no longer set by default when you fully select shared folders in the Preferred Shares tree.
[T2D2552] The tapecopy command switch -qPastTime now reliably identifies existing backup sessions.
[T2D2548] Makeup jobs now package the correct drives when backing up your local machine and the preferred share after the original job failed in the first session.
[T245267] The Message engine no longer stops when you restart the tape server and close the Tape Alert dialog.
[T2D2549] BrightStor ARCserve Backup now displays shared SAN disks managed by Veritas Volume Manager when you browse the virtual cluster name using the Client Agent for Windows.
[T2D2547] The Client Agent for Windows now accurately reports error messages in the Activity log for incomplete jobs.
[T2D2546] The BrightStor ARCserve Backup Client Agent for NetWare now reports the correct job results for failed jobs. Previously, the client agent reported jobs as successful when they had actually failed with errors.
[T2D2545] [T2D2541] The Client Agent for Windows has been updated to synchronize its behavior with the BrightStor ARCserve Backup base product when backing up the C:\Windows\temp folder. Previously, the client agent did not back up this folder while the base product backed up the folder itself but did not back up the data under the folder.
[T2D2544] BrightStor ARCserve Backup has been updated to ensure that multistreaming rotation jobs run correctly if sub-jobs cannot start on the day they are scheduled to run and are forced to start on the next (unscheduled) day.
[T245276] [T245275] You can now run the ca_backup command with the –source and –filesystem switches without generating errors.
[T1A5339] The Tape Engine has been enhanced to improve performance for multiplexing tapecopy jobs.
[T2D2543] Source priority is now honored when you run Microsoft Exchange Document Level backups with file system file backups.
[T245274] The job scheduler can now properly run generic jobs that execute applications that open windows.
[T2D2542] BrightStor ARCserve Backup has been updated to ensure that catalog files are reliably copied to tapes when you disable the Leave Catalog Details on Disk option in the staging policy. In addition, when you migrate and purge the session you no longer receive the warning message “W1533 [STAGING] Failed to Copy Catalog File from (SourceTapeName= xxx ID=xxx, SessionNo=x) to (FinalTapeName = xxx, ID=xx, SessionNo=x), EC=3.”
[T245271] The ca_dbmgr –show summary command no longer includes files in the total on the Session detail records line after they have been deleted by database prune jobs on Raima databases.
[T245272] The Tape engine now starts systems with LSI Logic LSI 20320-R adaptors properly. Previously, after applying BrightStor ARCserve Backup for Windows r11.5 SP1, starting these systems generated SCSI port errors.
[T36A344] You can now reliably restore multiple Lotus Domino databases with at least one database larger than 500 MB.
[T36A347] BrightStor ARCserve Backup now supports disaster recovery on distributed Windows 2003 machines.
[T36A348] BrightStor ARCserve Backup now reliably copies DRV folders to specified alternate locations.
[T36A341] You can now install the BrightStor ARCserve Backup r11.5 SP1 versions of the Agent for Oracle and the Agent for SAP R/3 in environments with BACKINT installed.
[T36A343] The Backup Manager now correctly displays Microsoft SQL database instances under virtual Microsoft SQL nodes with more than one active node in cluster environments.
[T36A340] You can now enter virtual Microsoft SQL server names when configuring the BrightStor ARCserve Backup Agent for Microsoft SQL.
[T36A342] You can now reliably restore very large Microsoft SQL databases.
[T46B136] Local and remote server backup jobs that do not use the Client Agent for Windows now run without stalling.
[T1A5335] The Agent for Open Files has been updated to ensure that it runs properly on machines on which Trend Micro anti-virus products have been installed.
[T16C617] You can now use Tandberg AT3200 libraries without installing the BrightStor ARCserve Backup Tape Library Option.
[T16C618] You can now run backup jobs on primary and distributed servers on either sides of a firewall in SAN environments. To implement this feature, add the DWORD value KeepAlivePing on the distributed server under the following registry key and set it to 1 :
```
Hkey_local_Machine\software\computerAssociates\Brightstor ARCserve Backup\base\tapeengine\CONFIG
```
[T16C620] Multistreaming backup jobs that span several sequences now reliably export tapes at the end of each backup when you set the global Export option.
[T245282] [T245259] [T245214] Agent for Microsoft Exchange Server makeup jobs now reliably reflect the source settings of the original jobs.
[T16C618] You can now run backup jobs on primary and distributed servers on either sides of a firewall in SAN environments. To implement this feature, add the DWORD value KeepAlivePing on the distributed server under the following registry key and set it to 1 :
```
Hkey_local_Machine\software\computerAssociates\Brightstor ARCserve Backup\base\tapeengine\CONFIG
```
[T16C612] You can now reliably configure IBM 3494 tape libraries that have fibre channel enabled drives assigned to different platforms.
[T16C615] You can now use dynamic device group configuration for GFS or rotation jobs on file system devices.
[T16C619] Backup jobs now start properly while tapecopy jobs are running on distributed servers in SAN environments.
[T16C623] BrightStor ARCserve Backup has been updated to ensure that RAID sets are retained in the Device Configuration settings when you have RAID 0 devices configured and you dismount and remount the magazine.
[T16C626] Multiplexing tapecopy jobs to multiplexing media no longer fail with the error “Error creating a tsi handle, make sure your tape engine is turned on. rc[38]” when you have more than 1000 sessions on a source tape.
[T16C628] BrightStor ARCserve Backup now reliably runs multiplexing backup jobs with more than 32 sub-jobs.
[T31A375] BrightStor ARCserve Backup now reliably creates child jobs and backs up Microsoft SQL databases in multistriping backup jobs on 64-bit machines.
[T31A380] You can now reliably modify Document Level backup jobs using Microsoft Exchange Organization on clusters.
[T31A381] BrightStor ARCserve Backup now properly identifies folders in the Agent for Microsoft Exchange Server mailboxes view. These folders are also properly saved in job scripts as having been selected for backup when you resubmit these jobs.
[T31A384] BrightStor ARCserve Backup now correctly restores only the brick level folders you select.
[T31A396] Transfer protocol settings are now retained for Microsoft Exchange backup jobs.
[T31A376] You can now reliably configure brick level jobs for Microsoft Exchange servers.
[T31A378] You can now view mailboxes in other domains when browsing at the Document Level with the Agent for Microsoft Exchange.
[T58C001] BrightStor ARCserve Backup has been updated to ensure that error messages are no longer logged in the qprint.log file during backup jobs.
[T46B071] [T46B121] You can now restore database sessions backed up using global encryption without erroneously generating the message “the session password is invalid.”
[T16C630] BrightStor ARCserve Backup has been updated to ensure that you no longer receive the following warnings and error messages when multiple append jobs are running at the same time:
- W3851 Media is full.
- E63638 Buffer under run occurred during backup at Drive [xx].
- E8003 Media manually ejected from drive[xx].
- E6500 Client connect to tape failed.
[T16C631] BrightStor ARCserve Backup no longer erroneously reports jobs as successful when these jobs fail with the error message “E63638 Buffer under run occurred.”
[T245204] Backup jobs with Sony SDX-800V as target devices no longer generate the error “E3803 Invalid file trailer signature. (SIG=2be62572)” when spanning sessions.
[T245256] You no longer receive warning messages when you restore a read only directory to its original location with the Restore and Preserve Directory Attributes and Security Information option set.
[T31A372] GFS rotation jobs no longer reschedule themselves to a date later than seven years.
[T46B056] BrightStor ARCserve Backup has been updated to correct the following decryption issues:
- You can now properly restore Oracle databases backed up with local file system drives with global encryption.
- You can now properly back up file system drives (for example, C) from one server and database agents from another node using global encryption and restore the database agent sessions without generating the error "E3482 Failed to decrypt data (EC:27)." Previously, if you restored this data using database agents, these errors would be generated.
[T245284] The barcode reader in libraries now works reliably when the library configuration wizard is used.
[T245189] The Japanese language version of BrightStor ARCserve Backup now properly displays the Print Preview of reports on remote machines.
[T2D2538] You can now reliably use virtual cluster names to connect to the Client Agent for Windows when you use IBM ServeRAID Logical Disks as shared disks in cluster environments
[T2D2537] You can now view session details after merging pruned NetWare sessions.
[T245261] You can now restore the files in the BrightStor ARCserve Backup\LOG folder to their original locations using the Client Agent for Windows with the Restore files to their original locations option disabled.
[T36A335] Rotation jobs now use the correct media when you schedule cross-platform backup jobs.
[T36A337] You can now reliably browse large UNIX or Linux Oracle databases (more than 300 tablespaces) from Windows machines.
[T245250] [T245260] Device management jobs created from the Schedule tab of the Format dialog now set correct expiration dates for library tapes.
[T31A373] Document Level Agent for Microsoft Exchange backup jobs now report skipped folders in the Activity log.
[T2D2527] [T2D2509] Cross-platform tapes in the ELO_POOL media pool are no longer erroneously moved to the ELO_POOL Scratch Set when you enable Media Pool Maintenance.
[T2D2530] [T2D2515] You can now specify that you are prompted with a warning message in the Activity log when backup jobs span multiple tapes. To enable this warning, add the DWORD value EnableSpanWarning to the following key and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\BrightStor ARCserve Backup\Base\Task\Backup\
```
[T2D2526] [T2D2507] You can now reliably perform tapecopy operations using WORM-capable tape drives and WORM-capable target tapes without the error “Connect to target tape failed, rc[239].”
[T2D2531] [T2D2517] Target tapes are now reliably merged into databases during tapecopy operations without the error “target tape failed to merge into database and ASDB_SetSessionMap Failed rc[-3].”
[T46B103] [T46B073] You can now reliably restore backed up Macintosh files to their original locations using BrightStor ARCserve Backup on Windows 2000 without receiving E3452 error messages.
[T46B105] [T46B100] Data Migration jobs now stop completely after encountering hardware errors.
[T46B107] [T46B097] BrightStor ARCserve Backup has been updated to ensure the start times for multiplexing master jobs are properly recorded when you use Microsoft SQL Server as the BrightStor ARCserve Backup database.
[T46B108] [T46B093] BrightStor ARCserve Backup has been updated to ensure that File System Device directories are properly backed up when you back up local nodes to tape.
[T46B109] [T46B088] [T46B094] You can now reliably set the Staging Group Chunk size to 64 KB to enhance backup job performance
[T36B221] [T36B208] You can now reliably clear the Reset File Access Time option when you modify backup jobs.
[T36B222] [T36B213] You can now select multiple servers and provide security credentials in the Security and Agent Information dialog before submitting backup jobs.
[T46B110] [T46B089] Disk staging GFS differential backup jobs are now properly purged at the time specified in your staging policy.
[T46B114] You can now exclude application agents from full node backup jobs without changing the type of backup from dynamically-packaged to explicitly-packaged. Previously, if you excluded application agents from full node backup jobs, the jobs would become selective, explicitly-packaged backup jobs and any volumes added to a node after the job was scheduled would not be included in the backup.
[T36B223] [T36B218] BrightStor ARCserve Backup has been updated to ensure that options that do not apply to your jobs are disabled when you create full rotation backup jobs.
[T36B224] [T36B219] BrightStor ARCserve Backup now accurately reports all applicable error messages in the Activity log.
[T46B117] [T46B075] Backup jobs now reliably prompt you to specify the first and subsequent tapes to use for rotation jobs and predict the tape to use the next time the rotation job runs.
[T46B119] [T46B086] BrightStor ARCserve Backup has been updated to improve performance for single-source staging node jobs.
[T36B225] [T36B217] The ca_qmgr –stop command now properly and completely stops jobs.
[T46B120] [T46B068] You can now change source server names using the /RS parameter for backup jobs submitted using cabatch.exe with existing scripts.
[T2D2528] [T2D2510] You can now reliably back up and restore data using the Data Growth option from BrightStor ARCserve Backup for Laptops & Desktops installed on cluster shared disks with the Client Agent for Windows to BrightStor ARCserve Backup servers.
[T2D2532] [T2D2520] The Client Agent Admin now properly displays connection names longer than 22 characters.
[T2D2533] You can now back up BrightStor ARCserve Backup for Laptops & Desktops servers from Linux servers.
[T46B112] [T46B085] You can now use cluster node names for System State backup jobs using the Client Agent for Windows.
[T46B113] [T46B091] The message “d:\ is skipped from backup, the device is busy” has been upgraded from an informational message to an error message.
[T46B124] [T46B123] BrightStor ARCserve Backup has been enhanced to improve performance for remote server backup jobs that do not use the Client Agent for Windows.
[T146403] You can now use tapecopy.exe to copy sessions from multiplexing tapes to file system devices without the error message “Message W3896 Unable to position session trailer. (MEDIA=XXX, SESSION=X, EC=DCB ERROR NO MEMORY).”
[T31A369] [T31A356] The Agent for Lotus Domino now reliably restores data.
[T36A327] [T36A322] You can now restore Oracle databases to alternate servers.
[T36A334] [T36A313] RMAN restore jobs on BrightStor ARCserve Backup using Microsoft SQL as the alternate database now run properly without impacting the Message engine.
[T146408] [T146404] BrightStor ARCserve Backup has been updated to ensure that duplicate tape sequences are not created when you rerun tapecopy jobs that failed because there were no available tapes to which to span.
[T245251] [T245212] System State restore jobs now properly restore MSCS Cluster databases without generating the message “E3250 Error interacting with cluster. (EC=Overlapped I/O operation is in progress).”
[T245252] [T245218] The Backup Manager now properly displays expanded server trees for Windows 64-bit Edition machines with multiple NIC enabled.
[T16C610] Backup jobs submitted from distributed servers in SAN environments now run reliably after tapes are imported or exported from HP ESL tape libraries.
[T1A5324] [T1A5317] BrightStor ARCserve Backup has been updated to allow you to use Dynamic Device Sharing (DDS) when restoring NAS data.
[T245253] [T245219] Backup jobs now run reliably on Windows XP and Windows 2003 machines that use Z as the CD-ROM drive letter.
[T146397] The global or RAID Export Media option now properly exports tapes when you back up to disk staging devices with a tape device as the final destination of your job.
[T146399] BrightStor ARCserve Backup now properly displays the status of slots in locally attached libraries in SAN environments with one or more distributed servers.
[T146411] You can now have tapes ejected when spanning to another sequence without having to enable the Eject Media option on the Operation tab of the Backup Manager. To eject tapes when spanning, create the DWORD value AlwaysEjectOnSpan in the following and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Backup\AlwaysEjectOnSpan.
```
Note: This is not applicable if you are using a tape library.
[T36B206] The Agent for Open Files console has been updated to accurately display license status.
[T245257] [T245217] The BrightStor ARCserve Backup Disaster Recovery Option has been updated to ensure that the DRScanSession utility now properly performs remote disaster recovery.
[T31A368] [T31A352] The Agent for Microsoft Exchange Server now reliably runs incremental Document Level backup jobs.
[T31A370] [T31A358] BrightStor ARCserve Backup now properly displays the database, brick level, and Document Level icons when you browse Microsoft Exchange 5.5 cluster virtual node IP addresses.
[T31A371] [T31A363] The Agent for Microsoft Exchange Server now reliably runs Document Level backup jobs.
[T245258] [T245223] Mail server names are no longer truncated in the Backup Manager.
[T146402] Multiplexing backup jobs now reliably export tapes when you set the Export All Tapes After Job option.
[T16C583] Backup jobs now run reliably on EXABYTE VXA-2 tape drives on IDE without the error message “E3855-Unable to position media” for EXABYTE VXA-2 tape drive on IDE.
[T16C595] You can now run tapecopy jobs multiple times to the same destination media pool.
[T16C597] You can now reliably run tapecopy jobs on distributed servers in SAN environments. In addition, you can run simultaneous tapecopy jobs on different servers in SAN environments using the same device groups in shared changer devices.
[T16C606] You can now reliably configure IBM 3494 tape libraries using Device Configuration without generating the error message “Failed to open library manager” in the ibmlmrdc.log.
[T16C608] [T16C594] You can now reliably run disk staging jobs with more than 50 sessions simultaneously.
[T16C611] Quick inventories, launched after tapes have been removed from slots, no longer display the name of the removed tape and the slots are correctly identified as empty.
[T16C613] You can now run multiple tapecopy jobs in SAN environments, with each server in the environment running one of the jobs, without causing the Tape Engine to fail on distributed servers when the tapes span.
[T31A374] BrightStor ARCserve Backup has been updated to ensure that you no longer receive the message Unrecognized command during Exchange database backup operations. Previously, this message appeared when the database exceeded thresholds during data transfer.
[T2D2514] BrightStor ARCserve Backup now reliably displays the source in the Backup Manager tree when modifying jobs.
[T2D2549] BrightStor ARCserve Backup now displays shared files when you browse the virtual cluster name using the Client Agent for Windows.
[T31A355] You can now view mailboxes when browsing at the Document Level with the Agent for Microsoft Exchange.
[T1A5313] Restore jobs on NetApp Ontap 7.0.3 now work during spanning sessions without the error “AE0279 Restore of Session # to Server Filer01 Failed (RET 1).”
[T31A360] You can now configure the Agent for Microsoft Exchange Server on a Domain Controller, and BrightStor ARCserve Backup now properly generates the ExchVerify.log.
[QO74086] BrightStor ARCserve Backup has been updated to support Microsoft SQL Server 2005.
[QO74774] You can now run multiplexing backup and restore jobs that span several sequences on Sony SDX 500C or 700C tape drives without generating warnings or errors.
[QO75067] BrightStor ARCserve Backup has been updated to ensure that backup jobs with the Append option no longer overwrite valid data on tapes when they follow successful restore jobs. This previously caused restores of particular sessions to fail with the error “E3802 Invalid File Header Signature.”
[QO75196] BrightStor ARCserve Backup has been enhanced to support long file paths.
[QO75197] BrightStor ARCserve Backup has been updated to ensure that restore jobs no longer modify the disk signature of a non-shared disk when you restore the backup folder from a shared disk to the non-shared disk.
[QO75874] BrightStor ARCserve Backup has been updated to ensure the following when you restore Agent for Lotus Domino or Agent for Oracle database files that exceed 500 MB and were backed up using the Client Agent for Windows:
- You no longer receive the error messages when you submit restore jobs to alternate locations.
- BrightStor ARCserve Backup now correctly displays the status of the datafiles.
- You can now reliably restore the selected datafiles. The entire session is no longer backed up when you have selected the datafiles to restore.
[QO76318] You can now reliably view tape libraries attached to NAS filers after you run Device Configuration to configure EMC Celerra 5.4 and manually enter a changer name.
[QO76448] Backup jobs no longer create multiple cst*.tmp files in the C: root and BAB Home\TEMP directories.
[QO78087] [T36A336] You are no longer prompted to reinstall the network drivers when you perform disaster recovery and reboot the Windows 2000 machine.
[QO78165] [T2D2512] [T2D2522] BrightStor ARCserve Backup has been updated to ensure that you no longer receive the error message “an attempt was made to move the file pointer before the beginning of the file RC=87 RC=131” when you back up sparse files using software compression.
[QO79440] BrightStor ARCserve Backup has been updated to support EMC Celerra 5.5, DDAR and filters.
[QO72372] [QO74009] [QO74087] [QO78545] [QO78909] [QO76166] [QO78545] [QO78909] BrightStor ARCserve Backup has been updated to support additional devices. For the complete list of the devices supported, see the Certified Device List on the product homepage.
[QO79641] You can now safely uninstall the Agent for Microsoft SQL Server without corrupting the Windows Registry and then reliably restart the server after the uninstallation is complete.

17.2 Included Fixes for BrightStor ARCserve Backup r11.5 SP1

The following section provides information about the fixes included in this release:

[T2D2348] BrightStor ARCserve Backup has been enhanced to ensure that you no longer receive file header or trailer invalid signature errors when merging, scanning, or comparing NetWare NDS sessions using (at minimum) the BrightStor ARCserve Backup version 9.01 Client Agent for NetWare. Scan, merge, and compare all run properly with tapes created using (at minimum) the BrightStor ARCserve Backup Client Agent for NetWare version 9.0.
For tapes created using the BrightStor ARCserve Backup version 7.0 Client Agent for NetWare, you must add the registry DWORD value OldNDSSession under the following and set the value to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Common
```

[T3D3017] BrightStor ARCserve Backup now properly records messages (without duplicates) when the Enable Message Logging into Windows Event Log setting is enabled.

[T3D3022] BrightStor ARCserve Backup has been updated to ensure that the Retry Open Files operation executes properly when the Retry Open Files option and the Disable File Estimate options are both selected in the Backup Options.

[T3D3026] The Client Agent no longer maintains connections to the backup drive root after backup jobs are finished, allowing you to format the backup drive without restarting the Client Agent.

[T3D3055] BrightStor ARCserve Backup has been updated to ensure that you can restore more than two drives with quota information in the same job and that the quota information for the additional drives is accurately restored.

[T3D3059] The BrightStor ARCserve Backup Agent Management GUI now properly displays job details from the log file for computers with names of three characters or fewer.

[T3D3063] [T245203] [T245246] All messages are now reliably recorded in the BrightStor.log.

[T16C349] BrightStor ARCserve Backup has been updated to ensure that jobs no longer fail with the error "E3801 Invalid Session Header Signature" on EXABYTE Mammoth2 tape drives.

[T36A109] You can now back up Oracle instances with tablespaces with many data files.

[T36A166] The Agent for Microsoft SQL Server now properly displays all Microsoft SQL databases, regardless of the characters used in the names.

[T245032] [T2D2529] BrightStor ARCserve Backup now reliably displays the source in the Backup Manager tree when modifying jobs.

[T245033] BrightStor ARCserve Backup has been updated to ensure that you can successfully merge tapes backed up with the File scanning option set to off without generating the error "E11033: The volume was backed up without file scanning, cannot merge session."

[T245057] The BrightStor ARCserve Backup Tape Engine no longer changes the layout of disks when you delete and recreate one of the partitions on a disk. Previously, if a file system device existed in the partition, the Tape Engine changed the layout of the entire disk to one partition.

[T3D3050][T3D3052] You can now successfully back up the System State on Windows XP or Windows Server 2003 without generating W3422 and W3404 warnings in the activity log, even if the registry contains a single entry with more than 523284 bytes.

[T245065] BrightStor ARCserve Backup now reliably retries open files when you select the Retry After Job option.

[T245157][T245150][T245158][T245067] BrightStor ARCserve Backup has been updated to ensure that the BrightStorMgr.exe process now closes properly when you close the Manager.

[T245140] The BrightStor ARCserve Backup log no longer displays the tape alert message "A drive inside the library has been taken offline" when drives in HP C5713A (40x6 AL), HP DAT72x6 AL, and HP C1557A (24x6 AL) devices are being cleaned.

[T245145] If you have enabled tape alert on changers that support tape alert, as soon as drive cleaning operations finish, you are now alerted when cleaning tapes have been exhausted.

[T245182] You can now restore backed up folders from shared disks to non-shared disks without modifying the disk signature of the non-shared disk.

[T369167] Write Once Read Many Media support messages have been added to the BrightStor ARCserve Backup base product in Simplified Chinese, French, German, Italian, and Japanese for Windows NT 4.0 and Windows 2000.

[T1A5205] BrightStor ARCserve Backup has been updated to ensure that you can now shut down machines running both BrightStor ARCserve Backup and VC++ .net without generating application errors.

[QO66651] [T146370] [T2D2534] BrightStor ARCserve Backup has been updated to ensure that tapes are no longer incorrectly moved from the save set to the scratch set when you use Microsoft SQL Server as the alternate BrightStor ARCserve Backup database.

[T16C512] BrightStor ARCserve Backup has been updated to ensure that, if you append an Exchange backup to a tape after restoring the sessions, you can successfully restore the same (or older) sessions, without generating error messages.

[T3D3015] [T3D3019] BrightStor ARCserve Backup has been updated to ensure that the Message Engine Service starts properly on machines with multiple processors and with Microsoft Service for UNIX 3.0 installed.

[T36A079] [T36A080] [T36A104] The Disaster Recovery Option has been updated to support the Japanese versions of Windows 2000 Server with SP4 and Windows 2000 Advanced Server with SP4.

[T245115] BrightStor ARCserve Backup has been updated to ensure that it properly recognizes tapes in the scratch set and save set slots in media pools. Previously, when rotation jobs mounted tapes from a particular media pool scratch set, the job would not finish.

[T245116] BrightStor ARCserve Backup can now successfully back up three-node jobs when the second node is for the Agent for Microsoft SQL Server and the tape spans while the second node is being backed up. Previously, the job failed with the error "E3841 Unable to find session number" (MEDIA=testmedia, SESSION=22, EC=EARLY WARNING) during verification when trying to find the third node.

[T245120] The Backup Manager now properly and reliably displays Media Pool status on the Destination tab.

[T245123] System State backup jobs no longer erroneously generate the following error and warning when long Active Directory DNS names are set and NTFRS replica root values are set with the prefix \\?\:
- W3301 Unable to find directory. (DIR=\, EC=The filename, directory name, or volume label syntax is incorrect.)
- E3322 Unexpected return from find first file. Unable backup files after (FILE=\\?\c:\windows\sysvol\domain\*.*, EC=The network path was not found.)

[T245149][T245148] BrightStor ARCserve Backup now reliably backs up data in jobs that span two barcode tapes with the same media name when the "Overwrite Same Media Name, or Blank Media" backup option is enabled.

[T245185] BrightStor ARCserve Backup can now successfully run jobs submitted from the Job Scheduler Wizard.

[T245198] You can now successfully change the name of tape library RAID groups from GROUP0 using the Device Group Configuration dialog. Previously, the name was reset automatically to GROUP0 when the tape engine restarted.

[T326113] The Disaster Recovery Wizard now correctly displays tape information.

[T1A5295] The Agent for Open Files has been updated to ensure that you can now successfully back up open files without generating the message "the process cannot access the file because another process is accessing the file." Additionally, the agent has been updated to improve the speed of backup or restore jobs.

[T146388][T31A320] BrightStor ARCserve Backup Application Agent and BrightStor Enterprise Backup application agent buffer overflow code has been enhanced to avoid security vulnerabilities. This applies to the following products:
- BrightStor ARCserve Backup v9.01
- BrightStor ARCserve Backup Version 9 Agent for SQL for Windows
- BrightStor ARCserve Backup Version 9 Agent for Oracle for Windows
- BrightStor ARCserve Backup Version 9 Agent for SAP R/3 for Windows
This test fix supersedes QO70770.

[T31A288] The BrightStor ARCserve Backup Universal Agent and BrightStor Enterprise Backup Universal Agent buffer overflow codes have been updated to prevent security vulnerability. We strongly recommend that you immediately apply this security update to all systems utilizing any of the following products:
- BrightStor ARCserve Backup v9.01
- BrightStor ARCserve Backup v9.01 Client Agent for Windows
- BrightStor ARCserve Backup v9.01 Network Attached Storage (NAS) Option for Windows
- BrightStor ARCserve Backup v9.01 Agent for Oracle for Windows
- BrightStor ARCserve Backup v9.01 Agent for SAP R/3 for Windows

[T31A261] This service pack addresses a security vulnerability due to buffer overflow in the BrightStor ARCserve Backup Discovery Service. This security update should be applied to all Windows systems on which the BrightStor ARCserve Backup for Windows v9.0 base product and any BrightStor ARCserve Backup agents are installed.

[T3F8085] For Microsoft SQL Server, BrightStor ARCserve Backup has been updated to successfully back up more than 1500 databases.

[T16C408] BrightStor ARCserve Backup has been enhanced to ensure that you no longer receive the error "File header signature or stream signature is invalid" when restoring or verifying data from certain backup sessions (a backup session is a backup of a file system or database - backup jobs can contain multiple sessions). Previously, data corruption problems occurred during backups if, while the first session of a backup job was running, 1000 other backup sessions started and were completed. If a new backup session started (session 1001) while session 1 was still running, this session would be corrupted.

[T1A5182] Restore jobs no longer erroneously generate the error "N3941 Skip file - Marked as invalid. (FILE=File Path Name>" in the log file.

[T352094] You can now create encrypted session passwords when backing up data.

[T3D3023] BrightStor ARCserve Backup has been updated to include a Symbol Table File.

[T3D3018] Restore jobs on NetApp Ontap 6.4.x no longer create the full path structure from the volume root as the restore destination when the Do Not Create the Base Directories option is enabled.
Additionally, incremental and differential backup jobs no longer create Restore Symbol Table files at the volume root.

[T369134] BrightStor ARCserve Backup has been updated to correct the following issues:
- You can now back up databases from two Microsoft SQL Server instances in a single job without mixing databases from the second instance with databases of the same name from the first instance.
- You can now restore Microsoft SQL data to alternate locations.

[T1A5143] When you restore specific files using the Image Option, you now receive an error message if all of the specified files are not restored.

[T245178] When a restore job cannot replace a file, it creates either a ACT$xxxx file or a SYT$xxxx file in the same directory as the file that could not be replaced. Previously, if the file was under WINDOWS\System32\CatRoot, the digital signature of the driver would sometimes disappear after you rebooted the machine and an error indicating that the ACT$xxxx file could not be found would be recorded in the dberr.log. BrightStor ARCserve Backup now ensures that digital signatures no longer disappear after you reboot.

[T245184] BrightStor ARCserve Backup has been updated to ensure that, after you reboot your system (if files were active and could not be replaced while a full restore job was running), restored files now reflect the correct timestamps, not the time the restore job ran.

[T1A5296][T245191] File names containing Japanese characters are no longer garbled in the Agent for Open Files settings (ofawin.exe) when you add these names to groups.

[T245170][T245177] BrightStor ARCserve Backup now reliably backs up catalog.wci directories even when the catalog.wci directory is empty or has no changed files to back up (in differential backup jobs) and the Estimate File Size option is enabled.

[T245171] You no longer erroneously receive the message "Computer Associates Licensing - 3BAL - Component not licensed" when backing up data using the BrightStor ARCserve Backup r11.1 Oracle Agent for Linux.

[T46B066] BrightStor ARCserve Backup has been updated to correct the following decryption issues:
- You can now properly restore Oracle databases backed up with local file system drives with global encryption
- You can now properly back up file system drives (for example, C) from one server and database agents from another node using global encryption and restore the database agent sessions without generating the error "E3482 Failed to decrypt data."
- You can now restore data backed up using the Client Agent for Windows without generating the errors "AE0322 Failed to initiate the encryption library. Job aborted," and "E3482 Failed to decrypt data (EC27)." Previously, if you restored this data using database agents, these errors would be generated.
- You can now properly restore Linux data and preserve attributes. Previously, random, nonsense characters were restored with the data and the attributes were not preserved.

[T16C514] BrightStor ARCserve Backup has been updated to ensure that you can properly run Serverless backup and restore jobs when the backup spans tapes and that you can reliably run restore jobs if the world wide name is all zeros. In addition, BrightStor ARCserve Backup now supports the CISCO Serverless solution.

[T16C515] You can now run VSS backup jobs on Windows 2003 machines with Windows 2003 SP1 installed.

[T1A5232] BrightStor ARCserve Backup has been updated to ensure that you no longer receive the error "Ofant.exe - Entry point not found; The procedure entry point setEUCStatus could not be located in the dynamic link library service.dll" in the Windows Event Viewer.

[T1A5259] When you install the Agent for Open Files and reboot your machine, the Login dialog no longer loses focus.

[T245122] System State backup jobs no longer erroneously generate the following error and warning when long Active Directory DNS names are set and NTFRS replica root values are set with the prefix \\?\:
- W3301 Unable to find directory. (DIR=\, EC=The filename, directory name, or volume label syntax is incorrect.)
- E3322 Unexpected return from find first file. Unable backup files after (FILE=\\?\c:\windows\sysvol\domain\*.*, EC=The network path was not found.)

[T245124] BrightStor ARCserve Backup has been updated to ensure that Pre/Post commands for Preferred Shares/Machines nodes, set in the Pre/Post Option dialog, are saved when you save or run these jobs and that they execute properly.

[T245129][T245131] The registry value Every reboot, SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\SNMP, is no longer inserted in the following key after every reboot:
```
HKEY_LOCAL_MACHINE\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents
```

[T245144] You are now properly alerted if your cleaning tape is exhausted when you have tape alert enabled on devices that support tape alert.

[T245146] BrightStor ARCserve Backup now properly recognizes tapes manually replaced in slots on NEC LL0101H-0A FW=0002 libraries with IBM Ultrium-TD1 FW=16E0 drives. To enable this fix, create the DWORD value DoorShutInit in the following key and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStorARCserve Backup\Base\TapeEngine\CHANGER_CFG
```

[T31A315] [QO69236] BrightStor ARCserve Backup now supports NEC Cluster Server (CLUSTERPRO/ExpressCluster) r4.2, version 7.0 SE and LE. For more information about this support and for information about configuring BrightStor ARCserve Backup in an NEC Cluster Server environment, see the Administrator Guide.

[T31A311] BrightStor ARCserve Backup has been enhanced to support CLUSTERPRO/ExpressCluster in Active/Passive environments.

[T36A235] If you use Microsoft SQL Server as the BrightStor ARCserve Backup database, media pool definitions are no longer reset to zero when you submit rotation jobs.

[T36A244] BrightStor ARCserve Backup has been updated to address a potential security vulnerability caused by a buffer overflow condition in the Agent for Microsoft SQL Server.

[T3F8101] BrightStor ARCserve Backup has been updated to address a potential security vulnerability caused by a buffer overflow condition in the Agent for Microsoft Exchange Server.

[T3F8110] Document level backup operations with folder filters enabled now properly back up user mailboxes as defined in the parameters of the filters.

[T46B039] BrightStor ARCserve Backup now reliably runs backup jobs successfully even when Pre-job commands return the exit code -1.

[T245161] BrightStor ARCserve Backup has been updated to enhance the speed of restore jobs on NEC changers. Previously, restore jobs were slowed because tapes were returned to the home slot when each session finished. This behavior has been corrected.

[T3F8081] When browsing Microsoft SQL servers with large numbers of databases, BrightStor ARCserve Backup now properly displays all of the databases. In addition, full backup jobs now properly and reliably back up all of the databases on these servers and the RPC server no longer fails.

[T31A229] This service pack addresses a security vulnerability due to buffer overflow in the BrightStor ARCserve Backup Discovery Service. This security update should be applied to all Windows systems on which the BrightStor ARCserve Backup for Windows r11.1 base product and any BrightStor ARCserve Backup agents are installed.

[T367143] BrightStor ARCserve Backup has been enhanced to ensure that Document Level backup jobs no longer fail incorrectly with Error 8535.

[T245156] Japanese characters in the Day column name of the Calendar dialog now display correctly when you run BrightStorMgr.exe on Windows2003 English Edition with Multilingual/Multilanguage User Interface.

[T1A5279] The BrightStor ARCserve Backup NDMP NAS Option has been updated to ensure that it no longer intermittently generates exceptions and fails and it no longer generates false spanning conditions at the end of restore operations. In addition, you can now reliably restore directories from NAS backups and can successfully perform DAR restores.

[T245159][T3D3045] The BrightStorMgr.exe process no longer occupies nearly 100% of CPU utilization. In addition, if you shut down the manager and start it again, the manager opens properly.

[T245160] You can now successfully perform Disaster Recovery full backup jobs on Windows 2003 or Windows XP with 21 or more partitions.

[T245166][T245167] BrightStor ARCserve Backup has been updated to ensure that skipped files are properly reported and the correct job status is recorded for compare jobs that do not use the Client Agent.

[T245162] [T36A338] On Lotus Notes Servers with names containing the character O in the first or second byte, you can now use the Setup Wizard without generating the error "Setup cannot find the file "notes.ini" of item 1 on the drive and directory specified."

[T245164] The RDS.EXE process no longer increases memory usage each time you run a job.

[T245165] BrightStor ARCserve Backup has been updated to allow you to specify that tapes should be rewinded at the end of jobs. To specify this, create the REG_DWORD value DisableLazyRewind in the following registry key and set it to 1:
```
HKEY_LOCAL_MACHINE\Software\CA\BrightStor ARCserve Backup\Base\TapeEngine\CONFIG
```

[T245168] On Japanese language Windows servers, the Backup Manager now properly displays directory names when you expand parent directories in the source tree when the source is a UNIX or Linux machine viewed through the Client Agent.

[T245173] BrightStor ARCserve Backup has been updated to allow Disaster Recovery information to be copied to an alternate location without generating the error 1326 "Failed to establish connection" in the drcfgdll.log.

[T245176][T245174] BrightStor ARCserve Backup has been updated to ensure that you can open Event logs that were restored to different locations using the Client Agent.

[T245179][T245192] You can now remove and add changer slots from groups without causing the Tape Engine to fail.

[T245180] The Operation tab of the Global Options dialog now accurately indicates when the Do not Eject Media option is selected for modified jobs.

[T245188] You can now use the back arrow when browsing the Technical Support and eNews links in the Japanese version of BrightStor ARCserve Backup.

[T245194] You can now format MTF tapes using the ca_devmgr -format command. Additionally, the ca_backup command with the owritesameblaankany option specified can now write to MTF tapes without generating the error "W3831: Unable to find any Computer Associates media."

[T245196] You can now run multiple processes of ca_backup.exe -waitForJobStatus commands in parallel without generating erroneous exit status codes.

[T245195] In Japanese environments, the date format in the print preview of the Job Status Report has been updated to display in YYYY/MM/DD format.

[T16C549][T16C587] BrightStor ARCserve Backup has been updated to ensure that backup jobs with the Append option no longer overwrite valid data on tapes when they follow successful restore jobs. This previously caused restores of particular sessions to fail with the error "E3802 Invalid File Header Signature."

[T36B202] You can now properly restore Linux data and preserve attributes. Previously, random, nonsense characters were restored with the data and the attributes were not preserved.

[T245199] BrightStor ARCserve Backup has been updated to ensure that you can load media in C9264CB-VS80 without starting a full inventory.

[T1A5285] BrightStor ARCserve Backup has been enhanced to improve performance when you restore files to a machine on which the Agent for Open Files and Symantec Anti Virus are both installed.

[T31A337] You can now restore backed up folders from shared disks to non-shared disks without modifying the disk signature of the non-shared disk.

[T31A305] A security vulnerability has been found in the BrightStor ARCserve Backup Universal Agent Service for Windows and the BrightStor Enterprise Backup Universal Agent Service for Windows. We strongly recommend that you immediately apply this security update to all systems utilizing any of the following products:
- BrightStor ARCserve Backup r11.1
- BrightStor ARCserve Backup r11.1 Client Agent for Windows
- BrightStor ARCserve Backup r11.1 for Windows Agent for Oracle
- BrightStor ARCserve Backup r11.1 for Windows Agent for Microsoft Exchange Premium Add-on
- BrightStor ARCserve Backup r11.1 for Windows Enterprise Option for SAP R/3 for Oracle
- BrightStor ARCserve Backup r11.1 for Windows NDMP NAS Option

[T367144] BrightStor ARCserve Backup has been updated to successfully restore data on Lotus Notes servers with names that contain the character / without generating the error “E8601 Failed to Connect to Agent.”

[T46B074] Backup jobs no longer create multiple cst*.tmp files in the C: root and BAB Home\TEMP directories.

[T46B041] If you set job-level Pre/Post commands for a backup job, specifying that the job should run only if a particular exit code is received for the pre-command, the job now runs only if the specified exit code is returned. If the exit code is not received, the job fails.

[T146382] BrightStor ARCserve Backup has been enhanced to reliably start scheduled jobs when the Tape RAID Option is enabled.

[T245203] When Tape Alert is enabled, the Tape Engine now successfully runs full inventories of libraries with many slots.

[T245200][QO75044] Backup jobs with Sony SDX-800V as target devices no longer generate the error "E3803 Invalid file trailer signature. (SIG=2be62572)" when spanning sessions.

[T16C416] BrightStor ARCserve Backup has been enhanced to use tapes formatted by Windows Backup Exec.

[T36A287][T36A294] BrightStor ARCserve Backup now supports Disaster Recovery Boot Kit creation on the German version of Windows 2000 Professional with SP1 integrated CDs.

[T1A5289] You can now install the Agent for Open Files without causing random system crashes with stop code C2.

[T2D2481] You can now run successful consecutive tapecopy jobs using the -mTargetPool switch for the first and subsequent tapecopy. Previously, the subsequent tapecopy job failed unless you deleted or erased the target tape from the first tapecopy job.

[T31A335] The Agent for Microsoft Exchange Server has been updated to improve performance for document level (specifically, user mailbox level) browsing. To enable this fix, create the DWORD value DisableChaseReferrals in the following and set it to 1:
```
HKEYLOCALMACHINE\SOFTWARE\ComputerAssociates\BrightStorARCserve Backup\ExchangeDocumentAgent\Parameters\
```

[T31A336] BrightStor ARCserve Backup has been updated to ensure that you no longer receive the message Unrecognized command during Exchange database backup operations. Previously, this message appeared when the database exceeded thresholds during data transfer.

[T36A282] Physical nodes in clusters now display only the Agents for Oracle configured on active servers.

[T36A292] You can now back up archive logs with log sequences greater than 99999 without generating the error "Agent cannot find next archive log to back up."

[T36A288] Microsoft SQL Server instances are now reliably displayed in the manager when you restore master databases in Microsoft SQL clusters using the command prompt on physical nodes when the SQL server is in single user mode.

[T36A290] BrightStor ARCserve Backup now supports Microsoft SQL Server 2005.

[T36A289] BrightStor ARCserve Backup has been enhanced to support the Agent for Microsoft SQL Server on Windows 2003 64-bit operating systems.

[T31A332] BrightStor ARCserve Backup has been enhanced to support long file paths. For more information, see the readme file.

[T16C564] You can now start the Tape Engine on Seagate DAT DAT72 virtual tape libraries.

[T16C567] BrightStor ARCserve Backup no longer changes IBM Ultrium-TD2 tape drives to IBM Ultrium-TD1 tape drives after the Tape Engine starts and now properly recognizes LTO-II tapes (which hold 400 GB of data) as different from LTO-I tapes (which hold 100 GB of data) for tape libraries attached to Network Appliance filers. You can enable high density auto-selection mode for Network Appliance filers by adding the DWORD value bPreferHighDensityForNetapp to the following key before NAS device configuration and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\TapeEngine\CONFIG
```

[T16C570] After successful auto-configuration (from the Windows side) of StorageTek ACSLS libraries shared between Windows and UNIX platforms, the correct assigned drives are now reliably saved in the NLODRV.CFG file.

[T16C576] BrightStor ARCserve Backup has been enhanced to launch consecutive RAID GFS rotation jobs. Previously, after the first RAID job was finished, no other jobs could be launched.

[T245190] BrightStor ARCserve Backup has been updated to ensure that if you turn your Compression settings to Off from Device Management, the setting is not changed to On during media formatting. Previously, this setting was changed to On even when the registry setting FormatWithoutHardwareCompression was not set to 1.

[T16C579] You can now run multiplexing backup and restore jobs that span several sequences on Sony SDX 500C or 700C tape drives without generating warnings or errors.

[T16C572] BrightStor ARCserve Backup has been updated to ensure the following:
- In cluster environments without failover, after you successfully configure your SAN environment, the configuration is properly retained when you close and reopen the SAN Configuration dialog. In addition, physical server names added to clusters are also retained properly.
- BrightStor ARCserve Backup has been enhanced to allow you add a registry key to display physical node names and filter out virtual node names in cluster environments without failover enabled. To do so, add the following key to the registry:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Tapeengine\DisplayPhysicalNodes
```

[T245192][T245179] BrightStor ARCserve Backup has been updated to ensure that if you cancel the removal of changer slots from a group in the Device Group Configuration dialog, the slots are not removed. In addition, the Tape Engine now reliably starts after you cancel the removal

[T245184] BrightStor ARCserve Backup has been updated to display accurate timestamps for restored files. Previously, if the files were active and could not be replaced while a full restore job was running, the timestamp of the restored file was changed to the time when the restore job ran.

[T2D2482] Data backed up using the 64-bit Client Agent for Windows is now reliably and properly encrypted.

[T36B206] The Agent for Open Files console has been updated to accurately display license status.

[T16C573] The log file \Program Files\CA\BrightStorARCserveBackup\LOG\Tsk Jobxx.log no longer grows rapidly and uses all available disk space when backup jobs span tapes and blank media is not provided.

[T31A339] Lotus Domino backups of large database files (500 MB or larger) are now displayed correctly in the Restore Manager. Previously, database files were displayed incorrectly and, if selected for a restore operation, the entire session was restored along with the selected file.

[T1A5297] You can now reliably view tape libraries attached to NAS filers after you run Device Configuration to configure EMC Celerra 5.4 and manually enter a changer name.

[T16C584] You can now submit jobs simultaneously from a UNIX server and a Windows server without causing the job on the Windows server to fail.

[T36A300] BrightStor ARCserve Backup has been updated to allow you to install SAP applications (other than SAP/R3) on machines with the Agent for Oracle installed without erroneously generating the message: "Backup Agent error (260) - Backup Agent does not support SAP/R3. Please get SAP/R3 backup Agent."

[T36A299] The system path has been updated to properly include the Oracle DLL directory. Previously, when you configured the Enterprise Option for SAP R3 for Oracle, BrightStor ARCserve Backup returned the error "Failed to copy 'initsid.utl' file!" and, when you expanded the SAP R3 instance, BrightStor ARCserve Backup returned the error "Cannot find Oracle DLL from the system path. Please set system path properly to include Oracle DLL directory."

[T245087] You can now successfully restore data backed up from Client Agent for Windows remote nodes using specific session passwords without generating the error "AE0322 Failed to initiate the encryption library. Job aborted."

[T245081] BrightStor ARCserve Backup has been updated to accurately detect current tape status. Previously, if a tape was set to write-protected after it had been detected as a write-enabled tape cartridge in the inventory, backups finished successfully despite the write-protected tape status.

[T245076] BrightStor ARCserve Backup has been updated to accurately detect tapes in slots. Previously, tapes were not reliably detected in slots, generating the messages "W3831 Unable to find any media that can be used in this job" or "W3832 Unable to find a blank media" in the Activity log and the message "Error in search for tape for JobID[370]. EC=ENUM_TAPE_EXHAUSTED" in the Tape log.

[T245060] BrightStor ARCserve Backup has been updated to ensure that, if the Agent for Oracle is installed, the Universal Agent no longer holds the handles of Oracle data folders after Client Agent backup jobs finish.

[T245054] Unrecognized format tapes (for example, netvault) in changer slots no longer generate an exception in the manager during automatic inventory operations after the Tape Engine is restarted.

[T245050] You can now restore data from MTF tapes with names that have multibyte characters occupying the 23rd and 24th byte.

[T245028] Image Option merge jobs no longer fail with the messages "E11033: The volume was backed up without file scanning, cannot merge session" and "E3841: Unable to find session number."

[T245024] BrightStor ARCserve Backup has been updated to ensure that Japanese Kanji file names match restore queries.

[T245007] In Japanese, incorrect comment text on the Alert tab of the Configuration window of the Server Admin tool indicating that text is case sensitive has been corrected to indicate that the text is case insensitive.

[T245002] BrightStor ARCserve Backup has been updated to allow the Unicenter^® Network and Systems Management (Unicenter^® NSM, formerly known as Unicenter^® TNG) Integration Option (CSTNGX.EXE) to create a managed object for BrightStor ARCserve Backup on Windows 2003 machines in the Business Process View and Unispace of the Unicenter NSM repository.

[T3D3048] BrightStor ARCserve Backup has been updated to allow the BrightStor ARCserve Backup v9.01 Client Agent for NetWare (running in a BrightStor ARCserve Backup 11.0 Windows environment) to restore NDS objects to their original location without generating the error "E3814 invalid session/encryption password."

[T3D3037] The error E11063, indicating that an object identifier is duplicated, is no longer generated unnecessarily.

[T3D3029] The Client Agent for Windows no longer keeps a connection to the backup drive root after backup jobs are finished. Previously, the client agent kept a connection to the backup drive root after backup jobs finished so the backup drive could not be formatted unless the agent was restarted.

[T245125] If you use the floppy-based Disaster Recovery method (local or remote) for a Windows 2000 server (rather than the more efficient CD recovery), see the readme file for information on how to update your installation.

17.3 Included Fixes for BrightStor ARCserve Backup r11.5

The following section provides information about the fixes included in this release:

[T245023] BrightStor ARCserve Backup has been enhanced to ensure that the Restore by Query option now displays Japanese Kanji filenames properly.
[T46B009] You can now back up NetWare NDS using multistreaming or multiplexing backup jobs without having the agent reject the job because it is still busy processing file system backups.
[T46B019] Tapecopy jobs now create random tape IDs if an IDR switch is provided. Previously, if you ran a tapecopy job and erased the target tape, the source tape database records were also deleted because both tapes had the same name and tape ID. Tapecopy now gives target tapes a different tape ID.

[T16C516] The user field in SAN configuration is no longer limited to 23 characters.

[T245074] Deleted files are no longer lost when the Delete After Backup option is enabled and a media error occurs before the backup can be completed and the files cannot be restored from the tape.

[T2AC193] Tapecopy jobs no longer stop running if you log off of Windows.

[T146366] [T3D4050] You can now modify jobs that use media pools in the Destination Tab without clearing the media pool selection when you refresh the screen.

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

[T2D2445] If you install BrightStor ARCserve Backup on a Windows system other than Windows 2000, the Job Detail log now displays Windows System Options. Previously, regardless of the Windows system, the Job Detail log displayed Windows 2000 Options.

[T36B155] You can now add multiple distributed servers to a primary server using the SAN configuration utility. Previously, if you added multiple distributed servers with the utility, you could not see all the distributed servers.

[T3F8074] Oracle backup jobs no longer fail in error with the message “E8604 Failed to start backup. (DBNAME = XXX, EC = Backup Agent Error (261) “Backup Agent cannot process the request.”

[QO67815] (T1A5246) You can now safely and reliably restore from multiplexing backup jobs using IBM Ultrium tape drives.

[QO66654] (T46B020) BrightStor ARCserve Backup has been enhanced to ensure that the correct number of tapes are maintained in the save set and moved from the save set to the scratch set when you use Microsoft SQL Server as the alternate BrightStor ARCserve Backup database.

[T16C533] You can now reliably format tapes from the Device Manager interface even if blank tapes occupy any slots.

[T245126] BrightStor ARCserve Backup has been enhanced to strengthen security when restoring data backed up using the Client Agent for Windows.

[T2D2454] (T245126) During system state backups, the client agent now properly backs up all registry related files.

[T1A5237] [T1A5238] - BrightStor ARCserve Backup has been updated to ensure that the Agent for Open Files no longer fails with an error indicating that another process is accessing the file on 32-bit and 64-bit machines.

[T2D2446] - BrightStor ARCserve Backup has been updated to ensure that the Client Agent for Windows opens properly on 64-bit machines.

[T1A5229] - BrightStor ARCserve Backup has been updated to ensure that volumes freeze properly when using the Image Option on Windows 2003 with SP1.

[T36A238] - Disaster recovery information is now generated properly on Windows 2003 SP1.

[T16C529] - BrightStor ARCserve Backup has been updated to ensure that the virtual tape engine no longer disconnects erroneously when the tape engine is started after applying Windows 2003 SP1.

[T146376] - BrightStor ARCserve Backup has been updated to ensure that the job queue is properly loaded when using the Advanced Type in the Diagnostics wizard on Windows 2003 SP1.

[T146354] If you erase multiple tapes at one time from BrightStor ARCserve Backup with the Microsoft SQL Server database, and you receive media management errors for tapes not protected by media management, the error messages may indicate a login failure with Microsoft SQL Server. Under certain circumstances (if the login failure error generates error codes 18456, 18452, or 5), BrightStor ARCserve Backup now retries the login to Microsoft SQL Server.

[T16C477] Device Configuration reliably configures StorageTek ACSLS libraries without generating errors or failures.

[T16C501] You can now reliably use the Auto Configuration option during the configuration of the Tape Library Option with multiple changers managed by BrightStor ARCserve Backup.

[T1A5212] You can now reliably restore backups made with the BrightStor ARCserve 2000 Image Option using BrightStor ARCserve Backup r11.1.

[T1A5213] BrightStor ARCserve Backup has been enhanced to solve a number of Microsoft oplock-related issues:
- Applications such as Quickbooks or AXIUM can now open files in multi-user mode
- Error messages no longer incorrectly indicate damaged .pst files on remote machines with the Agent for Open Files installed.
- You can now reliably archive folders in Outlook 2000.

[T1A5216] You can now import and export tapes from the Device Manager on a Windows primary server in a cross-platform SAN environment.

[T1A5225] BrightStor ARCserve Backup has been enhanced to increase the SCSI protocol timeout period for transmitting data, to ensure that the NDMP NAS Option no longer times out.

[T1A5228] BrightStor ARCserve Backup has been enhanced to provide raw NDMP mode support to allow EMC Celerra to detect tape devices.

[T245079] The restore query function now reliably matches filenames that include wildcards and Japanese Shift-JIS characters that include the value 0x5c in NAS volumes backed up with the NDMP NAS Option.

[T2D2387] Tapecopy operations now find full backup Microsoft SQL Server database sessions using the –qMethod FULL option to query all sessions.

[T2D2396] You can now restore more than 100 GB to NAS devices using network shares without difficulty.

[T326180] You can now create a Disaster Recovery boot kit when using Windows 2000 Traditional Chinese Advanced Server SP4 integrated CDs.

[T367146] You can now set machine-level filters through the Client Agent to exclude file patterns such as abc.ext or driveletter:*.ext.

[T367147] You can now reliably back up Microsoft Exchange data at the Document level using the Attachment Exclude filter, even when email attachments have no titles.

[T367148] BrightStor ARCserve Backup has been updated to prevent certain situations in which brick-level backup jobs fail after a small number of mailboxes have been backed up.

[T367149] You can now configure the Agent for Microsoft Exchange Server on a Domain Controller, and BrightStor ARCserve Backup now properly generates the ExchVerify.log.

[T36A205] [T36A206] Oracle backup jobs now properly release resources when they finish running.

[T36A207] You can now reliably connect to an Oracle database on machines with multiple versions of Oracle installed.

[T36A211] BrightStor ARCserve Backup now properly skips the MSDE writer during full backup operations when the Agent for Microsoft SQL Server is installed on the machine.

[T36A223] You can now perform a full system backup of remote Microsoft SQL Server machines. Previously, after applying the patch QO63594, such jobs would fail with the error “E8604 Failed to start backup errMsg=[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null).' Reason: Not associated with a trusted SQL Server connection.”

[T36B163] You can now select the entire machine and enable the option Scan backup media content when backing up Windows XP machines using the Client Agent for Windows.

[T36B182] The message “Filtering invalidates backups for the Disaster Recovery Option” has been changed to “Filtering might invalidate backups for the Disaster Recovery Option” to indicate that filtering does not always invalidate such backups.

[T3F8079] You can now restore a mix of file system and agent backup data with the global option for encryption set without generating the error message E3482 Failed to decrypt data (EC 27).

[T3F8080] BrightStor ARCserve Backup reconnects properly if the connection to the Exchange Information Store session is lost during document-level backups and finishes the job properly.

[T3F8082] You can back up Microsoft Exchange Server at the Document level when the Microsoft Exchange Mailbox Store name includes special characters such as /, #, or :.

[T3D3053] You can run system state backup operations using the Client Agent for Windows on Windows 2003 servers with registries larger than 524284 KB without generating warning messages or causing the job status to be Incomplete.

[T16C456] BrightStor ARCserve Backup has been enhanced to ensure that all tapes are exported properly at the end of multistreaming jobs when the option Eject Tape and Export Tape is enabled.

[T16C462] HP-UHDL autoloaders now run inventories of all slots only when necessary.

[T16C481] BrightStor ARCserve Backup has been updated to ensure that slot 0 is handled identically by the ca_devmgr –v –mediainfo command and the Device Manager GUI.

[T16C486] You can now reliably back up from distributed servers when new sessions start without generating an error message in the BrightStor log.

[T16C487] BrightStor ARCserve Backup now reliably sets the block size value so that backup jobs no longer fail as a result of an incorrectly set block size.

[T16C490] The Device Manager now properly displays the barcode or serial numbers of libraries with bar code readers with names containing hyphens (for example, ABC-XYZ).

[T16C492] BrightStor ARCserve Backup has been updated to ensure that all error messages are properly cleared from the GUI when you click OK. Previously, an error message appeared when the Tape Engine started and could not be cleared, preventing the Tape Engine from starting.

[T16C499] BrightStor ARCserve Backup now properly identifies slots as empty after magazines are changed.

[T16C503] BrightStor ARCserve Backup has been updated to ensure that, after GFS rotation jobs begin, the slot used in the last backup job is released.

[T16C504] BrightStor ARCserve Backup now correctly reports the results of quick inventory procedures launched after tapes are manually moved out of libraries.

[T16C506] Plasmon DVD Jukeboxes now appear as on line after you start the Tape Engine.

[QO64863] (T16C508) BrightStor ARCserve Backup has been enhanced to ensure that, if a successful restore job is followed by a backup job that appends to the same tape, the backup job does not overwrite valid data on the tape.

[T1A5210] BrightStor ARCserve Backup performance has been enhanced when backing up to file system devices on Windows 2003 Server. Previously, such backup jobs caused high CPU resource usage.

[T1A5222] Backup jobs no longer randomly fail at the beginning of the job.

[T1A5224] The Tape Engine now reliably and automatically inventories HP C1557A libraries after you replace magazines.

[T245069] BrightStor ARCserve Backup has been updated to ensure that you can restore subfolders using the Create Directories from the Base option without restoring the parent folder erroneously.

[T245070] You can now reliably sort by date in the Search dialog of the Restore Manager.

[T245078] The BrightStorMgr.exe process now stops when the window is closed.

[T245086] BrightStor ARCserve Backup now finds tapes in slots without generating erroneous messages indicating that it is unable to find media.

[T245088] BrightStor ARCserve Backup has been enhanced to ensure that tapes are properly identified as write-protected even if they were set to write-protect after having been identified as write-enabled in the inventory.

[T245092] The restore query function now properly and reliably matches filenames containing wildcards and Japanese Kanji characters.

[T2D2382] [T2D2384] You can now run backup jobs while running eTrust 7.0 and 7.1 without causing the server to freeze during or after the backup.

[T2D2391] You can now restore large .jpeg and .bmp files without generating error messages.

[T2D2399] BrightStor ARCserve Backup has been enhanced to ensure that you can properly back up DHCP files.

[T2D2405] You can now run Tapecopy jobs with more than 100 source sessions.

[T2D2413] BrightStor ARCserve Backup has been updated to ensure that the output from the following command displays the correct size (in MB) of the tapecopy job:
```
tapecopy  -d DR -qPastTime 1 -g -fDstMux -eject
```

[T2D2422] You can now restore multiple files with one job using the ca_restore command without specifying tape sessions.

[T2D2411] Incremental backups in rotation jobs with the character * in the media name now consistent append to previous media as specified.

[T36B174] You can now modify GFS backup jobs without causing the Calendar View to display the backup type of the current day as Full, rather than Incremental or Differential.

[T36B175] [T36B176] BrightStor ARCserve Backup no longer erroneously displays the message “The product is not currently licensed.”

[T36B177] You can now use the ca_restore command to restore files backed up from Linux machines.

[T36B178] Weekly full backups in rotation jobs with the character * in the media name no longer append to the tapes used for the incremental backups in the rotation job.

[T46B008] BrightStor ARCserve Backup properly prepares for certificate services during system state backup operations.

[T46B014] The Exclude *.* filter properly excludes all specified files and directories.

[T46B015] You can run system state backup operations on Windows 2003 servers with registries larger than 524284 KB without generating warning messages.

[T46B016] BrightStor ARCserve Backup has been updated to ensure that jobs with the pre/post options Run Command Before Job and Run Job Immediately On Exit Code 0 selected do not run if the pre/post command does not return an exit code of 0.

[T46B017] BrightStor ARCserve Backup has been enhanced to ensure that the sub-jobs of multistreaming rotation jobs run until the entire job is finished, even if some of the sub-jobs actually run on the next calendar day.

[T46B018] You can view all media in a Save Set when you use the command ca_dbmgr –show poolmedia.

[T3D3056] You can restore the Quota information of multiple drives in the same job.

[T3D3057] BrightStor ARCserve Backup properly calculates the drive usage time for jobs that span tapes, allowing auto-cleaning to be launched correctly.

[T3D3058] The Agent Management GUI has been updated to display job details from the log file for computers with names of three characters or fewer.

[T36B167] Modifying jobs while an inventory is running no longer causes the media pool name to disappear from the job.

[T36B170] Modifying a copy job no longer causes the machine name to appear twice under the Microsoft Windows Network.

[T367152] You must now set all related options (for example, the Bigger than and Older than parameters) to identify how much data to prune and when to run the pruning job, before you can select the Enable Auto-Pruning option.

[T367154] The correct files are copied when you copy files from a remote Windows machine using the Include: Directory Pattern: \ filter.

[T31A229] This service pack addresses a security vulnerability due to buffer overflow in the BrightStor ARCserve Backup Discovery Service. This security update should be applied to all Windows systems on which the BrightStor ARCserve Backup for Windows r11.1 base product and any BrightStor ARCserve Backup agents are installed.

[T16C458] You can now restore sessions from multiplexing tapes without generating the error message “AE0040 Invalid file signature: 0x421761de.”

[T2D2383] The Tapecopy –ex command now supports database query commands.

[T2D2392] IIS settings are now properly retained during system state restore jobs.

[T2D2400] Data growth jobs from BrightStor^® ARCserve^® Backup for Laptops & Desktops no longer fail randomly.

[T31A210] BrightStor ARCserve Backup has been enhanced to allow you to use the backup method specified in the job options for system state backup operations.

[T31A211] BrightStor ARCserve Backup has been enhanced to allow you to use Restore by Query with all double-byte Kanji characters.

[T31A212] BrightStor ARCserve Backup no longer sends duplicate alert messages.

[T31A214] BrightStor ARCserve Backup managers can now display unrecognized media types without problems.

[T367124] The owritesameblankany parameter of the ca_backup command no longer incorrectly requires a tape name.

[T367138] Copy jobs now reliably copy all specified files and folders on all supported Windows platforms.

[T36A176] BrightStor ARCserve Backup now consistently and reliably retains options when remote backup jobs are modified.

[T36A195] After running the Diagnostic Wizard, BrightStor ARCserve Backup now properly and reliably records information in the Activity log when jobs are executed. Previously, the Diagnostic Wizard improperly set the Message Type in Activity Log option to None, so that no information was recorded.

[T36A198] Incremental and Differential GFS backup jobs no longer create and include disaster recovery sessions on local cluster nodes.

[T367123] You can now modify and resubmit Information Store Level Storage Group Backup jobs without causing the Job Manager to fail.

[T367135] BrightStor ARCserve Backup now retains the selected backup methods for Database Level backup jobs when you modify previously submitted jobs.

[T367143] BrightStor ARCserve Backup has been enhanced to ensure that Document Level backup jobs no longer fail incorrectly with Error 8535.

[T31A213] You can now reliably perform merge operations on Document Level backup sessions with multibyte characters such as Japanese, and the Database and Restore Managers now properly display items containing multibyte characters.

[T3F8081] When browsing Microsoft SQL servers with large numbers of databases, BrightStor ARCserve Backup now properly displays all of the databases. In addition, full backup jobs now properly and reliably back up all of the databases on these servers and the RPC server no longer fails.

[T369182] BrightStor ARCserve Backup now supports the use of all Japanese characters in tablespace names.

[T36A180] You can now reliably and properly back up your data using the Agent for Oracle with SAP ITS Web Application 6.20 SAP Portal installed.

[T36A187] BrightStor ARCserve Backup has been enhanced to ensure that the dates and times of all sessions are displayed correctly when merging tapes from cross-platform backup jobs.

[T3F8074] Oracle backup jobs no longer fail in error with the message “E8604 Failed to start backup. (DBNAME = XXX, EC = Backup Agent Error (261) “Backup Agent cannot process the request.”

[T3F8073] Oracle SAP backup jobs no longer fail in error with the message “E8604 Failed to start backup. (DBNAME = XXX, EC = Backup Agent Error (261) “Backup Agent cannot process the request.”

[T31A194] BrightStor ARCserve Backup Disaster Recovery Option has been enhanced to allow you to use filtering during disaster recovery backup jobs.

[T36A177] BrightStor ARCserve Backup has been enhanced to ensure that USB keyboards are properly detected during disaster recovery operations on Japanese versions of Windows 2000.

[T16C484] Media pools now reliably display the proper media after the Tape Engine is restarted in SAN environments. This fix addresses a problem with BrightStor ARCserve Backup connecting to remote Microsoft SQL Server databases. To enable this fix, add the string value RemoteDBMachineNameEx to the following registry key on your BrightStor ARCserve Backup machine:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCServeBackup\base\Database
```
Set the value of this string as the name of the machine on which Microsoft SQL Server is installed.

[T16C485] BrightStor ARCserve Backup has been updated to ensure that GFS rotation jobs with the Append option enabled now launch properly and reliably in cross-platform SAN environments.

[T16C473] BrightStor ARCserve Backup has been enhanced to ensure that the Device Manager now properly displays the drives in changers in SAN environments in which distributed servers have locally attached tape drives. Previously, the Device Manager displayed the locally attached tape drive in the changer.

[T16C475] The Tape Engine on primary servers no longer fails randomly with the message “E6500 Client connect to tape failed” when backing up from the distributed server.

[T16C465] The Tape Engine no longer fails if a job fails and tapes are exported for multistreamed jobs.

[T16C479] BrightStor ARCserve Backup has been enhanced to ensure that in non-barcode changers, slots with tapes no longer appear empty when the Tape Engine starts, prompting an unnecessary inventory.

[T245072] BrightStor ARCserve Backup has been updated to ensure that backup jobs no longer hang as errors are repeatedly recorded in the tape log.

[T16C482] To avoid a situation in which the Tape Engine stops after it starts when two StorageTek 9710 libraries are managed by one ACSLS with one library used by BrightStor ARCserve Backup and the other by AS400, add the following DWORD value:
```
ShareWithAS400
```
under the following key:
```
Software\ComputerAssociates\BrightStor ARCserve backup\Base\Tapeengine\Config
```
Set this value to 1.

[T1A5208] This test fix addresses the following issues:
- When you replace a magazine in an HP C5713A library, the Tape Engine now automatically inventories and detects tapes in the new magazine.
- The Tape Engine no longer hangs on read element status SCSI commands.
- You can now position media with IBM 4560SLX libraries and HP Ultrium 1-SCSI drives.
- Per IBM, the ASC text Unsupported Target Descriptor Type Code [04, 07] has been changed to Logical Unit Not Ready, task in progress [04, 07].

[T31A207] Double-sided Optical Media now appear correctly in the Backup Manager.

[T16C488] Rotation jobs now use RAID 1 sets properly. Previously, if only one tape of a two tape RAID set was found, BrightStor ARCserve Backup backed up only the one tape. This fix ensures that, if only one tape is found (for example, if the other tape was exported from the library), BrightStor ARCserve Backup erases the remaining tape and creates a new RAID set for the rotation backup job. To enable this fix, you must add the DWORD value RaidForceToUseBlankSet to the following registry key:
```
SOFTWARE\ComputerAssociates\BrightStor ARCServe Backup\Base\Tapeengine\CONFIG
```
Set this value to 1.
[T16C497] BrightStor ARCserve Backup has been updated to ensure that, when the RAID Option is installed, GFS rotation jobs start properly when blank tapes exist in a tape library.

18.0 BrightStor ARCserve Backup for Windows r11.5 SP1 Readme

19.0 Welcome

The following sections provide information originally released with BrightStor ARCserve Backup for Windows r11.5 SP1 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3.

20.0 Operating System Support for BrightStor ARCserve Backup r11.5 SP1

For information originally released with BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the section Operating System Support for BrightStor ARCserve Backup r11.5.

Support for the following operating systems has been added to BrightStor ARCserve Backup for Windows r11.5 SP1:

Windows Server 2003 R2 Standard Edition and Enterprise Edition (32-bit and x64)
Windows 2003 SP1 Itanium
Microsoft Virtual Server 2005 R2 32-bit and 64-bit (EM64T/AMD) (BrightStor ARCserve Backup base product, BrightStor® ARCserve® Backup Client Agent for Windows, and BrightStor® ARCserve® Backup Agent for Open Files only)
VMware ESX Server version 2.5.2 on 32-bit (BrightStor ARCserve Backup base product, BrightStor ARCserve Backup Client Agent for Windows, and BrightStor ARCserve Backup Agent for Open Files only)

20.1 Supported Operating Systems for the Client Agent for Windows for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following operating systems has been added to the BrightStor® ARCserve® Backup Client Agent for Windows:

Windows Server 2003 R2 Standard Edition and Enterprise Edition (32-bit and x64)
Windows 2003 SP1 Itanium
Microsoft Virtual Server 2005 R2 32-bit and 64-bit (EM64T/AMD)
VMware ESX Server version 2.5.2 on 32-bit (Windows 2003 R2)

20.2 Supported Operating Systems for the Client Agent for UNIX for BrightStor ARCserve Backup r11.5 SP1

The supported operating systems for the BrightStor® ARCserve® Backup Client Agent for UNIX have been updated for this service pack to add the BrightStor® ARCserve® Backup Agent for FreeBSD. The agent now supports the following:

Solaris 2.6, 7, 8, 9, and 10 SPARC
Solaris 9 and 10 (x86 32-bit)
Solaris 10 AMD64
IBM AIX 4.3.3, 5L v5.1, v5.2, and v5.3
HP-UX 11.0, 11.11, and 11.23 PA RISC
HP-UX 11.22 and 11.23 Itanium (IA64)
Tru64 v4.0E, v4.0F, v4.0G, v5.0, v5.1, v5.1a, v5.1b
FreeBSD version 4.11
FreeBSD versions 5.3 and 5.4

20.3 Agent for Informix for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Informix:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.4 Agent for Lotus Domino Support for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Lotus Domino:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.5 Agent for Microsoft Data Protection Manager for BrightStor ARCserve Backup r11.5 SP1

In this release, BrightStor ARCserve Backup has added a new agent, the BrightStor® ARCserve® Backup for Windows Agent for Microsoft Data Protection Manager. This agent is supported on the following operating systems:

Windows Server 2003 Standard Edition and Enterprise Edition SP1
Windows Server 2003 R2 Standard Edition and Enterprise Edition (32-bit)
Windows 2003 Storage Server SP1

20.6 Agent for Microsoft Exchange Server Support for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Microsoft Exchange Server:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.7 Agent for Microsoft SharePoint Support for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Microsoft SharePoint:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.8 Agent for Microsoft SQL Server Support for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Microsoft SQL Server:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.9 Agent for Open Files for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Open Files:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-t)
Microsoft Windows 2003 R2 x64
Microsoft Virtual Server 2005 R2 32-bit and 64-bit (EM64T/AMD)
VMware ESX Server version 2.5.2 on 32-bit (Windows 2003 R2)

20.10 Agent for Oracle Support for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Agent for Oracle:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.11 Disaster Recovery Option for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Disaster Recovery Option:

Microsoft Windows 2003 Storage Server
Windows 2003 R2 Standard Edition and Enterprise Edition 32-bit
Windows 2003 R2 x64 and Windows 2003 Itanium SP1 (Remote Disaster Recovery only)

20.12 Image Option for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Image Option:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.13 NDMP NAS Option for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows NDMP NAS Option:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.14 Optical Library Option for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Optical Library Option:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.15 Storage Area Network (SAN) Option for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Storage Area Network Option:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)
Windows 2003 R2 x64

20.16 Serverless Backup Option for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Serverless Backup Option:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.17 Tape RAID Option for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Tape RAID Option:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.18 Enterprise Option for SAP R3 for Oracle for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup for Windows Enterprise Option for SAP R3 for Oracle:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

20.19 Enterprise Option for Advantage Ingres for BrightStor ARCserve Backup r11.5 SP1

In this release, support for the following has been added to the BrightStor® ARCserve® Backup Enterprise Option for Advantage™ Ingres®:

Microsoft Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

21.0 System Requirements for BrightStor ARCserve Backup r11.5 SP1

The following sections provide information about the minimum system requirements for each new BrightStor ARCserve Backup component added for this service pack.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the section System Requirements for BrightStor ARCserve Backup r11.5

21.1 Supported Clustering Software for BrightStor ARCserve Backup r11.5 SP1

BrightStor ARCserve Backup supports the following clustering software:

Microsoft Cluster Server (x86, x64 and IA-64)
NEC CLUSTERPRO/ExpressCluster Version 7.0 SE and LE
NEC CLUSTERPRO/ExpressCluster Version 8.0 SE

Note: NEC CLUSTERPRO/ExpressCluster is supported in English and Japanese only.

21.2 Citrix MetaFrame Support for BrightStor ARCserve Backup r11.5 SP1

BrightStor® ARCserve® Backup 11.5 SP1 Server, the Agent for Open Files, and the Disaster Recovery Option support the following versions of Citrix MetaFrame:

Citrix MetaFrame Presentation Server 3.0 for Windows 2000
Citrix MetaFrame Presentation Server 3.0 for Windows 2003 SP1
Citrix MetaFrame Presentation Server 4.0 for Windows 2000
Citrix MetaFrame Presentation Server 4.0 for Windows 2003 SP1
Citrix MetaFrame Presentation Server 4.0 for Windows 2003 R2 Standard Edition and Enterprise Edition (32-bit)

The Client Agent for Windows and the Disaster Recovery Option support the following Citrix Presentation Server Clients:

Citrix MetaFrame Presentation Server 4.0 Program Neighborhood for Windows 2000 SP4 and Windows 2003 SP1
Citrix MetaFrame Presentation Server 4.0 Program Neighborhood Agent for Windows 2000 SP4 and Windows 2003 SP1
Citrix MetaFrame Presentation Server 4.0 Web Client for Windows 2000 SP4 and Windows 2003 SP1
Citrix MetaFrame Presentation Server 3.0 Program Neighborhood for Windows 2000 SP4 and Windows 2003 SP1
Citrix MetaFrame Presentation Server 3.0 Program Neighborhood Agent for Windows 2000 SP4 and Windows 2003 SP1
Citrix MetaFrame Presentation Server 3.0 Web Client for Windows 2000 SP4 and Windows 2003 SP1

21.3 Agent for Microsoft Data Protection Manager Support for BrightStor ARCserve Backup r11.5 SP1

BrightStor ARCserve Backup r11.5 SP1 has added the Agent for Microsoft Data Protection Manager (DPM). The agent requires Microsoft System Center Data Protection Manager 2006.

21.4 Agent for Microsoft Exchange Server Support for BrightStor ARCserve Backup r11.5 SP1

Support for Microsoft Exchange Server Version 2003 SP2 has been added to the Agent for Microsoft Exchange Server for this release.

21.5 Agent for Microsoft SQL Server Support for BrightStor ARCserve Backup r11.5 SP1

The following section provides information relating to the system requirements for the Agent for Microsoft SQL Server for this service pack release:

Support for Microsoft SQL Server 2005 Final Release Version has been added to the Agent for Microsoft SQL Server for this release.
If you use Microsoft SQL Server 2000 Service Pack 4 64-bit for IA64, you must apply the December 15, 2005 Cumulative Hotfix Package for SQL Server 2000 Service Pack 4. For more information, see Microsoft Knowledge Base Article 904660, http://support.microsoft.com/?Kbid=904660 .

21.6 Agent for Microsoft SharePoint Support for BrightStor ARCserve Backup r11.5 SP1

The Agent for Microsoft SharePoint now supports the following:

Microsoft SharePoint Portal Server 2003 SP1 and SP2
Microsoft Windows SharePoint Services 2.0 SP1 and SP2

The following are the minimum system requirements for the agent (including shared components):

40 MB free disk space
512 MB RAM

The following indicates the correct allocation:

Router:
- 20 MB free disk space
- 512 MB RAM
External Data Agent:
- 20 MB free disk space
- 512 MB RAM
Agent for Microsoft SQL Server:
- You must have the following amount of free disk space:
  – 12 MB free disk space on x86
  – 16 MB free disk space on x64
  – 17 MB free disk space on IA64
- 512 MB RAM

Note: In a small server farm, if you install three agents on the same machine, the minimum disk size needed is the sum of the requirements for the three agents.

21.7 Agent for Lotus Domino Support for BrightStor ARCserve Backup r11.5 SP1

The Agent for Lotus Domino now supports the following on Lotus Notes 7.0:

Microsoft Windows 2003
Microsoft Windows 2003 R2

21.8 Agent for Oracle for BrightStor ARCserve Backup r11.5 SP1

The Agent for Oracle now supports the following versions of Oracle Server:

Oracle Server version 8, 8i, 9, 9i, 10g, and 10g R2

21.9 USB Device Detection for BrightStor ARCserve Backup r11.5 SP1

BrightStor ARCserve Backup detects the following USB devices:

Tape Drives
Medium Changers
Removable Devices

In addition, BrightStor ARCserve Backup enumerates USB (1.x and 2.x) interfaces.

BrightStor ARCserve Backup supports USB/IEEE1394 on Windows only.

Note: USB device drivers are required.

22.0 Installation Considerations for BrightStor ARCserve Backup r11.5 SP1

The following sections provide information to consider when installing this service pack.

For information originally released with BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the section Installation Considerations for BrightStor ARCserve Backup r11.5.

The licensing package does not install the CA License Server service if it is not already installed on the machine (CA License Server can be configured to retrieve licensing information from CA License Client machines connected to the CA License Server). To install CA License Server, from the CA_LIC directory, run the following command:
```
lic98rmtd -install
```
If CA License Server is installed on the machine, the licensing package does not remove it.

22.1 Install or Upgrade to BrightStor ARCserve Backup r11.5 SP1 as a Cluster-aware Application

To install BrightStor ARCserve Backup r11.5 SP1 as a cluster-aware application, or to upgrade from BrightStor ARCserve Backup r11.5 to BrightStor ARCserve Backup r11.5 SP1 on NEC CLUSTERPRO/ExpressCluster or MSCS on Windows, you can install BrightStor ARCserve Backup r11.5 SP1 directly, using the installation procedures in the appropriate cluster appendix of the Administrator Guide in the following sequence:

Install BrightStor ARCserve Backup r11.5 SP1 on the primary cluster node.
Install BrightStor ARCserve Backup r11.5 SP1 on the secondary cluster nodes.

Alternatively, you can perform the following steps:

Install BrightStor ARCserve Backup r11.5 on the primary cluster node using the installation procedure in the appropriate cluster appendix of the Administrator Guide.
Install BrightStor ARCserve Backup r11.5 on the secondary cluster nodes using the installation procedure in the appropriate cluster appendix of the Administrator Guide.
Remove all BrightStor ARCserve Backup services from monitoring by the cluster to avoid failover occurring during the installation of the service pack.
Upgrade to BrightStor ARCserve Backup r11.5 SP1 on the primary cluster node using the installation procedure for BrightStor ARCserve Backup r11.5 SP1.
Stop all BrightStor ARCserve Backup services on the primary cluster node.
Fail the BrightStor ARCserve Backup Cluster Group over to the secondary cluster nodes to continue installing the service pack on those nodes.
Upgrade to BrightStor ARCserve Backup r11.5 SP1 on the secondary cluster nodes using the installation procedure for BrightStor ARCserve Backup r11.5 SP1.
Stop all BrightStor ARCserve Backup services on the secondary cluster nodes.
Reinstate the monitoring of all BrightStor ARCserve Backup services by the cluster.

Important! You cannot install BrightStor ARCserve Backup r11.5 on the primary cluster node and then upgrade the primary cluster node to BrightStor ARCserve Backup r11.5 SP1 and then install BrightStor ARCserve Backup r11.5 and upgrade to BrightStor ARCserve Backup r11.5 SP1 on the secondary cluster nodes.

22.2 Install BrightStor ARCserve Backup as a Cluster-aware Application on Microsoft Windows Server 2003 R2 for BrightStor ARCserve Backup r11.5 SP1

To install and configure BrightStor ARCserve Backup as a cluster-aware application on Microsoft Windows Server 2003 R2 in an NEC CLUSTERPRO/ExpressCluster installation, perform the following procedure on all physical nodes in the cluster:

Install BrightStor ARCserve Backup using the cluster-aware installation instructions in the appendix Backing Up and Restoring NEC CLUSTERPRO/ExpressCluster Clusters in the Administrator Guide.
Do not configure your storage area network if you have the BrightStor ARCserve Backup Storage Area Network (SAN) Option installed.
Add the following DWORD value to the Windows registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters and set the value to 0x01:
```
DisableStrictNameChecking
```
Remove the following DWORD value from the Windows registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 if it exists:
```
BackConnectionHostNames
```
Recreate the following multi-string DWORD value with the virtual computer name in the Windows registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0:
```
BackConnectionHostNames
```
Set this value to Virtual Computer Name, the name associated with the BrightStor ARCserve Backup cluster failover group (for example BABVirServer).
Add the virtual computer name and the floating IP address to the hosts file (for example, %SystemRoot%\system32\drivers\etc\hosts).
Configure your SAN if you have the SAN Option installed.
Follow these steps on all other physical servers in the cluster to finish the installation.

22.3 Create New Disaster Recovery CDs after Applying Patches for BrightStor ARCserve Backup r11.5 SP1

After you apply any major patches, you must update the disaster recovery media used to protect your local backup server machine as well as any remote client machines. We strongly recommend that you update your disaster recovery media as soon as possible after applying any major patches.

The method you use to update your media depends upon the operating system and disaster recovery method you have chosen to protect the machines:

Windows 2000 using the Bootable CD method: Launch the Boot Kit Wizard and create a new bootable CD image (CDBOOT.ISO) after applying the patch. Burn the CD image to a blank CD and label it properly.
Windows 2000, Windows XP, or Windows 2003 using the Bootable Tape method (OBDR): Launch the Boot Kit Wizard to create a new bootable tape image (TOBER.ISO) after applying the patch. Format a new tape with the image before you run the backup.
Windows 2000 using the Bootable Disk method, Windows 2003, or Windows XP: Perform the following procedure to update your media after you apply any major patches:
1. Create the folder C:\dr_patch.
2. In the dr_patch folder, create the folder C:\dr_patch\BOOTDISK.
  Note: If you are using a language other than English, create the folder C:\dr_patch\BOOTDISK.xxx where xxx is a language extension, indicating the language you use. Use one of the following language extensions to indicate the language:
  – Simplified Chinese: CHS
  – Traditional Chinese: CHT
  – Japanese: JPN
  – Korean: KRN
  – German: GRM
  – Italian: ITA
  – French: FRN
  – Spanish: SPN
  – Brazilian Portuguese: PRB
3. From a command prompt, go to the BrightStor ARCserve Backup home directory and, from the bootdisk.w2k directory, execute the following command to decompress all the files in the bootdisk.w2k directory to the C:\dr_patch\BOOTDISK directory:
```
expand –r * C:\dr_patch\BOOTDISK
```
  Note: If you are using a language other than English, copy all files from C:\dr_patch\BOOTDISK to C:\dr_patch\BOOTDISK.xxx.
4. Create an empty signature file in C:\dr_patch and name it arc.w2k.
5. Burn a new CD to include the files in the C:\dr_patch folder (do not include the dr_patch folder itself). Include the following in the new CD root location:
  – BOOTDISK folder
  – BOOTDISK.xxx folder (where xxx is the language extension for languages other than English)
  – arc.w2k file
  Use the new CD as your BrightStor ARCserve Backup disaster recovery CD.

23.0 General Considerations for BrightStor ARCserve Backup r11.5 SP1

For information originally released with BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the section General Considerations for BrightStor ARCserve Backup r11.5.

The following sections provide general information to consider when using BrightStor ARCserve Backup.

23.1 Move BrightStor ARCserve Backup Base to a Different Drive for BrightStor ARCserve Backup r11.5 SP1

If the drive on which you installed BrightStor ARCserve Backup begins to run out of space, you can move BrightStor ARCserve Backup to another drive on the same machine.

To move the BrightStor ARCserve Backup base product to another drive on the same machine, perform the following procedure:

Stop all BrightStor ARCserve Backup services. From the home directory, enter cstop to stop all the necessary services.
Copy the directories \%ARCserve install folder%\00000001.qsd (the job queue) and \%ARCserve install folder%\database (the database directory) to a temporary location.
Uninstall all components of BrightStor ARCserve Backup.
Reinstall BrightStor ARCserve Backup on the new drive and apply any patches that were applied to the original installation.
Note: Because you are reinstalling BrightStor ARCserve Backup on the same computer, you do not need to register or license it again.
Copy the database directory and 00000001.qsd directory you copied to a temporary directory over the versions of these directories created by the new installation.
Start all of the BrightStor ARCserve Backup services. From the home directory, enter cstart to start all the necessary services.

23.2 High Density Mode for NAS Device Configuration for BrightStor ARCserve Backup r11.5 SP1

You can now use high density auto-selection mode for NetApp to set all devices to high compression mode. By default, devices are set to low density mode.

To use higher density mode, add the DWORD value bPreferHighDensityForNetapp to the following key before NAS device configuration, and set it to 1:

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\TapeEngine\CONFIG

Alternatively, you can use manual configuration to enter high density tape drive names.

23.3 iOmega USB Autoloader Configuration for BrightStor ARCserve Backup r11.5 SP1

If you use an iOmega USB autoloader, you need not install the BrightStor® ARCserve® Backup for Windows r11.5 SP1 Tape Library Option. In addition, you need not run Device Configuration to configure your devices.

23.4 Device Configuration on MSCS Cluster Servers for BrightStor ARCserve Backup r11.5 SP1

To configure your devices when BrightStor ARCserve Backup is installed as a cluster-aware application on MSCS Cluster Servers, you must perform the following procedure:

Delete the BrightStor BKP Registry resource from the MSCS Cluster Administrator.
Right-click the BrightStor ARCserve Backup resource and select Properties from the pop-up menu.
The Properties dialog appears.
On the Advanced tab of the Properties dialog, click Do Not Restart.
Configure your devices as necessary for your environment.
Right-click the BrightStor ARCserve Backup resource and select Properties from the pop-up menu.
The Properties dialog appears.
On the Advanced tab of the Properties dialog, click Restart and bring the BrightStor ARCserve Backup resource back on line.
Add the BrightStor BKP Registry resource to the MSCS Cluster Administrator, set dependencies for it, and bring it on line.

For more information, see the sections Register BrightStor ARCserve Backup Registry Hive for Replication and Set Up Dependencies Between BrightStor ARCserve Backup Groups in the appendix “Backing Up and Restoring MSCS Clusters” in the Administrator Guide.

23.5 Adjust NEC CLUSTERPRO/ExpressCluster Sleep Timing during Group Failover for BrightStor ARCserve Backup r11.5 SP1

Depending on your environment, errors related to the releasing of resources can cause BABGroup failover operations to fail. To address this issue, you can adjust the sleep timing in the BABGroup stop script (stop.bat) by adjusting the armsleep value.

The armsleep value indicates the number of seconds the system waits for resources to be released during failover. You can prolong this to 3 or 4 seconds if failover operations fail with errors relating to the releasing of resources.

To adjust the value, perform one of the following actions:

If you are using NEC CLUSTERPRO/ExpressCluster SE, add the armsleep value to the BABGroup stop script (immediately before the armkill CASTapeEngine value) and adjust the timing value.
If you are using NEC CLUSTERPRO/ExpressCluster LE, adjust the existing armsleep value of 2 to 3 or 4 seconds.

23.6 General Considerations for the Agent for Microsoft Data Protection Manager for BrightStor ARCserve Backup r11.5 SP1

The following sections provide general information to consider when using the Agent for Microsoft Data Protection Manager.

23.7 Data Protection Manager Server Recovery for BrightStor ARCserve Backup r11.5 SP1

Typically, to restore your Microsoft Data Protection Manager server completely, you must uninstall and reinstall Data Protection Manager (DPM) before the DPM database and the replica can be restored because, although a version of Microsoft SQL Server is installed automatically during the Data Protection Manager installation, DPM (through the DPM Writer) does not protect the Microsoft SQL server.

To avoid uninstalling and reinstalling Microsoft Data Protection Manager, you can use the BrightStor® ARCserve® Backup Client for VSS Software Snap-Shot to recover Microsoft Data Protection Manager in a disaster recovery scenario.

Depending upon your environment, you must perform one of the following procedures to recover your Microsoft Data Protection Manager server.

23.8 Recover DPM Servers with the BrightStor ARCserve Backup Client for VSS Software Snap-Shot for BrightStor ARCserve Backup r11.5 SP1

Use this procedure to restore your Data Protection Manager server if have the following installed in your environment:

BrightStor ARCserve Backup
BrightStor ARCserve Backup Client for VSS Software Snap-Shot
BrightStor ARCserve Backup Agent for Microsoft Data Protection Manager
BrightStor ARCserve Backup Disaster Recovery Option
Note: You must have created a disaster recovery machine-specific recovery disk using the procedures in the Disaster Recovery Option Guide.

To recover your Microsoft Data Protection Manager server, perform the following procedure:

Back up your entire local machine containing the MSDEWriter and the DPM Writer using BrightStor ARCserve Backup.
Load the Microsoft Windows 2003 CD into the drive and reboot your machine. Boot from the Windows 2003 installation CD, and, in the setup dialog, press F2 to start Microsoft Automated System Recovery (ASR).
Follow the onscreen procedures to load the BrightStor ARCserve Backup CD and the disaster recovery machine-specific recovery disk.
From the Disaster Recovery wizard, restore from the tape. When the restore is complete, reboot the machine.
Log into the operating system and launch the manager component of BrightStor ARCserve Backup.
Select the MSDEWriter in the Restore By Tree view of the BrightStor ARCserve Backup Restore Manager and submit the restore job.
From Windows Administrative Tools, launch Services and manually start the following services in the following sequence:
- MSSQL$MICROSOFT$DPM$
- SQLAgent$MICROSOFT$DPM$
For more information about restoring DPM Replicas, see the BrightStor ARCserve Backup Agent for Microsoft DPM Guide.

23.9 Typical DPM Server Recovery for BrightStor ARCserve Backup r11.5 SP1

Use the following procedure to recover your Data Protection Manager server, if you have the following installed in your environment:

BrightStor ARCserve Backup
BrightStor ARCserve Backup Agent for Microsoft DPM
BrightStor ARCserve Backup Disaster Recovery Option
Note: You must have created a disaster recovery machine-specific recovery disk using the procedures in the Disaster Recovery Option Guide.

To recover your Microsoft Data Protection Manager server, perform the following procedure:

Back up the entire local machine containing the DPM Writer using BrightStor ARCserve Backup.
Load the Microsoft Windows 2003 CD into the drive and reboot your machine. Boot from the Windows 2003 installation CD, and, in the setup dialog, press F2 to start Microsoft Advanced System Recovery (ASR).
Follow the onscreen procedures to load the BrightStor ARCserve Backup CD and the disaster recovery machine-specific disk.
In the Disaster Recovery wizard, restore from the tape. When the restore is complete, reboot the machine.
Log into the operating system and use Add or Remove Programs to uninstall Microsoft Data Protection Manager 2006.
Uninstall the following DPM prerequisite software in the following sequence:
- SQL Server 2000 Reporting Services
- Internet Information Services (IIS)
- Microsoft SQL Server 2000 (MICROSOFT$DPM$)
Reboot the computer and reinstall Microsoft Data Protection Manager.
Manually start the DPM Writer service.
From the BrightStor ARCserve Backup Restore Manager, select the Microsoft System Center Data Protection Manager 2006 Writer Database DPMDB and Database ReportServer from the Restore By Tree view and submit the restore job.
When the restore job is complete, reboot the machine.
Execute the following command from the C:\Program Files\Microsoft SQL Server\80\Tools\Binn directory:
```
rsconfig -c -s bab-dpm\MICROSOFT$DPM$ -d ReportServer -a Windows
```
where bab-dpm is your machine name.
Note: If you have installed the Data Protection Manager in a location other than the default, you must replace the path to rsconfig with the new path.
Execute the following command from the C:\Program Files\Microsoft SQL Server\80\Tools\Binn directory and choose Y to delete all encrypted data from the report server database:
```
rskeymgmt –d
```
Note: If you have installed the Data Protection Manager in a location other than the default, you must replace the path to rskeymgmt with the new path.
Execute the following command from the C:\Program Files\Microsoft Data Protection Manager\Prerequisites\MSSQL\Reporting Services\ReportServer directory:
```
rsactivate -c RSReportServer.config
```
Note: If you have installed the Data Protection Manager in a location other than the default, you must replace the path to rsactivate with the new path.
Execute the following command from the C:\Program Files\Microsoft Data Protection Manager\DPM\bin directory:
```
dpmsync -sync
```
Note: If you have installed the Data Protection Manager in a location other than the default, you must replace the path to dpmsync with the new path.
For more information about restoring DPM Replicas, see the BrightStor ARCserve Backup Agent for Microsoft DPM Guide.

23.10 Recover Fujitsu Siemens Computers DPM-Appliance for BrightStor ARCserve Backup r11.5 SP1

If you have the following installed in your environment, use the procedure in this section to restore your Data Protection Manager server:

BrightStor ARCserve Backup or the Client Agent for Windows
Client for VSS Software Snap-Shot
Agent for Microsoft Data Protection Manager

To recover your Microsoft Data Protection Manager server, perform the following procedure:

Reimage the appliance with the manufacturer-supplied Recovery DVD and sysprep.inf file.
Reinstall all BrightStor ARCserve Backup components.
Stop the IIS Admin Service using Windows Administrative Tools\Services.
Note: You must also stop the related services, World Wide Web Publishing Service, and HTTP SSL, when prompted.
From the Restore By Tree view of the BrightStor ARCserve Backup Restore Manager, select C: and System State and submit a job to restore your files to their original locations.
Note: If the BrightStor ARCserve Backup server is deployed on the appliance and used for the whole machine backup, you must merge the sessions on your backup media before you can see these sessions in the Restore Manager.
Reboot the appliance.
From the Restore By Tree view of the Restore Manager, select the MSDEWriter and submit a job to restore the files to their original locations.
Delete the tempdb.mdf and templog.ldf files from the C:\Program Files\Microsoft Data Protection Manager\Prerequisites\MSSQL$MICROSOFT$DPM$\Data directory.
From Windows Administrative Tools, launch Services and manually start the following services in the following sequence:
- MSSQL$MICROSOFT$DPM$
- SQLAgent$MICROSOFT$DPM$
For more information about restoring DPM Replicas, see the BrightStor ARCserve Backup Agent for Microsoft DPM Guide.

24.0 Known Issues for BrightStor ARCserve Backup r11.5 SP1

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

For information originally identified during the release of BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3, see the section Known Issues for BrightStor ARCserve Backup r11.5.

If you disconnect USB devices from the BrightStor ARCserve Backup server and do not restart the Tape Engine after disconnection, you can manually assign the disconnected devices to new groups. These assignments are activated after you reconnect your devices to the server and restart the Tape Engine. If you restart the Tape Engine after disconnecting USB devices from the BrightStor ARCserve Backup server, you cannot manually assign the disconnected devices to new groups.
When you search for a file to restore using the Restore by Tree or Restore by Query method, filenames longer than 19 characters are not detected unless you specify a wildcard in the filename field.
Note: The RAIMA database has a maximum limit of 20 characters with wildcards. File extensions (.TXT or .*) count toward this limit.
If you execute a restore job using the Client Agent for UNIX with the Rename File option enabled and the same file already exists in the destination, the file is renamed with an extension (for example, as1 or as2). If the file name length of the restored file (with the new extension) exceeds 255 bytes, the restore operation fails with the error “E9032 Failed to create file” because, due to an operating system limitation, the file name length is limited to 255 bytes.
During reinstallation, previously registered license keys need not be reregistered unless the key was originally registered as a Trial key. You cannot reuse Trial license keys. To avoid this problem, do not select the Trial option when registering License Keys.
The following issues are known to exist in this release when using Informix Server v10:
- When you perform a Physical Restore for a single dbspace using the Restore by Tree method, you must check the following file to determine the correct Point to Time:
```
C:\Program Files\IBM\Informix\etc\ixbar.*
```
  You must provide this value to the restore job.
- After you restore an entire Informix Dynamic Server, you must ensure that the Informix database is not in quiescent mode before you perform any operations.
If you have version 5.0.6100.142 (or lower) of the eTrust® Antivirus driver Ino_fltr.sys installed on your machine and you back up the Documents and Settings folder, the BrightStor ARCserve Backup for Windows Agent for Open Files perceives some files as open because of the behavior of eTrust Antivirus and provides open file access to those files.
On IA 64-bit, when you restore sessions backed up with the 32-bit Client Agent for Windows to a machine running the 64-bit Client Agent for Windows, encrypted sessions cannot be restored. To work around this issue, install the 32-bit Client Agent for Windows on an Itanium 64-bit system from the \\IntelNT\NTagent folder and restore the sessions. The encrypted sessions can then be restored.
When you submit backup and restore jobs from the command line without using the waitForJobStatus parameter, the Unicenter® Network and Systems Management Jobflow Status displays errors even though the jobs are successful.

24.1 Known Issues for the Agent for Microsoft Exchange Server for BrightStor ARCserve Backup r11.5 SP1

The following section provides information relating to issues affecting the Agent for Microsoft Exchange Server known to exist in this service pack:

You must use Windows Server 2003 SP1 and Exchange Server 2003 SP1 when using the Interorg replication utility to replicate Exchange.

24.2 Known Issues for the Agent for Microsoft DPM for BrightStor ARCserve Backup r11.5 SP1

The following section provides information relating to issues affecting the Agent for Microsoft Data Protection Manager (DPM) known to exist in this service pack:

If you recover a DPM server after a disaster, the SQL Reporting Service reports the error ID 3014 after you click the Reporting tab of the DPM Administrator Console. We are currently working with Microsoft to resolve this issue.

24.3 Known Issues for the Agent for Oracle for BrightStor ARCserve Backup r11.5 SP1

The following section provides information relating to issues affecting the Agent for Oracle known to exist in this service pack:

When you restore full database backup jobs using the Agent for Oracle, you must shut down the database completely to avoid generating an error message in the Activity log.

24.4 Known Issues for the Disaster Recovery Option for BrightStor ARCserve Backup r11.5 SP1

The following section provides information relating to issues affecting the Disaster Recovery Option known to exist in this service pack:

On Windows 2000 and older versions of Windows, when you create a machine-specific disk, the disk is not automatically labeled CADRIF, as it is on later versions of Windows. This does not affect the functionality of the Disaster Recovery Option.
If your tape drive is in OBDR (One Button Disaster Recovery) mode, the Windows operating system setup regards the primary master hard drive as the boot disk, by default. If your boot disk is not set to the primary master hard drive, the setup cannot continue.
To address this problem, turn off the primary master disk in BIOS and boot from the tape again.
To avoid this problem, set your boot disk as the primary master disk.

25.0 Documentation Changes for BrightStor ARCserve Backup r11.5 SP1

The following section provides information about items that have not yet been changed in the product documentation for BrightStor ARCserve Backup for Windows r11.5 SP1, but that affect the information in that documentation:

The online help does not currently provide information about the message W6926. The online help should contain the following information:
“W6926: The memory in the tape cartridge has failed, which reduces performance. Do not use the cartridge for further backup operations.” This Tape Engine warning indicates that a hardware error was reported by your devices. Do not continue to use this cartridge for backup jobs. We strongly recommend that you write-protect the cartridge, to ensure that it is used for restore purposes only.
The online help and the Administrator Guide state that the following switch for the ca_merge and ca_scan commands is not supported on Windows:
```
[-currenttapeseq] [-allsessions | -session <session range>]
```
This statement is no longer correct. BrightStor ARCserve Backup has been updated to enable this switch on Windows platforms.
The online help and the Administrator Guide state that the -condition switch is supported for the ca_scan command. This statement is not correct. This switch is not supported.
In the tapecopy Destination Options section of the Using Command Line Utilities, the Administrator Guide describes the following format for the Destination random ID option, used to copy to tapes with a random ID:
```
-idr <Destination Random ID>
```
This format is incorrect. The format of the Destination random ID option should be the following:
```
-idd <Destination Random ID>
```
The Agent for Microsoft SharePoint Guide states that the SQL Agent Filter Option is supported by the agent. This statement is not correct. The SQL Agent Filter Option is not supported by the Agent for Microsoft SharePoint.
The Agent for Microsoft SharePoint Guide states the following:

Important! Transaction logs are not backed up during full or differential database backups. You must back them up by running separate Transaction log backups.

This statement is partially correct and requires clarification. During a full database or differential backup, enough of the transaction log is backed up to produce a consistent database for when the database is restored.

The Image Option Guide states the following:
You can set the registry values for SyncTimeout, InactivityPeriod, and PreviewFilename in the following:
```
Software\ComputerAssociates\BrightStor ARCserve Backup\TapeEngine\Image
```
This statement is incorrect because this key does not exist by default. To change the default registry values for SyncTimeout, InactivityPeriod, and PreviewFilename, you must create this key and set the values for these parameters.

26.0 BrightStor ARCserve Backup for Windows r11.5 Readme

27.0 Welcome

The following sections provide information originally released with BrightStor ARCserve Backup for Windows r11.5 and included in this release of BrightStor ARCserve Backup for Windows r11.5 SP3.

28.0 Operating System Support for BrightStor ARCserve Backup r11.5

Note: For information added to BrightStor ARCserve Backup for Windows r11.5 SP3, see the section Operating System Support.

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

Windows XP Professional 32-bit (Server, Manager, and Client Agent) and 64-bit (Client Agent only) (at minimum, Service Pack 1 and Service Pack 2)
Windows Server 2003 Web Edition (32-bit only) and Windows Server 2003 Web Edition Service Pack 1
Windows Server 2003 Standard Edition (32-bit, x64, and IA-64) and Windows Server 2003 Standard Edition Service Pack 1
Windows Server 2003 Enterprise Edition (32-bit, x64, and IA-64) and Windows Server 2003 Enterprise Edition Service Pack 1
Windows 2000 Professional 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)
Windows 2000 Server 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)
Windows 2000 Advanced Server 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)
Windows 2000 Cluster Server (2 node Advanced Edition)
Windows Server 2003 Cluster 32-bit, x64, and IA-64
Windows 2000 and Windows 2003 Datacenter 32-bit and 64-bit
Windows Powered NAS (2000)
Windows Storage Server 2003
Windows Small Business Server 2000
Windows Small Business Server 2003 and Windows Small Business Server 2003 plus Service Pack 1
Microsoft Virtual PC 2004, Microsoft Virtual Server 2005 (BrightStor ARCserve Backup base product, BrightStor® ARCserve® Backup Client Agent for Windows, and BrightStor® ARCserve® Backup Agent for Open Files only)
VMWare GSX Server version 3.0 and 3.1, VMware ESX Server version 2.5 and 2.51, VMware Workstation version 4.0, 4.5, and 5.0 (BrightStor ARCserve Backup base product, BrightStor ARCserve Backup Client Agent for Windows, and BrightStor ARCserve Backup Agent for Open Files only)

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

28.1 Support for 64-bit Windows Platforms

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

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

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

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

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

29.0 System Requirements for BrightStor ARCserve Backup r11.5

Note: For information added to BrightStor ARCserve Backup for Windows r11.5 SP3, see the section System Requirements.

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

29.1 BrightStor ARCserve Backup Base Product

The minimum system requirements for BrightStor ARCserve Backup are:

CPU: 350 MHz
RAM: 512 MB
Disk Space: 500 MB free disk space
Internet Explorer: Version 6.0

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

29.2 Disk Staging Option

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

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

Windows 2000
Windows XP Professional
Windows 2003
Windows Storage Server 2003

29.3 Client Agents

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

Hardware Requirements

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

Windows-based platforms:
- CPU: 200 MHz
- Memory: 256 MB RAM
- Disk space: 100 MB
NetWare-based platforms:
- CPU: NetWare version 4.2 requires an 80586 processor with 128 MB RAM; NetWare versions 5.1, 6.0 and 6.5 require a Pentium-class processor with at least 512 MB RAM
- Disk space: 20 MB
UNIX-based platforms:
- Memory: 128 MB RAM
- Disk space: 16 MB
Linux-based platforms:
- Memory: 128 MB RAM
- Disk space: 10 MB

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

Minimum 10 MB hard disk space
Minimum 128 MB RAM

Software Requirements

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

BrightStor® ARCserve® Backup Client Agent for Windows:
- Windows XP Professional 32-bit (Server, Manager, and Client Agent) and 64-bit (Client Agent only) (at minimum, Service Pack 1 and Service Pack 2)
- Windows Server 2003 Web Edition (32-bit only)
- Windows Server 2003 Standard Edition (32-bit, x64, and IA-64)
- Windows Server 2003 Enterprise Edition (32-bit, x64, and IA-64)
- Windows 2000 Professional 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)
- Windows 2000 Server 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)
- Windows 2000 Advanced Server 32-bit (Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1)
- Windows 2000 Cluster Server (2 node Advanced Edition)
- Windows 2003 32-bit, x64, and IA-64
- Windows Server 2003 Cluster 32-bit, x64, and IA-64
- Windows 2000 and Windows 2003 Datacenter 32-bit and 64-bit
- Windows Powered NAS (2000)
- Windows Storage Server 2003
- Windows Small Business Server 2000
- Windows Small Business Server 2003 and Windows Small Business Server 2003 plus Service Pack 1
- Windows NT
BrightStor® ARCserve® Backup Client Agent for NetWare:
- Novell NetWare version 4.2
- Novell NetWare version 5.1
- Novell NetWare version 6.0 or 6.5 SP1, SP2, or SP3
BrightStor® ARCserve® Backup Client Agent for UNIX:
- Solaris 2.6, 7, 8, 9, and 10 SPARC
- Solaris 9 and 10 (x86 32-bit)
- Solaris 10 AMD64
- IBM AIX 4.3.3, 5L v5.1, v5.2, and v5.3
- HP-UX 11.0, 11.11, and 11.23 PA RISC
- HP-UX 11.22 and 11.23 Itanium (IA64)
- Tru64 v4.0E, v4.0F, v4.0G, v5.0, v5.1, v5.1a, v5.1b
BrightStor® ARCserve® Backup Client Agent for Linux:
- Red Hat 8 and 9
- Red Hat Advanced Server 2.1
- Red Hat Enterprise Linux 2.1 (AS, ES, WS)
- Red Hat Enterprise Linux 3 (AS, ES, WS) (x86, AMD64, and Intel EM64T)
- Red Hat Enterprise Linux 3 Update 4 (AS, ES, WS) (IA-64)
- Red Hat Enterprise Linux 4 (AS, ES, WS) (x86, AMD64, Intel EM64T, and IA-64)
- SuSE Linux Enterprise Server 7
- SuSE Linux Enterprise Server 8 (x86, AMD64, Intel EM64T, and IA-64)
- SuSE Linux Enterprise Server 9 (x86, AMD64, Intel EM64T, and IA-64)
- SuSE Standard Server 8
- SuSE Professional 8, 9, 9.1, 9.2. and 9.3
- SuSE Linux Desktop 1
- Novell Linux Desktop 9
- Turbolinux Enterprise Server 8
- Turbolinux Workstation 8
- Turbolinux 8 for AMD64
- Turbolinux 10 Server
- Turbolinux 10F
- Turbolinux 10 Desktop
- Miracle Linux 2.1
- Miracle Linux 3.0 (x86, AMD64, and Intel EM64T)
- Red Flag Desktop 3.0 and 3.2
- Red Flag Advanced Server 4.0 and 4.1
- Red Flag Data Center Server 4.0
- Red Flag Data Center Server 4.1 (x86, AMD64, Intel EM64T, and IA-64)
- Asianux 1.0
- SCO Linux Server 4.0
- Debian 3.0
BrightStor® ARCserve® Backup Client Agent for Mac OS X:
- Apple Power Mac G4/G5 (Mac OS X 10.2, 10.3, 10.4)
- Apple X Server (Mac OS X 10.2, 10.3, 10.4)
BrightStor® ARCserve® Backup Client Agent for OpenVMS
- VAX 6.2, 7.1, 7.2, 7.3
- AXP 6.2, 7.1, 7.2, 7.3
BrightStor^® ARCserve^® Backup Enterprise Option for AS400:
- AS400 V3 R7 M0 to V4 R5 M0
- AS400 V5 R1 (5.1) V5R2 (5.2)

29.4 Agent for IBM Informix

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

Informix Dynamic Server 9.21, 9.30, 9.40, and 10.0
Agent for IBM Informix
BrightStor ARCserve Backup for Windows

29.5 Agent for Lotus Domino

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

Lotus Domino Server version 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 6.0 for Windows NT 4.0 Service Pack 6a
Lotus Domino Server version 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 5.0.12, 5.0.13, 5.0.13a, 5.0.14, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.5, 6.5.1, 6.5.2, 6.5.3, 6.5.4 for Windows 2000 and Windows Server 2003 Standard Edition, and Enterprise Edition.

29.6 Agent for Microsoft Exchange Server

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

Hardware Requirements

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

The base Microsoft Exchange Server hardware requirements (for information about these requirements, see the Microsoft website)
At least 512 MB RAM
At least 100 MB of free disk space

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

Software Requirements

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

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

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

Microsoft Exchange Server Version 5.5 Service Pack 4
Microsoft Exchange Server Version 2000 Service Pack 3
Microsoft Exchange Server Version 2003 Service Pack 1

29.7 Agent for Microsoft Exchange Server Premium Add-on

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

Hardware Requirements

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

The base Microsoft Exchange Server hardware requirements (For information about these requirements, see the Microsoft website)
At least 512 MB RAM
At least 200 MB of free disk space

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

Software Requirements

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

Microsoft Windows NT 4.0 Service Pack 6a
Microsoft Windows 2000 Service Pack 3, Service Pack 4, or Service Pack 4 Rollup 1
Microsoft Windows 2003
Microsoft Exchange Server Version 5.5 Service Pack 4
Microsoft Exchange Server Version 2000 Service Pack 3
Microsoft Exchange Server Version 2003 Service Pack 1

29.8 Agent for Microsoft SharePoint

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

The Agent for Microsoft SharePoint is supported on the following:
- Windows 2003 Standard
- Windows 2003 Enterprise
- Windows 2003 Web
The agent does not require the BrightStor ARCserve Backup server component.
BrightStor ARCserve Backup must be installed before you install the Agent for Microsoft SharePoint Configuration Wizard. The Configuration Wizard is supported on all operating systems on which BrightStor ARCserve Backup is supported.
The Agent for Microsoft SharePoint requires at least one of the following:
- Microsoft SharePoint Portal Server 2003 SP1
- Microsoft Windows SharePoint Services 2.0 SP1
The agent is supported on Windows Small Business Server 2003 and has been tested on Windows 2003 Service Pack 1 and Windows Small Business Server 2003 Service Pack 1.

29.9 Agent for Microsoft SQL Server

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

Microsoft SQL Server 7.0 with Service Pack 2, Service Pack 3, or Service Pack 4
Microsoft SQL Server 2000 with Service Pack 3 or Service Pack 3a
Microsoft SQL Server Desktop Engine (MSDE) 2000 with Service Pack 3 or Service Pack 3a
Microsoft SQL Server 2005 Beta 2 (x86) and the March 3, 2005 Community Technology Preview

BrightStor ARCserve Backup is also required.

Microsoft SQL Server 2005 Support

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

The agent is compatible with Microsoft SQL Server 2005 Beta 2 and the March 3, 2005, April 18, 2005, and June 7, 2005 Community Technology Preview for x86-based (32-bit) systems on Windows 2000 SP3 and SP4 and on Windows 2003.
The agent is compatible with the Microsoft SQL Server 2005 March 3, 2005, April 18, 2005, and June 7, 2005 Community Technology Preview for x64-based (Athlon64, Opteron, Xeon EM64T) and IA-64 (Itanium) systems on Windows 2003 SP1.
The agent is expected to be compatible with Microsoft SQL Server 2005 Beta 3 for x86, x64 and IA-64 systems.

Microsoft SQL Server 7.0 Support

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

Microsoft Windows NT Server 4.0 Service Pack 6a
Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1
Windows 2003

Microsoft SQL Server 2000 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 2000, Service Pack 3 and Service Pack 3a on the following operating systems:

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

Support for 64-bit Systems

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

Microsoft SQL 2000 64-bit Edition for IA-64 on Windows 2003 for Itanium-based systems
Note: If you are using Microsoft SQL Server 2000 64-bit Edition Service Pack 4, you should be aware that the service pack is missing a 32-bit DLL. Without this DLL, you cannot perform virtual device-based backups. Contact Microsoft to obtain help with this issue.
Microsoft SQL 2000 for x86 (32-bit) on Windows 2003 SP1 for x64-based systems

Microsoft SQL Server Desktop Engine (MSDE) 2000 Support

The Agent for Microsoft SQL Server supports MSDE 2000, Service Pack 3 and Service Pack 3a on the following operating systems:

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

29.10 Agent for Open Files

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

The Agent for Open Files Server Engine requires one of the following operating systems:
- Windows NT 4.0
- Windows 2000
- Windows XP x86, x64, and IA-64
- Windows Server 2003 Web Edition, Standard Edition, or Enterprise Edition x86, x64, and IA-64
To manage the Agent for Open Files on NetWare servers, the Novell NetWare Client software must be installed. The agent does not support the Microsoft NetWare Client.
The Agent for Open Files NetWare Server Engine requires a server running Novell NetWare version 4.2, 5.1, 6.0, or 6.5.

29.11 Agent for Oracle

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

Oracle Server version 8, 8i, 9, 9i, or 10g
Oracle Fail Safe (OFS) Cluster version 3.3.1, 3.3.2 and 3.3.3 on 9.2.0.11
Windows NT 4.0 Service Pack 6a, Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1, or Windows 2003

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

29.12 Agent for Sybase

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

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

29.13 Disaster Recovery Option

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

The following versions of Windows are supported for floppy-based disaster recovery:
- Windows NT 4.0 Server with Service Pack 6a (remote only)
- Windows NT 4.0 Workstation with Service Pack 6a (remote only)
- Windows 2000 Professional Edition
- Windows 2000 Server Edition
- Windows 2000 Advanced Server Edition
The following versions of Windows are supported for bootable tape disaster recovery:
- Windows 2000 Professional Edition
- Windows 2000 Server Edition
- Windows 2000 Advanced Server Edition
- Windows XP Professional Edition
- Windows 2003 Web Edition
- Windows 2003 Standard Edition
- Windows 2003 Enterprise Edition
- Windows 2003 SBS Edition
The following versions of Windows are supported for bootable CD disaster recovery:
- Windows 2000 Professional Edition
- Windows 2000 Server Edition
- Windows 2000 Advanced Server Edition
- Windows XP Professional Edition
- Windows 2003 Web Edition
- Windows 2003 Standard Edition
- Windows 2003 Enterprise Edition
- Windows 2003 Datacenter Edition SP1 32-bit
- Windows 2003 SBS Edition

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

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

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

29.14 Image Option

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

29.15 NDMP NAS Option

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

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

Operating System: Windows 2000 or Windows 2003
Memory: Minimum 128MB RAM
Disk Space: Minimum 95 MB

In addition to these requirements, you must meet the following requirements, depending upon the devices you choose:

For Network Appliance devices:
- ONTAP Minimum Version 6.0.1R3
- NAS Server: Models F700 series, F800 series (ONTAP Version is of primary concern, not the model)
For EMC (IP4700) devices:
- Minimum firmware version R2.0 p21
- NAS Server Model: IP4700
For EMC (Celerra) devices:
- Minimum file server version 4.2.9.0
- NAS Server model: Celerra
For PROCOM devices:
- Minimum firmware version: 4.1.3
- NAS Server Model: NetForce 1000 series, 3000 series

29.16 Tape and Optical Library Option

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

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

Windows 2000
Windows XP Professional
Windows 2003

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

Windows 2000
Windows 2003

29.17 Serverless Backup Option

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

BrightStor ARCserve Backup for Windows
Tape Library Option
Storage Area Network (SAN) Option

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

29.18 Tape RAID Option

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

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

29.19 Storage Area Network (SAN) Option

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

BrightStor ARCserve Backup for Windows
Tape Library Option for Windows

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

Windows 2000
Windows 2003

29.20 Enterprise Option for StorageTek ACSLS

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

The option is supported on Windows 2000 and Windows 2003.

29.21 Enterprise Option for IBM 3494

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

The option is supported on Windows 2000 and Windows 2003.

29.22 Enterprise Option for SAP R/3 for Oracle

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

Oracle 8, Oracle 8i
Oracle 9, Oracle 9i

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

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

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

29.23 Enterprise Option for Advantage Ingres

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

Microsoft Windows NT 4.0 Service Pack 6a
Microsoft Windows 2000 Service Pack 1 or Service Pack 2
Microsoft Windows XP or Windows 2003
Advantage Ingres Database Server 2.0, 2.5, 2.6 SP2, or 3.0

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

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

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

29.24 Enterprise Option for VSS Hardware Snap-Shot

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

On the Production Server
- Microsoft Windows Server 2003 Enterprise Edition or Datacenter Edition
- Microsoft Exchange Server 2003 Service Pack 1 (if Microsoft Exchange 2003 Server is installed)
- Microsoft SQL Server 2000 Service Pack 3a (if Microsoft SQL 2000 Server is installed)
- BrightStor ARCserve Backup Client Agent for Windows r11.5
- BrightStor ARCserve Backup Enterprise Option for VSS Software Snap-Shot
- VSS Hardware Provider for your disk array, obtained from your disk array vendor
On the Backup Server
- Microsoft Windows Server 2003 Enterprise Edition or Datacenter Edition
- Microsoft Exchange System Management Tools (if you are using the option to protect Microsoft Exchange 2003 Server on the Production Server)
- Microsoft Exchange Server 2003 Service Pack 1 (if Microsoft Exchange Server 2003 Service Pack 1 is installed on the Production Server)
- BrightStor ARCserve Backup for Windows r11.5
- BrightStor ARCserve Backup for Windows r11.5 Enterprise Module
- License for BrightStor ARCserve Backup Enterprise Option for VSS Hardware Snap-Shot
- VSS Hardware Provider for your disk array, obtained from your disk array vendor

29.25 Client for VSS Software Snap-Shot

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

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

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

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

30.0 Installation Considerations for BrightStor ARCserve Backup r11.5

Note: For information added to BrightStor ARCserve Backup for Windows r11.5 SP3, see the section Installation Considerations.

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

30.1 BrightStor ARCserve Backup Base Product

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

BrightStor ARCserve Backup installs its services under the Local System Account. By default, the option Allow service to interact with desktop is not selected.
To install BrightStor ARCserve Backup, you must log in to your computer using an administrator account or a user account with administrator privileges.
If you are prompted to reboot your machine during the remote installation process, you must reboot the machine manually for the remote installation to be successful.
For successful integration with this release of BrightStor ARCserve Backup, you must use BrightStor® ARCserve® Backup for Laptops & Desktops r11.1 SP1.
If you are using BrightStor® High Availability (formerly SurviveIT™2000), and BrightStor ARCserve Backup, the BrightStor High Availability manager must be installed before you install BrightStor ARCserve Backup. If BrightStor ARCserve Backup is already installed, contact CA Technical Support.
If you are using BrightStor High Availability, you must ensure that you applied the latest patches for BrightStor High Availability before installing BrightStor ARCserve Backup.
If you are installing BrightStor ARCserve Backup on a system where BrightStor High Availability is installed and running, you must stop all replication tasks before restarting your system to allow BrightStor ARCserve Backup to update shared files. Because of this requirement, you should be aware that your system is unprotected by BrightStor High Availability while it is restarting.
If you are installing BrightStor ARCserve Backup with a Microsoft SQL Server database, you must ensure that you have upgraded to the correct version of the ODBC driver:
1. Change the ODBC Network Libraries setting to TCP/IP, if necessary.
2. Run SetupSQL.exe from BAB_HOME, or install Microsoft SQL 2000 or Microsoft SQL 7.0 server or client.
3. Enter Microsoft SQL security, or upgrade your ODBC driver from the web site, or install Microsoft SQL 2000 7.0 server or client.
If you are installing BrightStor ARCserve Backup agents on a machine where eTrust® InoculateIT® or eTrust® Antivirus is running, the following driver update must be applied to both the BrightStor ARCserve Backup server and the client machine: http://supportconnectw.ca.com/premium/antivirus/downloads/nt/4.5/ildrvupdate.asp
When you create equivalences using ca_Auth.exe, these equivalences are created for user names according to the Windows domain to which they belong. For example, the equivalence for Domain1\User1 is different from WinDomain2\User1 and from User1. By default, all command line utilities detect the domain name of the logged in user to validate access. To allow backward compatibility, existing equivalences without domain names are also accepted. However, this can introduce a security risk for your environment because a user with the same name but belonging to another Windows domain can use the command line utilities. We recommend that you delete existing equivalences and recreate them for all users to ensure that the correct domain name is included.
If you are upgrading to this release, the iSponsor cannot immediately communicate with BrightStor ARCserve Backup due to the change in the way in which equivalences are created. To allow the iSponsor to communicate with BrightStor ARCserve Backup, execute the following command
```
BAB_HOME\Authsetup.exe /p <caroot_password>
```
This command creates the equivalence for the BrightStor ARCserve Backup System account to allow the iSponsor to work correctly.

30.2 Client Agents

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

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

30.3 Agent for Lotus Domino

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

To upgrade from BrightStor® ARCserve® 2000 to BrightStor ARCserve Backup, you must first uninstall the BrightStor ARCserve 2000 agent. However, if the BrightStor ARCserve 2000 agent is for Lotus Notes for Windows (BAOF Version), you must first uninstall the BrightStor ARCserve 2000 agent, and then uninstall the embedded BAOF manually using the following procedure:
1. Uninstall the BrightStor ARCserve 2000 Agent for Lotus Notes for Windows (BAOF Version).
2. Insert the original BrightStor ARCserve 2000 CD, or ensure that an image of the CD is available.
3. From the Windows command prompt, run the following command:
```
msiexec.exe /x FULL PATH TO BAOFNTAG.MSI PRODUCTS=2
```
  For example, where the original CD is used and inserted in drive F, enter the following at the prompt:
```
msiexec.exe /x f:\IntelNT\Notes.DBA\baofntag.msi PRODUCTS=2
```

30.4 Agent for Microsoft SharePoint

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

BrightStor ARCserve Backup must be installed before you install the Agent for Microsoft SharePoint Configuration Wizard. The Configuration Wizard is supported on all operating systems on which BrightStor ARCserve Backup is supported.
To install and configure the Agent for Microsoft SharePoint in an environment with a firewall provided by Windows 2003 Server Service Pack 1 enabled, you must perform the following procedure:
Note: This procedure refers only to ports for the Agent for Microsoft SharePoint. You may have to open other ports to allow Microsoft SharePoint Portal to work properly. Verify that the Microsoft SharePoint Portal is working correctly before performing the following procedure.
1. Configure the firewall for the BrightStor ARCserve Backup base product using the instructions in the section Known Issues for the Base Product in this Readme document.
2. Ensure that the firewalls on any remote computers hosting the SharePoint installation are configured to allow exceptions.
3. Install the Agent for Microsoft SharePoint from the BrightStor ARCserve Backup installation CD. The Agent for Microsoft SharePoint Configuration wizard starts automatically.
4. Complete the Server Selection information and click Next. Although the SharePoint Router Agent is installed, you receive the following error message, indicating that the firewall is blocking access to the SharePoint Router Agent:
```
The router was not found on the selected machine. Check that the router is running correctly or install a router by selecting install.
```
5. Add the UnivAgent.exe executable to the Windows Firewall exception list on the machine on which the SharePoint Router Agent has been installed. This executable is found in the following directory
```
C:\Program Files\CA\SharedComponents\BrightStor\UniAgent
```
6. In the wizard, clear the Install router onto machine checkbox and click Next. The wizard obtains the SharePoint topology information, allowing you to proceed with either an Automatic or Custom installation type. Proceed to the Install screen of the wizard and click Next to install the required agents.
7. A list of computers and the agents installed on them appears. Before you can use the Agent for Microsoft SharePoint, these agents must be added to the Window Firewall exception list on those machines.
8. If you have the BrightStor External Data Agent installed on any computers, add the UnivAgent.exe executable to the Windows Firewall exception list. This executable is found in the following directory
```
C:\Program Files\CA\SharedComponents\BrightStor\UniAgent
```
9. If you have the Agent for Microsoft SQL Server installed on any computers, add the following to the Windows Firewall exception list:
  – Select File and Printer Sharing and choose TCP 139
  – dbasvr.exe, found in the following directory:
```
C:\Program Files\CA\SharedComponents\BrightStor\DBACommon
```
The Agent for Microsoft SharePoint can now be used successfully from the BrightStor ARCserve Backup server.

30.5 Agent for Microsoft SQL Server

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

If you are installing the agent with Microsoft SQL Server 2000, the Agent for Microsoft SQL Server requires Microsoft SQL Server 2000 with Service Pack 3, Service Pack 3a, or Service Pack 4.
Windows Small Business Server 2003 Standard Edition does not include Microsoft SQL Server 2000. However, you can install Microsoft SQL Server 2000 separately, but you must install Service Pack 3, Service Pack 3a, or Service Pack 4.
Note: Windows Small Business Server 2003 Premium Edition includes Microsoft SQL Server 2000, Service Pack 3.

30.6 Agent for Open Files

If you install the Microsoft Cluster Service after you have installed the Agent for Open Files, you must restart the system to provide the agent with open file access to the shared storage resources of the cluster.

30.7 Disaster Recovery Option

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

When upgrading to BrightStor ARCserve Backup r11.5, you should recreate the machine-specific disk for all protected machines. This ensures that you are using the option's latest executables. For more information about how to update machine-specific disks, see the Disaster Recovery Option Guide.
When you upgrade to BrightStor ARCserve Backup r11.5, a directory, called OldDR, is created to store information from old backup operations. If you want to create a machine-specific disk from an old backup, you must do one of the following:
- Rename the OldDR directory to DR
- Copy the machine_name directories to the DR directory and create the machine-specific disks.

31.0 General Considerations for BrightStor ARCserve Backup r11.5

Note: For information added to BrightStor ARCserve Backup for Windows r11.5 SP3, see the section General Considerations.

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

We recommend using the Agent for Open Files when backing up the Citrix MetaFrame Presentation Server 3.0.
Before restoring information to the Citrix Access Suite, stop the CitrixXTE Service. After the restore operation is complete, run a discovery in the Access Manager.
In the BrightStor® ARCserve® Backup Unicenter® Integration Option, the Unicenter® component previously called Workload Management is now the Job Management Option in Unicenter® Network and Systems Management r11.
The following files are not backed up during backup jobs:
- DOS System files:
  - The following Windows files:
    386SPART.PAR
    386SPART.TMP
    SPART.PAR
    WIN386.SWP
  - DoubleSpace Files (DBLSPACE with any extension)
  - DriveSpace Files (DRVSPACE with any extension)
  - Stacker Files (STACVOL.DSK)
  - BTrieve delta files
- The following Win32System Files:
  - PAGEFILE.SYS
  - NETLOGON.CHG
  - NTUSER.DAT.LOG
  - CPL.CFG
  - EA DATA. SF
- The following BrightStor ARCserve Backup files:
  - RDS.BAK
  - RDS.LOG
- The following Registry Keys:
  - \\HKEY_LOCAL_MACHINE\SYSTEM\CLONE
  - \\HKEY_LOCAL_MACHINE\HARDWARE
  - \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ BackupRestore\FilesNotToBackup (and all files specified)
- Registry files with the extensions *.ALT and *.LOG
- Cluster installation directory files (typically the WINNT\cluster folder), Files with no extension, and files with the extension *.LOG
- \%ARCserve install folder%\temp folder
- \Document and Settings\Administrator\Local Settings\Temp folder
- %systemroot%\Temp (and all subfolders)
- \RECYCLER folder
- Folders for file system devices
- If database agents are installed, all files backed up by the agents are skipped
- Database folders in the BrightStor ARCserve Backup home directory are skipped during regular file backup operations. If the server uses the Raima database, these folders are backed up by the database sessions.
You can manage BrightStor ARCserve Backup for NetWare r11.1 with the BrightStor ARCserve Backup for Windows r11.5 Manager.

32.0 Known Issues for BrightStor ARCserve Backup r11.5

The following sections provide information about issues known to exist in BrightStor ARCserve Backup for Windows r11.5 that have been verified as existing in the release of BrightStor ARCserve Backup for Windows r11.5 SP2.

Note: For information added to BrightStor ARCserve Backup for Windows r11.5 SP3, see the section Known Issues.

32.1 Portmapper Conflicts with BrightStor ARCserve Backup

If BrightStor ARCserve Backup detects port 111 conflicts, indicating that it is using the same port number for the CA Remote Procedure Call server service as a previously installed portmapper, BrightStor ARCserve Backup automatically switches to another port number.

To avoid having other software affected by a similar problem, change the Automatic status of the CA Remote Procedure Call server service to Manual. If you have installed BrightStor ARCserve Backup in a Microsoft Cluster Services environment, change the Automatic status of the CA Remote Procedure Call server service to Disabled. This enables you to avoid similar port conflicts after the system has completed the boot process.

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

Create the DWORD DelayedRegistration in the following:

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

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

32.2 Known Issues for the Base Product

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

If you select a non-default IP address for a client agent node, you must perform the following procedure to update the IP address to the new address, to allow you to add machines using AutoDiscovery:
1. On the agent machine, restart the discovery service (dsconfig.exe).
2. From the Backup Manager of the base server, delete the old machine object.
3. On the base server, restart the discovery service or launch AutoDiscovery using dsconfig.exe.
4. From the Backup Manager, add the machine with the new IP address using AutoDiscovery.
5. If you have a scheduled job in the queue, delete that job and recreate it to ensure that it runs properly.
Due to a netBIOS limitation, computer names longer than 15 characters are truncated to 15 characters, including when you set up a host server.
If you install Windows Server 2003 Service Pack 1 using an Emulex Fibre Channel Card, you must download the latest Windows 2003 Storport HBA drivers from the Emulex website. A problem with the Emulex driver released with Windows 2003 SP1 prevents BrightStor ARCserve Backup from initializing correctly unless you update the Emulex driver.
If you use Windows 2003 server with Service Pack 1 and the firewall enabled or if you upgrade your Windows XP system with Windows XP Service Pack 2, the upgrade to Service Pack 2 enables the firewall and blocks all ports by default. You must perform one of the following procedures to use BrightStor ARCserve Backup with Windows XP Service Pack 2.
Note: These methods can be applied to Windows 2003 Server systems with Service Pack 1 and the firewall enabled.
Method 1 (recommended):
1. In the Start menu, click Run, enter gpedit.msc, and press Enter.
  Note: This step does not apply to Windows 2003 Server SP1.
2. The Group Policy configuration GUI appears. In the Group Policy Configuration GUI, select Local Computer Policy, Computer Configuration, Windows Setting, Security Setting, Local Policy, Security Option.
  Note: This step does not apply to Windows 2003 Server SP1.
3. Change the setting Network access:Sharing and security model for local accounts to Classic - local users authenticate as themselves.
  Note: This step does not apply to Windows 2003 Server SP1.
4. The following key RPC and subkey RestrictRemoteClients must be created manually and the value set to 0:
```
[DWORD]HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\RPC\RestrictRemoteClients
```
  Note: This step does not apply to Windows 2003 Server SP1.
5. Access the Security Center (on Windows XP SP2) or Windows Firewall (on Windows 2003 Server SP1) and enable the firewall.
6. Add the following executables (if applicable) to the Security Center exception list (these can be found in the CA BrightStor ARCserve home directory):
  – caauthd.exe
  – cadiscovd.exe
  – caloggerd.exe
  – casdscsvc.exe
  – caserved.exe
  – casmrtbk.exe
  – catirpc.exe
  – dbeng.exe
  – jobeng.exe
  – ldbserver.exe
  – lqserver.exe
  – mediasvr.exe
  – msgeng.exe
  – tapeeng.exe
  – univagent.exe (if the Client Agent is installed)
  – carunjob.exe
  – dbasvr.exe (if any database agents are installed)
  – dbasqlr.exe (if the Agent for Microsoft SQL Server is installed)
  – dbaexchr.exe (if the Agent for Microsoft Exchange Server is installed)
7. If you have the Client Agent or any database agent installed, on the Exceptions tab, select File and Printer Sharing.
8. Restart the Windows XP Service Pack 2 machine and start BrightStor ARCserve Backup services.
Method 2:
1. In the Start menu, click Run, enter gpedit.msc, and press Enter.
2. The Group Policy configuration GUI appears. In the Group Policy Configuration GUI, select Local Computer Policy, Computer Configuration, Windows Setting, Security Setting, Local Policy, Security Option.
3. Change the setting Network access:Sharing and security model for local accounts to Classic - local users authenticate as themselves.
  Note: This is the default setting on Windows 2003 Server SP1.
4. The following key RPC and subkey RestrictRemoteClients must be created manually and the value set to 0:
```
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\RPC\RestrictRemoteClients
```
5. Access the Security Center and turn the firewall off.
6. Restart the Windows XP Service Pack 2 machine and start the BrightStor ARCserve Backup services.
If you use the Master Setup to install BrightStor ARCserve Backup remotely to a system in another Windows domain, you may receive a message indicating that the installation failed even if it is successful because the Master Setup cannot accurately detect the activity on the remote machine in the other domain because of firewalls or due to lost network connections. Check the installation status on the remote machine to verify that the installation succeeded.
If you enable both Success and Failure for Audit object access under Local Security Policy, Local Policies, Local Audit Policy, you may receive multiple Success Audit messages under Security Events in the Event Viewer. To avoid receiving multiple Success Audit messages, perform the following procedure:
1. Create a key called MessageEngine Under the following registry key:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Admin
```
2. Create a DWORD value called Impersonate under the following key and set it to 0:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Admin\MessageEngine
```
3. Reboot the Windows system.
NetWare Services no longer appear under the Network branch in the Backup and Restore Managers and BrightStor ARCserve Backup only supports Client Agent for NetWare backups when creating NetWare sessions from a BrightStor ARCserve Backup for Windows host.
If you import a DLTWORM-capable media into a library which has not converted to WORM yet, the Quick erase and Convert to WORM media option is disabled. You must perform a full inventory of tapes to enable this option.
If you use WORM media as the destination for any cross-platform jobs involving the BrightStor ARCserve Backup for UNIX Agent for Oracle or the BrightStor ARCserve Backup for Linux Agent for Oracle, these agents may not behave as expected. Child jobs are submitted by the agent, and, because WORM media is not supported on the UNIX or Linux agents, these child jobs may use destinations other than the WORM media.
When configuring the primary and secondary servers in a domain, the configuration must be same on all machines in the domain. You must define the secondary name when you install the primary to allow the secondary server information to be validated for security reasons. You can reconfigure the secondary name using the command line utility ca_conf.exe or edit the config\discovery.cfg file in the BrightStor ARCserve Backup installation folder.
Installing 32-bit components on a 64-bit machine generates two copies of the file PortsConfig.cfg on the machine. The PortsConfig.cfg file for the 64-bit components is in C:\Program Files\CA\SharedComponents\BrightStor and the PortsConfig.cfg file for the 32-bit components is in C:\Program Files (x86)\CA\SharedComponents\BrightStor. If you make changes to one, you must make the same changes to the other, or the components may not be able to contact one another.
Media checks using the Preflight Check are not supported for Disk Staging jobs.
In database agent backup operations using the Staging option, the backup method is set as a local option but copy and purge policies are set as global options.
If you install agents on cluster nodes, do not back up the physical nodes (the private drives C: and D:) or non-shared disks through preferred share using the virtual server IP address, because virtual servers can be moved from one node to another. For example, if virtual server 1 resides on physical node 1 and you backed up virtual server 1 through preferred share, the non-shared drives on physical node 1 are also backed up. If you move virtual server 1 to physical node 2, and perform a Restore to Original Location, the non-shared drives from physical node 1 are restored to physical node 2.
When you upgrade from older versions of BrightStor ARCserve Backup, tapes with lowercase letters in the tape names are listed in the Session View of the Restore Manager using all uppercase letters. In addition, you cannot expand the tape in the Session View. To address this problem, perform the following procedure:
1. In the Database Manager, expand the Media Records. The tape name appears at least twice, once in uppercase letters and at least once in lowercase letters.
2. Delete the uppercase entry. The Restore Manager displays the tape name and details correctly.
During uninstallation of BrightStor ARCserve Backup from non-primary cluster nodes perform the following procedure:
1. In the base home directory, run the following command to unregister the ashell.dll file from non-primary cluster nodes:
```
RegSvr32 /u <original full installation path of ashell.dll>
```
2. Log off from all login sessions, both local and remote (you do not have to reboot).
3. Uninstall BrightStor ARCserve Backup from the primary cluster node.
4. Log back in to each non-primary cluster node, copy the required modules for uninstallation, and continue with the uninstallation procedure.
When you uninstall BrightStor ARCserve Backup from non-primary cluster nodes, some files may be left in the BrightStor ARCserve Backup home directory and some registry keys may be left in the following:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs
```
You must remove the files and clean up the registry manually.
If you use the ca_conf command line utility to change the BrightStor ARCserve Backup domain name to a new domain name, you will encounter the following problems:
- The caroot password is reset to blank
- Equivalences are reset for all users
- The caroot password cannot be reset using the bconfig.exe utility
To correct these problems, run the ca_conf utility and perform the following procedure:
1. Set the password for the caroot user using the authsetup command line utility with the following syntax:
```
authsetup /p <new carootPassword>
```
  This command also creates equivalence for the user currently logged into BrightStor ARCserve Backup.
2. Recreate the equivalences for all users manually.
For more information, see the ca_auth Command section of the Using Command Line Utilities appendix of the Administrator Guide.

32.3 Known Issues for the Client Agent

The following issues related to the Client Agent are known to exist in this release:

For the Client Agent for Windows, installing 32-bit components on a 64-bit machine generates two copies of the file PortsConfig.cfg on the machine. The PortsConfig.cfg file for the 64-bit components is in C:\Program Files\CA\SharedComponents\BrightStor and the PortsConfig.cfg file for the 32-bit components is in C:\Program Files (x86)\CA\SharedComponents\BrightStor. If you make changes to one, you must make the same changes to the other, or the components may not be able to contact one another.
You cannot use the Client Agent for NetWare included in this release with the BrightStor ARCserve Backup for NetWare r11.1 Manager. The Client Agent for NetWare included in this release requires the BrightStor ARCserve Backup for Windows r11.5 Manager GUI.
When running the Client Agent for NetWare on NetWare 4.2, the agent requires the clibaux.nlm enhancement module provided by Novell (refer to Novell Technical Information Document 2955000).
When a full NetWare machine is selected for backup, the NDS session is not backed up. You must explicitly select the NDS session and other volumes to be backed up.
The Client Agent for NetWare handles only one job at a time. If a backup job includes the NetWare volume and NDS of the same node, it creates two nodes for the job in the job package, and, because multiplexing or multistreaming jobs create two jobs for the NetWare node and the two jobs run simultaneously, the agent rejects the second job.
The NetWare Services branch has been removed from the Network tree in the Backup and Restore Managers. To back up a NetWare machine from the BrightStor ARCserve Backup host, you must install the Client Agent for NetWare on the machine.
Whole node backup operations are not supported with the Client Agent for AS400.

32.4 Known Issues for the Agent for IBM Informix

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

Your Informix server should be installed on a Windows NT 4.0 or Windows 2000 machine in a Windows Domain. If you install Informix on a standalone Windows NT 4.0 server or a Windows NT workstation, the Informix backup utility does not allow you to back up your database to a remote BrightStor ARCserve Backup server. You must use the Backup and Restore Managers from BrightStor ARCserve Backup to submit the backup and restore jobs.
If you use the Informix Backup and Restore utility, rather than the Backup Manager, you must define security information using the Informix Agent Configuration utility dbacfg before submitting any backup or restore jobs.
When using remote BrightStor ARCserve Backup to back up or restore Informix server, the real backup and restore jobs created by the Informix Server are scheduled on the BrightStor ARCserve Backup server based on the local time from the Informix server. Therefore, time differences between the BrightStor ARCserve Backup machine and the Informix server machine can cause backup or restore delay. To prevent this delay, synchronize the time between both machines.
When using the Client Agent with the Restore by Tree method for your restore operation, databases appear under the Microsoft Windows Network icon in the Restore Manager.
The agent supports only the Restore by Tree method in the Restore Manager.
For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up.
The NetLogon service must be started to support pass-through authentication of account logon events for computers in a domain.

32.5 Known Issues for the Agent for Microsoft SharePoint

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

If a Microsoft SQL database is backed up using both the Agent for Microsoft SQL Server and the Agent for Microsoft SharePoint, the backup history for the database in the SharePoint branch of Restore by Tree will only include backups performed using the Agent for Microsoft SharePoint, while the backup history for the database in the Microsoft SQL Server branch of Restore by Tree lists all backups performed using both agents. This issue also applies to the Agent for Microsoft SQL Server.
If the Agent for Microsoft SQL Server and the database component of the Agent for Microsoft SharePoint are both deployed on the same machine, the SharePoint databases are included in whole-instance backups performed by the Agent for Microsoft SQL Server. This issue also applies to the Agent for Microsoft SQL Server.
The username entered in the Agent for Microsoft SharePoint Configuration Wizard must have administrative access to all machines in the SharePoint server farm.
Performance may be slowed when backing up or restoring search indexes, as these operations may consume 100% of your CPU resources if the SharePoint server used satisfies only the minimum hardware requirements for Microsoft SharePoint Portal Server. See the Microsoft SharePoint Portal Server Administrator's Guide for more information about hardware requirements.

32.6 Known Issues for the Agent for Microsoft SQL Server

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

If a Microsoft SQL database is backed up using both the Agent for Microsoft SQL Server and the Agent for Microsoft SharePoint, the backup history for the database in the SharePoint branch of Restore by Tree will only include backups performed using the Agent for Microsoft SharePoint, while the backup history for the database in the Microsoft SQL Server branch of Restore by Tree lists all backups performed using both agents. This issue also applies to the Agent for Microsoft SharePoint.
If the Agent for Microsoft SQL Server and the database component of the Agent for Microsoft SharePoint are both deployed on the same machine, the SharePoint databases are included in whole-instance backups performed by the Agent for Microsoft SQL Server. This issue also applies to the Agent for Microsoft SharePoint.
Installing 32-bit components on a 64-bit machine generates two copies of the file PortsConfig.cfg on the machine. The PortsConfig.cfg file for the 64-bit components is in C:\Program Files\CA\SharedComponents\BrightStor and the PortsConfig.cfg file for the 32-bit components is in C:\Program Files (x86)\CA\SharedComponents\BrightStor. If you make changes to one, you must make the same changes to the other, or the components may not be able to contact one another.
After upgrading Microsoft SQL Server (for example, from SQL Server 7.0 to SQL Server 2000) or installing additional instances, you must run the Account Configuration utility to update the agent with the appropriate changes. If you do not run the Account Configuration utility, BrightStor ARCserve Backup Agent for Microsoft SQL Server will be unaware of the new or changed instances, and you may not have access to additional instances or the additional features of the updated instance. You should also perform your first backup of the upgraded or new instances immediately after running the Account Configuration utility. For information about account configuration, see the Agent for Microsoft SQL Server Guide.
If an error message appears when you restore and move a database that uses a long file name, rename the database files using shorter file names, and perform the restore operation on the database.
When backing up or restoring a remote SQL database using the TCP/IP protocol, the TCPtimeout parameter defines how long the BrightStor ARCserve Backup Server waits for a response from the agent. This prevents problems such as network errors from causing jobs to wait forever for a response that might not come. Once this time-out period is expired, the waiting job fails with a network error.
However, when a large remote SQL database is restored, particularly when it involves creation of SQL data files, such as when you restore to a different SQL Server, the agent for SQL cannot reply immediately because SQL Server takes some time to create the files, and the agent must wait for this to complete before it can respond.
The default timeout value is set to 1200 seconds (20 minutes). This should be extended when you restore a large SQL database involving large data file creations. A large SQL database (60 GB) might require the value to be as long as 7200 seconds (120 minutes). In general, the default value (1200) can handle most SQL database restores, as well as network errors. However, if you have a network error on a large SQL database restore operation, you should increase the time-out value. After the restore is done, reset the value to 1200.
The SQL Agent TCPtimeout key can be found on the BrightStor ARCserve Backup Server machine under:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Common\DBAgentsettings
```
The Microsoft Windows 2003 SharePoint database is stored in a Microsoft SQL Server Desktop Engine (MSDE) instance. The SharePoint instance does not support SQL-native authentication. You must use Windows authentication for this database instance.
Several MSDE-based applications do not include a System Administrator account. The application vendor may provide a backup user with only Backup Operator rights. These MSDE instances must be backed up using Named Pipes. If you are not certain whether your MSDE instance has this restriction, contact your application vendor.
If BrightStor ARCserve Backup and the MSDE application with this requirement are installed on separate computers, you must specify the Named Pipes backup method. To specify the Named Pipes backup method, in the Backup Manager, right-click the MSDE database, select Remote Protocol, and choose Named Pipes.
If BrightStor ARCserve Backup and the MSDE application are installed on the same computer, you must direct BrightStor ARCserve Backup to consider the MSDE database as if it were on a different machine. To do this, perform the following steps:
1. Open the Registry Editor, and find the following registry key:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Common\DBAgentsettings
```
2. In this registry key, add a DWORD Value called DBLocalAsRemote and set its value to 1.
3. In the Backup Manager, add a second entry for the local computer in either the Windows 2000/Windows XP/Windows 2003 Systems or Preferred Shares folder. Expand this new entry to find the MSDE database. Right-click the MSDE database, select Remote Protocol, and choose Named Pipes.
Backup with Compare and Backup with Scan Tape are not performed on agent sessions.
If using the BrightStor ARCserve Backup Client Agent and the Restore by Tree method for your restore operation, databases are displayed under the Microsoft Windows Network icon in the Restore Manager.
The BrightStor ARCserve Backup manager and the BrightStor ARCserve Backup Client Agent must be stopped before uninstalling and reinstalling BrightStor ARCserve Backup Agent for Microsoft SQL Server if they are installed on the same server as the agent.
If a TCP/IP connection fails, or if the Port number has changed, restart the Backup Agent Remote Service.
If you are performing a remote backup, File and Printer Sharing for Microsoft Networks must be enabled on the agent machine you are backing up.
To support pass-through authentication of account logon events for computers in a domain, the NetLogon service must be started.
If you are using the current version of BrightStor ARCserve Backup and BrightStor ARCserve Backup Agent for Microsoft SQL Server to restore a backup made using BrightStor ARCserve 2000 or an older version of BrightStor ARCserve Backup, and you are using the Named Pipes protocol, perform the following procedure on the computer running the BrightStor ARCserve Backup Server:
1. Open the Registry Editor and select the key
```
KEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\

BrightStor ARCserve SBackup\Base\Task\Common\DBAgentsSettings
```
2. In the Edit menu, select New> DWORD Value. Set the name of this value to SQLProtocol and its value to 0.
3. Resubmit the restore job.
4. After all restore operations using these backups are completed, return to the Registry Editor and delete the SQLProtocol value.
When using Multistriping to back up databases from Microsoft SQL Server 7.0, the child jobs cannot obtain size estimates. While you can view progress in terms of the amount of data backed up, there is no accurate display of the total size of the database, nor of the percentage of the backup completed.
If you are using an agent from a version of BrightStor ARCserve Backup prior to r11 or from a version of BrightStor Enterprise Backup prior to Version 10.5 Service Pack 1, incremental backup jobs cannot determine if a transaction log backup is permitted. Therefore, differential backups are performed.
If you are using an agent from a version of BrightStor ARCserve Backup before r11.1 or any version of BrightStor Enterprise Backup, differential and incremental backup jobs cannot automatically identify new databases that require full backup rather than differential or transaction log backup.
When you log into SQL Server using Windows authentication to perform local or TCP-based backup and restore operations, you must have system administrator rights for SQL Server. This is a Microsoft requirement.
If you uninstall a Microsoft SQL Server or MSDE instance, some components used by other Microsoft SQL Server or MSDE instances on the machine may be deregistered, including the Virtual Devices mechanism used to perform backups. If this occurs, the agent generates Backup Agent Error 511 (“Error creating Virtual Device Interface: COM class not found”) within the error E8604 (“Failed to Start Backup”), or E8605 (“Failed to Start Restore”). To address this error, perform the following procedure:
1. Locate the version of sqlvdi.dll that belongs to the newest version of Microsoft SQL Server or MSDE on the machine.
2. From a command prompt, change to the directory containing the selected sqlvdi.dll, and enter the following command to reregister the Virtual Devices component and re-enable backup operations:
```
regsvr32 sqlvdi.dll
```

32.7 Known Issues for Agent for Open Files

The following issues related to the Agent for Open Files are known to exist in this release:

If you are upgrading the Agent for Open Files on a remote computer using Unicenter Software Delivery, you must reboot the target machine to complete the installation process successfully.
If you are running eTrust AntiVirus 7.1.192 and the Agent for Open Files on the same machine, you must apply a patch to the machine to avoid experiencing slow performance. Contact eTrust Antivirus Technical Support to obtain this patch.
The Agent for Open Files does not provide the eTrust Real-Time scan engine with access to open files to prevent viruses from presenting the scan engine with a version of the infected file concealed as an uninfected file.
When prompted to reboot your machine during remote installation, reboot the machine manually for the remote installation to be successful.
The agent may not start if it detects that an Open File Management product from another vendor is already running on the server. Multiple Open File Management products cannot function on the same server. To resolve this problem, remove the existing Open File Management product from your server and start the agent.
Because of the way that Windows 2000, Windows Server 2003, and Windows XP provide access to encrypted files for backup applications, access to open files is never prevented, so data integrity is not guaranteed. Therefore, the Windows Server Engine does not support the use of encrypted files and their inclusion in a group specification is ignored. Ensure that all encrypted files are closed while your systems are backed up.
To uninstall the NetWare Server Engine, you must manually delete the directory you selected during installation and remove the OFA.NLM file from the SYS:SYSTEM directory. Additionally, you must undo any changes you made to the NetWare autoexec.ncf file.
The NetWare Server Engine supports NetWare 5.1 but it does not support open files on NSS (Novell Storage Services) volumes.
The NetWare Server Engine automatically excludes the default virtual memory swap file on the SYS volume from open file operations. Any swap files on additional volumes must be excluded using the Configuration dialog from the Agent for Open Files Console. Alternatively, configure your backup product to exclude these files. If the swap file is backed up, it may cause the agent to write swap file data to its Preview Data Cache.
When running the Agent for Open Files Console on Windows 98 and Windows Me, you cannot access the Status, Logfile, or Configure dialogs for an IPX-only NetWare server, even though the agent may be indicated as active on that server. If you try to access these dialogs, you receive an Error Message stating that the agent is not available.

32.8 Known Issues for the Agent for Sybase

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

For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up.
To support pass-through authentication of account logon events for computers in a domain, the NetLogon service must be started.
The agent does not support table-level backup or restore operations.
We recommend that you avoid canceling restore jobs. If you cancel a restore job, your database is marked Do Not Recover or Suspect. If this happens, you must recreate the database before starting another restore job.
The Backup with Compare and Backup with Scan Tape options are not supported for agent sessions. Additionally, the Backup with Delete File option is not supported on agent sessions.
When Sybase Adaptive Server devices are mirrored, only the actual device information (the database on the device) is backed up; data in the mirror device is not backed up.
When you use the Client Agent with the Restore by Tree method, databases appear under the Microsoft Windows Network icon in the Restore Manager.
Alias names for Windows servers are not supported for database backup or restore operations using the Client Agent for Windows.
The agent does not support multiserver and cluster environment backup or restore operations.
The agent supports only the Restore by Tree and Restore by Session options.
For Sybase ASE 12.5, if the configuration parameter Enable xact coordination is set to On (the default setting), you cannot restore some Sybase system databases, such as sybsystemdb and the master database. To restore these system databases, disable this configuration parameter.
To restore these databases for Sybase ASE 12.5, you must reset the Sybase ASE 12.5 setting Enable xact coordination or the restore fails. To reset the Enable xact coordination parameter, perform the following steps:
1. From a DOS command prompt, start isql.
2. Enter the command:
```
1>sp_configure "enable xact coordination", 0
2>go
```
3. Restart the Sybase server.
If you restore the master database remotely and the Sybase source instance name is the same as the remote destination instance name, the job succeeds. However, when the Sybase source instance name is different from the remote destination instance name, the job fails.
When you restore the master database, the contents of the sysservers system table of the master database in the destination instance is identical to the contents of that system table in the source instance and the row that records the Sybase backup server name is incorrect. To address this issue, update the row using the following SQL statement:
```
update sysservers set srvnetname=remote destination Sybase backup server name where srvname="SYB_BACKUP"
```
Note: This name is case sensitive. You can find this name in the Windows registry.
To verify, use the following SQL statement:
```
select * from sysservers where srvname="SYB_BACKUP"
```

32.9 Known Issues for the Disaster Recovery Option

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

The option does not support local backup server recovery using file system devices located on another remote machine. In addition, support for using file system devices on local disks is very restricted. For more information, see the Disaster Recovery Option Guide.
When you run a remote recovery and the base is Windows XP with SP2, you must use different configurations depending on the version of BrightStor ARCserve Backup used to create your full backup:
- If your full backup was made using BrightStor ARCserve Backup r11.1, when you recover the machine, you must change the Share and security model for local account option in the Local security settings on the base Windows XP SP2 machine from the default setting of Guest only to Classic.
- If your full backup was made with BrightStor ARCserve Backup r11.5, on the base Windows XP SP2 machine, set the following registry key value to 0:
```
HKEY _LOCAL_MACHINE\Software\Polices\Microsoft\Windows NT\RPC\RestrictRemoteClients
```
  You do not need to change the Share and security model for local account setting.

32.10 Known Issues for the NDMP NAS Option

The following issues related to the NDMP NAS Option are known to exist in this release:

The EMC Celerra NDMP daemon has a maximum of eight (DART 5.4) concurrent connections. The NDMP NAS Option uses concurrent and persistent device connections. Each tape drive and TLU managed by the EMC data mover counts as a separate connection. Each backup, restore, or browse function also counts as a separate connection. If you exceed eight connections, you may encounter problems. We recommend that you keep this in mind when planning and implementing your storage topography.
If you have multiple NIC cards on the backup server, you cannot connect to the option. To connect to the option, you must add the loop back address for the backup server to the hosts file (the entry should be similar to the following):
```
127.0.0.1       HOSTNAME
```
Network Appliance Filers with OnTap 6.2.x and 6.3.x require a Network Appliance patch to fix a known Direct Access Restore (DAR) issue with spanned DAR recovery operations.
Sessions backed up with BrightStor Enterprise Backup 10.0 Service Pack 3 or earlier must have the following registry key set to 1 before starting a restore operation:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\NASAgent\Parameters\Use16kBlockonRestore
```
The option does not support Job failover.
You can use Direct Access Restore for files only. If you restore at least one folder, the restore operation reverts to scanning the session. This limitation does not apply to Network Appliance
Procom does not support multiple backup filters.
The Backup filter is supported at the volume and folder level.
When configuring the agent and the NAS device, you must use either an IP address or host name for both. Using a mixed configuration can result in a 3-way backup.
Dynamic Device sharing (DDS) configuration in a SAN environment with NAS is not supported on a cross-platform Windows SAN environment.
DDS configuration is supported in SAN environments with NAS on Windows SAN primary servers. This configuration is not supported on Windows SAN distributed servers.
BrightStor ARCserve Backup does not support copying NAS sessions using tapecopy.
To use DDS on EMC Celerra, you must set the NDMP.scsiReserve parameter to 0 on the data mover. This parameter is available starting with release 5.2.15.0. For more information about this issue, see EMC's Celerra documentation.
To allow BrightStor ARCserve Backup to connect to Network Appliance filers through Preferred Shares, you must create an ADMIN$ share for the volume containing the /ETC folder on the NAS server.
Note: Do not back up NAS devices through Preferred Shares, as it does not utilize the NAS-attached backup device or the NDMP protocol for proper NAS operating system backup procedures.

32.11 Known Issues for the Optical Library Option

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

Optical Library Option command line commands are not supported for the Device Manager.
The option does not support multistreaming.
If you receive the error message “Windows – No Disk, There is no disk in the drive. Please insert a disk into drive \Device\HardDiskx\DRx,” you must exclude the tapeeng.exe process from scanning by eTrust. To exclude the tapeeng.exe process from scanning, perform the following procedure:
1. In the Realtime Monitor Options dialog of eTrust, click the Filters tab.
2. On the Filters tab, in the Exclusions group box, click the Process button. The Exclude Processes dialog opens.
3. In the Exclude Processes dialog, enter tapeeng.exe in the Enter a process name field and click Add. The tapeeng.exe process appears in the List of Excluded Processes.
4. Click OK to close the Exclude Processes dialog and click OK to exit the Realtime Monitor Options dialog.

32.12 Known Issues for the SAN Option

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

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

32.13 Known Issues for the Enterprise Option for StorageTek ACSLS

The following issues relating to the Enterprise Option for StorageTek ACSLS are known to exist in this release:

If you are sharing a StorageTek ACSLS library using an AS400 system, create the following DWORD registry key and set it to 1:
```
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\TapeEngine\CONFIG\ShareWithAS400
```

32.14 Known Issues for the Enterprise Option for IBM 3494

When using the Enterprise Option for IBM 3494 with the Storage Area Network (SAN) Option, the Tape Engine on the distributed machines may fail. To prevent this failure, ensure that the most current IBM tape driver is installed on the primary and distributed machines. To do so, perform the following procedure on each machine:

Find the type of IBM drive installed:
- Ultrium (Windows 2000): ibmlto
- Magstar (Windows 2000): magstar
- Ultrium and Magstar (Windows 2003): ibmrmsst or ibmtp2k3
Find the registry key for this drive in the directory
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\type of IBM drive.
```
For example, for an Ultrium drive, find the registry key for the drive in the following directory:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmlto
```
Create the DWORD value DisableReserveUponOpen and set it to 1.
Exit regedit and restart your computer.

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

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

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

The following conditions apply if you are upgrading from BrightStor ARCserve Backup 2000 to BrightStor ARCserve Backup for Windows r11.5:
- You must upgrade the option and the base product during the same installation session.
- If the option is installed on a remote server, use the following procedure to reconfigure the option installation on the remote server:
  1. From the remote server, select Start, select Programs, Computer Associates, BrightStor ARCserve Backup Agents, and SAP R/3 Oracle Agent BACKINT Configuration.
  2. On the Security Information tab, reenter the security information for the remote server.
  3. Repeat the previous step as necessary, for all backup or restore jobs.
Because all archived redo log files must be removed after recovery is complete, all Recover Database Using Backup Control File commands must be followed by the Alter Database Open Resetlogs command.
The Backup with Compare and Backup with Scan Tape options do not apply to sessions using the Serverless Backup Option when using Oracle. These options apply to Windows only.
Before you shut down the Oracle Server in normal mode, you should shut down the local BrightStor ARCserve Backup Manager and the BrightStor ARCserve Backup Client Agent for Windows RPC Service.
When performing a remote backup from the Client Agent for Windows tree, use the Server NetBIOS name (machine name) for the agent node name. The Client Agent for Windows you to specify the Use Computer Name Resolution option or the IP address to include the databases when backing up the entire machine.
BACKINT supports only one instance at a time. If you define multiple instances, BACKINT saves only the first instance to the BACKINT registry. The Enterprise Option for SAP R/3 for Oracle Configuration utility modifies the information for this instance. For BACKINT to support other instances, change the SID value in the BACKINT registry, and rename the initSID.utl in %ORACLE_HOME%\database to your SID.
When you use BRRESTORE to restore objects to different destinations, if BrightStor ARCserve Backup is not installed on the local machine, BACKINT restores these objects to the remote server on which BrightStor ARCserve Backup is located.
When you use the Client Agent for Windows with the Restore by Tree method for your restore operation, databases appear under the Microsoft Windows Network icon in the Restore Manager.
For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up.
The NetLogon service must be started to support pass-through authentication of account logon events for computers in a domain.
The option only supports the BACKINT command interface.

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

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

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

32.17 Known Issues for BrightStor Portal Integration

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

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

32.18 Known Issues for Documentation

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

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

33.0 Documentation Changes for BrightStor ARCserve Backup r11.5

Changes that had been listed in this section for the release of BrightStor ARCserve Backup for Windows r11.5 have been merged into the documentation released with BrightStor ARCserve Backup for Windows r11.5 SP1.

34.0 International Support

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.

In addition to the English release of this product, CA supports only those languages listed in the following table.

Language Internationalized Translated

Brazilian-Portuguese Yes Yes

Chinese (Simplified) Yes Yes

Chinese (Traditional) Yes Yes

French Yes Yes

German Yes Yes

Italian Yes Yes

Japanese Yes Yes

Korean Yes Yes

Spanish Yes Yes

Language	Internationalized	Translated
Brazilian-Portuguese	Yes	Yes
Chinese (Simplified)	Yes	Yes
Chinese (Traditional)	Yes	Yes
French	Yes	Yes
German	Yes	Yes
Italian	Yes	Yes
Japanese	Yes	Yes
Korean	Yes	Yes
Spanish	Yes	Yes

Note: If you run the product in a language environment not listed in the table, you may experience problems.

35.0 Documentation

Updated guides for this product are available at http://ca.com/support.

The PDF guides for this product are as follows:

BrightStor ARCserve Backup for Windows Release Summary D011672E.PDF
BrightStor ARCserve Backup for Windows Getting Started D011682E.PDF
BrightStor ARCserve Backup for Windows Administrator Guide D011692E.PDF
BrightStor ARCserve Backup Client Agents Guide D011652E.PDF
BrightStor ARCserve Backup for Windows Agent for IBM Informix Guide D011702E.PDF
BrightStor ARCserve Backup for Windows Agent for Lotus Domino Guide D011712E.PDF
BrightStor ARCserve Backup for Windows Agent for Microsoft Exchange Guide D011723E.PDF
BrightStor ARCserve Backup for Windows Agent for Microsoft SharePoint Guide D011842E.PDF
BrightStor ARCserve Backup for Windows Agent for Microsoft SQL Server Guide D011732E.PDF
BrightStor ARCserve Backup for Windows Agent for Open Files Guide D011742E.PDF
BrightStor ARCserve Backup for Windows Agent for Oracle Guide D011752E.PDF
BrightStor ARCserve Backup for Windows Agent for Sybase Guide D011762E.PDF
BrightStor ARCserve Backup for Windows Disaster Recovery Option Guide D011782E.PDF
BrightStor ARCserve Backup for Windows Image Option Guide D011792E.PDF
BrightStor ARCserve Backup for Windows NDMP NAS Option Guide D011802E.PDF
BrightStor ARCserve Backup for Windows Tape and Optical Library Option Guide D011812E.PDF
BrightStor ARCserve Backup for Windows Serverless Backup Option Guide D011822E.PDF
BrightStor ARCserve Backup for Windows Tape RAID Option Guide D011832E.PDF
BrightStor ARCserve Backup Storage Area Network (SAN) Option Guide D011662E.PDF
BrightStor ARCserve Backup for Windows Enterprise Option for StorageTek ACSLS Guide D011852E.PDF
BrightStor ARCserve Backup for Windows Enterprise Option for IBM 3494 Guide D011862E.PDF
BrightStor ARCserve Backup for Windows Enterprise Option for SAP R/3 for Oracle Guide D011872E.PDF
BrightStor ARCserve Backup for Windows Enterprise Option for Advantage™ Ingres® Guide D011882E.PDF
BrightStor ARCserve Backup for Windows Enterprise Option for Microsoft SQL Using HDS Snap-Shot Guide D011892E.PDF
BrightStor ARCserve Backup for Windows Enterprise Option for Microsoft SQL Using HP-XP Snap-Shot Guide D011902E.PDF
BrightStor ARCserve Backup for Windows Microsoft Volume Shadow Copy Service Guide D011912E.PDF
BrightStor ARCserve Backup for Windows Agent for Microsoft Data Protection Manager Guide D012391E.PDF
BrightStor ARCserve Backup for Windows CA XOsoft WANSync Integration Guide D012451E.PDF

36.0 Contact Technical Support

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