Resolving server problems

Recreating the problem
Recreate the problem to isolate its cause to a specific sequence of events, if the problem can be easily or consistently recreated.

Checking the server activity log file
Check the server activity log file and look at the reports occurring 30 minutes before and 30 minutes after the time of the error.

Checking system error log files for device errors
If the problem is an error created by reading or writing data from a device, many systems and devices record information in a system error log.

Reverting server options or settings
If there were configuration changes to the server, try reverting the settings back to their original values and retry the failing operation.

Restarting the scheduling service
Scheduled client operations are influenced by the schedule definitions on the server as well as the scheduling service (dsmsched) that runs on the client computer itself.

Resolving server space issues
The IBM Tivoli Storage Manager server's primary function is to store data. If it runs out of space in the database or storage pools, operations might fail.

Allocating additional server memory
Allocate more memory on the server if there are indications that your server is low on memory resources. Refer to your operating system’s documentation for information about adding memory.

Configuring a server instance to use shared memory
Configure a server instance to use shared memory to help resolve slow database backups that can occur because of Transmission Control Protocol (TCP) loopback problems.

Changing the copy frequency
IBM Tivoli Storage Manager server policy demands that an incremental copy frequency be a non-zero value.

Resolving RELABEL operation errors
If you run a RELABEL operation when all drives are busy, the target volume cannot be relabeled because it cannot obtain a drive. Busy drives are drives that are in use for regular operations such as backup, restore, migration, and reclamation.

Avoiding communication errors during import processing
Communication errors are displayed in the activity log of the target server if you cancel the import process from the target server.

Resolving installation and upgrade problems
Resolving installation problems with IBM Tivoli Storage Manager server can involve reviewing log files, reinstalling the server, or several other possible options.

Resolving server stoppages
Server stoppages can occur from processing errors, the system trap handler, or other errors. When you determine the source of your server stoppage, the reason might resolve other known issues.

Resolving database errors
Database errors might be caused by issues such running out of space and by errors that are caused by insert, update, or delete operations.

Analyzing the process symptoms to resolve problems
You can sometimes determine the cause of errors by observing the process symptoms.

Resolving storage pool issues
Storage pools are integral to a successful server operation. The IBM Tivoli Storage Manager database contains information in storage pools about registered client nodes, policies, schedules, and the client data.