Use the backup-archive client to store backup versions of your workstation files to a Tivoli Storage Manager server. You can restore these backup versions to your workstation if the original workstation files are lost or damaged. This chapter discusses various ways you can back up your files and how to restore these files when you need them.
All client backup and restore procedures in this chapter also apply to the Web client, except those listed in "Using the Web Backup-Archive Client". See "Starting a Web Client Session" for information on starting the Web client.
Unless otherwise specified, references in this manual to Windows 98 also include Windows Me. References to Windows NT also include Windows 2000.
See Table 3 for a list of primary tasks.
Table 3. Backing Up and Restoring Files
If you are a first-time user, or if you only back up files occasionally,
you can use the checklist in Table 4 for preliminary planning.
Table 4. Preliminary Steps for Backing Up Files
|
|
---|---|
___ | Decide whether you want to back up or archive files. See "Do You Want to Back Up or Archive Files?" for more information. |
___ | See "Pre-Backup Considerations" for important migration information concerning the Windows NT and Windows 2000 clients, and how you may increase performance prior to backing up files and directories. |
___ | Create an include-exclude list to specify files and directories you want to exclude from backup services. See "Using an Include-Exclude 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" |
___ | For additional backup considerations, see "Backup: Additional Considerations". |
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 Chapter 4, 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.
Your administrator might set up schedules to automatically perform back ups. See Chapter 5, Automating Tasks for information about checking and running schedules that are available to you. The following sections discuss how to back up files without 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 Chapter 6, "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 or the journal database (Windows NT, 2000) 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.
Perform a selective backup if you want to back up empty directories and their attributes. See Chapter 3, "Backing Up and Restoring" for more information.
If you install the journal engine service and it is running, then by default the incremental command performs a journal-based incremental backup on any journaled file systems. Tivoli Storage Manager does not use the journaling facility inherent in Windows NTFS 5 file systems or any other journaled file system.
The journal engine service records changes to an object or its attributes in a journal database. During a journal-based backup, the client obtains a list of files that are eligible for backup from the journal database. Journal-based backup can increase backup performance because the client does not scan the local file system or contact the server to determine which files to process. Journal-based backup also reduces network traffic between the client and server.
Tivoli Storage Manager filters the list based on the current include-exclude list and processes, expires, and updates the resulting files according to policy constraints, such as serialization. You can use the copy frequency attribute during a traditional full incremental backup. However, Tivoli Storage Manager ignores this management class attribute during a journal-based backup.
The journal engine service does not record changes in specific system files, such as pagefile, registry, etc., in the journal. Therefore, journal-based backup will not back up these files. See the journal service configuration file tsmjbbd.ini in the Tivoli Storage Manager installation directory for excluded system files. See the Appendix in Tivoli Storage Manager Installing the Clients, SH26-4119, for more information about the journal service configuration file tsmjbbd.ini.
To support journal-based backup, you must install the journaling engine service background process as a service on Windows NT and 2000 using the dsmcutil command or the client GUI setup wizard. See Tivoli Storage Manager Installing the Clients, SH26-4119, for more information about using the dsmcutil command to install the journal engine service.
To install and configure this service using the client GUI setup wizard, perform the following steps:
See Incremental for more information about journal-based backup.
Notes:
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. Tivoli Storage Manager does not back up changes to NTFS security information on Windows NT clients because the changes do not alter the last changed date and time.
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.
Tivoli Storage Manager backs up files if their size, permissions, modification date, or other attributes change. The server does not update the date and time of the last incremental.
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. A full incremental with journaling active takes less time to process than an incremental-by-date. 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.
Beginning with Tivoli Storage Manager Version 4.2, the Windows NT and Windows 2000 clients are Unicode enabled. New clients storing data on the server for the first time require no special set up. The server automatically stores files and directories as Unicode enabled. However, if your client already stores data on the server and you upgrade to the Windows NT, 2000 Version 4.2 client, you need to plan for the migration of files spaces to Unicode. For migration information, see Migrating to the Unicode-Enabled Client.
This involves renaming your file spaces on the server and creating new Unicode-enabled file spaces on the server using the autofsrename option. For detailed information about this option, see Autofsrename.
For additional information about working with Unicode-enabled file spaces, see the following references:
Incremental backup performance suffers if the workstation has a low amount of memory available prior to starting the backup. If your workstation is not memory constrained, specify the memoryefficientbackup No option in your client options file dsm.opt to provide the best performance.
If your workstation is memory constrained, specify the memoryefficientbackup Yes option in your options file. Specifying Yes reduces memory consumption but increases backup time. When you specify Yes, Tivoli Storage Manager backs up only one directory at a time. If performance remains poor, check your communication buffer settings and the communication link between your workstation and the server.
If you plan to perform a backup over a network device that has limited bandwidth, such as a modem, you can help reduce network traffic by using adaptive subfile backup. Adaptive subfile backup requires a version 4 server. Reducing traffic can also increase the speed of your backup. An adaptive subfile backup sends only changed portions of a file to the server during successive backup operations.
Perform the following steps to use adaptive subfile backup.
When you are ready to back up changes, adaptive subfile backup will occur as part of incremental and selective backups.
Adaptive subfile backups can significantly reduce the amount of data exchanged between client and server. For example, suppose while at your work location you back up a two megabyte report. Then, while traveling, you change the report and want to send only the changes back to the server at your work location. To accomplish this, you would simply connect to a modem and use adaptive subfile backup.
Remember that you must perform the original backup with subfile backup enabled so that the base file will be stored in the cache.
You can restore an adaptive subfile backup using the restore command. The server restores the base file and the changed (delta) subfile.
Usually, there are files on your disk that you do not want to back up. These files might be operating system or application files that you can easily recover by reinstalling the program, or any other file that you can easily rebuild.
Use the include and exclude options in the client options file dsm.opt to define which files to exclude from backup processing. Tivoli Storage Manager uses the include-exclude list during incremental and selective backups. Tivoli Storage Manager backs up any file that is not explicitly excluded. It is not necessary to use an include option to include specific files, unless those files are in a directory that you are trying to exclude.
The include-exclude list may contain items specified by the server. To view the contents of your include-exclude list, use the query inclexcl command.
For more information about setting up an include-exclude list, see Chapter 7, "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 include.encrypt option, see Include Options. For more information about the exclude.encrypt option, see Exclude 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 the Registry by using the encryptkey option.
While restoring an 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.
See "Backup: Additional Considerations" for additional information to consider when performing a backup. You do not need to understand this information to perform basic backups.
The Tivoli Storage Manager Backup and Restore windows provide an estimate function that estimates the amount of time required to process your files and directories. The estimated transfer is a rough calculation of the time it takes to transfer your data. This estimate is based on previous transfers of data between your workstation and the current Tivoli Storage Manager 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.
The Estimated Transfer Time is based on previous backup transfer rate, so you must run at least one backup operation first. The Estimated Transfer Time field reads N/A if no files are sent to or from the current Tivoli Storage Manager server. The estimate function also 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.
Note: During installation, Tivoli Storage Manager creates the dsm.ini file to record statistics from the backup-archive client estimate function. This file resides in the client directory.
You can use Tivoli Storage Manager to 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 that match the filter criteria for your backup. Files that do not match the filter criteria do not display.
To perform a GUI backup, use the following steps:
To search:
To filter:
To perform subsequent incremental backups, you can select Actions >Backup Domain from the Tivoli Storage Manager main window.
When you start Tivoli Storage Manager, it sets your default domain to the drives you specify with the domain option in the dsm.opt file (see Domain). If you do not set the domain option, the default domain is all local fixed drives (the drives in your workstation).
Tivoli Storage Manager automatically selects your default domain as the drive or drives that you want to process. You can specify additional drives. For example, if your default domain contains drives c: and d:, and you want to back up those drives as well as the diskette in drive a:, enter:
dsmc incremental -domain="a:"
You can also use the Backup Domain function in the GUI to perform these backup functions.
Certain Windows NT and Windows 2000 system objects must be backed up together in order to create a consistent system state. You must be using a server that is Version 3.7.3 or higher. Servers at this level support the file grouping required to back up system objects. Objects can be backed up in any order.
System objects which must be backed up together include the following:
Other system objects can be backed up individually. These include the following:
To back up system objects using the GUI, select the desired entries under the system objects tree view of the backup window.
See "Backup: Additional Considerations" for additional information to consider when performing a backup. You do not need to understand this information to perform basic backups.
You can use the incremental or selective commands to perform backups. For information on the commands to use for backing up system objects, see Chapter 10, "Using Commands".
See "Full Incremental Backup" for detailed information about incremental backups.
To back up the c: drive, for example, enter:
dsmc incremental c:
Use the incrbydate option with the incremental command to run an incremental backup by date, by entering:
dsmc incremental -incrbydate
You can back up specific files, a group of files with similar names, or empty directories and their attributes. This is called a selective backup. You can use wildcards to back up more than one file at a time.
You can select the files you want to back up by specifying the path, name, and extension of the file.
If you back up a directory, use the subdir=yes option to include all the subdirectories under that directory in the backup. For example, to back up the d:\proj directory and its subdirectories, enter:
dsmc selective d:\proj\ -subdir=yes
To back up files under the proj directory, enter:
dsmc selective d:\proj\
You can enter up to 20 file names on the selective command by entering a space between each file name. For example, to back up the d:\h1.doc and d:\test.doc files, enter:
dsmc selective d:\h1.doc d:\test.docIf you want to specify more than 20 file names, you can use the filelist option. See Filelist for more information about this option.
When you run a selective backup, Tivoli Storage Manager also backs up the file attributes, directory information, and last changed date. This information is restored when you restore the file. You can exclude the files within a directory, and you can exclude an empty directory from backup. Directories are counted in the number of files backed up.
When you request a selective backup, Tivoli Storage Manager backs up a file if all of the following requirements are met:
See Selective for more information about the selective command.
See "Backup: Additional Considerations" for additional information to consider when performing a backup. You do not need to understand this information to perform basic backups.
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 volume 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:
Tivoli Storage Manager Version 4.2 Windows NT and Windows 2000 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 Windows 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 A, "Backing Up NAS File Systems" for more information.
This section discusses additional information to consider when performing a backup. You do not need to understand this information to perform basic backups.
Some files on your system might be in use when you try to back them up. These are called open files because they are opened by an application for its use. Because an open file can change, any backup of that file will not correctly reflect its contents at a given time.
If certain files are not backed up because they are open and they change when you try to back them up or when the backup schedule starts, consider the following points:
Tivoli Storage Manager backs up your removable media (such as tapes, cartridges or diskettes) based on the drive label, not the drive letter. If a drive has no label, the backup does not occur. This use of drive labels permits you to perform such tasks as backing up different diskettes from the a: drive.
For a restore or retrieve, Tivoli Storage Manager maintains a separate file space for each drive label. These labels become the file space names on the server. If you change the label of a drive you already backed up, Tivoli Storage Manager views it as a new drive and does not relate it to your previous drive.
Because Tivoli Storage Manager uses the labels to manage backups and archives of your removable media, you occasionally need to use those labels to locate data when using commands. For example, if you try to restore a file on diskette or CD-ROM using d:\projx\file.exe as a file name, Tivoli Storage Manager substitutes the current label of your d: drive for the d:. If the d: drive label is d-disk, d:\projx\file.exe becomes {d-disk}\projx\file.exe, and the label is enclosed in braces.
If the label of the d: drive does not match a file space name on the server, Tivoli Storage Manager cannot find your files. A mismatch between a label and a file space name might occur if you label your drives again, or if you access Tivoli Storage Manager from a different workstation than the one from which you backed up the files. If you have not relabeled the drive, and you are at the same workstation where the file was backed up, then you can use the drive letter as a shorthand version of the file space name (drive label).
Tivoli Storage Manager can back up your fixed drives even if they do not have a label, including drive aliases created with the DOS subst command. This applies to both the drive alias and the underlying physical drive, because the alias name and the physical drive label are the same.
When you back up Windows NT files on NTFS partitions, Tivoli Storage Manager also backs up file security information and these file descriptors:
You must specify a mixed or lowercase NTFS file space name enclosed in quotes and braces. For example, {"NTFSDrive"}. Single quotes or double quotes are valid in loop mode. For example: {"NTFSDrive"} and {'NTFSDrive'} are both valid. In batch mode, only single quotes are valid. The single quotes requirement is a restriction of the operating system.
A Universal Naming Convention (UNC) name is a network resource name for a share point on a workstation. The resource name includes the workstation name assigned to the workstation and a name you assign to a drive or directory so that it can be shared. The name you assign is also called a share point name.
The following rules apply when using UNC names to specify a domain list. You must specify:
Example 1: To specify drive a: containing removable media, enter
domain a: \\local\c$
Example 2: To specify fixed drive c:, enter
domain c: \\remote\share1 \\remote\c$
You can back up shared files in a network through the use of a UNC name. A UNC name is a network resource name for a share point on a workstation. The resource name includes the workstation name assigned to the workstation and a name you assign to a drive or directory so that it can be shared. The name you assign is also called a share point name.
Using a UNC name permits you to back up specific shared directories to a separate file space. This is useful if, for example, you or an administrator want to back up a small portion of data that you would otherwise be unable to access. Drives are not backed up to a separate file space.
On Windows NT and Windows 2000, every local drive is accessible via a UNC name except for drives containing removable media (such as tapes, cartridges or diskettes). Access these drives by using a predefined administrative share name consisting of the workstation name and the local drive letter, followed by $. For example, to specify a UNC name on drive c: for workstation ocean, enter:
\\ocean\c$
The $ sign must be included with the drive letter.
To enter a UNC name for workstation ocean and share point wave, enter:
\\ocean\wave
When accessing files, you do not need to enter the letter of the drive except for drives containing removable media.
See Table 5 for examples showing selective backup of files using UNC names. In these examples, assume that:
Example | Comment |
---|---|
dsmc sel \\alpha1\c$\ | name of remote file space is \\alpha1\c$ |
dsmc sel \\major\c$\ | name of local, fixed file space is \\major\c$ |
dsmc sel a:\ | name of local, removable file space is volume label of a: |
dsmc sel \\alpha1\betarc\ | name of remote file space is \\alpha1\betarc |
dsmc sel \\alpha1\testdir\ | name of remote file space is \\alpha1\testdir |
dsmc sel d:\ | name of local, fixed file space is \\major\d$ |
dsmc sel c:\ | file space name is \\major\c$ |
dsmc sel r:\ | file space name is \\alpha1\betarc |
You can also specify UNC names for files in your include-exclude and domain lists; see Chapter 7, "Creating an Include-Exclude List" and Domain for more information.
Note: This feature applies to Windows 2000 with NTFS file systems only.
If your organization uses the Microsoft Distributed File System (Dfs) server component for Windows 2000, you can back up and archive all your Microsoft Dfs files as a single file system, even if the files are on different servers and share points. Files contained on a Dfs server component are accessed using a standard UNC name, for example:
\\servername\dfsroot\
where servername is the name of the host computer and dfsroot is the name of the root file system.
If your organization uses the Microsoft directory services feature of Dfs, you can access a file system through either its fault tolerant domain name or its server name, for example:
\\default tolerant name\dfsroot\
where default tolerant name is a name your administrator has designated to specify a Microsoft Dfs server component stored in directory services, and dfsroot is the name of the root file system.
By default, an incremental backup of a DFS root does not traverse the Dfs junctions. Only the junction metadata is backed up.
You can use the dfsbackupmntpnt option to specify whether Tivoli Storage Manager sees a Dfs mount point as a Microsoft Dfs junction or as a directory. For more information on using this option, see Dfsbackupmntpnt.
To restore Dfs junctions and the data for each junction, restore the Dfs junction metadata first and then restore each junction separately. If the junction metadata is not restored, Tivoli Storage Manager creates a directory under the Dfs root using the same name as that of the junction point and restores the data in that directory.
Tivoli Storage Manager uses the methods described in this section to restore backup versions of specific files, a group of files with similar names, or entire directories.
If parent directories exist above the subdirectory branch and the parent directories do not exist at the target of the restore, then the parent directories are created but their permissions are not restored. This only applies to directories; attributes/permissions for files are always restored. For example, if you have a backup of the following directory structure:
a a\b a\b\c a\b\d
and, if you want to restore subdirectory branch b, and a does not exist, then a is created with default permissions restored. Tivoli Storage Manager will restore permissions for subdirectories b, c, and d.
If you attempt to restore or retrieve a file whose name is the same as an existing file's short name, a file name collision will occur (existence of duplicate file names). An example is when the file abcdefghijk.doc has a short name of abcdef~1.doc, and you attempt to restore or retrieve a file explicitly named abcdef~1.doc into the same directory. In this case, a collision will occur because the name of the file you are restoring conflicts with the short name for abcdefghijk.doc. Tivoli Storage Manager handles this situation based on the value of the replace option.
A collision can occur even if the files are restored or retrieved to an empty directory. For example, files abcdef~1.doc and abcdefghijk.doc may originally have existed in the directory as abcdefghijk.doc and abcdef~2.doc. During the restore, if abcdefghijk.doc is restored first, it is assigned a short name of abcdef~1.doc by the Windows operating system. When you restore abcdef~1.doc, the duplicate file name situation occurs.
If a file name collision occurs, you can do any of the following:
Using a UNC name permits you to restore specific shared files to a separate file space. This is useful if, for example, you or an administrator want to restore a portion of data that you would otherwise be unable to access.
Except for drives with removable media, every local drive letter is accessible using a local UNC name that includes the workstation name and a designation for the drive letter. For example, to enter a UNC name on drive c: for workstation ocean, enter:
\\ocean\c$
The $ sign must be included with the drive letter.
To enter a UNC name for workstation ocean and share point wave, enter:
\\ocean\wave
When accessing files, you do not need to enter the letter of the drive except for drives with removable media.
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. 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/inactive files item again. If you try to restore both an active and inactive version of a file at the same time, only the active version is restored.
You can restore specific files, a group of files with similar names, or directories. You can locate the files you want to restore by searching and filtering. Filtering displays only the files that match the filter criteria for your restore operation. Files that do not match the filter criteria do not display. The filter process searches files in the specified directory but does not include subdirectories.
To restore files or directories, perform the following steps:
To search:
To filter:
Certain Windows NT and Windows 2000 system objects must be restored together in order to create a consistent system state. It is recommended that you restore boot files first and commit the system hive of the registry last.
The following system objects should be restored together:
Other system objects can be restored individually. These include the following:
To restore system objects using the GUI, select System Objects> system object name from the Restore menu and follow the prompts.
You can use the restore command to restore files. For information on the commands for restoring system objects, see Chapter 10, "Using Commands".
You must specify the files you want to restore and where you want to restore them. If you do not specify a destination, the files are restored to their original location. For example, to restore the c:\doc\h2.doc file to its original directory, enter:
dsmc restore c:\doc\h2.doc
To restore it under a new name, enter:
dsmc restore c:\doc\h2.doc c:\doc\h3.doc
For the purposes of this manual, the workstation name is part of the file name. Therefore, if you back up files on one workstation and you want to restore them to another workstation, you must specify a destination. This is true even if you are restoring to the same physical workstation, but the workstation has a new name. For example, to restore the c:\doc\h2.doc file to its original directory on the workstation, named star, enter:
dsmc restore c:\doc\h2.doc \\star\c$\
To restore the file to star which has now been renamed meteor, enter:
dsmc restore \\star\c$\doc\h2.doc \\meteor\c$\
You could also enter:
dsmc restore c:\doc\h2.doc \\meteor\c$\
This example is valid because if the workstation name is not included in the specification, the local workstation is assumed (meteor, in this case).
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. If you do not want the most recent version, use the pick and inactive options to obtain a list of backups from which you can pick. For example, if you want to restore the latest version of the deleted file c:\doc\h2.doc, enter:
dsmc restore c:\doc\h2.doc -latest
If you are restoring a file to a disk with a different label than the disk from which the file was backed up, you must use the file space name (label) of the backup disk instead of the drive letter. For example, if you backed up a file from the a: drive from the diskette workathome, and you are restoring it to a diskette in the a: drive labeled extra, enter:
dsmc restore {workathome}\doc\h2.doc a:\doc\h2.doc
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 disk (the e: disk in this example) and restoring all the files, enter:
restore e:\ -subdir=yes
With Windows NT, if you need to restore a large number of files, you will get faster performance using the command line interface rather than the GUI interface. In addition, you will improve performance if you enter multiple restore commands at one time. For example, to restore all the files in your c: file space, enter:
dsmc restore c:\* -subdir=yes -replace=all -tapeprompt=no
However, if you enter multiple commands for the root directories in your c: file space, you can restore the files faster. For example, enter these commands:
dsmc restore c:\users\ -subdir=yes -replace=all -tapeprompt=no dsmc restore c:\data1\ -subdir=yes -replace=all -tapeprompt=no dsmc restore c:\data2\ -subdir=yes -replace=all -tapeprompt=no
Or, if you need to restore files for multiple drives, enter these commands:
dsmc restore c:\* -subdir=yes -replace=all -tapeprompt=no dsmc restore d:\* -subdir=yes -replace=all -tapeprompt=no dsmc restore e:\* -subdir=yes -replace=all -tapeprompt=no
You can also use the quiet option with the restore command to save processing time. However, you will not receive informational messages for individual files.
When you enter multiple commands to restore your files, you must specify a unique part of the file space in each restore command. Do not use any overlapping file specifications in the commands.
To display a list of the root directories in a file space, use the query backup command. For example:
dsmc query backup -dirsonly -subdir=no c:\
As a general rule, you can enter 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 network utilization and how much memory you have. For example, if \users and \data1 are on the same tape, the restore for \data1 must wait until the restore for \users is complete. However, if \data2 is on a different tape, and there are at least two tape drives available, the restore for \data2 can begin at the same time as the restore for \users.
The speed at which you can restore the files also depends upon how many tape drives are available and whether your administrator is using collocation to keep file spaces assigned to as few volumes as possible. If your administrator is using collocation, the number of sequential access media mounts required for restore operations is also reduced.
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:
c:\mydocs\1999\*
An example of a restricted wildcard command would be:
c:\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 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 Windows NT 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.
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.
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.
This section discusses additional considerations for restoring data. You do not need to understand this information to use Tivoli Storage Manager for basic work.
You can authorize a user on another node to restore your backup versions or retrieve your archive copies. This lets you share files with other people or with other workstations that you use with a different node name. To authorize another node to restore or retrieve your files:
The node you are authorizing must be registered with your Tivoli Storage Manager server.
You can also use the set access command to work with your user access list. Use the query access command to display your current list and delete access to delete users from the list. For more information on these commands, see:
After users give you access to their files on the server, you can restore or retrieve those backup versions to your local drives (if the other user has authorized you to do so). To do this:
If you are using commands, use the fromnode option to indicate the node. You must also use the file space name, rather than the drive letter, to select the restore-retrieve drive you want to access. Include the file space name in braces and use it like a drive letter. For example, to restore cougar's files from the projx directory on the d-disk file space to your own projx directory, enter:
dsmc restore -fromnode=cougar {d-disk}\projx\* d:\projx\
Use the query filespace command to obtain a list of file spaces. For example, to obtain a list of cougar's file spaces, enter:
dsmc query filespace -fromnode=cougar
For more information about using the fromnode option with the restore command, see Restore. See Retrieve for the retrieve command. For more information about the fromnode option, see Fromnode.
When you are using a different workstation, you can restore or retrieve files you backed up from your own workstation. Your backup versions and archive copies are stored according to your node, not your specific workstation. Your Tivoli Storage Manager password protects your data.
To restore or retrieve files to another workstation, use the nodename option to specify the node name of the workstation from which you backed up the files. You can use the nodename option when starting Tivoli Storage Manager or place the option in your client options file dsm.opt on the workstation. If you are using a workstation other than your own, use the nodename option with the dsm command. For example, if your node name is cougar, enter:
start dsm -nodename=cougar
You can then restore or retrieve files as if you were working on your original workstation.
You can use nodename on commands also. For example, if you want to restore your projx files, enter:
dsmc restore -nodename=cougar {d-disk}\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.
Because the file formats used on Windows NT, 98, and Me are compatible, you can restore or retrieve files from one system type to another. This is called cross-client restore. For example, if you archive a file from a Windows NT workstation, you can retrieve that file to a Windows 98 workstation.
Attention: You must have the appropriate permissions to access the file spaces of the other workstation, as explained in Authorizing Another User to Restore or Retrieve Your Files and Restoring or Retrieving Another User's Files.
Although each client can recover data from each of these file systems, some restrictions apply when recovering files that were backed up or archived from a drive that the client does not support. For example:
Windows NT clients have no restrictions when recovering files from Windows 98 clients; however, unique Windows 2000 attributes may be lost during recovery.
Windows 2000 clients have no restrictions when recovering files.
When you use the Windows NT, 98, or Me client to recover files with long names to an NTFS disk, the long names are preserved, even if you are recovering the file to a different type of drive than the source drive.
The considerations for retrieving files are the same as for restoring them.
Tivoli Storage Manager only recovers your files if you run the client. If the disk that contains the client is lost, you must reinstall the client before you can recover your files.
If your administrator has created a backup set of your files on portable media, you can use that set to recover the files without the use of a server. See "Restoring Data from a Backup Set" for information on backup sets.
If you lose the disk containing the operating system, you must recover the operating system before you can connect to the server.
To protect yourself against these kinds of losses, you should have available the operating system installation media or a software installation mechanism that you used to build the workstation originally. Alternatively, you may be able to assemble a set of diskettes to repair or boot your system to a condition that permits you to contact the server and begin recovering data. Depending on your environment, these diskettes may need to contain some or all of the following items:
Windows 98, Me, and 2000 provide a "safe mode" start-up that allows you to boot to a command line prompt.
The exact files you need differ depending on the communication package you use. Consult your operating system and communication software manuals for help in setting up these diskettes.
If you have large volumes of data that may need to be recovered, your administrator may want to create a backup set of those files on portable media. You can then use that set to recover the files without using a server. See "Restoring Data from a Backup Set" for information on backup sets.
If your Tivoli Storage Manager administrator grants 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, both backup versions and archive copies, that are contained within the file space. For example, if you delete the file space for your c: drive, you are deleting every backup for every file on that disk and every file you archived from that disk. Carefully consider what you are doing before you attempt to delete a file space.
You can delete file spaces using the 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 client, 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.