9. General

9.1. Where are the TSM configuration and log files located?

TSM configuration files are found in the following locations:

Table 2. Config File Locations
Platform File Location
Windows dsm.opt C:\Program Files\tivoli\tsm\baclient
Linux, Solaris dsm.sys, dsm.opt /usr or /opt /tivoli/tsm/client/ba/bin
Mac OS X dsm.sys, dsm.opt /Library/Preferences/Tivoli Storage Manager
Netware dsm.opt Installation directory

TSM log files are as follows:

Table 3. Log File Locations
Platform File Location
Windows* dsmerror.log, dsmsched.log C:\Program Files\tivoli\tsm\baclient
Linux, Solaris dsmerror.log, dsmsched.log, tsm-install.log /var/log or /opt/tivoli/tsm/client/ba/bin
Mac OS X dsmerror.log, dsmsched.log, tsm-install.log /Library/Logs/Tivoli/TSM
Netware dsmerror.log, dsmsched.log, tsm-install.log Installation directory
* The Windows installation log files are tsm-install.log and msi.log. To find the directory where these files are located in Windows, do as follows:
  • Windows XP/2003: go [Start] > [Run], and type explorer %temp%.
  • Windows Vista/7/2008: click on the Windows logo in the bottom-left corner of the screen and type explorer %temp% in the search box (overtyping the words Start Search).

Windows users can find the files via Explorer/My Computer. Additionally, there is an automated way of sending us the required files - please see our page on log file collection for Windows.

Mac users can find the files via Finder but may need to run [Go] > [Go to Folder...] and type or paste in the above-mentioned folder name in order to locate the files. Please also note that the configuration files are in /Library/Preferences/Tivoli Storage Manager, not the (always empty) folder /Users/<your-username>/Library/Preferences/Tivoli Storage Manager.

9.2. What is the difference between backup and archive?

Many people mistakenly consider backup and archive to be the same thing and use the terms interchangeably. In fact they are very different.

Backup is intended to provide a mechanism for securing your current, active files: that is files and data that are resident on your local disk and by implication actively in use. It enables you to recover your disk to its most current state in the event that it is lost (for example, hardware failure); it also enables you to recover a file or files that have been lost (for example, accidentally deleted).

Archive is for the long-term storage of data which is considered to be of value to the university. It is held independent of any files' continued existence on your local disk. Archived files may be removed from the local disk on your computer if required (for example, for space reasons).

9.3. Can I back up/restore from home?

Yes. The HFS supports VPN-based backup for systems that are registered for the desktop backup service. This allows the backup and restore of important University data from anywhere in the world using connections via the University's VPN service: please see further our page on VPN-based backups.

9.4. My account was deleted, so I have re-registered but the TSM Client is not working

The reason for this is because the original deleted node was probably registered to a different server than the newly registered node. To resolve follow the instructions on removing and reinstalling the TSM Client.

Further Explanation: In order to spread the load of new registrations, the HFS team change the server on which new TSM nodes are registered. [Odd numbered HFS servers (OX_HFS_B1, OX_HFS_B3, OX_HFS_B5, OX_HFS_B7) are for desktops; even-numbered (OX_HFS_B2, OX_HFS_B4, OX_HFS_B6, OX_HFS_B8, OX_HFS_B10) are for servers.] One user may therefore have accounts spread over several different HFS servers. If a user de-registers an old account from, say, B3, and re-registers, then the new account may come out on, say, B7, if that is where new registrations go. When he/she tries to install, the TSM installer will pick up on all the old settings it finds in dsm.sys/dsm.opt and will try to contact only B3. But, as the user says in their question, we deleted that old B3 account, so the installer finds no account there. So the B7 account will be ignored by the installer and the user can’t run TSM.

9.5. What do I need to do if my machine is being renamed and/or moved?

