CA

CA ARCserve® Backup r12 SP1 Readme


1.0 Welcome

2.0 Operating System Support

3.0 System Requirements
3.1 System Requirements for the CA ARCserve Backup Base Product
3.2 System Requirements for CA ARCserve Backup and CA XOsoft Integration
3.3 System Requirements for the CA ARCserve Backup Client Agents
3.4 System Requirements for the Agent for IBM Informix
3.5 System Requirements for the Agent for Lotus Domino
3.6 System Requirements for the Agent for Microsoft Exchange
3.7 System Requirements for the Agent for Microsoft SharePoint
3.8 System Requirements for the Agent for Microsoft SQL Server
3.9 System Requirements for the Agent for Oracle (UNIX/Linux)
3.10 System Requirements for the Agent for Oracle (Windows)
3.11 System Requirements for the Agent for Open Files
3.12 System Requirements for the Agent for Microsoft Data Protection Manager
3.13 System Requirements for the Agent for VMware
3.14 System Requirements for the Agent for Sybase
3.15 System Requirements for the Content Management Option
3.16 System Requirements for the Disaster Recovery Option
3.17 System Requirements for the Enterprise Module
3.18 System Requirements for the Disk to Disk to Tape Option
3.19 System Requirements for the Enterprise Option for IBM 3494
3.20 System Requirements for the Enterprise Option for SAP R/3 for Oracle
3.21 System Requirements for the Enterprise Option for StorageTek ACSLS
3.22 System Requirements for the Image Option
3.23 System Requirements for the NDMP NAS Option
3.24 System Requirements for the Tape Library Option
3.25 System Requirements for the Serverless Backup Option
3.26 System Requirements for the Storage Area Network (SAN) Option
3.27 System Requirements for the CA ARCserve Backup Small Business Server Editions
3.28 System Requirements for the CA ARCserve Backup for Microsoft Windows Essential Business Server

4.0 Installation Considerations
4.1 Installation Considerations for the CA ARCserve Backup Base Product
4.2 Upgrade Considerations for the CA ARCserve Backup Base Product
4.3 Installation Considerations for the Client Agents
4.4 Installation Considerations for the Agent for Microsoft Exchange
4.5 Installation Considerations for the Agent for Microsoft SharePoint 2003
4.6 Installation Considerations for the Agent for Microsoft SharePoint 2007
4.7 Installation Considerations for the Agent for Microsoft SQL Server
4.8 Installation Considerations for the Agent for Open Files
4.9 Installation Considerations for the Enterprise Module
4.10 Installation Considerations for the Media Management Option (MMO)
4.11 Installation Considerations for CA ARCserve Backup for Microsoft Windows Essential Business Server

5.0 General Considerations

6.0 Supported Upgrade Paths
6.1 Backward Compatibility

7.0 Known Issues
7.1 Known Issues for the Base Product
7.2 Known Issues When Upgrading to CA ARCserve Backup
7.3 Known Issues for Integration
7.4 Known Issues for the Client Agents
7.5 Known Issues for the Agent for IBM Informix
7.6 Known Issues for the Agent for Microsoft Data Protection Manager
7.7 Known Issues for the Agent for Microsoft Exchange
7.8 Known Issues for the Agent for Microsoft SharePoint
7.9 Known Issues for the Agent for Microsoft SQL Server
7.10 Known Issues for the Agent for Open Files
7.11 Known Issues for the Agent for Oracle (Windows)
7.12 Known Issues for the Agent for Oracle (UNIX and Linux [RMAN])
7.13 Known Issues for the Agent for Sybase
7.14 Known Issues for the Agent for VMware
7.15 Known Issues for the Disaster Recovery Option
7.16 Known Issues for the Image Option
7.17 Known Issues for the NDMP NAS Option
7.18 Known Issues for the Tape Library Option
7.19 Known Issues for the Storage Area Network (SAN) Option
7.20 Known Issues for the Enterprise Option for AS400
7.21 Known Issues for the Enterprise Option for IBM 3494
7.22 Known Issues for the Agent for Lotus Domino
7.23 Known Issues for the Enterprise Option for SAP R/3 Oracle
7.24 Known Issues for the Enterprise Option for StorageTek ACSLS
7.25 Known Issues for Displaying Non-English Characters
7.26 Known Issues for CA ARCserve Backup for Microsoft Windows Essential Business Server
7.27 Known Issues for CA ARCserve Backup Licensing
7.28 Known Issues for Documentation
7.29 Portmapper Conflicts with CA ARCserve Backup

