Home > Tsm Error > Tsm Error Messages Guide

Tsm Error Messages Guide

ANS4047E There is a read error on '/var/log/test.log'. However, you can specify preschedulecmd or postschedulecmd with a blank or a null string to disable the scheduling of these commands. Summary You should now have performed enough troubleshooting to ensure that you know why the scheduled backup failed and hopefully put corrective measures in place to ensure subsequent scheduled backups are Informational (ANS####I) messages will not indicate the cause of a scheduled backup failing or being severed; rather, usually the problem is indicated by an error (ANS####E) message. check over here

In the search box type ANS, then select up and click Find Next. Once the log is open (this may take a while if it is large), scroll to the bottom of the log file: this is where the most recent information will be. Ensure the DEFINE DRIVE and DEFINE DEVCLASS have been issued properly. 208 X'D0' Command aborted Contact Tivoli Storage Manager support. 209 X'D1' Device microcode failure detected Check the microcode level of Return codes from the command line interface The backup-archive command line interface and the scheduler exit with return codes that accurately reflect the success or failure of the client operation. http://www.ibm.com/support/knowledgecenter/SSSQZW_6.3.0/com.ibm.itsm.srv.common.doc/r_srv_msgcodes.html

To specify a user's particular domain, click the dropdown list next to the domain name. Folder/File structures that create memory issues on the client machine, causing backup to fail. Not all file failures cause schedule failures but Windows in particular does sometimes lock open files in such a way that it causes TSM to call a schedule failed when really When it has been unlocked we suggest running a manual backup so that you can: Test that the issue has been resolved; Ensure that we have an up-to-date copy of your

See Windows Event Log Entries. If you have nodes registered to you that you know do not represent existing machines, please follow the instructions for de-registering the node. Click OK. In order to provide effective support for this issue the HFS Team need all of the following files (for the appropriate operating system) attached to the email from the client machine

To find out when your next scheduled backup is, please see the FAQ item When is my scheduled backup due to run?. 2. Examining dsmsched.log using a spreadsheet If you find your log difficult to read then try using a spreadsheet package such as Microsoft Excel or Open Office Calc. There were no other errors or warnings. https://help.it.ox.ac.uk/hfs/help/scheduledts1 Any file system errors that are easily fixable will then be fixed on the next reboot.

To prevent this, you need to set power management correctly, as follows: In Windows: In XP/2003, go to Start > (Settings >) Control Panel > Power Options > Power Schemes (tab), The file is skipped.' If TSM is having trouble reading certain files, then it could be because they are corrupted. The most common reasons are: The file is in an exclude list. TSM effectively classes System State as a separate drive, meaning that you can exclude it from the backup domain by using our instructions on how to exclude files, folders and drives

  1. The drive or library reference manual provided with the device usually contain tables explaining the values of the KEY, ASC, and ASCQ fields.
  2. Additionally, the scheduled backup will complete with a return code of 12 and be listed as a 'FAILED' backup.
  3. Searching tip Excel users - In the search window you can enter ANS????E to search for Errors or ANS????W to search for warnings.
  4. In these entries, byte 3E is the sense key, byte 3D is the ASC, and byte 3C is the ASCQ. (This is also true of entries logged by any of the
  5. crashing) of the client machine.
  6. On AIX, display the errpt to check for hardware errors. 307 X'133' Entry/exit failure Contact Tivoli Storage Manager support. 308 X'134' Entry/exit port not present Contact Tivoli Storage Manager support. 309

Return codes and meanings Code Explanation 0 All operations completed successfully. 4 The operation completed successfully, but some files were not processed. See Completion Code and Operation Code Values for a list of completion codes. See "Specifying scheduling options" for more information. Retry the failing operation. 211 X'D3' The SCSI bus was busy.

After performing the recommended action, retry the failing operation. You must have a physical or VPN network connection to the Oxford University network for the scheduled backups to run. Once sent your email will be automatically passed to the HFS Team who will review and advise you of any further action required. For example, you can automatically back up files at the end of each day or archive some of your files every Friday.

Some possible values displayed are: READ WRITE FSR (forward space record) FSF (forward space file) WEOF (write end of file mark) A string of hex digits See Operation Code Values for If you have been unable to determine the likely cause of why the backups are failing then please follow the steps below for logging calls with the HFS Team with the For more information about scheduling options, changing the scheduling mode, specifying the TCP/IP address or port number, or running commands before or after a schedule, see "Scheduling options". The next incremental backup will start in 30 minutes.

If your account was neither locked nor had an expired password then please proceed to the following section. 1.3. Firewall intervention prohibiting/delaying network traffic. You will need to open the file dsmsched.log, whose location on your machine is listed in table 1.

After performing the recommended action, retry the failing operation.

Was your machine left connected to the Oxford University network? Clean the drive heads with a cleaning cartridge that is not too old. 409 X'199' Media fault Clean the heads and ensure the media is not physically damaged or too old. X'6D37' MTIOCLQ Return information about the tape library and its contents. The Services window is displayed.

Ensure the SCSI ids are correctly assigned to the correct device, and the device is not being accessed by another process. You are advised to run a a manual backup to ensure your data is backed up. As a general rule, this return code means that the error was severe enough to prevent the successful completion of the operation. Ensure the volumes have not been rearranged.

Summary You should now have performed enough troubleshooting to ensure that you know why the scheduled backup was missed and hopefully put corrective measures in place to ensure subsequent scheduled backups Please try the request again. In Linux or Solaris, use the command fsck to check your disk - please refer to your system documentation for the appropriate procedure. NO - Are you registered for the Wake on LAN service?

Basic steps are as follows, though you may want to do further research before implementing them. For example: 20-11-2013 20:28:42 ANS5250E An unexpected error was encountered. Users who already have scripts, batch files, or other scheduling or automation facilities that interpret the return code from the command line interface may need to make changes in order to Sample query schedule output Schedule Name: DAILY_INC Description: Daily System-wide backup Action: Incremental Options: QUIET Objects: Priority: 1 Next Execution: 30 minutes Duration: 4 Hours Period: 1 Day Day of Week:

The file is skipped.If the fault is only software-related, then the problem can be fixed by checking the disk. What people are saying-Write a reviewWe haven't found any reviews in the usual places.Bibliographic informationTitleTivoli Storage Manager for Virtual Environments - Data Protection for VMware Deployment GuideAuthorsJulien Sauvanet, Mikael Lindstrom, IBM