Home » Computer Associates Manuals » Computer Software » Computer Associates BABWBR1151S38 » Manual Viewer

Computer Associates BABWBR1151S38 Implementation Guide - Page 50

Microsoft SQL Server Database Considerations

UPC - 757943307405

View all Computer Associates BABWBR1151S38 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 50 highlights

Database Requirements ■ Consider the following upgrade scenarios: - You are using Microsoft SQL Server 2005 Express Edition to host the CA ARCserve Backup database. The name of the CA ARCserve Backup database instance is ARCSERVE_DB (default). This scenario also includes situations where a previous release of CA ARCserve Backup may not be installed on the target system, however, Microsoft SQL Server 2005 Express Edition is installed on the target system and you are using an instance named ARCSERVE_DB for other applications. - You are using Microsoft SQL Server 2005 Express Edition to host the CA ARCserve Backup database. The name of the CA ARCserve Backup database instance is not ARCSERVE_DB. When you upgrade to this release, Setup searches for the default CA ARCserve Backup database instance. If Setup detects an instance named ARCSERVE_DB, Setup upgrades the instance to Microsoft SQL Server 2008 Express Edition, and CA ARCserve Backup continues using the instance, and data, from the previous release. However, if Setup cannot detect an instance named ARCSERVE_DB, Setup creates a new instance called ARCSERVE_DB. If Setup creates a new database instance, the information from the previous CA ARCserve Backup release is not retained in the new instance. Microsoft SQL Server Database Considerations Review the following information if you are considering using Microsoft SQL Server for the CA ARCserve Backup database: ■ If you are upgrading to this release and currently running Microsoft SQL Server for the CA ARCserve Backup database, you must continue using Microsoft SQL Server for the CA ARCserve Backup database. ■ CA ARCserve Backup does not support using Microsoft SQL Server 7.0 for the CA ARCserve Backup database. ■ By default, CA ARCserve Backup creates the CA ARCserve Backup database (ASDB) using a simple recovery model. You should retain this model for proper operation. ■ Microsoft SQL Server supports local and remote communication. This capability lets you configure the CA ARCserve Backup database to run locally or remotely to your CA ARCserve Backup server. Note: For more information, see Remote Database Considerations. ■ By default, CA ARCserve Backup stores information about the backed up files and directories in the Catalog Database. This behavior causes the Catalog Database to grow in size at a faster rate than the CA ARCserve Backup database. Given this behavior and the needs of your organization, you should plan to have a sufficient amount of free disk space to support the growth of the Catalog Database. 50 Implementation Guide

