Home > Storage > Data Storage Essentials > AppSync > Dell AppSync Integration with Microsoft SQL Server > Restoring from the copy
Before restoring a database, we recommend backing up the current transaction logs first. This action minimizes the amount of data that is lost. AppSync can back up the transaction logs before the restore by using the SQL Server Restore wizard.
Select Yes if you want AppSync to initiate a transaction log backup. Enter a location to copy the logs, and check other available options. Use one of the SQL Server management tools to restore, after the database has been restored. It allows for specific transaction logs to be replayed.
The Recovery, No Recovery, and Standby options are available when restoring the full database copy model. You may also restore from an AppSync SQL database copy when:
Again, be aware of the restore implications that may arise due to the storage layout of the databases. See the section titled Affected entities during restore for more detailed information.
Depending upon the recovery type selected, either Standby or Recovery, AppSync performs database recovery post completion of a storage level restore. If No Recovery is selected, the database is attached to the production instance but left in a nonoperational mode. Next, manual intervention is required to fully recover the database.
AppSync only supports the No Recovery mode during a restore of a SQL database if the copy was taken using Non-VDI or Crash Consistent backup types. Restoring with recovery or standby when the copy was taken using Non-VDI or Crash Consistent copy types is not supported.
The following table depicts different restore scenarios and their preferred recovery types.
Recovery Type |
Purpose |
Recovery |
Recovers the database after a restore. Additional backups cannot be restored post-recovery, that is transaction logs cannot be rolled forward. |
Standby |
Leaves the database in a standby state, where the database is available for limited read-only access. It rolls back uncommitted transactions but saves the undo actions in a standby file so that recovery results can be reverted. |
No Recovery |
Leaves the database in the restoring state and does not roll back the uncommitted transactions. This behavior allows the transaction log backups to be restored in the current recovery path. |