Your TSM backup is unlikely to be affected if your machine is moved, even if it moves to a different part of the university network. However, if it is renamed and it is also running Windows, then it is likely that it will resend all its data, which may cause your account to be locked. Please see further our page on renaming TSM nodes.

9.6. How secure is TSM?

For a discussion of the various aspects of this subject, please see our page on TSM security.

9.7. What are filespaces?

Filespaces within TSM are typically subsections of nodes that have previously been backed up. For example a node (desktop, laptop or server) may have several physical or logical disks contained with them - these would locally be seen to as c:\, d:\, e:\ etc. As the TSM Backup is required to run with some administrative privileges it backs up the data using Administrative shares that access directly into the root of each drive letter whilst using the UNC for the client, these are generally seen as \\testpc\c$, \\testpc\d$, \\testpc\e$, etc.

For windows clients there for when a filespace is referred to as \\testpc\c$ it is referring to the local C:\ on the machine called TESTPC.

9.8. Which version of TSM am I running?

  • If you are using the Graphical User Interface (GUI) click on Help and choose About TSM. The screen will display the relevant information, such as Version 6, Release 4, Level 0.0. Click the screen to close it and return to the TSM hub window.

    On a Mac, you can alternatively select [Tivoli Storage Manager] > [About Tivoli Storage Manager] from next to the Apple logo (i.e. at the top left corner of the screen). Please note that this does not always give correct results: if you do this after having run TSM Tools for Administrators (which is the recommended method of running TSM on a Mac) then you will be told that you have TSM 1.0; if you do not run TSM via TSM Tools for Administrators, then TSM 6.3 and 6.4 will mis-report that you are running TSM 6.2.

  • If you are using the Command Line Interface (CLI) you should, on starting the client see the Version, Release and Level displayed above the tsm> prompt.

9.9. How can I check that my backup was successful?

There are several ways to check that your backup was successful, whether you only back up manually, only use the automatic schedules, or both. Please see further our page on how to check that backups ran successfully.

9.10. What limits are there on use of the HFS?

In order to provide a reliable service for thousands of users we have to apply some limits on daily usage of the HFS so that a small number of users do not adversely affect the service for everyone else. These include a daily transfer limit (see 9.11. How much data can I back up? ) and the following:
Type Limit
Backup Session Duration 10 Hours
Transfer Speed Average of 10KB/sec over 2 hours
Maximum File Size Same as Daily Limit (below)
If you exceed one of these limits then you will receive a mail headed "HFS backup cancellation report": if this occurs please see our section on HFS backup cancellation reports.

9.11. How much data can I back up?

The HFS limits data uploads by imposing a daily quota. If you exceed this amount then your account will be locked out - this is necessary in order to ensure fair use of the HFS. The limits are as follows:

Desktop/laptop Server Large server
Daily backup quota 150GB 300GB 400GB

The total data backed up by a node in a 24 hour period is not allowed to exceed the daily backup quota. That 24 hour period is linked to the operation of the HFS service but typically starts in the early hours of the morning.

If you exceed the daily transfer limit then you will receive a mail headed "HFS backup cancellation report": if this occurs please see our section on HFS backup cancellation reports.

If you need to send more than the daily limit then you can stage your backups by limiting the amount that you send each day. If you need to do this, please see the FAQ item 9.12. How can I limit the amount of data that I'm backing up?.

Unfortunately we cannot accept more than the daily limit for each account. This is because of the way in which newly-received data is processed: it would delay our daily processes the next day if we were to receive an excessively large amount for a single account.

In addition to the daily limit, there is a limit on the size of a single account, which should not exceed 10TB.

9.12. How can I limit the amount of data that I'm backing up?

You can limit your manual backups by stopping the upload before it reaches the daily limit. This cannot be done on the command line, but only in the Graphical User Interface.
  • Start a manual backup, using the appropriate instructions from our section on Using TSM Backup & Restore on your client platform.
  • In the Task List window, click on Report; this opens a Backup Report window that shows the running total (listed as Bytes Transferred).
  • When the total is approaching the limit, close the Backup Report window and click on Stop in the Task List window.