Section	Page
CA ARCserve Backup for Windows Implementation Guide	1
Contents	7
1: Introducing CA ARCserve Backup	13
Introduction	13
Purpose of This Guide	14
2: Planning Storage Environments	15
Preliminary Tasks	15
Enterprise Storage Requirements	16
Budget Considerations	16
Network and Computer Infrastructure Requirements	17
Data Transfer Requirements	17
Backup Schedule Requirements	18
Data Backup Window Considerations	18
Hardware Data Transfer Rates	18
SCSI or Fibre Interface Considerations	19
Tape Drive Considerations	19
Network Bandwidth Considerations	20
Data Transfer Requirements and Resources Calculations	21
Data Path Considerations	22
Network Enhancements	22
Storage Area Networks	22
SCSI Bus and Device Enhancements	22
Alternate Data Path Considerations	23
Segment Your Network	23
Segment Data	23
Backup Scope	24
Parallel Storage Operations (Multiple Streaming)	26
Storage Capacity Requirements	26
Online Recovery Data Storage Requirements	26
Backup Data Storage Requirements	27
Global Dashboard Data Storage Requirements	27
Storage Capacities and Resources	28
Media Capacities	28
Factors Affecting Storage Capacity Calculations	29
Testing Plans and Assumptions	29
Catastrophic Events	30
Risk Assessment	30
Off-Site Repository Considerations	30
Vault Security Considerations	31
Vault Accessibility Considerations	31
Vault Expense Considerations	31
Disaster Recovery Archive Considerations	31
Disaster Recovery Testing	32
Sample Calculations	32
Transfer Rate for Clients and Servers on a 100Base-T Ethernet LAN With No Subnets	33
Transfer Rate for Clients and Servers on Two 100Base-T Ethernet Subnets	34
Transfer Rate for Clients and Servers on a Gigabit Ethernet Network	35
Transfer Rate for a Server With No Clients	35
Transfer Rate For Server With SAN Option	36
Storage Capacity for Two Sets of Recovery Data, One Full and One Incremental Backup	37
3: Planning CA ARCserve Backup Installations	39
Supported Platforms	39
Supported Devices	39
Tape Library Installations	40
Storage Area Network (SAN) Installations	40
Amount of Disk Space Required to Install CA ARCserve Backup	41
Installation Methods	42
Types of CA ARCserve Backup Server Installations	43
CA ARCserve Backup Server Options	47
caroot User Account	47
Database Requirements	48
Microsoft SQL Server 2008 Express Edition Considerations	48
Microsoft SQL Server Database Considerations	50
Remote Database Considerations	52
How to Enable TCP/IP Communication on Microsoft SQL Server Databases	53
Agent for ARCserve Database	53
Installation Progress Logs	54
Global Dashboard Considerations	56
Upgrade Considerations	57
Supported Upgrades	58
Backward Compatibility	59
Global Dashboard Upgrades	59
Data Migration from a Previous Release	60
Product License Requirements	60
ALP Key Certificate	61
CA ARCserve Backup File System Agents Release Levels	61
How the Installation Process Affects Operating Systems	62
Unsigned Binary Files	69
Binary Files Containing Incorrect File Version Information	74
Binary Files that are not Uninstalled Completely	82
Binary Files that do not Contain an Embedded Manifest	83
CA ARCserve Backup MSI Installer Package Identification	86
4: Installing and Upgrading CA ARCserve Backup	87
How to Complete Prerequisite Tasks	87
Install CA ARCserve Backup	92
Upgrade CA ARCserve Backup from a Previous Release	101
Create a Silent Installation Response File	108
Upgrade CA ARCserve Backup Agents Silently to the Current Release	114
Deploy Agents to Remote Computers from the Primary Server	117
Remote Deployment Considerations	119
Deploy Agents to Remote Computers Using Automatic Upgrade	120
Deploy Agents to Remote Computers Using Custom Deployment	122
Deploy Agents to Virtual Machines Using Virtual Machine Deployment	124
How to Install CA ARCserve Backup Using Unicenter Software Delivery	127
Register CA ARCserve Backup on the Unicenter Software Delivery Server	127
Components and Prerequisites	128
Install CA ARCserve Backup Components Using Unicenter Software Delivery	133
Post-Installation Tasks	134
5: Installing and Upgrading CA ARCserve Backup in a Cluster-aware Environment	135
Introduction to Cluster-aware Installations	135
Deployment Considerations	135
Plan Your CA ARCserve Backup HA Deployment	136
Deploy CA ARCserve Backup Server on MSCS	138
MSCS Hardware Requirements	139
MSCS Software Requirements	139
MSCS Cluster Resource Preparation	139
Prepare MSCS Cluster Resources on Windows Server 2008 Systems	141
Install CA ARCserve Backup in an MSCS Cluster-aware Environment	142
Upgrade CA ARCserve Backup from r12, r12.5, and r15 to r16 in an MSCS Cluster Environment	152
Uninstall CA ARCserve Backup from an MSCS Cluster	156
Delete CA ARCserve Backup Cluster Resources	157
Deploy CA ARCserve Backup Server on NEC Cluster	158
NEC CLUSTERPRO/ExpressCluster Hardware Requirements	158
NEC CLUSTERPRO/ExpressCluster Software Requirements	159
NEC CLUSTERPRO/ExpressCluster Resource Preparation	159
Install CA ARCserve Backup in an NEC Cluster-aware Environment	160
start.bat Script Changes for Member Servers and Non-SQL Express Primary Servers	171
stop.bat Script Changes for Member Servers and Non-SQL Express Primary Servers	172
start.bat Script Changes for SQL Express Primary Servers	173
stop.bat Script Changes for SQL Express Primary Servers	174
Upgrade CA ARCserve Backup from r12, r12.5, and r15 to r16 in an NEC CLUSTERPRO Environment	175
Manage and Configure NEC CLUSTERPRO/ExpressCluster X 3.0	179
Uninstall CA ARCserve Backup from an NEC CLUSTERPRO/ExpressCluster	180
Stop NEC Cluster Groups	182
Disable CA ARCserve Backup in NEC Cluster Scripts	183
Enable CA ARCserve Backup in NEC Cluster Scripts	185
How to Verify a Cluster-aware Installation and Upgrade	188
6: Integrating CA ARCserve Backup with Other Products	191
CA Antivirus Integration	191
CA ARCserve Replication Integration	191
CA ARCserve Backup Patch Manager Integration	192
7: Configuring CA ARCserve Backup	193
Open the Manager or Manager Console	193
CA ARCserve Backup Home Page	195
First-Time Home Page and User Tutorial	199
Service State Icons	200
Log in to CA ARCserve Backup	200
Specify CA ARCserve Backup Manager Preferences	202
Code Pages	204
How CA ARCserve Backup Supports Multiple Code Pages	204
Specify Code Pages in the Backup Manager Window	205
Specify Code Pages in the Restore Manager Window	206
CA ARCserve Backup System Account	206
How CA ARCserve Backup Manages Authentication	207
How to Use the System Account for Job Security	207
Configure the Windows Firewall to Optimize Communication	208
Allow Database Agents that Reside on Remote Subnets to Communicate with the ARCserve Server	210
Start the CA ARCserve Backup Database Protection Job	211
Fine-Tune the CA ARCserve Backup SQL Server Database	212
How to Calculate the Number of Required SQL Connections	213
Database Consistency Checks	213
Specify ODBC Communication for Remote Database Configurations	213
Configure Devices Using the Device Wizard	214
Configure Enterprise Module Components	215
Configure Global Dashboard	215
Configure the Central Site	217
Configure a Branch Site	220
Create File System Devices	224
How to Define Include and Skip Parameters for CA ARCserve Backup Database Agents	226
Configuring Firewalls to Optimize Communication	227
Ports Configuration File Guidelines	228
Modify the Ports Configuration File	229
Ports Used by CA ARCserve Backup Components	230
External Ports Used for Communication	230
Ports Used by the CA ARCserve Backup Base Product	231
Manager Console Communication with the Base Product	234
Primary Server and Member Server Communication Ports	234
Global Dashboard Server Communication	239
Base Product Communication with CA ARCserve Backup Agents and Options	239
Ports Used by CA ARCserve Backup Common Components	239
Discovery Service Communication Ports	240
Common Agent for UNIX and Linux Communication Ports	240
Ports Used by CA ARCserve Backup Agents and Options	240
Agent for Microsoft SharePoint Server Communication Ports	241
Client Agent for Windows Communication Ports	241
Agent for Microsoft Exchange Server Communication Ports	242
Agent for Microsoft SQL Server Communication Ports	243
Agent for Microsoft SharePoint Server Database Communication Ports	243
NDMP NAS Option Communication Ports	244
CA ARCserve Backup Database Agents Communication Ports	244
GUI Communication to CA ARCserve Backup Agents	245
How to Allow Agents and Database Agents to Communicate through a Firewall	245
GUI Managing the Base Product	246
CA ARCserve Backup Dashboard for Windows Firewall Communication Configuration	247
Additional Resources - Firewall Ports Specifications	248
Examples of How You Can Modify the Ports Configuration File	250
Ports Configuration File Configuration Considerations	252
Test Communication Through a Firewall	254
8: Uninstalling CA ARCserve Backup	255
Uninstall CA ARCserve Backup	255
Uninstall CA ARCserve Backup Components Using the Command Line	258
Uninstall Agent Deployment Setup Files	261
A: Troubleshooting CA ARCserve Backup Installations	263
Setup Cannot Communicate with Remote Microsoft SQL Server Databases	263
Unable to Log In to CA ARCserve Backup After Installing This Release	265
CA ARCserve Backup Services Fail to Initialize	266
The Tape Engine Does Not Start on Member Server Upgrades	267
Unable to Log in to CA ARCserve Backup After Upgrading to This Release	268
Unable to Determine What Devices Are Supported by CA ARCserve Backup	269
Cluster HA Resources Not Created	270
B: Using Best Practices to Install and Upgrade CA ARCserve Backup	271
Best Practices for Installing CA ARCserve Backup	271
How to Complete Prerequisite Tasks for Installing CA ARCserve Backup	272
Installing CA ARCserve Backup into a Single-server Environment	273
Recommended Configuration - Stand-alone Server	273
Components You Must Install	274
How to Install a Stand-alone Server or Primary Server	274
How to Verify a Stand-alone Server Installation	274
Installing a Primary Server with Member Servers	276
Recommended Configuration	276
Components You Must Install	277
How to Install a Primary Server with Member Servers	278
How to Verify a Primary Server with Member Servers Installation	278
Installing a Primary Server with Member Servers and Devices	280
Recommended Configuration	281
Components You Must Install	282
How to Install a Primary Server with Member Servers and Devices	283
How to Verify a Primary Server with Member Servers and Devices Installation	284
Installing a Primary Server with Member Servers and Shared Devices in a SAN	286
Recommended Configuration	286
Components You Must Install	287
How to Install a Primary Server with Member Servers and Shared Devices in a SAN	289
How to Verify a Primary Server with Member Servers and Shared Devices in a SAN Installation	289
Installing Multiple Primary Servers with Member Servers in a SAN	291
Recommended Configuration	292
Components You Must Install	293
How to Install Multiple Primary Servers with Member Servers in a SAN	295
How to Verify a Multiple Primary Servers with Member Servers in a SAN Installation	295
Installing CA ARCserve Backup into a Cluster-aware Environment	297
Recommended Configuration	298
Components You Must Install	299
How to Install CA ARCserve Backup into a Cluster-aware Environment	299
How to Verify a Cluster-aware Installation	300
Best Practices for Upgrading CA ARCserve Backup from a Previous Release	301
How to Complete Prerequisite Tasks for Upgrading CA ARCserve Backup	302
Upgrading a Stand-alone Server or Primary Server	303
Current Configuration - ARCserve Stand-alone Server	304
Recommended Configuration - CA ARCserve Backup Stand-alone Server or Primary Server	304
New Components You Must Install	305
Components You Must Upgrade	305
How to Upgrade to an ARCserve Stand-alone Server	305
How to Verify a Stand-alone Server or Primary Server Upgrade	306
Upgrading Multiple Stand-alone Servers in a Domain	308
Current Configuration - Multiple ARCserve Servers in a Domain	308
Recommended Configuration - CA ARCserve Backup Domain with a Primary Server and Member Servers	309
New Components You Must Install	310
Components You Must Upgrade	310
How to Upgrade Multiple ARCserve Servers to a Centralized Management Environment	311
How to Verify a Domain with a Primary Server and Member Servers Upgrade	311
Upgrading Multiple Stand-alone Servers Sharing a Remote Database	314
Current Configuration - Multiple ARCserve Servers Sharing a Remote Database	314
Recommended Configuration - CA ARCserve Backup Domain with a Primary Server and Member Servers	315
New Components You Must Install	316
Components You Must Upgrade	316
How to Upgrade Multiple ARCserve Servers Sharing a Database to a Centralized Management Environment	317
How to Verify a Centralized Management Environment Upgrade	317
Upgrading Servers in a SAN Using a Local or Remote Database	320
Current Configuration - Multiple ARCserve Servers in a SAN Using a Local or Remote Database	320
Recommended Configuration - CA ARCserve Backup Domain with a SAN Primary Server and SAN Distributed Servers	321
New Components You Must Install	322
Components You Must Upgrade	323
How to Upgrade Multiple ARCserve Servers in a SAN to This Release	323
How to Verify a Centralized Management Environment Upgrade+	324
Upgrading Multiple Servers in a SAN and Non-SAN Environment to this Release	326
Current Configuration - Multiple ARCserve Servers in a SAN and Non-SAN Environment	327
Recommended Configuration - CA ARCserve Backup Domain with a Primary Server and Member Servers	327
New Components You Must Install	328
Components You Must Upgrade	330
How to Upgrade Multiple ARCserve Servers in a SAN and a Non-SAN Environment to this Release	330
How to Verify a Centralized Management Upgrade	331
Upgrading Multiple Servers Using a Central Database	332
Current Configuration - Multiple ARCserve Servers Using a Central Database	333
Recommended Configuration - CA ARCserve Backup Domain with a Primary Server and Member Servers	334
New Components You Must Install	334
Components You Must Upgrade	335
How to Upgrade Multiple ARCserve Servers Using a Remote Database to a Centralized Management Environment	336
How to Verify a Centralized Management Upgrade	336
Upgrading Multiple Servers in a Cluster-aware Environment	339
Current Configuration - Multiple ARCserve Servers in a Cluster	339
Recommended Configuration - ARCserve Primary and Members Servers Installed in a Cluster-aware Environment	340
New Components You Must Install	342
Components You Must Upgrade	343
How to Upgrade an ARCserve Cluster-aware Environment to this Release	343
How to Verify a Cluster-aware Upgrade	344
General Best Practices	346
Where to Install the Manager Console	347
How to Install and Manage Licenses	347
Manage CA ARCserve Backup Component Licenses	348
Release Licenses from Servers	350
How to Install CA ARCserve Backup Server-Based Options	351
C: Acknowledgements	353
RSA Data Security, Inc. Acknowledgement	353
VMware VDDK	354
Glossary	355

