12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

further action by the client. The client merely accepts the data coming from theserver <strong>and</strong> restores it to the destination named on the restore comm<strong>and</strong>.Using the comm<strong>and</strong> line client, an example of an unrestricted wildcard comm<strong>and</strong>would be:An example of an unrestricted wildcard file specification would be:/home/mydocs/2004/*An example of a restricted wildcard file specification would be:/home/mydocs/2004/sales.*St<strong>and</strong>ard restore processThe st<strong>and</strong>ard restore process (also known as classic restore) is outlined below.1. The client queries the server <strong>for</strong> a list of files backed up <strong>for</strong> the client file spaceyou want to restore.2. The server sends a list of backed up files that match the restore criteria. If youwant to restore both active <strong>and</strong> inactive files, the server sends in<strong>for</strong>mationabout all backed up files to the client.3. The list of files returned from the server is sorted in client memory todetermine the file restore order <strong>and</strong> to minimize tape mounts required toper<strong>for</strong>m the restore.4. The client tells the server to restore file data <strong>and</strong> directory objects.5. The directories <strong>and</strong> files you want to restore are sent from the server to theclient.No query restore process1. The client tells the server that a no query restore is going to be per<strong>for</strong>med <strong>and</strong>provides the server with details about file spaces, directories, <strong>and</strong> files.2. The server sorts the data using an internal sort table which minimizes tapemounts.3. The data to be restored is sent to the client. File <strong>and</strong> directory objects stored ondisk are sent immediately since sorting <strong>for</strong> such data is not required be<strong>for</strong>erestoring it.4. You can use multiple sessions to restore the data. If the data resides on multipletapes, there are multiple mount points available at the server. The combinationof using the resourceutilization option <strong>and</strong> MAXNUMMP allows multiplesessions. See “Resourceutilization” on page 327 <strong>for</strong> more in<strong>for</strong>mation.If the restore process stops because of a power outage or network failure, theserver records the point at which this occurred. This record is known to the clientas a restartable restore. It is possible to have more than one restartable restoresession. Use the query restore comm<strong>and</strong> to find out if your client has anyrestartable restore sessions in the server database.You must complete a restartable restore be<strong>for</strong>e attempting further backups of thefile system. If you attempt to repeat the restore that was interrupted or try to backup the destination file space, the attempt will fail because you did not completethe original restore. You can restart the restore at the point of interruption byentering the restart restore comm<strong>and</strong>, or you can delete the restartable restoreusing the cancel restore comm<strong>and</strong>. If you restart the interrupted restore, it willrestart with the first transaction, which might consist of one or more files, notcompletely restored when the interruption occurred. Because of this, you mightreceive some replace prompts <strong>for</strong> files from the interrupted transaction which werealready restored.Chapter 5. Restoring your data 125

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!