Trust Center ยท Backup and recovery
Getting systems and data back when something fails
Moraph builds and runs software for banks, health systems and government agencies. If a client loses data or a system goes down, payments, patient care or public services can stop. This page covers our recovery targets, the tools that back up each part of what we run, how a failed backup is caught and how restores are tested.
Recovery targets
One hour to restore, 15 minutes of data at most
For our most critical systems (Tier 1), we commit to restoring service within one hour and losing no more than 15 minutes of data.
1 hour: recovery time objective
The longest a Tier 1 system should be down before it is running again.
15 minutes: recovery point objective
The most recent data a Tier 1 system can lose, measured in time. After a restore, nothing older than 15 minutes should be missing.
The recovery objectives for a particular service are set in the client's agreement.
What protects what
The tools behind the targets
Client data that has to stay in-country is held in Moraph's own data centers: Switch in the United States, Ark Data Centres in the United Kingdom and NextDC in Sydney. These tools back up what we run there, plus the devices of the teams that support federal clients.
| Tool | What it does for Moraph |
|---|---|
| Veeam | Backs up the servers in our data centers at Switch (US), Ark Data Centres (UK) and NextDC (Sydney). |
| Veeam ONE | Monitors those backups and alerts our 24/7 operations team when one fails. |
| Cohesity SmartFiles | Manages the files and documents stored in our data centers. |
| NetBackup (Cohesity) | Backup software we already ran when it was Veritas NetBackup. It became part of Cohesity when Cohesity acquired Veritas's data protection business. |
| Druva GovCloud | Backs up the laptops and Microsoft 365 data of the teams that support our federal clients. See Federal work. |
Failed backups
A missed backup is caught on the next shift, not during a recovery
The risk
A backup that fails without anyone noticing usually comes to light at the worst moment: when someone needs to restore from it.
What we do
Veeam ONE alerts our 24/7 operations team when a backup fails. The team works around the clock, so a missed backup is caught on the next shift, not in the middle of a recovery.
Restore tests
Backups are tested by restoring them
A backup is only useful if it can be restored. We test restores regularly against the Tier 1 targets.
Time
Did the system come back within one hour?
Data
Was the restored data no more than 15 minutes old?
If your vendor-risk review needs evidence of restore testing, say so when you request the evidence pack.
Federal work
FedRAMP-authorized backup for federal teams
Our federal work requires tools the US government has approved under FedRAMP, so the teams that support federal clients are backed up separately from everyone else.
Druva GovCloud
Druva GovCloud is FedRAMP Moderate authorized. It runs on AWS GovCloud (US), Amazon's separate cloud for US government data. We use it only for federal work: it backs up the laptops and Microsoft 365 data of the teams supporting our federal clients.
Everyone else
Laptops and cloud apps of other teams are backed up by other means, not through Druva GovCloud.
A FedRAMP authorization belongs to the service that holds it, here Druva GovCloud. Moraph itself holds no FedRAMP authorization; see Frameworks.
Where backups are held
Backups follow your residency terms
Your agreement names the region and facility that hold your data. It also says where backups and recovery copies are kept, and whether any copy leaves the region. If your regulator needs that in writing, ask for it. The data residency section of the Trust Center describes each region.
Limits
What this page does and doesn't cover
- The one-hour and 15-minute objectives are for Tier 1, our most critical systems. The objectives for each service you use are the ones in your agreement.
- This page covers how Moraph backs up the systems it runs itself. If you want Moraph to manage backups in your own environment, that is part of the Global Resilience Operations managed service, which works with tools such as Rubrik, Cohesity or Veeam.
- Druva GovCloud's FedRAMP authorization covers Druva's service. It does not make Moraph, or any other Moraph system, FedRAMP authorized.
Questions
Frequently asked questions
What do recovery time and recovery point objectives mean?
The recovery time objective is how quickly a system must be running again after a disruption. The recovery point objective is how much recent data, measured in time, can be lost. For Tier 1 systems they are one hour and 15 minutes.
Do the one-hour and 15-minute targets apply to every system?
They apply to Tier 1, our most critical systems. The objectives for a particular service are set in your agreement.
Who finds out when a backup fails?
Our 24/7 operations team. Veeam ONE alerts them when a backup of a data center server fails, so it is dealt with on the next shift.
Can our backups leave our region?
Where backups and recovery copies are kept, and whether any copy leaves the region, is set in your agreement.
Can Moraph back up our own systems?
Yes, as part of a managed service from Global Resilience Operations, which manages backups and tests restores in client environments.