An IT team planning together at a whiteboard

Managed IT & Support

Cloud disaster recovery
and business continuity.Keep Your Organization Resilient and Prepared

Our BC/DR services ensure your data, people, and operations stay protected during unexpected events. We help organizations design and test cloud-based disaster recovery strategies using Google Cloud, Vault, Drive, and Workspace tools.

Talk about a recovery plan What Google covers, what a plan adds

What are backup and disaster recovery services?

Backup and disaster recovery services plan how your systems and data come back after an outage, a deletion or an attack, and set how long each can be down and how much data you can afford to lose.

Google calls those two limits the recovery time objective (RTO), "the maximum acceptable length of time that your application can be offline", and the recovery point objective (RPO), the most data you can lose to a major incident, measured in time. Business continuity is the wider plan: how your people keep working while systems recover. Google keeps Google Workspace running under a 99.9% monthly uptime SLA, but once a user's deleted mail or files leave the trash, an admin has 25 days to restore them. A continuity plan covers both.

Two IT staff reviewing a document beside rows of white server cabinets

Service elements

Incident readiness planning

Recovery targets for each system, and who does what, and how people reach each other, when something goes wrong.

Backup and retention configuration

Backups for the Google Cloud workloads you can't lose, and Vault retention rules set with your legal team, so data outlasts Workspace's restore windows.

Cross-region redundancy

Google Cloud workloads designed to keep running, or come back quickly, if a zone or a whole region goes down, matched to each application's RTO and RPO.

Recovery playbooks + simulations

Step-by-step recovery playbooks your team can follow, tested in simulations and adjusted after each one.

Data governance and access controls

Who can restore, export or delete your data, set out and checked, so the people recovering it are the people who should.

What Google covers, what a plan adds

Google runs the infrastructure and gives you the tools. What to protect, how fast it comes back and who does the work is yours to decide, and that's the plan.

Compare	With a Suitebriar plan	Google, on its own
Workspace uptime	A plan for the hours your people can't work as usual: who does what, and how they reach each other	A 99.9% monthly uptime SLA for Gmail, Drive, Meet and the other covered services
Deleted Workspace data	Backup and retention set up so the data you need outlasts those windows	Admins can restore a deleted user for 20 days, and Drive or Gmail data for 25 days after it leaves the trash
Google Cloud workloads	Cross-region redundancy and backups designed around each application's RTO and RPO	Zones and regions, and the Backup and DR Service with immutable, indelible backup vaults
Retention	Retention periods decided with your legal team, and backups for what Vault doesn't cover	Vault retention rules and holds; Google notes that Vault isn't a data archive
Testing	Recovery playbooks and simulations, with the plan updated after each one	Google's advice: test a DR plan regularly and adjust it

Compare	Google, on its own	With a Suitebriar plan
Workspace uptime	A 99.9% monthly uptime SLA for Gmail, Drive, Meet and the other covered services	A plan for the hours your people can't work as usual: who does what, and how they reach each other
Deleted Workspace data	Admins can restore a deleted user for 20 days, and Drive or Gmail data for 25 days after it leaves the trash	Backup and retention set up so the data you need outlasts those windows
Google Cloud workloads	Zones and regions, and the Backup and DR Service with immutable, indelible backup vaults	Cross-region redundancy and backups designed around each application's RTO and RPO
Retention	Vault retention rules and holds; Google notes that Vault isn't a data archive	Retention periods decided with your legal team, and backups for what Vault doesn't cover
Testing	Google's advice: test a DR plan regularly and adjust it	Recovery playbooks and simulations, with the plan updated after each one

How we build a recovery plan

Set recovery targetsList the systems and data you run on, and agree an RTO and RPO for each with the people who depend on them.
Configure backup and retentionSet up backups for Google Cloud workloads and retention for Workspace data, and check who can restore, export or delete it.
Build in redundancyDesign Google Cloud workloads to run in more than one zone or region where their targets call for it.
Write playbooks and test themWrite the recovery steps down, run a simulation, and adjust the plan from what it shows.

Talk about a recovery plan

Three colleagues reviewing a plan on a laptop

Disaster recovery FAQ

What IT leads ask when they plan for an outage, a deletion or an attack on Google Cloud and Workspace.

Not sure where you stand?

Tell us what you run on Google Cloud and Workspace and what would hurt most if it stopped, and we'll talk through where to start.

(888) 545-3685 Talk about a recovery plan

What's the difference between disaster recovery and business continuity?

Disaster recovery brings systems and data back after an incident, within the recovery targets you set. Business continuity is the wider plan for keeping the organization working meanwhile: your people, how they communicate and which work comes first. Our BC/DR services cover both.

Do we need disaster recovery if we're on Google Workspace?

Google keeps Workspace running, with a 99.9% monthly uptime SLA, but it doesn't keep deleted data indefinitely. An admin can restore a deleted user for 20 days, and Drive or Gmail data for 25 days after it leaves the trash; after that, Google says, the data can't be restored, even by technical support. Vault retention helps, but Google notes Vault isn't a data archive. So a Workspace continuity plan still needs backup, retention and a plan for people.

How does Google Cloud disaster recovery work?

Google recommends deploying applications across multiple zones and regions, and running backup services in a different region to soften a region outage. Its Backup and DR Service backs up Compute Engine, Cloud SQL, AlloyDB and other workloads into isolated backup vaults that can't be changed or deleted. The design for each application follows from its RTO and RPO.

What are RTO and RPO?

RTO, the recovery time objective, is how long an application can be offline. RPO, the recovery point objective, is how much data, measured in time, you can afford to lose. Google suggests choosing a recovery pattern, from cold (rebuild when needed) to hot (keeps running), that meets both.