Calculate the capacity you can actually use.
Start with current live data, growth, retention and the number of copies required. Include logs, indexes, temporary processing space and operational headroom. If the service uses redundancy or reserved capacity, ask the proposal to distinguish raw disk capacity from usable capacity.
Explain whether files are mainly small and numerous or large and sequential. A design for media archives may differ from a database or a repository receiving many concurrent backup streams. Capacity forecasts should include the point at which more disks or another storage tier would be required.
Match the interface to the application.
Describe the access protocol, client locations and concurrent users or jobs. Establish the required throughput, latency and expected transfer window. Network capacity, disk layout and controller behaviour should be considered as one path between the application and its data.
If the server will provide a file service, define ownership, permissions and authentication. For a repository, check compatibility with the backup software and its supported storage layouts. Confirm how performance will be assessed using representative file sizes and operations.
Build a deliberate retention policy.
A backup repository needs a clear policy for retention, deletion and administrator access. Identify who can change the policy or remove stored copies. Where protection against deletion is required, state the required control and request confirmation of its implementation and operational limits.
Separate production access from repository administration where the design allows it. Include encryption and key ownership in the discussion. Retention should reflect the business need and applicable data-handling rules, with a process for reviewing growth and removing data when appropriate.
Plan the time needed to restore service.
Consider disk failures, a host incident, an accidental deletion and loss of the location as different scenarios. Local redundancy can support continued operation through some failures; an independent recovery copy addresses a different problem. Define which scenarios the proposed service must cover.
Test the restore path and measure how long useful data takes to become available. Include replacement capacity, network transfer and application validation in that estimate. The quotation should cover hardware, management, licences, connectivity and any additional recovery storage separately.
