Solve for Disaster Recovery for Databases

Organisations today are focusing on disaster recovery plan with a combination of processes, policies, procedures and key metrics to recover all vital infrastructures, databases, applications, and services after a disaster in minimal time with a minimal impact.
Learn how #GoogleCloud as a DR site can help you in achieving Recovery Time Objective (RTO) and Recovery Point Objective (RPO) with minimal cost and maximum resiliency in comparison to being on any other cloud or on-premises.
To know more, talk to us → goo.gle/3u4rrKU

[@justinjeyaseelanalbert207]

Wonderful Explanation for DR solution and importance of RPO/RTO

[@shubhamnigam8209]

Nice expalnation..

[@ravichanderkt326]

Thanks for the wonderful session friend, I just have one concern lets take a scenario as cold recovery we can make use of backup's as a recover point and Read Replica will help us in Hot Recovery what's the best suitable recover strategy for Warm?

[@GoogleCloudAPAC]

Thanks for the question!
Disaster Recovery is defined for the entire tech stack and quantified by Recovery Point Objective (RPO) and Recovery Time Objective (RTO).
For planning a DR for databases -
Cold DR: Restoring from a Level-0 backup
Warm DR: Keeping the standby in sync using incremental backups as regular intervals (defined by RPO and RTO)
Hot DR: Keeping the standby in sync using Read replicas.
Hope this helped! Let us know if you have any further questions :)

[@ravichanderkt326]

@@GoogleCloudAPACThanks for your response, its make sense for me. See you in the cloud 😀