• No results found

Learn about prerequisite information before installing Data Protection for SQL and review the installation instructions.

Quick installation and configuration

Install and set up Data Protection for SQL to help you start protecting your SQL server data as quickly as possible.

Follow these instructions to quickly install, configure, verify, and customize Data Protection for SQL:

1. Install Data Protection for SQL. a. Log on as an administrator.

a. Insert the IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server product DVD into your DVD drive. If autorun is enabled, the setup wizard starts automatically when the DVD loads. Otherwise, clickStart>Run, and at the prompt, specify: x:\setupfcm.exe, wherex:is your DVD drive. ClickOK.

b. Follow the installation instructions that are displayed on the screen. c. If prompted, restart your system before the installation completes. d. ClickFinishto complete the installation of Data Protection for SQL. e. If you plan to use VSS operations, you must install the most recent version

of the Tivoli Storage Manager backup-archive client. The backup-archive client is also the VSS Requestor and is available separately.

2. Configure Data Protection for SQL.

a. Start the Management Console (MMC GUI) by clickingStart>All

Programs>Tivoli Storage Manager>Data Protection for Microsoft SQL Server>DP for SQL Management Console. If you have not previously configured Data Protection for SQL, the Tivoli Storage Manager

configuration wizard starts automatically.

b. If the Tivoli Storage Manager configuration wizard does not start

automatically, clickManage>Configuration>Wizardsin the tree view, select the wizard, and clickStartin the Actions pane.

c. Complete the following pages of the wizard:

Data Protection Selection

SelectSQL Serveras the application to protect.

Requirements Check

Click anyFailedorWarningslinks for help on resolving potential issues.

TSM Node Names

Enter the Data Protection for SQL Tivoli Storage Manager node name. If you are using VSS, enter the VSS Requestor node name.

TSM Server Settings

Specify the Tivoli Storage Manager server address, and choose whether to have the wizard configure the Tivoli Storage Manager server.

Custom Configuration

ClickDefault in most situations, or clickCustomto enter all service related information.

TSM Configuration

Wait for all components to be provisioned and configured. Click

Re-runif there are any problems. Click theFailedorWarnings link for more information if any problems remain.

Completion

This page shows the status of the configuration. If you are using Windows Server 2008 or later, and you plan to use VSS operations, check theVSS Diagnosticscheck box to begin VSS verification.

Important: If you did not choose to have the wizard configure the Tivoli Storage Manager server, the Tivoli Storage Manager administrator must configure the Tivoli Storage Manager server before verification can be done. If the wizard does not configure the Tivoli Storage Manager server, it provides a link to a macro that can be provided to the Tivoli Storage Manager administrator as an example of one way to configure the Tivoli Storage Manager server.

3. Verify the configuration.

a. If you are using VSS operations on Windows Server 2008 or later, verify that VSS is working correctly.

If theVSS Diagnosticscheck box was selected at the completion of the configuration wizard, the VSS Diagnostics wizard is displayed. You can also start this wizard by clickingManage>Diagnostics, and clickingVSS Diagnosticsin the Actions pane.

Attention: Do not run these tests if you are already using SAN Volume Controller or Storwize V7000 space-efficient snapshots on your computer. Doing so can result in the removal of previously existing snapshots. Complete the following pages in the VSS Diagnostics wizard:

Snapshot Volume Selection

Select the volumes that you want to test and review the VSS provider and writer information.

VSS Snapshot Tests

Review event log entries that are logged as the persistent and non-persistent snapshots are taken, and resolve any errors.

Completion

Review the test status and clickFinish.

b. Verify that Data Protection for SQL is configured properly:

1) Click theAutomate tab to open the integrated command-line interface. 2) At the bottom part of the window, click the Open folder icon, and select

theverify_sql.txtfile. Then clickOpen.

3) These commands are displayed in the command-line panel:

query tdp query tsm query sql

With the cursor in the command-line panel, pressEnterto run the commands to verify your configuration. The configuration is verified when these commands run without warnings or errors.

4) When verification is complete, you can use Data Protection for SQL to back up are restore SQL server data.

