File Backup (TSM)

File backup is a practice that can save you hours of headache if a system crash occurs. Hardware failures can occur without notice so it is critical for you to have a backup copy of your important files. There are several ways to backup your system. You can burn your data on CDs, save to an external hard drive, or use use a backup client like TSM.

TSM (Tivoli Storage Manager) provides functionality that allows employees of Auburn University to backup their local computer or specific files on their local computer to an OIT network server. Employees must use their username for their TSM user id and TSM password when logging in to the TSM client.

Common Topics

  • Information about TSM backup software

    ADSM, now renamed Tivoli Storage Manager (TSM), provides flexible, powerful backup protection of desktop computer hard drives to an OIT network server. The client runs on Windows, Macintosh, Linux and a variety of Unix platforms. Lost files can be recovered by restoring them from the server.

    TSM is site licensed and provided at no additional cost to the Auburn University community. Backing up from off-campus is not recommended unless the connection is at least as fast as cable/DSL connections.

    All employees at Auburn University have an username established for them. An AU employee's TSM account is automatically activated when the username is assigned. Of course, it is important to note that the employee is still responsible for downloading and running TSM on their University computer.

  • System requirements
    • Use TSM version 5.2
    • Pentium-based processor
    • 32 MB of RAM
    • 50 MB available disk space
    • TCP/IP Communications capability
    • Current web browser (Internet Explorer is recommended)

    Connection Speeds

    If you are off-campus and wish to use TSM, it will be necessary for you to have a high bandwidth Internet connection such as DSL or Cable. Dial-up connections will not work properly.

  • Procedure for requesting TSM backup restrictions exemption

    In extenuating circumstances, it is possible for distributed IT providers or Administrative Computing Coordinators to request that a machine be exempted from the recently announced TSM backup restrictions.

    If you identify such a system in your area, the procedure for making a request for exemption is outlined below. Keep in mind, that this should be reserved for critical needs only.

    1. Send an e-mail request for exemption from TSM backup restrictions tohelpdesk@auburn.edu.
    2. Provide the TSM node name, user's name and campus contact information (address, phone, e-mail).
    3. Provide justification for the exemption requested.
    4. Provide your name and campus contact information.

    Your request will be reviewed and you will receive a reply from the Office of Information Technology within two (2) business days. Feel free to follow up at helpdesk@auburn.edu anytime.

  • TSM - Important background information

    Below are some important facts that you should know about TSM and its uses on the Auburn University campus.

    • What the backups exclude

      Backups for Windows platforms exclude things like network drives and Windows system objects. This change was made December 18, 2003, in order to make more efficient use of our backup storage space. There will be no interruption of your regularly scheduled backups using TSM, and everything in My Documents and Program Files will continue to be backed up.

      Windows profiles and favorites will be included. If you have any questions or concerns about the backup routine used on your desktop computer, please consult the IT specialist for your area or the OIT HelpDesk at (334) 844-4944 or helpdesk@auburn.edu.

    • What is restored on your computer

      Files backed up with TSM can be restored to recover lost data or work files. However, TSM is not meant to be used for restoring everything on your hard drive or to restore software. Remember, TSM is for disaster recovery. It cannot be expected to always contain any version of any file that you want.

    • Getting Started

      Be sure you've read and followed the "etting Started instructions".

    • Difference between active and inactive

      How long a backed up file is kept depends on whether it is "active" or "inactive". A file is considered "active" if it is still on your hard drive. "Active" files have a current copy available indefinitely on the server. "Inactive" files (that have been deleted from your hard drive) are only kept for a few weeks. Also, older versions of "active" files are deleted after a short time. Therefore, you will not be able to pull up multiple copies of the same file. TSM is for disaster recovery.

    • Security features

      TSM has a compression option that can be set at the client end. This option can be used for security purposes. It will keep the system from sending data in clear text; however, it will probably increase the overall back up time.

    • Options for running the scheduler

      The scheduler program runs in the system tray for Windows 98 and ME. For systems running Windows NT/2000 and XP, there are two options: run the scheduler as a service, or run it as a regular program where it will run as a DOS window which can be minimized while you work on something else. When run as a service, the scheduler is invisible to you. Whenever you want to back up your files overnight you can simply leave your PC running.

    • Archive is not allowed

      Users should back up with the Backup button.

  • Using different TSM IDs to back up multiple machines

    OIT strongly advises TSM users to use a single TSM ID (node name) for each machine that is backed up. To get additional TSM IDs for backing up multiple computers, contact your Administrative Computing Coordinator.

    Potential Problems

    Using a single TSM ID on more than one machine is not supported by the vendor; the software is designed to run in an environment where each machine on which the client runs is assigned a unique TSM ID (or 'node name', in Tivoli-speak). In practice this means that one must be very careful in attempting to use the same ID on more than one machine, and when problems are encountered we can expect no help from the vendor in trying to resolve them.

    Also, the behavior exhibited by TSM in this area is subject to change from one release of the software to another, with no announcements or explanations regarding changes. This is because the vendor neither codes for nor tests the use of a single ID on multiple machines. If you still wish to use the same TSM ID on more than one machine, then the following information may be helpful. These guidelines are the result of our experiences with version 4 of the TSM client.

    Proceed with caution if you plan to use the same ID to back up more than one machine!

    Incremental Backups

    The first potential problem arises when doing an incremental backup. TSM bases all of its decisions on what files to back up and what files to expire on its perceived status of what it calls a 'filespace'. What a filespace is depends to some extent on the platform on which the client is running. In Unix, a filespace is simply a filesystem (or part of a filesystem); in Windows, a filespace is a combination of Windows 'Computer Name' and drive letter.

    When an incremental backup is run, the TSM client compares the filespace as it currently exists on the machine with the filespace as it exists at the TSM server. Any differences will cause action to be taken by the client. For example, if a file on the local machine has been changed since it was last backed up, it will be backed up again. If a file exists in the filespace at the server, but not on the local machine, it will be assumed to have been deleted and will be marked inactive at the server. If you run an incremental backup on two different machines that both contain the same filespace name, you will very likely get unexpected and undesirable results.Files will be incorrectly marked inactive, etc.

    If you plan to run an incremental backup on more than one machine using the same TSM ID, then you must ensure that all filespace names involved are unique. On Windows, this can be accomplished by having unique Windows computer names; on Unix, having unique filespace names is impractical for system directories but might be possible for some other directories.

    Scheduled Backups

    Another problem arises if you attempt to use the TSM Scheduler to perform scheduled backups of multiple machines with a single TSM ID. Because the server assumes that an ID is only being used on one machine, all sorts of problems and misunderstandings can occur.

    Scheduler clients connect periodically to the server to request a time at which they should perform a backup, and they report to the server the success or failure of an attempted scheduled backup. It is left to the reader's imagination to come up with possible points of confusion and failure if multiple machines are attempting scheduled backups using the same ID. The bottom line is this: once a machine successfully completes a scheduled backup using a given TSM ID, no other machine can start a scheduled backup using the same TSM ID during the same backup window. (A backup window is generally the period from 6 p.m. one evening until 9 a.m. the following morning.)

    The more machines on which the same TSM ID is used to do scheduled backups, the greater the number of machines will not be backed up on a given night. For this reason, OIT recommends that you not use the same TSM ID on more than one machine on which you also run the TSM Scheduler, even if you can manage to ensure unique filespace names on the machines in question. The reliability of scheduled backups in this scenario is simply too poor.

    Unicode Support

    Support for Unicode filespaces was added to the TSM server in August of 2002. Unicode filespaces allow for greater flexibility in data being backed up from and restored to client platforms running under different national languages.

    Some TSM clients are capable of backing up filespaces in Unicode format while other clients are not. As of Fall 2002, the only Unicode capable clients are:

    • V4.2.0 or higher for Windows NT/2000
    • V4.2.1.15 or higher for Windows XP

    Now to how this affects using a single TSM ID on more than one machine. The important rule to keep in mind is this: once a filespace has been backed up to the server in Unicode format under a given ID, the server will not allow a non-Unicode capable client to connect using that ID. A filespace will be backed up in Unicode format under the following circumstances:

    1. The client doing the backup is Unicode enabled, and
    2. The filespace being backed up does not exist at the server in a non-Unicode format

    Number 2 above needs to be understood; the TSM server will not convert an existing filespace backup image to Unicode format, but if a new filespace is backed up (e.g., a new drive is added to an existing machine, or a drive that was previously being EXCLUDEd in the TSM client options is now being INCLUDED, or if an ID that was being used to back up one machine is later used to back up files on a second machine), that filespace will be backed up in Unicode format. Once that has happened, no non-Unicode capable client will be allowed to connect to the server using that ID.

    So, for example, if you're using the same ID from a Windows 2000 machine and a Mac, or a Windows 98 machine, etc., you might suddenly find that the client cannot connect from the Mac (or 98...) platform. You find that you're getting the following error message:

    ANS1357S Session rejected: Downlevel client code version

    More than likely what has happened is that a Unicode format filespace has been backed up and the server is rejecting connections for your ID from non-Unicode clients.

    The best solution to this problem is to use a given TSM ID for backing up one machine only. You can request additional TSM IDs for your machines by contacting the OIT Account Administrator.

  • TSM Filespace Cleanup (Automatic Filespace Deletion)

    TSM stores backup copies of your files in what it calls a 'filespace'. What a filespace is depends to some extent on the platform on which the TSM client is running. In Unix, a filespace is simply a filesystem (or part of a filesystem); in Windows, a filespace is a combination of Windows 'Computer Name' and drive letter. Note that for Windows platforms, when you get a new PC, the Windows computer name usually changes; this means that the c: drive from your old machine will be stored in one filespace, while the c: drive from the new machine will be stored in a different filespace.

    There are two circumstances under which TSM filespaces are automatically deleted:

    1. After your OIT-provided Auburn username/account is terminated
    2. Filespaces that are not backed up for a long time ("abandoned" filespaces)

    Account termination

    When your OIT-provided account is terminated, your TSM ID is renamed. Any data stored under your ID will remain at the server for six months. At that time, all backup data for your ID will be deleted from the server and the TSM ID will be removed.

    Abandoned filespaces

    The TSM server keeps a date/time stamp that records when a given filespace was last backed up. Note that this timestamp is only updated when a full incremental backup is done on a filespace. A full incremental backup happens in one of three ways:

    1. A scheduled backup runs
    2. From the TSM GUI client, "Actions/Backup Domain" is clicked
    3. A command line "dsmc incremental" backup runs

    Using the GUI to selectively back up files and directories, even if you back up the entire c: drive , does not result in a full incremental backup and does not update the 'last backed up' timestamp. For this reason, it is highly recommended that you perform backups using one of the three methods listed above.

    On the first weekend of each month, OIT runs a "cleanup abandoned filespaces" process.  This process does two things:

    1. checks the 'last backed up' timestamp of each filespace. For those filespaces that have not been backed up in at least 14 months, email is sent to the owner of the filespace. The email lists the filespace(s) that appear to have been abandoned and informs the owner that the filespace(s) will be deleted during the next month's cleanup. Note that the email is sent to address " TSM_ID@auburn.edu ". For most people, this is a valid email address; however, if you have multiple TSM accounts for multiple machines, there's a good chance that some of those accounts will not represent valid email addresses.  For that reason, we maintain a list of filespaces that are scheduled to be deleted during the next cleanup process.
    2. for filespaces that were emailed about during the previous month's run, check the 'last backed up' timestamp; if the filespace still hasn't been backed up, then it is deleted.

    If you see that a filespace of yours is scheduled to be deleted, you should check the filespace name to be sure that it is from a machine that you no longer have. If so, no action is necessary on your part. If the filespace is a backup of a hard drive that still exists, then you should perform a full incremental backup via one of the three methods listed above. This is the only way that the 'last backed up' timestamp will be updated.  You should also take steps to ensure that the drive continues to be backed up in the future.

    List of Filespaces Scheduled to be Deleted

     

    Backups to be Deleted the First Weekend of March
    TSM ID (Node Name) Filespace Date of last backup
    5CTUTSM\\huang-65ext\d$2010-11-15 15.49.43
    ALDERCW\\au15536\c$2010-11-12 20.23.04
    ARMSTM3\\au16642\c$2010-11-23 09.23.01
    ATC0005\\lib-atc-bucket\d$2010-12-01 18.32.10
    BARNASP\\au15510\c$2010-11-16 15.00.21
    BODYQST\\bodyquest\c$2010-11-12 18.19.25
    BRACKPD\\hsop-brackpd\c$2010-11-18 20.04.05
    BROWN18\\au17976\c$2010-11-17 07.27.31
    CHAPPA2\\sfws-kcxl0n3\c$2010-12-01 08.08.13
    CHAPPAH\\sfws-kcxl0n3\c$2010-12-01 11.31.22
    CHAVEMJ\\iittab2209\c$2010-11-09 07.24.47
    CHENGU1\\sfws-8hr5l61\g$2010-11-16 23.31.38
    CHENGU1\\sfws-8hr5l61\f$2010-11-17 14.56.02
    CHURCAE\\pathopc1978\d$2010-12-03 11.16.01
    CMS0014\\au15678\c$2010-11-11 00.56.22
    COOKJAN\\au13558\c$2010-11-17 19.24.09
    COOPST5\\au17502\e$2010-11-19 08.22.29
    CSMFS01\\cosam-fs-01\e$2010-11-19 18.14.49
    DAVISVD\\au15508\c$2010-11-12 11.20.12
    EDUSUPP\\au15446\c$2010-11-18 20.09.07
    EDWARCM\\au16616\c$2010-11-17 18.27.00
    EJO0001\\au16630\c$2010-11-17 09.01.48
    ERLANAH\\au13786\c$2010-11-18 08.41.50
    FRESHYR\\au15444\c$2010-11-29 20.11.50
    FULLESA\\au15492\c$2010-11-12 11.22.51
    FUN318\\funchess363-2\g$2010-11-22 21.32.21
    FUN318\\funchess363-2\h$2010-11-22 21.32.22
    GARREMI\\lib_au15756\c$2010-12-03 18.08.43
    GAYCONN\\au15548\c$2010-11-09 21.25.11
    HAHNMAS\\funchess-301c1\c$2010-11-19 00.12.39
    HAHNMAS\\funchess-301c1\i$2010-11-19 00.12.32
    HAMMEMM\\lib_au16166\c$2010-12-03 18.27.36
    HANKEDM\\au15458\c$2010-11-23 08.29.53
    HARTEMH\\au15498\c$2010-11-15 10.48.48
    HILLLAU\\rbd1022a-01\c$2010-11-08 22.10.58
    HILLLAU\\rbd1022a-01\e$2010-11-08 22.15.32
    HILLMIC\\au15468\c$2010-11-17 19.20.59
    HWANGMI\\srrcpc0311\c$2010-11-12 18.27.06
    IMPACT\\au16608\c$2010-11-18 19.18.32
    INTLEDU\\au13978\e$2010-11-23 20.33.44
    JAH0034\\au14762\e$2010-11-23 21.16.34
    JBS0003\\au15431\c$2010-11-19 08.05.44
    JJM0001\\hc6012\c$2010-12-02 22.31.44
    JJM0001\\hc6012\e$2010-12-02 22.36.11
    KALINLA\\sfws-32nztl1\c$2010-12-03 13.47.17
    KNIGHRP\\ausamba\public_html2010-11-11 10.50.03
    LAB0021\\radpc1209\e$2010-12-02 08.52.01
    LAB0021\\radpc1209\c$2010-12-02 18.56.09
    LEEMEAG\\au15476\c$2010-11-19 16.21.43
    LIBECTO\\lib-ecto1\e$2010-11-17 19.27.37
    LIBECTO\\lib-ecto1\c$2010-11-17 19.28.09
    LZM0020\\au13788\c$2010-11-12 14.59.56
    MACDODM\\csm-studentpc\g$2010-11-10 08.40.25
    MACDODM\\cosam-scc247c\c$2010-11-29 07.49.32
    MARKLCC\\au15490\c$2010-11-18 09.21.29
    MARTILI\\au15976-7\i$2010-11-05 08.28.31
    MARTILI\\au15976-7\c$2010-11-08 21.51.24
    MARTILI\\au15976-7\d$2010-11-08 21.52.00
    MARTILI\\au15976-7\e$2010-11-08 21.52.26
    MARTILI\\au15976-7\f$2010-11-08 21.53.16
    MARTILI\\au15976-7\h$2010-11-08 21.51.20
    MARTILI\\au15976\h$2010-11-16 22.32.42
    MCCALSM\\au17929\c$2010-12-03 09.29.58
    MCCALSM\\au17929\e$2010-11-10 08.21.18
    MCDANN1\\au15448\c$2010-11-18 22.24.06
    MCLANSL\\au18032\c$2010-12-03 08.17.23
    MEHRHJR\\au15530\c$2010-11-09 08.34.53
    MELDARS\\sfws-ralph-s-m\g$2010-11-20 09.27.57
    MHI0001\\pathopc2065\c$2010-11-16 09.23.32
    MOSELRU\\au16336\h$2010-12-01 08.05.34
    NAD0009\\au15334\c$2010-11-18 09.29.48
    NELSOJ2\\au14600\c$2010-11-29 19.14.27
    NSW0001\\au15544\c$2010-11-05 18.00.54
    ORION\\orion\c$2010-11-08 13.59.15
    ORION\\orion\g$2010-11-08 14.05.06
    PATTIAM\\au13546\c$2010-11-17 21.17.43
    PATTILA\\au16778\c$2010-11-29 09.18.28
    PRICKDR\\au15514\c$2010-11-16 22.06.59
    REYNOM2\\au12130\c$2010-11-23 10.18.36
    RIVERSY\\lib_au16180\c$2010-11-10 15.26.20
    ROEHMJM\\au17952\c$2010-11-22 21.56.21
    ROOKELV\\au15528\c$2010-11-05 21.34.44
    RUSSEJ3\\mc2078\k$2010-12-01 20.43.09
    SANFOPA\\au15540\c$2010-11-30 21.55.53
    SANTOVR\\ti0316\e$2010-11-30 22.52.48
    SGAPRES\\au16620\c$2010-11-16 20.17.02
    SGAVPAD\\au16618\c$2010-11-16 19.12.47
    SGAVPRS\\au16606\c$2010-11-16 20.41.00
    SINGLCL\\au15496\c$2010-11-09 08.34.42
    SMITHS2\\au15494\c$2010-11-17 10.54.40
    SNIPEDH\\au16794\c$2010-11-17 18.07.19
    TAL0002\\adminpc1266\c$2010-11-20 03.00.05
    TAL0002\\adminpc1266\f$2010-11-19 23.12.52
    TCD0006\\lib_au15864\c$2010-11-11 10.30.54
    TDS0009\\sfws-d70gng1\f$2010-11-03 20.29.41
    TDS0009\\sfws-d70gng1\e$2010-11-22 19.58.48
    TIANHAN\\sfws-2ua0441r8t\c$2010-11-15 12.04.52
    TIANHAN\\sfws-2ua0441r8t\d$2010-11-15 12.16.22
    VANVICK/Volumes/Time Machine (FreeAgent)2010-11-18 09.17.58
    VM1245\\avdlpc1245\e$2010-11-05 20.15.34
    WALKELB\\cosam-walkelb2\c$2010-11-18 18.20.39
    WCM0005\\sfws-2ua0371zd9\f$2010-11-19 21.07.06
    WILLI11\\au15460\c$2010-11-19 18.15.15
    WILSOT2\\au15474\c$2010-11-16 22.33.50
    WOFFOJL\\biomedpc1799\k$2010-11-10 11.09.06
    WOFFOJL\\biomedpc1799\f$2010-11-10 11.09.06
    WOODSAB\\au15472\c$2010-11-15 09.40.25
    YOUNGJ1\\au155550\c$2010-11-09 18.01.25

