Recover Microsoft SQL Server Databases

After you protect your Microsoft SQL Server databases, you can recover them from Cohesity DataProtect as a Service, to their original or a new location.

To recover protected Microsoft SQL Server databases:

  1. In DataProtect as a Service, go to Sources to set up your recovery task.

  2. Click on the Source name.

  3. Above the tree, select Show All > Protected.

  4. Use the filters, search box, and views to locate and select the SQL databases you need including MS MSQL standalone, FCI, and AG.

    You can also use Global Search to locate, filter, and select the objects you need. Click the Global Search box at the top or type slash (/) anywhere to start your search.

  5. Click Recover at the top to open the New Recovery form with the Latest snapshot (protection run).

    If you need to recover from an earlier snapshot, click the Edit icon to open the Recovery Point calendar. Click List to view the available recovery points by timestamp and click one.

    • Click Select Recovery Point.

    • Click Next: Recover Options to return to the form.

  6. Under Targets, select Recover as a new Database or Overwrite Original Database. If you choose:

    • Recover as a new Database, select a registered Microsoft SQL Server Instance or Restore to Original SQL Server Instance.

    • Overwrite Original Database, Cohesity will overwrite the original SQL Server instance. Note that this is a destructive action that cannot be undone.

  7. If necessary, under Database File Paths, you can:

    • Update the Database Files and Log Files paths.

    • Enter additional File Path Rules.

  8. Select your Recovery Options:

    • Rename. Choose whether to Bulk Rename with a Suffix or Rename Individual Objects.

    • WITH RECOVERY: By default, a Microsoft SQL Server restore WITH RECOVERY is performed. You can optionally toggle this off to perform a restore WITH NORECOVERY.

    • Keep CDC: Use this option to restore a backed-up database with the change data capture (CDC) enabled. By default, the Keep CDC switch is ON. If the backed-up database is not CDC enabled and the user tries to restore it with Keep CDC, the database will be restored without CDC.

    • Overwrite Alternate Database: Enable this option to recover the database by overwriting the existing database.

    • WITH Clause for Full/Incremental Restore: Specify the WITH clause that you want to use for the full/ incremental recovery.

    • WITH Clause for Log Restore: Specify the WITH clause that you want to use for the log recovery.

    • Capture Tail Logs: You can optionally choose to Capture tail logs. Tail logs capture records that have not yet been backed up. They are captured to ensure all transactions are backed up before restoring the database.

    • Task Name. Change the default name of the recovery task.

  9. Click Start Recovery.