The Microsoft SQL Server mount and migrate feature is available for recovery of thefollowing:

• SQL databases—stand-alone and failover cluster
• Consistency group of SQL databases
• SQL instances
• SQL AAGs

SQL Server mount and migrate is a three step process that includes thefollowing:

1. Mount or restore: Perform either an application aware mount or a mountand migrate restore. For more information,seeMount or restore
2. Migrate: Configure the migration schedule for an image fromtheActive Mounts page. Image migration follows the scheduledefined and migrations jobs are run repeatedly at the frequencyspecified. For more information,seeConfigure migration schedule

3. Finalize: Initiate the last and final stage of the image migrationprocess. For more information, seeFinalize

   Note: When working with a SQL availability group, the finalize step cannot be performed on a database in a group that is on the primary node. To finalize migration on the primary node, a failover to another node must be performed first, that changes the node to be a secondary node.

For instructions on how to perform an application aware mountof SQL databases,seeMount a SQL Server databases as virtual applications.For instructions on performing a mount and migrate restore,seeMount and migrate restore.

Multiple restores can be performed concurrently for a parent applicationlike SQL instance, SQL availability group, or SQL consistency group, but theyhave to be on different databases.

Mount and migrate restore

To perform a mount and migrate restore, follow these steps:

1. From the Backup and DR Service management console, clickApp Manager and selectApplications from the drop-down menu.

   TheApplications page opens.

2. Select the SQL application with the image that you want to restoreusing mount and migrate capability. Then selectAccess from thedrop-down list at the bottom of theApplications page.

   TheAccess page opens listing captured images appear in the timeline rampview. For more information on the view, seeAccess the timeline ramp view of an image

   Note: Background differentiates snapshot images containing a SQL database with archive log files, and also illustrates the restore range time period for the logs.

3. Select the image, then selectRestore from the list of operations.TheRestore page opens.

4. Select theMount and Migrate option.

5. If the selected database does not have logs, theRestore pagedoes not show roll forward options.

6. If the source application is protected by a snapshot policy that hasenabled database log backups, and logs are available with the image,you can use the logs to roll forward to a specific point in time by changingthese options in theRoll Forward Time section:

   • The date field contains all possible dates that the database can berolled forward to—through the application of database transactionlogs. Select the date you want the database to be rolled forward to.
   • The time field contains a slider showing all possible times on theselected date that the database can be rolled forward to. If you selectthe latest possible date and then move the slider to the right mostposition, the restore job applies to all available logs. If you selectthe earliest possible date and move the slider to the left most position,the restore job applies no logs.
   • You can specify to roll forward using eitherUser Time orHost Time.User Time is relative to the local time of the current user.Host Time is relative to the system that hosts the data to be restored.

   When using an OnVault image as the source, the log range is visible whenlogs are available in either the OnVault pool for the source image or in thesnapshot pool on the backup/recovery appliance for the selected target host.When dealing with imported OnVault images, this might result in differentranges of available logs based on the target host, or it might result inno roll forward time option appearing at all.

7. InLabel, optionally enter a name. TheLabel is pre-populatedwith the textRestore - M&M - 04 June, 2019 06:52:29pm, using date andcurrent time, so if you don't update the property, the default value isused.

   You are not be able to change the default selection forRestore with Recovery, as the property is disabled.

8. ForSQL Server Instance Name, select the targetSQL Server Instance.The new database will be managed by the instance you specify.Similarly, forConsistency Groups, enter the name of the targetConsistency Group in theEnter Consistency Group Name field.

9. InSQL Server Database Name, enter the new SQL Server databaseto be provisioned.

10. ForSQL Instances and Consistency Groups, select the databases to beincluded in the restore job.TheRestore with Recovery option is enabled by default and youcannot disable it.

11. InUsername, enter the name of the username for database provisioning.It is needed only when the account running the Backup and DR agentdoes not have the privileges to apply transaction logs or to dispatch adatabase.

12. InPassword, enter the password for the user you specified in step 10.