Starting Out

  • Getting started with TSM
    1. Know your username. All employees at Auburn University have an username established for them. An employee's TSM account is activated when the user name is assigned.
    2. To login the first time, you will type the user name in both the user name field and the password field. If this doesn't work, call the Help Desk at 844-4944 to have the TSM password reset.
    3. Make sure your computer meets the minimum system requirements.
    4. If you have an earlier version of ADSM or TSM, you will need to first uninstall it via Start > Settings > Control Panel > Add/Remove Programs.
    5. Install ADSM/TSM.
    6. Configure the ADSM/TSM scheduler.
  • Installing TSM
    1. Go to AU Install and click the "click here to download" button next to TSM 5.2.
    2. When prompted, choose to "Save" the installation to your desktop.
    3. Double-click the "tivoli_install_win32.exe" icon to start up the installer.
    4. When you see the screen below, enter your AU user name and click Next.

      Installing TSM
    5. Choose "English" or any language you desire when the "Choose Setup Language" box appears.
    6. Click "Next" through the following two screens.
    7. Choose "Typical" and click Next.

      Installing TSM
    8. Click "Install" on the next screen.
    9. The program will install the TSM software. Click "Finish" when it has completed and restart your computer.
  • Configuring the TSM scheduler manually
    1. From the Windows Start Menu, choose Programs, Tivoli Storage Manager, Backup Archive GUI.
    2. Choose Setup Wizard from the Utilities menu.

      Configure TSM Manually
    3. Select "Help me configure the TSM Client Scheduler" and click Next.

      Configure TSM Manually
    4. Select "Install a new or additional scheduler".

      If you have already created a scheduler task, you may choose the option to update a previously installed scheduler or remove a previously installed scheduler.

      Note: It is not recommended you run more than one scheduler at a time.

      Configure TSM Manually
    5. Enter a name of your choice for the scheduler and click Next.

      Configure TSM Manually
    6. Next you will be asked for the option file's name. Leave it as shown below.

      Configure TSM Manually
    7. Enable event logging. Leave the other selections as shown below.

      Configure TSM Manually
    8. Enter your username and TSM password.

      Configure TSM Manually
    9. Set the service login options to use "The System account" when logging into Windows NT and to start the service "Automatically when Windows boots" as shown below.

      Configure TSM Manually
    10. Click Finish to complete the configuration process

