VirtuWa
Try Demo
Hemaya · Use cases

Hemaya backup and DR scenarios

How protection and recovery for virtual workloads is designed to work for organisations with formal recovery objectives.

Illustrative deployment scenario. These pages describe how VirtuWa is designed to be deployed for this type of organisation — they are not customer references and contain no named customers, quotes or measured customer results.

Scenarios

Where Hemaya fits

Government entity

Protecting national services with in-country recovery

An entity must protect internal and public-facing services and keep backup copies inside facilities it controls.

Requirements
  • Backup copies held in controlled facilities
  • Documented restore procedures
  • Retention aligned to internal policy
How VirtuWa is applied
  • Scheduled backup of virtual workloads through Hemaya
  • Retention policies per workload class
  • Recovery orchestration exercised on a defined cycle
Operational outcomes to validate
  • Restores tested, not assumed
  • Retention that matches written policy
  • Recovery evidence available for audit
Financial institution

Meeting recovery objectives for critical systems

A financial institution defines recovery time and recovery point objectives per system tier.

Requirements
  • Different objectives for each system tier
  • Regular proof that recovery works
  • Recovery to a secondary site
How VirtuWa is applied
  • Protection policies mapped to system tiers
  • DR orchestration for grouped workloads
  • Scheduled recovery rehearsals
Operational outcomes to validate
  • Objectives validated by rehearsal
  • Documented recovery runbooks
  • Clear ownership per system tier
Education / research

Protecting research and administrative workloads

A university protects administrative systems and long-running research environments with limited operational staff.

Requirements
  • Small team managing many workloads
  • Long retention for research data sets
  • Simple, repeatable restore process
How VirtuWa is applied
  • Policy-driven backup across the estate
  • Retention tiers for research versus administration
  • Self-service restore workflows for approved staff
Operational outcomes to validate
  • Less manual protection work
  • Predictable storage consumption
  • Faster restores for common requests
Validation

What to validate in a POC

  • Backup and restore of your representative workloads
  • Retention policy behaviour over a full cycle
  • Recovery orchestration for a grouped application
  • Recovery time and recovery point measured in your environment
  • Evidence and reporting suitable for audit
FAQ

Questions about this scenario

No. They are illustrative protection scenarios describing how Hemaya is designed to be used.

Test recovery against your own objectives

Measure restore and recovery behaviour with your workloads before committing.