3. SEVERED

You have a node whose scheduled backup is reported to have been SEVERED.

A SEVERED backup generally means a loss of communication between the TSM client on your machine and the HFS TSM server, whilst the backup was in progress. Possible reasons include:

  • Intervention at the client (user) end - the user forcibly cancelled the backup/stopped TSM services, or switched the machine off during the backup.
  • Intervention at the server end - the backup may have been cut off from the HFS server for exceeding a daily limit.
  • Failure (e.g. crashing) of the client machine.
  • TSM client machine going into sleep mode/state of hibernation.
  • Several large files causing multiple connection timeouts between the server and client.
  • Dropped network connection either at the client end, or somewhere on the network between the client and the server.
  • Firewall intervention prohibiting/delaying network traffic.

If you are aware of your machine crashing or the backup being forcibly cancelled then you may wish to simply run a manual backup.

To troubleshoot why your backup was SEVERED please follow the above troubleshooting steps provided for FAILED backups.

Up: Contents Previous: 2. FAILED Next: 4. Logging calls with the HFS Team