IBM Tivoli Software IBM Tivoli Software

[ | | | ]


IBM Tivoli Storage Manager for UNIX: Backup-Archive Clients Installation and User's Guide


Chapter 5. Restoring your data

Use Tivoli Storage Manager to restore backup versions of specific files, a group of files with similar names, or entire directories. Select the files you want to restore using file specification (file path, name, and extension), a directory list, or a subdirectory path to a directory and its subdirectories. UNIX socket files are skipped during restore, including socket files that were backed up with earlier versions of Tivoli Storage Manager.

All client restore procedures in this chapter also apply to the Web client, except the following:

See Starting a Web client session for information on starting the Web client.

Table 35 identifies tasks described in this chapter:

Table 35. Restore: Primary tasks

Task Page
Restoring data using the GUI "Restoring data using the GUI"
Restoring data using the command line "Restoring data using the command line"
Performing point-in-time restores "Performing point-in-time restores"
Restoring an image "Restoring an image"
Restoring data from a backup set "Restoring data from a backup set"
Restoring NAS file systems "Restoring NAS file systems"
Restoring the WebSphere Application Server (WAS) "Restoring the WebSphere Application Server (WAS)"
Authorizing another user to restore or retrieve your files "Authorizing another user to restore or retrieve your files"
Restoring or retrieving files from another client node "Restoring or retrieving files from another client node"
Restore or retrieve files to another workstation "Restore or retrieve files to another workstation"
Restoring a disk in case of disk loss "Restoring a disk in case of disk loss"
Deleting file spaces "Deleting file spaces"

Do you want to restore an active or inactive backup?

Your administrator determines how many backup versions Tivoli Storage Manager maintains for each file on your workstation. Having multiple versions of a file permits you to restore older versions if the most recent backup is damaged. The most recent backup version is the active version. Any other backup version is an inactive version. Every time Tivoli Storage Manager backs up your files, it marks the new backup version as the active backup, and the last active backup becomes an inactive backup. When the maximum number of inactive versions is reached, Tivoli Storage Manager deletes the oldest inactive version.

To restore a backup version that is inactive, you must display both active and inactive versions by clicking on the View menu-> Display active/inactive files item. To display only the active versions (the default), click on the View menu -> Display active files only item. If you try to restore more than one version at a time, only the active version is restored.

On the Tivoli Storage Manager command line, use the inactive option to display both active and inactive objects. See Inactive for more information.


Restoring data using the GUI

To restore backup versions of individual files or subdirectories:

  1. Click Restore from the main window. The Restore window appears.
  2. Expand the directory tree. Select the selection boxes next to the files or directories you want to restore. To search or filter files, click the Search icon on the tool bar.

      To search:

    1. Enter your search criteria in the Find Files (Restore) window.
    2. Click the Search button. The Matching Files (Restore) window appears.
    3. Click the selection boxes next to the files you want to restore and close the Matching Files (Restore) window.

      To filter:

    1. Enter your filter criteria in the Find Files (Restore) window.
    2. Click the Filter button. The Restore window displays the filtered files.
    3. Click the selection boxes next to the filtered files or directories you want to restore.
  3. To modify specific restore options, click the Options button. Any options you change are effective during the current session only.
  4. Click Restore. The Restore Destination window appears. Enter the information in the Restore Destination window.
  5. Click Restore. The Restore Task List window displays the restore processing status. Transfer statistics may not match the file statistics if the operation was retried due to a failure such as a communications failure or session loss. The transfer statistics will show the bytes attempted to be transferred across all command attempts.

Restoring data using the command line

Use the restore command to restore files. See Restore for more information about the restore command. Table 36 shows examples of using the restore command to restore objects from Tivoli Storage Manager server storage. See Restore for additional examples.

Table 36. Command line restore examples

