Skip to main content
Druva Documentation

Restore Microsoft SQL Server databases on VMware virtual machines

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Overview 

You can restore MS SQL databases from virtual machines where application-aware backup was done successfully. When you enable application-aware backup on VMware virtual machines, Druva Phoenix detects the applications inside the virtual machine and takes a backup of the data that the application generates. Since Druva Phoenix supports backup of Microsoft SQL Server databases inside VMs, it takes VSS snapshots of the SQL Server instances and uploads it to the Druva Cloud along with the virtual machine snapshot. 

To restore databases from application-aware backups you need a Windows staging virtual machine. It is used to attach and mount the disk(VMDK)  to selected SQL data for restoring to the destination virtual machine. See, Windows staging virtual machine for application aware database restores.

The following options are available to restore databases:

You can restore the database to an original or an alternate location. 

You can also restore database files. The files are downloaded to the specified server location. The database you need to restore must be manually attached to the target SQL server instance. 

Also, when you perform a full VM restore, of MS SQL virtual machines (application-aware), the restored databases will be application-consistent.

To know more about the restore workflow, see About VMware restores.

The following graphics illustrate the data flow using an example:

App_aware_story_files.png

App_aware_story_files.png

Before you beginEdit section

Perform a Database restore

When you want to restore the database to a virtual machine, you can choose a snapshot and Druva Phoenix restores the databases to a state that was backed up in the selected snapshot.  

The following video provides a quick demo of the process. 

 

Procedure

  1. Log in to the Phoenix Management Console
  2. Under Product & Services > Druva Phoenix, click VMware.
  3. Select your organization.
  4. The vCenter/ESXi host page appears that lists all the registered vCenter/hypervisors. 
  5. You can either select the registered vCenter from the list or select it from the vCenter/ESXi host list in the left navigation pane.
  6. In the left navigation pane, click Configured VMs.
  7. Select the MS SQL virtual machine you want to restore.
  8. Click Restore > MS SQL Restore.
  9. Select Database Restore.

    Database.png

  10. Select a snapshot. 
  11. Click on an instance name or expand it to see the databases inside it.
  12. Select the database you want to restore.
  13. Click Restore.

    Enter the restore target details.

    Restore to original VM: The database is restored to the original virtual machine from which it was backed up.

    Field Description
    Restore location
    Restore database as a copy The database is restored with an alternate name as rst_<original DB name>.
    Settings
    After Restore, maintain databases in

    Select an option to leave databases in one of the following modes: 

    Recovery Mode: In this mode, Druva Phoenix rolls back all the uncommitted transactions and keeps the database in the ready state. Druva Phoenix also ensures that all the data sets restored are consistent with the database, and reports errors in case of inconsistencies.

    Non Recovery Mode:  In this mode, Druva Phoenix does not roll back any uncommitted transactions. The database is not usable in this intermediate, non-recovered state. This mode is used for restoring a database backup and multiple transaction logs, or when multiple RESTORE statements are needed.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine.  You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores
    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.

    Restore to alternate VM: The database is restored to the selected alternate virtual machine.

    Field Description
    Restore location
    Destination VMware Setup Choose the vCenter/ESXi setup that hosts the virtual machine on which you want to restore the databases. Druva Phoenix lists the vCenter/ESXi setups that are registered with it.
    Destination Hypervisor

    Choose the ESXi host that hosts the virtual machine, if the destination VMware setup that you select is a vCenter.  

    If your destination VMware setup is a standalone ESXi host, the option for this field is the same as the Destination VMware Setup.

    Destination VM Choose the  virtual machine on which you want to restore the databases.
    SQL Instance Choose the SQL instance on the  target virtual machine.
    Druva Phoenix only validates the naming convention of the SQL Instance.
    Restore MDF, LDF, NDF files to

    You choose to restore the file types to a single location or each type to a different location.

    Settings
    Backup Proxy Pool Choose a backup proxy pool that can allocate a backup proxy to restore the virtual machine with databases. For optimal results, choose a backup proxy pool that can allocate a backup proxy that is locally connected to the hypervisor on which the virtual machine with databases should be restored.
    After Restore, maintain databases in

    Select an option to leave databases in one of the following modes: 

    Recovery Mode: In this mode, Druva Phoenix rolls back all the uncommitted transactions and keeps the database in the ready state. Druva Phoenix also ensures that all the data sets restored are consistent with the database, and reports errors in case of inconsistencies.

    Non Recovery Mode:  In this mode, Druva Phoenix does not roll back any uncommitted transactions. The database is not usable in this intermediate, non-recovered state. This mode is used for restoring a database backup and multiple transaction logs, or when multiple RESTORE statements are needed.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine. You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.

    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.

    Restore database files: This is similar to alternate location restore but only the database files are downloaded to the specified server location. The database you need to restore must be manually attached to the SQL server instance.

    Field Description
    Restore location  
    Destination VMware Setup Choose the vCenter/ESXi setup that hosts the virtual machine on which you want to restore the databases. Druva Phoenix lists the vCenter/ESXi setups that are registered with it.
    Destination Hypervisor

    Choose the ESXi host that hosts the virtual machine, if the destination VMware setup that you select is a vCenter.  

    If your destination VMware setup is a standalone ESXi host, the option for this field is the same as the Destination VMware Setup.

    Destination VM

    Choose the virtual machine on which you want to restore the databases.
    Restore MDF, LDF, NDF files to You choose to restore the file types to a single location or each type to a different location.
    Settings
    Backup Proxy Pool Choose a backup proxy pool that can allocate a backup proxy to restore the virtual machine with databases. For optimal results, choose a backup proxy pool that can allocate a backup proxy that is locally connected to the hypervisor on which the VM with databases should be restored.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine.  You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.

    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.
  14. The restore job is initiated. You can view the details from the Jobs page.  

