DEFINE STGPOOL (Define a storage pool)

DEFINE STGPOOL (Define a storage pool)

 Use this command to define a primary storage pool, copy storage pool,

or an active-data pool. A primary storage pool provides a destination

for backup files, archive files, or files migrated from client nodes. A

copy storage pool provides a destination for backup copies of files that

are in primary storage pools. An active-data pool provides a destination

for active versions of backup data that are in primary storage pools.

All volumes in a storage pool belong to the same device class. Random

access storage pools use the DISK device type. After you define a random

access storage pool, you must define volumes for the pool to create

storage space.

Sequential access storage pools use device classes that you define for

tape devices, optical devices, files on disk (FILE device type), and

storage on another server (SERVER device type). To create storage space

in a sequential access storage pool, you must allow scratch volumes for

the pool when you define or update it, or define volumes for the pool

after you define the pool. You can also do both.

The DEFINE STGPOOL command takes four forms:

*  Defining a primary storage pool assigned to random access devices

*  Defining a primary storage pool assigned to sequential access devices

*  Defining a copy storage pool (always assigned to sequential access

   devices)

*  Defining an active-data pool (always assigned to sequential access

   devices)

 The syntax and parameters for each form are defined separately.

CANCEL EXPIRATION (Cancel an expiration process)

CANCEL EXPIRATION (Cancel an expiration process)

Use this command to cancel a process that is running as a result of an

inventory expiration operation.

 

Privilege class

To issue this command, you must have system privilege.

 

Syntax

>>-CANcel EXPIration-------------------------------------------><

 

Examples

Task

Cancel the process that was generated by an inventory expiration

operation.

Command  cancel expiration

Restoring a database to a point-in-time -- volume history file unavailable

Restoring a database to a point-in-time -- volume history file unavailable

If the volume history file is unavailable, you can use one or more

DSMSERV RESTORE DB commands to restore the database to a specific point

in time. A device configuration file with the applicable device

information must also be available, or you must manually create one.

For example, to load a full backup and one or more incremental backups,

issue a DSMSERV RESTORE DB command for the full backup and an additional

DSMSERV RESTORE DB command for each incremental backup. When you use

multiple DSMSERV RESTORE DB commands, specify COMMIT=NO for each command

except the last one. For the last command, specify COMMIT=YES. The

database remains in an inconsistent and unusable state until you issue a

DSMSERV RESTORE DB command with a COMMIT=YES.

To manually create a device configuration file with the applicable

device information (library, drive, and device class definitions) see

the Administrator's Guide).

Full and incremental database backups or snapshot database backups can

be used to restore a database to a point in time.

To restore the database using snapshot backup volumes, you must:

1. Specify all the volume names for the same snapshot backup series

2. List the volumes in the sequence in which the backup was written

3. Specify COMMIT=YES

Note:

      1. If you issue a DSMSERV RESTORE DB command with COMMIT=NO, and

         you decide not to load another incremental backup, reissue the

         last DSMSERV RESTORE DB command with COMMIT=YES.

      2. If you issue a DSMSERV RESTORE DB command with COMMIT=YES, and

         you decide to load an additional incremental backup, reissue

         all the DSMSERV RESTORE DB commands in order with COMMIT=NO on

         each. Then, enter any additional DSMSERV RESTORE DB commands,

         with COMMIT=YES on the last one.

Syntax

>>-DSMSERV RESTORE DB--DEVclass--=--device_class_name----------->

                     .-,-----------.     

                     V             |     

>--VOLumenames--=--+--volume_name-+-+------------------------>

                   '-FILE:--file_name-'  

   .-COMMIT--=--No------.  

>--+-------------------+-------------------------------------><

   '-COMMIT--=--+No--+'  

                '-Yes-'    

Parameters