Task Command Considerations
Restore the most recent backup version of the /home/monnett/h1.doc file, even if the backup is inactive. dsmc restore /home/monnett/h1.doc -latest If the file you are restoring no longer resides on your workstation, and you have run an incremental backup since deleting the file, there is no active backup of the file on the server. In this case, use the latest option to restore the most recent backup version. Tivoli Storage Manager restores the latest backup version, whether it is active or inactive. See Latest for more information.
Display a list of active and inactive backup versions of files from which you can select versions to restore. dsmc restore "/user/project/*"-pick -inactive If you try to restore both an active and inactive version of a file at the same time, only the active version is restored. See Pick and Inactive for more information.
Restore the /home/monnett/h1.doc file to its original directory. dsmc restore /home/monnett/h1.doc If you do not specify a destination, the files are restored to their original location.
Restore the /home/monnett/h1.doc file under a new name and directory. dsmc restore /home/monnett/h1.doc /home/newdoc/h2.doc None
Restore the files in the /home file system and all of its subdirectories. dsmc restore /home/ -subdir=yes When restoring a specific path and file, Tivoli Storage Manager recursively restores all subdirectories under that path, and any instances of the specified file that exist under any of those subdirectories. See Subdir for more information about the subdir option.
Restore all files in the /home/mydir directory to their state as of 1:00 PM on August 17, 2002. dsmc restore -pitd=8/17/2002 -pitt=13:00:00 /home/mydir/ See Pitdate and Pittime for more information about the pitdate and pittime options.
Restore all files from the /home/projecta directory that end with .bak to the /home/projectn/ directory. dsmc restore "/home/projecta/*.bak" /home/projectn/ If the destination is a directory, specify the delimiter (/) as the last character of the destination. If you omit the delimiter and your specified source is a directory or a file spec with a wildcard, you will receive an error. If the projectn directory does not exist, it is created.
Restore files specified in the restorelist.txt file to a different location. dsmc restore -filelist=/home/dir2/restorelist.txt /home/NewRestoreLocation/ See Filelist for more information about restoring a list of files.
Restore all members of the /virtfs/group1 group backup stored on the Tivoli Storage Manager server. dsmc restore group /virtfs/group1 See Restore Group for more information.

Performing large restore operations

If you need to restore a large number of files, you can get faster performance by using the restore command instead of the GUI. In addition, you can improve performance by entering multiple restore commands at one time.

For example, to restore all the files in your /home file system, enter:

   dsmc restore /home/ -subdir=yes -replace=all -tapeprompt=no

However, if you enter multiple commands for the directories in the /home file space, you can restore the files faster.

For example, you could enter these commands:

   dsmc restore /home/monnett/ -subdir=yes -replace=all -tapeprompt=no
   dsmc restore /home/gillis/ -subdir=yes -replace=all -tapeprompt=no
   dsmc restore /home/stewart/ -subdir=yes -replace=all -tapeprompt=no

You can also use the quiet option with the restore commands to save processing time. However, you will not receive informational messages for individual files.

Note: If you already have the appropriate values set for the subdir, replace, tapeprompt, and quiet options in your client user options file, you do not need to include those options in the commands.

When you enter multiple commands to restore your files, you must specify a unique part of the file space in each restore command. Be sure you do not use any overlapping file specifications in the commands.

To display a list of the directories in a file space, use the query backup command. For example:

   dsmc query backup -dirsonly -subdir=no /usr/

As a general rule, you can enter from two to four restore commands at one time. The maximum number you can run at one time without degrading performance depends on factors such as how much memory you have and network utilization.

The speed at which you can restore the files also depends on how many tape drives are available on the server, and whether your administrator is using collocation to keep file spaces assigned to as few volumes as possible.

For example, if /home/monnett and /home/gillis are on the same tape, the restore for /home/gillis must wait until the restore for /home/monnett is complete. However, if /home/stewart is on a different tape, and there are at least two tape drives available, the restore for /home/stewart can begin at the same time as the restore for /home/monnett.

If your administrator is using collocation, the number of sequential access media mounts required for restore operations is also reduced.

No query restore

When you enter an unrestricted wildcard source file specification on the restore command and do not specify any of the options: inactive, latest, pick, fromdate, or todate, the client uses a different method for restoring files and directories from the server. This method is called no query restore because instead of querying the server for each object to be restored, a single restore request is sent to the server. In this case, the server returns the files and directories to the client without further action by the client. The client merely accepts the data coming from the server and restores it to the destination named on the restore command.

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.*

