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

available for the data. If you use big or scalable volume groups on your system,and need to restore the whole volume including the first sector, restore the volumeto file and then copy it to a destination volume. The following dd command can beused for this purpose.dd if= of=/dev/ bs=1mRelated concepts“Performing an image restore using the command line” on page 171Use the restore image command to restore an image using the Tivoli StorageManager command line client.Related tasks“Performing an image restore using the GUI” on page 170This topic explains the procedure that you use to restore an image of your filesystem or raw logical volume.Restoring data to a GPFS file system with multiple storage poolsGPFS 3.1 and 3.2 allow you to manage your data using storage pools. A storagepool is a collection of disks or RAIDs with similar properties that are managedtogether as a group. The group under which the storage pools are managedtogether is the file system. The automated placement and management of files onthe storage pool level is done by policies. A policy is a set of rules that describesthe life cycle of user 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.1or 3.2 file system are distributed over different storage pools, depending on theenabled placement and migration policies.During restore, the files are placed on the correct storage pool. Tivoli StorageManager is not aware of pool-to-pool migrations, so the files are placed on thestorage pool from where the backup has taken place. The policy engine replacesthe files based on migration policies.GPFS 3.1 handles the placement of files after a restore as follows:v The file is placed according to the storage pool ID that is stored in the extendedattributesv The file is placed based on the current placement policyv The file is placed in the system poolIf a storage pool ID is stored in the extended attributes of the file, and that storagepool is available, the file is always placed in that storage pool. If the storage poolis not available, the file is placed according to the placement policy. If theplacement policy does not match the file, the file is placed in the system pool.GPFS 3.2 handles the placement of files after a restore as follows:v The file is placed in the pool that can be selected by matching the saved fileattributes to a RESTORE rulev The file is placed in the pool that it was in when it was backed upv The file is placed based on the current placement policyv The file is placed in the system storage poolChapter 5. Restoring your data 179