BEFORE YOU BEGIN
Check before you begin
Capacity, performance and scale limits depend on data type, method and release. No deduplication/compression ratio, linear speed increase or automatic clustering is guaranteed. Contact destek@menabyte.com.tr for technical sizing.
Visual note: no suitable real capacity/scale screenshot without customer capacity or internal topology is available. An unrelated screen was not used as capacity evidence. This work changed no storage, nodes, workers, policies or data.
- Product release, method and workload scope
- Source volume, change and growth measurements
- Retention chain, reserve and recovery objectives
- Pilot testing, rollback and support acceptance
011. Define the scaling requirement
Assess space shortages, queue delays, backup windows and restore duration separately. More disks do not resolve every CPU or network bottleneck. Identify unmet objectives through measurement.
Expected resultAssumptions, measurements and acceptance results are recorded.
022. Verify the supported architecture
Verify repository expansion, Data Mover scope and management-model options with support for the installed release. Multiple repositories do not guarantee automatic scale-out, active-active masters or unlimited horizontal scaling.
Expected resultAssumptions, measurements and acceptance results are recorded.
033. Measure resource constraints together
Measure source reads, CPU/memory, network, repository I/O and queue time over the same test interval. Job concurrency differs from transfer worker count. Assess whether added parallelism could saturate target storage or source applications.
Expected resultAssumptions, measurements and acceptance results are recorded.
044. Preserve data and identity continuity
Preserve catalog, chain and access dependencies during expansion or repository transitions. Do not reuse an old repository identity for a different physical data area. Move data only under supported migration and rollback plans.
Expected resultAssumptions, measurements and acceptance results are recorded.
055. Test one variable with a small pilot
In an approved test environment, change one variable and compare duration, throughput, errors/retries, CPU and I/O. Use the same data and method. A lab or development test does not establish acceptance of all production scale limits.
Expected resultAssumptions, measurements and acceptance results are recorded.
066. Complete backup and restore acceptance
Under expanded capacity and load, verify chain readability, isolated restore and application acceptance. Check access to older backups too. Increased transfer speed alone is not successful scaling.
Expected resultAssumptions, measurements and acceptance results are recorded.
077. Plan production rollout and monitoring
Record maintenance windows, rollback conditions, capacity reserves and response owners. Monitor alerts and recovery measurements after staged rollout. Request authorized documentation from destek@menabyte.com.tr for internal topology and technical limits.
Expected resultAssumptions, measurements and acceptance results are recorded.
COMMON QUESTIONS
Does adding a repository provide automatic scale-out?
There is no such guarantee from repository addition alone. Data placement, engine support, load and recovery acceptance require separate release-specific validation.