Standard restore process

The standard restore process (also known as classic restore) and the no query restore process are outlined below.

  1. The client queries the server for a list of files backed up for the client file space you want to restore.
  2. The server sends a list of backed up files that match the restore criteria. If you want to restore both active and inactive files, the server sends information about all backed up files to the client.
  3. The list of files returned from the server is sorted in client memory to determine the file restore order and to minimize tape mounts required to perform the restore.
  4. The client tells the server to restore file data and directory objects.
  5. The directories and files you want to restore are sent from the server to the client.

No query restore process

  1. The client tells the server that a no query restore is going to be performed and provides the server with details about file spaces, directories, and files.
  2. The server sorts the data using an internal sort table which minimizes tape mounts.
  3. The data to be restored is sent to the client. File and directory objects stored on disk are sent immediately since sorting for such data is not required before restoring it.
  4. You can use multiple sessions to restore the data. If the data resides on multiple tapes, there are multiple mount points available at the server. The combination of using the resourceutilization option and MAXNUMMP allows multiple sessions. See Resourceutilization for more information.

If the restore process stops because of a power outage or network failure, the server records the point at which this occurred. This record is known to the client as a restartable restore. It is possible to have more than one restartable restore session. Use the query restore command to find out if your client has any restartable restore sessions in the server database.

You must complete a restartable restore before attempting further backups of the file system. If you attempt to repeat the restore that was interrupted or try to back up the destination file space, the attempt will fail because you did not complete the original restore. You can restart the restore at the point of interruption by entering the restart restore command, or you can delete the restartable restore using the cancel restore command. If you restart the interrupted restore, it will restart with the first transaction, which may consist of one or more files, not completely restored when the interruption occurred. Because of this, you may receive some replace prompts for files from the interrupted transaction which were already restored.

For more information on using the command line to begin restartable restores, see Restore. To perform restartable restores using the GUI, follow these steps:

  1. Click Help from the Restore window.
  2. Click Restoring Backup Versions
  3. Click Work with restartable restore sessions.

Performing point-in-time restores

Use a point-in-time restore to restore files to the state that existed at a specific date and time. A point-in-time restore can eliminate the effect of data corruption by restoring data from a time prior to known corruption, or recover a basic configuration to a prior condition.

You can perform a point-in-time restore of a file space, directory, or file. You can also perform a point-in-time restore of image backups. For more information see Backup Image.

Perform incremental backups to support a point-in-time restore. During an incremental backup, the client notifies the server when files are deleted from a client file space or directory. Selective and incremental-by-date backups do not notify the server about deleted files. Run incremental backups at a frequency consistent with possible restore requirements.

If you request a point-in-time restore with a date and time that is prior to the oldest version maintained by the Tivoli Storage Manager server, the object is not restored to your system. Files which were deleted from you workstation prior to the point-in-time specified will not be restored.

Notes:

  1. Your administrator must define copy group settings that maintain enough inactive versions of a file to guarantee that you can restore that file to a specific date and time. If enough versions are not maintained, Tivoli Storage Manager may not be able to restore all objects to the point-in-time you specify.

  2. If you delete a file or directory, the next time you run an incremental backup, the active backup version becomes inactive and the oldest versions that exceed the number specified by the versions data deleted attribute of the management class are deleted. See Chapter 8, Understanding storage management policies for more information about the versions data deleted attribute.

When performing a point-in-time restore, consider the following:

To perform a point-in-time restore using the client GUI, use the following steps:

  1. Click the Restore button in the main window. The Restore window appears.
  2. Click the Point-in-Time button from the Restore window. The Point in Time Restore window appears.
  3. Select the Use a Point-in-Time Date selection box. Select the date and time and click OK. The point in time that you specified appears in the Point in Time display field in the Restore window.
  4. Display the objects you want to restore. You can search for an object by name, filter the directory tree, or work with the directories in the directory tree.
  5. Click the selection boxes next to the objects you want to restore.
  6. Click the Restore button. The Restore Destination window displays. Enter the appropriate information.
  7. Click the Restore button to start the restore. The Restore Task List window displays the restore processing status.

