This chapter covers how to perform backup and restore tasks. See Table 3 for a list of primary tasks.
Table 3. Backing Up and Restoring Files
Note: | Unless otherwise specified, references in this manual to Windows 95 also include Windows 98. References to Windows NT also include Windows 2000. |
A primary function of TSM is to maintain a set of backup versions for your workstation. This permits you to recover older versions of your files if those files are lost or damaged. This chapter discusses the various ways you can back up your files, how you can restore them, and the difference between backing up and archiving files.
TSM provides an Estimate function on the Backup and Restore windows which are accessible from the TSM main window. Use this function if you want TSM to estimate the amount of time it takes to process your files and directories. The estimated transfer is a rough calculation of the time it takes to transfer 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 such as network traffic, system load on your workstation, or system load on the server.
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
|
|
---|---|
&box. | Decide whether you want to back up or archive files. See "Do You Want to Back Up or Archive Files?" for more information. |
&box. | If your workstation has limited memory, decide whether performance is important. See "Running Incremental Backups On Memory-Constrained Machines" for more information. |
&box. | Create an include-exclude list to specify files and directories you want to exclude from backup services. See "Controlling Processing With the Include-Exclude List" for more information. |
&box. | Decide what type of backup you want according to your needs. See the following sections for more information: "Full Incremental", "Partial Incremental", and "Full Incremental Versus Partial Incremental" |
&box. | If a file is important, ensure that it is closed before backing it up. See "Backing Up Open Files" for more information. |
&box. | For further backup considerations, see "Additional Considerations". |
When TSM 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 (the number of backup versions is set by your administrator), and older versions are deleted as newer versions are made.
Archive copies are more permanent. They maintain a file in a particular state indefinitely (although your administrator can limit how long archives are kept). They are useful if you need, for example, to go back to a particular version of your files, or if 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 archives for maintaining more permanent versions of your files.
Your administrator might set up schedules to automatically perform back ups. See Chapter 5, Automating TSM 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.
When you request an incremental backup, TSM backs up a file if all of the following requirements are met:
When you run an incremental backup, TSM also backs up all directory information. When you back up a file, the directories in the path in which that file is contained are also backed up. Directories are counted in the number of objects backed up.
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 maintaining current server storage of your workstation files according to your storage management policies. See Chapter 6, "Understanding Storage Management Policies" for more information about storage management polices.
To perform a full incremental backup select the Incremental (complete) option from the type of backup pull-down menu on the TSM backup window, or use the incremental command. You must specify one or more file systems to include in the back up.
During a full incremental, the client queries the server to determine the exact state of your storage as of your last incremental. TSM uses this information to:
To ensure that a file retains the attributes it had before being backed up, use a selective back up. For information on the selective command, see Selective.When you restore a file, TSM restores the attributes to what they were when you backed up the file.
When you run an incremental backup, TSM also backs up all directory information. You can exclude the files within a directory, and you can exclude a directory from being backed up. To exclude directories from backup, use the exclude.dir option. For more about exclude.dir, see Exclude Options. Directories that match the exclude.dir specification are not displayed in the backup-archive GUI.
Directories are counted in the number of files 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).
A partial incremental backs up new and changed files but does not expire or rebind files on the server, and it ignores the frequency attribute of the copy group. 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. Changes to NTFS security information on Windows NT clients are not backed up 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 an incremental-by-date is performed on only part of a file system, the date of the last full incremental is not updated, and the next incremental-by-date will back up these files again.
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. However, unlike a full incremental, an incremental-by-date does not maintain current server storage of all your workstation files because:
For these reasons, if you have limited time during the week to perform backups, but extra time on weekends, you may want to maintain current server storage of your workstation files by performing a partial incremental backup on weekdays, and a full incremental backup on weekends.
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.
References to Windows NT in this manual also include Windows 2000, unless explicitly stated otherwise.
Notes:
For help in performing any task within a graphical user interface, place your cursor on the field or option of interest, and press F1. You can also select the How do I? item from the Help menu.
To perform a backup of your new or changed files and directories:
TSM informs you when the backup is complete. The first time you perform an incremental backup, TSM must back up all your files, which can take a long time. Subsequent backups usually do not take as long.
To perform subsequent incremental backups, you can select Actions >Backup Domain from the TSM main window.
Note: | If you perform an incremental backup on a domain containing the system drive or on the system drive, itself, the Windows registry will also be backed up. |
You can perform an incremental backup from the command line with the incremental command. To back up the c: drive, for example, enter:
dsmc incremental c:
If you do not indicate the drives to back up, TSM uses your default domain. See Specifying Drives in Your Domain for more information on the default domain. See Incremental for more information about the incremental command.
To start an incremental backup by date, add the incrbydate option:
dsmc incremental -incrbydate
The performance of an incremental backup suffers if your machine has a low amount of memory available prior to starting the backup. If your machine is not memory-constrained, you can use a more efficient method of backup. Specify the memoryefficientbackup No option in your options file. Specifying No provides the best performance for machines with sufficient memory.
If your machine is memory-constrained, specify the memoryefficientbackup Yes option in your options file. Specifying Yes reduces memory consumption but increases backup time. TSM backs up only one directory at a time. If you have poor performance even when using memoryefficientbackup Yes, check your communication buffer settings and the communication link between your machine and the server.
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 could be easily recovered by reinstalling the program, or any other file that you could easily rebuild.
Use the include and exclude options in the TSM options file to define which files to exclude from backup processing. TSM honors the include-exclude list whether you are performing an incremental or selective backup. TSM 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.
For more information about setting up an include-exclude list, see Chapter 7, "Creating an Include-Exclude List".
The TSM Backup and Restore windows provide an estimate function that estimates the amount of time to process your files and directories. The estimated transfer is a rough calculation of the time it takes to transfer your data. It is based on previous transfers of data between your workstation and the current TSM 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.
Note: The Estimated Transfer Time is based on previous backup transfer rates so you must run at least one backup operation first. The Estimated Transfer Time filed reads N/A if no files are sent to or from the current TSM server.
When you start TSM, 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 have the domain option set, the default domain is all local fixed drives (the drives in your workstation).
TSM automatically selects your default domain as the drives that you want to process, and you can add drives. For example, if your default domain contains drives c: and d:, and you want to back up those drives and the diskette in drive a:, enter:
dsmc incremental -domain="a:"
You can also use the Backup Domain function in the GUI to perform these back up functions.
A universal naming convention (UNC) name is a network resource name for a share point on a machine. The resource name includes the machine name assigned to the machine 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$
TSM backs up your removable media (such as tapes, cartridges or diskettes) based on the drive label. TSM does not use the drive letter. If a drive has no label, TSM cannot back up the media. This use of drive labels permits you to perform such tasks as backing up different diskettes from the a: drive.
Each drive label results in TSM maintaining a separate file space for a restore or retrieve. These labels become the names of file spaces on the server. If you change the label of a drive you already backed up, TSM views it as a new drive and does not relate it to your previous drive.
Because TSM uses the labels to manage backups and archives of your removable media, you occasionally need to use those labels to locate data when using TSM commands. For example, if you try to restore a file on diskette or CD-ROM using d:\projx\file.exe as a file name, TSM 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, TSM cannot find your files. A mismatch between a label and a file space name might happen if you label your drives again, or if you access TSM 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).
TSM 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.
Note: | You must specify a mixed or lowercase NTFS file space name enclosed in quotes and braces. For example, {"NTFSDrive"}. If TSM is running in loop mode, then either single quotes or double quotes are valid. For example: {"NTFSDrive"} and {'NTFSDrive'} are both valid. If TSM is running in batch mode, only single quotes are valid. The single quotes requirement is a restriction of the operating system. |
Some files on your system might be in use when you try backing 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 backing them up or when the backup schedule starts, consider the following points:
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 locate the files you want by using search and filter features.
You can select the files you want to back up by
When TSM backs up a file, it also backs up the file attributes, directory information, and last changed date. These items are restored when you restore the file.
When you back up Windows NT files on NTFS partitions, TSM also backs up file security information and these file descriptors:
To back up a file or a group of files, follow these steps:
Use the selective command to back up specific files. Use wildcards to back up more than one file at a time. 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 use more than one file name on the selective command. For example, to back up the d:\h1.doc and d:\test.doc files, enter:
dsmc selective d:\h1.doc d:\test.doc
When you request a selective backup, TSM backs up a file if all of the following requirements are met:
When you run a selective backup, TSM also backs up all directory information. 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.
See Selective for more information about the selective command.
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 machine. The resource name includes the machine name assigned to the machine 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.
Except for drives containing removable media (such as tapes, cartridges or diskettes), every local drive is accessible using a predefined administrative share name consisting of the machine name and the local drive letter followed by $. For example, to specify a UNC name on drive c: for machine ocean, enter:
\\ocean\c$
The $ sign must be included with the drive letter.
To enter a UNC name for machine 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 back up 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, TSM does not traverse the Dfs junctions when doing an incremental backup of a Dfs root. Only the junction metadata is backed up.
You can use the dfsbackupmntpnt option to specify whether TSM 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, TSM will create a directory under the Dfs root using the same name as that of the junction point, and restore the data in the directory it has created.
If you plan to perform a backup over a network device that has limited bandwidth, such as a modem, you can help reduce the traffic on that network by using adaptive subfile backup. 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 instead of sending the entire file. Differencing technology is used to determine which portion of file data has actually changed since the last backup.
An adaptive subfile backup is enabled through the subfilebackup option that you specify in the client options file. You must also specify subfilecachep and subfilecaches in order to tell TSM the path and size of the data to be transferred. Adaptive subfile backups occur as part of incremental and selective backups; therefore, in order to use this feature, you must first specify the adaptive subfile backup options during a normal backup. For more information on adaptive subfile backup options, see Chapter 8, "Setting Common Options".
Perform the following steps to use adaptive subfile backup.
Using adaptive subfile backups can significantly reduce the amount of data exchanged between client and server. For example, suppose while at your work location you backed up a 2 megabyte report. Then, while traveling, you change the report and want to send only the changes back to the server at your work location. You would simply connect to a modem and use adaptive subfile backup.
You can restore an adaptive subfile backup using the restore command.
This section discusses additional information to consider when performing a backup. You do not need to understand this information in order to do basic backups.
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 this option, see Chapter 8, "Setting Common Options".
To encrypt file data, you must select an encryption key password which TSM uses to generate the encryption key for encrypting and decrypting the file data. TSM requires that you remember the encryption key password. You can configure the encryption key password to be saved in the registry by using the encryptkey option. For information about this option, see Chapter 8, "Setting Common Options".
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:
For information on the commands to use for backing up system objects, see Chapter 10, "Using Commands". To back up system objects using the GUI, select System Objects><system object name> from the Backup menu, and follow the prompts.
Select File details on the View menu to display file attributes for any highlighted file.
When TSM 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 the server.
The Web client and backup-archive client GUI provide a Task List window that displays information about files that are processing. The backup-archive command line displays similar information.
When a task completes, a Task Report window displays processing details. You can click the Help button in the Task Report window for information about the following processing statistics:
The command line displays the name of each file after it is sent to the server. If a file is not sent immediately, a progress indicator displays the file's progress.
TSM uses the methods described in this section to restore backup versions of specific files, a group of files with similar names, entire directories, or backup sets.
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. TSM 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). For example, if 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. The collision will occur because the name of the file you are restoring conflicts with the short name for abcdefghijk.doc. TSM handles this situation based on how the replace option is specified.
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 TSM attempts to restore abcdef~1.doc, the duplicate file name situation occurs.
To correct a situation where file name collision has occurred, you can do any of the following:
You can use a directory tree to display only those files matching search and filter criteria that you specify. The filter process searches files in the specified directory but does not include subdirectories.
To restore a file using a directory tree (directory attributes and permissions are not restored):
You can use TSM to restore specific files, a group of files with similar names, directories, or backup sets.
You can copy a version of a backup file from a storage pool to your workstation or file server without affecting the backup copy in the storage pool. If you know all or part of the name of the file you want to restore, you can search for the name and use it to restore the file. When you restore a file using the file name, directory attributes and permissions are not restored.
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 are not displayed.
To search or filter files during a restore operation, perform the following:
To restore backup versions of individual files or subdirectories along with directory attributes and permissions:
Your administrator determines how many backup versions TSM maintains for each file on your workstation, and more than one is often maintained. Having multiple versions of a file permits you to restore older versions in the event the most recent backup is damaged. TSM considers the most recent backup version to be the active version. Any other backup version is considered to be an inactive version. To restore a backup version that is inactive, you must display both active and inactive versions.
If you try to restore both an active and inactive version of a file at the same time, only the active version will be restored.
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 machine name and a designation for the drive letter. For example, to enter a UNC name on drive c: for machine ocean, enter:
\\ocean\c$
The $ sign must be included with the drive letter.
To enter a UNC name for machine 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 TSM administrator can generate a backup set (a collection of your active files that reside on the server) onto portable media that are supported by both the server and client.
Portable media can be used on devices such as a tape, CD-ROM, DVD, 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 either of the following locations:
Note: | If you cannot restore a backup set from portable media, check with your TSM administrator to ensure that the portable media was created on a device using a format that is compatible with your device. |
TSM 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 TSM database. The media is self-describing and contains all the information required to perform a successful restore.
Backup sets can provide you with instant archive and rapid recovery capability as described below:
See Restore Backupset for information on how to use the restore backupset command.
Note: | Before you begin a restore, be aware that backup sets can contain data for multiple filespaces. If you specify a destination other than the original location, data from all filespaces is restored to the location you specify. |
To restore a backup set, perform the following steps:
A point-in-time restore recovers a file space or a directory to a previous condition. For example, a point-in-time restore can eliminate the effect of data corruption, or recover a basic configuration to a prior condition.
To start a point-in-time restore from the backup-archive GUI, select the Point-in-Time date from the Restore window. A point-in-time restore can be started from the backup-archive command line client using the pitdate and pittime command line options.
A point-in-time restore is supported on the file space, directory, or file level. When a point-in-time restore is performed, files that were created on the client after the point-in-time date are not deleted.
Perform incremental backups to a Version 3 or higher server in order to support a point-in-time restore. The server is only notified when files are deleted from a client file space or directory during an incremental backup. Run incremental backups frequently to provide the necessary point-in-time resolution. A point-in-time restore restores files that were deleted after the point-in-time date, but not files deleted before the point-in-time date. Ensure the point-in-time date that you specify is not the same as the time and date that a backup was performed.
Point-in-time overrides object condition so that even if an object has an active backup from a later date, the previous inactive copy is returned.
The point-in-time command-line options, pitdate and pittime, are used with the query and restore commands. For example, when the pitdate and pittime options are used with the query backup command, the date and time values specified with pitdate and pittime are used to establish the point-in-time for which file information is returned. When pitdate and pittime are used with the restore command, the specified date and time values are used to establish the point-in-time for which files are returned. The pitdate and pittime values are mutually exclusive from the todate and totime parameters.
You can use the restore command to restore files. Indicate the files you want restored and where you want to restore them. If you are using a client version earlier than 3.1.0.5, and you do not indicate 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
If you are using client version 3.1.0.5 or later, the machine name is part of the file name. Therefore, if you back up files on one machine and you want to restore them to another machine, you must specify a destination. This is true even if you are restoring to the same physical machine, but the machine has a new name. For example, to restore the c:\doc\h2.doc file to its original directory on the machine, 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 c:\doc\h2.doc \\star\c$\ \\meteor\c$\
You could also enter:
dsmc restore c:\doc\h2.doc \\star\c$\
This example is valid because if the machine name is not included in the specification, the local machine 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 that has 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
Note: | You must use this option to restore directory attributes/permissions. |
Client functions such as point-in-time restore and restartable restores, use no query restore to address potential memory constraints. No query restore coexists with other restore protocols and is supported on all Version 3 servers and clients.
No query restore addresses potential memory constraints on the client. For clients with large file spaces the list of backed up files can become very large; too large for some clients to keep and sort in memory. No query restore gets its name from the fact that, when using this protocol, the client does not need to query the server for a list of backed up files, nor does the client need to perform a sort of the list of files returned.
When an entire directory or directory tree is restored, and the inactive, latest, pick, todate, and fromdate options are not specified on the restore command, TSM keeps track of which objects have been restored. If the restore process is interrupted for any reason, such as a power outage or network failure, you can restart the restore at the point of interruption by entering the restart restore command. It is possible to create more than one restartable restore session. Use the query restore command to display a list of your 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 using the restart restore command or the restartable restore is dropped using the cancel restore command.
The differences between the standard restore process and the no query restore process are described 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:
This section discusses additional considerations for restoring data. You do not need to understand this information in order to use TSM for basic work.
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:
For information on the commands for restoring system objects, see Chapter 10, "Using Commands". To restore system objects using the GUI, select System Objects>system object name from the Restore menu, and follow the prompts.
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 TSM node you are authorizing must be registered with your TSM server.
You can also use the set access command to work with your authorization 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.
You can restore or retrieve files you back up from your own workstation when you are using a different workstation. Your backup versions and archive copies are stored according to your node, not your specific machine. Your TSM 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 TSM, or update the options file on the machine. If you are using a machine other than your own, use the nodename option with the dsm command so you do not change the configuration. 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, Windows 95, and Windows 98 are compatible, you can restore, retrieve or archive files from one type of system to another type of system. 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 95 or Windows 98 workstation.
Note: | 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 95 and 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, Windows 95, or Windows 98 client to recover files with long names to an HPFS or NTFS disk, the long names are preserved, even if you are recovering the file to a different type of drive than the source drive (for example, NTFS to HPFS).
The considerations for retrieving files are the same as for restoring them.
TSM 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 and communication software, you must recover them before you can connect to the server.
Attention: 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 machine, 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 2000 and Windows 95 and 98 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.
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. 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, TSM 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 more 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 options file, it is not necessary to include these 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. 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
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 TSM 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.
If your administrator gives your client node backdelete authority, you can delete entire file spaces that you own from 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 cannot delete individual backup versions kept on the server. If you decide you do not need the file space, click the Utilities menu. On the Delete Filespaces window, select the objects to delete. Click the Delete button.
You can also delete a file space using the delete filespace command.