All-In-One TSM Client Commands

TSM (Tivoli Storage Manager)  is  a centralized, policy-based, enterprise class, data backup and recovery package from IBM Corporation.The software enables the user to insert objects not only via backup, but also through space management and archive tools. It also allows retrieval of the same data via similar restore, recall, and retrieve methods.

As  Unix Admins  we used to get lot of requests from the application teams for tsm backup restores.I would like to discuss about the the best 14 best use-full TSM client commands.

I will  go by the  a category wise  "Query,Backup & Restore".

Generally we use dsmc/dsm  for the  TSM client commands.

In this article we are going to discuss about the following contents with practice examples.

  1) Querying the server
    A. Querying your scheduled backup slot
    B. Querying what files are included / excluded for backup
    C.Querying what partitions have been backed up
    D.Querying what files have been backed up
   
 2) Backing Up data
    A. Backing your local filesystems
    B. Backing up selected files
   
 3) Restore Data
    A. Restore a file to its original directory
    B. Restore the most recent backup version of a file
    C. Display a list of active and inactive backup versions of files from which you can select versions to restore
    D. Restore with a directory including subdirectories
    E. Restore the  file under a new name and directory
    F. Restore all files in a directory  as of their current state
    G. Restore all files from a  directory that end with .xyz to the another directory
    H. Restore files specified in the text file to a different location

1) Querying the server

A. Querying your scheduled backup slot

To query your scheduled backup slot enter dsmc q sched (which is short for query schedule). The output should look similar to that below:

#dsmc q sched

    Schedule Name: WEEKLY_UM
      Description: UM weekly incremental backup
   Schedule Style: Classic
           Action: Incremental
          Options:
          Objects:
         Priority: 5
   Next Execution: 135 Hours and 25 Minutes
         Duration: 20 Minutes
           Period: 1 Week
      Day of Week: Thursday
           Expire: Never

B. Querying what files are included / excluded for backup

"q inclexcl" to list output similar to the following:

#dsmc q inclexcl
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
---- --------- ------------------------------ -----------------
Excl Filespace /var/run                       /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl Filespace /tmp                           /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl Directory /.../.opera/.../cache4         /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl Directory /.../.mozilla/.../Cache        /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl Directory /.../.netscape/.../cache       /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl Directory /var/tmp                       /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl All       /.../dsmsched.log              /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl All       /.../core                      /opt/tivoli/tsm/client/ba/bin/incl.excl
Excl All       /.../a.out                     /opt/tivoli/tsm/client/ba/bin/incl.excl

C.Querying what partitions have been backed up

"q fi" to list which partitions have been backed up:

** Unix/Linux  **

#dsmc q fi
  #     Last Incr Date      Type    File Space Name
---     --------------      ----    ---------------
  1   02-05-2013 02:13:13   UFS     /        
  2   25-07-2012 12:26:09   UFS     /export/home
  3   02-05-2013 02:13:26   UFS     /home    
  4   16-01-2013 11:26:37   UFS     /scratch  
  5   02-05-2013 02:13:54   UFS     /usr/local
  6   12-02-2013 02:52:41   UFS     /var    

** Netware **

  #     Last Incr Date      Type       File Space Name
---     --------------      ----       ---------------
  1   02-05-2013 00:23:46   NTW:LONG   Oracle_data\usr:
  2   02-07-2013 00:22:42   NDS        Oracle_data\bin:
  3   02-07-2013 00:25:33   NTW:LONG   Oracle_data\apps:
  4   02-07-2013 00:25:11   NTW:LONG   Oracle_data\usr:

D.Querying what files have been backed up

In order to query the files or directories that are backed-up earlier you can use "q ba".

The below example gives you only the directory information.

#dsmc q ba /home/oraadmin
   Size      Backup Date                Mgmt Class           A/I File
   ----      -----------                ----------           --- ----
   1024  B  15-10-2013 02:52:09          STANDARD             A  /home/oraadmin
 

If you just add a trailing * (star) as a wildcard in the above query, TSM will only return those files and directories backed up immediately below the directory path given in the query

#dsmc q ba /home/oraadm/*
   Size      Backup Date        Mgmt Class A/I File
   ----      -----------        ---------- --- ----
    512  12-09-2012 19:57:09    STANDARD    A  /home/oraadm/data1.dtf
  1,024  08-12-2012 02:46:53    STANDARD    A  /home/oraadm/data2.dtf
    512  12-09-2012 19:57:09    STANDARD    A  /home/oraadm/data3.dtf
    512  24-04-2002 00:22:56    STANDARD    A  /home/oraadm/data4.dtf

If you want to query all the current files and directories backed up under a directory and all its sub-directories you need to add the -subdir=yes option as below:

#dsmc q ba /home/oraadm/* -subdir=yes
   Size      Backup Date        Mgmt Class A/I File
   ----      -----------        ---------- --- ----
    512  12-09-2012 19:57:09    STANDARD    A  /home/oraadm/data1.dtf
  1,024  08-12-2012 02:46:53    STANDARD    A  /home/oraadm/data2.dtf
    512  12-09-2012 19:57:09    STANDARD    A  /home/oraadm/data3.dtf
    512  24-04-2002 00:22:56    STANDARD    A  /home/oraadm/data4.dtf
  1,024  12-09-2012 19:57:09    STANDARD    A  /home/oraadm/datasmart1/test
  1,024  12-09-2012 19:57:09    STANDARD    A  /home/oraadm/datasmart1/test/test2
 12,048  04-12-2012 02:01:29    STANDARD    A  /home/oraadm/datasmart2/tables
 50,326  30-04-2013 01:35:26    STANDARD    A  /home/oraadm/datasmart3/data_file1
 50,326  27-04-2013 00:28:15    STANDARD    A  /home/oraadm/datasmart3/data_file2
 11,013  24-04-2013 00:22:56    STANDARD    A  /home/oraadm/datasmart3/data_file3

---

2. Backing Up data

A. Backing your local filesystems

The syntax for this is "dsmc backup-type filesystem" , where backup-type is one of incremental or selective. 

Incremental Backup : It is one that backs up only the data that changed since the last backup — be it a full or incremental backup
Selective Backup : A type of backup where only the user specified files and directories are backed up. A selective backup is commonly used for backing up files which change frequently or in situations where the space available to store backups is limited. Also called a partial backup.

