Backup & Disaster Recovery

RPO vs RTO — the two numbers that matter

Recovery Point Objective (RPO) is how much data you can afford to lose, measured in time. Recovery Time Objective (RTO) is how long you can afford to be down. Every backup and DR design is ultimately an exercise in engineering to a specific RPO and RTO for each workload — and in proving, through testing, that those targets are actually met.

The 3-2-1-1-0 rule

• 3 copies of your data,
• on 2 different media types,
• with 1 copy off-site,
• 1 copy offline or immutable (air-gapped against ransomware),
• and 0 errors verified through regular recovery testing.

Enterprise backup with Veritas NetBackup

NetBackup remains a workhorse for heterogeneous enterprise estates — physical, virtual, database, and cloud workloads under a single policy framework. Its strengths are scale, granular policy control, and deduplication; the operational challenge is governance: ensuring policies actually cover every workload and that restores are routinely exercised, not assumed.

Cloud-integrated backup & Indian retention compliance

Cloud tiers make long-term, immutable retention economical, but Indian enterprises must reconcile this with data-residency rules. The practical answer is a hybrid posture: keep primary and operational restores local for speed and compliance, and use a compliant cloud tier for long-term, ransomware-resistant retention that satisfies sector-specific record-keeping mandates.