HP Device Manager 4.6 - Deployment Guide

20,000 GB ÷ (100 Mbps ÷ 8 bits per byte ÷ 1000 x 3600 seconds per hour) ≈ 444.4 hours
To reduce the data transfer time to 48 hours, you need 10 repositories (444.4 ÷ 48). Keep in mind that there is some
overhead to synchronize from the Master Repository to the Child Repositories.
Simultaneously connected users
There is no significant increase of memory or CPU usage on the HPDM Server for any additional, connected HPDM Consoles.
However, it requires more resources for database access and communication. Do not have too many connected HPDM
Consoles.
Scenarios
The followingollowing are some typical scenarios.
Table 3. Minimun requirements for typical senarios
Devices HPDM Servers
HPDM
Gateways
Databa
se
1–5,000 1 1
PostgreSQL
5,000–20,000 1 1
PostgresQL or MS SQL Server
20,000–50,000 1 ≥1
MS SQL Server
> 50,000 ≥ (device number/50,000) ≥3
MS SQL Server
Note
This table introduces the minimum requriements of some typical scenarios, but you must deploy your enviorment according
to your network situation and company strategies, such as whether devices are in a NAT environment or distributed in
different places.
Small scale deployment
Device number: <5000
Deployment: 1 HPDM Server, 1 HPDM Gateway, PostgreSQL (or MS SQL Server), 1 Master Repository
Figure 3. Small scale topography
HPDM Server
(
PostgreSQL/MS SQL Server)
HPDM Gateway
HPDM Master Repository
HPDM Console 1
Thin
Client
Thin
Client
Thin
Client
HPDM Console 2
This is a small scale deployment, so the minimum requirement is that you can deploy all HPDM components on one
machine.
7