Public facing KB can be found here:
How to Restore SQL Data in AppAssure 5
You need to recover a SQL database or table from AppAssure 5 recovery points
Complete the following steps.
1. Launch the AppAssure 5 Core Console.
2. Click on the agent machine and go to the Recovery Points tab.
3. Expand the desired recovery point from which you wish to restore by clicking the arrow beside it.
4. Click Mount.
• In the Mount dialog box, specify the path to mount this recovery point. This will be the location to access the data in Windows Explorer.
• In the Mount dialog box, specify which volumes to mount. You must choose at least one volume. If you have multiple volumes you can mount all volumes at the same time.
• In the Mount dialog box, choose whether to mount the recovery point at read only or writeable.
Read only truncating previous writes
Writeable – Allows you to make changes to the recovery point (i.e. change permissions on files or folders).
• In the Mount dialog box, if you would like to mount the recovery point as a network share you can do this as well. Enter the share name and specify which users/groups have access (optional).
5. After the required fields have been filled in the Mount dialog box, click Mount.
6. The Recovery Points tab will automatically return until the mount begins, at which time a ‘Monitor Task’ window will display to view the progress of the mounting job.
• Users can also view mounting progress from the events tab.
7. Once the mount is completed, open windows explorer and navigate to the mount path that was specified in Step 4.
• You can also locate all current mounts from Core>Tools>Mounts. This displays all mounted recovery points in the system at the given time and the location where they are mounted to.
8. Use the SQL Server Management Studio application to attach the database, then copy over any desired data.
- To attach the database:
1. Open and log into the SQL Server Management Studio application.
2. Attach the database by pointing to the mounted recovery point volume(s).
If the logs are in another location other than the same as the databases, make sure to correct the “Attach dialog” path to the correct location for the respective log files.
3. After the database is attached, use any of the typical SQL tools to retrieve the data.
- To retrieve data using SQL commands:
• After mounting and attaching the database, do one of the following:
o Copy the table or rows back to the original database by using either INSERT, BCP (Bulk Copy Utility), or SELECT INTO.
o Right-click on the original database name, select Tasks, and then click Import Data.
Point to the attached database or recovery point on the AppAssure Core.
9. Once data has been recovered, it is a good idea to dismount the recovery point. This can be accomplished from the Core>Tools>Mounts page by clicking ‘Dismount’ on the mounted recovery point.
• Note: stopping the AppAssure Core Service will dismount all active mounted recovery points.
Useful SQL Commands:
NOTE: The following solution discusses using the SQL commands INSERT, BCP, and SELECT INTO. It does not recommend using the command DTS.
See the follow SQL command descriptions for use when retrieving data using the SQL Server Management Studio application.
Use INSERT to retrieve a subset of rows or only a small table. INSERT requires the most transaction log space when inserting the rows back in to the original database. If there are many indexes on the original table this increases the logging for the INSERT statement.
NOTE: You may want to drop the indexes before performing the insert, and then re-create the indexes.
Consider using the BCP (also called Bulk Copy) utility when you must retrieve a whole table or if the table size is large.
• If the table does not already exist, generate a script of the table if there is not already one, and then re-create the table.
• Use the BCP utility to copy the table data (rows) from the restored database to a text file, and then from the text file to the original database. For more information about how to use the BCP utility, see the “BCP Utility” topic in SQL Server Books Online.
NOTE: If performing a “minimally logged” or “nonlogged” bulk copy, perform a full database backup of the original database after completing the BCP. For more information, see the “Logged and Minimally Logged Bulk Copy Operations” topic in SQL Server 2000 Books Online, and see the “Logged and Nonlogged Bulk Copy Operations” topic in SQL Server 7.0 Books Online.
If the table was deleted, select the table from the restored database to the original database by using SELECT INTO. You do not have to create the table first with this method. SELECT INTO creates the table and copies the table data.
CAUTION: With SQL Server 2000 or SQL Server 2005, do not use the select into/bulkcopy option if it is not required to select into a permanent table. The amount of logging and whether a full database backup of the original database is needed after the SELECT INTO command depends on the recovery model of the original database. See the “SELECT Clause” topic in SQL Server Books Online and the subtopics “INTO Clause” and “Using Recovery Models”.
NOTE: Because retrieving data that is not consistent with the current state of the database, the referential integrity may be broken. The user may experience constraint and key errors when trying to insert the data back in to the database. Take appropriate steps to address any referential integrity issues.
NOTE: If the original table was lost, you must re-create any indexes, full-text indexes, triggers, and constraints.
Run the DBCC CHECKTABLE Transact-SQL reference on the new table to verify the integrity of the data. For more information, see the “DBCC CHECKTABLE” topic in SQL Server Books Online.