A SQL Server Protection Plan backs up all files for each SQL Server database selected. This page discusses the process of restoring and recovering SQL Server databases.


In addition to restoring an individual file or a group of files, the software can restore the entire protection plan. Generally, you would only need to restore an entire protection plan in the case of moving files, accidental deletion, or restoring a system after a disk change or crash.


This software protects Microsoft SQL using the SQL Writer for VSS included in newer versions of Windows. When a database is backed up by the software the VSS writer is engaged and the files that compose the database are backed up in an open state (while databases are mounted). New transactions and transaction logs are deferred in memory while the existing files are backed up. The databases are left in an open state.


The software will restore database files to a location of your choosing. After restoring, you will need to reattach the database to the Database Server. Whether the goal is to replace an existing damaged database, or simply to recover data from a table or tables will determine if you should move the restored files to the original location of the database files, or leave them in their restored location. The software will never restore the database files back to their original location due to the potential of corrupting running databases.


The process of restoring a protection plan begins with finding the archive time for the plan you want to restore. Refer to Finding a Plan's Archive Times.


Select the archive time you want to restore and the "Restore" button at the bottom right of the screen will become active. Click "Restore" and a "Storage Group Restore" dialog will appear.


After restoring, you simply need to re-attach the database files to the SQL instance. Please refer to http://msdn.microsoft.com/en-us/library/ms190209.aspx for information on attaching databases to SQL instances.