I would always suggest you always go with incremental. The command is "dsmc incremental"  or "dsmc incr" Where "incr" is an abbreviation for incremental.

Perform an incremental backup of your client server.
#dsmc incr
Make this will omit the filesystems which were mention in the exclude file.
To incrementally back up specific file-systems enter:
#dsmc incr /  /usr  /usr/local  /home

To back up entire filesystem irrespective of whether files have changed since the last backup, use the selective command with a wild-card and -subdir=yes as below:
#dsmc sel /*  /usr/*   /home/*  -su=yes

B. Backing up selected files

For backing up selected files is similar to that for backing up filesystems. Be aware, however, that you cannot use wildcards in directory / folder names:

#dsmc incr /home/oradm/data*/* -su=yes
ANS1071E Invalid domain name entered: '/home/oradm/data*/*'

#dsmc sel /home/oradm/data*/* -su=yes
Selective Backup function invoked.
ANS1081E Invalid search file specification '/home/oradm/data*/*' entered

You can, however, enter several file specifications on the command line, as below:
#dsmc incr /home/surya/*  /usr/bin/* -su=yes

---

3) Restore Data

We use the "restore" command to restore  files

 A. Restore a file to its original directory

 Restore the /home/oraadm/data.txt  file to its original directory.

 #dsmc restore /home/oraadm/data.txt

 If you do not specify a destination, the files are restored to their original location.

B. Restore the most recent backup version of a file

Here is an example to restore  /home/oraadm/data.txt file, even if the backup is inactive.

#dsmc restore /home/oraadm/data.txt -latest

If the file you are restoring no longer resides on your client machine, and you have run an incremental backup since deleting the file, there is no active backup of the file on the server. In this case, use the latest option to restore the most recent backup version. Tivoli Storage Manager restores the latest backup version, whether it is active or inactive.

C. Display a list of active and inactive backup versions of files from which you can select versions to restore

#dsmc restore "/home/oraadmin/*"-pick -inactive

D. Restore with a directory including subdirectories

Restore the files in the /oradata1 directory and all of its sub-directories (-sub=yes)

#dsmc restore /oradata1/ -subdir=yes

When restoring a specific path and file, Tivoli Storage Manager recursively restores all sub-directories under that path, and any instances of the specified file that exist under any of those sub-directories.

E. Restore the  file under a new name and directory

In-order to restore the  /home/oraadm/data.txt   file under a new name and directory.

#dsmc restore /home/oraadm/data.txt /tmp/data-renamed.txt

F. Restore all files in a directory  as of their current state

Restore all files in the /usr/oradata/docs directory to their state as of 5:00 PM on October 16, 2013.

#dsmc restore -pitd=10/16/2013 -pitt=17:00:00 /usr/oradata/docs/

Use the pitdate option with the pittime option to establish a point in time for which you want to display or restore the latest version of your backups. Files that were backed up on or before the date and time you specified, and which were not deleted before the date and time you specified, are processed. Backup versions that you create after this date and time are ignored.

G. Restore all files from a  directory that end with .xyz to the another directory

Restore all files from the /usr/oradata/docs/ directory that end with .bak to the /usr/oradata/projects/ directory.

# dsmc restore "/usr/oradata/docs/*.bak" /usr/oradata/projects/

If the destination is a directory, specify the delimiter (/) as the last character of the destination. If you omit the delimiter and your specified source is a directory or a file spec with a wildcard, you will receive an error. If the projects directory does not exist, it is created.

H. Restore files specified in the text file to a different location

Restore files specified in the restorelist.txt file to a different location.

# dsmc restore -filelist=/tmp/restorelist.txt /usr/ora_backup/

The files (entries) listed in the filelist must adhere to the following rules:

• Each entry must be a fully or partially qualified path to a file or directory or a relative path.
• Each entry must be on a new line.
• Do not use wildcard characters.
• Each entry results in the processing of only one object (file or directory).
• If the file name contains any spaces, enclose the file name with quotes.
• The filelist can be an MBCS file or a Unicode file with all Unicode entries.
• Tivoli Storage Manager ignores any entry that is not valid.

Read More

TSM Quick Reference for the Backup-Archive Unix Clients

UNIX Backup-Archive Clients

Starting a TSM GUI Session

You can start a TSM GUI session, do the following:

   • Start the X Window System

   • Enter dsm (runs TSM in foreground) or dsm & (runs TSM in background)

Performing a GUI Backup

To run a GUI backup, perform the following steps:

   1. Click on Backup files and directories from the TSM window.

   2. Expand the directory tree. Select the object that you want to back up. To search or filter files, click   Search icon from the tool bar.

   3. Select the type of backup from the pull-down menu:

        o To perform an incremental backup: click on Incremental (complete)Incremental (complete)

        o To perform an incremental by date: click on Incremental (date only)

        o To perform a selective backup: click on Always backup

        o To perform an image backup: click on Image Backup

    4. To modify specific backup options click the Backup Options button located to the right of the Estimate button. The options you select are effective during the current TSM session only.

    5. Click on Backup. The Task List window displays backup processing status.

Restoring Backup Versions

To run a GUI restore, perform the following steps:

   1. Click on Restore files and directories to your system from the TSM window.

   2. Expand the directory tree. Select the object that you want to restore. To search or filter files, click the Search icon from the tool bar.

         To restore a backup set:

             a. Expand the Backup Sets directory tree object.

              b. To restore backup sets locally, expand the Local object and specify the local device or
                  filename  containing the backup set.

             c. To restore a backup set from the server, expand the Server object and select the backup set 
                  name.

   3. To modify specific restore options click the Restore Options button located to the right of the Estimate
       button. The options you select are effective during the current TSM session only.

   4. Click on Restore. Enter the information in the Restore Destination window.

    5. Click on Restore. The Task List window displays restore processing status.

Performing a GUI Archive

To archive directory or drive files you can use search and filter criteria to locate the files that match that criteria. To search or filter files during an archive operation, perform the following steps:

   1. Click on Archive files and directories into long term storage from the TSM window. The Archive 
       window displays.
   2. Expand the directory tree. Select the object that you want to archive. To search or filter files, click the 
       Search icon from the tool bar.

   3. In the Description field:

       o Enter a description, or

       o Accept the default description, or

       o Select an existing description from the drop-down list.

  4. To modify specific archive options click the Archive Options button located to the right of the Estimate   button. The options you select are effective during the current TSM session only.

  5. Click on Archive. The Task List window displays the archive processing status.

