Home | Concept/Dataflow | Usage | Typical Scenarios | Troubleshoot

The concept behind this toolset

Data flow of a typical backup operation
The data flow of a typical backup operation will be depicted by the following diagram.
image001.png
The following table is to describe each of the steps.

Step Description
Step 1 (Optional) Copy the source database to a new database on the same logical server in data center A for transactionally consistent purpose.
Step 2 (Optional) Use Import/Export Service to export the just made database copy to Windows Azure Storage in another data center B.
Step 3 (Optional) Once export finishes, immediately import the BACPAC to a logical server in the same data center B to verify the restore will be successful or not.
Step 4 (Optional) Copy the exported BACPAC to an on-premises secured storage location.


Notes & caveats:
  • Both step 1 and step 2 are optional, however, at least one of these two steps are required. If only step 1 is enabled, only database copy on the same logical server (the same data center) will happen. This configuration is typically useful for scenarios like just before a deployment, a database migration, etc. to prevent unwanted user errors
  • If only step 2 is enabled, then only export to another data center will happen. While this configuration provide cost effective effects, it has a risk of inconsistent data export, especially when concurrency is high on the source database
  • If both step 1 and step 2 are enabled, the export will be from the just made database copy. This will provide transactionally consistency. Once the export finishes, the database copy will be deleted; however, the database copy will still generate a single unit of cost
  • Step 3 is optional and only recommended to enable when testing the backup setup and also in an infrequent manner to balance the exported BACPAC files’ reliability and the cost effectiveness
  • Step 4 is optional and recommended to prevent unexpected catastrophic situations
Data flow of a typical restore operation
Correspondingly, a typical restore operation data flow will be depicted by the following diagram. Depending on different restore scenarios, some of the steps might be optional.
image002.png
The following table is to describe each of the steps.

Step Description
Step 1 (Optional) Copy the exported BACPAC from the on-premises secured storage location to Windows Azure Storage in data center B.
Step 2 Use Import/Export Service to import the BACPAC on Windows Azure Storage in data center B to the production logical database server in data center A. (Note: The targeted database name must be valid which means the corrupted database needs to be deleted or renamed for this import operation if it still exists.)


Notes & caveats:
  • Step 1 is not supported by the tool itself considering these are already many existing tools that can do this job. For example, the Azure Storage Explorer is a good candidate for this purpose

Last edited Nov 2, 2012 at 10:27 AM by jack4it, version 8

Comments

No comments yet.