8.0 Included Fixes

9.0 Security Related Enhancements

10.0 Language Certifications

11.0 Contact Technical Support


1.0 Welcome

Welcome to the CA ARCserve Backup Readme. This readme contains issues and other information discovered after publication. For a complete list of the known issues for this release and details about how the features and enhancements for this release might affect you, see the CA ARCserve Backup Release Summary.

CA ARCserve Backup supports the following suites:


2.0 Operating System Support

CA ARCserve Backup is supported on the following operating systems:

Windows Server 2008

Note: CD installation of CA ARCserve Backup is not supported on Windows 2008 Core systems. Only DVD installation is supported.

Windows Server 2003

Windows 2000

Windows XP

Windows Vista (x86 and x64)

Windows Essential Business Server Operating System Support

Support for Guest OS for Virtualization Software

Guest OS Support

Supported CA ARCserve Backup Components


3.0 System Requirements

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

3.1 System Requirements for the CA ARCserve Backup Base Product

The minimum system requirements for CA ARCserve Backup are:

CA ARCserve Backup Database

CA ARCserve Backup supports the following applications to host the CA ARCserve Backup database:

Note: Microsoft SQL Server 2005 Express 2005 Edition Service Pack 2 is included on the CA ARCserve Backup installation media.

Note: In addition to these requirements, you should consider the disk space necessary for the default CA ARCserve Backup database. Depending upon usage, the database can grow to several GB in size.

Other Hardware

Internet Browser

Adobe Reader

3.2 System Requirements for CA ARCserve Backup and CA XOsoft Integration

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

To integrate CA ARCserve Backup with CA XOsoft, you must be running CA XOsoft, version 4.0, starting with Build 69.

The Master servers are supported on the following operating systems:

The Replica servers are supported on the following operating systems:

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

For more information about integration, refer to the CA ARCserve Backup for Windows CA XOsoft Integration Guide.

Note: CA XOsoft does not support Microsoft Windows Server 2008.

3.3 System Requirements for the CA ARCserve Backup Client Agents

The following sections provide hardware and software requirements for CA ARCserve Backup Client Agents.

Note: Refer to the appropriate Agent section for additional requirements, if any.

Hardware Requirements

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

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

Software Requirements

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

3.4 System Requirements for the Agent for IBM Informix

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

The CA ARCserve Backup Agent for IBM Informix also requires the following:

3.5 System Requirements for the Agent for Lotus Domino

Hardware Requirements

The CA ARCserve Backup Agent for Lotus Domino supports the following:

Note: The Agent for Lotus/Domino supports only 32-bit Windows systems

3.6 System Requirements for the Agent for Microsoft Exchange

Note: The Agent now installs the Exchange Database Level Agent with the Exchange Document Level Agent.

Hardware Requirements

To install the Agent for Microsoft Exchange, the following hardware must be available and configured according to the version of Microsoft Exchange you are running:

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

Additional Software Requirements for the Agent for Microsoft Exchange

3.7 System Requirements for the Agent for Microsoft SharePoint

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

The CA ARCserve Backup Agent for Microsoft Office SharePoint supports the following:

The agent does not require the CA ARCserve Backup server component.

Notes:

If running Microsoft Office SharePoint Server 2007 with SQL Server as database server, apply SP2 to SQL Server.

If running Microsoft Office SharePoint Server 2007 with SQL Server Express as database server, apply SP2 to SQL Server Express.

3.8 System Requirements for the Agent for Microsoft SQL Server

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

