KB ID : 115082
Published : July 23, 2018
Created : July 23, 2018
Last Modified : July 23, 2018


Dumping MS SQL backup data fails at Vembu NetworkBackup client.


The above error occurs at Vembu NetworkBackup client machine in the following scenarios:

Cause 1:

MS SQL database(s) configured for backup is set to offline.


Check the status of the backup configured database(s) in the MS SQL Server Management console i.e, the database(s) configured for backup should be in the online state. If it is in the offline state, make it online and then run the backup. This will resolve the issue.

Cause 2:

Not enough space available to dump MS SQL backup in the client machine.


Check the size of databases configured for backup schedule and ensure sufficient free space is made available in the drive in which the dump location is configured. It is recommended to keep free space as same as the size of the database. By default, the dump location for MS SQL backup is "<vembunetworkbackup home="">/plugin-data/mssqlserver/".

Cause 3:

The master DB of MS SQL Server is configured with differential/transaction log backup.


The master DB can only be configured for ‘Full’ backup. Disable the differential and transaction log backups from being configured to master DB.

Reference Link:https://social.msdn.microsoft.com/For...

Cause 4:

MS SQL database of "Simple" recovery model configured with TRANSACTION LOG backup.


MS SQL database of "Simple" recovery model can only be configured as "FULL” backup with DIFFERENTIAL LOG backup as the TRANSACTION LOG backup is not allowed for the "Simple" recovery model database(s).

Reference Link:https://docs.microsoft.com/en-us/sql/...

Cause 5:

Running differential/transaction log backup after a full database restore.


It is recommended to run only "Full Backups" after the full database restore before running differential/transaction log backup.

Cause 6:

Backup chain breakup error - Different backup applications using the same MS SQL DB for backup.


It is recommended not to allow two different backup applications to use the same MS SQL DB. Allowing such will cause log chain breakup resulting in inconsistent backup data.

But if you wish to backup MS SQL Server DBs using multiple backup applications, we suggest you configure ‘Full Backups Only’ setup for SQL Server DBs.

Steps to configure additional full backup using Vembu NetworkBackup:

a) Open the list backup jobs page in Vembu NetworkBackup web console.

b) Choose the MS SQL backup job you wish to configure and proceed with edit option.

c) Enable the immediate additional full backup option in the scheduling section along with the additional full backup and save the backup.

Cause 7:

Error in getting the virtual device backup configuration(SQLVDI) due to following reasons:

1) OSQL utility path not set in the environment variables. 2) SQLVDI.DLL not registered in the registry


1) OSQL utility error - Vembu NetworkBackup uses OSQL utility to backup and list the SQL databases. For this, the path of the utility should be set in the environmental variables of the system. We recommend you to verify this.

2) SQLVDI.DLL error - Vembu NetworkBackup uses the SQLVDI.DLL to dump the SQL databases. For this, the SQLVDI.DLL should be present in the system. We recommend you to verify this in the registry. If the DLL entry is not found in the registry, run the following command.

For the default path, C:\Program Files\Microsoft SQL Server:

→ Regsvr32 "C:\Program Files\Microsoft SQL Server\80\COM\SQLVDI.DLL".

For the path, C:\Program Files (x86)\Microsoft SQL Server:

→ Regsvr32 "C:\Program Files (x86)\Microsoft SQL Server\80\COM\SQLVDI.DLL"

Recommended practices for MS SQL server backup:

The type of backup (FULL, DIFFERENTIAL, TRANSACTION LOG) allowed on the MS SQL Server databases depends on the Recovery Model property of the individual database. By default, 'Recovery Model' for user databases were inherited from the 'model' system database. Totally, there are three types of recovery models available: 1. Simple Recovery model, 2. Bulk-Logged Recovery model and 3. Full Recovery model.

1) Configure a separate backup job for 'master' database with 'FULL' backup schedule alone, as 'DIFFERENTIAL & TRANSACTIONAL’ log backups are not allowed for the ‘master’ database. And also 'master' has to be restored first when restoring SQL Server for disaster recovery.

2) The databases with 'Recovery Model' as 'Simple' shall be configured with 'FULL' backup option and optionally with 'DIFFERENTIAL LOG' backup as 'TRANSACTIONAL LOG' backup are not allowed.

3) The databases with 'Recovery Model' as 'Full' or 'Bulk Logged' shall be configured with 'FULL' backup type and optionally with 'DIFFERENTIAL' and 'TRANSACTIONAL LOG' backup.


  1. If another backup software is being used alongside Vembu NetworkBackup, then the backup of MS SQL server database(s) would cause inconsistency unless the full backup is run. This is because the MS SQL server changes the reference of the database dump during the backup schedule. So, when two schedules from two different backup applications try to backup of the same SQL Server database, both the backed up data will turn inconsistent. Hence it is recommended not to use the MS SQL management studio to backup the SQL databases.

  2. If you still wish to backup the SQL Server databases using multiple backup applications for added redundancy, then we would suggest you configure only "Full Backups" for the SQL Server databases. In this method, Vembu NetworkBackup/another backup application will backup the full SQL Server database for every backup schedules. This will take more time and bandwidth. Therefore, you may have to schedule this full backup of MS SQL database less frequently and also make sure that one application starts the full backup schedule only after the other has completed it.

edit retag flag offensive close merge delete