How to build a Disaster recovery plan in a 2nd AWS region for a small SQL Server DB (30 GB)
  • Anibal Palacios
    0
    Hi
    I have a Production SQL Server DB (30 GB) in Virginia and I want to have a DR plan in Oregon
    I want to have a cold strategy with a full backup (Virginia) and restore (Oregon) done every day at 01:00 and a transaction log backup done every 10 minutes only in Virginia to be restored in the DR site only if a DR event arises
    Could you please tell me how Cloudberry tools could help me in this situation?
    Thanks
    Anibal Palacios Options
  • Anton Zorin
    30
    ↪Anibal Palacios
    ↪Anibal Palacios
    in a nutshell, the plan is following:
    1. Do a full copy of your SQL server (image based) to S3.
    2. Then back up your MS SQL DB with MS SQL backup plan.
    3. Restore the server as another EC2 instance in the desired region.
    4. Create an application load balancer with target instances to your production and your DR instances.
    5. Point your users via the load balancer endpoint.
    6. Shut down the DR server.

    In case of disaster restore, start up your DR server and restore the DB to the latest recovery point available.

    Once the DB is restored your users will be able to connect.

    RTO should be around 10-20 minutes.
    The whole approach to be thoroughly tested before going to production.
    Thanks
    Anton Zorin Options
  • Anibal Palacios
    0
    Thanks
    Concerning RPO and your statement "restore the DB to the latest recovery point available", what tool do you recommend in order to have a 15 minutes RPO, taking in account that we are have a small DB (30 MB).
    Anibal Palacios Options
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment