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

 

At the time of configuring virtual machines for backup, you were asked if you wanted to enable application-aware processing. Phoenix supports SQL Server application-aware backups, it provides the following options to restore databases:

  • Database restore: Restore SQL Server databases using snapshots.
  • Point In Time restore: Restore SQL Server databases to a point in time using transaction logs.
  • Transaction Mark restore: Restore SQL Server databases using transaction marks.

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

The following video provides a quick process overview.

Prerequisites

  • Before you proceed with the restore, ensure you have reviewed the prerequisites and considerations
  • For the list of supported disks, partitions, and files, see Support matrix.
  • You must have write permission for the target location, where you want to restore the files. 

Procedure 

  1. Log in to the Phoenix Management Console
  2. Under Product & Services > 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 the type of restore you want to perform.
    • Database Restore: Restore databases from a snapshot.
      1. Select a snapshot. To know more about restoring cold snapshots, see Restoration of cold-tier data
      2. Click on an instance name or expand it to see the databases inside it. 
      3. Select the database you want to restore.
        Restore_MS_database.png
      4. Click Restore and proceed to step 10.
    • Point in Time Restore: Restore databases to a point in time.
      1. Specify a date and time to which you want 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. 
      2. Click Show Databases. All the available databases are displayed.
      3. Select the databases that you can restore.
        Restore_MS_PIT.png
      4. Click Restore and proceed to step 10.
    • Transaction Mark Restore: Select a transaction mark and choose one of the following options:
      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.
      3. Select the databases that you want to restore.
        Restore_MS_TM.png
      4. Click Restore and proceed to step 10.
  10. Enter the target details:
Field Description
Destination VMware Setup Choose the vCenter/ESXi setup that hosts the virtual machine on which you want to restore the databases. Phoenix lists the vCenter/ESXi setups that are registered with it. 
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. 
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 Datastore Choose the datastore of the virtual machine where you want to restore the virtual machine databases. 
Compute Resource Choose the host, cluster, or resource pool for the virtual machine where you want to restore the databases. You cannot select a datacenter or a folder. 

This option is not available if you are restoring databases with a virtual machine on a standalone ESXi host. 
Folder Choose a folder under the data center hierarchy where you want to restore the virtual machine and the databases. 

This option is not available if you are restoring a virtual machine to a standalone ESXi host.

Network

Choose a network setting available at the destination hypervisor.

Only for on-premises, If a network adapter was not attached to the virtual machine at the time of backup, Phoenix will attach the VMXNET3 or VMXNET2  type adapter and restore the virtual machine with the selected network setting. 

If a network adapter was attached to the virtual machine at the time of backup, Phoenix will restore the virtual machine with the backed up network adapter and selected network setting. 

If multiple network adapters were attached to the virtual machine at the time of backup, Phoenix will restore the virtual machine with all the adapters and selected network setting.

For troubleshooting network issues, see Troubleshooting

IP address

If the source SQL virtual machine has a static IP, ensure that a different static IP is set to ensure that the recovered virtual machine doesn't have a conflict with the original SQL virtual machine.

 

Select the Assign static IP to the destination VM checkbox and provide the details for the recovered VM.

VM Guest OS Credentials

Choose guest OS credentials to let the backup proxy run the guest OS process to restore Microsoft SQL Server databases inside the virtual machine. You can choose a credential that is already stored with Phoenix or you can choose the Use Custom Credentials option to provide new credentials. If the credential uses a domain, enter the username as domain\username. For example,  DruvaCorp\JohnDoe.  

After Restore, leave databases in 

(Not applicable for Transaction Mark Restore)

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

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

Nonrecovery mode:  In this mode, 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.

  1. Click Finish to run the restore job with the specified settings.

 

 

 

 

  • Was this article helpful?