5) Back up and restore a set of test data. 4. Customize Data Protection for SQL.

After Data Protection for SQL is configured and verified successfully, customize your settings by defining your policy settings and scheduled operations to ensure that your business requirements are satisfied.

For detail informations about the installation and configuration procedures, or if you want to perform these tasks manually, see Chapter 3, “Installing Data Protection for SQL Server,” on page 45 and Chapter 4, “Configuring Data Protection for SQL,” on page 61.

Related concepts

“Managing policy” on page 75

Installation prerequisites

Before you install IBM Tivoli Storage Manager for Databases: Data Protection for SQL, ensure that your system meets the minimum hardware, software, and operating system requirements.

The following sections provide an overview of the minimum hardware and software requirements for the V6.3 release of Data Protection for SQL.

Details of the hardware and software requirements for Data Protection for SQL can evolve over time due to maintenance updates and the addition of operating system, application, and other software currency support.

For the most current requirements, review the Hardware and Software

Requirements technote that is associated with your level of your Data Protection for SQL program. This technote is available in the All Requirement Documents website at http://www.ibm.com/support/docview.wss?uid=swg21218747. When you are at the website, follow the link to the requirements technote for your specific release or update level.

Minimum hardware requirements

Before installing Data Protection for SQL, ensure that your system meets the minimum hardware requirements.

The hardware required to install Data Protection for SQL is listed in this section:

Hardware for an x86 platform

Compatible hardware supported by the Windows operating system and SQL Server in use.

Hardware for an x64 platform

Compatible hardware supported by the Windows operating system and SQL Server in use.

Minimum software and operating system requirements

Before installing Data Protection for SQL, ensure that your system meets the minimum software and operating requirements.

The operating systems supported for the x86 platform are listed in this section: v 32-bit Windows Server 2003 SP2, or later Service Pack levels: Standard,

Enterprise, or Data Center editions

v 32-bit Windows Server 2003 R2 SP2, or later Service Pack levels: Standard, Enterprise, or Data Center editions

v 32-bit Windows Server 2008 SP2, or later Service Pack levels: Standard, Enterprise, or Data Center editions.

The operating systems supported for the x64 platform are listed:

v 64-bit Windows Server 2003 SP2, or later Service Pack levels: Standard x64, Enterprise x64, or Data Center x64 editions

v 64-bit Windows Server 2003 R2 SP2, or later Service Pack levels: Standard x64, Enterprise x64, or Data Center x64 editions

v 64-bit Windows Server 2008 SP2, or later Service Pack levels: Standard x64, Enterprise x64, or Data Center x64, editions

v 64-bit Windows Server 2008 R2, or later Service Pack levels: Standard x64, Enterprise x64, or Data Center x64 editions

Additional operating environments that are supported are listed in this section: v Microsoft Cluster Server (MSCS) and Windows Failover Clustering

v Veritas Cluster Server (VCS) environments.

Microsoft SQL levels supported that are supported for x86 platforms are listed in this section:

v Microsoft SQL Server 2005 SP3, or later Service Pack levels: Standard or Enterprise editions

v Microsoft SQL Server 2008 SP1, or later Service Pack levels: Standard or Enterprise editions

v Microsoft SQL Server 2008 R2, or later Service Pack levels: Standard, Enterprise, or Data Center editions.

Microsoft SQL levels supported that are supported for x64 platforms are listed in this section:

v Microsoft SQL Server 2005 SP3, or later Service Pack levels: Standard x64 or Enterprise x64 editions

v Microsoft SQL Server 2008 SP1, or later Service Pack levels: Standard x64 or Enterprise x64 editions

v Microsoft SQL Server 2008 R2, or later Service Pack levels: Standard, Enterprise, or Data Center editions.

Virtualization support

Information for virtualization environments supported by Data Protection for SQL is available at the IBM Tivoli Storage Manager (TSM) guest support for Virtual Machines and Virtualization web page at: http://www.ibm.com/support/ docview.wss?uid=swg21239546

Install Data Protection for SQL on a local system

