La novela moderna, el canon occidental y la obra de Luisa Carnés

When a data object is sent, the TSM server places the copy of the client data out on TSM pre-allocated storage (in a storage pool) and records information in its own internal database describing the object. This description includes such things as the node name, filespace name, high level qualifier, low level qualifier, management class. This information is stored in a TSM internal table that can be queried using an SQL select statement. For backup objects, you can run the command, select * from backups. For archive objects you use the command, select * from archives. Both commands are run using the TSM Administrative command line program (^dsmadmc).

4.5.2.1 Viewing the description of a backup object

Information about each backup object is stored in a TSM internal database table named backups. You can use an SQL selectstatement to view the entries in this table. We will restrict the output of the select command by nodename. Before running this command, we did an Oracle RMAN backup of a database using Tivoli Storage Manager.

After taking the backup we ran the SQL query select * from backups where node_name=’JAMAICA_ORACLE’. The entry in the quotes is case sensitive and must be upper case. The output of this command tells us that the backup object was sent by a client program (TDP Oracle) that authenticated with the TSM server as node JAMAICA_ORACLE. The client program did not specify which management class to use with this object so the TSM server bound the default management class for the node to this backup object. TDP for Oracle for Windows uses ^\adsmorc as the FILESPACE_NAME when sending the object to the TSM server. The HL_NAME or high level qualifier is \orcnt\. For the LL_NAME or low level qualifier, TSM uses the piece name that is

automatically generated by RMAN. The LL_NAME can be controlled by using the ^format option in the RMAN script.

4.5.2.2 Viewing the description of an archive object

TDP for Oracle does not store any database objects as archive objects on the TSM server. You could use the TSM backup-archive client archive feature to perform an operating system or file level backup of the Oracle database files.

The archive feature does not perform versioning, but keeps all objects under an archive description.

RMAN> run{

2> allocate channel t1 type 'sbt_tape';

3> backup (database);

4> } ...

RMAN-08503: piece handle=0ncm82dr_1_1 comment=API Version 1.1,MMS Version 2.1.10 .0

RMAN-08525: backup set complete, elapsed time: 00:02:48 RMAN-08031: released channel: t1

tsm: BRAZIL>select * from backups where node_name='JAMAICA_ORACLE'

ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute.

Do you wish to proceed? (Yes (Y)/No (N)) y

Chapter 4. TSM server considerations 39 Information about each archive object is stored in a TSM internal database table named archives. You can use an SQL select statement to view the entries in this table. Here is an example of such a query: select * from archives where node_name=’JAMAICA’. The entry in the quotes is case sensitive and must be upper case. Prior to running this command, we used the

backup-archive client to archive the tnsnames.ora file.

4.5.2.3 Differences between backup and archive objects

Based on the output of the SQL commands for backup and archive objects, you can see that there are some similarities and some differences.

The backups table contains two fields that the archives table does not:

STATE and DEACTIVATE_DATE. These two fields are used in implementing versioning which is specific to backup objects. The STATE field can be either ACTIVE_VERSION or INACTIVE_VERSION. When the backup object is inactivated, the STATE changes to INACTIVE_VERSION and a timestamp when this occurred is placed in the DEACTIVATE_DATE field.

The archives table contains one field that the backups table does not:

DESCRIPTION. The DESCRIPTION field is used to group archive objects logically together. For example, the TSM backup-archive client GUI uses this field for the retrieve operation to group archive objects that were backed up with similar descriptions.

4.5.2.4 Owner field in backups and archives tables

Both the backups and archives tables have an OWNER field for each data object. This is used for client data sent from a UNIX operating system. For files and directories the OWNER corresponds to the UNIX security owner for the file or directory. For API data this field normally comes from the UNIX user that is used to perform the backup.

tsm: BRAZIL>select * from archives where node_name='JAMAICA' and type='FILE' ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute.

Do you wish to proceed? (Yes (Y)/No (N)) y

Only the owner of the data object or a root user can access data objects on a TSM server. In our example in the prior section, the OWNER field is blank.

This is because the backup was done on a Windows operating system that does not use this field.

Oracle backups and restores source the OWNER value from the user performing the backup or restore. This plays an important role when doing redirected restores.