SQL Virtual Restore 2.3
Rapidly mount live, fully functional databases direct from backups

Frequently asked questions
How can I use SQL Virtual Restore?
SQL Virtual Restore is fully scriptable with T-SQL's RESTORE DATABASE and RESTORE LOG commands, or you can use the Restore Wizard to access your backups in just four steps.
What are the requirements?
Please see the requirements page. If you have any questions, please don't hesitate to email us. We would be more than happy to help.
Does SQL Virtual Restore support all versions of Microsoft SQL Server?
SQL Virtual Restore is supported for Microsoft SQL Server 2000 (SP 3 or later), SQL Server 2005, SQL Server 2008 and SQL Server 2008 R2.
Which backup types are supported?
Full, differential and transaction log backups created with native SQL Server, SQL Backup Pro (version 6.xx), and SQL HyperBac are all supported by SQL Virtual Restore. Decryption is supported for all backup types.
Why SQL Virtual Restore?
SQL Virtual Restore presents a quick and easy way to mount your backup as a live, fully functional database without the time or space needed for a physical restore. The time it takes to mount your backup is typically on par with a RESTORE VERIFYONLY operation, but with all the benefits a full restore would bring you.
SQL Virtual Restore, like all other products powered by HyperBac, is installed at the system layer with a single component on the target server. No hooks or links into your SQL Server instances and no extended stored procedures are required, providing a zero-touch deployment.
SQL Virtual Restore is the only third-party virtual database solution on the market that instructs SQL Server to interpret your MDF and LDF files. This means that there will never be any conflicts between how SQL Server and SQL Virtual Restore interpret your backup file as SQL Virtual Restore only handles the mounting of your backup file, and not the interpretation of your data.
Another advantage of SQL Virtual Restore is that it takes into account all rollback and other transactions in the backup, making the mounted database ACID compliant and reinforcing the referential integrity of your data.
How can I use SQL Virtual Restore to verify backups?
Using the SQL Virtual Restore Wizard, you can run DBCC CHECKDB against a database as part of the restore process. The options to run DBCC CHECKDB and to drop the database immediately afterward are included in Step 3 of the Wizard.
What happens if the SQL Virtual Restore Wizard finds a problem with my database?
DBCC CHECKDB against it, you will be notified in the UI. Your database won't be dropped after the integrity check, so you can access it immediately and investigate further.
How does object level recovery with SQL Virtual Restore work?
Simply point SQL Virtual Restore at your backup file to run point-in-time virtual restore operations. You will have access to full, transactionally consistent data, with all objects visible and available.
Will my restore operations with SQL Virtual Restore take less time?
Yes. Virtually restoring a database backup is much faster than a regular database restore operation. The time it takes is typically on par with a RESTORE VERIFYONLY operation.
Will a database restored with SQL Virtual Restore take up less space than a database following a regular physical restore?
Yes. A mounted database carries a near-zero additional storage footprint.
How can I access my data?
All data and objects are fully accessible using any data access method – SQL Server Management Studio, ADO.NET and Query Analyzer.
How is SQL Virtual Restore licensed?
SQL Virtual Restore is licensed per server. 'Server' in this context refers to a distinct system running a Windows operating system with SQL Server. You can attach a backup as a live database to the licensed SQL Server.
Try a 14-day fully functional free trial of SQL Virtual Restore.