Note: If there are no backup versions of a directory for the point-in-time you specify, files within that directory are not restoreable from the GUI. However, you can restore these files from the command line.

You can start point-in-time restore from the command line client using the pitdate and pittime options with the query backup and restore commands. For example, when you use the pitdate and pittime options with the query backup command, you establish the point-in-time for which file information is returned. When you use pitdate and pittime with the restore command, the date and time values you specify establish the point-in-time for which files are returned. If you specify pitdate without a pittime value, pittime defaults to 23:59:59. If you specify pittime without a pitdate value, it is ignored.


Restoring an image

Before you perform an image restore, consider the following:

Peforming an image restore using the GUI

Use the following procedure to restore an image of your file system or raw logical volume:

  1. Click Restore from the main window. The Restore window appears.
  2. Expand the directory tree.
  3. Locate the object in the tree named Image and expand it. Click the selection box next to the image you want to restore. You can obtain detailed information about the object by highlighting the object and selecting View -> File Details... from the main window or click the View File details button.
  4. (Optional) To perform an incremental image restore, click the Options button to open the Restore Options window and select the Image plus incremental directories and files option. If you want to delete inactive files from your local file system, select the Delete inactive files from local check box. Click the OK button.
  5. Click Restore. The Restore Destination window appears. The image can be restored to the volume with the mount point from which it was originally backed up. Alternatively, a different volume can be chosen for the restore location.
  6. Click the Restore button to begin the restore. The Task List window appears showing the progress of the restore. The Restore Report window displays a detailed status report.

Considerations:

Performing an image restore using the command line

Use the restore image command to restore an image using the Tivoli Storage Manager command line client. See Restore Image for more information.

You can use the verifyimage option with the restore image command to specify that you want to enable detection of bad sectors on the destination target volume. If bad sectors are detected on the target volume, Tivoli Storage Manager issues a warning message on the console and in the error log. See Verifyimage for more information.

If bad sectors are present on the target volume, you can use the imagetofile option with the restore image command to specify that you want to restore the source image to a file. Later, you can use a 'dd' utility (available on Unix) or its equivalent to copy data from this file to a logical volume. See Imagetofile for more information.


Restoring data from a backup set

Your Tivoli Storage Manager administrator can generate a backup set (a collection of your active files that reside on the server) onto portable media created on a device using a format that is compatible with the client device.

It is possible to generate a backup set as a number of special files if the device class the Tivoli Storage Manager administrator specifies when creating it is file. These files can be stored locally (on the client) to provide more restore flexibility.

WAS and group backups can also be added to a backup set. See Group backup: Backing up files from one or more file spaces for more information about group backups. See Backing up the WebSphere Application Server (WAS) for more information about WAS backups.

Portable media can be used on devices such as a tape, CD-ROM, DVD, and Iomega JAZ or ZIP drives. Current device support information is available at the following Web site:

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

You can restore backup sets from the following locations:

Backup sets can provide you with instant archive and rapid recovery capability as described below:

Instant archive
This capability allows an administrator to create an archive collection from backup versions already stored on the server.

Rapid recovery
When you are away from your office without a network connection and you lose data, you can restore the data from the backup set.

Notes:

  1. If you cannot restore a backup set from portable media, check with your Tivoli Storage Manager administrator to ensure that the portable media was created on a device using a format that is compatible with your device.

  2. There is no support in the Tivoli Storage Manager API for the backup set format.

  3. To enable the GUI client to restore a backup set on an attached device on a UNIX standalone workstation, without requiring a server connection, use the localbackupset option. See Localbackupset for more information.

  4. Note that the restore backupset command supports restore of local backup sets from local media without using the localbackupset option.

Restoring an entire or partial backup set

Tivoli Storage Manager considers a backup set as one object containing the whole file structure. You can restore the entire backup set or just select portions. The backup set media is self-describing and contains all the information required to perform a successful restore.

Use the GUI to restore an entire backup set only. The command line can be used to restore an entire backup set or individual files within a backup set. See Restore Backupset for information on how to use the restore backupset command.

Restoring backup sets using the GUI