The CA ARCserve Backup Agent for Microsoft SQL Server requires one of the following versions of Microsoft SQL Server:

Microsoft SQL Server 2005 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 2005 Service Pack 1 and Service Pack 2 on the following operating systems:

Microsoft SQL Server 7.0 Support

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

Microsoft SQL Server 2000 Support

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

Microsoft SQL Server 2008 Support

The Agent for Microsoft SQL Server supports Microsoft SQL Server 2008 on the following operating systems:

Support for 64-bit Systems

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

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:

3.9 System Requirements for the Agent for Oracle (UNIX/Linux)

The following section provides the system requirements for the CA ARCserve Backup Agent for Oracle (UNIX/Linux):

Hardware Requirements

To install the Agent for Oracle, the following hardware must be available and configured according to the version of Oracle Database you are running:

Additional Hardware Requirements

3.10 System Requirements for the Agent for Oracle (Windows)

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

Hardware Requirements

To install the Agent for Oracle, the following hardware must be available and configured according to the version of Oracle Database you are running:

Additional Software Requirements for the Agent for Oracle

3.11 System Requirements for the Agent for Open Files

Hardware Requirements

In addition to the Minimum Requirements previously listed, you should have at least 1.5 MB of disk space available for this agent.

Additional Software Requirements

The Agent for Open Files requires one of the following operating systems:

The following is also required:

Note: The agent does not support the Microsoft NetWare Client.

Agent for Microsoft Volume Shadow Copy Service (VSS)

The CA ARCserve Backup Agent for Open Files now includes functionality for the CA ARCserve Backup Agent for Microsoft Volume Shadow Copy Service (VSS).

Note: The Agent for Microsoft VSS can perform a full backup of Microsoft SQL Server 2005 databases, but cannot perform differential or incremental backups.

3.12 System Requirements for the Agent for Microsoft Data Protection Manager

Hardware Requirements

3.13 System Requirements for the Agent for VMware

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Note: When the Agent for VMware is installed on the same server as the base product, the agent requires the same hardware specified for the base product. When the Agent for VMware is installed on a remote node, the agent requires the same hardware specified for the Client Agent for Windows.

Additional Software Requirements

The CA ARCserve Backup Agent for VMware supports the following:

3.14 System Requirements for the Agent for Sybase

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

The CA ARCserve Backup Agent for Sybase requires Sybase Adaptive Server 12.0, 12.5, or 15.0.

The Agent for Sybase supports Windows as the host server platform.

3.15 System Requirements for the Content Management Option

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

3.16 System Requirements for the Disaster Recovery Option

Hardware Requirements

In addition to the Minimum Requirements previously listed, you should have at least 70 MB of disk space available for the Disaster Recovery Option.

Additional Software Requirements

The CA ARCserve Backup Disaster Recovery Option supports several methods of disaster recovery, depending on operating system.

Note: Use of a Japanese USB keyboard during bootable floppy disaster recovery is not supported on Windows 2000.

Note: Bootable tape disaster recovery from a USB tape drive is not supported on Windows 2000.

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

Note: The bootable CD method to protect local and remote 64-bit systems is supported on the following platforms:

The bootable CD is a CD containing OS, CA ARCserve Backup, Machine Specific Disk, Drivers for NIC and Mass Storage (SCSI/Fibre/RAID). For Windows 2008 systems only, the creation of a unified CD is not supported. Machine Specific Data may reside on a USB drive.

Create a Machine Specific Disk that contains network drivers if you need to perform Disaster Recovery remotely, on a member server of a SAN, or from a remote File System Device because you will likely face network connection problems at the time of a disaster recovery. You may re-create a Machine Specific Disk using the Disaster Recovery Create Boot Kit Wizard, if you realize later that you do not have network drivers. The procedure is the same as for initial creation.

3.17 System Requirements for the Enterprise Module

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

The Enterprise Module is a prerequisite component for the following options:

Note: In addition to the above options, the Enterprise Module must be installed to access CA ARCserve Backup advanced features and enhanced functionality. For more information, see the Administration Guide.

