IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual, Page: 408 / 828

378
IBM Tivoli Storage Manager Implementation Guide
2. Back up the primary storage pools to their copy storage pool. See 6.5.3,
“Back up a storage pool” on page 248, for more information.
a. Back up the DISKDIRS storage pool to the OFFDIRS storage pool.
b. Back up the DISKDATA storage pool to the OFFDATA storage pool.
c. Back up the TAPEDATA storage pool to the OFFDATA storage pool.
3. Back up the database. See 5.8, “Database backup” on page 210, for more
information.
Since all of these commands are going to take a variable amount of time to
execute, and they should be run in sequence, it makes sense to use a server
script to run them. This will guarantee that each command will complete its tasks
before another command is started.
Defining the server script
Example 12-2 displays the commands you would use to manually accomplish the
off-site backup tasks. We can put the commands into a server script to run them
one after the other.
Example 12-2 Commands for storage pool backup
select * from sessions where upper(session_type)='NODE'
backup stgpool diskdirs offdirs wait=yes
backup stgpool diskdata offdata wait=yes
backup stgpool tapedata offdata wait=yes
backup db devclass=coffsite type=full scratch=yes
When working interactively, you would use the query session command to check
whether any clients are still backing up. If you see any clients still backing up,
you can just wait for a while and try again. However, a script cannot tell from the
output of the query session if there are any clients backing up. Instead, we use
the SQL select statement (as shown in the first line of Example 12-2) and check
its return code. If clients are still backing up, the return code is true. We can then
make the script reschedule itself for a later time. If the return code is false (that is,
no clients are backing up), we can proceed with the storage pool backups.
Example 12-3 shows the finished script for our recommended configuration. In
1.1.1, “Our support material” on page 5, we show how to load a predefined
macro into Tivoli Storage Manager. The macro mac.scripts, which we provide to
define a script to back up storage pools and the database to an off-site location,
is shown in “Define server scripts” on page 737.
Example 12-3 Contents of “REDBOOK_OFFSITE” script
/*--------------------------------------------*/
/* Script Name: REDBOOK_OFFSITE
*/
/* Description: Back up all primary storage */