The setup wizard guides you through installing Data Protection for SQL.

Before you begin, verify that your environment meets the hardware and software prerequisites.

Data Protection for SQL is available in both licensed and maintenance packages. The installation process differs between these two package types.

Licensed package

Includes a license enablement file is are only available via your software distribution channel, such as Passport Advantage, and include the initial General Availability release of a product or component.

Maintenance update (fix pack or interim fix package)

Available from the maintenance delivery channel, and can sometimes be used to refresh the software distribution channel. Maintenance packages do not contain license enablement files and must be installed after a licensed package.

See theREADME.FTPfile for instructions regarding how to install a fix pack or interim fix package. TheREADME.FTPfile is available in the same directory where the maintenance package is downloaded.

Follow these instructions to install Data Protection for SQL from a DVD:

1. Install Data Protection for SQL using the setup wizard. This installs the product and any prerequisites such as the .NET Framework and Report Viewer.

a. Log on as an administrator.

b. Insert the IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server product DVD into your DVD drive. If autorun is enabled, the installation dialog starts automatically when the DVD loads. Otherwise, selectStart>Run, and at the prompt, specify: x:\setupfcm.exe, wherex:is your DVD drive, and clickOK.

c. Follow the installation instructions displayed on the screen. d. If prompted, restart your system before the installation completes. e. ClickFinishto complete the installation of Data Protection for SQL.

Note: The MMC GUI is shared among, Data Protection for Microsoft SQL Server, Data Protection for Microsoft Exchange Server, and Tivoli Storage FlashCopy Manager. If one of these products is installed in a non-default location, then the setup wizard defaults to the existing installation directory. Use the same directory when installing any of these products on the same computer. The default base directory isc:\program files\tivoli.

2. If you are installing Data Protection for SQL in a Microsoft Windows Failover Clustering environment or Veritas Cluster server environment, repeat the installation procedure on all nodes of your cluster.

3. To install additional language packs, see “Install the language packs for Data Protection for SQL.”

4. If you plan to back up and restore local snapshots or perform VSS offloaded backup operations, perform the tasks described in “Installing Tivoli Storage FlashCopy Manager.” If not, see Chapter 4, “Configuring Data Protection for SQL,” on page 61 for important configuration information.

Installing Tivoli Storage FlashCopy Manager

IBM Tivoli Storage FlashCopy Manager is a separately purchasable program that provides application-aware backups and restores by using the advanced snapshot technologies of storage system.

Install IBM Tivoli Storage FlashCopy Manager if you want to use advanced functionality with Tivoli Storage Manager such as:

v Offloaded backups

v Create and manage local (persistent) VSS snapshots v VSS Fast Restore

v VSS Instant restore v Query managed capacity

For information about how to install Tivoli Storage FlashCopy Manager, see http://publib.boulder.ibm.com/infocenter/tsminfo/v6r3/

com.ibm.itsm.fcm.win.doc/c_fcm_installing.html.

After installing Data Protection for SQL and Tivoli Storage FlashCopy Manager, see Chapter 4, “Configuring Data Protection for SQL,” on page 61 for important configuration information.

Installing Data Protection for SQL in an MSCS or VCS environment

Instructions are provided for installing the Data Protection for SQL in a cluster environment.

Installing Data Protection for SQL in a MSCS or VCS environment requires the following:

1. Install Data Protection for SQL on both nodes of your MSCS or VCS if you are installing Data Protection for SQL for a clustered SQL Server.

2. Follow the instructions in “Install Data Protection for SQL on a local system” on page 49 for all nodes of your cluster.

Install the language packs for Data Protection for SQL

Use these instructions for installing Data Protection for SQL language packs. Make sure that Data Protection for SQL has been successfully installed before attempting to install the Language Packs.

To view the MMC GUI, command-line output, and messages in a language other than English, install the language pack that you want. The language packs are executable program files located in their respective language directory on the product DVD.

Thesetupfcm.exeprogram automatically starts the setup program for the MMC language pack if installation is done on a computer with a supported language other than English.

The configuration wizard automatically provisions a language pack for any components it provisions. The following instructions describe how to install a language pack manually.

