Task | Required Privilege Class |
---|---|
Start, halt, and restart the server | System or operator |
The following events occur when the TSM server is started:
Note: | By default, TCP/IP and Named Pipes communication methods are enabled in the server options file. To adjust the TSM communication method value or to disable a communication method, choose the server options file editor panel in the TSM Server Utilities. |
You can start the TSM server as one of the following:
OR
Windows requires that all applications be closed before you log off. As a production server, TSM must be available to clients 24 hours a day. At many sites, it is a security exposure to leave an administrator ID logged on at an unattended computer. The solution is to run the TSM server as a Windows service.
You can start the TSM server as a console application during configuration, or when you use it in a test environment. When you start the TSM server as a console application, TSM provides a special administrator user ID named SERVER_CONSOLE. All TSM server messages are displayed directly on the screen. The console can be useful when debugging start-up problems.
When TSM is installed, a database and recovery log is created. Only one server at a time can access a particular database and recovery log. If you have installed a single TSM server on a computer and start it as a console application, you cannot start the server as a service until you have first stopped the console application. Similarly, if you start the server as a Windows service, you must stop the server before you can successfully start it as a console application.
If you have more than one TSM server installed and configured on a computer, you can run multiple servers because each server has its own database and recovery log. However, multiple servers cannot use the same device because possible data loss may occur.
Because the TSM server can issue a number of requests that require action, it is important to monitor server activity with the administrative client using either the console monitor or mount monitor modes. You can easily select one of these administrative client modes from the TSM Server Utilities' toolbar and launch menu.
To start the TSM server as a Windows service, do the following:
At this time you can also set up the TSM server to start automatically at system boot time and log TSM server console output to a file. Logging the server console output to a file is useful for reviewing messages that are normally displayed at the server console. You can refer to the messages in this file if you encounter any problems with running TSM as a service.
Perform the following steps from within the TSM Server Service window:
The default name for the output file is console.log.
To view start and stop completion messages that are logged in the Windows Application log, you can use the Windows Event Viewer in Administrative Tools.
If you plan to use the ADSMSCSI device driver, you may also need to start the driver at this time. For more information, see Starting and Stopping the Tivoli Storage Manager Device Driver (ADSMSCSI).
To start the server console from the command line prompt, change to the directory where the server is installed. For example, c:\program files\tivoli\tsm\server
Enter:
dsmserv
TSM displays the following information when the server is started:
If TSM detects an invalid system date and time, the server is disabled and expiration, migration, reclamation, and volume history deletion operations are not allowed. An error message (ANR0110E) is displayed and you may either change the system date if it is in error, or issue the ACCEPT DATE command to force the server to accept the current system date as valid. After the system date is resolved, you must issue the ENABLE SESSIONS command to re-enable the server for client sessions.
The date and time check occur when the server is started and once each hour thereafter. An invalid date is one that is:
System administrators must allow TSM to update the Active Directory schema before TSM can store information in and retrieve information from Active Directory. The Active Directory schema, stored on the Windows 2000 domain controller, is a list of definitions that identifies objects and information about those objects. This one-time configuration allows TSM to extend the schema by adding objects to the schema that define TSM servers. For more information about the Active Directory schema, search for active directory schema in the Windows 2000 online help.
To update the schema, you must use the Active Directory Schema snap-in. This snap-in is part of Windows 2000 Administration Tools, which is included on the Windows 2000 Server and Advanced Server compact disc sets. These tools enable administrators to manage the Active Directory schema on a Windows 2000 domain controller.
The Windows 2000 Administration Tools are available on the Windows Server compact disc (CD).
After you have installed the Windows 2000 Administration Tools, you can configure permissions. From the domain controller that contains the Active Directory schema, do the following:
Complete the following steps on the TSM server:
If you want to disable the permissions to extend the schema, do the following:
If you want to disable further schema updates, do the following:
To have the TSM server define itself to the Active Directory, do the following:
Note: | If you do not see any entries, you must first initialize the server. You can use the TSM Server Initialization Wizard in the TSM Server Utilities. |
The next time the TSM server starts, it will define itself to Active Directory and add information that includes the list of registered nodes and communication protocol information. You can verify this information at any time by using the Active Directory Configuration wizard in the Server Utilities.
TSM backup-archive clients in the domain can select a TSM server by clicking the browse button on the protocol page of the Backup-Archive Client Setup Wizard. The wizard lists the TSM servers, that the node is already registered with, that support the selected protocol. When the client selects a server and the wizard selections are complete, the wizard includes the corresponding communication protocol information in the client options file.
You can halt the server without warning if an unplanned operating system problem requires the server to be stopped.
When you halt the server, all processes are abruptly stopped and client sessions are canceled, even if they are not completed. Any in-progress transactions are rolled back when the server is restarted. When the server is halted, 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:
To stop the TSM Server from the Utilities, complete the following steps:
To stop the TSM Server from the administrative client graphical user interface, complete the following steps:
Note: | The QUIESCE option on the HALT command is recommended only if you plan to do a database dump by using the DSMSERV DUMPDB command immediately after halting. Because TSM supports online database backup (BACKUP DB command), the DSMSERV DUMPDB command should be rarely, if ever, needed. |
To start the server after it has been halted, follow the instructions in Starting the Server.
When you restart the server after it has been halted, TSM rolls back any operations that had been in process to ensure that the database remains in a consistent state.