Software Requirements

The minimum operating system requirements for the Enterprise Module are:

3.18 System Requirements for the Disk to Disk to Tape Option

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

CA ARCserve Backup must be installed before you install the CA ARCserve Backup Disk to Disk to Tape Option.

Disk to Disk to Tape Option supports the following operating systems:

3.19 System Requirements for the Enterprise Option for IBM 3494

The Enterprise Option for IBM 3494 is now supported by the Enterprise Module.

3.20 System Requirements for the Enterprise Option for SAP R/3 for Oracle

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

The CA ARCserve Backup Enterprise Option for SAP R/3 for Oracle supports the following:

Notes:

3.21 System Requirements for the Enterprise Option for StorageTek ACSLS

The Enterprise Option for StorageTek ACSLS is now supported by the Enterprise Module.

3.22 System Requirements for the Image Option

Image Option support is now supported by the Enterprise Module.

3.23 System Requirements for the NDMP NAS Option

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

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

3.24 System Requirements for the Tape Library Option

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

CA ARCserve Backup for Windows must be installed before you install the CA ARCserve Backup Tape Library Option:

The minimum operating system requirements for the Tape Library Option are:

Note: The following capabilities have been incorporated into the Tape Library Option:

3.25 System Requirements for the Serverless Backup Option

Serverless Backup is now supported by the Enterprise Module.

3.26 System Requirements for the Storage Area Network (SAN) Option

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

Additional Software Requirements

The CA ARCserve Backup Storage Area Network (SAN) Option may be installed on the following operating systems:

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

3.27 System Requirements for the CA ARCserve Backup Small Business Server Editions

Hardware Requirements

The following agents/options are included in the CA ARCserve Backup Small Business Server Standard Edition:

The following agents/options are included in the CA ARCserve Backup Small Business Server Premium Edition:

3.28 System Requirements for the CA ARCserve Backup for Microsoft Windows Essential Business Server

Hardware Requirements

To run CA ARCserve Backup for Microsoft Windows Essential Business Server, your system must meet the same requirements Microsoft sets for running Windows EBS.

Software Requirements

To access CA ARCserve Backup Backup for Microsoft Windows EBS, you must meet the following prerequisites:


4.0 Installation Considerations

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

4.1 Installation Considerations for the CA ARCserve Backup Base Product

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

http://supportconnectw.ca.com/premium/antivirus/downloads/nt/4.5/ildrvupdate.asp

1.    Open Control Panel, Administrative Tools, Local Security Policy, Local Policies, Security Options.

2.    Select Network access: Sharing and security model for local accounts.

3.    Change setting to Classic - local users authenticate as themselves.

4.    Click OK.

0.    Create a key called MessageEngine under:

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

1.    Create a DWORD valued called Impersonate under:

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Admin\MessageEngine

2.    Set Impersonate to 0.

3.    Reboot the Windows system.

4.2 Upgrade Considerations for the CA ARCserve Backup Base Product

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

The Server Configuration Wizard lets you change the role of the server after you complete the upgrade process. Optionally, you can uninstall and then reinstall CA ARCserve Backup. However, to ensure that you do not lose records of your backup and restore data, you must not overwrite the CA ARCserve Backup database instance that is detected by the Installation Wizard.

§   
§  C:\Program Files\CA\SharedComponents\Jre

If there are no other applications on your computer using these files, you can safely delete them.

Note: For more information, see Uninstall CA ARCserve Backup in the Implementation Guide.

Note: For more information, see Configure Devices using Enterprise Module Configuration in the Administration Guide.

4.3 Installation Considerations for the Client Agents

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

Agent for NetWare

Note: Version 9 of the CA ARCserve Backup Agent for NetWare is no longer supported and requires an upgrade to a current version. There is no backwards compatibility with this release of CA ARCserve Backup.

Agent for Oracle UNIX/Linux (RMAN)

Agent for Windows

