Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/IT Desktop Management Overview and System Design Guide


4.6.5 Analysis of site server requirements

Installing site servers in a JP1/IT Desktop Management system can reduce the disk usage on a management server and the load on the network. Before you install site servers, analyze the number of site servers, purpose of use, and grouping.

Conditions that require site servers

Whether a site server is necessary depends on the number of managed devices, whether operations logs are acquired, and whether you are using the distribution function. The following table describes, for each set of conditions, whether you need to deploy a site server.

Number of managed devices

Operation logs

Distribution function

Site server required

1 to 3,000

Acquired

Enabled

N

Not acquired

Disabled

Not acquired

Enabled

Acquired

Disabled

3,001 to 5,000

Acquired#

Enabled

Y

Not acquired

Disabled

N

Not acquired

Enabled

N

Acquired#

Disabled

Y

5,001 to 50,000

Acquired#

Enabled

Y

Not acquired

Disabled

N

Not acquired

Enabled

Y

Acquired#

Disabled

Y

Legend: Y: A site server must be deployed. N: A site server is not needed.

#: Operation logs stored on a site server and those stored on the management server cannot be viewed concurrently. Therefore, when you use site servers, we recommend that operation logs be stored on the site servers only, not on the management server.

Note that we recommend the use of site servers in environments where the available network bandwidth between the management server and computers with agents installed is small.

Deciding the number of site servers

There are no restrictions on the number of site servers that can be deployed in a system.

Decide the number of site servers based on the following guidelines.

If a site server is deployed within the network search range (that is, one of the IP address ranges specified in the IP Address Range view displayed by clicking Discovery and then Configurations in the Settings module), the search is conducted from the site server. This allows you to search for devices that cannot be directly accessed from the management server. To make every device in the organization discoverable, deploy a site server within each search range.

Tip

To implement an environment in which load distribution is always possible, at least one site server registered in a site server group must be running. When you set up a site server that runs 24 hours a day, select a computer that monitors the network connections of devices (24-hour computer is recommended) as the site server. This reduces the number of always-running computers.

Considering the purpose of site servers

Site servers have two roles. They are used to store operation logs or as distribution relay sites. You can specify site server groups with either role assigned for each network segment. The same site server group can also be used more than once.

Because operation logs are acquired every day, a huge amount of data is accumulated. Therefore, we recommend that you select computers with sufficient hard disk size as site servers in which operation logs are stored.

Analyzing site server groups

To determine the site server group to which computers connect, select a site server group for each network segment. Computers will then be connected to the site servers according to the priority set for the site server group.

When you use site servers to store operation logs, we recommend that you use only one site server in the site server group specified for each network segment. This causes operation logs for each computer to be collected on one site server, thus facilitating management of operation logs.

When you use site servers as relay sites for distribution, we recommend that you use multiple site servers in a site server group. By doing so, if an error occurs in one site server, another site server can be connected, thus implementing a robust system. In this case, you can assign the connection priority for each site server in the site server group, or set a random priority. Analyze the configuration of the site server groups based on the consideration of how to balance the load.

Important note

Ensure that at least one site server is running in a site server group. If no site servers are running, load balancing in the system will no longer be possible.

Related Topics: