A backup matters when the business service can be restored.
Design protection around the service you need to recover, including its identity, data, application and infrastructure dependencies. TRILOGY helps define the recovery scope, configure the selected architecture and verify restoration through agreed tests.
When this solution is relevant
Backup refresh
Review workload support, retention, storage and restore requirements.
Disaster recovery
Define recovery-site dependencies, sequence and operating responsibilities.
Ransomware recovery
Separate protected recovery data and assess isolated restoration options.
SaaS data protection
Evaluate independent backup for the supported Microsoft 365 or other SaaS workloads.
Technology options
Technology options to evaluate against your requirement. Product capabilities, editions and integrations are confirmed in the agreed configuration.
Platforms
Cohesity — DataProtect / FortKnox
- DataProtect provides backup and recovery within Cohesity Data Cloud
- FortKnox adds managed cyber-vault options
- Isolation architecture, supported regions and workload fit are reviewed before selection
Cohesity — NetBackup — formerly Veritas enterprise data protection
- Enterprise backup and recovery through the NetBackup product line
- Supported integration with FortKnox for protected cloud storage
- Existing estates are reviewed for migration, support and licensing continuity
NetBackup and DataProtect are distinct product lines under one vendor; they are not two independently ranked vendors.
Official product reference
Commvault — Commvault Cloud
- Backup and recovery across supported hybrid workloads
- Air Gap Protect offers separately scoped immutable cloud storage
- Recovery design includes workload coverage, access and test procedures
Rubrik — Rubrik Security Cloud
- Protection and cyber-recovery workflows within Rubrik Security Cloud
- Recovery simulation supports testing defined recovery plans
- Additional vault and threat-analysis capabilities are separately scoped
Veeam — Veeam Data Platform / Backup & Replication
- Backup and recovery for supported virtual, physical and cloud workloads
- Platform editions determine monitoring and recovery-orchestration capabilities
- Backup & Replication 13.1 is documented as released on 29 July 2026
Dell Technologies — PowerProtect Data Manager
- Centralized protection management for supported enterprise workloads
- Integrates with the selected Dell protection-storage architecture
- Recovery and orchestration capabilities depend on version and workload
Additional backup platform
- Arcserve
Arcserve — Unified Data Protection — UDP
- Data protection across supported physical, virtual and cloud environments
- Backup and recovery features selected by UDP edition
- Storage and appliance availability require a current configuration review
Continuous protection and disaster recovery
HPE — HPE Zerto Software
- Continuous data protection and replication for supported platforms
- Virtual protection groups coordinate multi-VM recovery checkpoints
- Site recovery and mobility are scoped separately from long-term backup
Protection storage
Dell Technologies — PowerProtect Data Domain
- Protection storage for supported backup architectures
- Data reduction and repository functions sized by model
- Storage security and retention are defined independently of backup orchestration
- ExaGrid
ExaGrid — Tiered Backup Storage
- Landing Zone disk cache separates backup ingest from long-term retention
- Repository tier provides retention with time-lock options
- Capacity and backup-software compatibility are sized for the environment
SaaS protection
Veeam — Veeam Data Cloud / Backup for Microsoft 365
- Microsoft 365 backup covers supported Exchange, SharePoint, OneDrive and Teams data
- SaaS and self-managed deployment models are distinct
- Supported identity coverage and retention depend on the chosen offering
Commvault — Commvault SaaS Backup
- SaaS workload protection within the Commvault portfolio
- Backup scope is selected for supported cloud applications
- Recovery, retention and storage region are reviewed per service
Names and trademarks belong to their owners.
What we verify
Protection coverage
Protected workloads reconciled with the approved inventory.
Restore-point age
Age of a usable tested recovery point compared with the agreed objective.
Observed recovery time
Elapsed time to restore and verify the defined service in the test environment.
Recovery completeness
Dependency, integrity and functional checks completed with documented exceptions.
How the technical work is scoped
01
Scope and architecture
Define the assets, integrations, ownership and acceptance criteria before selecting the configuration.
02
Implementation and change
Configure the agreed controls through an approved change plan, with rollback steps and assigned responsibilities.
03
Verification and handover
Test agreed scenarios, record exceptions and hand over the configuration, operating procedures and test evidence.
Technical scope in detail
Recovery objectives start with the service
RTO and RPO are agreed for defined business services, not copied from a product brochure. Dependencies, recovery order and test conditions are documented. Results describe what was actually achieved in that test.
Protected copies and administrative separation
Immutability, retention and privileged access are configured according to the selected platform. Backup administration and recovery access are reviewed separately. A protected copy still requires a verified restoration path.
Isolated restore environment
The recovery design identifies compute, network, identity and security checks needed before reconnecting a restored workload. Isolation is scoped to the architecture. Test evidence records the environment and the validation performed.
Disaster recovery and CDP
Replication and continuous data protection support selected recovery objectives. They are not automatically substitutes for independent long-term backups. Failover and failback are tested as separate procedures.
SaaS backup
Covered applications, object types, retention and service region are checked before selection. Restore tests verify supported granular and bulk recovery paths. A SaaS subscription does not imply that every data type is recoverable through the chosen backup product.
Recovery evidence and handover
Tests capture recovery-point selection, restoration steps and application validation. Known exceptions and untested dependencies remain visible. Handover includes the runbook, ownership and a plan for future tests.
Licensing and sizing
Review workload count and capacity, retention, change rate, storage targets and recovery objectives. Include the required platform edition, orchestration, vault, SaaS coverage, repository and support components in the scope.
What to share with us
Critical services and dependencies; workload inventory; current backup; recovery objectives and test resources.
What you receive
Agreed scope and architecture
Selected configuration and integration record
Approved change and rollback plan
Test record and documented exceptions
Operating procedures and technical handover
Frequently asked questions
Can you promise a fixed recovery time before discovery?
A credible target requires a defined service, dependencies, resources and test conditions. Verified test results and contractual commitments are distinct.
Does immutable storage guarantee clean recovery?
No. Recovery also requires usable data, working dependencies, suitable resources and security validation.
Are NetBackup and Cohesity separate vendors?
NetBackup is now part of Cohesity. NetBackup and DataProtect remain distinct product options within that portfolio.
Is all Saudi data required to stay in Saudi Arabia?
Hosting and transfer requirements depend on the applicable rules, data classification and service scope. PDPL does not justify a blanket statement for every workload.
Discuss the requirement
Tell us what you need to protect, change or recover. We will use the details to define the next technical discussion.
Prefer to talk? Call +966591909277