Before you begin, determine whether the Vista machine is part of a domain or part of a workgroup. Use a Domain Administrative account if the target computer is part of a domain. Grant a domain account with administrator privileges on the Vista machine and use that domain account to log on. You may then remotely install the Client Agent on the Vista machine.

If the target computer is part of a workgroup, disable the client computer's local account filtering policy by creating a new registry key, as follows:

DWORD value: LocalAccountTokenFilterPolicy

Location: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\

New Value: 1

After installation, set the LocalAccountTokenFilterPolicy setting to 0 to re-enable local account filtering.

Virtual Machines

If you wish to back up and restore VM data:

Install the Client Agent on each VM. Individual file backup and restore is not supported when the Client Agent is installed on the Host OS.

Install the Agent for Open Files, Client Agent (Windows, Linux), SQL, Exchange or SharePoint on each VM.

4.4 Installation Considerations for the Agent for Microsoft Exchange

The following section provides information to consider when installing the Agent for Microsoft Exchange.

To activate the Document Level Agent, perform the following:

1.    Obtain Microsoft Messaging API and Collaboration Data Objects 1.2.1 from the Microsoft website and install it.

2.    Run <Exchange agent home directory>\DocumentLevel\ExchDocWrapper.exe -regServer to register the Document Level Agent.

3.    Restart the CA ARCserve Universal Agent service.

4.5 Installation Considerations for the Agent for Microsoft SharePoint 2003

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

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.    Ensure that the firewalls on any remote computers hosting the SharePoint installation are configured to allow exceptions.

2.    Install the Agent for Microsoft SharePoint from the CA ARCserve Backup installation media. The Agent for Microsoft SharePoint Configuration wizard starts automatically.

3.    Complete the Server Selection information and click Next. Although the SharePoint Router Agent is installed, you may 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.

4.    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\ARCserve Backup\UniAgent

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

6.    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 Windows Firewall exception list on those machines.

7.    If you have the CA ARCserve Backup External Data Agent installed on any computers, add the UnivAgent.exe executable to the Windows exception list. This executable is found in the following directory:

c:\Program Files\CA\SharedComponents\ARCserve Backup\UniAgent

8.    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\ARCserve Backup\DBACommon

The Agent for Microsoft SharePoint can now be used successfully from the CA ARCserve Backup server.

4.6 Installation Considerations for the Agent for Microsoft SharePoint 2007

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

4.7 Installation Considerations for the Agent for Microsoft SQL Server

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

Note: Windows Small Business Server 2003 Premium Edition includes Microsoft SQL Server 2000, Service Pack 3.

4.8 Installation Considerations for the Agent for Open Files

The following section provides information to consider when installing the Agent for Open Files on Vista machines.

You can remotely install the Agent for Open Files on Vista machines, but may need to disable local account filtering first. User Account Control (UAC) is a Vista feature that blocks local administrative accounts from remotely accessing administrative shares (C$, Admin$).

Before you begin, determine whether the Vista machine is part of a domain or part of a workgroup. Use a Domain Administrative account if the target computer is part of a domain. Grant a domain account with administrator privileges on the Vista machine and use that domain account to log on. You may then remotely install the Agent for Open Files on the Vista machine.

If the target computer is part of a workgroup, disable the client computer's local account filtering policy by creating a new registry key, as follows:

DWORD value: LocalAccountTokenFilterPolicy

Location: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\

New Value: 1

After installation, set the LocalAccountTokenFilterPolicy setting to 0 to re-enable local account filtering.

4.9 Installation Considerations for the Enterprise Module

Hardware Requirements

No additional hardware is required beyond the Minimum Requirements previously listed.

The Enterprise Module is a prerequisite component for the following options:

Note: In addition to the above options, the Enterprise Module must be installed to access CA ARCserve Backup advanced features and enhanced functionality. For more information, see the Administration Guide.

Software Requirements

The minimum operating system requirements for the Enterprise Module are:

4.10 Installation Considerations for the Media Management Option (MMO)

