Home > Storage > Data Storage Essentials > AppSync > Dell AppSync Integration with Microsoft SQL Server > Back up of transaction logs
It is highly recommended to back up transaction logs before performing a restore. Every SQL Server database has a transaction log that records all transactions, and modifications for each transaction. Optionally, choose to backup transaction logs before a restore in AppSync by specifying a location, including specifying a file prefix and an extension. This backup can be used to recover the database in case the database is restored with either the Norecovery or Standby options. If the database is damaged, select the Database is damaged option to facilitate a tail log backup. See the Restoring damaged databases section.
Optionally, choose to truncate the transaction logs and overwrite existing backup files. If the database is damaged, these options are not available.
The following table explains the UI combination options that are selected to achieve the correct BACKUP LOG command as needed, for taking transaction log backups during restore.
Database is Damaged |
Truncate the transaction logs |
Overwrite existing backup files |
Sample BACKUP LOG command |
Checked |
N/A- Not Selectable |
N/A- Not Selectable |
WITH NO_TRUNCATE/WITH CONTINUE_AFTER_ERROR |
N/A- Not Selectable |
Checked |
Cleared |
None |
N/A- Not Selectable |
Checked |
Checked |
WITH INIT, SKIP
|
N/A- Not Selectable |
Cleared |
Checked |
WITH NO_TRUNCATE, INIT, SKIP |
If you choose not to back up the transaction logs before the restore operation, other recovery options such as Leave databases ready to use (RESTORE WITH RECOVERY) and Overwrite the existing databases (WITH REPLACE) appear in the user interface. The latter should be selected if intending to erase and replace the existing database with the backed up or restored data. It must be done carefully, otherwise, it may result in data loss or corruption.