What information is needed to size business servers and storage?
Provide application requirements, user concurrency, current utilisation, data growth, performance needs and recovery objectives. Include resilience and maintenance conditions. Sizing from staff numbers or raw storage capacity alone can miss the constraints that determine real performance.
Measure the workload over time
Capture representative busy periods and recurring tasks such as reporting or backups. Include CPU, memory, storage latency and throughput where relevant. A single quiet-day snapshot can underestimate the resources the business needs.
Distinguish capacity from performance
A storage system can have enough space and still respond too slowly. Different workloads produce different access patterns. Ask the supplier to explain the assumptions behind both usable capacity and performance.
Allow for failure and maintenance
Check whether the remaining infrastructure can run the essential workload during a component failure or planned update. Include backup windows and recovery tests in the operating plan. Growth allowances should be tied to a realistic forecast.
Confirm application and support compatibility
Review supported platforms, versions, licences and vendor support boundaries. A technically capable server is not a sound choice if the application vendor will not support the proposed configuration.
A useful proposal includes a sizing rationale, assumptions and acceptance tests. Keep those records for later capacity reviews so future upgrades are based on evidence rather than a fresh guess.
Put this guidance to work.
Explore the relevant emtech service, then discuss the scope that fits your business.