Use Tivoli Storage Manager to maintain a set of backup versions of your file system or raw logical volumes on your workstation. You can recover these older file versions in the event your current files are lost or damaged. This chapter covers different ways to back up files, how to restore the files, and the difference between backing up and archiving files.
All backup and restore procedures in this chapter also apply to the Web client, except those identified in "Using the Web Backup-Archive Client". See "Starting a Web Client Session" for information about starting and using the Web client.
The following table contains tasks in this chapter:
If you are a first-time user, or if you only back up files occasionally,
you may wish to use Table 3 as a checklist of preliminary steps to consider before
performing a backup.
Table 3. Preliminary Steps for Backing Up Files
|
|
---|---|
___ | Decide whether you want to backup files or archive them. See "Do You Want to Back Up or Archive Files?" for more information. |
___ | Do you plan to use the AFS or DFS backup client, or both. See "Using the AFS/DFS Backup Clients" for more information. |
___ | Do you need to exclude files from backup services? See "Using an Include-Exclude Options List to Control Processing" for more information. |
___ | Decide what type of backup you want according to your needs. See the following sections for more information: "Full Incremental Backup", "Partial Incremental Backup", and "Full Incremental versus Partial Incremental Backup" |
___ | If you are performing an image backup, ensure that you have accounted for unique considerations. See "Image (Raw Logical Volume) Backup" for more information. |
___ | For further backup considerations, see "Backup: Related Topics". |
When the backup-archive client backs up or archives a file, it sends a copy of the file and its associated attributes to the server; however, backups and archives have different goals.
Backups protect against file damage. A sequence of backup versions is kept for each file on your workstation and older versions are deleted as newer versions are made. The number of backup versions is set by your administrator.
Archive copies are more permanent. They maintain a file in a particular state indefinitely (although your administrator can limit how long archives are kept). Archives are useful if you need to go back to a particular version of your files, or you want to delete a file from your workstation and retrieve it if necessary. For example, you might need to save spreadsheets for tax purposes, but because you are not using them, you do not want to leave them on your workstation. See Archiving and Retrieving Files for more information about archiving and retrieving files.
Use backups to protect against unforeseen damage to your files, and use archives for maintaining more permanent versions of your files.
The AFS/DFS backup clients are available on AIX workstations. Tivoli Storage Manager includes executable files for the graphical user interface and the command-line interface in non-AFS/DFS, AFS, and DFS versions.
If you perform a command-line backup of AFS or DFS files using the non-AFS/DFS versions, Tivoli Storage Manager backs up the files and saves standard UNIX access permissions and extended permissions, but does not back up AFS or DFS access control lists for directories. If you want to back up AFS or DFS access control lists, or to recognize AFS or DFS virtual mount points, you must use the AFS or DFS versions of the executable files.
For more information, please see Appendix A, The AFS and DFS File Backup Clients.
There may be files on your file systems that you do not want to back up. These files may be core files, local caches of network file systems, operating system or application files that could be easily recovered by reinstalling the program, or any other files that you could easily rebuild.
An Authorized User on your workstation can use the exclude and include options in your include-exclude options list to specify which files to exclude from backup processing.
Tivoli Storage Manager uses the include-exclude options file for incremental and selective backups and backs up any file that is not explicitly excluded. You do not need to use an include option to include specific files unless those files are in a directory you want to exclude.
You can also specify the include and exclude options in the dsm.sys file. For more information on creating an include-exclude options file, see Creating an Include-Exclude List.
You can encrypt the data that is sent to the server during a backup or archive operation using standard DES 56-bit encryption. Files are selected for encryption using include.encrypt and exclude.encrypt processing. By default, files are not encrypted unless they are explicitly included using the include.encrypt option. For more information about the exclude.encrypt option, see Exclude Options. For more information about the include.encrypt option, see Include Options.
To encrypt file data, you must select an encryption key password, which Tivoli Storage Manager uses to generate the encryption key for encrypting and decrypting the file data. Store the encryption key password for later use. You can specify whether to save the encryption key password in a file named TSM.PWD by using the encryptkey option. While restoring the encrypted file, Tivoli Storage Manager will prompt you for the key password to decrypt the file in the following cases:
For more information about this option, see Encryptkey.
Your administrator might have set up schedules to automatically back up files on your workstation. See Automating Tasks for information on checking and running the schedules available to you. The following sections discuss how to back up files without using a schedule.
There are two types of incremental backup: full incremental and partial incremental.
A full incremental backup (also called an incremental backup) initially backs up all specified drives, directories and files, and thereafter, all new and changed files. Thus Tivoli Storage Manager maintains current server storage of your workstation files according to your storage management policies. Files that you delete from your workstation will not have active backup versions on the server. See "Understanding Storage Management Policies" for more information about storage management polices.
To perform a full incremental backup using the client GUI, select the Incremental (complete) option from the type of backup pull-down menu on the backup window or use the incremental command on dsmc prompt. Specify file systems, directory trees, or individual files to include in the backup.
During a full incremental, the client queries the server to determine the exact state of your storage as of your last incremental. Tivoli Storage Manager uses this information to:
Attention: An incremental backup backs up all directory information. When you back up a file, the directories in the path that contain the file are also backed up. To exclude directories from backup, use the exclude.dir option. For more about exclude.dir, see Exclude Options. Directories count in the number of objects backed up.
A partial incremental backs up new and changed files but does not expire or rebind files on the server. The frequency attribute of the copy group is also ignored. There are two types of partial incremental backup:
Files added at the client after the last incremental backup, but with a modification date earlier than the last incremental, are not backed up.
Incremental-by-date updates the date and time of the last incremental at the server. If you perform an incremental-by-date on only part of a file system, the date of the last full incremental is not updated. The next incremental-by-date will back up these files again.
To perform a selective backup using the client GUI, see "Performing a GUI Backup" for more information.
Use the selective command to perform a selective backup from the client command line. See Selective for more information.
Both full and partial incrementals back up new and changed files. An incremental-by-date takes less time to process than a full incremental and requires less memory. Unlike a full incremental, an incremental-by-date does not maintain current server storage of all your workstation files because:
You can maintain current server storage of your workstation files by performing a partial incremental backup on weekdays and a full incremental backup on weekends.
When you back up your files, Tivoli Storage Manager also saves standard UNIX access permissions assigned to the files. Depending on your operating system, it also saves extended permissions. For example, for files on an AIX workstation, Tivoli Storage Manager saves access control lists.
If you use the AFS or DFS versions of the dsm and dsmc commands (dsmafs and dsmcafs for AFS, dsmdfs and dsmcdfs for DFS) to back up AFS or DFS files (on an AIX workstation only), Tivoli Storage Manager also saves the access control lists that exist for each AFS or DFS directory. If you perform a command line backup of AFS or DFS files using the non-AFS/DFS versions, Tivoli Storage Manager backs up the files and standard UNIX access permissions, but does not save the AFS or DFS access control lists for directories. See Using the AFS/DFS Backup Clients for more information.
Note: If an Authorized User backs up files for another user, the other user owns the backup versions of the files in storage. The Authorized User does not need to grant the other user access to the backup versions.
If you are an Authorized User and you want back up files beginning with a specific directory within a file system, you can define that directory as a virtual mount point (see Virtualmountpoint).
Defining a virtual mount point within a file system provides a direct path to the files you want to back up, thus saving processing time. It is more efficient than defining the file system with the domain option and then using an exclude option to exclude the files you do not want to back up. It also allows you to store backups and archives for specific directories in separate storage file spaces.
Note: The backup-archive client does not recognize AFS/DFS volume mount points. You must install the AFS/DFS client. For more information about using the AFS/DFS backup-archive clients, see Appendix A, The AFS and DFS File Backup Clients.
You can use the Estimate function to estimate the amount of time it takes to process files and directories. The estimated time is a rough calculation of the time required to transfer your data and is based on previous transfers of data between your workstation and the current server. The actual transfer time could be longer or shorter than the estimate due to factors like network traffic, system load on your workstation, or system load on the server.
Since the Estimated Transfer Time is based on previous backup transfer rates, you must run at least one backup operation first. Note that the estimate function does not take into account whether or not files are excluded from backup. The assumption made by the estimation algorithm is that all the files selected will be sent to the server. The Estimated Transfer Time field reads N/A if no files are sent to or from the current server.
Note: During installation, Tivoli Storage Manager creates the .adsmrc file to record statistics from the backup-archive client estimate function. The .adsmrc file resides in the $HOME environment variable.
You can back up specific files, a group of files with similar names, or entire directories. You can locate the files you want to back up by searching or filtering. Filtering displays only the files matching the filter criteria for your backup.
To perform an automatic incremental backup of your default domain, select Actions> Backup Domain. Your default domain is set with the domain option in your client user options file (see Domain). If you do not have the domain option set, the default domain is all local file systems.
You can use the selective or incremental command to perform a backup. When the incremental and selective commands complete, Tivoli Storage Manager displays processing statistics similar to those shown in the GUI Backup Report window. These statistics also display in the schedule log for scheduled commands. See Incremental and Selective for more information.
Selective: The selective command backs up specific files. Use wildcards to back up more than one file at a time. If you back up a directory, you can use the subdir=yes option to include all the subdirectories under that directory in the backup. For example, to back up the /home/monnett/proj directory and its subdirectories, enter:
dsmc selective /home/monnett/proj/ -subdir=yes
If a subdirectory is a mounted file system, Tivoli Storage Manager does not back up the files in that subdirectory when you use the subdir=yes option.
You can use more than one file specification on the selective command. For example, to back up the /home/monnett/h1.doc and /home/monnett/test.doc files, enter:
dsmc selective /home/monnett/h1.doc /home/monnett/test.doc
Incremental: You can run an incremental backup from the command line using the incremental command. For example, to back up the /home file system, enter:
dsmc incremental /home
If you do not select the file systems to back up, Tivoli Storage Manager uses your default domain. Add file systems to the default domain with the domain option. For example, if your default domain contains file systems /home and /usr, back up those file systems plus the /mfg file system using:
dsmc incremental -domain=/mfg
To start an incremental-by-date, add the incrbydate option:
dsmc incremental -incrbydate
During an incremental backup, Tivoli Storage Manager displays the status of each file it attempts to back up. Tivoli Storage Manager reports the file's size, volume, path, file name, and whether the backup attempt was successful. Similar statistics are produced by the selective and archive commands. These also display in the schedule log for scheduled commands.
When Tivoli Storage Manager backs up a file space or other set of files, it attempts to improve performance and load balancing by using multiple sessions. This can result in as many as five sessions running at one time to read files and send them to a server.
The Web client and backup-archive client GUI provide a Task List window that displays information about files during processing. When a task completes, a Backup Report window displays processing details. Click the Help button in the Backup Report window for context help.
The command line displays similar information. On the backup-archive command line the name of each file displays after it is sent to the server. The progress indicator shows overall progress. Informational messages may display as follows:
Root User
From your local workstation, you can back up an entire file system or raw logical volume as a single object. This as an image (or raw logical volume) backup and provides the following benefits:
Image backup is supported on AIX, AIX 5L, Solaris, and HP-UX.
If copy serialization is static, ensure that no one is using the file system when you perform an image backup. If the file system is in use when Tivoli Storage Manager attempts to unmount it, the backup will fail. To ensure a consistent image, Tivoli Storage Manager remounts the file system in read-only mode before starting the backup. After the backup completes, Tivoli Storage Manager remounts the file system to its original state.
Do not include system file spaces in an image backup because they cannot be unmounted.
Important: If a mounted file system has nested mount points, unmount them before attempting a backup or restore. Image backups cannot be performed on nested mount points.
The server stores and manages image backups in the same way as other objects. However, a unique object type is used to distinguish image backups.
The entire image (not individual files) is assigned a management class. If you do not specify a management class, the default class is used for the entire file system. You can define policy sets, management classes, and copy groups for an image, as well as exclude specific file systems from the image.
Use the backup image and restore image commands to perform backup and restore operations on a single volume.
Place an include.image entry in your include-exclude list to assign a management class to the image. Place an exclude.image entry in your include-exclude list to exclude a file system from being backed up with the backup image command.
The following table lists devices supported by the backup image
command. In this table, Yes means that the backup
image command is supported, No means backup image
command is not supported, and a dash (-) means the type of
logical volume manager is not available.
Table 4. Devices Supported by the Backup Image Command
Logical Volume Manager | Raw Device Types | Sample Device Name | AIX, AIX 5L | HP UX | Solaris |
---|---|---|---|---|---|
AIX Logical Volume Mgr | Logical Volumes | /dev/1v00 | Yes | - | - |
Sun Solstice Volume Mgr | Meta Devices | /dev/md/ dsk/dl | - | - | Yes |
Veritas Volume Mgr | Logical Volumes | /dev/vx/dsk/ rootdg/vol01 | - | Yes | Yes |
Raw Disk | Disk Slices | /dev/dsk/ c0tld0s0 | No | No | Yes |
The client must support the raw device type on the specific platform in order to perform an image backup of a raw device. If you want to perform an image backup for a file system mounted on a raw device, the raw device must be supported. Remember to specify raw devices by their block device name.
You can perform an incremental-by-date image backup to back up files that have changed since your last image backup. The following restrictions apply:
To create an image backup of your file system or raw logical volume, perform the following steps:
incremental backup
incremental-by-date backup
Following is an example of how an image backup might work.
| Client | Server |
---|---|---|
Monday | Files 1, 2 and 3 reside here. | An image backup is performed. (Assume a full incremental was also performed.) A list of files in the image is created on the server. |
Tuesday | File 4 is created. | Daily incremental is performed - including incremental for file 4. |
Wednesday | File 2 is deleted; file 3 is changed. | Daily incremental is performed - including incremental for file 3; list of files in image backup shows file 2 was deleted. |
Thursday | File 1 is deleted. | Daily incremental is performed; list of files in image backup shows file 1 was deleted. |
Suppose you want to use the image created on Monday to restore your file system as it appeared just after Thursday's incremental backup. Tivoli Storage Manager would use the following process:
Tivoli Storage Manager Version 4.2 AIX, AIX 5L, and Solaris clients support LAN-free data movement, which shifts the movement of client data from the communications network to a storage area network (SAN). Shifting the client data movement from the communications network to a SAN decreases the load on the Tivoli Storage Manager server. This allows the server to support a greater number of simultaneous client connections.
The SAN provides a path that allows you to backup, restore, archive, and retrieve data to and from a SAN-attached storage device. Client data moves over the SAN to the storage device via the Tivoli Storage Manager Storage Agent. The Tivoli Storage Manager Storage Agent must be installed on the same system as the client.
To enable LAN-Free support, you must install and configure the Tivoli Storage Manager Managed System for SAN feature on the client workstation. For more information, see the Tivoli Storage Manager for AIX Managed System for SAN Storage Agent User's Guide or Tivoli Storage Manager for Sun Solaris Managed System for SAN Storage Agent User's Guide listed in Related Publications.
After installing and configuring the Tivoli Storage Manager Managed System for SAN feature on the client workstation, you can use the following options to enable LAN-Free data movement:
Tivoli Storage Manager supports backup and restore of network attached storage (NAS) file system images to tape drives or libraries that are locally attached to NAS file servers. Tivoli Data Protection for NDMP enables backup and restore support on the Tivoli Storage Manager Windows NT and Windows 2000 servers for NAS file servers from Network Appliance. Tivoli Data Protection for NDMP is a separately priced and licensed product. See Appendix B, "Backing Up NAS File Systems" for more information.
This section includes topics related to incremental and selective backups. You do not need to understand this information to use Tivoli Storage Manager for basic work.
When you back up and archive files, Tivoli Storage Manager stores the backups and archives in a file space in storage that has the same name as the file system or virtual mount point from which the files originated.
For example, if you have a file system named /home, and you back up a file named doc1 in the /home/monnett directory, Tivoli Storage Manager stores the file in a file space named /home. If an Authorized User later defines /home/monnett as a virtual mount point, any files you back up from the /home/monnett directory, such as doc2, are stored in a file space named /home/monnett. If you enter this command:
dsmc query backup "/home/monnett/*"
Tivoli Storage Manager looks for files in the /home/monnett file space. It always looks for a file in the file space with the longest name that matches the file specification you include in a command. It locates the file named doc2 that was backed up after the virtual mount point was defined. However, it does not locate the file named doc1 because that file was backed up before the virtual mount point was defined and the backup was stored in the /home file space.
To list or restore the doc1 file using a command, you must explicitly specify the file space name by enclosing it in braces. For example:
dsmc query backup "{/home}/monnett/*" dsmc restore {/home}/monnett/doc1
If the Authorized User subsequently removes the /home/monnett virtual mount point, and you then back up additional files in the /home/monnett directory, the backups are once again stored in the /home file space. For example, if you now back up a file named doc3 in the /home/monnett directory, it is stored in the /home file space. It is not stored in the existing /home/monnett file space.
However, because the /home/monnett file space already exists, when you try to query or restore the doc3 file, Tivoli Storage Manager looks for the file in the /home/monnett file space unless you specify the correct file space name. For example:
dsmc query backup "{/home}/monnett/*" dsmc restore {/home}/monnett/doc2
Note: You must explicitly specify the file space name only when there can be more than one resolution to the file specification.
For example, if the following file spaces exist in storage:
/home /home/monnett /home/monnett/project1 /home/monnett/project1/planning
then enter:
dsmc query backup "/home/monnett/project1/planning/*"
Tivoli Storage Manager looks for files only in the /home/monnett/project1/planning file space, even if one or more of the other file spaces contains a path with the same name. But, when you enter one of the following:
dsmc query backup "{/home}/monnett/project1/planning/*" dsmc query backup "{/home/monnett}/project1/planning/*" dsmc query backup "{/home/monnett/project1}/planning/*"
Tivoli Storage Manager looks for files only in the /home file space, the /home/monnett file space, or the /home/monnett/project1 file space, depending on which form you use.
For full incrementals, Tivoli Storage Manager considers a file changed if any of these items are different from the last backup performed:
These next items do not cause the entire file to be backed up to the server; however, they cause the information about the file to be updated.
When you request an incremental or selective backup, Tivoli Storage Manager backs up a file if all of the following requirements are met:
When you perform an incremental backup of your files, Tivoli Storage Manager also checks the following:
When you run an incremental or selective backup, Tivoli Storage Manager also backs up all directory information that is not already backed up. Directories are counted in the number of objects backed up.
Special file systems contain dynamic information generated by the operating system; they contain no data or files. The Tivoli Storage Manager client ignores special file systems and their contents. Special file systems include the following:
Tivoli Storage Manager uses management classes to determine how to manage your backups on the server. Every time you back up a file, the file is assigned a management class. The management class used is either a default selected for you, or one assigned to the file by an Authorized User with an include option in the include-exclude options list. The selected management class must contain a backup copy group in order for the file to be backed up. See Automating Tasks and Understanding Storage Management Policies for more information on management classes, how an Authorized User assigns management classes to files, and storage management policies.
A UNIX symbolic link is a file that contains a pointer to another file or directory. Tivoli Storage Manager handles symbolic links differently than it does regular files and directories. In some operations, such as a backup, only the path information that the symbolic link contains is backed up. In other operations, such as archive, the file to which the symbolic link points is archived, but under the name of the symbolic link. For more information on how symbolic links are handled during an archive operation, see Archsymlinkasfile.
For directories, most operations are affected by the setting of the subdir option. If the subdir option is set to no, only the directory and the files it contains are affected. If the subdir option is yes, Tivoli Storage Manager recursively processes all files and directories in the directory tree.
The following table shows symbolic link backup and restore functions along
with the action taken:
Table 5. Symbolic Link Management Table for Backup and Restore
Function | Action Taken |
---|---|
Selective backup of a file. | Backs up the symbolic link only, the file is not backed up. |
Selective backup of a directory. | Backs up the directory only, the symbolic link is not backed up. |
Incremental backup with subdir=no. | Backs up the symbolic links only, files and directories pointed to are not backed up. |
Incremental backup with subdir=yes. | Backs up the symbolic links and directories and files they point to. |
Restore a symbolic link that points to a file. | The symbolic link is restored, regardless of whether the file the symbolic link points to still exists. |
Restore a symbolic link that points to a directory. | The symbolic link is restored, regardless of whether the directory the symbolic link points to still exists. |
Restore a symbolic link that points to a directory with subdir=yes, the directory still exists. | The symbolic link and files in the directory and subdirectories are restored. |
Restore a symbolic link that points to a directory with subdir=yes, the directory and symbolic link no longer exist. | A directory is created in the directory in which the symbolic link resides and all files and subdirectories are restored to that directory; the symbolic link name is used as the new directory name. |
A hard link is established when two files point to the same data file. When you back up a file that contains a hard link to another file, Tivoli Storage Manager stores both the link information and the data file on the server. If you back up two files that contain a hard link to each other, Tivoli Storage Manager stores the same data file under both names, along with the link information.
When you restore a file that contains hard link information, Tivoli Storage Manager attempts to reestablish the links. If only one of the hard-linked files is still on your workstation, and you restore both files, they are hard-linked together.
The one exception to this procedure occurs if you back up two files that are hard-linked together and then break the connection between them on your workstation. The two files then contain separate data files. If you restore the two files from the server, Tivoli Storage Manager will respect the current file system and not restore the hard link.
Problems can occur if you back up only one file of a hard-linked pair. For example, files texta and textb contain a hard link to each other. You back up texta, then edit textb and make some changes. If you restore texta, the changes you made to textb will be lost.
To ensure that hard-linked files remain synchronized, always back up all files that have hard links to each other at the same time and restore those same files together.
When Tivoli Storage Manager connects a backup-archive client to an NFS file system, you can use either a hard mount or a soft mount. Tivoli Storage Manager uses the nfstimeout option setting to determine how long to wait for an NFS system call to respond before timing out; this applies to hard and soft mounts. The default is 10 seconds.
You should be aware of the consequences of hard and soft mounts if the mount becomes stale (for example, if the server for the file system is not available).
When one of these events occurs, control returns to the calling program.
Tivoli Storage Manager looks for files that have changed between the start and the completion of the file's backup. Some files on your system may be in use, or open, when you try to back them up. Because an open file may change, a backup action might not reflect the correct contents of the file at a given time.
Consider if a file is important. Can you build the file again? If the file is not important, you may not want to back up the file. Or, if the file is important, a root user on your workstation can ensure the file is closed before back up.
If your backups run on a schedule, a root user can use the preschedulecmd option to enter a command to close the file. For example, if the open file is a database, use the database's quiesce command to shut down the database. A root user can use the postschedulecmd option to restart the application that uses the file after the backup completes. If you are not using a schedule for the backup, ensure that you close the application that uses the file before you start the backup.
Tivoli Storage Manager can back up the file even if it is open and gets changed during the backup. This is only useful if the file will be usable even if it changes during backup. To back up these files, assign the files a management class with the serialization dynamic or shared dynamic. See Selecting a Management Class for Files and Displaying Information about Management Classes and Copy Groups for information.
You can use the operating system's wildcard characters in file specifications with Tivoli Storage Manager. These characters let you select groups of files that have similar names.
In a command, wildcard characters can only be used in the file name or extension. They cannot be used to specify destination files, file systems, or directories. When using wildcard characters in non-loop mode, as in
dsmc sel "/home/*"
enclose the parameter containing the asterisk in quotes to ensure the
system does not interpret the wildcard character and produce unexpected
results. Wildcard character information is covered in the following
table.
* (Asterisk) | Zero or more characters that match all files: |
---|---|
*.exe | With an exe extension |
hm*.* | Starting with hm, regardless of extension |
hm* | Starting with hm, whether an extension exists or not |
*h*.* | With an h somewhere in the file name, regardless of extension |
? (Question mark) | One character that matches all files with: |
---|---|
?.exe | The extension exe with one, and only one, character in the file name |
hm?.exe | Three-character names beginning with hm and that have the exe extension |
* ? (Asterisk and question mark) | Asterisk and question mark combinations matching: |
---|---|
??hm.* | All four-character file names ending in hm., no matter what extension they have |
In a path name for a file specification, you cannot specify a directory whose name contains an asterisk (*) or a question mark (?). Tivoli Storage Manager will recognize those characters only as wildcard characters.
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.
When you enter an unrestricted wildcard source file specification on the restore command and do not specify any options: inactive, latest, pick, fromdate, or todate, the client uses a slightly different method for retrieving 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. This request results in files and directories being returned directly from the server 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 command would be:
/home/mydocs/1999/*
An example of a restricted wildcard command would be:
/home/mydocs/1999/sales.*
When the client uses this method, the restore session is treated a bit differently. If the restore process is interrupted for any reason, such as a power outage or network failure, the server records the point at which the restore was interrupted. This record is known to the client as a restartable restore. It is possible to create 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.
The existence of a restartable restore inhibits further backups of that file system until the restartable restore is completed. If you attempt to repeat the restore that was interrupted or try to back up the destination file space, the attempt will fail because the original restore was not completed. 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 object not completely restored when the interruption occurred.
The differences between the standard restore process and the no query restore process are outlined below.
For more information on using the command line to begin restartable restores, see Restore. For help with performing restartable restores using a GUI, follow these steps:
Your administrator determines how many backup versions to maintain for each file on your workstation. Frequently, the administrator has maintains more than one version of each file. Having multiple versions of a file lets you restore older versions in case the most recent backup is damaged.
Tivoli Storage Manager considers the most recent backup version to be the active version. The most recent backup version is considered an inactive version if the file was deleted or excluded at the client and an incremental backup was run. Any other backup version is considered an inactive version. If you try to restore both an active and inactive version of a file at the same time, only the active version is restored.
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 display active and inactive backup versions:
dsmc query backup "/home/*" -inactive
To display active backup versions only, click Display active files only from the View menu.
To restore backup versions of individual files or subdirectories:
Use the restore command to restore files. Indicate the file you want to restore and where you want to restore it. If you do not indicate a destination, the files are restored to their original location.
For example, to restore the /home/monnett/h1.doc file to its original directory, enter:
dsmc restore /home/monnett/h1.doc
To restore it under a new name, use:
dsmc restore /home/monnett/h1.doc /home/monnett/h2.doc
If the file you want to restore is not 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, you need to use the latest option to tell the server to restore the most recent backup version. If you do not want the most recent version, use the pick and inactive options to get a list of backups from which you can select.
For example, if you want to restore the latest version of the deleted file /home/monnett/h1.doc, enter:
dsmc restore /home/monnett/h1.doc -latest
Add the subdir=yes option to the command if you need to restore the files in a directory and all of its subdirectories. For example, if you are recovering an entire file system (the /home file system in this case), you can restore all of the files using:
dsmc restore /home/ -subdir=yes
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 space, 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 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.
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, 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. Only an active copy of the object that exists prior to but not after the point-in-time date is restored to the system.
Notes:
When performing a point-in-time restore, consider the following:
To perform a point-in-time restore from the GUI client, use the following steps:
Note: If there are no backup versions of a directory for the point-in-time you specify, files within that directory that exist for that point-in-time are not restoreable from the GUI. However, you can restore these files from the command line. To ensure that you can view and restore all existing files from the GUI during a point-in-time restore, you must maintain the same number of backup versions for directories as days you are restoring back to.
You can start point-in-time restore from the command-line client using the pitdate and pittime options. You can use these options with the query and restore commands. For example, when you use the pitdate and pittime options with the query backup command, the date and time values specified in the pitdate and pittime parameters establish the point-in-time for which file information is returned. When you usepitdate 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.
You can use the following procedure to restore an image of your file system or raw logical volume. If you have run progressive incremental backups and image backups on your file system, you can perform an incremental restore of the file system. This process updates the original image with individual files backed up after the last image backup. Optionally, if files were deleted after the original backup, the incremental restore can delete those files from the base image.
Attention: Incremental backups and restores can be performed only on mounted file systems, not on raw logical volumes.
To restore a backup of your logical volume or raw logical volume image, perform the following steps:
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.
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.
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.tivoli.com/support/storage_mgr/tivolimain.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:
Notes:
Tivoli Storage Manager considers a backup set as one object containing the whole file structure. Files are copied down to the file space level, and you can perform partial restores. After a backup set is generated, it is not tracked by the Tivoli Storage Manager database. The 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.
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 is restored to the location you specify.
To restore a backup set, perform the following steps:
Note: 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.
Note: 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.
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.
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. To authorize another user to restore or retrieve your files:
See Set Access, Query Access, and Delete Access for information on using commands.
The Tivoli Storage Manager node you are authorizing must be registered with your Tivoli Storage Manager server.
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:
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.
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 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.
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:
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 Tivoli Space Manager for Unix Using the Hierarchical Storage Management Clients.
Note: Your administrator can schedule restore operations which can be very useful when you need to restore a large number of files.
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:
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.