Attention: Before you begin a restore, be aware that backup sets can contain data for multiple file spaces. If you specify a destination other than the original location, data from all file spaces are restored to the location you specify.

To restore a backup set, perform the following steps:

Notes:

  1. If the object you want to restore is part of a backup set generated on a node, and the node name is changed on the server, any backup set objects that were generated prior to the name change will not match the new node name. Ensure that the node name is the same as the node for which the backup set was generated.

  2. If the backup set is on the server, normal Tivoli Storage Manager security applies, and you can only restore your own files and files to which you have been granted access. However, normal Tivoli Storage Manager security does not apply to backup set data when restored locally because the physical media can be explored by the person who has access to it.

  3. To enable the GUI client to restore a backup set on an attached device on a UNIX standalone workstation, without requiring a server connection, use the localbackupset option. See Localbackupset for more information. The restore backupset command supports restore of local backup sets from local media without using the localbackupset option. Also, certain local devices such as tape devices require device drivers to be set up prior to performing a restore. See the device manual for assistance with this task. You will also need to know the device address in order to perform the restore.

Restoring backup sets using the command line client

The restore backupset command restores a backup set from the server, a local file, or a local tape device. See Restore Backupset for more information

Use the location option with the restore backupset and query backupset commands to specify where Tivoli Storage Manager searches for a backup set during a query or restore operation. You can use this option to locate backup sets on the server or local files. Tapes that are generated on the server can be used locally by specifying the location option and either the file name or the tape device. See Location for more information.

Use the query backupset command to query a backup set from a local file, tape device, or the Tivoli Storage Manager server. The query backupset command displays the backup set name, generation date, retention, and description. See Query Backupset for more information.


Restoring NAS file systems

You restore NAS file system images using the Web client or command line interface. For information on how to install and configure the Web client, see Configuring the Web client.

You can restore full or differential NAS file system images that were backed up previously. If you restore a differential image, Tivoli Storage Manager automatically restores the full backup image first, followed by the differential image. It is not necessary for a client node to mount a NAS file system to perform backup or restore operations on that file system.

Restoring NAS file systems using the Web client

For information on how to install and configure the Web client, see Configuring the Web client. To restore NAS file systems using the Web client GUI:

  1. Click the Restore from the main 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.

    Notes:

    1. Nodes shown are those that have been backed up and to which your administrator has authority.

    2. The root node called Nodes is not selectable. This node only appears if a NAS plug-in is present on the client machine.

    3. NAS nodes display on the same level as the client workstation's node. Only nodes to which the administrator has authority appear.
  3. Expand the NAS node to reveal the Image object.
  4. Expand the Image object to display volumes that you can restore. You cannot expand Volume objects.
  5. Click the selection boxes next to the volumes under the Image object that you want to restore.

    Notes:

    1. If you want to restore a NAS image that was backed up on a particular date, click the Point In Time button. After you select a date, the last object that was backed up on or prior to that date appears, including any inactive objects.

    2. If you want to display all images (including active images and inactive images), before you select them, select View -> Display active/inactive files from the menu bar.
  6. Click Restore. The Restore Destination window appears. Enter the information in the Restore Destination window. If you choose to restore to a different destination, you can only restore one volume at a time to a different destination.
    Note:
    You can restore NAS file system images to any volume on the NAS file server from which they were backed up. You cannot restore images to another NAS file server.
  7. Click Restore. The NAS Restore Task List window displays the restore processing status and progress bar. If there is a number next to the progress bar, it indicates the size of the restore, if known. After the restore completes, the NAS Restore Report window displays processing details.
    Note:
    If it is necessary to close the Web browser session, current NAS operations will continue after disconnect. You can use the Dismiss button on the NAS Restore Task List window to quit monitoring processes without ending the current operation.
  8. (Optional) To monitor processing of an operation, select the Actions -> TSM Activities from the main window.

Considerations:

Restoring NAS files and directories using the Web client

