Differential Backup Time Mismatch with Vembu NetworkBackup Database
KB ID: 110005
Cause:
If you are using another backup software alongside BDRSuite and backing up SQL Server database(s) using multiple applications, it can lead to inconsistency in backup sets. This issue arises when two schedules attempt to back up the same SQL Server database, causing SQL Server to change the reference of the database dump. Consequently, both backed-up datasets may become inconsistent when backed up across two schedules.
Solution:
To address this issue, it is recommended to configure SQL Server database backups using only one backup software. If you opt for more than one backup software for added redundancy, configure only 'Full Backups' of SQL Server databases. This ensures that BDRSuite and other backup applications will back up only full backups of SQL Server databases for each schedule.
Please note the following recommendations:
1. Backup Frequency: Set the backup frequency based on your available bandwidth.
2. Avoid Schedule Collisions: Ensure that backup schedules of any applications do not collide with each other and are scheduled upon completion of the other backup job.
To resolve this issue, configure additional full backups by editing the backup schedule and verifying the backup results.
Related Articles
Issue: Full Backup Time Mismatch Troubleshooting
KB ID: 110003 Cause: The mismatch in full backup time is observed when utilizing another backup software concurrently with Vembu NetworkBackup. Performing SQL Server database backups through multiple applications leads to inconsistency in backup ...
Mismatched Incremental Backup Time with BDRSuite Database
KB ID: 110004 Cause: If you were using another backup software concurrently with BDRSuite, inconsistency in backup sets might occur, especially when backing up SQL Server database(s) using multiple applications. This inconsistency arises from SQL ...
Database Backup Status: Last Full Backup Details for +<currDBName>+
KB ID: 109104 Issue: The last Full Backup of the database +<currDBName>+ appears to have been executed by another application, not Vembu NetworkBackup. The last Full Backup initiated by Vembu NetworkBackup was at [+<lastFullBkpTime>+]. Cause: If you ...
Unable to List Information Stores in Vembu NetworkBackup
KB ID: 115005 Cause: Vembu NetworkBackup employs a PowerShell script to list the Storage Groups available in the Exchange Server during the backup process. If the execution of PowerShell scripts is disabled in the Exchange Server, Vembu NetworkBackup ...
Addressing Issues with Incorrect Next Backup Schedule Time in BDRSuite
KB ID: 115 Causes: The "Next Backup Schedule Time" may appear empty or be updated incorrectly in the "List Job" window due to the following reasons: 1. Manual changes to the system time. 2. Rare cases of database update failure. Solution: To rectify ...