1. Insert the product DVD into the DVD drive and selectRunfrom theStart

menu.

2. Run the following commands:

Data Protection for SQL Management Console language packs

x:\fcm\aaa\mmc\3100\bbb\setup.exe

DP for SQL language packs

x:\fcm\aaa\languages\bbb\setup.exe

Wherex:is your DVD drive,aaais eitherx86 orx64, andbbbis the three-letter country code that is associated with that language.

3. Selectsetup.exe and clickOK. Follow the installation instructions contained in the prompt windows.

4. ClickFinish to complete the installation.

After installing the language pack, activate the language by updating the Data Protection for SQL configuration file (tdpsql.cfgby default) by using either of these methods:

v Use thesetcommand with thelanguageparameter to specify the language that you want. For example:

tdpsqlc set lang=fra

See the description of thelanguageparameter in “Set positional parameters” on page 223 for a list of available languages and their three-letter country codes. v Use the property pages to set the language by doing the following steps:

1. Select the SQL server instance in the tree view. 2. Click Propertiesin the Actions pane.

3. Select the Regional property page.

4. Click Regional and Language Optionsto ensure that system settings match the language that you want to use. The MMC GUI uses system language settings.

5. Select the language from the list of installed language packs. The Data Protection components use language settings from a configuration file. 6. For the best results and correct operation, select the language that matches

the system settings. ClickMatch MMC language to automatically update the language to match the system.

Installing Data Protection for SQL silently

Administrators can install Data Protection for SQL by using silent installation. A silent installation runs on its own without any intervention so that administrators are freed from the task of monitoring the installation and providing input to dialogs.

This method is especially useful when Data Protection for SQL must be installed on a number of different computers with identical hardware. For example, a company might have 25 SQL servers installed across 25 different sites. To ensure a consistent configuration and to avoid having 25 different people enter Data Protection for SQL parameters, an administrator can choose to produce an unattended installation package and make it available to the 25 sites. The

installation package can be placed on a DVD and sent to each of the remote sites, or the package can be placed on a file server for distribution to the sites.

You can perform a silent installation using one of the following methods:

Setup Program

Use thesetup command with the command-line invocation and special silent installation options.

Microsoft Installer (MSI)

Usemsiexec.exe to install the MSI package.

The following options can be used with both silent installation methods: Table 12. Silent installation options

Option Description

/i Specifies the program is to install the product.

/l*v Specifies verbose logging.

/qn Runs the installation without running the external user

interface sequence.

/s Specifies silent mode.

/v Specifies the Setup Program to pass the parameter string to the call it makes to the MSI executable program (msiexec.exe). Note the following syntax requirements when invoking the/voption:

v A backslash (\) must be placed in front of any quotation marks (" ") that reside within existing quotation marks.

v Do not include a space between the/vcommand line option and its arguments.

v Multiple parameters entered with the/vcommand

line option must be separated with a space.

v You can create a log file by specifying the directory

and filename at the end of the command. The directory must exist at the time a silent installation is performed.

/x Specifies the program is to uninstall the product.

addlocal Specifies features to install.

allusers Specifies which users can use the installation package.

installdir Specifies the directory where Data Protection for SQL is to be installed.

Table 12. Silent installation options (continued)

Option Description

reboot Specifies whether or not to prompt the user to reboot the system after silent installation.

Force Always prompts user to reboot after silent installation.

Suppress

Suppresses prompt to reboot after silent installation.

ReallySuppress

Suppresses all reboots and prompts to reboot after silent installation.

rebootyesno Specifies whether or not to reboot the system after silent installation. SpecifyYesto reboot the system after silent installation. SpecifyNonot to reboot the system after silent installation.

transform Specifies language to install.

Note: Setting therebootyesnooption toNoapplies only to the installation of the Data Protection for SQL software. The installation package includes a number of prerequisites that will be installed by Data Protection for SQL if they have not been installed as prerequisites onto the system. Ensure that all the prerequisites are installed before starting the silent installation, then set therebootyesno option to

Related documents