#TSM 4 ISSUES FOR MAC OS#
#TSM 4 ISSUES MANUAL#
#TSM 4 ISSUES PASSWORD#

You must have a physical or VPN network connection to the Oxford University network for the scheduled backups to run.

If not, go to System Preferences > Energy Saver and check that the computer (not the display) is set never to go to sleep.

#TSM 4 ISSUES FOR MAC OS#

If you are running OS X 10.7 (Lion) or higher, download the latest client for Mac OS X.

If your machine is a laptop and close its lid when you leave it on for backup, also check that When I close the lid is set to Do nothing.

Check Start > Control Panel > Power Options > Choose what the power button does > When I press the power button is not set to Sleep.

Check Start > Control Panel > Power Options > Change when the computer sleeps > Put the computer to sleep is set to Never.

Your machine may still have switched itself off or gone into sleep mode, meaning that the scheduled backup was missed.

If your machine was switched on overnight:

If the machine was off when the schedule was due to run then the schedule will have been missed.

You need to leave your machine on overnight to run a scheduled backup.

If your machine was NOT switched on overnight:

Click on Change node password in the left hand menu.

#TSM 4 ISSUES PASSWORD#

If the Details tab shows your node's Password set date to be over a year old, your password may have expired and need to be changed.

If the Summary tab shows your node's Locked status as Yes, contact request it is unlocked, you can also do this by clicking on Request unlock in the left hand side menu.

To check your node's status do as follows: If your TSM node is locked then you will not be able to back up to the HFS until it is unlocked. Is your TSM node locked or has the password changed? If you have nodes registered to you that you know do not represent existing machines, please deregister the node. It could be that one is active and being backed up, whilst the other does not exist and is therefore being reported as missed.

Check the HFS Portal to ensure that you do not have two or more similarly named registered nodes.

If the node has been replaced, rebuilt or is no longer used then please deregister the node so that it is no longer on the backup schedule.

The first thing to check is whether the machine that used this nodename has been replaced, rebuilt, or is no longer used. To troubleshoot why your scheduled backup was missed, please proceed through the following steps in order: Is the node in question still active? If you already know why this scheduled backup was missed and then you may just wish to run a manual backup. You have a node whose scheduled backup is reported to have been MISSED. OUCS0111-TEST02-OUCS FAILED 07-04-2010 22:30:00 WEEKLY_22įor each node, check which status has been given and chose from: Nodename Status Schedule Date Time Schedule Name The email will state for each node whether the scheduled backup was Missed, Failed or Severed:įollowing is a list of machines which missed or failed their scheduled backups Since each node has its own unique account name, password and installation of TSM, you will need to repeat this process for each of the nodes listed in the email.

Within the email there will be one or more Nodenames listed.

#TSM 4 ISSUES MANUAL#

Therefore it is important both to resolve this issue as soon as possible to enable future scheduled backups to run and also to perform a manual backup to ensure that your current data is backed up and secure. If you have received this message then some or all of your data will NOT have been backed up. This article aims to assist you if you have received an e-mail advising of a Missed, Failed or Severed backup, such an email will have the subject heading TSM Scheduled backup failure report.

Tsm 4 issues