You can use the toc option with the include.fs.nas option in your client system options file (dsm.sys) to specify whether Tivoli Storage Manager saves Table of Contents (TOC) information for each file system backup. See Toc for more information. If you save TOC information, you can use Tivoli Storage Manager Web client to examine the entire file system tree and select files and directories to restore. Creation of a TOC requires that you define the TOCDESTINATION attribute in the backup copy group for the management class to which this backup image is bound. Note that TOC creation requires additional processing, network resources, storage pool space, and possibly a mount point during the backup operation. If you do not save TOC information, you can still restore individual files or directory trees using the restore node server command, provided that you know the fully qualified name of each file or directory and the image in which that object was backed up.

To restore NAS files and directories:

  1. Click the Restore from the main 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.

    Notes:

    1. Nodes shown are those that have been backed up and to which your administrator has authority.

    2. The root node called Nodes is not selectable. This node only appears if a NAS plug-in is present on the client machine.

    3. NAS nodes appear on the same level as the client workstation's node. Only nodes to which the administrator has authority appear.
  3. Expand the NAS node to display the File Level object.
  4. Expand the File Level object to display the volumes, directories, and files that were last backed up. When you expand the volume object, and complete TOC information is available on the server for the latest backup, the Load Table of Contents dialog appears. If complete TOC information is not available for the latest backup, no objects will appear below the volume object. The next step explains how to display objects from backups other than the latest backup. Complete TOC information is provided if you performed either of the following operations:
  5. Click the selection boxes next to the directories or files that you want to restore. If you want to restore files from a NAS image that was backed up on a particular date or display files from several older versions, highlight the volume you want to restore and click the Point In Time button. If you select Use a Point in Time Date in the Point in Time Restore windows, files from the image backed up on that date, and if it is a differential image, files from its corresponding full image appear under the File Level object. If you click Use Selected Images in the Point in Time Restore window, the Selected Images window appears for you to select images. The contents of the selected images appear in the File Level object.
  6. Click Restore. The Restore Destination window appears. Enter the information in the Restore Destination window. If you choose to restore to a different destination, you can only restore one volume at a time to a different destination.
  7. Click Restore. The NAS Restore Task List window displays the restore processing status and progress bar. If there is a number next to the progress bar, it indicates the size of the restore, if known. After the restore completes, the NAS Restore Report window displays processing details.
    Note:
    If it is necessary to close the Web browser session, current NAS operations will continue after disconnect. You can use the Dismiss button on the NAS Restore Task List window to quit monitoring processes without ending the current operation.
  8. (Optional) To monitor processing of an operation, select the Actions -> TSM Activities from the main window.

Considerations:

Restoring NAS file systems using the command line

Table 37 lists the commands and options you can use to restore NAS file system images from the command line.

Table 37. NAS options and commands

Option or command Definition Page
query node Displays all the nodes for which a particular administrative user ID has authority to perform operations. The authorized administrative user ID should have at least client owner authority over both the NAS node and the client workstation node they are using either from command line or from the Web client. Query Node
query backup Use the query backup command with the class option to display information about file system images backed up for a NAS file server. Query Backup
query filespace Use the query filespace command with the class option to display a list of file spaces belonging to a NAS node. Query Filespace
restore nas Restores the image of a file system belonging to a Network Attached Storage (NAS) file server. Restore NAS
monitor process Displays current backup and restore processes for all NAS nodes for which an administrative user has authority. The administrative user can then select one process to monitor. Monitor Process
cancel process Displays current back up and restore processes for all NAS nodes for which an administrative user has authority. From the display, the administrative user can select one process to cancel. Cancel Process
delete filespace Use the delete filespace with the class option to display a list of file spaces belonging to a NAS node so that you may choose one to delete. Delete Filespace

Regardless of client platform, NAS file system specifications use the forward slash (/) separator, as in this example: /vol/vol0.

Note:
When you initiate a NAS restore operation using the command line client or the Web client, the server starts a process to initiate, control, and monitor the operation. It may take several moments before you notice progress at the command line client interface because the server must perform mount and other necessary tasks before data movement occurs. The Tivoli Storage Manager command line client may display an Interrupted ... message when the mount occurs. You can ignore this message.

Restoring the WebSphere Application Server (WAS)

