You will not see a directory structure for a backupset - This is one of the
features that I do not like about backupsets - another is that it is not
automated as far as being able to reclaim the tapes back - you have to
manually keep track of it - Anyway, the following is some help on this:
Restoring Data from Backup Sets
You can restore the files that you backed up to the TSM server from backup
sets. Your TSM administrator creates backup sets from your active files on
the server.
Backup sets are written in a format that can be read directly by the client.
If a backup set is created on a device that is supported by the TSM server
and your client machine, then you can take the backup set volumes to your
client machine and restore your data directly from the locally attached
device. Alternatively, you can restore a backup set directly from the
server.
Examples of supported media devices are: tape, CD-ROM drives, removable disk
drives like JAZ drives and ZIP drives. These tape devices are supported:
DLT, 4mm, 8mm, 3590, and 3570.
Contact your TSM administrator to find out how often backup sets are created
and what devices are supported.
You might want to restore data from backup sets in these situations.
To restore your data from backup sets:
1. Click the Restore button in the Tivoli Storage Manager window. The
Restore window appears.
2. Expand the directory tree if necessary. To expand a node in the
tree, click the plus sign (+) next to an object in the tree.
3. Locate the object in the tree named Backup Sets and expand it.
4. If you want to restore the data from the backup sets on the server,
expand the Server object. If you are restoring data from a backup set on a
locally attached device, first define the backup set location, then expand
the Local object.
5. Your backup sets appear in the tree and are grouped by backup set
descriptions. Expand a backup set description to see the backup sets with
that description.
6. Click the selection box next to the backup set that you want to
restore.
7. Click the Restore button. The Restore Destination window appears.
8. Fill in the Restore Destination window, then click the Restore
button to start the restore. The Task List window appears showing the
progress of the restore.
Considerations:
· Backup sets can contain data from multiple filespaces. If you
specify a restore destination other than the original, all of the data from
all the filespaces will be restored in the specified destination.
· If you want to change the options for your restore, click the Modify
Restore Options button in the Restore Options window.
· If you want TSM to estimate the amount of time it takes to process
your files and directories, click the Estimate button. Note: The Estimated
Transfer Time field reads N/A if no files have ever been sent to or from
the current TSM server.
-----Original Message-----
From: MacDonald, David DA [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 14, 2000 10:23 PM
To: [EMAIL PROTECTED]
Subject: Backupsets appear empty on client
Hi all,
We're having some problems getting backupsets to work.
We generate the backupsets with the following server command:
generate backupset [nodename] [backupsetname] dev=3590
This process completes without any problems. We can view the contents of the
backupset from the server using the "query backupsetcontents" command. When
we go to restore from the backupset in the client, the backupsets appear
under the "Backupsets - Server" heirachy, but they are empty. No ammount of
fiddling with display or restore options seems to make any difference.
Server: TSM 3.7.3 on AIX 4.3.3
Client: Version 3.7.0 on NT4
Any suggestions as to how this is supposed to work? Am I missing something
really obvious? Any help at all would be appreciated.
Thanks,
Dave.
Unix Services
CSC TS
EOM
NOTICE - This message contains information intended only for the use of the
addressee named above. It may also be confidential and/or privileged. If
you are not the intended recipient of this message you are hereby notified
that you must not disseminate, copy or take any action in reliance on it.
If you have received this message in error please notify [EMAIL PROTECTED]