IBM Tivoli Storage Manager, Version 7.1

Setting up a managed server

Setting up the managed server can be done by an administrator working at a central location, or by administrators working at the servers that will be managed servers.

About this task

Figure 1 shows the specific commands needed to set up one Tivoli® Storage Manager server as a managed server. The following procedure gives you an overview of the steps required to set up a server as a managed server.

Figure 1. Setting up a managed server
Commands required for a managed server MUNICH: QUERY PROFILE, DEFINE SUBSCRIPTION, and SET CONFIGREFRESH.

A server becomes a managed server when that server first subscribes to a profile on a configuration manager.

Procedure

  1. Query the server to look for potential conflicts.

    Look for definitions of objects on the managed server that have the same name as those defined on the configuration manager. With some exceptions, these objects will be overwritten when the managed server first subscribes to the profile on the configuration manager.

    If the managed server is a new server and you have not defined anything, the only objects you will find are the defaults (for example, the STANDARD policy domain).

  2. Subscribe to one or more profiles.

    A managed server can only subscribe to profiles on one configuration manager.

    If you receive error messages during the configuration refresh, such as a local object that could not be replaced, resolve the conflict and refresh the configuration again. You can either wait for the automatic refresh period to be reached, or kick off a refresh by issuing the SET CONFIGREFRESH command, setting or resetting the interval.

  3. If the profile included policy domain information, activate a policy set in the policy domain, add or move clients to the domain, and associate any required schedules with the clients.

    You may receive warning messages about storage pools that do not exist, but that are needed for the active policy set. Define any storage pools needed by the active policy set, or rename existing storage pools.

  4. If the profile included administrative schedules, make the schedules active.

    Administrative schedules are not active when they are distributed by a configuration manager. The schedules do not run on the managed server until you make them active on the managed server. See Tailoring schedules.

  5. Set how often the managed server contacts the configuration manager to update the configuration information associated with the profiles.

    The initial setting for refreshing the configuration information is 60 minutes.

    For more information, see the following topics:



Feedback