Use the Web client GUI or command line client to restore full or differential image backups of a WebSphere Application Server if the Data Protection for WebSphere Application Server is installed. When you back up a WAS, file spaces are created on the Tivoli Storage Manager server with the naming convention WAS_INSTANCENAME (for the Application Server file space) and WAS_ND_INSTANCENAME (for the Network Deployment Manager file space).

Before you begin:

To restore the WebSphere Application Server::

  1. Click Restore from the Web client GUI main window. The Restore window appears.
  2. Expand the directory tree if necessary.
  3. Expand the WebSphere Application Server node to reveal the WAS_<INSTANCENAME> and WAS_ND_<INSTANCENAME> file spaces.

    Notes:

    1. The most recent active full or differential backup appears under the WebSphere Application Server tree.

    2. If only a single instance of WAS was backed up, the WebSphere Application Server tree displays only the WAS_<NODENAME> and WAS_ND_<NODENAME> file spaces.

    3. If multiple instances of WAS were backed up, the WebSphere Application Server tree displays multiple instances as WAS_<INSTANCENAME> and WAS_ND_<INSTANCENAME>. The INSTANCENAME is a variation of the NODENAME.
  4. Click the selection box next to the Application Server (INSTANCENAME) node or Network Deployment Manager (INSTANCENAME) node that you want to restore.

    Notes:

    1. If you want to restore objects that were backed on a particular date, click the Point In Time button. After you select a date, the last object that was backed up on or prior to that date appears, including inactive objects.

    2. If you want to see all active and inactive WAS backups before you select them, select View -> Display active/inactive files from the menu bar. Inactive WAS backup objects are displayed with an X next to the object in the tree.
  5. Click Restore. The Restore Task List window displays the restore processing status. If you want to re-access the Task List window after exiting and restarting the Web client, select Actions -> TSM Activities from the menu.

Considerations:

To restore WAS objects from the Tivoli Storage Manager command line, use the restore was command. See Restore WAS for more information.


Restore: Additional considerations

This section discusses some advanced considerations for restoring data. You do not need to understand this information to use Tivoli Storage Manager for basic work.

Authorizing another user to restore or retrieve your files

You can authorize another user on the same workstation or a different workstation to restore backup versions or retrieve archive copies of your files. This permits you to share files with other people or with other workstations that you use with a different node name. To authorize a user on another workstation to restore or retrieve your files, the other workstation must be running one of the UNIX clients and must be registered with your Tivoli Storage Manager server.

To authorize another user to restore or retrieve your files:

  1. Click Utilities -> Node Access List from the main window. The Node Access List window appears.
  2. Click the Add button. The Add Access Rule window appears.
  3. In the Add Access Rule window, select an item in the Permit Access to field to specify the type of data that the other user can access. You can select either Backed up Objects or Archived Objects.
  4. Type the node name of the user's host machine that can access your data in the Grant Access to Node field.
  5. Type the name of the user on a node who can access your data in the User field.
  6. In the Filespace and Directory field, select the file space and the directory that the user can access. You can select one file space and one directory at a time. If you want to give the user access to another file space or directory, you must create another access rule.
  7. If you want to limit the user to specific files in the directory, type the name or pattern of the files on the server that the other user can access in the Filename field. You can make only one entry in the Filename field. It can either be a single file name or a pattern which matches one or more files. You can use a wildcard character as part of the pattern. Your entry must match files that have been stored on the server.
  8. For the Java GUI: If you want to give access to all files that match the file name specification within the selected directory including its subdirectories, click Include subdirectories.
  9. Click the OK button to save the access rule and close the Add Access Rule window.
  10. The access rule that you created is displayed in the list box in the Node Access List window. When you have finished working with the Node Access List window, click the OK button. If you do not want to save your changes, click Cancel or close the window.

On the command line client, use the set access command to authorize another node to restore or retrieve your files. You can also use the query access command to see your current list, and delete access to delete nodes from the list. For more information about these commands, see:

Restoring or retrieving files from another client node

After users grant you access to their files on the server, you can restore or retrieve those files to your local system. You can display another user's file spaces on the server, restore the other user's backup versions, or retrieve the other user's archive copies to your local file system.