Retrieving Archives

Retrieve a file when you want to return an archive copy from the TSM server to your workstation. To retrieve an archived file:

1. Click on Retrieve from the TSM window. The Retrieve window displays.

2. Expand the directory tree. Select the directory or files you want to retrieve. To search or filter files, click the Search icon from the tool bar.

3. To modify specific retrieve options, click the Retrieve Options button located to the right of the Estimate button. The options you select are effective during the current TSM session only.

4. Click the Retrieve button. The Retrieve Destination window displays. Enter the appropriate information.

5. Click on Retrieve. The Task List window displays the retrieve processing status.

Displaying GUI Online Help

To display GUI online help, do one of the following:

• Place cursor on option or field of interest and press F1

• Select Help menu

• Click on Help button in many windows

Ending a GUI Session

To end a GUI session, do one of the following:

• Select File menu; Exit item

• Double-click on the system menu icon

• Select the system menu; close item

Starting the TSM Scheduler

To start the TSM Scheduler, do one of the following:

• Enter the dsmc schedule command, or

• Include the dsmc schedule command in your /etc/inittab file

To display information about scheduled work for your client node, enter:

dsmc query schedule

To display information about completed work for your client node: Check the dsmsched.log file in the current directory.

To stop the scheduler:

To stop the scheduler:

• Use Ctrl+C (foreground)

• Enter the kill command (background)

• Enter q.

________________________________________

Starting a TSM Command Line Session

To start a command line session, do the following:

• On the command line, change directory to the TSM directory:

o Batch mode--for a single client command, enter:

> dsmc command

o Interactive mode--for more than one client command, enter:

> dsmc or dsmc loop

tsm> command

:

tsm> quit

Performing a Command Line Backup

• To run an incremental backup of the /home file system:

• dsmc incremental /home

• To run an incremental backup by date of the /home/jones directory, enter:

• dsmc incremental -incrbydate /home/jones

• To run a selective backup of the proja file in the /home/jones directory, enter:

• dsmc selective /home/jones/proja

• To run an image backup of the /home/jones directory, enter:

• dsmc backup image /home/jones

Restoring Backup Versions

To run a command line restore:

• To restore the /home/jones/proja file to its original directory, enter:

• dsmc restore /home/jones/proja

• To restore a backup set from the /dev/rmt0 tape device, enter:

• dsmc restore backupset /dev/rmt0 -location=tape

Note: You can use wildcard characters to restore groups of files, or entire directories.

Performing a Command Line Archive

Use the archive command to archive a single file, a group of files, or all files in a directory and its subdirectories. If you want to archive all the files in a directory and its subdirectories, use the subdir=yes option. Use the deletefiles option if you want TSM to delete the files from your local workstation after they are archived and committed to storage.

For example, to archive the files in the /home/jones/proj directory and its subdirectories, enter:

dsmc archive /home/jones/proj/ -subdir=yes -deletefiles

You can use more than one file specification with the archive command. For example, to archive the /home/jones/h1.doc and /home/jones/test.doc files, enter:

dsmc archive /home/jones/h1.doc /home/jones/test.doc

Use the description option to assign a description to the archive, as follows:

dsmc archive /home/jones/h1.doc -description="Chapter 1, first version"

Retrieving Archives

You can use the retrieve command to retrieve files or directories. Enter the file name you want to retrieve and its destination. If you do not indicate a destination, the files are retrieved to their original location. For example, to retrieve the /home/jones/h1.doc file to its original directory; enter:

dsmc retrieve /home/jones/h1.doc

To retrieve this file under a new name, enter:

dsmc retrieve /home/jones/h1.doc /home/jones/h2.doc

Displaying Command Line Help

To display command line help, enter the following command:

dsmc help

________________________________________

Using the Web Client

You can use the Web client to perform backup, archive, restore, and retrieve operations from any machine, or platform that supports a Java 1.1.6-capable browser, such as Netscape Navigator 4.06 or higher, and Microsoft Internet Explorer 4.01 or higher. Using the Web client, you can back up and restore your own data, or a TSM administrator can centralize the backup or restore operations of many TSM clients. To use it, simply point your Web browser at any TSM client machine that is running the Web client. The Web client is only supported on a server that is Version 3 or higher.

All backup and restore procedures in this chapter are also supported on the Web client. The following functions are not supported by the Web client:

• Estimate

• View Policy Information

• Access Another User

• Searching and Filtering

• User Access List

• Setup Wizard

• Querying and Restoring Backup Sets

To use the Web client, perform the following steps

1. If you do not already have password files generated for TSM clients, specify passwordaccess generate in the dsm.sys options file.

2. To create the TSM password file, start the native backup-archive client by entering:

3. dsmc query session

and, when prompted, enter your user ID and password.

4. Quit from the native TSM backup-archive client.

5. Start the TSM Client Acceptor daemon by entering the dsmcad command. The TSM Web client agent service automatically starts when needed.

The only options you can use with the dsmcad command are optfile, httpport, and httpsport.

All the Web client messages are written to the Web client log file, dsmwebcl.log. Error messages are also written to the TSM error log file. The dsmwebcl.log file and the TSM error log file are located in the same directory specified by the errorlogname option.

6. To use a Web client with an enterprise management server, ensure that you were assigned an administrative user id with system privilege, policy privilege, client access, or clientowner authority. If your server does not support enterprise management, then use your node name and password when prompted by the Web client. To determine whether your server supports enterprise management, contact your server administrator.

Note: Use the revokeremoteaccess option to restrict an administrator with client access privilege from accessing your workstation through the Web client. Administrators with clientowner privilege, system privilege, or policy privilege can access the Web client.

7. You can access the TSM Web client using any browser that is Java1.1.6-capable by entering the following URL:

8. http://your_machine_name:1581

where your_machine_name is the hostname of the machine running the TSM Web client.

Port 1581 is the default port number. The administrator can set a different port number using the httpport option.

The Web client workstation can also be accessed through the TSM system administrative GUI.

If you want to use the Web client with secure socket layer (SSL) communications, which is only supported on the AIX clients, see the Appendix in Tivoli Storage Manager Installing the Clients, order number SH26-4119, for more information.

________________________________________

Summary of Commands

