It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Backup

How do I restore a SQL database with the Barracuda Backup Service?

  • Type: Knowledgebase
  • Date changed: 2 years ago

Solution #00004682



Applies to Barracuda Backup Service.



When you restore a Microsoft SQL database you must perform the restores in the order in which they were created.


  • Restore a full backup of the SQL Server database


  • Restore the logs in the order in which they were created
  • The following requirements and considerations apply to all SQL database recovery operations:

  • The entire database is recovered with each recovery operation. Barracuda does not support granular recovery of SQL database records.
  • A database must be recovered to an SQL instance that is the same version or later than that of the original SQL instance. Databases cannot be recovered to an older SQL version.
  • Any existing database of the same name that resides on the recovery target is overwritten during the recovery operation (even if you specify a different path). To retain the original database, you must modify the recovery database name in the Restore dialog.

The following sections detail the requirements and considerations for different types of recovery operations.


Restoring a SQL User Databases

To restore a SQL Server user database, begin by restoring the most recent full back up of the database, followed by all the transaction logs. When a database is restored, if the database does not exist in the location where it was backed up, it will be recreated. Each of the transaction log backups must be restored separately and none of the transaction log back ups can be skipped.
For example, if you did a Full backup on Monday and Log backups each day Tuesday through Friday, you would need to run five separate restores: one restoring the database from Monday?s full backup and then four additional restores which restore each of the transaction log backups in sequential order, beginning Tuesday and continuing with each log backup sequentially until Friday. You do not have to follow these procedures when restoring databases backed up with Smart backup.


Restoring a SQL Master Database


A damaged master database is evident by the failure of the SQL Server to start, by segmentation faults or by input/output errors. The procedure used to recover a damaged master database is different from the procedure used to recover user databases. If the master database becomes unusable, it must be restored from a previous SQL Dump or back up. All changes made to the master database after the last backup or dump are lost when the dump is reloaded and therefore must be reapplied. It is strongly recommended that the master database be backed up each time it is changed.


Recovering a damaged master database

  1. Verify that the Barracuda Backup Agent is installed on the local machine.
  2. Stop the SQL Server Services using the SQL Server Enterprise Manager.
  3. Rebuild the master database. Refer to MSDN for detailed procedures for your version of SQL.
  4. Initiate Single User Restore Mode on the SQL database by entering the following from a command prompt. Leave the window open after executing the command.

    CD \program files\microsoft sql server\<sql version>\mssql\binn

    sqlservr -c -m (SQL 7)

    sqlservr -c -m -s %<Named Instance>% (SQL 8)

  5. After you are finished with the restore, remove the -m before you restart the server instance in the normal multi-user mode.

    CD \program files\microsoft sql server\<sql version>\mssql\binn

    sqlservr (SQL 7)

    sqlservr -s %<Named Instance>% (SQL 8)

  6. If login IDs or devices have been added to or dropped from the master database since the last backup, those changes must be reapplied. Restart the server and reapply the changes manually or from saved batch files.
  7. If any databases have been created, expanded or shrunk since the last dump of the master, those databases must be dropped and then restored. Refer to MSDN for detailed procedures for your version of SQL.
  8. Close the command prompt.
  9. Restart the SQL Service using SQL Enterprise Manager.


During a rebuild of the master database, the set up program drops and re-creates the msdb database, which results in a loss of all scheduling information. This includes tasks that you schedule from the Task Scheduling window, automatic backups scheduled from the Database Backup/Restore window and all replication tasks. As a result, you may want to restore the msdb

database from your last full backup.


Restoring a SQL SharePoint Database


Before you execute a restore of Microsoft SharePoint Services and databases:

  • Start the Windows SharePoint Services VSS Writer service
  • Start the Volume Shadow Copy service
  • Shutdown any Web applications whose content is being restored.


Additional directions can be found here:

Link to this page: