Troubleshooting Guide - BDRSuite GranularRecovery for MS Applications Termination Issue
KB ID: 127004
Issue:
The 'BDRSuite GranularRecovery for MS Applications' service terminated unexpectedly.
Cause:
This error occurs when the 'BDRSuite GranularRecovery for MS Applications' service is not running.
Solution:
To resolve this issue, perform the following steps:
1. Access the Windows Services management console by executing `services.msc`.
2. Locate the 'BDRSuite GranularRecovery for MS Applications' service within the list.
3. If the service displays a 'Stopped' status, right-click on it, and select 'Start' to initiate the service.
By following these steps, you should successfully restore the availability of the BDRSuite Service.
Related Articles
Troubleshooting Guide: BDRSuite Backup Failed - Internal File System Error
KB ID: 102180 Issue: Backup operations have failed due to an internal file system error within BDRSuite. This error occurs when a specific backup job in BDRSuite possesses a negative chunk file ID value, resulting in job failure. Cause: The failure ...
Backup aborted
KB ID: 101005 Product: BDRSuite Backup Server Cause This will occur due to the following reasons: Backup configuration stored in the server and client is incompatible. When the Backup storage location is inaccessible to the backup server. If you ...
Troubleshooting SNAPSHOT_FAILURE: Snapshot Initialization Issue in BDRSuite
KB ID: 115121 Cause: BDRSuite backup server relies on the Volume Shadow Copy Service (VSS) to create snapshots. The alert is usually generated when VSS is unable to start due to an ongoing VSS process. Microsoft's native snapshot manager can only ...
Error: Database Not Found in BDRSuite for Applications & DBs
KB ID: 115089 Issue: Encountering a "Database not found" error during an MS-SQL server backup indicates that the configured databases are either unavailable, removed, deleted, corrupted, or facing connectivity issues. Cause: The error occurs when one ...
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 ...