Search Wiki:
Project Description
This GUI tool will help users determine whether the SQLVDI.DLL is functioning correctly and where you need to concentrate your troubleshooting efforts in case of SQL backup/restore operations are failing due to VDI errors.

This GUI tool works in two steps:
1. Captures the information regarding the backup location, SQL Server name and database name.
2. The it uses a modified version of simple.exe available as part of the VDI Sample applications available for download to perform the backup/restore of SQL databases. The modified EXE is called SQLBackupS.exe which gets copied to your %tempdir% as SQLBackupS.exe.

For details on how to use this utility, read the following blog post.

The modifications for the existing code of simple.exe is mentioned under the following blog post.

----
SQL VDI UI
----
Simulate VDI Backup/Restore

The input parameters for this tab are as follows:
1. Backup Location: This is the location where the database will be backed up to for backup operation OR the location from which the database will be restored along with the filename. This can be a local disk or a UNC path. Known issue: Currently file path with a space is not accepted. This will be addressed in a later release.
eg:
For backup operation: C:\Backups\ or \\backups\master\
For restore operation: C:\Backups\SQLBackupSim.BAK or \\backups\master\SQLBackupSim.BAK

If you just specify the backup folder, then the application will look for the SQLBackupSim.BAK file present in that location and return a File Not Found error if it doesn't exist.

2. SQL Server Name: The name of the SQL Server on which the operation (backup\restore) needs to be performed. This can be selected from the drop-down box. MSSQLSERVER is the default instance. The tool enumerates all the instances installed on the box.

3. Database name: Name of the database on which the backup\restore operation is to be performed. This can be selected using the "Select a Database" drop-down box.

4. Backup/Restore: Selecting the appropriate option (Backup/Restore) using the "Select an operation" drop-down box.

5. Use 64-bit process: For 64-bit boxes, you have the option of testing both 32-bit and 64-bit version of SQLVDI.DLL. The default is to check the functionality of the 32-bit DLL. To check the same for the 64-bit DLL, enable the check box.


Validate VDI Environment
This tab lets you validate the VDI DLL version and permission related checks that are required for a VDI backup to be successful. It will check the common known issues with VDI and report it in the text box below. You need to select the appropriate instance to perform the validation against using the "Select SQL Server Instance Name" drop-down box.

FAQs


1. What is the text output that is provided in the text box below the verbose output?
When a backup/restore operation is performed by the SQL Backup Simulator, it prints the verbose output to help troubleshoot in case of any failures.

2. The START button is disabled!
Select the operation using the drop down list for Backup/Restore option. For subsequent operations, reselect the operation type using the drop-down list.

3. What is the name of the backup file?
The name of the backup file is SQLBackupSim.BAK.

4. What is the version of .NET Framework needed to run this tool?
This tool will work perfectly in machines having .NET Framework 3.5 and above.

5. Application crashes when attempting to take a backup of a SQL instance running in WOW (32-bit SQL on 64-bit server) using the 32-bit version of SQLVDI.DLL?
This is a known issue with the tool. We are looking at addressing this in the next version.

For bugs/design change requests, please use the Issue Tracker to file your requests. In case you have any questions, then send it across as a tweet to banerjeeamit or start a new discussion using the dicussions tab.
Last edited Nov 7 2010 at 7:07 PM  by amitban, version 9
Comments
agiotti wrote  Oct 29 2010 at 2:23 PM  
Great tool. However, the following options would also be helpful.
1. Perform TLOG backups
2. Perform RESTORE WITH VERIFY

We currently use Quest Light Speed and experiencing the following error conditions performing a RESTOER WITH VERIFYONLY.
BackupMedium::ReportIoError: read failure on backup device 'VDI_EB9CF096-6723-4CA2-AE80-02BAEE17B741_0'. Operating system error 1223(The operation was canceled by the user.).

yeohray wrote  Nov 2 2010 at 3:33 PM  
Useful troubleshooting tool, but be careful with the database you choose to back up. I don't see the COPY_ONLY option being used in the backup, so the test backup is going to be the base for any future differential backups, at least until the next full non-COPY_ONLY database backup. On my system, I don't see any physical file generated, so those differential backups are going to be useless.

Luckily, there's no option to perform TLOG backups, otherwise users may unknowingly break their log chain.

amitban wrote  Nov 3 2010 at 4:35 PM  
@agiotti: Looks like LiteSpeed is cancelling the operation due to some error condition. Are you able to backup a test database using Backup Simulator successfully. If yes, then you need to enable LiteSpeed logging and find out if the LiteSpeed logs provide further insight into the cause.
@yeohray: Good point. I shall look into the option of incoroporating the COPY_ONLY option in the next update for the tool.

amitban wrote  Feb 8 2011 at 7:46 PM  
We have added the COPY_ONLY option in the v1.2 version of the tool.

amitban wrote  Jun 17 2011 at 11:22 PM  
Explanation of the new features for v2.0 are available @ http://troubleshootingsql.com/2011/06/18/sql-server-backup-simulator-v2-available-now/

Updating...
Page view tracker