Restoring Tivoli Storage Manager Data - IBM Storwize V7000 Unified Problem Determination Manual

4. After you verify that the data on Site A has been replicated accurately, you can
reconfigure Site A as the primary site. Remove any replication tasks from Site B
to Site A by using the rmtask CLI command.

Restoring Tivoli Storage Manager data

The Storwize V7000 Unified system contains a Tivoli Storage Manager client that
works with your Tivoli Storage Manager server system to perform high-speed data
backup and recovery operations.
Before you begin
Before restoring a file system, determine whether a backup is running and when
backups were completed. To restore the data, perform the following steps:
Procedure
1. Determine whether a backup is running and when backups were completed by
running the lsbackup CLI command. Specify the file system.
For example, the command to display the gpfs0 file system backup listing
shows the output in the following format:# lsbackup gpfs0 Filesystem Date
Message gpfs0 20.01.2010 02:00:00.000 G0300IEFSSG0300I The filesystem
gpfs0 backup started. gpfs0 19.01.2010 06:10:00.123 G0702IEFSSG0702I The
filesystem gpfs0 backup was done successfully. gpfs0 15.01.2010
02:00:00.000 G0300IEFSSG0300I The filesystem gpfs0 backup started.
2. Restore the backup by using the startrestore CLI command. Specify a file
system name pattern.
You cannot restore two file systems at the same time; therefore, the file pattern
cannot match more than one file system name.
Use the -t option to specify a date and time in the format
"dd.MM.yyyyHH:mm:ss.SSS" to restore files as they existed at that time. If a time
is not specified, the most recently backed up versions are restored. For
example, to restore the /ibm/gpfs0/temp/* file pattern to its backed up state
as of January 19, 2010 at 12:45 PM, enter the following command:
# startrestore "/ibm/gpfs0/temp/*" -t "19.01.2010 12:45:00.000"
See the startrestore CLI command for additional command information,
default options, and file pattern examples.
Attention: The -R option overwrites files and has the potential to overwrite
newer files with older data.
3. Use the lsbackupfs CLI command to determine whether a restore is running.
The Message field displays RESTORE_RUNNING if a restore is running on a file
system.
4. Monitor the progress of the restore process by using the QUERY SESSION
command in the Tivoli Storage Manager administrative CLI client.
Run this command twice and compare the values in the Bytes Sent column of
the output. Incremental values indicate that the process is in progress; whereas,
identical values indicate that the restore process has stopped.
Note: The following error message can occur while restoring millions of files:
ANS1030E The operating system refused a TSM request for memory
allocation. 2010-07-09 15:51:54-05:00 dsmc return code: 12
Chapter 7. Recovery procedures
287