Step 3 - Upgrade BDRSuite Clients

BDRSuite components like Backup Proxy, BDRSuite Integration Service (VIS), and Tape Backup Service are bundled with this backup server by default. When upgrading the backup server, these BDRSuite components will also get added for automatic upgrade.

In order to automatically upgrade the BDRSuite Clients, you have to download the necessary BDRSuite Client builds to the BDRSuite Backup Server and add them for automatic update. 

With every version release of the BDRSuite, the BDRSuite Client builds & XML file will be provided.  Follow the below steps to add the BDRSuite Client builds & XML files for automatic update.

  1. Download the BDRSuite Client builds and its XML to one of the folders in your BDRSuite Backup Server machine. Make sure the downloaded Client builds and its XML are in the same folder.

  2. Login to the BDRSuite Backup Server web console, and navigate to the “Data Sources > Manage BDRSuite Clients > Software Updates" page, and click on "Add builds".

  3. Browse for the folder where you added the Client builds & its XML, and click on the “List Build File(s)

All the builds available in the selected folders will be listed. Select the required builds by selecting the checkbox alongside the respective build you wish to update, and click on the “Add Build Files”.

Information Note:

  • The configuration file(XML) will contain the version and build details of the installation file
  • To add 32-bit client build for Windows, the user needs to copy the respective 64-bit client and its associated XML file to the same folder

  • Now Select the location under the backup server where the build and configuration files are copied and click the 'List Build File(s)' option.

This will list all build files present in the folder as shown below, enable a checkbox alongside the respective build you wish to update, and click the 'Add Build Files' option.

Information Note:

Client proxies running older versions(v3.0, v3.1.0, v3.1.1, v3.1.2, and v3.1.3) cannot be upgraded directly to the latest version and should be upgraded at one version after another as follows:

Older versions v3.5  v3.6  v3.7  v3.8  v3.9.1  v4.0  v4.2


PreviousNext