We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Yosemite Server Backup

Restoring Microsoft SQL Server

  • Last updated on

You can watch a short video about restoring a SQL Server database from a backup created with the Yosemite Server Backup SQL Server agent.

You should have already configured Yosemite Server Backup SQL Agent. See Configuring Backup for Microsoft SQL Server for more information. When restoring SQL Server databases, you must:

  1. Restore a full backup of the SQL Server database.
  2. Restore the logs in the order created.
  3. Follow special procedures when renaming databases (if you rename databases).

Any time Yosemite Server Backup returns an error message that is greater than 10000, a Microsoft SQL or Exchange error has occurred. Refer to your Microsoft documentation for more information as this is a Microsoft error code.

Restoring Microsoft SQL Server databases and transaction logs

 When recreating a database, you must first restore the whole database (created by a backup job running in full backup mode), and then you must restore the transaction logs in the order created and in separate jobs. No log can be skipped when restoring.

 For example, if you did a full backup on Monday and incremental backups each day Tuesday through Friday, you must run five separate jobs: one restoring the database from Monday’s full backup job and then four additional separate jobs restoring each transaction log in sequential order, beginning Tuesday and continuing with each log sequentially until Friday.

You do not have to follow these procedures when restoring databases backed up with full backup jobs. ( Full backup jobs back up the entire database, while Incremental and Differential jobs only back up the database logs.)

Last updated on