You can halt the TSM server without warning if an unplanned operating system problem requires the server to be stopped. Always make sure that you have latest successfull DB backup available before trying to stop the TSM services.
In order for the administrative client to recognize an alias for the HALT command, the client must be started with the CHECKALIASHALT option specified.
Precautions to be taken before halting TSM Server
When you halt the server, all processes are abruptly stopped and client sessions are canceled, even if they are not complete. Any in-progress transactions are rolled back when the server is restarted. Administrator activity is not possible.
If possible, halt the server only after current administrative
and client node sessions have completed or canceled. To shut down
the server without severely impacting administrative and client node
activity with the server, you must follow the below precautions
- Disable the server to prevent new client node sessions from starting by issuing the DISABLE SESSIONS command. This command does not cancel sessions currently in progress or system processes like migration and reclamation.
- Notify any existing administrative and client node sessions that you plan to shut down the server. The server does not provide a network notification facility; you must use external means to notify users.
- Cancel any existing administrative or client node sessions by issuing the CANCEL SESSION command and the associated session number. To obtain session numbers and determine if any sessions are running, use the QUERY SESSION command. If a session if running, a table will appear showing the session number on the far left side of the screen.
- Find out if any other processes are running, such as server migration or inventory expiration, by using the QUERY PROCESS command. If a database backup process is running, allow it to complete before halting the server. If other types of processes are running, cancel them by using the CANCEL PROCESS command.
- If the process you want to cancel is currently waiting for a tape volume to be mounted (for example, a process initiated by EXPORT, IMPORT, or MOVE DATA commands), the mount request is automatically cancelled. If a volume associated with the process is currently being mounted by an automated library, the cancel may not take effect until the mount is complete.
- Then you can Halt the server to shut down all server operations by using the HALT command.
To stop the IBM Tivoli Storage Manager server
from the IBM Tivoli Storage Manager Console,
complete the following steps:
- Double-click the IBM Tivoli Storage Manager Console icon on the desktop.
- Expand the tree until the Tivoli Storage Manager server you want to work with is displayed.
- Expand Reports.
- Click on Service Information.
- Select the server, and click on Stop.
The HALT command can be replicated using the ALIASHALT server
option. The server option allows you to define a term other than HALT
that will perform the same function. The HALT command will still function,
however the server option provides an additional method for issuing
the HALT command.
Also Read: Steps to do after successful TSM DB restore
Also Read: Steps to do after successful TSM DB restore
In order for the administrative client to recognize an alias for the HALT command, the client must be started with the CHECKALIASHALT option specified.
Stopping the server when running as a background process
If you started the server as a background process and want to stop the server, connect to the server as an administrative client and issue the HALT command. If you cannot connect to the server with an administrative client and you want to stop the server, cancel the process by using these steps:Moving the Tivoli Storage Manager server to another system
You can move your Tivoli Storage Manager server from one computer to another.These are the prerequisites to back up the database from one server and restore it to another server:- The same operating system must be running on both servers.
- The sequential storage pool that you use to back up the server database must be accessible from both servers. Only manual and SCSI library types are supported for the restore operation.
- The restore operation must be done by a Tivoli Storage Manager server at a code level that is the same a that on the server that was backed up.
To move the database to another system perform the following
steps:
- Install Tivoli Storage Manager on the target server. Ensure that you install the instance as if you were creating a new server.
- Back up the database to sequential media. For example, issue the following command:
- The sequential storage pool that you use to back up the server database must be accessible from both servers.
- Halt the server.
- Move any libraries and devices from the original server to the new server, or ensure that they are accessible through a storage area network.
- Move copies of the volume history file, device configuration file, and server options file to the target server.
- Restore the backed up database on the target server. Ensure that you issue the following commands as the instance user. For example:
dsmserv restore db
To change the current directory structure on the target server, create a file (for example dbdir.txt), list the directories that are to be restored on separate lines, and issue this command
dsmserv restore db on=dbdir.txt
- Start the target server.
If dsmserv.dsk file is deleted from TSM sever. what troubleshooting steps need to follow. how to recover the file dsmserv.dsk
ReplyDelete