HP BladeSystem bc2000 - Blade PC Administrator's Manual page 23

To optimize the HP SAM database performance, a database administrator should do two things:
●
Develop a SQL maintenance plan. This includes backing up HP SAM database and truncating
orphaned transaction logs in the LDF file. When backing up, the orphaned transactions are
truncated, but the size of the LDF file is not reduced. The database administrator can shrink the
LDF file as far as the 100MB default, if desired.
●
If the history and audit logs are not disabled, the database administrator will need to truncate these
two tables periodically. It is recommended that this be done on a weekly basis to keep
SAM_data.mdf under 1GB.
Number of HP SAM Servers
It is recommended that, as user populations grow, the number of HP SAM Servers (gateways) be
increased to handle loading and provide backup gateways when another server is inaccessible for
whatever reason.
If you want to avoid continuing to increase memory and processor cores on the HP SAM Server, create
multiple gateway servers and split user populations to limit the number of users using a particular
gateway as their primary target. You may also split resources between HP SAM servers to distribute
the load between servers.
Regionalization of Data Centers
When placing users in one region and blades in another:
● As population size increases, the HP SAM Server should be local to the blades/resources as
opposed to local to the users for the following reasons:
◦
Because the database of users has to be pulled across the network to HP SAM Server
memory, the WAN could impact performance if this database becomes too large.
◦ If the two servers (SQL and HP SAM) are in the same data center, their communication can
occur over the high speed backbone with little to no performance impact from the network.
●
With relatively small population sizes (fewer than 3,000), you may place the HP SAM Server local
to the users as opposed to local to the blades/resources for the following reasons:
◦ The database of users being pulled across the network to HP SAM Server is small and
impacted very little by the WAN.
◦
The local HP SAM Server limits the number of users hitting that server, so the server can be
smaller.
Disaster Recovery designs
●
Multiple HP SAM servers can be configured so that users and resources will failover to another HP
SAM server if a server becomes unreachable. It is recommended that the HP SAM servers be
installed in different locations for a greater likelihood that at least one server will remain accessible.
ENWW HP SAM Hardware and Software Requirements 15