Error While Dumping MS SQL Backup Data in the Client

Error While Dumping MS SQL Backup Data in the Client

KB ID: 115082
Error: Dumping MS SQL backup data fails at the BDRSuite client.
Scenarios: The above error occurs at the BDRSuite client machine in the following scenarios:
Cause 1: MS SQL database(s) configured for backup is set to offline.
Solution: Check the status of the backup-configured database(s) in the MS SQL Server Management console. The database(s) configured for backup should be in the online state. If it is offline, make it online and then run the backup to resolve the issue.
Cause 2: Not enough space available to dump MS SQL backup in the client machine.
Solution: Check the size of databases configured for the backup schedule and ensure sufficient free space is available in the drive where the dump location is configured. Recommended free space is the same as the size of the database.
Cause 3: The master DB of MS SQL Server is configured with a differential/transaction log backup.
Solution: The master DB can only be configured for ‘Full’ backup. Disable the differential and transaction log backups from being configured to the master DB. Refer Link
Cause 4: MS SQL database of "Simple" recovery model configured with TRANSACTION LOG backup.
Solution: MS SQL database of "Simple" recovery model can only be configured as "FULL” backup with DIFFERENTIAL LOG backup, as TRANSACTION LOG backup is not allowed. Refer Link
Cause 5: Running differential/transaction log backup after a full database restore.
Solution: It is recommended to run only "Full Backups" after a full database restore before running a differential/transaction log backup.
Cause 6: Backup chain breakup error - Different backup applications using the same MS SQL DB for backup.
Solution: Avoid allowing two different backup applications to use the same MS SQL DB, as it may cause log chain breakup resulting in inconsistent backup data. Configure ‘Full Backups Only’ setup for SQL Server DBs if using multiple backup applications.
Steps to configure additional full backup using BDRSuite
a) Open the list backup jobs page in BDRSuite 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 the following reasons:
1. OSQL utility path not set in the environment variables.
2. SQLVDI.DLL not registered in the registry.
Solution:
1) OSQL utility error - BDRSuite 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 - BDRSuite 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:
1. Configure a separate backup job for the 'master' database with 'FULL' backup schedule only.
2. Databases with 'Recovery Model' as 'Simple' should be configured with 'FULL' backup option and optionally with 'DIFFERENTIAL LOG' backup.
3. Databases with 'Recovery Model' as 'Full' or 'Bulk Logged' should be configured with 'FULL' backup type and optionally with 'DIFFERENTIAL' and 'TRANSACTIONAL LOG' backup.
Note:
  1. If using another backup software alongside BDRSuite, avoid inconsistencies by running only "Full Backups" for SQL Server databases or schedule them with sufficient time gap to avoid collision.
  2. Do not use MS SQL Management Studio to backup SQL Server databases if multiple backup applications are used.


    • Related Articles

    • Error While Dumping Backup Data on the Client Side: [Microsoft][ODBC SQL Server Driver] Login Timeout Expired

      KB ID: 87 Causes: This error is typically triggered when the system variables under environment variables lack proper path settings or have incorrect paths configured. Solution: To resolve this issue, follow these steps on the affected machine: 1. ...

    • Error while dumping backup data in the BDRSuite client

      KB ID: 101017 Cause: This error might arise during backup operations with the BDRSuite Backup Server when attempting to dump backup data using the BDRSuite Client. Solution: To address this matter, kindly reach out to our support team. Before doing ...

    • Add MS SQL Server

      MS SQL Server can be backed up using the BDRSuite Backup Server. You can simply add the MS SQL Host as a Data Source to the BDRSuite Backup Server and configure backups. Navigate to Data Sources tab and choose Add MS SQL Server. When a MS SQL Server ...

    • Configuring SQL Database Backup

      Step 1: Adding Basic Job Details Enter the following details; Backup Job Name: Provide any proper name for your backup job. Backup Repository: Select the backup repository type. You can choose either Block Storage or Object Storage. Repository Name: ...

    • Microsoft SQL Server - Adding Data Source

      The data sources tab will list the various environment that you can backup and by selecting which you can enter the host details that you like to backup will be added and then listed for you to proceed with the further configuration. Also, you can ...