TSM provides a command line interface (CLI) that you can
use as an alternative to the graphical user interface (GUI). This
chapter describes how to start or end a client command session, and how to
enter commands. It also provides detailed information about each TSM
command. Table 24 shows a list of tasks related to entering commands.
Command | Description | Page |
---|---|---|
archive | Archives files from a workstation to TSM storage. | Archive |
cancel restore | Displays a list of restartable restore sessions and permits you to select one to cancel. | Cancel Restore |
delete access | Revokes authorization for a user to restore or retrieve files. | Delete Access |
delete archive | Deletes archived files from TSM storage. | Delete Archive |
delete filespace | Deletes file spaces in TSM storage. | Delete Filespace |
help | Displays online command help. | Help |
incremental | Backs up new and changed files. | Incremental |
loop | Starts an interactive command session. | Loop |
macro | Uses commands within a macro file. | Macro |
query access | Displays a list of current authorization rules. | Query Access |
query archive | Displays a list of archived files. | Query Archive |
query backup | Displays a list of backup versions. | Query Backup |
query backupset | Queries a backup set from the server or a local file. | Query Backupset |
query filespace | Displays a list of file spaces in TSM storage. | Query Filespace |
query mgmtclass | Displays information about available management classes. | Query Mgmtclass |
query restore | Displays a list of your restartable restore sessions in the server database. | Query Restore |
query schedule | Displays information about scheduled events. | Query Schedule |
query session | Displays information about the current session. | Query Session |
query tsa | Displays information about current TSA. | Query TSA |
restart restore | Displays a list of restartable restore sessions and permits you to select one to restart. | Restart Restore |
restore | Restores backup versions from TSM storage. | Restore |
restore backupset | Restores a backup set from the server or a local file. | Restore Backupset |
retrieve | Retrieves archived files from TSM storage. | Retrieve |
schedule | Starts the client scheduler on the workstation. | Schedule |
selective | Backs up selected files. | Selective |
set access | Authorizes another user to access your backup versions or archive copies. | Set Access |
set password | Changes the TSM password for your workstation. | Set Password |
You can start or end a client command session in either batch mode or interactive mode. Use batch mode when you want to enter a single client command. TSM processes the command and returns to the command prompt.
Use interactive mode when you want to enter a series of commands. Since TSM establishes connection to the server only once for interactive mode, a series of commands can be processed more quickly. TSM processes the commands and returns to the tsm> prompt.
When you enter a single command in batch mode, precede it with the executable program name, load dsmc. For example, to process the incremental command in batch mode, you would enter:
load dsmc incremental
If a password is required, TSM prompts you each time you enter a command if the passwordaccess option is set to prompt, or authentication on the server is set to On. Type your password and press Enter.
You can also enter your password using the password option with a command, but your password is displayed. For example, if your password is secret, enter:
load dsmc incremental -password=secret
If you set the passwordaccess option to generate in your dsm.opt file, you are not required to specify the password with the command. TSM only prompts you for your password if you are registering your workstation with a server, or manually changing your password.
To end a batch mode session, enter quit at the prompt.
Use the interactive mode to enter a series of commands. Enter load dsmc on the command line and press Enter. Do not precede each command with the executable program name, load dsmc. When the tsm> command prompt displays, type the command name and press Enter. Alternatively, you can enter load dsmc loop on the command line to start a client command session in interactive mode. Loop is the default command for dsmc.
If a password is required, TSM prompts you when you enter the first command. Type your password and press Enter. You can also enter your password using the password option with the loop command, but your password is displayed. For example, if your password is secret, you would enter:
load dsmc loop -password=secret
To end an interactive session, enter quit at the prompt.
A client command can include one or more of these components:
The sections that follow describe each of these components.
The first part of a command is the command name. The command name consists of a single word, such as help or schedule, or an action word and an object for that action, such as query archive. Enter the full command name, or its minimum abbreviation. For example, you can enter any of the following versions of the query schedule command:
query schedule q sc q sched query sc
There are two groups of options that you can use with commands:
Commands can have required parameters, optional parameters, or no parameters at all. Required parameters provide information to perform a task. The most commonly required parameter is a file specification. For example, if you want to archive a file named budget from the project directory, you would enter:
load dsmc archive t3\sys:project/budgetIt is unnecessary to enter the to enter the NetWare server name from which you are working.
Some commands have optional parameters. If you do not enter a value when you include an optional parameter, TSM uses the default value. For example, the restore command includes a required parameter, sourcefilespec, that specifies the path and file name in storage that you want to restore. The optional parameter, destinationfilespec, specifies the path and file name where you want to place the restored files. If you do not specify the destinationfilespec, by default, TSM restores the files to the original source path. If you want to restore the files to a different directory, enter a value for destinationfilespec. For example, to restore nw1\sys:project/budget to nw2\sys:newproj/planning, you would enter:
load dsmc restore nw1\sys:project/budget nw2\sys:newproj/planning
Enter parameters in the order indicated in the command syntax diagram.
Use the following syntax rules when specifying file specification parameters, such as filespec, sourcefilespec, and destinationfilespec:
load restore sys:dir1/* mydir/
load dsmc i sys:The following example is not valid:
load dsmc sel sys:
When specifying a file specification, if the name ends with /, then it is considered a directory, otherwise it is considered a file.
The following example illustrates these two rules. Even though mydir and yourdir are directories, the command will fail because /* is implied after mydir, and yourdir is considered a file:
restore sys:mydir/ /away/yourdir
The following example illustrates the second rule. Even though mydir and yourdir are directories, the command will fail because mydir and yourdir are considered files:
restore sys:mydir /away/yourdir
load dsmc set access sys:/dir1/*/*
If the editor=yes option is specified in your options file, TSM permits you to recall and edit as many as 20 previously entered commands using the up arrow and down arrow keys. If the editor=no option is specified, the feature to recall previous commands is not active. If the editor and command retrieve functions are not working on a specific workstation setting, you should turn off the editor option. For more information regarding the editor option, see Editor.
Pressing the Up arrow key displays the previous command in memory.
Pressing the Down arrow key displays the next command in memory. Table 26 lists other functions you can perform when you recall
commands.
Table 26. Command Recall and Edit Functions
Function | Press |
Display the previous command in memory. | Up arrow |
Display the next command in memory. | Down arrow |
Move to the beginning of the command. | Home |
Move to the end of the command. | End |
Move to the left. | Left arrow |
Move to the right. | Right arrow |
Move five spaces to the right. | Tab right |
Delete a character to the right of the cursor. | Delete |
Delete a character to the left of the cursor. | Backspace |
Insert a character. | Toggle the Insert key |
Finish or execute the command. | Enter |
Clear the current line. | Esc |
End the program. | CTRL-C |
End the program. | QQ (Scheduler or Incremental Backup/Restore) |
In a command, wildcard characters can be used in the file name or file extension only. You cannot use them to specify destination files, volume names, server names, the bindery, or NDS names. Use wildcard characters when you want to specify multiple files with similar names in one command. Without wildcard characters, you must repeat the command for each file. Valid wildcard characters that you can use include:
Table 27 shows examples of each wildcard.
Pattern | Matches | Does Not Match |
---|---|---|
Asterisk (*) |
|
|
ab* | ab, abb, abxxx | a, b, aa, bb |
ab*rs | abrs, abtrs, abrsrs | ars, aabrs, abrss |
ab*ef*rs | abefrs, abefghrs | abefr, abers |
abcd.* | abcd.c, abcd.txt | abcd, abcdc, abcdtxt |
Question Mark (?) |
|
|
ab? | abc | ab, abab, abzzz |
ab?rs | abfrs | abrs, abllrs |
ab?ef?rs | abdefjrs | abefrs, abdefrs, abefjrs |
ab??rs | abcdrs, abzzrs | abrs, abjrs, abkkkrs |
dsmc selective "/home/me/*.c"
Follow the general rules below when you enter commands:
The following sections contain detailed information about each of the TSM commands. These commands are arranged in alphabetical order. Information for each commands includes:
The archive command archives a single file, selected files, or all files in a directory and its subdirectories on a server. Directories are archived.
Archive files that you want to preserve in their current condition. To release storage space on your workstation, delete files as you archive them. Retrieve the archived files to your workstation whenever you need them again.
Syntax
.-----------------------. V | >>-ARchive---+-----------+-----+-filespec---------+--+--------->< '- options--' +-BINdery----------+ '-DIRectory or NDS-'
Parameters
You can use the changingretries and subdir common options with the archive command. See Chapter 8, "Setting Common Options" for information about these common options.
Examples
The following are examples of tasks you might perform using the archive command.
Command: load dsmc archive t9\sys:user/proj1\budget
Command: load dsmc archive t9\sys:plan/proj1/*.txt
Command: load dsmc archive t9\sys:home/*
The cancel restore command displays a list of your restartable restore sessions in the server database. You can select zero or more restartable restore sessions that you want to cancel. To restart restartable restore sessions, use the restart restore command.
Use the cancel restore command when:
Syntax
>>-CANcel Restore---+-----------+------------------------------>< '- options--'
Parameters
Examples
Following is an example of a task you might perform using the cancel restore command.
Command: load dsmc cancel restore
The delete access command deletes authorization rules for files that are stored on the server. When you delete an authorization rule, you revoke user access to any files specified by that rule.
Syntax
>>-Delete ACcess---+-----------+------------------------------->< '- options--'
Parameters
Examples
The following are examples of tasks you might perform using the delete access command.
Command: load dsmc delete access
See the following screen example:
Index Type Node User Path _____ ______ ____________________________________ 1 Backup node1 * mo\sys:u/dev/proja/list 2 Backup node4 * mo\sys:u/plan/exp/deptc 4 Archive node5 * mo\sys:u/mfg/inv/parta Enter Index of rule(s) to delete, or quit to cancel:
To delete the authorization rules that allow node3 and node5 to access your files, type 2 4 or (2,4) (your selections can be separated by commas or spaces) and press Enter. Quit without making a selection by entering quit.
The delete archive command deletes archived files from TSM storage. Your administrator must give you authority to delete archived files.
Attention: When you delete archived files, you cannot retrieve them. Verify that the files are obsolete before you delete them.
Syntax
.-----------------------. V | >>-Delete ARchive---+-----------+-----+-filespec---------+--+-->< '- options--' +-BINdery----------+ '-DIRectory or NDS-'
Parameters
You can use the subdir common option with the delete archive command. For information about common options, see Chapter 8, "Setting Common Options".
Examples
The following are examples of tasks you might perform using the delete archive command.
Command: load dsmc del arch sys:user/plan/proj1/budget
Command: load dsmc del arch sys:user/plan/proj1/*.txt
Command: load dsmc d ar sys:user/project/* -pick
The delete filespace command deletes file spaces from TSM storage. A file space is a logical space on the server that contains files you backed up or archived. TSM assigns a separate file space on the server for each drive at your workstation from which you back up or archive files. The file space name is the same as the drive label name. When you enter the delete filespace command, TSM displays a list of your file spaces. Select those file spaces that you want to delete from this list.
Your administrator must give you authority to delete a file space. You need BACKDEL authority if the file space you want to delete contains backup versions, or ARCHDEL authority if the file space contains archive copies. If the file space contains both backup versions and archive copies, you need both types of authority.
Attention: When you delete a file space, you delete all backup versions and archive copies within that file space. When you delete a file space, you cannot restore the files. Verify that the files are obsolete before you delete them.
Syntax
>>-Delete Filespace---+-----------+---------------------------->< '- options--'
Parameters
Examples
The following are examples of tasks you might perform using the delete filespace command.
Command: load dsmc delete filespace
Command: load dsmc del f -date=5 -time=4
The help command displays help information for the command line client. Enter the number of the topic that you want to view. If there is more than one screen of topics, scroll backward or forward through the Table of Contents. To exit, type q and press Enter.
Syntax
>>-Help---+-----------+---------------------------------------->< '- options--'
Parameters
Examples
Following is an example of a task you might perform using the help command.
Command: load dsmc help
The incremental command backs up all new or changed files or directories in the default client domain or from NetWare volumes you specify that are not excluded from backup services. TSM also backs up file system trustee rights along with file data. It is not possible to restore only the trustee rights; they are restored as part of the file restore process.
You can incrementally back up an entire file space (domain) or just a single file. If you specify only the file space name, the entire directory tree is traversed. If you specify a directory, only that directory is backed up, unless you use subdir=y. This is considered a partial incremental back up.
The following attributes in the management class assigned to the file or directory affect whether the data is actually backed up:
For more information on management classes, see Chapter 6, "Understanding Storage Management Policies".
You can assign the default management class to a file, or you can assign a specific management class to a file using the include option in an include-exclude list.
You can perform either a full incremental backup or an incremental by date backup. The default is a full incremental backup.
You can also the selective command to perform a selective backup that backs up only the files, directories or empty directories that you specify. See Selective for more information.
A full incremental backs up all files or directories that are new, or have changed since the last incremental backup. During a full incremental backup, the client queries the server to determine the exact condition of your storage. TSM uses this information to:
An incremental-by-date backup, backs up new and changed files with a modification date later than the date of the last incremental backup stored at the server, unless the files are excluded from backup by an exclude statement.
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. Use the query filespace command to determine the date and time of the last incremental backup of the entire file system.
To perform an incremental-by-date backup, use the incrbydate option with the incremental command.
Unlike a full incremental, an incremental-by-date does not maintain current server storage of all your NetWare server files because:
For these reasons, it is recommended that if you have limited time during the week to perform backups, but extra time on the weekends, you can use a partial incremental backup on weekdays, and a full incremental backup on weekends to maintain current server storage of your NetWare server files.
If you are running NetWare Btrieve on your NetWare server (or any other server-based database), stop the database application before backing up the files associated with the database. Many database applications place locks on files that can prevent TSM from backing them up. Because TSM is a Storage Management Services (SMS) backup application, it supports database Target Service Agents (TSA's) as soon as they are available. This allows TSM to maintain database integrity without manual interaction.
If you are running your communication with SNA LU6.2 (NetWare for SAA), you cannot stop the Btrieve database application because NetWare for SAA requires Btrieve to be running. Therefore, you cannot back up the file named btrieve.trn in the system subdirectory. As a result, you might not be able to maintain true data integrity here.
If TSM refuses to back up a file, check to see if it is marked for execute only or it is opened and locked by another user.
If the incremental command is retried because of a communication failure or session loss, the transfer statistics will display the number of bytes TSM attempted to transfer during all commands attempts. Therefore, the statistics for bytes transferred may not match the file statistics, such as those for file size.
For information about backing up server specific information, see the Netware Backup and Recovery Guide. This document is shipped with the client under the name ntwback.htm.
Syntax
.---------------------. V | >>-Incremental---+-----------+------+---------------+--+------->< '- options--' +-filespec------+ '-filespacename-'
Parameters
You can use the following common options with the incremental command: changingretries, domain, memoryefficientbackup, subdir, tapeprompt. For information about these options, see Chapter 8, "Setting Common Options".
If a volume is specified, all new and changed files are backed up and the last incremental date for the file space is updated on the server. If a file or directory is specified, the last incremental date is not updated, so the file or directory might be backed up again if a later backup is performed using the incrbydate option.
If a volume is specified, specify the volume without a trailing slash.
Examples
The following are examples of tasks you might perform using the incremental command.
Command: load dsmc Incremental
Command: load dsmc i b9\sys: b9\data: b9\bind:
Command: load dsmc inc vol:system/*
Command: load dsmc inc -incrbydate
Command: load dsmc inc nds:
Command: load dsmc inc b9\sys:
Command: load dsmc inc nds:.o=ann.*
The loop command starts an interactive command line session that is maintained until you enter quit. In an interactive command line session, it is unnecessary to precede each command name with load dsmc and your password, if one is required. After you start an interactive session, most of the options you entered with other commands are in effect throughout the session, unless you enter them again using a different setting.
You can enter all valid commands in interactive mode except the schedule and loop commands.
Some options cannot be used within the interactive session created by the loop command, and are identified in the option description by this statement: This option is valid only on the initial command line. It is not valid in interactive mode.
See Chapter 8, "Setting Common Options" for options that cannot be used in interactive mode.
Syntax
.-LOOP-. >>-+------+---+-----------+------------------------------------>< '- options--'
Parameters
Examples
Following is an example of a task you might perform using the loop command.
Command: load dsmc loop
At the tsm> prompt, enter a command.
There are three methods for ending an interactive session:
Note: | Do not attempt to end an interactive session by unloading dsmc. |
The macro command sends a series of commands that you specify in a macro file. By including the macro command within a macro file, you can nest as many as ten levels of commands.
Comment lines are not supported within the macro file specified for the macro command.
Syntax
>>-MAcro- macroname--------------------------------------------><
Parameters
Examples
The following is an example of how to use the macro command.
Command: macro sys:tsm/backabc.mac
where backabc.mac contains the following statements:
sel sys:devel/project/proja/* sel sys:devel/project/projb/* sel sys:devel/project/projc/*
The query access command displays a list of nodes to whom you have given access to backup versions or archive copies of specific files. TSM displays a list of authorization rules that you defined with the set access command. The information includes:
Syntax
>>-Query ACcess---+-----------+-------------------------------->< '- options--'
Parameters
Examples
Following is an example of a task you might perform using the query access command.
Command: load dsmc query access
The query archive command displays a list of your archived files, the file size, archive date, file specification, expiration date, and file description.
Syntax
.-----------------------. V | >>-Query ARchive---+-----------+-----+-filespec---------+--+--->< '- options--' +-BINdery----------+ '-DIRectory or NDS-'
Parameters
You can use the following common options with the query archive command: scrolllines, scrollprompt, subdir. See Chapter 8, "Setting Common Options" for more information..
Examples
The following are examples of tasks you might perform using the query archive command.
Command: load dsmc q ar -sub=y servera\sys:*
Command: load dsmc q ar -sub=yes -date=5 -time=4 servera\sys:*
Command:
load dsmc q ar -date=1 -time=4 servera\sys:uproj/ proj*
The query backup command displays a list of backup versions of your files. For each backup version, TSM displays the file specification, file size, backup date, whether the file is active or inactive, and the management class to which the file is assigned. TSM displays only the first ten characters of the management class name.
Syntax
.------------------------. V | >>-Query Backup---+-----------+-----+- filespec---------+--+--->< '- options--' +- BINdery----------+ '- DIRectory or NDS-'
Parameters
You can use the subdir, scrolllines and scrollprompt common options with the query backup command. See Chapter 8, "Setting Common Options" for information about these common options.
Examples
The following are examples of tasks you might perform using the query backup command.
Command: load dsmc q backup -su=y serva\sys:*
Command: load dsmc q b -date=1 -time=4 -su=y serva\sys:*
Command: load dsmc q b -date=1 -time=4 serva\sys:proj/proj*
The query backupset command queries a backup set from a local file or the server. Attributes, directories, and files associated with the backup set are displayed.
Syntax
>>-Query BACKUPSET---+---------+---+- backupsetname-+---------->< '-options-' '- filename------'
Parameters
You can use these common options with the query backupset command: scrolllines and scrollprompt. See Chapter 8, "Setting Common Options" for information about these common options.
Examples
The following are examples of tasks you might perform using the query backupset command.
Command: load dsmc query backupset mybackupsetname -loc=server
Command: load dsmc query backupset sys:u/budget /backupsetfile.name -loc=file
The query filespace command displays a list of file spaces for a node stored on the server. A file space is a logical space on the server that contains files you backed up or archived. TSM assigns a separate file space on the server for each node at your workstation from which you back up or archive files.
Syntax
>>-Query Filespace---+-----------+----------------------------->< '- options--'
Parameters
You can use the scrolllines and scrollprompt options with the query filespace command. See Chapter 8, "Setting Common Options" for more information..
Examples
The following are examples of tasks you might perform using the query filespace command.
Command: load dsmc query filespace
The query mgmtclass command displays information about the management classes available in your active policy set.
Your administrator defines management classes that contain attributes controlling whether a file is eligible for backup or archive services. They also contain attributes that determine how TSM manages the backups and archives after they reach the server.
Your active policy set contains a default management class; it can contain any number of additional management classes. You can assign specific management classes to files using include options that are located in the client options file. If you do not assign a management class to a file, TSM uses the default management class.
When you archive files, you can override the assigned management class by using the archmc option.
Syntax
>>-Query Mgmtclass---+-----------+----------------------------->< '- options--'
Parameters
You can also use the scrolllines and scrollprompt common options with the query mgmtclass command. For more information about these common options, see Chapter 8, "Setting Common Options".
Examples
The following are examples of tasks you might perform using the query mgmtclass command.
Command: load dsmc query mgmtclass -det
The query restore command displays a list of your restartable restore sessions in the server database. The list contains the following fields: owner, replace, subdir, preservepath, source, and destination.
Certain restore operations, called restartable restore sessions, start a special protocol within TSM. Some restore sessions can be restarted for these reasons:
Syntax
>>-Query Restore-----------------------------------------------><
Parameters
Examples
The following are examples of tasks you might perform using the query restore command.
owner Rep Sub Pre Source ----- --- --- --- ------- 1. framke P N L \home\ramke\testdir\* 2. framke P N L \home\framke\* dest = \tmp\
The query schedule command displays the events scheduled for your node. Your administrator can set up schedules to perform automatic backups and archives for you. To plan your work, use this command to determine when the next scheduled events occur.
Syntax
>>-Query SCHedule---+-----------+------------------------------>< '- options--'
Parameters
Examples
Following is an example of a task you might perform using the query schedule command.
Command: load dsmc query schedule
The query session command displays information about your TSM session, including the current node name, when the session was established, server information, and server connection information.
Syntax
>>-Query SEssion---+-----------+------------------------------->< '- options--'
Parameters
Examples
Following is an example of a task you might perform using the query session command.
Command: load dsmc query session
The query tsa command displays information associated with a specific NetWare Target Service Agent (TSA). This information includes the TSA name, type, version information, and location of the password file for the TSA (if applicable).
This command also verifies the user ID and password information, depending on how they are stored. If the user id and password are stored locally using the nwpwfile option to create a password file, and the current password file does not contain valid information or a current password files does not exist, this command prompts for the correct information. (For more information on nwpwfile, see Nwpwfile.
If the password is stored in the local options file nwuser, the command verifies the user ID and password in that file. For more information on nwuser, see Nwuser
Syntax
>>-Query TSA---+---------+---+----------------+---------------->< '-options-' +-tsaname--------+ +-NDS------------+ '-servername\NDS-'
Parameters
Examples
The following are examples of tasks that you can perform using the query tsa command.
Command: load dsmc q tsa
Command: load dsmc q tsa ramke
Command: load dsmc q tsa nds
Command: load dsmc q tsa mock/nds
Command: load dsmc q tsa ramke -nwuser=.admin.adsm:viksne -nwpwfile=yes
Command: load dsmc q tsa ramke -nwpwfile=yes
Command: load dsmc q tsa nds -nwpwfile=yes
Example 1
A sample output for query tsa follows:
Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 1 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Node Name: GOETHE Session established with server spikes: Windows NT Server Version 3, Release 1, Level 0.1 Server date/time: 16/04/1999 16:09:52 Last access: 16/04/1999 16:08:39 Connecting to a NetWare File System (goethe) Connected to goethe TSA Name..........: goethe TSA Module Name........: TSA410.NLM TSA Version.....: 4.14.0 SMDR Version....: 1.0.0 User/Password Location..: goethe\sys:tsm/030199/74cc82cb.pwd User/Password Valid.....: Yes tsm>
Example 2
A sample output for query tsa nds (no password file present) follows:
Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 7 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Node Name: goethe Session established with server spikes: Windows NT Server Version 3, Release 1, Level 0.1 Server date/time: 06/04/1999 16:09:52 Last access: 06/04/1999 16:08:39 Connecting to a Novell Directory (goethe_tree) Please enter NetWare user for "goethe_tree":.admin.adsm Please enter the password on "goethe_tree" for NetWare user".admin.adsm":***** Connected to goethe_tree NetWare TSA Information TSA Name..........: goethe TSA Module Name........: tsands TSA Version.....: 1.0.0 SMDR Version....: 1.0.0 User/Password Location..: goethe\sys:tsm/040199/5e82fd66.pwd User/Password Valid.....: Yes tsm>
Example 3
A sample output for query tsa (non-NetWare platforms) follows:
Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 7 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Node Name: spikes Session established with server spikes: Windows NT Server Version 3, Release 1, Level 0.1 Server date/time: 06/04/1999 16:09:52 Last access: 06/04/1999 16:08:39 Selected function is not supported for this client platform. tsm>
The restart restore command displays a list of your restartable restore sessions in the server database. You can select zero or more restartable restore sessions that you want to restart.
The restarted restore uses the same options you used in the failed restore. The restarted restore continues from the point at which the restore previously failed.
To cancel restartable restore sessions, use the cancel restore command. Use the restart restore command when:
Options from the failed session supersede new or changed options for the restarted session.
Syntax
>>-RESTArt Restore---+-----------+----------------------------->< '- options--'
Parameters
For information about common options you can use with the restart restore command, see Chapter 8, "Setting Common Options".
Examples
Following is an example of a task you might perform using the restart restore command.
Command: load dsmc restart restore
The restore command obtains copies of backup versions of your files from a TSM server. To restore files, specify the directories or selected files, or select the files from a list. Restore files to the directory from which you backed them up, or to a different directory. TSM uses the preservepath option with the subtree value as the default for restoring files. For more information on this option, see Chapter 9, "Using Options With Commands".
System trustee rights are restored as part of the file restore process. They cannot be restored alone option.
The restore command can be used to restore a backup set. See Restore Backupset the command for the syntax.
Syntax
>>-REStore---+--------+---+-----------+-------------------------> '- FILE--' '- options--' .-----------------------. V | >-------+-sourcefilespec---+--+---+----------------------+----->< +-BINdery----------+ '- destinationfilespec-' '-DIRectory or NDS-'
Parameters
You can use these common options with the restore command: replace, subdir. See Chapter 8, "Setting Common Options" for information about common options.
Always restore the bindery first to ensure the trustee data (permissions) are restored correctly.
It is also a good idea to ensure that the bindery restore is reconciled with the current NetWare system configuration, especially if the bindery is restored using a version that is back level.
To restore each volume on the server, enter load dsmc res sys:* -su=yes -rep=yes
Note: | Any changes made after the backup version was made are lost. |
To restore one container, specify dir:.o=container_name In all examples, nds: instead of dir: may be entered.
It is also a good idea to ensure that the directory restore reconciled with the current NetWare system configuration, especially if the directory is restored using a version that is back level.
Note: | Objects added after the backup version was made are not deleted. |
Examples
The following are examples of tasks you might perform using the restore command.
Command: load dsmc restore sys:u/projecta/budget
Command: load dsmc restore file budget
Command: load dsmc res sys:u/projecta/*.bak
Command: load dsmc res servb\sys:user/project/* -pick -inactive
Attention: If the destination is a directory, specify the delimiter (/) as the last character of the destination. If you omit the delimiter and your specified source is a directory or a file spec with a wildcard, you will receive an error.
Command: load dsmc res sys:projecta/*.bak sys:projectn/
Command: load dsmc restore sys:projecta/*.bak serverb\sys:projectn/
Command: load dsmc res T9.dir
Command: load dsmc res adsm40.directory.o=ibm
Command: load dsmc res servb\sys:user/projedct/* -pick -inactive
The restore backupset command restores a backup set from the server or a local file. If you are restoring a file space from a backupset to a system that did not perform the original backup, you may need to either specify a destination or use the following syntax to correctly specify the source file, or you may need to do both.
If you are unable to restore a backup set from portable media to your client machine, 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.
NDS restores are not supported. If TSM creates a backup set containing only the NDS, and you attempt to restore it with the restore backupset command, TSM produces an error message. If a backup set contains both a file specification and the NDS, no error message is produced, however only the file specification is restored. To restore the NDS, you must use the use the restore command from the command line.
The restore backupset command restores a backupset from the server or a local file only. For example, the following command restores a backup set from the server: tsm> res backupset bkset.101394 -su=y -rep=all, and the following command restores the backup set from file on a local NetWare server: tsm> res backupset sys:\34477804.ost -su=y -rep=all -loc=file.
If you copy a backup set from the TSM server to the NetWare server in order to restore it, you must specify -loc=file. The backup set can reside on NetWare volumes, CDROM, DVD, or a similar device that can be mounted as a volume with files than can be accessed as file specifications.
You cannot restore a subset of files from a local backup set. TSM issues the following error message: "Invalid source file specification."
Syntax
>>-REStore BACKUPSET---+---------+---+- backupsetname-+---------> '-options-' '- filename------' >-----+--------------------+---+----------------------+-------->< +- --sourcefilespec--+ '- destinationfilespec-' '-BINdery------------'
Parameters
You can use these common options with the restore backupset command: quiet, replace, and subdir. See Chapter 8, "Setting Common Options" for information about these common options.
Examples
The following are examples of tasks you might perform using the restore backupset command.
Command: load dsmc restore backupset mybackupsetname -loc=server
Command: load dsmc restore backupset sys:u/budget/backupsetfile.name -location=file
The retrieve command obtains copies of archived files from the server. You can retrieve specific files or entire directories. Use the description option to specify the descriptions assigned to the files you want to retrieve.
Place the retrieved files in the same directory from which they were archived, or in a different directory. TSM uses the preservepath option with the subtree value as the default for restoring files. For more information on this option, see Chapter 9, "Using Options With Commands".
Note: | If you are retrieving files to a different directory than the original directory, file names become the names you specify with the destinationfilespec parameter. Because only DOS names are valid within the TSM client, the file name becomes a DOS name. |
Syntax
.-----------------------. V | >>-RETrieve---+-----------+-----+-sourcefilespec---+--+---------> '- options--' +-BINdery----------+ '-DIRectory or NDS-' >-----+----------------------+--------------------------------->< '- destinationfilespec-'
Parameters
For information about common options you can use with the retrieve command, see Chapter 8, "Setting Common Options".
Examples
The following are examples of tasks you might perform using the retrieve command.
Command: load dsmc ret sys:projecta/budget
Command: load dsmc retrieve sys:projecta/*.bak
Command: ret sys:project/* -pick
Note: | If the destination is a directory, you must specify the delimiter (/) as the last character of the destination. If you omit the delimiter and your specified source is a directory or a file spec with a wildcard, you will receive an error. |
Command: load dsmc ret/projecta/*.bak servb\sys:projectn/
Note: | To retrieve files contained in a subdirectory, you must specify the subdirectory in another retrieve command. |
Command: retrieve sys:home/*
Command: ret sys:project/* -pick
The schedule command starts the client scheduler on your workstation. The client scheduler must be running before scheduled work can start.
When you start the client scheduler, it continuously contacts the server for scheduled events based on the time you specified with the queryschedperiod option in your client options file. If your administrator sets this option for all nodes, that setting overrides your setting.
If you are using TCP/IP communications, the server can prompt your workstation when it is time to run a scheduled event. To do so, set the schedmode option to prompted in the client options file or on the schedule command.
After you start the client scheduler, it continues to run and to start scheduled events. To end the scheduler, enter QQ. If the scheduler is active, it completes necessary transactions, then stops.
Syntax
>>-SCHedule---+-----------+------------------------------------>< '- options--'
Parameters
Examples
The following is an example of a task you might perform using the schedule command.
Command: load dsmc schedule -password=notell
When you run the schedule command, all messages regarding scheduled work are sent to a file called dsmsched.log or to an alternate file specified in the schedlogname option in your client options file. If you do not specify a directory path with the file name in the schedlogname option, TSM stores the file in the default installation directory.
The selective command backs up files that you specify. If these files become damaged or lost, you can replace them with backup versions from the NetWare server. When you run a selective backup, TSM backs up all the files unless they are excluded from backup in your include-exclude list, or they do not meet management class requirements for serialization.
You can selectively back up single files and directories from the NetWare server. You can also selectively back up the NDS and the bindery. Use wildcard characters to back up groups of related files.
During a selective backup, TSM sends copies of the files to the server even if they have not changed since the last backup. This might result in more than one copy of the same file on the server. If this occurs, you might not have as many different down-level versions of the file on the server as you intended. Your version limit might consist of identical files. To avoid this, use the incremental command to back up only new and changed files.
If TSM refuses to back up a file, check to see if it is marked for execute only or if it is opened and locked by another user.
During a selective backup, a directory path may be backed up, even if the specific file that was targeted for backup is not found. For example:
load dsmc selective sys:dir1/dir2/bogus.txt
still backs up dir1 and dir2 even if the file bogus.txt does not exist.
If the selective command is retried because of a communication failure or session loss, the transfer statistics will display the number of bytes TSM attempts to transfer during all command attempts. Therefore, the statistics for bytes transferred may not match the file statistics, such as those for file size.
Syntax
.-----------------------. V | >>-Selective---+-----------+-----+-filespec---------+--+------->< '- options--' +-BINdery----------+ '-DIRectory or NDS-'
Parameters
You can use these common options with the selective command: changingretries, quiet, tapeprompt, and subdir. See Chapter 8, "Setting Common Options" for information about these common options.
Examples
The following are examples of tasks you can perform using the selective command.
Command: load dsmc Selective sys:u/devel/proja
Command: load dsmc selective sys:u/devel/proj*
Command: load dsmc selective sys:u/devel/proj* sys:user/budget
Command: load dsmc s t9\dir:
Command: load dsmc s servc\bindery:
Command: load dsmc s t9\dir/.o=tfr
The set access command gives users at other nodes access to your backup versions or archived copies. You can give another user access to a specific file, multiple files, or all files in a directory. When you give access to another user, that user can restore or retrieve your objects. Specify in the command whether you are giving access to archives or backups.
Note: | You cannot give access to both archives and backups using a single command. Access is enabled only between like platforms. You can grant access only to another NetWare client node. |
Syntax
.-*----. >>-SET Access---+- Archive-+----- filespec----- node---+------+-> '- Backup--' '-user-' >-----+---------+---------------------------------------------->< '-options-'
Parameters
If you give access to a branch of the current working directory, you only need to specify the branch. If you give access to objects that are not in a branch of the current working directory, you must specify the volume and directory. The file spec to which you gave access must have at least one backup version or archive copy object (file or directory) on the server.
To give access to all objects below a certain level, use an asterisk, directory delimiter, and an asterisk at the end of your file spec. For example, to give access to all objects below sys:ann, use file spec sys:ann/*/*.
To specify all files in all directories off the root directory, enter sys:*/* on the command line. Enter sys:* on one set access command and sys:*/* on another if you want another user to have complete access to your file space. The first sys:* gives access to all subdirectories and all files off the root directory.
Examples
The following are examples of tasks you might perform using the set access command:
Command: load dsmc set access backup sys:budget node2
Command: load dsmc set access archive sys:devel/proja/*.sys node3
Command: load dsmc set a archive sys:u/devel/proja node3
Command: load dsmc set a b *bldgb
Command: load dsmc set access b * node3
The set password command changes the TSM password for your workstation. You are prompted twice for your new password.
A password is not case-sensitive, and it can be as many as 64 characters. Valid characters are:
Syntax
>>-SET Password---+--------------+---+-----------+------------->< '- oldpw newpw-' '- options--'
Parameters
Examples
The following is an example of using the set password command.
Command: load dsmc set password osecret nsecret