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

Typical Scenarios

Following are the typical scenarios that can (or not) be supported.

Creating a backup/restore profile

A profile is the necessary input for a backup/restore operation. For example, where the source database is and what the necessary credentials are for the database. Profiles can be created by manually editing the profile data file; however, it would be strongly recommended to use the Admin Tool to do that. The Admin Tool will provide GUI experience to help create and edit a profile. Please refer to Usage for more information about this scenario. (Note: The credentials information is all encrypted based on unique information of the machine where the profile is created. The profile data cannot be reused by copying to another different machine for security consideration.)

Scheduling a periodical backup operation (NOT supported by the toolset itself)

Ops team can use any existing scheduling framework/tool to schedule a backup operation by using the Task Execution Tool. The toolset itself will not explicitly provide the schedule capability. Following is an example of using Task Scheduler to schedule a daily backup operation.


Triggering a backup operation

A backup operation can be triggered by an Ops scheduling agent or by on-demand executing the execution tool. The following is an example of this operation:

Backup a database by using a specified profile:
   ExecutionTool -p profile1 -b

Triggering a restore operation

A restore operation can only be triggered by on-demand running the execution tool. Following are examples of this operation:

Restore a database by using a specified profile and a specified bacpac file: (*1)
   ExecutionTool -p profile1 -r pocdb.2012-05-01-00-30-00.bacpac

Restore a database by using a specified profile, a specified bacpac file and also a new database name: (*1)
   ExecutionTool -p profile1 -r pocdb.2012-05-01-00-30-00.bacpac -rn NewDatabaseName

Monitoring an operation progress

When an operation is in progress, the Task Execution Tool’s console window can display progress information. The tool also emits detailed messages and well defined error codes when exceptions happen to Windows event log and a rolling text file. Ops can leverage existing tools like SCOM to get alerted on these events. The rolling file can be located in the log sub-folder of the toolset installation folder. The source name in the Window event log is SqlAzureDataProtector. Please refer to Troubleshoot for more information about the error codes and recommended troubleshooting actions.

Deleting BACPAC archives (retention)

During the execution of the backup operations, a retention process will be executed in parallel. All outdated archives will be deleted. For example, if the “Days to keep a bacpac file (Retention)” is configured to be as 90 days, then all archives that are created 90 days before this time the tool is running will be deleted both on Azure storage and on-premises location as the profile configured.

Last edited Nov 1, 2012 at 1:49 PM by jack4it, version 2


No comments yet.