1. Manuals
  2. Brands
  3. Computer Associates Manuals
  4. Software
  5. SQLSTQ99000600 - Unicenter SQL-Station 6.0.0
  6. Manual

Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 Manual

Agent for microsoft sql server guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
CA ARCserve
Backup for
®
Windows
Agent for Microsoft SQL Server Guide
r15

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0

Summary of Contents for Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0

  • Page 1 CA ARCserve Backup for ® Windows Agent for Microsoft SQL Server Guide...
  • Page 2 This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.
  • Page 3 CA Product References This documentation set references the following CA products: ® ■ BrightStor Enterprise Backup ■ CA Antivirus ® ■ CA ARCserve Assured Recovery™ ® ® ■ CA ARCserve Backup Agent for Advantage™ Ingres ® ■ CA ARCserve Backup Agent for Novell Open Enterprise Server for Linux ®...
  • Page 4 ® ■ CA ARCserve Backup for Windows Enterprise Option for IBM 3494 ® ■ CA ARCserve Backup for Windows Enterprise Option for SAP R/3 for Oracle ® ■ CA ARCserve Backup for Windows Enterprise Option for StorageTek ACSLS ® ■ CA ARCserve Backup for Windows Image Option ®...
  • Page 5 Contact CA Contact Technical Support For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At CA ARCserve Backup Support, you can access the following: ■...

  • Page 6: Documentation Changes

    Documentation Changes The following documentation updates have been made since the last release of this documentation: ■ Compatibility Matrix (see page 16) --Shows the features of Microsoft SQL Server supported in CA ARCserve Backup, by version. ■ Planning a Backup and Recovery Strategy (see page 107)--Presents essential Microsoft SQL Server basics you should know before you use CA ARCserve Backup, describes new SQL Server 2008 features, and provides a...

  • Page 7: Table Of Contents

    Contents Chapter 1: Introducing the Agent Introduction .................. Architectural Overview ................ How the Agent Works ................. How a Backup Request Works ............. How a Restore Request Works ............. How Data Flows During Backup ............Agent Services ................Access Requirements ..............Backup and Restore Options ...............
  • Page 8 Chapter 4: Restoring Microsoft SQL Server Databases Restore Options ................Automatic Selection Option ..............Restore Types ................Log Point-in-Time Restore Options ............Recovery Completion State Options ............Database Consistency Check (DBCC) Options ..........Force Restore to use Named Pipes ............Continue Restore After Checksum Failure ...........
  • Page 9 Configure Agent Behavior for Databases Ineligible for Backup ........Additional Database Status Considerations ..........Microsoft SQL Server Disaster Recovery ............The Master Database ..............Disaster Recovery Scenario ............... Appendix B: Configuring Microsoft SQL Server Security Settings Types of Microsoft SQL Server Authentication ..........

  • Page 11: Chapter 1: Introducing The Agent

    Chapter 1: Introducing the Agent This section contains the following topics: Introduction (see page 11) Architectural Overview (see page 12) How the Agent Works (see page 13) Microsoft SQL - CA ARCserve Backup Compatibility Matrix (see page 16) Agent Activity Log (see page 17) Online Backup of SAP R/3 Databases (see page 17)

  • Page 12: Architectural Overview

    Architectural Overview Architectural Overview You can install CA ARCserve Backup on the same host as the Agent for Microsoft SQL Server for local operation, or on separate systems. A single installation of CA ARCserve Backup can work with agents on many systems, allowing multiple machines to be backed up by a single backup server.

  • Page 13: How The Agent Works

    How the Agent Works How the Agent Works CA ARCserve Backup and the agent work together to back up and restore SQL Server databases. When CA ARCserve Backup backs up a database, it sends a request to the agent. The agent retrieves a point-in-time-consistent image of the database or its transaction log from Microsoft SQL Server in the form of a logical data stream, and sends it to CA ARCserve Backup, where the complete database image is backed up to media.

  • Page 14: How A Restore Request Works

    How the Agent Works How a Restore Request Works Restore jobs use the following process: 1. You issue a restore command from CA ARCserve Backup. 2. CA ARCserve Backup informs the agent of the restore job. 3. The agent instructs Microsoft SQL Server to prepare to receive the data. 4.

  • Page 15: Access Requirements

    How the Agent Works Access Requirements When you submit a job that includes Windows database servers, CA ARCserve Backup prompts you for a system user name and password for the system on which the database resides. CA ARCserve Backup accesses the remote servers using this user name and password.

  • Page 16: Microsoft Sql - Ca Arcserve Backup Compatibility Matrix

    Microsoft SQL - CA ARCserve Backup Compatibility Matrix Restore options enable you to do the following: ■ Restore data and transaction logs ■ Automatically determine a sequence of backups to restore, to produce a live, consistent database with a single restore job ■...

  • Page 17: Agent Activity Log

    Agent Activity Log Microsoft SQL Server Version Feature/Function SQL 7.0 2000 2005 2008 Full-text search catalogs (see page 110) Resource database Full database backups (see page 118) Differential database backups (see page 119) Partial database backups (see page 122) Torn Page Repair Include checksum generated by SQL Server Continue restore after checksum...

  • Page 18: Agent For Arcserve Database

    Agent for ARCserve Database Agent for ARCserve Database The CA ARCserve Backup Agent for ARCserve Database is a form of the CA ARCserve Backup Agent for Microsoft SQL Server. The agent is either installed automatically when you install CA ARCserve Backup, or manually using a special utility, either after the location of the CA ARCserve Backup database is changed, or on multiple nodes of a cluster.
  • Page 19 Agent for ARCserve Database Because the Agent for ARCserve Database is a form of the Agent for Microsoft SQL Server, it will appear as the CA ARCserve Backup Agent for Microsoft SQL Server in the system’s installed programs list. If both are present, only a single entry will appear.

  • Page 21: Chapter 2: Installing The Agent

    Chapter 2: Installing the Agent The Agent for Microsoft SQL Server is a client program you can install in two configurations: ■ On the same machine as Microsoft SQL Server ■ On a local drive of each node in a Microsoft Cluster Services cluster that contains Microsoft SQL Server This section explains how to install the Agent for Microsoft SQL Server in both configurations.
  • Page 22 Installation Prerequisites ■ Install the Agent for Microsoft SQL Server on the local drives of all nodes in the MSCS cluster as part of the initial agent installation. 22 Agent for Microsoft SQL Server Guide...

  • Page 23: Installation Considerations

    Installation Considerations Installation Considerations The following should be considered before installing the CA ARCserve Backup Agent for Microsoft SQL Server: ■ 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\CA ARCserve Backup, and the PortsConfig.cfg file for the 32-bit components is in c:\Program Files (x86)\CA\SharedComponents\CA ARCserve Backup.

  • Page 24: Install The Agent

    Install the Agent ■ In cluster environments, you may receive a Lost Connection error while installing the Agent for Microsoft SQL Server. This occurs in primary and stand-alone installations when you select the clustered SQL server instance as the CA ARCserve Backup database. To avoid this error, copy the Agent for CA ARCserve Backup database package to each cluster node and run setup manually.

  • Page 25: Install The Agent In A Microsoft Sql Server 2000 Or Later Cluster Environment

    Post-Installation Procedures Install the Agent in a Microsoft SQL Server 2000 or Later Cluster Environment To install the Agent for Microsoft SQL Server in a Microsoft SQL Server 2000, 2005, or 2008 cluster environment, follow the standard installation procedure for the system components, agents, and options of CA ARCserve Backup. For the detailed steps in this procedure, see the Implementation Guide.

  • Page 26: Configure Backup And Restore Parameters For The Agent For Microsoft Sql Server

    Post-Installation Procedures Configure Backup and Restore Parameters for the Agent for Microsoft SQL Server Use the Central Agent Admin utility to configure the Agent for Microsoft SQL Server backup and restore parameters for supported versions of Microsoft SQL Server. The parameters include settings for Microsoft Virtual Device Interface (VDI) objects and remote communication.
  • Page 27 Post-Installation Procedures 6. Select the Instance (ARCSERVE_DB) or the name of the instance for which you wish to change configuration for the Agent for Microsoft SQL Server. 7. Set the parameters under Virtual Device Configuration as follows: Number of Stripes--Determines the number of CPUs used to perform ■...

  • Page 28: How To Uninstall The Ca Arcserve Backup Agent For Microsoft Sql

    How to Uninstall the CA ARCserve Backup Agent for Microsoft SQL 8. Under Named Pipes Configuration, specify the Maximum Connection Wait Time (ms) time, in milliseconds, the Agent for Microsoft SQL Server should wait to close a named pipe if a remote connection fails. The default setting is 400 ms.

  • Page 29: Chapter 3: Backing Up Microsoft Sql Server Databases

    Chapter 3: Backing Up Microsoft SQL Server Databases This section contains information about backing up databases and Transaction logs using CA ARCserve Backup, the Agent for Microsoft SQL Server, and Microsoft SQL Server 7.0, Microsoft SQL Server 2000, Microsoft SQL Server 2005 and Microsoft SQL Server 2008.

  • Page 30: Backup Manager Agent Options

    Backup Overview Backup Manager Agent Options You may select backup options on a per-database basis or define a set of default options for all databases in a backup job. The Agent then applies the options to each database as appropriate. ■...
  • Page 31 Backup Overview ■ When you upgrade an older agent to CA ARCserve Backup r12.5 or later, the agent applies both any pre-existing local options and all global options that apply and do not conflict with the database level (local) options. ■...
  • Page 32 Backup Overview Agent Options (Global Options) Global Options/Agent Options (supported by releases of the Agent in r12.5 and later) allow you to set default job options for all SQL Server Agent objects and include essentially the same options accessible from the local options. Backup Methods The following backup methods are provided on both the Agent Options (database level) and Agent Options (Global Options) dialogs:...
  • Page 33 Backup Overview In releases of the agent that pre-date CA ARCserve Backup r12, the Global Backup Method or Rotation Scheme option from the Job Scheduler overrides local database options. In this release, the Global Backup Method or Rotation Scheme is applied only if you selected Use Global or Rotation Options in the database level options for the database and in the Global Agent Options for SQL Server.
  • Page 34 Backup Overview ■ For databases that have not yet received a Database Full backup, CA ARCserve Backup ignores the backup method set in the Global Agent Options tab and performs a full backup by default. ■ For databases using the Simple Recovery Model, CA ARCserve Backup performs a Differential backup when you choose Transaction Log Only on the Global Agent Options tab.
  • Page 35 Backup Overview Be aware of the following behavior: If you select this option on the Global Options/Agent Options tab and ■ specify Incremental backup method using the Job Scheduler, CA ARCserve Backup performs only one transaction log backup on the database and uses the Transaction Log Truncation Options from the Global Agent Options tab instead of the Incremental backup's default behavior (truncate the transaction log).
  • Page 36 Backup Overview Log Truncation Options Log Truncation Options are accessible from the Database Level/Agent Options and Global Options/Agent Options dialogs: ■ Remove inactive entries from transaction log, after backup--(Truncation) Truncates the Transaction Log files, removing entries included in the backup so that the space in the files can be reused. This is the default option.
  • Page 37 Backup Overview ■ Do not check indexes--Checks the database for consistency without checking indexes for user-defined tables. Note: The system table indexes are checked regardless of whether you select this option. ■ Check only the physical consistency of the database--Detects torn pages and common hardware failures, but does not check the data against the rules of the database schema.

  • Page 38: Dynamic And Explicit Job Packaging

    Dynamic and Explicit Job Packaging Other Options From the Global Agent Options tab, you can specify the following additional options: ■ Include Checksum Generated by SQL Server--Includes error checking information from Microsoft SQL Server, which can be used to validate the integrity of the backed-up data during restore.

  • Page 39: Dynamic Job Packaging

    Dynamic and Explicit Job Packaging Dynamic Job Packaging If you mark a database instance for dynamic job packaging when defining a backup job, CA ARCserve Backup automatically selects, at the time the backup job runs, all the components of the object (for example, child volumes and files) for backup.

  • Page 40: Mark Objects For Dynamic Job Packaging

    Dynamic and Explicit Job Packaging Mark Objects for Dynamic Job Packaging When you mark an object for dynamic job packaging when defining a backup job, CA ARCserve Backup automatically selects all the components of that object (child volumes, files, and so on) for backup. To mark an object for dynamic job packaging 1.

  • Page 41: Mark Objects For Explicit Job Packaging

    Dynamic and Explicit Job Packaging Mark Objects for Explicit Job Packaging Instead of an entire database, you may wish to select a specific child object for backup, but not its parent. To customize volume and database options, mark objects for explicit job packaging. To mark an object for explicit job packaging 1.

  • Page 42: Back Up A Database

    Back Up a Database Back Up a Database Use the Backup Manager in CA ARCserve Backup to back up databases. To back up a database 1. Ensure that Microsoft SQL Server is running on your server. The Microsoft SQL Server service must be started. 2.
  • Page 43 Back Up a Database 9. If you chose the Files-and-FileGroups subset, click the Browse button. The Specify FileGroups and Files dialog opens. Select the specific files and FileGroups you want to back up and click OK. 10. (Optional) Enable a Database Consistency Check and select the Database Consistency Check options.

  • Page 45: Chapter 4: Restoring Microsoft Sql Server Databases

    Chapter 4: Restoring Microsoft SQL Server Databases This section contains information about restoring databases and Transaction logs using CA ARCserve Backup, the Agent for Microsoft SQL Server, and Microsoft SQL Server 7.0, Microsoft SQL Server 2000, Microsoft SQL Server 2005 and Microsoft SQL Server 2008.

  • Page 46: Restore Options

    Restore Options Restore Options The Agent for Microsoft SQL Server provides restore options as shown in the following dialog: ■ Automatic Selection (see page 47) ■ Restore Type (see page 47): Database, Files or FileGroups, Partial (Microsoft SQL Server 2000 and later), or Torn Page Repair (Microsoft SQL Server 2005) ■...

  • Page 47: Automatic Selection Option

    Restore Options Automatic Selection Option The Automatic Selection option automatically: ■ Selects other sessions that must be restored with the session you are restoring for the restore job to be successful ■ Applies selected options appropriately to the automatically selected sessions The Automatic Selection option is enabled by default for every restore job.
  • Page 48 Restore Options You must load backups of the Transaction log in the sequence in which they were created. Microsoft SQL Server checks the timestamps on each backed up database and each backed up Transaction log to verify that the sequence is correct.
  • Page 49 Restore Options Files and FileGroups restore Restores selected files and FileGroups. You can restore files and FileGroups from either a Files-and-FileGroups backup, Partial backup or Database backup. When restoring files or FileGroups, you must first restore from a Full backup session, then optionally from a differential session, followed by all of the Transaction log backup sessions performed after the Full or Differential backup.

  • Page 50: Log Point-In-Time Restore Options

    Restore Options Log Point-in-Time Restore Options The Log Point-in-Time Restore option restores a database to the state it was in at a date and time, or as of a named transaction, that you have specified. You should use Automatic Selection with this option. This option is only available when the selected session is a Transaction Log backup.

  • Page 51: Recovery Completion State Options

    Restore Options Stop at log mark The option recovers the database activity through the transaction which is marked with the specified name, including the transaction that contains the mark. If you do not select the After Date and Time option, recovery stops at the first marked transaction with the specified name.

  • Page 52: Database Consistency Check (Dbcc) Options

    Restore Options Leave database nonoperational, but able to restore additional transaction logs Instructs the restore operation not to roll back any uncommitted transactions and to leave the database in a state where it can accept additional Files-and-FileGroups, Differential, or Transaction Log restores. You must choose either this option or the Leave database read-only option to apply another differential backup or Transaction log after this restore job is complete.

  • Page 53: Force Restore To Use Named Pipes

    Restore Options Check only the physical consistency of the database Detects torn pages and common hardware failures, but does not check the data against the rules of the database schema. It still checks the integrity of the physical structure of the page and record headers, and the consistency between the page’s object ID and index ID.

  • Page 54: Database File Options

    Database File Options Restricted User Access After Restore Option Restricts access to a newly restored database to members of the db_owner, dbcreator, or sysadmin roles. In Microsoft SQL Server 2000 and Microsoft SQL Server 2005, Restricted_User replaces the DBO_Only option from Microsoft SQL Server 7.0.
  • Page 55 Database File Options You can move the files to a different location on disk either individually or using Move Rules. Move Rules can be applied to an entire database, individual FileGroup or Transaction Log, or to an individual file. You can specify rules to move files to a particular drive, directory path, or rename the file, all independently of each other.
  • Page 56 Database File Options Restore to Original Location, Except Available at the Database, FileGroup and Transaction Log, and File levels. Applies the requested changes to the drive letter, paths and file names based on the location of the file when the backup was performed. Inherit Move Rules, Except Available at the FileGroup and Transaction Log, and File levels.

  • Page 57: Restore Databases Using Restore By Tree Method

    Restore Databases Using Restore by Tree Method Restore Databases Using Restore by Tree Method To restore using the Restore by Tree method 1. On the Restore Manager Source tab, select Restore by Tree from the drop-down list. 2. In the navigation tree, expand the computer from which the database was backed up to view the database instances.
  • Page 58 Restore Databases Using Restore by Tree Method 7. In the Restore Manager, click the Destination tab and select a destination using one of the following procedures: To restore to the original instance on the original server using the ■ original database name, select the Restore files to their original locations option if not selected already.
  • Page 59 Restore Databases Using Restore by Tree Method 11. Verify or change the user name or password for the database servers to which you are restoring. To verify or change the user name or password for the database servers, follow these steps: a.

  • Page 60: Restore Databases Using Restore By Session Method

    Restore Databases Using Restore by Session Method Restore Databases Using Restore by Session Method To perform a restore operation using Restore by Session method 1. On the Restore Manager Source tab, select Restore by Session from the drop-down list. A list of the media you have used when backing up with CA ARCserve Backup opens.
  • Page 61 Restore Databases Using Restore by Session Method 5. Perform one of the following to select restore options: Click OK to accept the default options and allow the Automatic Selection ■ option select the appropriate restore sequence and options for the restore job.
  • Page 62 Restore Databases Using Restore by Session Method 10. Verify or change the user name or password for the Windows computer on which Microsoft SQL Server is loaded. To verify or change the user name or password, follow these steps: a. Select a session on the Machine tab and click Edit. The Enter User Name and Password dialog opens.

  • Page 63: Sql Agent Filter Options

    SQL Agent Filter Options SQL Agent Filter Options You can use the SQL Agent Filter option in the Restore Manager to display backup sessions of a particular database belonging to a particular server name and, for Microsoft SQL Server 2000 and Microsoft SQL Server 2005 or later, a particular instance.

  • Page 64: Restore To Alternate Disk Locations By Individual Session

    Restore to Alternate Disk Locations by Individual Session 2. Choose Agent Options. The Agent Restore Options dialog opens. 3. In the second folder tab, if the FileGroups and data files appear, you can use Automatic Selection. Follow the appropriate procedures in this chapter to restore your data.

  • Page 65: Restore By Session Using A Separate Job For Each Session

    Restore to Alternate Disk Locations by Individual Session 7. For the earliest of these backup sessions (the full backup on which the others depend), make the appropriate changes to the file paths and names. Important! Do not edit the file names or paths for any of the sessions except the full backup session.

  • Page 66: Restore By Tree Using A Separate Job For Each Session

    Restore to Alternate Disk Locations by Individual Session 11. Click OK to close the Agent Restore Options dialog and submit the restore job. For instructions about restoring by session, see the appropriate section in this chapter. 12. Repeat the preceding steps from the point at which you close the Agent Restore Options dialog and submit the restore job until all backup sessions have been submitted for the restore.
  • Page 67 Restore to Alternate Disk Locations by Individual Session 10. If this is not the last session to be restored, select the Leave database nonoperational, but able to restore additional transaction logs option under Recovery Completion State. If this is the last session to be restored, confirm that the Leave database operational.

  • Page 68: Perform An Offline Torn Page Restore Using Microsoft Sql Server 2005 Or 2008

    Perform an Offline Torn Page Restore Using Microsoft SQL Server 2005 or 2008 Perform an Offline Torn Page Restore Using Microsoft SQL Server 2005 or 2008 Microsoft SQL Server 2005 and 2008 have the ability to detect when the data in the database has been damaged and isolate the damage at the data page level.
  • Page 69 Perform an Offline Torn Page Restore Using Microsoft SQL Server 2005 or 2008 Submit the Restore job. 6. Change to Simple Recovery Model, if you changed the Recovery Model in step 1. 7. Resume use of the database. Chapter 4: Restoring Microsoft SQL Server Databases 69...

  • Page 70: Perform An Online Torn Page Restore Using Microsoft Sql Server 2005 Or 2008 Enterprise, Data Center, Or Developer Editions

    Perform an Online Torn Page Restore Using Microsoft SQL Server 2005 or 2008 Enterprise, Data Center, or Developer Editions Perform an Online Torn Page Restore Using Microsoft SQL Server 2005 or 2008 Enterprise, Data Center, or Developer Editions Microsoft SQL Server 2005 and 2008 have the ability to detect when the data in the database has been damaged, and isolate the damage at the data page level.
  • Page 71 Perform an Online Torn Page Restore Using Microsoft SQL Server 2005 or 2008 Enterprise, Data Center, or Developer Editions 4. Attempt to query the table that contained the damaged page. 5. Perform a Transaction Log backup with the default options. 6.

  • Page 73: Chapter 5: Backing Up And Restoring In Cluster Environments

    Chapter 5: Backing Up and Restoring in Cluster Environments This section contains information about backing up and restoring database and transaction logs using CA ARCserve Backup, the Agent for Microsoft SQL Server, and Microsoft SQL Server 2000, 2005, or 2008 in a Microsoft SQL Server cluster environment.

  • Page 74: Microsoft Sql Server 2000, 2005 And 2008 Cluster Environment Prerequisites

    Microsoft SQL Server 2000, 2005 and 2008 Cluster Environment Prerequisites Microsoft SQL Server 2000, 2005 and 2008 Cluster Environment Prerequisites Before you install the Agent for Microsoft SQL Server in a Microsoft SQL Server 2000, 2005, or 2008 cluster environment, in addition to the basic prerequisites, perform the following tasks: ■...
  • Page 75 Microsoft SQL Server 2000, 2005, or 2008 Cluster Environment Backups 4. On the Source tab, expand the Microsoft SQL Server virtual server name, not the physical nodes or the Windows virtual server. The Microsoft SQL Server virtual server instances are located under the Microsoft SQL Server virtual server object with which they are associated.

  • Page 76: Select Backup Destination, Schedule, And Submit The Job

    Microsoft SQL Server 2000, 2005, or 2008 Cluster Environment Backups 14. (Optional) In the Agent Backup Options dialog, enable a Database Consistency Check, select Database Consistency Check options, and click Note: For more information about Database Consistency Checks, see Backing Up Microsoft SQL Server Databases (see page 29) and the Microsoft SQL Server documentation.

  • Page 77: Restore By Tree In Microsoft Sql Server 2000, 2005 Or 2008 Cluster Environments

    Restore by Tree in Microsoft SQL Server 2000, 2005 or 2008 Cluster Environments 5. (Optional) Use the Submit Job dialog to select the job execution time, submit the job on hold, add an optional job name for the backup job, or select source priority.
  • Page 78 Restore by Tree in Microsoft SQL Server 2000, 2005 or 2008 Cluster Environments 6. Perform one of the following to select restore options: Click OK to accept the default options and allow the Automatic Selection ■ option select the appropriate restore sequence and options for the restore job.
  • Page 79 Restore by Tree in Microsoft SQL Server 2000, 2005 or 2008 Cluster Environments 11. Verify or change the user name or password for the Windows computer on which Microsoft SQL Server is loaded. To verify or change the user name or password, follow these steps: a.

  • Page 80: Restore By Session In Microsoft Sql Server 2000, 2005 Or 2008 Environments

    Restore by Session in Microsoft SQL Server 2000, 2005 or 2008 Environments Restore by Session in Microsoft SQL Server 2000, 2005 or 2008 Environments You can restore databases by session in a single restore job using the Restore by Session method. To perform a restore using the Restore by Session method 1.
  • Page 81 Restore by Session in Microsoft SQL Server 2000, 2005 or 2008 Environments 7. In the Restore Manager, click the Destination tab and select a destination using one of the following procedures: To restore to the original instance on the original server using the ■...
  • Page 82 Restore by Session in Microsoft SQL Server 2000, 2005 or 2008 Environments 10. Verify or change the user name or password for the Windows computer on which Microsoft SQL Server is loaded. To verify or change the user name or password, follow these steps: a.

  • Page 83: Perform Disaster Recovery In Microsoft Sql Server 2000, 2005, Or 2008 Cluster Environments

    Perform Disaster Recovery in Microsoft SQL Server 2000, 2005, or 2008 Cluster Environments Perform Disaster Recovery in Microsoft SQL Server 2000, 2005, or 2008 Cluster Environments If a disaster occurs, you can recover your SQL database in a cluster environment. To perform a disaster recovery in a Microsoft SQL Server 2000, 2005, or 2008 cluster environment 1.

  • Page 85: Appendix A: Troubleshooting And Disaster Recovery

    Appendix A: Troubleshooting and Disaster Recovery This appendix explains the most common messages for CA ARCserve Backup and the Agent for Microsoft SQL Server and provides general troubleshooting information and important information about disaster recovery. This section contains the following topics: General Considerations for CA ARCserve Backup and the Agent (see page 86) Upgrade Considerations for the Agent for Microsoft SQL...

  • Page 86: General Considerations For Ca Arcserve Backup And The Agent

    General Considerations for CA ARCserve Backup and the Agent General Considerations for CA ARCserve Backup and the Agent The following general considerations apply to CA ARCserve Backup and the Agent for Microsoft SQL Server: ■ CA ARCserve Backup does not support special characters (for example, /, \, *, <, >, or ?) in file names, FileGroup names, and database names.
  • Page 87 General Considerations for CA ARCserve Backup and the Agent However, when a large remote SQL Server database is restored, particularly when it involves creation of SQL data files, such as when you restore to a different SQL Server, the Agent for Microsoft SQL cannot reply immediately because SQL Server takes some time to create the files, and the agent must wait for this to complete before it can respond.

  • Page 88: Upgrade Considerations For The Agent For Microsoft Sql

    Upgrade Considerations for the Agent for Microsoft SQL Upgrade Considerations for the Agent for Microsoft SQL The following considerations relate to upgrading the CA ARCserve Backup Agent for Microsoft SQL: ■ After upgrading Microsoft SQL Server (for example, from SQL Server 7.0 to SQL Server 2000) or installing additional instances, you must run the Account Configuration utility to update the agent with the appropriate changes.

  • Page 89: Skip Or Include Database Files In Backups

    Skip or Include Database Files in Backups Skip or Include Database Files in Backups Effective with CA ARCserve Backup r12, there are two registry keys used to include or skip certain database files during backup jobs. Use of these keys is determined by the type of database agent you are using.
  • Page 90 Skip or Include Database Files in Backups To use the SkipDSAFiles registry key 1. When performing agent backups: HKEY_LOCAL_MACHINE\SOFTWARE\Computer Associates\CA ARCserve Backup\ClientAgent\Parameters 2. Set the registry key to Value Name: SkipDSAFiles Type: DWORD Value: 0 to back up and 1 to skip...

  • Page 91: Agent And Ca Arcserve Backup Error Messages

    Agent and CA ARCserve Backup Error Messages Agent and CA ARCserve Backup Error Messages This section explains the most common error messages for CA ARCserve Backup and the Agent for Microsoft SQL Server. Backup or Restore Operation Failed Backup or restore failed. Reason: There are a number of reasons for backup or restore failure.
  • Page 92 Agent and CA ARCserve Backup Error Messages E8535 Failed to receive data from the Client Agent. Reason: The network connection was lost or a response was not received from the agent within the specified timeout period. A Windows error code may be embedded in the message to indicate the reason for failure.

  • Page 93: Microsoft Sql Server Error Messages

    Microsoft SQL Server Error Messages AE50009 or AE50010 Unable to sign in to Windows as specified user. Unable to sign in to Microsoft SQL Server as specified user. Reason: CA ARCserve Backup may have failed to connect to the Agent for Microsoft SQL Server for any of the following reasons: Machine authentication failure may have occurred.
  • Page 94 Microsoft SQL Server Error Messages 3023 Backup and file manipulation operations on a database must be serialized. Reason: An attempt was made to back up or restore a database while another backup or restore operation was in progress on that database. Action: Close all programs that might be accessing the database, including the SQL Server Enterprise Manager.

  • Page 95: Limitations Of Microsoft Sql Server Database

    Replication of Microsoft SQL Server 4305 or 4326 The log in this backup set terminates at …, which is too early to apply to the database. Reason: An attempt was made to restore transaction logs out of order, with an older log being restored after a newer one or an attempt was made to restore a transaction log after a more recent backup.

  • Page 96: Configure Agent Behavior For Databases Ineligible For Backup

    Configure Agent Behavior for Databases Ineligible for Backup Configure Agent Behavior for Databases Ineligible for Backup The Agent for Microsoft SQL Server has a pre-defined set of rules that governs how databases ineligible for backup are recognized and handled. Backup eligibility is determined by database status and other properties.
  • Page 97 Configure Agent Behavior for Databases Ineligible for Backup Database Status If Database is If Whole Instance is Selected Selected Explicit Implicit Recovering (in the middle Message Type: Error Message Type: Error of processing restored Job Result: Failure Job Result: Failure data) Setting Name: Setting Name: Restoring...

  • Page 98: Additional Database Status Considerations

    Microsoft SQL Server Disaster Recovery Additional Database Status Considerations Database Status -- Mirror When the entire instance is selected, Mirror databases do not appear on the database list, and are ignored. For a Mirror database to be explicitly selected for backup, it would have been selected while it was the Principal (Active) member of the Mirroring partnership, and entered the Mirror state due to a subsequent fail-over.
  • Page 99 Microsoft SQL Server Disaster Recovery Potential Restore Problems The master database tracks all of the resources allocated to Microsoft SQL Server. If you do not perform an offline backup after you have made a major change in the Microsoft SQL Server configuration, restore problems can occur. For example, for a Microsoft SQL Server configuration with five databases in addition to the master database, you back up the master database, drop one database (detach it from Microsoft SQL Server) and delete the files that make it...

  • Page 100: Disaster Recovery Scenario

    Microsoft SQL Server Disaster Recovery Disaster Recovery Scenario A typical disaster recovery scenario consists of the following steps: 1. Reinstall Windows, if necessary. 2. Reinstall CA ARCserve Backup, if necessary. 3. Reinstall the Agent for Microsoft SQL Server and the Client Agent for Windows, if necessary.

  • Page 101: Appendix B: Configuring Microsoft Sql Server Security Settings

    Appendix B: Configuring Microsoft SQL Server Security Settings This appendix explains how to configure Microsoft SQL Server security settings for CA ARCserve Backup. This section contains the following topics: Types of Microsoft SQL Server Authentication (see page 101) Authentication Requirements (see page 101) How User Authentication Is Changed (see page 102)

  • Page 102: How User Authentication Is Changed

    How User Authentication Is Changed How User Authentication Is Changed Regardless of the authentication option you choose, you must configure the Agent and confirm that the settings in Windows are configured to match. In addition, if you change the option, you must update any existing backup jobs to reflect the change.

  • Page 103: Update The Agent Account Configuration

    How User Authentication Is Changed To check or change the Microsoft SQL Server authentication method for SQL Server 2005 and 2008 1. On the system where Microsoft SQL Server is running, open the SQL Server Management Studio. 2. Connect to the instance of Microsoft SQL Server that you want to change. 3.

  • Page 104: Check And Change The Odbc Settings

    How User Authentication Is Changed Check and Change the ODBC Settings To check and change the ODBC settings 1. On the system where Microsoft SQL Server is running, from the Start Menu, select Control Panel (if necessary) and select Administrative Tools. 2.

  • Page 105: Update The Backup Manager

    How User Authentication Is Changed The SQL Server ODBC Data Source Test dialog opens. After a few seconds, the dialog displays the results of a quick connection test: If the Microsoft SQL Server ODBC Data Source Test dialog reports that ■...

  • Page 107: Appendix C: Backup And Recovery Best Practices

    Appendix C: Backup and Recovery Best Practices Data loss can be limited to a file on a single disk drive or encompass your entire data center. Ideally, you should consider a strategy that protects each database you maintain. Consider database size and activity as well as business importance as you design your strategy.

  • Page 108: Microsoft Sql Server Database Basics

    Microsoft SQL Server Database Basics Microsoft SQL Server Database Basics To achieve optimal results using CA ARCserve Backup to back up your Microsoft SQL Server databases, the following database fundamentals are provided. A database is a collection of tables, which are comprised of rows or records. Each row is made up of columns that contain some sort of structured information about a record.
  • Page 109 Microsoft SQL Server Database Basics Example The following diagram illustrates a database with six user-defined Secondary Data Files (.ndf) grouped in two user-defined FileGroups and stored on three separate disks. You can create a table on each FileGroup so that any queries against the data in a table can then be allocated across the three disks in parallel, to improve performance.
  • Page 110 Microsoft SQL Server Database Basics Full-Text Search Catalogs With SQL Server 2005, Microsoft added full-text search enhancements that let you back up and restore one or more full-text catalogs. You can now backup catalogs with, or separate from, your database data. A database can hold one or many full-text catalogs, but a catalog can only belong to one database.

  • Page 111: Performance Improvement Tips

    Microsoft SQL Server Database Basics Performance Improvement Tips Consider the physical layout of your database to take advantage of the way files and FileGroups and partial backups/restores can optimize your database performance. ■ If you separate tables with high traffic estimates from tables with less expected traffic by placing them into different FileGroups, you can store the high-traffic table on high-performance disks and store the other files in another FileGroup on different disks.
  • Page 112 Microsoft SQL Server Database Basics Partitioning In SQL Server 2005, Microsoft introduced Partitioning, a method that makes large data sets easier to manage by limiting how much data is read during a single query. Partitioned tables can be divided among more than one FileGroup in a database.

  • Page 113: Recovery Models

    Microsoft SQL Server Database Basics Recovery Models The SQL Server recovery model is a decision that manages the risk of lost information in case of a disaster by controlling the level of transaction log involvement. You may change recovery models on a per-database basis to help you manage database maintenance tasks.

  • Page 114: System Databases

    Microsoft SQL Server Database Basics For more information about File and FileGroup Backups, see Files and FileGroup Backups. (see page 121) For more information about Partial Database backups, Partial Backups (see page 122). System Databases You can use CA ARCserve Backup to manage the protection and recovery of SQL Server system databases: master database The master database stores all system-level information for a SQL Server...

  • Page 115: Backup And Restore Considerations In Microsoft Sql Server Cluster Environments

    Backup Concepts Backup and Restore Considerations in Microsoft SQL Server Cluster Environments CA ARCserve Backup supports clustered Microsoft SQL Server in the Microsoft Clustering Server (MSCS) environment. Use CA ARCserve Backup and the Agent for Microsoft SQL Server to back up and restore clustered Microsoft SQL Servers just like any nonclustered instance of Microsoft SQL Server, with the following important differences: ■...

  • Page 116: Backup Considerations

    Backup Concepts Backup Considerations You should back up a database immediately after you create it and continue to back it up on a regular schedule to ensure smooth recovery from a database or media failure. Maintain regular backups of all databases, including: ■...
  • Page 117 Backup Concepts ■ Changed the arrangement of files among the FileGroups ■ Changed the arrangement of tables among the FileGroups ■ Changed the partition scheme of a Partitioned Table or Index ■ Canceled a full backup job while it is running ■...
  • Page 118 Backup Concepts ■ If your database activity is high for a large size database using the Full or Bulk-Logged Recovery model, we recommend the following pattern: – Full backup: once per week – Differential backup: once per day – Transaction Log backup: every 20 minutes ■...
  • Page 119 Backup Concepts Differential Backups A differential backup records only the data that has changed since the last full backup of the same part of the data/same data files/same database subset. Usually, these backups are smaller and faster than full backups, but larger and longer than Transaction log backups.
  • Page 120 Backup Concepts Transaction Log Backups Transaction logs record Microsoft SQL Server database activity. When using the Full or Bulk-Logged Recovery Models, they should be backed up frequently. To back them up, run self-contained Transaction log backups separately from database backups. Transaction log backups offer the following advantages over other types of backups: ■...
  • Page 121 Backup Concepts Truncate Transaction Logs You can truncate Transaction logs when you back them up. To truncate a Transaction log, select the Remove inactive entries from transaction log option when you configure the backup. If the Transaction log is not truncated, it may eventually grow large.
  • Page 122 Backup Concepts How the Create Index Statement Impacts File and FileGroup Backups The Backup statement requires that you back up entire FileGroups affected by a Create Index statement. This requirement exists in the following situations: ■ If you create an index on a FileGroup, you must back up that entire FileGroup in a single backup operation.

  • Page 123: Restore Overview

    Restore Overview Note: When using the Simple Recovery Model, you cannot perform a Database Differential backup after a Partial Full backup, until you first perform another Database Full backup. For all recovery models, if you perform a Partial Full backup after a Database Differential backup, the Partial Full backup will be dependent on the Database Differential backup as a pre-requisite.

  • Page 124: Restore Types And Methods

    Restore Overview Microsoft SQL Server locks a database while restoring it, so that the database cannot be modified during the restore operation. However, users can access and modify other Microsoft SQL Server databases during this time. Note: If a restore is attempted when you are accessing a database, Microsoft SQL Server will not allow the restore operation.

  • Page 125: Checklists For Dependencies, By Type

    Restore Overview For any type of restore operation, you can use the following restore methods: ■ Restore by Tree: This option displays a tree of the computers and objects backed up by CA ARCserve Backup. To run a restore operation, expand the appropriate computers and instances to select the databases you want to restore.
  • Page 126 Restore Overview Transaction Log Restore Dependency Checklist A Transaction Log Restore restores and processes the Transaction Log contents, a process also known as "applying" or "replaying" the logs. Microsoft SQL Server re-executes the changes contained in the log and rolls back any transactions that were uncommitted when you backed up the Transaction Log.
  • Page 127 Restore Overview Files and FileGroups Restore Dependency Checklist-MSSQLSvrWSPW A Files and FileGroups Restore restores and recovers selected files and FileGroups. You can restore Files and FileGroups from a Files and FileGroups, Partial, or Database backup. A Files and FileGroups restore, like a Differential or Log restore, can only be applied to either the original database from which it was backed up, or to a copy that has never left the loading or standby state.
  • Page 128 Restore Overview Selected Session Prerequisites Post-requisites Files and FileGroups The last prior Full Backup Use one of the following: Differential Backup that contains the files All successive Transaction Log backups ■ included in the selected For more information, see All successive Transaction Log backups session Note 1 (see page 130).
  • Page 129 Restore Overview Torn Page Repair Dependency Checklist A Torn Page Restore restores only the pages of data on disk marked as damaged. SQL Server 2005 and later have the ability to isolate damaged parts of a database while leaving the rest intact. When this happens with a Full Recovery Model database, the database may be eligible for a Torn Page repair, which is much faster than a Database restore.
  • Page 130 Restore Overview Selected Session Prerequisites Post-requisites backup Files and FileGroups The last prior Full Backup that Use one of the following: Differential Backup contains the files included in All successive Transaction Log backups ■ the selected session For more information, All successive Transaction Log backups ■...

  • Page 131: Microsoft Sql Server Disaster Recovery Elements

    Restore Overview Microsoft SQL Server Disaster Recovery Elements When you backup a Microsoft SQL Server instance that includes Full Database backups of the master, model and msdb system databases, the Agent for Microsoft SQL Server will generate an additional backup session called Microsoft SQL Server Disaster Recovery Elements.

  • Page 132: Restore Master Databases

    Restore Overview Restore Master Databases Before you restore the master database, if the database files are missing, you may need to either restore Microsoft SQL Server Disaster Recovery Elements for that instance, or rebuild it using the Microsoft SQL Server Rebuild Master utility. Restoring the master database requires that the restore operation have exclusive access to the SQL Server instance.

  • Page 133: Index

    Index Backing Up Microsoft SQL Server Databases • 15, 29, 76 3023 • 94 backup 3101 • 94 actions requiring a full backup after • 116 3108 • 94 Backup Agent Options dialog • 42 Backup Manager • 42 configuring parameters • 26 4305 or 4326 •...
  • Page 134 Backup or Restore Operation Failed • 91 Database Consistency Check (DBCC) Options • Backup Overview • 29 31, 36, 46, 52 Backup Strategy Recommendations • 117 Database Consistency Check option Basic Prerequisites • 21 explained • 36 Database Consistency Checks • 117 Database File Options •...
  • Page 135 Files and FileGroups Restore Dependency Checklist-MSSQLSvrWSPW • 127 Limitations of Microsoft SQL Server Database • FILESTREAM Data • 110 Force Restore to use Named Pipes • 46, 53 load • 123 Full Backups • 17, 118 loading transaction logs sequentially • 47 Full-Text Search Catalogs •...
  • Page 136 by session using separate restore job for each session • 65 No Icon in Browse Tree • 91 by session using single restore job for each session • 64 by tree using a separate restore job for each ODBC settings, checking and changing • 104 session •...
  • Page 137 procedure • 57 Restore by Tree in Microsoft SQL Server 2000, The Master Database • 98 2005 or 2008 Cluster Environments • 77 Torn Page Repair Dependency Checklist • 129 Restore by Tree Using a Separate Job for Each transaction log Session •...

This manual is also suitable for:

Arcserve backup

Table of Contents