HP Session Allocation Manager (HP SAM) v.3.1 Administrator's Guide

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.
Multiple SQL Databases
Typically, one SQL database should be shared between all HP SAM servers. Only in some situations
does it make sense to use more than one distinct SQL database:
●
When customers can keep user and resource populations in entirely separate support arenas
and users do not need to migrate between them.
●
When user populations go beyond 40,000.
●
When large user populations log on and off extremely frequently, because this will impact
performance for everyone on that SQL database.
Otherwise, you should only have a single SQL database
Domain Environment Requirements for HP SAM
●
HP SAM is supported in domains whose domain controllers are running Windows 2003 Server
or later.
●
HP SAM is supported in domains with Domain Functional Level of Windows 2003, Windows
2008, or Windows 2008 R2 Server.
NOTE: If the domain is using Windows 2008 domain functional level, you must install Service
Pack 1 for Microsoft .NET Framework on the HP SAM server.
ENWW
HP SAM Hardware and Software Requirements
13