Perform a Point in Time restore

Transaction logs are a tool to restore databases to a point in time in between database snapshots. Druva Phoenix can back up transaction logs in addition to the database snapshots so that you can get a tighter recovery time objective (RTO). When you enable SQL Server aware backup on VMware virtual machines, Druva Phoenix provides an option to enable transaction log backups. If you enable it, Druva Phoenix uses the virtual device interface (VDI) to back up and upload the transaction logs to Druva Cloud at specified intervals until the next full SQL Server aware virtual machine snapshot is backed up. Now, you can choose a point in time to restore databases. Druva Phoenix restores the databases to the transaction with a timestamp that is closest to the point in time that you choose.

Procedure

  1. Log in to the Phoenix Management Console
  2. Under Product & Services > Druva Phoenix, click VMware.
  3. Select your organization.
  4. The vCenter/ESXi host page appears that lists all the registered vCenter/hypervisors. 
  5. You can either select the registered vCenter from the list or select it from the vCenter/ESXi host list in the left navigation pane.
  6. In the left navigation pane, click Configured VMs.
  7. Select the virtual machine you want to restore.
  8. Click Restore > MS SQL Restore.
  9. Select Point in time Restore.

    Point_In_Time.png

  10. Specify a date and time to which you want Druva Phoenix to restore the databases. Databases will be restored to the last available committed transaction before the specified point in time. The backup proxy time zone is used. 
  11. Click Show Databases. All the available databases are displayed.
  12. Select the databases that you can restore.
  13. Click Restore.
  14. Enter the restore target details. 

    Restore to original VM: The database is restored to the original virtual machine from which it was backed up.

    Field Description
    Restore database as a copy The database is restored with an alternate name as rst_<original DB name>.
    Settings
    After Restore, maintain databases in

    Select an option to leave databases in one of the following modes: 

    Recovery Mode: In this mode, Druva Phoenix rolls back all the uncommitted transactions and keeps the database in the ready state. Druva Phoenix also ensures that all the data sets restored are consistent with the database, and reports errors in case of inconsistencies.

    Non Recovery Mode:  In this mode, Druva Phoenix does not roll back any uncommitted transactions. The database is not usable in this intermediate, non-recovered state. This mode is used for restoring a database backup and multiple transaction logs, or when multiple RESTORE statements are needed.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine.  You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.

    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.

    Restore to alternate VM: The database is restored to the selected alternate virtual machine.

    Field Description
    Restore location
    Destination VMware Setup Choose the vCenter/ESXi setup that hosts the virtual machine on which you want to restore the databases. Druva Phoenix lists the vCenter/ESXi setups that are registered with it.
    Destination Hypervisor

    If the destination VMware setup that you select is a Center, choose the ESXi host that hosts the virtual machine,

    If your destination VMware setup is a standalone ESXi host, the option for this field is the same as the Destination VMware Setup.

    Destination VM Choose the  virtual machine on which you want to restore the databases.
    SQL Instance Choose the SQL instance on the  target virtual machine.
    Druva Phoenix only validates the naming convention of the SQL Instance.
    Restore MDF, LDF, NDF files to

    You choose to restore the file types to a single location or each type to a different location.

    Settings  
    Backup Proxy Pool Choose a backup proxy pool that can allocate a backup proxy to restore the virtual machine with databases. For optimal results, choose a backup proxy pool that can allocate a backup proxy that is locally connected to the hypervisor on which the virtual machine with databases should be restored.
    After Restore, maintain databases in

    Select an option to leave databases in one of the following modes: 

    Recovery Mode: In this mode, Druva Phoenix rolls back all the uncommitted transactions and keeps the database in the ready state. Druva Phoenix also ensures that all the data sets restored are consistent with the database, and reports errors in case of inconsistencies.

    Non Recovery Mode:  In this mode, Druva Phoenix does not roll back any uncommitted transactions. The database is not usable in this intermediate, non-recovered state. This mode is used for restoring a database backup and multiple transaction logs, or when multiple RESTORE statements are needed.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine. You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.

    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.

    Restore database files: This is similar to alternate location restore but only the database files are downloaded to the specified server location. The database you need to restore must be manually attached to the SQL server instance.

    Field Description
    Restore location  
    Destination VMware Setup Choose the vCenter/ESXi setup that hosts the virtual machine on which you want to restore the databases. Druva Phoenix lists the vCenter/ESXi setups that are registered with it.
    Destination Hypervisor

    If the destination VMware setup that you select is a Center, choose the ESXi host that hosts the virtual machine,

    If your destination VMware setup is a standalone ESXi host, the option for this field is the same as the Destination VMware Setup.

    Destination VM Choose the virtual machine on which you want to restore the databases.
    Restore MDF, LDF, NDF files to

    You choose to restore the file types to a single location or each type to a different location. 

    Transaction log files are also uploaded to restore location.

    Settings
    Backup Proxy Pool Choose a backup proxy pool that can allocate a backup proxy to restore the virtual machine with databases. For optimal results, choose a backup proxy pool that can allocate a backup proxy that is locally connected to the hypervisor on which the virtual machine with databases should be restored.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine.  You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.

    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.
  15. The restore job is initiated. You can view the details from the Jobs page.  

