Aws elastic disaster recovery vade vallu vunnara

[Sreeven]

Share your exp replicating and protecting database servers from onprem to cloud

[dasari4kntr]

i dont know…

curious to see the comments…

@csrcsr @Spartan @Ladies_Tailor

[Spartan]

Thats additional pay I feel.

You can configure your DB ex: Aurora MySQL RDS for PITR which is almost equal to <5min of dataloss in case of DR.

If you do multi-region replication which it allows, thats easy with no data loss.

AWS DR service kuda chesedi ade...but he will charge for that service...its very costly, similar to AWS DMS.

 

What we do is Aurora RDS, enable PITR and cross-region replication.

For DynamoDB we use Global Tables.

 

US East down aina, we were running fine, as I work on Tier0 services and have active-active stack.

[Spartan]

OnPrem to Cloud ante, its good service, replicate to AWS

Bandwidth Network IO and Storage ki pay chestav.

but you have to take care of again running backup both on-perm and also on AWS

[Sreeven]

39 minutes ago, Spartan said:

OnPrem to Cloud ante, its good service, replicate to AWS

Bandwidth Network IO and Storage ki pay chestav.

but you have to take care of again running backup both on-perm and also on AWS

Ba backup kadu just disaster recovery continues replication. VMs ante restore avutayi easy..main database on a VM replication konchem different and consistent leka pothe DB recover avvadu..real time evarikanna e aws elastic DR exp vundeo ani checking..released 2 years back only..

[Spartan]

2 minutes ago, Sreeven said:

Ba backup kadu just disaster recovery continues replication. VMs ante restore avutayi easy..main database on a VM replication konchem different and consistent leka pothe DB recover avvadu..real time evarikanna e aws elastic DR exp vundeo ani checking..released 2 years back only..

On Prem DB - VM lo run avutnda..?

you can still replicate it directly to AWS RDS Cluster instead of VM.

backup teskokapote, what is your plan if both on-perm and AWS RDS both fail.? 

 

[csrcsr]

12 minutes ago, Spartan said:

On Prem DB - VM lo run avutnda..?

you can still replicate it directly to AWS RDS Cluster instead of VM.

backup teskokapote, what is your plan if both on-perm and AWS RDS both fail.? 

 

 

58 minutes ago, Spartan said:

Thats additional pay I feel.

You can configure your DB ex: Aurora MySQL RDS for PITR which is almost equal to <5min of dataloss in case of DR.

If you do multi-region replication which it allows, thats easy with no data loss.

AWS DR service kuda chesedi ade...but he will charge for that service...its very costly, similar to AWS DMS.

 

What we do is Aurora RDS, enable PITR and cross-region replication.

For DynamoDB we use Global Tables.

 

US East down aina, we were running fine, as I work on Tier0 services and have active-active stack.

Anna you are telling how to make active active , in cloud environmen cross region replication. I guess the ask is to use on prem servers , they don't want to migate data using dms etc 

May be use this service to remove the replicated environment onprem and use this service in case of DR for RPO

[Spartan]

6 minutes ago, csrcsr said:

 

Anna you are telling how to make active active , in cloud environmen cross region replication. I guess the ask is to use on prem servers , they don't want to migate data using dms etc 

May be use this service to remove the replicated environment onprem and use this service in case of DR for RPO

ledanna..nenu cheppina scenario renditiki use avutadi.

ex1:

Assume On Perm is continuously replicating to AWS RDS, which can be done by AWS Virtual Connect, no need of AWS DR service.

On Perm, down aite, DNS dwara they can switch to serve from AWS DB.

ex2:  Same Assume On Perm is continuously replicating to AWS RDS, and traffic reads/writes are served to both. or

AWS RDS can be used for read ops, and On-Perm for write ops.

 

in both scenarios he has to take back up right. daniki PITR enable cheyali on AWS RDS antunna...

Assume a scenario where your both on perm and aws rds are down.

 

[Sreeven]

21 minutes ago, Spartan said:

On Prem DB - VM lo run avutnda..?

you can still replicate it directly to AWS RDS Cluster instead of VM.

backup teskokapote, what is your plan if both on-perm and AWS RDS both fail.? 

 

Backups separate..aws vadu 2021 december lo e elastic dr one started..this helps to do dr from onprem..onprem prod site and aws is DR..just replicate VMs and DBs runs on VM.

[Sreeven]

1 minute ago, Spartan said:

ledanna..nenu cheppina scenario renditiki use avutadi.

ex1:

Assume On Perm is continuously replicating to AWS RDS, which can be done by AWS Virtual Connect, no need of AWS DR service.

On Perm, down aite, DNS dwara they can switch to serve from AWS DB.

ex2:  Same Assume On Perm is continuously replicating to AWS RDS, and traffic reads/writes are served to both. or

AWS RDS can be used for read ops, and On-Perm for write ops.

 

in both scenarios he has to take back up right. daniki PITR enable cheyali on AWS RDS antunna...

Assume a scenario where your both on perm and aws rds are down.

 

Idhi expensive kada

[Spartan]

1 minute ago, Sreeven said:

Idhi expensive kada

virtual connect ki you pay for Network IO ops.

and then for RDS

nenu cheppedi enti ante......   above rendu combine chesi + some coloring = AWS DR Service.

[csrcsr]

Just now, Spartan said:

ledanna..nenu cheppina scenario renditiki use avutadi.

ex1:

Assume On Perm is continuously replicating to AWS RDS, which can be done by AWS Virtual Connect, no need of AWS DR service.

On Perm, down aite, DNS dwara they can switch to serve from AWS DB.

ex2:  Same Assume On Perm is continuously replicating to AWS RDS, and traffic reads/writes are served to both. or

AWS RDS can be used for read ops, and On-Perm for write ops.

 

in both scenarios he has to take back up right. daniki PITR enable cheyali on AWS RDS antunna...

Assume a scenario where your both on perm and aws rds are down.

 

Anna on prem db can be anything , why are you thinking only RDS ?? The goal is not to serve the traffic with aws instance  who knows the database compatability , here the goal is RTO RPo by storing data in some staging subnet , adi TS ask ani anukuntuna may be wrong

[csrcsr]

2 minutes ago, Spartan said:

virtual connect ki you pay for Network IO ops.

and then for RDS

nenu cheppedi enti ante......   above rendu combine chesi + some coloring = AWS DR Service.

No anna  guess the approach you mentioned us  good when you have strategy to move eventually to aws , not for using as DR back up

[Spartan]

1 minute ago, csrcsr said:

Anna on prem db can be anything , why are you thinking only RDS ?? The goal is not to serve the traffic with aws instance  who knows the database compatability , here the goal is RTO RPo by storing data in some staging subnet , adi TS ask ani anukuntuna may be wrong

RDS was example

[Spartan]

1 minute ago, csrcsr said:

No anna  guess the approach you mentioned us  good when you have strategy to move eventually to aws , not for using as DR back up

what is DR definition mix up aipoindi anukunta disco lo