Dr planning tools

App to manage Google Cloud services from your mobile device. Interactive shell environment with a built-in command line. Kubernetes add-on for managing Google Cloud resources. Tools for monitoring, controlling, and optimizing your costs.

Tools for easily managing performance, security, and cost. Service catalog for admins managing internal enterprise solutions. Open source tool to provision Google Cloud resources with declarative configuration files. Media and Gaming. Game server management service running on Google Kubernetes Engine. Open source render manager for visual effects and animation. Convert video files and package them for optimized delivery. App migration to the cloud for low-cost refresh cycles.

Data import service for scheduling and moving data into BigQuery. Reference templates for Deployment Manager and Terraform. Components for migrating VMs and physical servers to Compute Engine. Storage server for moving large volumes of data to Google Cloud. Data transfers from online and on-premises sources to Cloud Storage. Migrate and run your VMware workloads natively on Google Cloud.

Security policies and defense against web and DDoS attacks. Content delivery network for serving web and video content. Domain name system for reliable and low-latency name lookups. Service for distributing traffic across applications and regions. NAT service for giving private instances internet access. Connectivity options for VPN, peering, and enterprise needs. Connectivity management to help simplify and scale networks.

Network monitoring, verification, and optimization platform. Cloud network options based on performance, availability, and cost. VPC flow logs for network monitoring, forensics, and security. Google Cloud audit, platform, and application logs management. Infrastructure and application health with rich metrics.

Application error identification and analysis. GKE app development and troubleshooting. Tracing system collecting latency data from applications. CPU and heap profiler for analyzing application performance. Real-time application state inspection and in-production debugging. Tools for easily optimizing performance, security, and cost. Permissions management system for Google Cloud resources. Compliance and security controls for sensitive workloads.

Manage encryption keys on Google Cloud. Encrypt data in use with Confidential VMs. Platform for defending against threats to your Google Cloud assets. Sensitive data inspection, classification, and redaction platform. Managed Service for Microsoft Active Directory. Cloud provider visibility through near real-time logs.

Two-factor authentication device for user account protection. Store API keys, passwords, certificates, and other sensitive data. Zero trust solution for secure application and resource access.

Platform for creating functions that respond to cloud events. Workflow orchestration for serverless products and API services. Cloud-based storage services for your business. File storage that is highly scalable and secure. Block storage for virtual machine instances running on Google Cloud. Object storage for storing and serving user-generated content. Block storage that is locally attached for high-performance needs.

Data archive that offers online access speed at ultra low cost. Contact us today to get a quote. Request a quote. Google Cloud Pricing overview. Pay only for what you use with no lock-in. Get pricing details for individual products. Related Products Google Workspace. Get started for free. Self-service Resources Quickstarts. View short tutorials to help you get started. Stay in the know and become an Innovator.

Prepare and register for certifications. Expert help and training Consulting. Partner with our experts on cloud projects. Enroll in on-demand or classroom training. Partners and third-party tools Google Cloud partners. Explore benefits of working with a partner.

Join the Partner Advantage program. Deploy ready-to-go solutions in a few clicks. More ways to get started. The series consists of these parts: Disaster recovery planning guide this article Disaster recovery building blocks Disaster recovery scenarios for data Disaster recovery scenarios for applications Architecting disaster recovery for locality-restricted workloads Disaster recovery use cases: locality-restricted data analytic applications Architecting disaster recovery for cloud infrastructure outages Introduction Service-interrupting events can happen at any time.

Basics of DR planning DR is a subset of business continuity planning. DR planning begins with a business impact analysis that defines two key metrics: A recovery time objective RTO , which is the maximum acceptable length of time that your application can be offline.

This value is usually defined as part of a larger service level agreement SLA. A recovery point objective RPO , which is the maximum acceptable length of time during which data might be lost from your application due to a major incident. This metric varies based on the ways that the data is used. For example, user data that's frequently modified could have an RPO of just a few minutes.

