Preventing BDRSuite Server Crashes: Best Practices for Restarting BDRSuite Application During Live Recovery
KB ID: 48
Cause:
If the BDRSuite application is restarted while a live recovery is in progress, the BDR server fails to start, resulting in the error message "32005 UI communication port to {{non-existent}} state."
Solution:
To resolve this issue, follow the steps below:1. Reboot the system on which the BDRSuite server is installed.Note: Ensure that the live recovery process is completed before restarting the BDRSuite application to avoid server crashes.
Related Articles
What are the best practices VMware vSphere Backup?
When implementing a VMware vSphere backup strategy, it’s essential to follow best practices with BDRSuite, to ensure complete data protection. Implement regular backups based on your RPO and criticality of the VMs Utilize agentless VM backups ...What are the Azure VM backup best practices available in BDRSuite?
Here are some best practices to follow when backing up your Azure VMs; Agentless VM backup: Complete image backup of the Azure VMs, including the operating system, applications, and data and store the backups in On-premise or Cloud. Incremental ...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 ...Microsoft Exchange Server Recovery
You can perform granular recovery of Microsoft Exchange Server directly from the BDRSuite Backup Server. To begin, click on the Recovery tab on the BDRSuite Backup Server home screen and select Restore Backup Data. A list of all backup jobs will be ...Microsoft SQL Server Recovery
Granular recovery for Microsoft SQL Server can also be performed directly from the BDRSuite Backup Server. Start by clicking on the Recovery tab and selecting Restore Backup Data. All backup jobs will be listed, from which you can select the one to ...