dsmc archive [options] filespec|"filespec"
dsmc backup image [options] filespec|"filespec"
dsmc cancel restore [options]
dsmc delete access [options]
dsmc delete archive [options] filespec|"filespec"
dsmc delete filespace [options]
dsmc help
dsmc incremental [options] [filespec|"filespec"]
dsmc loop [options]
dsmc macro macroname
dsmc query access [options]
dsmc query archive [options] filespec|"filespec"
dsmc query backup [options] filespec|"filespec"
dsmc query backupset [options] [backupsetname|filename]
dsmc query filespace [options]
dsmc query image [options] logicalvolumename|filespacename
dsmc query mgmtclass [options]
dsmc query restore [options]
dsmc query schedule [options]
dsmc query session [options]
dsmc restart restore [options]
dsmc restore [file] [options] sourcefilespec|"sourcefilespec" [destinationfilespec]
dsmc restore backupset [options] [backupsetname|filename sourcefilespec|
"sourcefilespec" [destinationfilespec]
dsmc restore image [options]sourcefilespec|"sourcefilespec" [destinationfilespec]
dsmc retrieve [options] sourcefilespec|"sourcefilespec" [destinationfilespec]
dsmc schedule [options]
dsmc selective [options] filespec|"filespec"
dsmc set access [archive|backup] filespec|"filespec" node [user] [options]
dsmc set password [oldpw newpw] [options]

Read More

TSM Client Backup Guide

TSM Backup Principles

TSM Capabilities:

The following passages are from the TSM server documentation and serve as an overview of only a small subset of capabilities that TSM offers. These are the most frequently used capabilities, but even still, only the “Backup and restore” option is the one which our TSM backup service utilizes. Our TSM backup service uses the progressive backup method (incremental forever).

Backup and restore

The backup process copies data from client workstations to server storage to ensure against loss of data that is regularly changed. The server retains versions of a file according to policy, and replaces older versions of the file with newer versions. Policy includes the number of versions and the retention time for versions. A client can restore the most recent version of a file, or can restore earlier versions.

Archive and retrieve

The archive process copies data from client workstations to server storage for long-term storage. The process can optionally delete the archived files from the client workstations. The server retains archive copies according to the policy for archive retention time. A client can retrieve an archived copy of a file.

File-level Backup Policies:

Policies available to you are defined with four parameters. The table below outlines the use of each parameter:

TSM marks versions of a file as inactive once a new “active” version is backed up, once the file is deleted, or when it is excluded. Once a file is deleted or excluded, TSM marks all versions inactive. If the file exists on the host and it is not excluded from backups, there will always be an active version on TSM.


Our policy information can be found in the “Data Retention Form”. Please keep in mind that these policies are for data protection only. Any need for archiving, long-term retention, or bare system restores will not be addressed by these policies.

When registering for the service, you must specify one default retention plan. You may configure your client to back up certain files or filesystems under non-default policies by creating an include-exclude list. Refer to the include-exclude list documentation.

TSM Client Installation and Configuration

Client components which are normally installed are:


• Client Native GUI

• Client Web GUI

• Client Command Line Interface

• Client Acceptor Daemon and Scheduler


Refer to client readme as some of these features are not included with some platforms (i.e. Netware does not have a native GUI).

For quick and easy installation procedures, please see the  below e:

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmc.doc/baclients.html

Though installation and configuration can be pretty straightforward, there are many other options available in TSM to fine-tune your backups for performance and space-saving benefits.  Most clients should operate well with defaults, but if you run into bottlenecks, or your clients are eratic, consider setting some advanced configuration options.

Advanced Client Configuration

Unix/Linux/Mac OS clients rely on the dsm.opt and dsm.sys files for configuration options.
Windows/Netware clients rely solely on dsm.opt files for configuration options.
For official documentation for all available options, refer to:

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmc.doc/baclients.html

Include/Exclude lists dictate what to backup, and what policies should files be placed under.


Exclude Statement Structures

exclude [file] Excludes files from backups and archives

exclude.archive [file] Excludes file from archives

exclude.fs [filesystem] Excludes filesystem from backups and archives

exclude.dir [directory] Excludes directory from backups and archives

exclude.compression [file] Excludes file from compression


Include Statement Structures

include [file] [class]
 Includes file for backups and archives. If class is specified, then it binds the file to that management class. Otherwise, it uses the default.

include.archive [file] [class]
Includes file for archives only. If class is specified, then it binds the file to that management class. Otherwise, it uses the default.

include.compression [file]
Includes file for compression only if “Compression yes” is specified in options file.

A note regarding the use of wildcards for include/exclude processing (Unix syntax):

/… : matches 0 or more directories

* : matches and characters/files

? : matches any one character

[ ] : matches a character class enumeration or range

If you exclude a file with /… then all subdirectory information is backed-up. The files contained in those directories are not. For spaces in file names, use single-quotation marks.


A note regarding the order of exclude/include lists (Unix syntax):

Tivoli Storage Manager evaluates all exclude.fs and exclude.dir statements first (regardless of their position within the include-exclude list), and removes the excluded file spaces, directories, and files from the list of objects available for processing. All other include-exclude statements are processed from the bottom of the list up. Therefore, it is important to enter all your include-exclude statements in the proper order. For example, in the following include-exclude list the includefile.txt file is not backed up:


include /home/usr/includefile.txt

exclude /home/usr/.../*

However, in the following include-exclude list the includefile.txt file is backed up:

exclude /home/usr/.../*

include /home/usr/includefile.txt

For more detailed information on the usage of include-exclude lists, refer to the official documentation:

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmc.doc/baclients.html:

TSM Client Operations

This section details the client operations that you may encounter after the installation. Maintenance, backups, and restores are covered.


Regular Client Maintenance:

Regular maintenance tasks include:

• Checking the backup log for files that have consistently failed backing up. Files with backup errors are good candidates for exclusion or for corrective measures. Scheduled backup logs and error logs are available on all clients:

Windows: C:\Program Files\Tivoli\TSM\baclient\

Netware: SYS:\tivoli\tsm\client\ba\

Linux: /opt/tivoli/tsm/client/ba/bin/

Solaris: /opt/tivoli/tsm/client/ba/bin/

AIX: /usr/opt/tivoli/tsm/client/ba/bin/

Mac OS X: /Library/Logs/tivoli/tsm/

TSM Scheduled vs. Manual Backups:



Scheduled backups are handled through the ManagedServices client option along with server-defined schedules. The legacy way of handling schedules was through the “dsmc sched” command. The dsmcad does the following to pick up its scheduled backup time:

1. Once the administrator runs dsmcad, it sits in the background.

2. dsmcad kicks off the scheduler after a minute, and the scheduler queries the server for its next scheduled action (either another query or incremental backup). It logs to the dsmsched.log and exits.

3. dsmcad remains idle until its next scheduled activity.


Manual backups are handled either through the GUI or commandline.

Command line sample:

# dsmc incremental “/usr/*”

The incremental backup performs versioning-based backups. A selective backup forces all files to be backed up:
# dsmc selective “/usr/*”

TSM Client Restores - Techniques and Best Practices:

TSM classifies restores into two categories: no-query restore, and traditional restores.

Traditional Restores

Traditional restores involve the specification of a particular file or files to be restored. The GUI offers the easiest method to identify precise versions of files that you need restored. However, the command line also offers traditional restores.

Example:

#dsmc restore “/home/*/foo.*” –pick -inactive

No-Query Restores

A no-query restore (also known as a restartable restore) offers disaster recovery for directories and filesystems. A single wild-card specification identifies the restore as a no-query restore.

Example:

#dsmc restore “/var/tsm/*” –subdir=yes

Best Practices

Below are recommendations for improved restore times:

• For large restores, familiarize yourself with the command line client (dsmc). It is a more powerful mechanism for file restoration than the GUI, though it is less user friendly.

• For point-in-time restores, the GUI offers the easiest method to identify which files you need precisely.

• For large restores, try running multiple restore sessions at the same time. Though restores may compete for tape resources, each session will run to completion so less intervention is necessary.

Client Commands

Query backup and arch:

>/usr/bin/sudo /usr/bin/dsmc q arch –subdir=1 –fromnode=

>/usr/bin/sudo /usr/bin/dsmc q arch –subdir=1 –fromnode=

-fromdate=08/20/2006 -fromtime=11:00 -todate=08/20/2006 -totime=17:00 /db/abc/oradata01/

>/usr/bin/sudo /usr/bin/dsmc q back –subdir=1 –fromnode= /db/abc/oradata01/

>/usr/bin/sudo /usr/bin/dsmc q back –ina –subdir=1 –fromnode= /db/abc/oradata01/

Backup and arch:

>/usr/bin/sudo /usr/bin/dsmc arch –subdir=1 –desc=” OAPR_hotdb” /db/abc/oradata01/ -archmc=”OAPRHOT”

>/usr/bin/sudo /usr/bin/dsmc arch –subdir=1 "” /db/abc/oradata01/ -archmc=”OAPRHOT” -desc=”OAPR_hotdb_"%%$DATE._%%TIME

>/usr/bin/sudo /usr/bin/dsmc incremental –subdir=1 /db/abc/oradata01/

Restore and retrieve:

> /usr/bin/sudo /usr/bin/dsmc retrieve -subdir=yes -fromnode=- desc="ABCD_COLD_20060820_11:00" /db/ABCD/oradata02/ /db/ABCD/oradata02/

>/usr/bin/sudo /usr/bin/dsmc retrieve -subdir=yes -fromnode=-fromdate=08/20/2006 -fromtime=11:00 -todate=08/20/2006 -totime=17:00 /db/ABCD/oradata02/ /db/ABCD/oradata02/

> /usr/bin/sudo /usr/bin/dsmc restore -subdir=yes -fromnode=- desc="ABCD_COLD_20060820_11:00" /db/ABCD/oradata02/ /db/ABCD/oradata02/

To set Access to a node

>set access arch * node

or

>set access arch * *

To delete Access

type

>q access (to see the list then type)

>delete access

then choose the list to delete. such 1,2,3.

To see what is backedup on a client.

>q files

>q backup d:\

>q node

>q mgmt (policydomain) active * f=d

Read More

TSM Cheat Sheet

Command ▾	Common Arguments & Description	Command Description
IBMtapeutil	-f /dev/IBMchanger0 inventory (Run an inventory on the library, useful to see where tapes are physically located including in the hopper (import/export station))	IBM tape utility for Linux
audit libr	lib_name checkl=barcode (Audits the library "lib_name" and uses the barcode reader to read the storage volume label, to decrease the audit time.)	Audits and synchronizes volume inventories in an automated library
audit vol	V0123 (Audits the volume V0123)	Verify database information for a storage pool volume
cancel process	3 (Cancel process number 3)	Cancel an administrative process
checkin libv	lib_name search=bulk status=scratch checkl=barcode (Check volumes into the library "lib_name" as scratch searching the entry/exit ports (bulk). Read the barcode on the tape for quicker checkin times. Then type "q req" - see command below.)	Check scratch storage volumes from the hopper into the library
checkin libv	lib_name search=bulk vollist=V0123 status=scratch checkl=barcode (Checkin volume V0123 into the library "lib_name" as scratch searching the entry/exit ports (bulk). Read the barcode on the tape for quicker checkin times. Then type "q req" - see command below.)	Check a scratch storage volume from the hopper into the library
checkin libv	lib_name search=bulk vollist=V0123 status=private checkl=barcode (Checkin volume V0123 into the library "lib_name" as private searching the entry/exit ports (bulk). Read the barcode on the tape for quicker checkin times. Then type "q req" - see command below.)	Check a private storage volume from the hopper into the library
checkin libv	lib_name search=yes status=scratch checkl=barcode (Check volumes into the server inventory of the library "lib_name" as scratch searching the library). Read the barcode on the tape for quicker checkin times. Then type "q req" - see command below.)	Checkin a scratch storage volume searching the library into the library
checkin libv	lib_name search=bulk status=scratch checkl=yes (Check volumes into the server inventory of the library "lib_name" as scratch searching the entry/exit ports (bulk), reading the media label (checkl=yes). Then type "q req" - see command below.)	Checkin a scratch storage volume from the hopper reading the media label
checkout libv	lib_name V0123 checkl=no (Checkout volume V0123 from library "lib_name" and do not check the label)	Check a storage volume out of the library
checkout libv	lib_name V0123 checkl=no remove=no (Checkout volume V0123 from library "lib_name" without physically moving the tape and do not check the label)	Check a storage volume out of the library without moving the tape
clean drive	lib_name drive_name (clean the drive "drive_name" in the library "lib_name")	Clean a drive with a cleaning tape in the library
define	volume backuppool bkup01.dsm formatsize=200 (Increases the size of storage pool BACKUPPOOL by creating a 200MB volume named bkup01.dsm in BACKUPPOOL)	Define a volume in a storage pool
dismount	vol V0123 (Dismounts a volume V0123 from the drive)	Dismount a volume from the drive
dsmadmc	With no arguments - runs the administrative command line client	Start the administrative command line client
dsmadmc	-cons (Run dsmadmc in console mode to monitor TSM activities as they occur)	Start an administrative client session in console mode
dsmc arc	-archmc=LOGARC -deletefiles "/app/*" (Archive all files in /app binding the archived files to the LOGARC management class, then delete the files from disk after successful archival)	TSM client utility - Archive files
dsmc del	ar /opt* -su=yes -pick (Delete archive files in archive /opt and use the "pick" command to list the archive files to select)	TSM client utility - Delete archive files
dsmc i	-quiet > /tmp/tsm.out (Run an incremental backup (i) and only report errors (-quiet) and direct all output to the log file /tmp/tsm.out)	TSM client utility - Incremental backup
dsmc q	ar /opt* -subdir=yes (Display information about the files and subdirectories within the archive /opt. Run as root to see all files regardless of permissions)	TSM client utility - Query archived files
dsmc q	archive /opt* (Display information about the archive /opt)	TSM client utility - Query archived files
dsmc q	inclexcl (Display a list of include-exclude statements in the order in which they are processed during backup and archive operations)	TSM client utility - Query include-exclude statements
dsmc q	sess (Display information about your session including server and server connection information)	TSM client utility - Query session
dsmc rest	/app/ (Restore all files in /app not including sub-directories)	TSM client utility: Restore - no sub-directories
dsmc rest	-replace=all -subdir=yes /app (Restore /app including sub-directories replacing all files)	TSM client utility: Restore - including subdirectories
dsmc rest	-subdir=yes -inactive -dateformat=1 -pitdate=01/23/2011 /app/* (Perform a point in time restore of /app including sub-directories from the 23rd Jan. The latest file at or before this date including inactive files will be restored.)	TSM client utility - Point in time restore
dsmc sel	/home/vera -subdir=yes /app (Execute a selective backup of /home/vera including subdirectories. A selective backup will backup files regardless of whether they have changed since the incremental backup.)	TSM client utility - Selective backup
grant	authority jane classes=system (Grant system authority to the administrator jane)	Grant authority to administrator
halt	With no arguments - The halt command forces an abrupt shutdown, which cancels all the admin and client node sessions even if they are not completed. Any transactions in progress interrupted by the halt command are rolled back when the server is restarted.	Shutdown the server
itdt	(Select S to scan for devices, select a device from the list and then select D for a firmware dump (support information log)	ITDT IBM Tape Diagnostic Tool
label libv	lib_name checkin=scratch search=bulk labelsource=barcode overwrite=yes (Searches library "lib_name" entry/exit ports for useable volumes to label, attempts to read bar-code label and adds them to scratch pool. Then type "q req" - see command below.)	Label tape volumes
lslpp -L	| grep -i tsm (Lists the installed filesets and filters out any ones with tsm in the name)	Check if the TSM server or client is installed
move data	V0123 (Moves files from volume V0123 to other volumes in the same storage pool if they have space available)	Move files on a storage pool volume
move drm	V0123 wherestate=mountable tostate=vault (moves volume V0123 from mountable to vault. Used to ready tapes to go offsite and moves them to an exit port.)	Move disaster recovery media offsite and back onsite
move drm	V0123 wherestate=vaultret tostate=onsiteret (moves volume V0123 from vault retrieve to onsite retrieve)	Move disaster recovery media offsite and back onsite
q act	search=checkin begint=-6 (Query activity log for checkin processes within the last 6 hours)	Query activity log
q act	begind=MM/DD/YYYY begint=HH:MM:SS (Query activity log from date and time specified)	Query activity log
q assoc	With no arguments - display information about which client nodes are associated with one or more schedules	Query client node associations with a schedule
q copy	With no arguments - display information about one or more copy groups	Query copy groups
q drive	With no arguments - display information about all drives associated with the server	Query information about a Drive
q drm	With no arguments - display info about database backup and copy storage pool volumes	Query Disaster Recovery Media
q event	* * begint=05:00 (Query client events (i.e. backups) for all domains and schedules using wildcards *, starting from 5am.)	Query client scheduled and completed events
q event	* * nodes=node1 (Query client events (i.e. backups) for all domains and schedules using wildcards *, for node "node1")	Query client scheduled and completed events
q event	* t=a (Query events for all domains using wildcard *, for administration schedules t=a short for type=admin)	Query admin scheduled and completed events
q file	node1 (Display info about file spaces (as of the last incremental backup) that belong to the client node node1)	Query one or more file spaces
q libv	With no arguments - query all volumes in all libraries	Query a library volume - Displays info about checked in volumes
q mount	With no arguments - display info about the status of all sequential access volumes that are mounted. (Shows if there are any tapes in the drives)	Display info on mounted sequential access volumes
q node	f=d (Display detailed info about all registered nodes including TSM client version)	Display info about one or more registered nodes
q opt	With no arguments - display information about server options such as BufPoolSize	Query server options
q path	With no arguments - displays information about all paths associated with the server	Query a Path Definition
q proc	With no arguments - display all active background process information	Query one or more server processes
q req	With no arguments - display info about all pending mount requests. See "reply" command below	Query one or more pending mount requests
q sch	schedule_name t=a f=d (Display detailed information (f=d) about the admin (t=a) schedule "schedule_name" (default displays client schedules))	Displays information about schedules
q script	With no arguments - display info about all scripts	Displays information about TSM scripts
q script	script_name f=r (Display the code of the script "script_name" to the console)	Displays the code of TSM scripts
q sess	With no arguments - display information about admin and client node sessions	Query client sessions
q status	With no arguments - display information about system parameters	Query system parameters
q stg	stgpool_name (Display detailed (f=d) information about storage pool "stgpool_name")	Query storage pools
q vol	vol_name f=d (Display detailed info about volume "vol_name")	Query storage pool volumes
q vol	access=unavailable (Display volumes with access set to unavailable)	Query unavailable storage pool volumes
q volh	t=dbb (Display history information about full and incremental database backup volumes)	Display sequential volume history information
register	admin jane poppy (Register an administrator with a user ID of jane and a password of poppy)	Register an administrator
reply	2 (Use "q req" first for the ID number, then reply (if required) to inform the server you have completed a requested operation.)	Allow a request to continue processing
reset	bufpool (Reset the buffer pool counter)	Reset the counters that track server statistics
run	script_name (Run script "script_name")	Run a TSM script
set	actlogretention 8 (Set the activity log retention period to 8 days)	Set a value for a TSM object
setopt	bufpoolsize 262144 (Update the server option bufpoolsize to 256MB without restarting the server)	Set a server option for dynamic update
tapeutil	-f /dev/IBMchanger0 inventory (Run an inventory on the library, useful to see where tapes are physically located including in the hopper (import/export station))	IBM tape utility for AIX
upd drive	lib_name drive_name online=no (Update the drive in the library "lib_name" with drive name "drive_name" to be offline)	Update a drive
upd path	source_name destination_name srct=server destt=drive library=lib_name online=yes (Change the path to the drive to online. Here source type is server and dest type is drive. Use q path to get the relevant details for this command.)	Update a path to a drive
upd path	source_name destination_name srct=server destt=library online=no (Change the path to the library to offline. Here source type is server and dest type is library. Use q path to get the relevant details for this command.)	Update a path to the library
upd sch	schedule_name t=a startt=08:00(Update the admin schedule "schedule_name" by changing its start time to 08:00)	Update an administrative schedule
upd sch	schedule_name t=a cmd="migrate stg notes_disk lowmig=0" active=yes(Update the admin schedule "schedule_name" by specifying the administrative command to be scheduled for processing (cmd="") and make the schedule active.)	Update an administrative schedule
upd stg	stgpool_name reclaim=90 (Update storage pool stgpool_name and set the reclamation threshold to 90%. Therefore if the volume has 10% utilisation or less the tape can be reclaimed and made available for resuse)	Update a storage pool's reclamation threshold
upd stg	stgpool_name maxscr=50 (Update the storage pool "stgpool_name" and set the "Maximum Scratch Volumes allowed" parameter to 50)	Update a storage pool and set max scratch
upd vol	vol_name access=readwrite (Give vol_name read/write access)	Change access mode for one or more storage pool volumes

Read More

AIX-Backup and Recovery

Backup rootvg using mksysb

mksysb

• Creates an installable image of the root volume group either in a file or on to a bootable tape
• Bootable tape is created in backup format
• Can be restored individual files/directories using restore command
  

mksysb

        -e  /excludes files in /etc/exclude.rootvg 
        -i  to create image.data file
        -v  verbose mode 
        -X  extend /tmp filesystem if necessory for storing boot image

-i option calls mkszfile command which inturn creats /image.data file.

The bootable mksysb volume contains four images

1. Boot image
2. bosinstall image (image.data, bosinst.data, tapeblksz, etc..)
3. An empty table of contents
4. System Backup Image in Back up format

/bosinst.data file contains answer for questions during installation time such as Console name, Installation methode, locale seetings, etc.. If there is no /bostinst.data file present, then a sample file /usr/lpp/bosinst/bosinst.template is copied as /bosinst.data during backup process.

/image.data file contains logical volume and filesystem information of root volume group which is used by BOS install for creating target rootvg. If you want to create a custom image.data file, create the file using mkszfile, modify the file as per your requirement and call the mksysb command without -i option.

With these two files, it is possible to carry out an un-attended installation.

Examples:

To create system backup and create an /image.data file

 # mksysb -i /dev/rmt0

To exclude files and directories stored in /etc/exclude.rootvg file

 # mksysb -i -e /dev/rmt0

To store the mksysb image to a file called /stage/backp/mksysb.img

 # mksysb /stage/backp/mksysb.img

Backup or restore VGs using savevg and restvg

savevg command is used to backup volume groups other than rootvg
restvg command is used to restore volume groups other than rootvg

savevg

   -e excludes files/directories being backed in /etc/exclude.<vgname> file
   -i creates /tmp/vgdata/<vgname>/<vgname>.data file
   -f <device>  device or filename on which the image to be stored
   -v verbose mode
   -X automatically expand /tmp filesystem if required

-i option calls mkvgdata command which inturn creates /tmp/vgdata/<vgname>/<vgname>.data file

restvg

Backing up a filesytem or files

Restore files

restore

       -q  tells restore commnad that volume is ready
       -t, -T  to list the list of files in the backup archive
       -v  verbose
       -r  restores all files in the filesystem archive
       -x  to restore specifig files/directories
       -d  to restore all files in a directory if the File parameter is a directory
       -s <number>  To seek and restore the multiple backup tapes

To list the names of files in either a file-name or file-system archive

  # restore -Tq -f /dev/rmt0

To list all the files in a mksysb tape backup

  # restore -Tvqs 4 -f /dev/rmt0.1      

To restore an entire file-system archive, enter:

  # restore -rvqdf /dev/rmt0

To restore a specific file

  # restore -xvqf myhome.bkup system.data

To restore a specific file "/etc/passwd" from mksysb image file "mksysb.host1"

  # restore -xvqdf mksysb.host1 ./etc/passwd

Extracting data from mksysb tape

 a. Rewind the tape using the command:
    # tctl -f /dev/rmt0 rewind
 b. Move the tape forward to the third tape marker (beginning of fourth image):
    # tctl -f /dev/rmt0.1 fsf 3
 c. Restore data:
    # restore -xqvf /dev/rmt0.1 /tmp/my_file

Read More

Netbackup Cheat Sheet

Master Server Daemons/Processes

Request daemon	bprd
Scheduler	bpsched (started with bprd)
Netbackup database manager	bpdbm (started with bpsched)
Job Monitor	bpjobd (started with bpdbm)

Media Server Daemons/Processes

Communications daemon	bpcd
Backup and restore manager	bpbrm (started with bpcd)
Tape Manager	bptm (started with bpbrm)
Disk Manager	bpdm (started with bpbrm)
Media Manager	ltid
Bar code reader	avrd (started with ltid)
Remote device management/ controls volume database	vmd (started with ltid)
Roboticdaemon (one on each media server) talks to tldcd	tldd (started with ltid)
Robotic control daemon talks to the robot directl via scsi	tldcd (started with ltid)

Catalogs

Master Server
Information about backed-up files	image - /opt/openv/netbackup/db
Storage Unit, Global Configuration, Catalog backup configuration.	config - /opt/openv/netbackup/db
Backup Policy information	class - /opt/openv/netbackup/db
Job status information	jobs - /opt/openv/netbackup/db
Netbackup logs with error and status information	error - /opt/openv/netbackup/db
Information on volumes, volume pools, scratch pool and volume groups	volume - /opt/openv/volmgr/database
Media Server
Tracks assigned volumes (media that has data them)	media - /opt/openv/netbackup/db
Information about devices managed by the media server	device - /opt/openv/volmgr/database

Log and Information Files

Netbackup and Patch versions	/opt/openv/netbackup/bin/version
Media Version	/opt/openv/volmgr/version
Patch Level history	/opt/openv/netbackup/patch/patch.history
Buffer size	/opt/openv/netbackup/db/config/SIZE_DATA_BUFFERS
Number of buffers	/opt/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
Network Buffer Size	/opt/openv/netbackup/NET_BUFFER_SZ (default = 32)
Java GUI authorisation	/opt/openv/java/auth.conf
Catalog type (binary or ASCII)	/opt/openv/netbackup/db/config/cat_format.cfg
Netbackup and media manager parameter files	/opt/openv/netbackup/bp.conf /opt/openv/volmgr/vm.conf
Corrupt Database image files (5.0 and above)	/opt/openv/netbackup/db.corrupt

Server Commands

Check license details	/opt/openv/netbackup/bin/admincmd/get_license_key
Start Netbackup	netbackup start /opt/openv/netbackup/bin/initbprd (master) /opt/openv/volmgr/bin/vmd (media)
Stop Netbackup (does not disconnect GUI sessions)	netbackup stop /opt/openv/netbackup/bin/admincmd/bprdreq -terminate (master) /opt/openv/netbackup/bin/bpdbm -terminate (master)
Stop Netbackup and kill all GUI sessions	/opt/openv/netbackup/bin/goodies/bp.kill_all
Start the GUI	/opt/openv/netbackup/bin/jnbSA
Scan for tape devices	sgscan (solaris) ioscan (HPUX)
Display all Netbackup processes	bpps -a
lists servers errors	bperror -U -problems -hoursago <number of hours> bperror -U -backstat -by_statcode -hoursago <number of hours>
display information on a error code	bperror -statuscode <statuscode> [-recommendation]
Reread bp.conf file without stopping Netbackup	bprdreq -rereadconfig
Check database consistency	bpdbm -consistency 1 bpdbm -consistency 2 Check for the below lines: Bad image header Does not exist
Netbackup Recovery
Device catalog is intact	bprecover -l -m <media ID> -d dlt (listing) bprecover -r -m <media ID> -d dlt (recovering)
Device catalog is gone or corrupted	bprecover -l -tpath <tape_path> (listing) bprecover -r -tpath <tape_path> (recovering)
Disk backups	bprecover -l -dpath <disk_path> (listing) bprecover -r -dpath <disk_path> (recovering)

Volume Commands

Tape Drive and Inventory Commands
List drive status, detail drive info and pending requests	vmoprcmd
List the tape drive status	vmoprcmd -d ds
List the pending requests	vmoprcmd -d pr
Control a tape device	vmoprcmd [-reset][-up][-down] <drive number>
List all changes in the robot(but do not update)	vmupdate -recommend -rt tld -rn 0 vmcheckxxx -rt tld -rn 0 -recommend
Empty the robot and re-inventory (using barcodes)	vmupdate -rt tld -rn <robot number> -rh <silo slave> -vh <host> -nostderr -use_barcode_rules -use_seed -empty_ie
Tape Media Commands
List all pools	vmpool -listall -bx
List tapes in pool	vmquery -pn <pool name> -bx
List all tapes in the robot	vmquery -rn 0 -bx |grep 'TLD' | sort +4
List cleaning tapes	vmquery -mt dlt_clean -bx
List tape volume details	vmquery -m <media ID>
Delete a volume from the catalog	vmdelete -m <media ID>
Change a tapes expiry date	vmchange -exp 12/31/06 23:59:58 -m <media ID>
Change a tape's media pool	vmchange -p <pool number> -m <media ID>

Media commands

List the storage units	bpstulist -U
Freeze or unfreeze media	bpmedia [-freeze][-unfreeze] -ev <media ID>
List media details	bpmedialist -ev <media ID>
List media contents	bpmedialist -U mcontents -m <media ID>
List backup Image Information	bpimagelist -backupid <image ID>
Expire client images	bpimage -cleanup -allclients
Expire a tape	bpexpdate -d 0 -ev <media ID> -force
List all netbackups jobs	bpdbjobs -report [-hoursago]
Move media from one media server to another	bpmedia -movedb -newserver <media server> -oldserver <media server>

Tape/Robot commands

List tape drives	tpconfig -d
List cleaning times on drives	tpclean -L
clean a drive	tpclean -C <drive number>
change a drives cleaning frequency	tpclean -F <drive> <frequency>
set a drives cleaning time to zero	tpclean -M <drive>
Move tapes within robot using robtest	robtest commands that can be used are as follows: s s       (show slots) s d       (show drives) s i       (show load port) m s300 d5 (move tape from slot 300 into drive 5) uload d5  (unload tape from drive 5) m d5 s300 (move tape from drive 5 to slot 300) m s300 i1 (mov tape from slot 300 to load port 1)
List load port tapes	echo "s i q" | tldtest -r /dev/sg/c0t4l0
List all slot contents	echo "s s q" | tldtest -r /dev/sg/c0t4l0
List tape drive contents	echo "s d q" | tldtest -r /dev/sg/c0t4l0
Move a tape in s100 to drive 1	echo "m s100 d1" | tldtest -r /dev/sg/c0t4l0
Move a tape to load port 1	echo "m s100 i1" | tldtest -r /dev/sg/c0t4l0

Archiving Commands

list archive info	bpcatlist -client all -before Jul 01 2006 bpcatlist -client all -before Aug 01 2006
archive and remove images	bpcatlist -before Jul 01 2006 | bpcatarc | bpcatrm
restore archive files	bpcatlist -before Jul 01 2006 | bpcatres

Client commands

test client connectivity

bpclntcmd [-ip <ip addres>] bpclntcmd [-hn <hostname>] bpclntcmd [-pn] bpclntcmd [-sv]

Read More