Match case Limit results 1 per page

Database Requirements

Implementation Guide

■

Consider the following upgrade scenarios:

–

You are using Microsoft SQL Server 2005 Express Edition to host the CA

ARCserve Backup database. The name of the CA ARCserve Backup database

instance is ARCSERVE_DB (default). This scenario also includes situations where

a previous release of CA ARCserve Backup may

not

be installed on the target

system, however, Microsoft SQL Server 2005 Express Edition is installed on the

target system and you are using an instance named ARCSERVE_DB for other

applications.

–

You are using Microsoft SQL Server 2005 Express Edition to host the CA

ARCserve Backup database. The name of the CA ARCserve Backup database

instance is not ARCSERVE_DB.

When you upgrade to this release, Setup searches for the default CA ARCserve

Backup database instance. If Setup detects an instance named ARCSERVE_DB, Setup

upgrades the instance to Microsoft SQL Server 2008 Express Edition, and CA

ARCserve Backup continues using the instance, and data, from the previous release.

However, if Setup cannot detect an instance named ARCSERVE_DB, Setup creates a

new instance called ARCSERVE_DB. If Setup creates a new database instance, the

information from the previous CA ARCserve Backup release is not retained in the

new instance.

Microsoft SQL Server Database Considerations

Review the following information if you are considering using Microsoft SQL Server for

the CA ARCserve Backup database:

■

If you are upgrading to this release and currently running Microsoft SQL Server for

the CA ARCserve Backup database, you must continue using Microsoft SQL Server

for the CA ARCserve Backup database.

■

CA ARCserve Backup does not support using Microsoft SQL Server 7.0 for the CA

ARCserve Backup database.

■

By default, CA ARCserve Backup creates the CA ARCserve Backup database (ASDB)

using a simple recovery model. You should retain this model for proper operation.

■

Microsoft SQL Server supports local and remote communication. This capability lets

you configure the CA ARCserve Backup database to run locally or remotely to your

CA ARCserve Backup server.

Note:

For more information, see Remote Database Considerations.

■

By default, CA ARCserve Backup stores information about the backed up files and

directories in the Catalog Database. This behavior causes the Catalog Database to

grow in size at a faster rate than the CA ARCserve Backup database. Given this

behavior and the needs of your organization, you should plan to have a sufficient

amount of free disk space to support the growth of the Catalog Database.