9.13. What does and doesn't get backed up to the HFS?

TSM will inspect your local hard drive(s) and any locally-attached external drives and by default will back up all the files that it finds there. However, for a variety of reasons, some files are excluded from backup. A list of excluded files can be found on the HFS Policy Pages.

9.14. How many copies of my files are kept, and how long for?

The HFS keeps up to two copies of any one file that is backed up. For information on how long files are held for, please see section 9.18. How long do you keep data for?.

9.15. What does "always incremental" mean?

The backup service provided by IT Services creates a copy of your active files. This is achieved through incremental backups.

Incremental backups mean that we only take copies of the data that has changed since the last time a backup was taken, and we then add this to the existing data that has been backed up.

New Files
New files are backed up during the incremental backup and added to the backup set.
Changed Files
If a file that has been backed up once is then modified, then the original file is retained in the backup but marked as inactive, and the modified version is backed up and marked as active; only the currently version and the previous version are retained in the backup.
Deleted Files
If a file that has been backed up once is then deleted from your file system, then the file is flagged as inactive during the backup process. This file will still be held in the backup dataset for 90 days, at which point it will be removed and no longer be available to restore.

9.16. What should I do if I can't back up for several weeks/months?

If you do not back up for four weeks then you will receive a warning mail headed 'Old data on the HFS'. Another will be sent after ten weeks of inactivity, warning you that your data will be deleted in four weeks' time. After that point, if we have received no response, then the filespaces/accounts listed in the second e-mail will be deleted. More information about these mails is to be found in our pages on Standard TSM emails: old data on the HFS and deletion policy.

Perhaps, however, you are unable to run a backup because e.g. you are out of Oxford or away on leave. If that is the case and you cannot run a backup for more than two months, please contact help@oucs.ox.ac.uk and let us know the reason, and also the date when you will be able to back up again. We will then put your data on hold until that date.

9.17. When is the HFS available?

Generally, the HFS service is available 24/7. However, as with all systems there is from time to time a requirement to update the software and device firmware that underpins the service. Where this requires limiting access to some or all elements of the HFS Service, such interruptions will be advertised to the itss-announce maillist and on the IT Services Status Page, where real-time availability of all IT services can be checked.

9.18. How long do you keep data for?

The answer to this question falls into two parts. Data that has been backed up to the HFS is, if it still exists on the local disk, retained as long as the drive/partition that sent it continues to back up to the HFS. Data from drives that have ceased backing up for 90 days is subject to deletion, in accordance with our deletion policy; up to three warning e-mails are sent before such deletion occurs.

Secondly, data is also subject to our data retention policy. The HFS backup service is intended to secure your current work and consequently, a maximum of two versions of any particular file on your local system are kept: the current version (known as active) and the penultimate version (known as inactive, and backed up before the current version was created). If a third (or subsequent) copy is made of the file, at the next backup the oldest copy held is deleted, the current one held becomes the oldest, and the very latest becomes the current copy. In cases where a file has been deleted from the local disk, the following maximum retention policy applies:
Desktop/laptop backup policy
  • Maximum number of versions of any one file kept = 2
  • Maximum retention of the second (oldest) version of a file = 28 days
  • Maximum retention of the most recent version of a file = 90 days
Server backup policy
  • Maximum number of versions of any one file kept = 2
  • Maximum retention of the second (old) version of a file = 90 days
  • Maximum retention of the most recent version of a file = 90 days

9.19. How do I back up my Nexus e-mail?

All data covered by the Nexus groupware solution - including e-mail, calendars and SharePoint data - is backed up automatically to the HFS, directly from the Nexus servers. There is therefore no need for Nexus users to back up such data using TSM.

For details on the backup and restore of data held on Nexus, see the Nexus (Exchange) service level description.

Up: Contents Previous: 8. Deregistering