To display another user's file spaces on the server, restore the other user's backup versions, or retrieve the other user's archive copies to your local drives:

  1. Click Utilities from the main window.
  2. Click Access Another Node. The Access Another Node window appears.
  3. Type the node name of the user's host machine in the Node name field. Type the user name in the User name field.
  4. Click the Set button.

If you are using commands, use the fromnode and fromowner options to indicate the node name and the name of the user who owns the files.

For example, to restore files to one of your own file systems that were backed up from a workstation named Node1 and owned by a user named Ann, enter:

   dsmc restore -fromn=node1 -fromo=ann "/home/proj/*" /home/gillis/

Use the query filespace command to get a list of file spaces (see Query Filespace). For example, to get a list of file spaces owned by Ann on Node1, enter:

   dsmc query filespace -fromn=node1 -fromo=ann

See Fromnode for more information about the fromnode option. See Restore for more information about using the fromnode and fromowner options with the restore command. Also seeRetrieve for more information about the retrieve command.

Restore or retrieve files to another workstation

From a different workstation, you can restore or retrieve files you have already backed up from your own workstation. You must know the Tivoli Storage Manager password assigned to your node.

To restore or retrieve files to another workstation, use the virtualnodename option to specify the node name of the workstation from which you backed up the files. Virtualnodename cannot be set to the hostname of the machine. You can use the virtualnodename option when you start Tivoli Storage Manager or you can add the virtualnodename option to your client user options file dsm.opt. Use the virtualnodename option on the dsm or dsmj command if you are borrowing another user's machine and you do not want to update their client user options file.

Tivoli Storage Manager prompts you for the password for your original node. After you enter the correct password, all file systems from your original workstation appear in the Restore or Retrieve window. You can restore or retrieve files as if you were working on your own workstation.

Attention: When you use this method to access files, you have access to all files backed up and archived from your workstation. You are considered a virtual root user.

You can use the virtualnodename option in a command. For example, to restore your projx files, enter:

   dsmc restore -virtualnodename=nodeone "/home/monnett/projx/*"

If you do not want to restore or retrieve the files to the same directory name on the alternate workstation, enter a different destination.

The considerations for retrieving files are the same as restoring files.

Restoring a disk in case of disk loss

Tivoli Storage Manager can recover your files only if you can run the client. If the file system that contains the client is lost, you must reinstall the client before you can recover your files. If you also lose the file system that contains the operating system and communication software, you must recover them before you can connect to the server.

To protect yourself against these kinds of losses, you need to put together a set of installation media that you can use to restore your system to a state that lets you contact the server and begin recovering data. The installation media should contain:

  1. A bootable operating system that lets you perform basic functions.
  2. A correctly configured communication program that lets you establish communications with the server.
  3. A client with appropriate customized options files. You can use the command line client to complete this task.

The communication package you use determines what files you need. Consult your operating system and communication software manuals to set up your installation media.

If you also have the Tivoli Space Manager installed on your workstation, your installation media should include the space manager command line client. For information about restoring migrated files, see IBM Tivoli Storage Manager for Space Management for UNIX User's Guide, GC32-0794.

Note: Your administrator can schedule restore operations which can be very useful when you need to restore a large number of files.

Deleting file spaces

Authorized User

If your Tivoli Storage Manager administrator gives you authority, you can delete entire file spaces from the server. You cannot delete individual backup versions that are kept on the server. When you delete a file space, you delete all the files and images, both backup versions and archive copies, that are contained within the file space. For example, if you delete the file space for your /home/monnet file system, you are deleting every backup for every file in that file system and every file you archived from that file system. Carefully consider whether you want to delete a file space.

You can delete file spaces using the Tivoli Storage Manager GUI or command line clients. To delete NAS file spaces, use the Web client or command line client.

To delete a file space using the GUI, perform the following steps:

  1. Select Utilities-> Delete Filespaces from the main window.
  2. Click the selection boxes next to the file spaces you want to delete.
  3. Click the Delete button. Tivoli Storage Manager prompts you for confirmation before deleting the file space.

You can also delete a file space using the delete filespace command. See Delete Filespace for more information. Use the class option with the delete filespace command to delete NAS file spaces. See Class for more information.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]