Resolving Issue - "No Databases Were Listed for Backup" in BDRSuite

Resolving Issue - "No Databases Were Listed for Backup" in BDRSuite

KB ID: 109000
Cause:
BDRSuite utilizes a PowerShell script to list databases available in Exchange Server. If the execution of PowerShell scripts is disabled in the Exchange Server, BDRSuite will not be able to list the available databases during the backup process.
Solution:
To resolve the issue of "No Databases Were Listed for Backup," follow these steps:
1. Open PowerShell.
2. Change the PowerShell script's execution policy from 'Restricted' to either ‘RemoteSigned’ or 'Unrestricted' by issuing the following command:
Set-ExecutionPolicy Unrestricted
Note: This command sets the execution policy to allow the running of scripts.
3. After updating the execution policy, try listing databases again.
By changing the PowerShell script's execution policy, you enable the necessary permissions for BDRSuite to list databases during the backup process.

    • Related Articles

    • BDRSuite - Release Notes

      BDRSuite 8.1.0 Release Date: Sep 12th, 2025 BDRSuite v8.1.0, delivering faster backups, easier recovery, and stronger security. With features like Agent-Centric Backups, ISO-based Bare-Metal Recovery, and improved restore performance, this release ...

    • Addressing "Microsoft 365 Domains not listed during backup configuration" Issue

      KB ID: 310000 Cause: This issue arises when the Domain status is unhealthy or inactive for any of the domains in the Microsoft 365 Organization added to the BDRSuite Server. Solution: 1. Check Domain Status: Contact your Microsoft 365 account ...

    • 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 ...

    • Handling Inconsistent Incremental Backups in BDRSuite for Exchange Server Databases

      KB ID: 109105 Issue: The last Incremental Backup of the database +<currDBName>+ appears to have been executed from another application instead of BDRSuite for Exchange Server. The last Incremental Backup executed by BDRSuite for Exchange Server was ...

    • 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 ...