Perform a Transaction Mark restore

If you enable transaction log backups for databases, Druva Phoenix can utilize transaction marks to identify specific transactions. At the time of restoring databases, you can choose transactions that are marked to restore databases up to the point when these transactions occurred.

Procedure

  1. Log in to the Phoenix Management Console
  2. Under Product & Services > Druva Phoenix, click VMware.
  3. Select your organization.
  4. The vCenter/ESXi host page appears that lists all the registered vCenter/hypervisors. 
  5. You can either select the registered vCenter from the list or select it from the vCenter/ESXi host list in the left navigation pane.
  6. In the left navigation pane, click Configured VMs.
  7. Select the virtual machine you want to restore.
  8. Click Restore > MS SQL Restore.
  9. Select Transaction Mark Restore.

    TransactionMark.png

  10. Select a transaction mark.
  11. Select a restore option. 
    1. Stop before mark: Select this option to exclude the marked transaction in the restore job.
    2. Stop at mark: Select this option to include the marked transaction in the restore job.
  12. Select the databases that you want to restore.
  13. Click Restore. 
  14. Enter the restore target details.

    Restore to original VM: The database is restored to the original virtual machine from which it was backed up.

    Field Description
    Restore location
    Restore database as a copy The database is restored with an alternate name as rst_<original DB name>.
    Settings
    After Restore, maintain databases in

    Select an option to leave databases in one of the following modes: 

    Recovery Mode: In this mode, Druva Phoenix rolls back all the uncommitted transactions and keeps the database in the ready state. Druva Phoenix also ensures that all the data sets restored are consistent with the database, and reports errors in case of inconsistencies.

    Non Recovery Mode:  In this mode, Druva Phoenix does not roll back any uncommitted transactions. The database is not usable in this intermediate, non-recovered state. This mode is used for restoring a database backup and multiple transaction logs, or when multiple RESTORE statements are needed.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine.  You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.
    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.

    Restore to alternate VM: Database is restored to the selected alternate virtual machine.

    Field Description
    Restore location
    Destination VMware Setup Choose the vCenter/ESXi setup that hosts the virtual machine on which you want to restore the databases. Druva Phoenix lists the vCenter/ESXi setups that are registered with it.
    Destination Hypervisor

    If the destination VMware setup that you select is a Center, choose the ESXi host that hosts the virtual machine,

    If your destination VMware setup is a standalone ESXi host, the option for this field is the same as the Destination VMware Setup.

    Destination VM Choose the  virtual machine on which you want to restore the databases.
    SQL Instance Choose the SQL instance on the  target virtual machine.
    Druva Phoenix only validates the naming convention of the SQL Instance.
    Settings
    Backup Proxy Pool Choose a backup proxy pool that can allocate a backup proxy to restore the virtual machine with databases. For optimal results, choose a backup proxy pool that can allocate a backup proxy that is locally connected to the hypervisor on which the virtual machine with databases should be restored.
    After Restore, maintain databases in

    Select an option to leave databases in one of the following modes: 

    Recovery Mode: In this mode, Druva Phoenix rolls back all the uncommitted transactions and keeps the database in the ready state. Druva Phoenix also ensures that all the data sets restored are consistent with the database, and reports errors in case of inconsistencies.

    Non Recovery Mode:  In this mode, Druva Phoenix does not roll back any uncommitted transactions. The database is not usable in this intermediate, non-recovered state. This mode is used for restoring a database backup and multiple transaction logs, or when multiple RESTORE statements are needed.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine.  You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.

    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.

    Restore database files: This is similar to alternate location restore but only the database files are downloaded to the specified server location. The database you need to restore must be manually attached to the SQL server instance.

    Field Description
    Restore location
    Destination VMware Setup Choose the vCenter/ESXi setup that hosts the virtual machine on which you want to restore the databases. Druva Phoenix lists the vCenter/ESXi setups that are registered with it.
    Destination Hypervisor

    Choose the ESXi host that hosts the virtual machine, if the destination VMware setup that you select is a vCenter.  

    If your destination VMware setup is a standalone ESXi host, the option for this field is the same as the Destination VMware Setup.

    Destination VM Choose the virtual machine on which you want to restore the databases.
    Restore MDF, LDF, NDF files to

    You choose to restore the file types to a single location or each type to a different location. 

    Transaction log files are also uploaded to restore location.

    Settings
    Backup Proxy Pool Choose a backup proxy pool that can allocate a backup proxy to restore the virtual machine with databases. For optimal results, choose a backup proxy pool that can allocate a backup proxy that is locally connected to the hypervisor on which the VM with databases should be restored.
    Staging VM

    A staging virtual machine is used to mount the selected SQL data for restoring to the target virtual machine. You can also use the destination server for staging. See, Windows staging virtual machine for application aware database restores.
    Provide the following details: 

    Hypervisor: Select the ESXi host of the staging virtual machine. 

    VM: You can select a staging virtual machine with or without credentials already assigned.

    When you select a staging virtual machine without credentials, you can select credentials saved in the credential store or provide custom credentials. 

    To manage virtual machine credentials, go to All Virtual Machines > Manage Credentials.
  15. The restore job is initiated. You can view the details from the Jobs page.  
  • Was this article helpful?