13. ClickSubmit. A warning dialog opens. Read it and then enterDATA LOSS to confirm.

    The selected databases are taken offline. A mount is performed toprovide fast access to the databases with the selected point in time.After the mount completes, the migrate option becomes available as anaction on the resulting active image.

    Note: If the target is a VM, and the mount mode is not pRDM, the user will see the warning text after theData Loss message: Warning: pRDM is not selected. This means that while the databases are running from the mount, backups can consume a full copy's worth of space in the snapshot pool, plus the changed-block changes. When the migrate begins, backups can stop until the migration is finalized.

Configure migration schedule

You can configure the migration schedule from theActive mounts page. Anyapplication aware mounted image can be migrated at a later time. Images thatwere restoredusing the mount and migrate optioncan also be migrated. Mounted images show the image state ofMountedand images that were restored using the mount and migrate capability havethe image state ofRestore (Mounted).

For instructions on how to configure migration schedule,seeConfigure migration schedule for mount and migrate.Image migration follows the schedule defined and migrationsjobs are run repeatedly at the frequency specified.

Once migration starts, the image state changes toMigrating—in casethe image is an application aware mount—orRestore (Migrating&mdash);if the image was created using theRestore Mount and Migration option.The image is inMigrating state until you initiated finalize migration instep three, when the last migration that is performed.

Finalize

Finalize migration initiates the last and final stage of the image migrationprocess. Once you begin the finalize stage, you cannot cancel the migrationprocess.

Before you initiate the finalize stage, complete the following:

• change the migration frequency specified for the image
• perform an on-demand migration job
• cancel image migration
• cancel image restore

To begin the finalize stage, follow these steps:

1. Go to theActive Mounts page and filter byImage State ofMigrating orRestore (Migrating).
2. Select the image and then selectFinalize Restorefrom the drop-down menu at the bottom of the page.
3. You see a confirmation message. Read it carefully and then clickProceed.The databases are taken offline during final migration and then brought backup again on the target production database.

4. Go toMonitor & Jobs, and filter byFinalize job type.Locate the job and view the job details.

   You can also view images with theFinalize image state in theActive Mounts page.

Change migration frequency

To change the migration schedule, follow these steps:

1. Select an active image withImage State ofMounted orRestore Mounted.

2. SelectMigrate from the drop-down menu at the bottom of the page.

   TheUpdate Migrate Frequency page opens.

3. ForFrequency, use the slider to define the frequency with whichto schedule migrate jobs from one to 24 hours.

4. ForCopy Thread Count, specify the number of parallel copy threadsto use, per disk volume, during the migration. The default value is four.

5. For mounted images, update theFile Locations section using instructionsinConfigure migration schedule for mount and migrate.

6. ClickSubmit. You see a success message.

7. ClickOkay to close the message and return to theActive Mounts page.

Run an on-demand migration job

Once you have configured the migration schedule, image migration follows theschedule you specified and migration jobs run at the frequency you specified.However, you can run the migration on demand if needed.

To run an on-demand image migration, complete the following:

1. Select an active image with anImage State ofMigrating.
2. SelectRun Migration Job Now from the drop-down menu.

Cancel a migration job

To cancel an image migration, follow these steps:

1. Select an active image with anImage State ofMigrating.
2. SelectCancel Migration from the drop-down menu.
3. At the warning message, clickProceed to cancel. Canceling stops themigration and deletes all data that was copied over during previousmigrations.

Cancel image restore

To cancel an image restore, follow these steps:

1. Go to theActive Mounts page and filter by theImage State ofRestore (Migrating).
2. Select the image and then selectCancel Restore from thedrop-down menu at the bottom of the page.
3. ClickProceed to cancel. This cancels all running and scheduled migrationjobs for the image, deletes all data copied by prior migrations, takes thedatabases offline, and finally performs an unmount and delete of the mounteddatabases.

The Backup and DR Microsoft SQL Server DBA guide

This page is one in a series of pages specific to protecting and recoveringMicrosoft SQL Server databases with Backup and DR.You can find additional information at:

• Backup and DR for Microsoft SQL Server Databases
• Prepare SQL Server databases for Backup and DR Service
• Add a SQL Server database host and discover databases
• Configure backup plans for Microsoft SQL Server instances and databases
• Application details and settings for Microsoft SQL Server instances and databases
• Mount a SQL Server database
• Mount databases into SQL Always On Availability Groups
• Manage an active mount
• Migrate a SQL Server database
• Clone SQL Server databases
• Recover SQL Server backups