Re: Question on database availability

From: yudhi s <learnerdatabase99_at_gmail.com>
Date: Sun, 20 Aug 2023 23:25:38 +0530
Message-ID: <CAEzWdqeqqxwuME83WpB1g1BG9pk0rBgCw4QZrJpbV9X=XA997A_at_mail.gmail.com>



There are different methods like backups, snapshots, physical standby, replications etc. Tools like data guard in Oracle Patroni in Postgre etc. But as you said, I also think you can divide broadly into two categories like HA(High Availability) and DR(Disaster Recovery). Backup option will make the RTO >0 , so in those cases the two data centers with data guard option are there and are mostly the standard used across all the on premise databases. In cloud too you may see the same or else a common strategy as three data centers with one in SYNC replication in the same region(mainly with minimal network latency to make sure RTO(in minutes),RPO=0 and used as High availability option mainly) and another data center with ASYNC replication in another region for the DR(RTO/RPO>0). I believe these are the common setups. Not sure if there exists a true RPO=0 and RTO=0 solution for DR. Also you may talk about different backup strategies incremental etc.

On Sun, Aug 20, 2023 at 11:09 PM Lok P <loknath.73_at_gmail.com> wrote:

> Hello Experts,
>
> We want to have a ~1hr presentation for our dev and DBA groups around the
> criticality of database resilience for businesses. Different methods
> (irrespective of any specific database though) of database resilience both
> around "on premise" and cloud font. I am not able to come up with exact
> steps to move ahead. What are the things we should go through here? Can you
> suggest how to put it in a consolidated steps wise way or some ideas around
> it? Maybe some sample document/blog which can provide the details around
> it. I understand it's a vast topic , so should we mainly divide into two
> categories like HA(high availability) and DR(Disaster recovery) and talk on
> those, or does any other side exist too?
>
> Regards
> Lok
>

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Aug 20 2023 - 19:55:38 CEST

Original text of this message