DEVclass (Required)

   Specifies the name of the sequential access device class to use. The

   device class must be defined in a device configuration file. If a

   device configuration file is not available, you can manually create

   one (see the Administrator's Guide).

   Note:

         1. You cannot use a device class with a device type of NAS.

         2. A restore database operation fails if the source for the

            restore is a FILE library. A FILE library is created if the

            device class specifies SHARED=YES.

VOLumenames (Required)

   Specifies the backup volumes to use to restore the database. Possible

   values are:

   volume_name

      Specifies the names of the volumes. To specify multiple volumes,

      separate the names with commas and without intervening spaces.

      List the volumes in the order in which they were written.

   FILE:file_name

      Specifies the name of a file that contains a list of the volumes.

      Enter the volumes in the order in which they were written with

      each name on a separate line.

COMMIT

   Specifies whether this is the last restore command needed to restore

   the database. This parameter is optional. The default value is NO.

   Possible values are:

   No

      Specifies that you will issue one or more additional DSMSERV

      RESTORE DB commands.

   Yes

      Specifies that this is the last restore command to restore the

      database.

Examples

Task 1

Restore the database to the time of its most recent incremental backup.

The volume history file is not available. Tape volumes FULL1, FULL2,

INCR1, and INCR2 contain the database backup series.

Commands

dsmserv restore db devclass=tape volumenames=full1,full2 commit=no

dsmserv restore db devclass=tape volumenames=incr1 commit=no

dsmserv restore db devclass=tape volumenames=incr2 commit=yes

Task 2

Restore a database to the time of its most recent snapshot backup. The

volume history file is not available. Tape volumes TAPE01 and TAPE02 are

snapshot volume names in a volume sequence that spans two tapes.

Command

dsmserv restore db devclass=8MM volumenames=tape01,tape01 commit=yes

BACKUP DB (Back up the database)

BACKUP DB (Back up the database)

Use this command to back up a Tivoli Storage Manager database to

sequential access volumes.

To determine how much additional storage space a backup will require,

use the QUERY DB command. That command displays the database pages, in

megabytes, that have changed since the last backup.

Privilege class

To issue this command, you must have system privilege or unrestricted

storage privilege.

Syntax

>>-BAckup DB--DEVclass--=--device_class_name-------------------->

   .-Type--=--Incremental-----.  

>--+--------------------------+--------------------------------->

   '-Type--=--+-Incremental-+-'  

              +-Full--------+    

              '-DBSnapshot--'    

>--+-------------------------------------+---------------------->

   |                   .-,-----------.   |  

   |                   V             |   |  

   '-VOLumenames--=--+---volume_name-+-+-'  

                     '-FILE: file_name-'    

   .-Scratch--=--Yes-----.  .-Wait--=--No------.  

>--+---------------------+--+------------------+---------------><

   '-Scratch--=--+-Yes-+-'  '-Wait--=--+-No--+-'  

                 '-No--'               '-Yes-'    

Parameters

DEVclass (Required)

   Specifies the name of the sequential access device class to use for

   the backup.

   Note:

         1. You cannot use a device class with a device type of NAS or

            CENTERA.

         2. A restore database operation will fail if the source for the

            restore is a FILE library. A FILE library is created if the

            FILE device class specifies SHARED=YES.

   

   If all drives for this device class are busy when the backup runs,

   Tivoli Storage Manager cancels lower priority operations, such as

   reclamation, to make a drive available for the backup.

Type

   Specifies the type of backup to run. This parameter is optional. The

   default is INCREMENTAL. Possible values are:

   Incremental

      Specifies that you want to run an incremental backup of the Tivoli

      Storage Manager database. The maximum number of incremental

      backups you can run between full backups is 32.

   Full

      Specifies that you want to run a full backup of the Tivoli Storage

      Manager database.

   DBSnapshot

      Specifies that you want to run a full snapshot database backup.

      The entire contents of a database are copied and a new snapshot

      database backup is created without interrupting the existing full

      and incremental backup series for the database.

VOLumenames

   

   Specifies the volumes used to back up the database. This parameter is

   optional. However, if you specify SCRATCH=NO, you must specify a list

   of volumes.

   

   volume_name

      Specifies the volumes used to back up the database. Specify

      multiple volumes by separating the names with commas and no

      intervening spaces.

   FILE:filename

      Specifies the name of a file that contains a list of volumes used

      to back up the database. Each volume name must be on a separate

      line. Blank lines and comment lines, which begin with an asterisk,

      are ignored.

      For example, to use volumes DB0001, DB0002, and DB0003, create a

      file named TAPEVOL.DATA that contains these lines:

      DB0001

      DB0002

      DB0003

      

      You can then specify the volumes for the command as follows:

      VOLUMENAMES=FILE:TAPEVOL.DATA

Scratch

   Specifies whether scratch volumes can be used for the backup. This

   parameter is optional. The default is YES. Possible values are:

   Yes

      Specifies that scratch volumes can be used.

      If you specify SCRATCH=YES and the VOLUMENAMES parameter, Tivoli

      Storage Manager will only use scratch volumes if space is

      unavailable on the specified volumes.

      

      If you do not include a list of volumes by using the VOLUMENAMES

      parameter, you must either specify SCRATCH=YES or use the default.

   No

      Specifies that scratch volumes cannot be used.

      If you specify volumes by using the VOLUMENAMES parameter and

      SCRATCH=NO, the backup will fail if there is not enough space

      available to store the backup data on the specified volumes.

Wait

   Specifies whether to wait for the server to complete processing this

   command in the foreground. The default is NO. Possible values are:

   No

      Specifies that the server processes this command in the

      background. You can continue with other tasks while the command is

      being processed. Messages created from the background process are

      displayed either in the activity log or the server console,

      depending on where messages are logged.

      To cancel a background process, use the CANCEL PROCESS command. If

      a BACKUP DB background process is canceled, some of the database

      may have already been backed up before the cancellation.

   Yes

      Specifies that the server processes this command in the

      foreground. Wait for the command to complete before continuing

      with other tasks. The server then displays the output messages to

      the administrative client when the command completes.

      Note: You cannot specify Wait=Yes from the server console.

 

Examples

Task

Run an incremental backup of the database using a scratch volume. Assume

a device class of FILE for the backup.

Command  backup db devclass=file type=incremental