TSM deprecated

New archives for TSM are no longer supported. Archiving solutions and data management is provided using iRODS.

Archiving on MOGON

While we try to ensure regular backups on MOGON, this does not include archiving solutions. These are kindly provided by our colleagues from the ZDV-UNIX group

Before contemplating archiving solutions for your group, please check whether your group already possesses a ZDV-archive. If in doubt, please write a mail to with your inquiry.

Likewise you can apply for an archive at Please note, that external users will be send an invoice on a yearly basis. Please ask for conditions in your mail. Internal users should be aware that there is currently no charge to them.

Instead of specifying the archive server always as, use the one assigned for your group. This will be tsm02 for most practical purposes, we therefore used that for our examples.

The archiving software is wrapped with a script. In order to list filespaces which have been archived invoke it like

$ /cluster/bin/tsmarchive archivetest query filespace

Output will be like:

> IBM Tivoli Storage Manager
> Command Line Backup-Archive Client Interface
>   Client Version 7, Release 1, Level 6.5 
>   Client date/time: 08/18/2017 12:23:03
> (c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights Reserved. 
> Please enter your user id <ARCHIVETEST>:

Now, users need to confirm with their ID, which is identical to the node in question (this is information you obtain with your archiving account), and hitting Enter/Return.

Then, your password is required:

> Please enter password for user id "ARCHIVETEST": 

An alternative way is to provide the password with -password on the command line.

It is possible to inquire what has been archived, e.g. on /gpfs/fs1/:

$ /cluster/bin/tsmarchive archivetest query archive /gpfs/fs1/ -subdir=yes -password=<your password>

When knowing a given description, one can search for it:

$ /cluster/bin/tsmarchive archivetest query archive c:\ -su=y -descr="some description"

Known Issues

When invoking the archiving command the client might complain about existing files it cannot write to (particularly dsmerror.log and dsminstr.log1). Try to delete those and proceed.

$ /cluster/bin/tsmarchive archivetest retrieve <path you want to restore> -sub=yes -descr=\"<your description>\"

The description can be omitted, but in case of double entries (entries with identical paths but different descriptions) a description is mandatory to retrieve the correct archive version.

If a recursive retrieval for a given path is desired a trailing slash / is required to amend to your path, like when archiving.

Getting help is as simple as:

$ /cluster/bin/tsmarchive archivetest help

or specific

$ /cluster/bin/tsmarchive archivetest help archive

This one will only cause a warning.
  • start/fs_dm/archiving/tsm.txt
  • Last modified: 2020/04/16 11:58
  • by jrutte02