The Enterprise Module is a prerequisite component for the Media Management Option (MMO) and you must install it in order to use the MMO option.

4.11 Installation Considerations for CA ARCserve Backup for Microsoft Windows Essential Business Server

This release of CA ARCserve Backup lets you integrate Microsoft Windows Essential Business Server 2008, English - Release Candidate 1, with CA ARCserve Backup. For information about Windows Essential Business Server 2008 configurations and how you can use CA ARCserve Backup to protect Windows Essential Business Server 2008 implementations, see the appendix "Using CA ARCserve Backup for Microsoft Windows Essential Business Server" in the CA ARCserve Backup for Windows Administration Guide.

This following list provides information about installation prerequisites to consider before installing CA ARCserve Backup for Microsoft Windows Essential Business Server 2008:

To modify the Forefront TMG firewall policy, perform the following procedure to create a new access rule that enables port 6050:

1.    From the Windows Start menu, choose Programs, Microsoft Forefront TMG, Forefront TMG Management.

Forefront TMG opens.

2.    In the Threat Management Gateway list, right-click Firewall Policy and choose New, Access Rule from the shortcut menu.

3.    Follow the prompts on the wizard screen to create a new access rule with a rule action of 'Allow'.

a.    Create two new protocols, one that allows for TCP incoming, UDP send, and UDP send receive for port 6050.

b.    Add another protocol for TCP outgoing, UDP receive, and UDP receive send for port 6050.

c.    Add the new protocols to the access rule you are creating.

d.    Complete the remaining wizard steps as required. Ensure the sources and destinations include All Networks.

4.    Apply the new rule.

5.    In the Threat Management Gateway list, click Monitoring.

6.    Click the Configuration tab and ensure the status for the new rule is synched.

Note: For more information, see your Microsoft Windows Essential Business Server 2008 documentation, the Microsoft website, and the Microsoft Windows Essential Business Server Overview in the CA ARCserve Backup for Microsoft Windows Essential Business Server online help.


5.0 General Considerations

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

1.    Open the ASDBBackups.txt file with Word 2003 or later version.

2.    In the file conversion dialog, select other encoding and UNICODE in the list box, and click OK.

The following section provides general information to consider when using CA ARCserve Backup for Microsoft Windows EBS:

Note: For more information about how to add a new CA ARCserve Backup user using the User Profile utility of CA ARCserve Backup, see the CA ARCserve Backup online help.

Note: The caroot user profile controls access only to the CA ARCserve Backup Manager and backup-related functions, and should not be confused with the user credentials required to log in to the Microsoft Windows operating system. For more information regarding this user profile, see the CA ARCserve Backup Administration Guide.

Important! You should not leave the password blank for caroot.


6.0 Supported Upgrade Paths

You can upgrade to this release of CA ARCserve Backup from the following products:

Note: CA ARCserve Backup does not support upgrading BrightStor ARCserve Backup for Windows r11.1 in a cluster-aware environment to this release. You must uninstall BrightStor ARCserve Backup for Windows r11.1 and then install this release into a cluster-aware environment.

For all other releases, you must uninstall the existing software version before you install CA ARCserve Backup.

6.1 Backward Compatibility

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

You must retain the previous BrightStor ARCserve Backup Manager to view and manage ARCserve servers that are running the following releases:

This release of CA ARCserve Backup Manager can view and manage r12 CA ARCserve Backup Servers.


7.0 Known Issues

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

7.1 Known Issues for the Base Product

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

1.    On the agent machine, restart the discovery service.

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.

If you are running the CA ARCserve Backup Manager Console on a 64-bit system, you must disable RSM so that CA ARCserve Backup can use the device. To disable RSM, perform one of the following:

0.    Confirm that the remote machine is reachable across the network and that the IP Address matches the remote machine name. Run the following commands to confirm:

·         ping <MachineName>

·         ping <IPAddress>

·         ping –a <IPAddress>

If the remote system can be pinged and the name matches the IP address, the Diagnostic Wizard should experience no problems. If the system cannot be pinged at all, check the network connections and ensure the system is operational. If the name does not match the IP address, continue.

