0

On AWS I've always imaged machines that contained SQL Server installations and running databases. When I spin up new instances from the images, SQL Server and all database always returned without issue (e.g. consistency checking always came back successful).

Is this to be expected? i.e. SQL Server being ACID compliant, allows a snapshot of the disk to be taken due to the data in the DB file and log being in a consistent and durable state, so allowing the database to recover itself when it comes back to life when spun up on a new instance from the image.

The following seem to support this idea, but discussion at work this week have resulted in me questioning this?

https://docs.aws.amazon.com/prescriptive-guidance/latest/backup-recovery/ec2-backup.html

https://n2ws.com/blog/aws-sql-server-backup/backup-and-restore-your-microsoft-sql-server-on-aws-cloud-part-2

Does anyone have any definitive information, and if this is ok to do, is it AWS only, or do other IAAS platforms (Azure / GCP) support this as a DR strategy?

ANDYTEAS
  • 1
  • 2

1 Answers1

0

Yes it is possible to backup the RDBMS data in blob storage format and doing point in time recovery from the same, retaining ACID properties. In GCP this is the recommended way 1. Here you backup the data in Google Cloud Storage which is a blob storage, but it works for backing up and restoring relational data.

Krish
  • 120
  • 3