Using TSM

  • Logging in
    1. Locate the Tivoli Storage Manager from your Windows start menu and select Backup Archive GUI.
    2. When you configure TSM, it will remember your login information and go straight to the main menu.

      If you have to login, enter your AU User Name in both the "Node name" and the "Password" fields.

      Logging In to TSM
    3. You should now be logged into TSM.
  • Changing your password
    1. Locate the Tivoli Storage Manager from your Windows start menu and select Backup Archive GUI.
    2. Pull down the Utilities menu and select Change Password.
    3. Fill in the blanks with your current and new passwords.

      TSM
  • Backing up files automatically using the Scheduler

    TSM can be used to back up files overnight. Since the scheduler program is in the startup folder, it will be launched when you start up your machine. All you have to do is leave your machine running all night and the system will automatically back up your files.

    1. If you leave the scheduler running, it will back up your files every night.
    2. If the scheduler is configured to run as a service, just leave the computer turned on. If it runs as a window, be sure it hasn't been closed during the day. However, it only does a complete copy of all files and directories the first time you do a back up. After that, it only backs up the files that have changed.

      Note: Before backing up your system, make sure TSM is set up to only back up your local drives, usually C: and/or D:. Do not back up network drives such as G:, H: and Q: because they are already backed up by the system administrators and are very large. To check your settings, click Start > Tivoli Storage Manger > Backup Archive GUI > Edit > Preferences > Backup (look at the Domain List); then click Include-Exclude.
  • Backing up files manually

    If TSM has been configured from the web, it will back up all of the the data and program files on the hard drives but not the system files, recycle bin, or temporary internet files.

    1. Locate the Tivoli Storage Manager from your Windows start menu and select Backup Archive GUI.
    2. Click "Actions" from the main menu bar in the GUI client and select "Backup Domain".

      Backup Domain

      Note: When you manually back up files, the process begins immediately; you can just minimize TSM and work on something else while they are being backed up.

  • How to tell when/if a file was backed up
    1. Method One: Open Backup Archive GUI and choose Restore from the opening menu. Then find a file that should have been backed up and note the time and date.

    2. Method Two: Look at the file named "dsmsched.log" in the folder "Program Files\Tivoli\TSM\baclient\" on your hard drive. Scroll to the bottom of the file to see the most recent activity. Click to position the cursor near the bottom of the file, then search (Ctrl-F) up the page for the word "completed successfully." A typical daily backup produces a line like this in the log:

      02/07/2002 04:35:57 Scheduled event 'AUDAILY' completed successfully.

      TSM does not leave a window open to let you know when and what was backed up.
  • Restoring files
    1. Locate the Tivoli Storage Manager from your Windows start menu and select Backup Archive GUI.
    2. Click on Restore from the main menu.

      Restoring Files in TSM

    3. The restore window lists the files' size and times and dates created, last modified, and last backed up.

      Restoring Files in TSM

      Click the + box labeled "File Level". Keep expanding the listing as needed by clicking the + boxes on the left until you find the files you need. TSM does not keep multiple versions of a file.

    4. Find and highlight the file(s) you want to restore.
    5. Click the Restore button.
    6. Choose "Following location" and browse to the place you want it restored. Do not check "Original location" even if you want to restore it to the same location.

      Restoring Files in TSM
    7. Click Restore.
  • Deleting files on the server
    1. Know the name of your current computer. To find out, right-click My Computer, click Properties, and click Network Identification. The first part of your full computer name, before the domain name auburn.edu, is used to name the TSM filespace.
    2. Locate the Tivoli Storage Manager from your Windows start menu and select Backup Archive GUI.
    3. From the Utilities menu, choose Delete Filespaces.
    4. Check the + to the left of "Filespace" to expand the listing. You may need to enlarge the window by dragging its bottom edge down.
    5. Find what you want to delete and check the gray box beside it. The box appears yellow with a red check inside. In the example below, two network (H:) drives have been chosen for deletion.

      Delete Files in TSM
    6. Click Delete.

      Delete Files in TSM
    7. Click Yes if you're sure that you want to delete the file(s).
  • Updating TSM
    1. To find out what version of TSM you have, locate the Tivoli Storage Manager on your Windows start menu and select Backup Archive GUI. From the menu bar, select Help > About TSM. You'll see a window similar to this that shows the version, release and level numbers.

      Updating TSM
    2. To download the latest version, visit the AU Download page.

Troubleshooting

  • Session rejected: All server sessions are currently in use
    This error occurs if too many different computers attempt to make TSM backups simultaneously. Try again later. If the Scheduler is running, it will try again in 20 minutes automatically.
  • Error restoring to original location

    If you get an error at the "Select destination for restored object" window after choosing 'Original location', choose instead the "Following location" option.

    This is usually caused by the fact that "original location" doesn't mean just the same directory from which the file was backed up, it also means the same filespace.  Keep in mind that the filespace name changes when you get a new PC.

  • Node name unknown to server
    In TSM, select "Edit > Preferences" and type your AU user name in the "Node Name" field. This is needed when a previously used computer with TSM changes hands.
  • More than one computer
    If you want to use TSM to back up more than one computer, use different TSM IDs (node names).
  • ANS1357S Session rejected: Downlevel client code version

    More than likely what has happened is that a Unicode format filespace has been backed up and the server is rejecting connections for your ID from non-Unicode clients.

    The best solution to this problem is to use a given TSM ID from one machine only. You can request additional TSM IDs for your machines by contacting the OIT Accounts Administrator.

Last Updated: Feb. 9, 2012