Cluster Deployment
The BDRSuite Backup Server can be deployed in a cluster on both the Windows and Linux. Click on the respective links to learn about the detailed installation process for cluster deployment.
If your BDRSuite Backup Server operates as a standalone server, you can configure it as a new Cluster setup by following this KB article.
The cluster installation comes with a few limitations, which are as follows;
- All the nodes should have a common cluster name. Multiple cluster names are not supported.
The BDR Backup Server web login and access are restricted for sub-nodes (User can access it only through the Main node).
The Disk Rotation repository type of Block Storage is not supported.
All nodes should have a common storage location; Backups will fail if the sub-nodes don't have access to the storage repository (Backup Repository).
Conversion of BDR Backup Server from Standalone to Cluster environment requires common storage for all nodes, else backups will fail when sub-nodes don't have access to the storage after conversion.
If you have opted for Object Storage as the backup repository in a cluster deployment, make sure that all nodes have seamless internet connectivity for the cloud upload of backup data.
The Backup Copy feature requires a common storage location for all nodes to access.
Windows BDR Server cluster group - should not support Linux BDR Server as a Main/Sub node; and Linux BDR Server cluster group - should not support Windows BDR Server as a Main/Sub node.
The BDR Cluster deployment doesn’t support the backup and recovery of AWS, Microsoft 365, and Google Workspace.