tdpsql explained

TDP SQL Installation and ConfigurationJune 5th, 2009

TDP SQL Installation and ConfigurationTDP SQL Installation and Configuration

Author dave thompsonVersion 1.0Date of Creation 05-06-2009Email DT [email protected]

1

mailto:[email protected]


Change History:

Revision Date Author Comments

1.0 04-06-2009 DT TDP SQL Installation and Configuration

1.1

1.2

1.3

1.4

2


CONTENTSCONTENTS

1.1. INTRODUCTIONINTRODUCTION

2.2. INSTALLATION OF TDP SQLINSTALLATION OF TDP SQL

3.3. CONFIGURING TDP SQLCONFIGURING TDP SQL

4.4. TAKING A SQL DATABASE IN GUI AND IN CUITAKING A SQL DATABASE IN GUI AND IN CUI

5.5. RESTORATION OF SQL DATABASE IN GUI AND IN CUIRESTORATION OF SQL DATABASE IN GUI AND IN CUI

6.6. REFERENCESREFERENCES

3


1) INTRODUCTION1) INTRODUCTION

How TDP SQL Communicates SQL SERVER DATABASE to backup data to TSM SERVER?

TDP for SQL communicates with TSM using the TSM application program interface (API) and with a SQL Server using the SQL-DMO interface and the SQL-VDI (Virtual Device Interface).

TDP for SQL must be installed on the same machine as SQL Server. The TSM server may be on the same machine as SQL Server. TDP for SQL must be able to connect to a TSM server (version 3.7.4 or higher) running on any supported operating system platform. The TSM server does not need to run on Windows NT or 2000. TDP for SQL also supports operation in a Microsoft Cluster Server environment.

SQL Server Database Backup and Types

A backup creates a copy of all or part of a SQL database on TSM storage media. TDP for SQL provides selection mechanisms and the logic that are required to back up and restore SQL data. For example, when you initiate a backup operation, TDP for SQL:

1. Starts a session with a TSM server using the TSM API and information contained in a client options file. 2. Starts a session with the SQL server using the SQL-DMO interface. 3. Instructs the SQL server to begin a backup of the selected database objects. 4. Receives data from the SQL server and sends it to the TSM server. 5. Ends the TSM and SQL server sessions.

Notes:

TDP for SQL can compress SQL data before sending it to the TSM server. [compression option]

Meta Data:

When a backup is performed, TDP for SQL retains information about the SQL server and database. This information is available for query and restore operations after the backup is completed. The information about the names and sizes of the database filegroups and files is stored along with the database data, as a sub-object. This sub-object is referred to as meta data. You will need this "meta" subobject only when you need information about individual database filegroups and files.

TDP for SQL offers an expanded range of backup types beyond full and log backups which allow greater flexibility when you do not want to backup an entire database, or when it is not practical to do so due to available backup time or performance requirements. TDP for SQL provides six types of backup:

Full database backup TDP for SQL backs up an entire SQL server database and the portion of the transaction log necessary to provide a consistent database state. With both full and differential backups, the copy includes enough information from any associated transaction logs to make a backup consistent with itself. The

4

http://publib.boulder.ibm.com/tividd/td/DPSQLN/SH26-4111-01/en_US/HTML/ab5m1m02.htm#ToC_25


portion of the log included contains only the transactions that occur from the beginning of the backup until its completion.

Note: You do not have to do a full backup to constitute the equivalent of a full backup. Backing up all the groups or files in a database as well as its log are recognized as a full backup by SQL. A base backup may be a full, group, file, or set.

Differential backup TDP for SQL backs up only the data pages in a SQL server database changed since the last full backup and a portion of the transaction log.

Log backup TDP for SQL backs up only the contents of a SQL server database transaction log since the last successful log backup. To do the first log backup, you need to have done a full backup or its equivalent first. Log backups normally follow full backups. The portion of the log included in full and differential backups is not equivalent to a log backup. Additionally, in full and diff backups, the log is not truncated as it is during a log backup. However, a log backup following a full or differential backup will include the same transactions as a full or differential. Log backups are not cumulative as are differential; they must be applied against a base backup and in the correct order.

Note: A log backup in SQL terms is not equivalent to an incremental backup in TSM terms.

File backup TDP for SQL backs up only the contents of a specified SQL server logical file. This can ease the scheduling for backing up very large databases by allowing you to back up different sets of files during different scheduled backups. File, group, and set backups must be followed by a log backup, but a full is not required.

Group backup TDP for SQL backs up only the contents of a specified SQL server filegroup. This allows you to back up just the set of database tables and indexes within a specific group of files.

Set backup TDP for SQL backs up the contents of specified SQL server filegroups and files as a unit.

5


2) INSTALLING TDPSQL2) INSTALLING TDPSQL

Select the language and click OK.

Welcome to Installation wizard of TDP SQL,

6


Accept the agreement and click on NEXT,

By default it will load in following location, Click NEXT

7


Click on INSTALL to proceed with installation,

8


3)3) CONFIGURING TDP SQLCONFIGURING TDP SQL

After completion of Installation go to “c:\Program Files\Tivoli\TSM\TDPSql\” and type “tdpsqlc”

9


Since we have not copied the license file, we will get the above ERROR ACo0053E. Copy the license file in the same location.

Execute the “TDPSQLC”command now; check the help of the all related commands,

10


Check the communication between the TSM SERVER and TDP SQL, using >> tdpsqlc q tsm <<

11


Since there is mismatch with API version and TDP SQL version, we have received the above error. Before installing the TDP SQL, we must need to check the BA Client version, it means that API version, and TDP SQL version. Check the README document of TDP SQL for Supported API Version.

To resolve this issue, copy the DSCENU.TXT, file from baclient directory and paste it API directory, then Execute “tdpsqlc q tsm”,

12


Since the dsm.opt file has not been updated with TCP SERVER address, NODENAME; we got this above error.

Modified the “DSM.OPT”file, with the necessary parameters.

13


Now, trigger the command “tdpsqlc q tsm”

Since we are trying to communicate with TSM SERVER for the first time, we must need to give the password. That is what the above screenshot error shows.

The easy way to store the PASSWORD locally is through GUI, open TDP SQL GUI using command “tdpsql”

From GUI, go to utilities and give “CHANGE PASSWORD”.

14


Now, trigger the command “tdpsqlc q tsm” to check the communication between TSM SERVER and TDP SQL.This command will show complete details about the domain where the SQL node is registered and TSM SERVER version etc.,

15


16


Creating a New Database in SQL-SERVER 2005, KTDB

Creating a Table,

17


18


19


4) TAKING BACKUP & RESTORING USING GUITAKING BACKUP & RESTORING USING GUI

20


21


22


23


5)5) TAKING BACKUP&RESTORE USING COMMANDLINETAKING BACKUP&RESTORE USING COMMANDLINE

24


25


6) REFERENCES6) REFERENCES

www.ibm.redbooks.comhttp://publib.boulder.ibm.com/tividd/td/DPSQLN/SH26-4111-01/en_US/HTML

26

http://publib.boulder.ibm.com/tividd/td/DPSQLN/SH26-4111-01/en_US/HTML

http://www.ibm.redbooks.com/

tdpsql explained

Documents