1.    Open a command prompt and run ipconfig /all to show the current IP configurations and other network configurations of a machine. Examine the command output for mistakes in your configurations. If mistakes exist, the network cannot communicate properly.

 .     Open Network Connections.

a.    Double-click <Connection Name>.

b.    Click the Support tab.

c.    Click Details.

d.    Note the values for "WINS Servers". The WINS Servers provide the NetBIOS name resolution for your remote servers.

e.    Ping the WINS servers using the commands in Step 1.

2.    Run the following command to check the NetBIOS Remote Cache Name Table:

nbtstat -c

Using NetBIOS over TCP/IP, this command lists the cache of remote machine names and their IP addresses, and outputs statistics into four columns: Name, Type, Host Address and Life (sec). Examine the output and ensure the remote machine IP address matches its machine name for all types of the machine name specified.

If the machine name matches the IP address for all types, the remote system can be accessed by its NetBIOS name.

If the machine name does not match the IP address, or if no such items exist in the table, proceed to Step 4.

3.    (Optional) If you find a mismatch in the mapping between a System Name and IP Address, run the following command to purge the Server Name and IP address mapping on both the local and remote machines. Otherwise, skip to Step 5.

ipconfig /flushdsn

4.    Purge and reload the NetBIOS Remote Cache Name Table:

nbtstat -R

5.    Run nbtstat -c again. The table should now be empty, or contain only a few new items with lives of about 600 seconds.

6.    Check the NetBIOS Remote Machine Name Table:

nbtstat -a <RemoteName>

This command lists a remote machine name table, given the machine name you specify.

nbtstat -A <IPAddress>

This command lists a remote machine name table, given the IP address you specify.

The tables should show identical information: the name of the remote system as "Registered" for the IP Address.

If the steps above do not solve your NetBIOS communication problem, you must contact your WINS server administrator to reconfigure the system.

Key: DeleteDirInMigration

Location: Client\Agent Parameters

Value: 0 to retain directory folders, 1 to delete them.

To remedy this problem, do the following:

1.    After you restore the ARCserve database, use the Merge utility to merge the ARCserve database backup sessions.

2.    Close and then reopen the Restore Manager window to refresh the information that displays in the Restore by Tree source directory tree.

You should skip these files when restoring the database.

If you do not want the destination tape to be the exact same as the source tape, you can include the –idr switch with the tapecopy command so that CA ARCserve Backup automatically assigns a different random ID to the destination tape and ensures that the destination tape is not exactly the same as the source tape.

W5110 The Database is no longer available

During recovery, the CA ARCserve Backup database is offline. So any client programs trying to access the database during this period will be denied. This message does not prevent recovery from completing successfully.

Note: If you select only the \SIS Common Store to back up, excluded files are not backed up, as expected.

To eliminate Warning 3, perform the following steps:

3.    Click Start, Control Panel, Administrative Tools, Services.

4.    From the list of services, double-click SQL Server Browser service to open its properties.

5.    Change the startup type to Disabled.

6.    Click OK. Rebooting should now proceed without this warning.

These errors are related to the sequence in which CA ARCserve Backup and SQL Server services are started and can be eliminated if you adjust the following CA ARCserve Backup services that depend on SQL Service to start:

Note: If SQL Server is installed on a remote machine, rebooting CA ARCserve Backup does not affect it.

To adjust CA ARCserve Backup services

1.    Determine SQL Server service name.

Find the following registry key:

 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLXXXX, where XXXX is the unique name of the SQL Server and MSSQLXXXX is the SQL Server Service name.

2.    Set CA ARCserve Backup services to depend on SQL Server service to start up by using the Microsoft sc utility (see Using Utility steps a through c, below) or by manually setting the registry keys (see Manually editing the registry, below).

Using the Utility:

a.    Install the Windows support tool, "SUPTOOLS.MSI" from your Windows installation CD. Go to the <CD-ROOT>\SUPPORT\TOOLS\ directory.