In contrast, less critical, infrequently modified data could have an RPO of several hours. This metric describes only the length of time; it doesn't address the amount or quality of the data that's lost. Why Google Cloud? For example, traditional DR planning requires you to account for a number of requirements, including the following: Capacity: securing enough resources to scale as needed. Security: providing physical security to protect assets. Network infrastructure: including software components such as firewalls and load balancers.

Support: making available skilled technicians to perform maintenance and to address issues. Bandwidth: planning suitable bandwidth for peak load. Facilities: ensuring physical infrastructure, including equipment and power. Google Cloud offers several features that are relevant to DR planning, including the following: A global network. Google has one of the largest and most advanced computer networks in the world. The Google backbone network uses advanced software-defined networking and edge-caching services to deliver fast, consistent, and scalable performance.

Multiple points of presence PoPs across the globe mean strong redundancy. Your data is mirrored automatically across storage devices in multiple locations. Google Cloud is designed to scale like other Google products for example, search and Gmail , even when you experience a huge traffic spike. Managed services such as App Engine, Compute Engine autoscalers, and Datastore give you automatic scaling that enables your application to grow and shrink as needed.

The Google security model is built on over 15 years of experience with helping to keep customers safe on Google applications like Gmail and Google Workspace. In addition, the site reliability engineering teams at Google help ensure high availability and prevent abuse of platform resources.

Google undergoes regular independent third-party audits to verify that Google Cloud is in alignment with security, privacy, and compliance regulations and best practices. DR patterns DR patterns are considered to be cold, warm, or hot. How you deal with a flat tire depends on how prepared you are: Cold: You have no spare tire, so you must call someone to come to you with a new tire and replace it. Your trip stops until help arrives to make the repair.

Warm: You have a spare tire and a replacement kit, so you can get back on the road using what you have in your car. However, you must stop your journey to repair the problem. Hot: You have run-flat tires. You might need to slow down a little, but there is no immediate impact on your journey.

Your tires run well enough that you can continue although you must eventually address the issue. Design according to your recovery goals When you design your DR plan, you need to combine your application and data recovery techniques and look at the bigger picture. Design for end-to-end recovery It isn't enough just to have a plan for backing up or archiving your data. Make your tasks specific When it's time to run your DR plan, you don't want to be stuck guessing what each step means.

Implementing control measures Add controls to prevent disasters from occurring and to detect issues before they occur. Preparing your software Part of your DR planning is to make sure that the software you rely on is ready for a recovery event.

Verify that you can install your software Make sure that your application software can be installed from source or from a preconfigured image. Design continuous deployment for recovery Your continuous deployment CD toolset is an integral component when you are deploying your applications. Implementing security and compliance controls When you design a DR plan, security is important. Configure security the same for the DR and production environments Make sure that your network controls provide the same separation and blocking that the source production environment uses.

The following list outlines ways to synchronize permissions between environments: If your production environment is Google Cloud, replicating IAM policies in the DR environment is straightforward. Verify your DR security After you've configured permissions for the DR environment, make sure that you test everything.

Make sure users can log in to the DR environment Similarly, don't wait for a disaster to occur before checking that your users can access the DR environment.

Train users Users need to understand how to undertake the actions in Google Cloud that they're used to accomplishing in the production environment, like logging in, accessing VMs, and so on. Make sure that the DR environment meets compliance requirements Verify that access to your DR environment is restricted to only those who need access.

Treat recovered data like production data Make sure that the security controls that you apply to your production data also apply to your recovered data: the same permissions, encryption, and audit requirements should all apply. Making sure your DR plan works You want to make sure that your planning pays off by making sure that if disaster does strike, everything works as you intend. Maintain more than one data recovery path In the event of a disaster, your connection method to Google Cloud might become unavailable.

Test your plan regularly After you have a DR plan in place, test it regularly, noting any issues that come up and adjusting your plan accordingly. We recommend that you implement the following in order to help with your testing: Automate infrastructure provisioning with Deployment Manager.

If you're running your production environment on premises, make sure that you have a monitoring process that can start the DR process when it detects a failure and can trigger the appropriate recovery actions.

