Windows Server 2003 is the follow-up to Windows 2000 Server, incorporating compatibility and other features from Windows XP. Unlike Windows 2000, Windows Server 2003's default installation has none of the server components enabled, to reduce the attack surface of new machines. Windows Server 2003 includes compatibility modes to allow older applications to run with greater stability. It was made more compatible with Windows NT 4.0 domain-based networking. Windows Server 2003 brought in enhanced Active Directory compatibility and better deployment support to ease the transition from Windows NT 4.0 to Windows Server 2003 and Windows XP Professional.[22]
download windows server 2003 enterprise edition sp2 37
Windows Server 2003 comes in a number of editions, each targeted towards a particular size and type of business.[36][37] In general, all variants of Windows Server 2003 have the ability to share files and printers, act as an application server, host message queues, provide email services, authenticate users, act as an X.509 certificate server, provide LDAP directory services, serve streaming media, and to perform other server-oriented functions.[38][39][40][41]
Windows Server 2003 Web is meant for building and hosting Web applications, Web pages, and XML web services. It is designed to be used primarily as an IIS web server[43] and provides a platform for developing and deploying XML Web services and applications that use ASP.NET technology. Domain controller and Terminal Services functionality are not included on Web Edition. However, Remote Desktop for Administration is available. Only 10 concurrent file-sharing connections are allowed at any moment.[citation needed] It is not possible to install Microsoft SQL Server and Microsoft Exchange software in this edition without installing Service Pack 1[citation needed]. Despite supporting XML Web services and ASP.NET, UDDI cannot be deployed on Windows Server 2003 Web[citation needed]. The .NET Framework version 2.0 is not included with Windows Server 2003 Web, but can be installed as a separate update from Windows Update.[citation needed]
Windows Server 2003 Web supports a maximum of 2 physical processors and a maximum of 2 GB of RAM.[42] It is the only edition of Windows Server 2003 that does not require any client access license (CAL) when used as the internet facing server front-end for Internet Information Services and Windows Server Update Services. When using it for storage or as a back-end with another remote server as the front-end, CALs may still be required.[43][clarification needed]
Windows Server 2003 Enterprise is aimed towards medium to large businesses. It is a full-function server operating system that supports up to 8 physical processors and provides enterprise-class features such as eight-node clustering using Microsoft Cluster Server (MSCS) software and support for up to 64 GB of RAM through PAE.[42] Enterprise Edition also comes in specialized variants for the x64 and Itanium architectures. With Service Pack 2 installed, the x64 and Itanium variants are capable of addressing up to 1 TB and 2 TB of RAM,[42] respectively. This edition also supports Non-Uniform Memory Access (NUMA). It also provides the ability to hot-add supported hardware. Windows Server 2003 Enterprise is also the required edition to issue custom certificate templates.[citation needed]
Windows Storage Server 2003, a part of the Windows Server 2003 series, is a specialized server operating system for network-attached storage (NAS).[49] Launched in 2003 at Storage Decisions in Chicago, it is optimized for use in file and print sharing and also in storage area network (SAN) scenarios. It is only available through Original equipment manufacturers (OEMs).[50] Unlike other Windows Server 2003 editions that provide file and printer sharing functionality, Windows Storage Server 2003 does not require any CAL.[51]
Windows Storage Server 2003 NAS equipment can be headless, which means that they are without any monitors, keyboards or mice, and are administered remotely.[52] Such devices are plugged into any existing IP network and the storage capacity is available to all users. Windows Storage Server 2003 can use RAID arrays to provide data redundancy, fault-tolerance and high performance.[53] Multiple such NAS servers can be clustered to appear as a single device, which allows responsibility for serving clients to be shared in such a way that if one server fails then other servers can take over (often termed a failover) which also improves fault-tolerance.[54]
Windows Storage Server 2003 led to a second release named Windows Storage Server 2003 R2. This release adds file-server performance optimization, Single Instance Storage (SIS), and index-based search. Single instance storage (SIS) scans storage volumes for duplicate files, and moves the duplicate files to the common SIS store. The file on the volume is replaced with a link to the file. This substitution reduces the amount of storage space required, by as much as 70%.[55]
Windows Storage Server 2003 R2 provides an index-based, full-text search based on the indexing engine already built into Windows server.[55] The updated search engine speeds up indexed searches on network shares. This edition also provides filters for searching many standard file formats, such as ZIP archives, AutoCAD models, XML documents, MP3 audio files, PDF documents, and all Microsoft Office file formats.
Windows Storage Server 2003 R2 includes built in support for Windows SharePoint Services and Microsoft SharePoint Portal Server, and adds a Storage Management snap-in for the Microsoft Management Console. It can be used to manage storage volumes centrally, including DFS shares, on servers running Windows Storage Server R2.
Windows Storage Server 2003 R2 can be used as an iSCSI target with standard and enterprise editions of Windows Storage Server 2003 R2, incorporating WinTarget iSCSI technology which Microsoft acquired in 2006 by from StringBean software.[56][57] This will be an add-on feature available for purchase through OEM partners as an iSCSI feature pack, or is included in some versions of WSS as configured by OEMs.
Windows Storage Server 2003 can be promoted to function as a domain controller; however, this edition is not licensed to run directory services. It can be joined to an existing domain as a member server.[58]
Windows Server 2003 for Embedded Systems replaced "Windows 2000 Server for Embedded Systems". Intended use was for building firewall, VPN caching servers and similar appliances.[68] Variants were available with "Server Appliance Software" and with "Microsoft Internet Security and Acceleration Server" [69]
1.0 Welcome2.0 Operating System Support 2.1 Support for 64-bit Windows Platforms3.0 System Requirements3.1 BrightStor ARCserve Backup Base Product3.2 Disk Staging Option3.3 Client Agents3.4 Agent for IBM Informix3.5 Agent for Lotus Domino3.6 Agent for Microsoft Exchange Server3.7 Agent for Microsoft Exchange Server Premium Add-on3.8 Agent for Microsoft SharePoint3.9 Agent for Microsoft SQL Server3.10 Agent for Open Files3.11 Agent for Oracle3.12 Agent for Sybase3.13 Disaster Recovery Option3.14 Image Option3.15 NDMP NAS Option3.16 Tape and Optical Library Option3.17 Serverless Backup Option3.18 Tape RAID Option3.19 Storage Area Network (SAN) Option3.20 Enterprise Option for StorageTek ACSLS3.21 Enterprise Option for IBM 34943.22 Enterprise Option for SAP R/3 for Oracle3.23 Enterprise Option for Advantage Ingres3.24 Enterprise Option for VSS Hardware Snap-Shot3.25 Client for VSS Software Snap-Shot4.0 Installation Considerations4.1 BrightStor ARCserve Backup Base Product4.2 Enterprise Module4.3 Client Agents4.4 Agent for Lotus Domino4.5 Agent for Microsoft SharePoint4.6 Agent for Microsoft SQL Server4.7 Agent for Open Files 4.8 Disaster Recovery Option 5.0 General Considerations6.0 Known Issues6.1 Portmapper Conflicts with BrightStor ARCserve Backup6.2 Known Issues for the Base Product6.3 Known Issues for the Client Agent6.4 Known Issues for the Agent for IBM Informix6.5 Known Issues for the Agent for Microsoft SharePoint6.6 Known Issues for the Agent for Microsoft SQL Server6.7 Known Issues for Agent for Open Files6.8 Known Issues for the Agent for Sybase6.9 Known Issues for the Disaster Recovery Option6.10 Known Issues for the NDMP NAS Option6.11 Known Issues for the Optical Library Option6.12 Known Issues for the SAN Option6.13 Known Issues for the Enterprise Option for StorageTek ACSLS6.14 Known Issues for the Enterprise Option for IBM 34946.15 Known Issues for the Enterprise Option for SAP R/3 for Oracle6.16 Known Issues for the Client for VSS Software Snap-shot6.17 Known Issues for BrightStor Portal Integration6.18 Known Issues for Documentation7.0 Documentation Changes8.0 Language Certifications9.0 Documentation10.0 Contact Customer Support1.0 WelcomeWelcome to BrightStor ARCserve Backup forWindows r11.5. This Readme file contains importantinformation to help you with your implementation of theproduct, including installation considerations, operatingsystem information, known issues, and how to contactComputer Associates Customer Support.2.0 Operating System SupportBrightStor ARCserve Backup for Windows is supported onthe 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) 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 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 2.5 and 2.51, VMware Workstation 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. 2.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. 3.0 System RequirementsThe following sections provide information about theminimum system requirements for each BrightStor ARCserveBackup component. 3.1 BrightStor ARCserve Backup Base ProductThe minimum system requirements for BrightStor ARCserveBackup are: CPU: 350 MHzRAM: 512 MBDisk Space: 500 MB free disk spaceInternet Explorer: Version 6.0In addition to these requirements, you should considerthe disk space necessary for the Raima or Very LargeDatabase (VLDB), the default BrightStor ARCserve Backupdatabase. Depending upon usage, the BrightStor ARCserveBackup database can grow to several GB in size. 3.2 Disk Staging OptionBrightStor ARCserve Backup for Windows must be installedbefore you install the BrightStor ARCserveBackup Disk Staging Option. The following are the minimum platform requirements forthe Disk Staging Option: Windows 2000 Windows XP Professional Windows 2003 Windows Storage Server 2003 3.3 Client AgentsThe following sections provide hardware and softwarerequirements for the BrightStor ARCserveBackup Client Agents.Hardware RequirementsTo install the agent, your system must meet thefollowing minimum hardware requirements:Windows-based platforms:CPU: 200 MHzMemory: 256 MB RAMDisk space: 100 MBNetWare-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 MBUNIX-based platforms:Memory: 128 MB RAMDisk space: 16 MBLinux-based platforms:Memory: 128 MB RAMDisk space: 10 MBTo install the Client Agent for Mac OS X, your systemmust meet the following minimum hardware requirements:Minimum 10 MB hard disk spaceMinimum 128 MB RAMSoftware RequirementsYou can install the BrightStor ARCserve Backup ClientAgents 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 Server 2003 Cluster 32-bit, x64, and IA-64 Windows 2000 and Windows 2003 Datacenter 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 (IA-64) 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) 3.4 Agent for IBM InformixThe BrightStor ARCserve Backup Agent forIBM Informix requires the following: Informix Dynamic Server 9.21 or 9.40Agent for IBM InformixBrightStor ARCserve Backup for Windows3.5 Agent for Lotus DominoThe BrightStor ARCserve Backup Agent forLotus 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. 3.6 Agent for Microsoft Exchange ServerThe following sections provide the hardware and softwarerequirements for installing and running theBrightStor ARCserve Backup Agent forMicrosoft Exchange Server. Hardware RequirementsTo install the agent, the following hardware must beavailable and configured: The base Microsoft Exchange Server hardwarerequirements (for information about these requirements, seethe Microsoft website)At least 512 MB RAMAt least 100 MB of free disk spaceNote: You must meet the base BrightStor ARCserveBackup product requirements before you install the agentand BrightStor ARCserve Backup on the same machine. Forupdated information about these requirements, contactComputer Associates Customer Support at RequirementsThe Agent for Microsoft Exchange Server requires atleast 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 atleast one of the following Windows Exchange versions:Microsoft Exchange Server Version 5.5 Service Pack 4Microsoft Exchange Server Version 2000 Service Pack 3Microsoft Exchange Server Version 2003 Service Pack 13.7 Agent for Microsoft Exchange Server Premium Add-onThe following sections provide hardware and softwarerequirements for installing and running theBrightStor ARCserve Backup Agent forMicrosoft Exchange Server Premium Add-on.Hardware RequirementsTo install the agent, the following hardware must beavailable and configured:The base Microsoft Exchange Server hardwarerequirements (For information about these requirements, seethe Microsoft website)At least 512 MB RAMAt least 200 MB of free disk spaceNote: You must meet the base BrightStor ARCserveBackup product requirements before you install the agentand BrightStor ARCserve Backup on the same machine. ContactComputer Associates Customer Support at any updates to these requirements.Software RequirementsThe Agent for Microsoft Exchange Server Premium Add-onrequires at least one of the following Windows operatingsystems: 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 3.8 Agent for Microsoft SharePointThe BrightStor ARCserve Backup Agent forMicrosoft SharePoint requires the following:The Agent for Microsoft SharePoint is supported onthe following:Windows 2003 StandardWindows 2003 EnterpriseWindows 2003 WebThe agent does not require the BrightStor ARCserveBackup server component.BrightStor ARCserve Backup must be installed beforeyou install the Agent for Microsoft SharePointConfiguration Wizard. The Configuration Wizard is supportedon all operating systems on which BrightStor ARCserveBackup is supported.The Agent for Microsoft SharePoint requires at leastone of the following:Microsoft SharePoint Portal Server 2003 SP1Microsoft Windows SharePoint Services 2.0 SP1The 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.3.9 Agent for Microsoft SQL ServerThe BrightStor ARCserve Backup Agent forMicrosoft SQL Server requires at least one of the followingMicrosoft SQL Server platforms: Microsoft SQL Server 7.0 with Service Pack 4 Microsoft SQL Server 2000 (32-bit and 64-bit) with Service Pack 3, Service Pack 3a, and Service Pack 4 Microsoft SQL Server Desktop Engine (MSDE) 2000 with Service Pack 3, Service Pack 3a, and Service Pack 4 Microsoft SQL Server 2005 Beta 2 (x86) and the March 3, 2005, April 18, 2005, and June 7, 2005 Community Technology Previews (x86, x64, IA-64) BrightStor ARCserve Backup is also required. 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 Server 2005 SupportThe Agent for Microsoft SQL Server is compatible withthe following versions of Microsoft SQL Server 2005:The agent is compatible with Microsoft SQL Server2005 Beta 2 and the March 3, 2005, April 18, 2005, and June7, 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 SQLServer 2005 March 3, 2005, April 18, 2005, and June 7, 2005Community Technology Preview for x64-based (Athlon64,Opteron, Xeon EM64T) and IA-64 (Itanium) systems on Windows2003 SP1. The agent is expected to be compatible with future beta and CTP builds of Microsoft SQL Server 2005 and with the final product when released. Microsoft SQL Server 7.0 SupportThe Agent for Microsoft SQL Server supports Microsoft SQL Server 7.0 Service Pack 4 on the following operating systems: Windows NT Server 4.0 Service Pack 6a Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1 Windows 2003 and Windows 2003 with Service Pack 1 Microsoft SQL Server 2000 SupportThe Agent for Microsoft SQL Server supports Microsoft SQL Server 2000, Service Pack 3, Service Pack 3a, and Service Pack 4 on the following operating systems: Windows NT 4.0 Service Pack 6a Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1 Windows 2003 and Windows 2003 with Service Pack 1 Support for 64-bit SystemsUsing Microsoft SQL Server 2000, the Agent for MicrosoftSQL Server supports Microsoft SQL 2000 on the following64-bit editions of Windows: Microsoft SQL Server 2000 64-bit Edition for IA-64 on Windows 2003 for Itanium systems Note: If you are using Microsoft SQL Server 200064-bit Edition Service Pack 4, you should be aware that theservice pack is missing a 32-bit DLL. Without this DLL, youcannot perform virtual device-based backups. ContactMicrosoft to obtain help with this issue. Microsoft SQL Server 2000 for x86 (32-bit) on Windows 2003 SP1 for x64-based systems Microsoft SQL Server Desktop Engine (MSDE) 2000 SupportThe Agent for Microsoft SQL Server supports MSDE 2000, Service Pack 3, Service Pack 3a, and Service Pack 4 on the following operating systems: Windows NT 4.0 Service Pack 6a Windows 2000 Service Pack 4 or Service Pack 4 Rollup 1 Windows XP Service Pack 1 and Service Pack 2 Windows Server 2003 and Windows 2003 with Service Pack 1 3.10 Agent for Open FilesThe following section provides the minimum systemrequirements for the BrightStor ARCserveBackup Agent for Open Files:The Agent for Open Files Server Engine requires oneof the following operating systems:Windows NT 4.0Windows 2000Windows XP x86, x64, and IA-64Windows Server 2003 Web Edition, Standard Edition,or Enterprise Edition x86, x64, and IA-64To manage the Agent for Open Files on NetWareservers, the Novell NetWare Client software must beinstalled. The agent does not support the Microsoft NetWareClient. The Agent for Open Files NetWare Server Engine requires a server running Novell NetWare version 4.2, 5.1, 6.0, or 6.5. 3.11 Agent for OracleThe following section provides the minimum systemrequirements for the BrightStor ARCserveBackup 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 Service Pack 1 The Agent for Oracle supports Oracle Real ApplicationClusters (RAC) architecture through the use of the OracleRecovery Manager (RMAN) utility.3.12 Agent for SybaseThe BrightStor ARCserve Backup Agent forSybase requires Sybase Adaptive Server 11.9.2, 12.0, or12.5.The Agent for Sybase supports Windows as the host serverplatform. For Sybase Version 11.9.2, contact Sybase for thenecessary bcksrvr.exe and sybmuf.exe files.3.13 Disaster Recovery OptionThe BrightStor ARCserve Backup DisasterRecovery Option supports the following:The following versions of Windows are supported forfloppy-based disaster recovery:Windows NT 4.0 Server with Service Pack 6a (remoteonly)Windows NT 4.0 Workstation with Service Pack 6a(remote only)Windows 2000 Professional EditionWindows 2000 Server EditionWindows 2000 Advanced Server EditionThe following versions of Windows are supported forbootable 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 Datacenter Edition SP1 Windows 2003 SBS Edition The following versions of Windows are supported forbootable CD disaster recovery:Windows 2000 Professional EditionWindows 2000 Server EditionWindows 2000 Advanced Server EditionWindows XP Professional EditionWindows 2003 Web EditionWindows 2003 Standard EditionWindows 2003 Enterprise EditionWindows 2003 SBS EditionNote: Windows XP and Windows 2003 disasterrecovery are supported with the Microsoft Windows CD. The version of Windows you use to generate the bootmedia should be the version of Windows installed on yourmachine. The Disaster Recovery Option is not supported on 64-bitmachines.3.14 Image OptionYou can install BrightStor ARCserve BackupImage Option on Windows 2000 or Windows 2003.3.15 NDMP NAS OptionThe following section provides the minimum systemrequirements for the BrightStor ARCserveBackup NDMP NAS Option.To use the NDMP NAS Option, you must meet the followingrequirements:Operating System: Windows 2000 or Windows 2003Memory: Minimum 128MB RAMDisk Space: Minimum 95 MBIn addition to these requirements, you must meet thefollowing requirements, depending upon the devices youchoose:For Network Appliance devices:ONTAP Minimum Version 6.0.1R3NAS Server: Models F700 series, F800 series (ONTAPVersion is of primary concern, not the model)For EMC (IP4700) devices:Minimum firmware version R2.0 p21NAS Server Model: IP4700For EMC (Celerra) devices:Minimum file server version 4.2.9.0NAS Server model: CelerraFor PROCOM devices:Minimum firmware version: 4.1.3NAS Server Model: NetForce 1000 series, 3000 series3.16 Tape and Optical Library OptionBrightStor ARCserve Backup for Windows must be installedbefore you install the BrightStor ARCserveBackup Tape and Optical Library Option.The minimum platform requirements for the Tape LibraryOption are as follows:Windows 2000Windows XP ProfessionalWindows 2003The minimum platform requirements for the OpticalLibrary Option are as follows:Windows 2000Windows 20033.17 Serverless Backup OptionYou must install the following applications beforeinstalling the BrightStor ARCserve BackupServerless Backup Option:BrightStor ARCserve Backup for WindowsTape Library OptionStorage Area Network (SAN) OptionYou can install the Serverless Backup Option on Windows2000 or Windows 2003. 3.18 Tape RAID OptionBrightStor ARCserve Backup for Windows must be installedbefore installing the BrightStor ARCserveBackup Tape RAID Option.You can install the Tape RAID Option on Windows 2000 orWindows 2003.3.19 Storage Area Network (SAN) OptionYou must install the following applications beforeinstalling the BrightStor ARCserve BackupStorage Area Network (SAN) Option:BrightStor ARCserve Backup for WindowsTape Library Option for WindowsYou can install the Storage Area Network (SAN) Option onthe following Windows platforms:Windows 2000Windows 20033.20 Enterprise Option for StorageTek ACSLSThe BrightStor ARCserve Backup EnterpriseOption for StorageTek ACSLS requires, at minimum, theStorageTek ACSLS Library Attach (LibAttach) softwareversion 1.2.The option is supported on Windows 2000 and Windows 2003.3.21 Enterprise Option for IBM 3494The BrightStor ARCserve Backup EnterpriseOption for IBM 3494 requires the IBM Library ManagerControl service version 5.4.8.The option is supported on Windows 2000 and Windows 2003.3.22 Enterprise Option for SAP R/3 for OracleThe BrightStor ARCserve Backup EnterpriseOption for SAP R/3 for Oracle requires one of the followingversions of Oracle Server:Oracle 8, Oracle 8iOracle 9, Oracle 9iSAPDBA should be installed on the same server to use theagent BACKINT option.SAP R/3 for Windows version 4.6, 4.7, 6.2, or 6.4 is also required. 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 notobtain an Excluded Files List from Oracle databases underthis configuration. File system backups performed throughthe Client Agent for Windows may try to back up Oracledatabase files, but the Oracle data files in those backupsdo not represent a consistent copy of the databaseunless they have been taken when the Oracle database isoffline.3.23 Enterprise Option for Advantage IngresThe following section provides the minimum systemrequirements for the BrightStorARCserve Backup Enterprise Option forAdvantage™ Ingres:Microsoft Windows NT 4.0 Service Pack 6aMicrosoft Windows 2000 Service Pack 1 or ServicePack 2Microsoft Windows XP or Windows 2003Advantage Ingres Database Server 2.0, 2.5, 2.6 SP2,or 3.0Before using the option, ensure that the followingprivileges are assigned to the Windows user who owns theAdvantage Ingres installation (for version 2.0, 2.5, or 2.6SP2, this user is ingres; for version 3.0, it can beany user): Access this computer from network Act as part of the operating system Logon as a service Replace a process level tokenIf your Windows system is a workgroup member, performthe privilege verification and updates in Local SecurityPolicy. If your Windows system is a primary or secondarydomain controller, perform the privilege verification andupdates in Domain Controller Security Policy. If yourWindows system is a domain member, perform the privilegeverification and updates in Domain Security Policy.3.24 Enterprise Option for VSS Hardware Snap-ShotThe following section provides the minimum systemsrequirements for the BrightStor ARCserveBackup Enterprise Option for VSS Hardware Snap-Shot:On the Production ServerMicrosoft Windows Server 2003 Enterprise Edition orDatacenter EditionMicrosoft Exchange Server 2003 Service Pack 1 (ifMicrosoft Exchange 2003 Server is installed)Microsoft SQL Server 2000 Service Pack 3a (ifMicrosoft SQL 2000 Server is installed)BrightStor ARCserve Backup Client Agent for Windowsr11.5BrightStor ARCserve Backup Enterprise Option for VSSSoftware Snap-ShotVSS Hardware Provider for your disk array, obtainedfrom your disk array vendorOn the Backup ServerMicrosoft Windows Server 2003 Enterprise Edition orDatacenter EditionMicrosoft Exchange System Management Tools (if youare using the option to protect Microsoft Exchange 2003Server on the Production Server)Microsoft Exchange Server 2003 Service Pack 1 (ifMicrosoft Exchange Server 2003 Service Pack 1 is installedon the Production Server)BrightStor ARCserve Backup for Windows r11.5BrightStor ARCserve Backup for Windows r11.5Enterprise ModuleLicense for BrightStor ARCserve Backup EnterpriseOption for VSS Hardware Snap-ShotVSS Hardware Provider for your disk array, obtainedfrom your disk array vendor3.25 Client for VSS Software Snap-ShotThe following versions of Windows are supported forBrightStor ARCserve Backup Client for VSSSoftware Snap-Shot:Microsoft Windows XP Professional (BrightStorARCserve Backup does not support VSS Writers under WindowsXP Professional)Windows Server 2003To use the Client for VSS Software Snap-Shot, you musthave created at least one NTFS volume.If you are using VSS with Microsoft Exchange Server2003, you must have installed Microsoft Exchange Server2003 Service Pack 1 on both the Production Server and theBackup Server (for transportable snap-shot).4.0 Installation ConsiderationsThe following sections provide information aboutinstallation prerequisites, configurations, and issues toconsider before installing BrightStor ARCserve Backup andits agents and options.4.1 BrightStor ARCserve Backup Base ProductThe following section provides information aboutinstallation prerequisites, configurations, and issues toconsider before installing the BrightStor ARCserve Backupbase 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 Computer Associates Customer 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: Change the ODBC Network Libraries setting to TCP/IP, if necessary. Run SetupSQL.exe from BAB_HOME, or install Microsoft SQL 2000 or Microsoft SQL 7.0 server or client. 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: 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 This command creates the equivalence for the BrightStor ARCserve Backup System account to allow the iSponsor to work correctly. 4.2 Enterprise ModuleThe following section provides information aboutinstallation prerequisites, configurations, and issues toconsider before installing the BrightStorARCserve Backup Enterprise Module:The Enterprise Module must be installed to accessBrightStor ARCserve Backup advanced features and all theEnterprise Options except the Enterprise Option forAdvantage Ingres, the Enterprise Option for SAP/R3 forOracle, and the Enterprise Option for VSS HardwareSnap-Shot.4.3 Client AgentsThe following section provides information aboutinstallation prerequisites, configurations, and issues toconsider before installing the BrightStor ARCserve BackupClient Agents.Remote installation and response file installationof the Client Agents for Windows 98 and Windows Me are notsupported in the Master Setup.4.4 Agent for Lotus DominoThe following section provides information aboutinstallation prerequisites, configurations, and issues toconsider before installing the Agent for Lotus Domino.To upgrade from BrightStor ARCserve2000 to BrightStor ARCserve Backup, you must firstuninstall the BrightStor ARCserve 2000 agent. However, ifthe BrightStor ARCserve 2000 agent is for Lotus Notes forWindows (BAOF Version), you must first uninstall theBrightStor ARCserve 2000 agent, and then uninstall theembedded BAOF manually using the following procedure:Uninstall the BrightStor ARCserve 2000 Agent forLotus Notes for Windows (BAOF Version).Insert the original BrightStor ARCserve 2000 CD, orensure that an image of the CD is available.From the Windows command prompt, run the followingcommand:msiexec.exe /x FULL PATH TO BAOFNTAG.MSI PRODUCTS=2For example, where the original CD is used and inserted indrive F, enter the following at the prompt:msiexec.exe /x f:\IntelNT\Notes.DBA\baofntag.msi PRODUCTS=24.5 Agent for Microsoft SharePointThe following section provides information to considerwhen 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. When upgrading from a beta version of BrightStor ARCserve Backup r11.5, use the Agent for Microsoft SharePoint Configuration Wizard to upgrade all BrightStor ARCserve Backup SharePoint agents, including the Router Agent, External Data Agent, and Embedded SQL Agent. 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. 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. Ensure that the firewalls on any remote computers hosting the SharePoint installation are configured to allow exceptions. Install the Agent for Microsoft SharePoint from the BrightStor ARCserve Backup installation CD. The Agent for Microsoft SharePoint Configuration wizard starts automatically. 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. 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 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. 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. 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 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. 4.6 Agent for Microsoft SQL ServerThe following section provides information aboutinstallation prerequisites, configurations, and issues toconsider before installing the Agent for Microsoft SQLServer. 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 PremiumEdition includes Microsoft SQL Server 2000, Service Pack 3.4.7 Agent for Open FilesIf you install the Microsoft Cluster Service after youhave installed the Agent for Open Files, you must restartthe system to provide the agent with open file access tothe shared storage resources of the cluster.4.8 Disaster Recovery OptionThe following section provides information aboutinstallation prerequisites, configurations, and issues toconsider before installing the Disaster Recovery Option:When upgrading to BrightStor ARCserve Backup r11.5,you should recreate the machine-specific disk for allprotected machines. This ensures that you are using theoption's latest executables. For more information about howto update machine-specific disks, see the DisasterRecovery Option Guide.When you upgrade to BrightStor ARCserve Backupr11.5, a directory, called OldDR, is created to storeinformation from old backup operations. If you want tocreate a machine-specific disk from an old backup, you mustdo one of the following:Rename the OldDR directory to DRCopy the machine_name directories to the DRdirectory and create the machine-specific disks.5.0 General ConsiderationsThe following section provides general information toconsider 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 Registry Keys: \\HKEY_LOCAL_MACHINE\SYSTEM\CLONE
\\HKEY_LOCAL_MACHINE\HARDWARE
Registry files with the extensions *.ALT and *.LOG
Cluster installation directory files (typically, the WINNT\cluster folder), files with no extensions, and files with the extension *.LOG
\RECYCLER folder
Folder for file system devices
You can manage BrightStor ARCserve Backup for NetWare r11.1 with the BrightStor ARCserve Backup for Windows r11.5 Manager.
6.0 Known IssuesThe following sections provide information about issuesknown to exist in BrightStor ARCserve Backup for thisrelease.6.1 Portmapper Conflicts with BrightStor ARCserve BackupIf BrightStor ARCserve Backup detects port 111conflicts, indicating that it is using the same port numberfor the CA Remote Procedure Call server service as apreviously installed portmapper, BrightStor ARCserve Backupautomatically switches to another port number. To avoid having other software affected by a similarproblem, change the Automatic status of the CA RemoteProcedure Call server service to Manual. If you haveinstalled BrightStor ARCserve Backup in a Microsoft ClusterServices environment, change the Automatic status of the CARemote Procedure Call server service to Disabled. Thisenables you to avoid similar port conflicts after thesystem 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 thefollowing: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. 6.2 Known Issues for the Base ProductThe following issues relating to the BrightStor ARCserveBackup 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: On the agent machine, launch Discovery Environment configuration (dsconfig.exe). From the Backup Manager of the base server, delete the old machine object. On the base server, restart the discovery service or launch AutoDiscovery using dsconfig.exe. From the Backup Manager, add the machine with the new IP address using AutoDiscovery. If you have a scheduled job in the queue, delete that job and recreate it to ensure that it runs properly. Due to a netBIOS limitation, computer names longer than 15 characters are truncated to 15 characters, including when you set up a host server. If you install Windows Server 2003 Service Pack 1 using an Emulex Fibre Channel Card, you must download the latest Windows 2003 Storport HBA drivers from the Emulex website. A problem with the Emulex driver released with Windows 2003 SP1 prevents BrightStor ARCserve Backup from initializing correctly unless you update the Emulex driver. 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): In the Start menu, click Run, enter gpedit.msc, and press Enter. Note: This step does not apply to Windows 2003 Server SP1. 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. 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. 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. Access the Security Center (on Windows XP SP2) or Windows Firewall (on Windows 2003 Server SP1) and enable the firewall. 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) If you have the Client Agent or any database agent installed, on the Exceptions tab, select File and Printer Sharing. Restart the Windows XP Service Pack 2 machine and start BrightStor ARCserve Backup services. Method 2: In the Start menu, click Run, enter gpedit.msc, and press Enter. 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. 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. 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 Access the Security Center and turn the firewall off. 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 when it is successful because the Master Setup cannot accurately detect the activity on the remote machine in the other domain because of a firewall or due to a lost network connection. Check the installation status on the remote machine to verify that the installation succeeded. If you enable both Success and Failure for Audit object access under Local Security Policy, Local Policies, Local Audit Policy, you may receive multiple Success Audit messages under Security Events in the Event Viewer. To avoid receiving multiple Success Audit messages, perform the following procedure: Create a key called MessageEngine Under the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Admin 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 Restart the CA BrightStor Message Engine service.
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: 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. 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: 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) Log off from all login sessions, both local and remote (you do not have to reboot).
Uninstall BrightStor ARCserve Backup from the primary cluster node.
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 secondary 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. 2ff7e9595c
Comentarios