b.    Run the Command Prompt: Start, All Programs, Windows Support Tools, Command Prompt.

c.    Type the following in the open Command Prompt window:

sc config CASDBEngine depend= MSSQLXXXX

sc config CASUniversalAgent depend= MSSQLXXXX

sc config CASTapeEngine depend= MSSQLXXXX

d.    Go to step 3.

Manually editing the registry:

Create a Multi-String value named "DependOnService" under each of the following keys and set its value to your SQL service name (see step 1).

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASDBEngine

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASMgmtSvc

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASUniversalAgent

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASTapeEngine

3.    Reboot the computer. The errors should not reappear.

7.2 Known Issues When Upgrading to CA ARCserve Backup

1.    In the Database Manager, expand the media Records. The tape name appears at least twice, once in uppercase letters and once in lowercase letters.

2.    Delete the uppercase entry. The Restore Manager displays the tape name and details correctly.

Use SkipDSAFiles

Set the SkipDSAFiles registry key to 0 to include these files and 1 to skip them.

Value Name: SkipDSAFiles

Type: DWORD

Value: 0 to back up and 1 to skip

HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCserve Backup\Base\Task\Backup

HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCserve Backup\ClientAgent\Parameters

Agent for Oracle, Agent for SAP R/3

Agent for Domino

Agent for Sybase

Agent for Informix

Use BackupDBFiles

Set the BackupDBFiles registry key to 0 to skip these files and 1 to include them:

Value Name: BackupDBFiles

Type: DWORD

Value: 0 to skip and 1 to back up (1 is default)

HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCserve Backup\Base\Task\Backup

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserveBackup\ClientAgent\Parameters

Agent for Microsoft SQL

The list of data and transaction log files that are part of online databases is retrieved from Microsoft SQL Server at the start of a file backup. This list typically includes, but not exclusively:

Except distmdl.mdf, distmdl.ldf, mssqlsystemresource.mdf, mssqlsystemresource.ldf, which cannot be skipped. Also, if a SQL Server instance is shut down, the database files will not be skipped.

Exchange Database Level Agent/Exchange Document Level Agent

Note: The Exchange Brick Level Agent is no longer supported, but in r11.5 used the SkipDSAFiles registry key.

To specify SQL Server collation settings, do the following:

1.    Upgrade to CA ARCserve Backup for Windows r12, Service Pack 1.

After the upgrade process is complete, from the Windows Start menu, select All Programs, CA, ARCserve Backup, and click Server Configuration Wizard.

The Server Configuration Wizard opens.

2.    Click Select Database and click Next

3.    Follow the prompts and complete the required fields on the Check Caroot, System Account, and Select Database dialogs.

Important! On the Select Database dialog, you must specify the type of database (Microsoft SQL Server or Microsoft SQL Server Express 2005 Edition) that is currently installed in your CA ARCserve Backup environment and then click Next.

4.    Do one of the following:

·         Microsoft SQL Server 2005 Express Edition database--Clear the check mark from Overwrite the existing ARCSERVE_DB instance on the SQL Server Express Instance dialog.

·         Microsoft SQL Server database--Complete the required fields on the SQL Database System Account dialog and click Next. Clear the check mark from Overwrite DB option on the Select database installation path dialog.

5.    Click Language Support Options.

The Collation Settings dialog opens.

6.    Click East Asian collation, specify the required language from the drop-down list, and then click OK.

The Collation Settings dialog closes.

7.    Click Next.

Follow the prompts and complete the required fields on the subsequent dialogs to complete the configuration.

7.3 Known Issues for Integration

The following issues relating to CA Desktop Management Suite Backup and CA ARCserve Backup integration are known to exist in this release:

7.4 Known Issues for the Client Agents

The following issues relating to the Client Agents are known to exist in this release:

7.5 Known Issues for the Agent for IBM Informix

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

Note: For more information about the dbacfg utility, see the Agent for IBM Informix Guide.

Warning: Encryption will be skipped for Informix backups