Monitor and debug your tests with Cloud Logging and Cloud Monitoring. Google Cloud has excellent logging and monitoring tools that you can access through API calls, allowing you to automate the deployment of recovery scenarios by reacting to metrics. When you're designing tests, make sure that you have appropriate monitoring and alerting in place that can trigger appropriate recovery actions.

Perform the testing noted earlier: Test that permissions and user access work in the DR environment like they do in the production environment.

Perform penetration testing on your DR environment. Perform a test in which your usual access path to Google Cloud doesn't work. What's next? Read about Google Cloud geography and regions. Read other articles in this DR series: Disaster recovery building blocks Disaster recovery scenarios for data Disaster recovery scenarios for applications Architecting disaster recovery for locality-restricted workloads Disaster recovery use cases: locality-restricted data analytic applications Architecting disaster recovery for cloud infrastructure outages Explore reference architectures, diagrams, tutorials, and best practices about Google Cloud.

Take a look at our Cloud Architecture Center. Cloud Premium uses Virtualization of your systems and data, and in the event of a disaster can be used as a failover. Sungard AS delivers a leading DRaaS and business continuity solution, as part of its cloud and physical infrastructure recovery service. The company also provides infrastructure and resilience consulting, as well as managed colocation services. For Sungard's DRaaS, the focus is in working with complex hybrid systems, where some of the IT infrastructure may be in a private cloud, some running on-premises, while other legacy systems are tacked on.

The process involves starting with data protection, then restoring environments, and the process is fully managed. Veeam Availability Suite provides an all-round back-up and replication solution through a single management console.

Veeam uses a cloud repository to store and replicate all data and IT infrastructure, so it can be called upon for use for any disaster recovery purposes. Databarracks is a British company that has provided online backup services since The company also provide public cloud management, including designing, building, and migrating to Amazon Web Services, Google Cloud Platform, and Microsoft Azure.

Brian has over 30 years publishing experience as a writer and editor across a range of computing and technology titles, and has been interviewed multiple times for BBC News and BBC Radio. He is also a science fiction and fantasy author, writing as Brian G Turner. North America. View Deal. Microsoft Azure Site Recovery. Reasons to avoid - Lacks integrations. Ekco Disaster Recovery. Brian Turner. AWS went down hard, yet again - here's what happened.

Microsoft Teams update will level the playing field for all users. Honor's new foldable phone is bigger and more powerful than the Galaxy Z Fold 3. Apple Watch 7 vs Samsung Galaxy Watch 4: which is the best smartwatch? Building a disaster recovery plan is not as simple as writing a document. You need to do careful research to understand the needs of your organization and the risks it faces.

You also need to carefully coordinate the plan with all stakeholders, test it to make sure it works, and continuously update it to make sure it stays relevant. If you need to backup data to on-premises storage, Cloudian offers low-cost disk-based storage with capacity up to 1. You can also set up a Cloudian appliance in a remote site and save data directly to the remote site using our integrated data management tools.

Alternatively, you can use a hybrid cloud setup. Backup data to a local Cloudian appliance, and configure it to replicate all data to the cloud. This allows you to access data locally for quick recovery, while keeping a copy of data on the cloud in case a disaster affects the on-premise data center.

Personnel — who is responsible for executing the DR plan. IT inventory — list hardware and software assets, their criticality, and whether they are leased, owned or used a service. Backup procedures — how and where exactly on which devices and in which folders each data resource is backed up, and how to recover from backup. Disaster recovery procedures — emergency response to limit damages, last-minute backups, mitigation and eradication for cybersecurity threats.

Disaster recovery sites — a robust DR plan includes a hot disaster recovery site — an alternative data center in a remote location that has all critical systems, with data replicated or frequently backed up to them. Operations can be switched over to the hot site when disaster strikes.

Restoration — procedures for recovering from complete systems loss to full operations. Follow these steps to create a working disaster recovery plan: Map out your assets — identify what you need to protect, including network equipment, hardware, software, cloud services, and most important, your critical data.

For each item note its physical or virtual location, relation to other assets, vendor and version, networking parameters, etc. Identify criticality and context — understand how your assets are used and their importance to the business.

Classify assets into high impact, medium impact and low impact, by identifying how likely they are to disrupt business operations.