IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

||||||||generated prior to the name change will not match the new node name. Ensurethat the node name is the same as the node for which the backupset wasgenerated.2. The client can be used to restore a backupset on an attached device with orwithout a server connection. If the server connection fails, a prompt will appearto continue for purposes of local backupset restore. Also, the localbackupsetoption can be used to tell the client not to attempt the connection to the server.3. Certain local devices such as tape devices require device drivers to be set upprior to performing a restore. See the device manual for assistance with thistask. You will also need to know the device address in order to perform therestore.4. The following features of a backupset restore from the server are not availablewhen restoring locally:a. Image restoreb. The GUI display and restore of individual files and directories. Thecommand line can be used to restore an individual directory or file from alocal backupsetc. Application data restore if the server was migrated from the Tivoli StorageManager Express productRestoring backupsets using the command line clientThe restore backupset command restores a backupset from the server, a local file,or a local tape device. Refer to the backupsetname option on the restore and querycommands for more information.Use the location option with the restore backupset and query backupsetcommands to specify where Tivoli Storage Manager searches for a backupsetduring a query or restore operation. You can use this option to locate backupsetson the server or local files. Tapes that are generated on the server can be usedlocally by specifying the location option and either the file name or the tapedevice. Refer to the backupsetname option on the restore and query commands formore information.Use the query backupset command to query a backupset from a local file, tapedevice, or the Tivoli Storage Manager server. The query backupset commanddisplays the backupset name, generation date, retention, and description. See“Query Backupset” on page 447 for more information.|||||||||||||Restoring data to a GPFS 3.1 file system with multiple storage poolsGPFS 3.1 allows you to manage your data using storage pools. A storage pool is acollection of disks or RAIDs with similar properties that are managed together as agroup. The group under which the storage pools are managed together is the filesystem. The automated placement and management of files on the storage poollevel is done by policies. A policy is a set of rules that describes the life cycle ofuser data, based on the file’s attributes.When a file is created, the placement policy determines the initial location of thefile’s data and assigns the file to a storage pool. All data written to that file isplaced in the assigned storage pool. The management policy determines filemanagement operation, such as migration and deletion. The files within a GPFS 3.1file system are distributed over different storage pools, depending on the enabledplacement and migration policies.Chapter 5. Restoring your data 133