1. If you add the Windows Endpoint using the option: I will manually Download BBA and install it on the target host
   
2. If adding the Windows Endpoint has failed through the option: Automatically Install BBA in the target host.
   

Steps to Add Endpoints (Windows using the option: Download and Manually Install BBA on the target host:

Steps to Download and Install BBA on Windows Endpoints

1. Download the BBA installer.
   
2. Open Command Prompt and run the below command (from the location where BBA is installed) to connect BBA to the backup server. Ensure you provide the backup server’s IP address/DNS name.
   

msiexec /i BDRShield_Delegation_Service_5_3_0_0.msi /qn ISENDPOINTENABLED="1" BACKUPSERVERINFO="{Enter BDRShield Backup Server IP Address/DNS Name}" BUILDTYPE="14"

Establishing Connection between the target Endpoint and BDRShield Server:

1. If the BBA on the target Endpoint is successfully connected to the BDRShield Server, then the status will be shown as ‘Idle’.
2. If the target Endpoint is not connected, then the status will be shown as ‘BBA Not Connected’. In this case, ensure the following on the target Endpoint:
   
1. Make sure BDRShield Backup Agent(BBA) (runs with service name:BDRShield Delegation Service) is installed.
   
2. Make sure the ‘BDRShield Delegation Service’ status is running.
   
3. BBA installed on the target Endpoint uses port 42005 to communicate with the BDRShield Server. To check whether the port is open for communication between the Endpoint and BDRShield Server, open Command Prompt on the Endpoint and execute the following command.
   
1. 

   telnet [BDRShield Server IP Address/DNS Name] [port]
2. If the port is not accessible, it can be due to the firewall settings. Make sure your firewall rules allow port 42005 to be open for communication.
   
4. If the connection to the target Endpoint has still not been established, please check the logs on the location below for more information. The errors you may encounter in the logs while adding Endpoints are listed below along with the solutions.
   

Target Endpoint:

Windows Log Location: <installation location>\Vembu\VembuIntegrationService\log\server.log Example: C:\Program Files\Vembu\VembuIntegrationService\log\server.log Linux Log Location:<installationlocation>/vembuintegrationservice/Vembu/VembuIntegrationService/log/server.log Example: /home/vembuintegrationservice/Vembu/VembuIntegrationService/log/server.log

BDRShield Server:

Windows Log Location: <installation location>\Vembu\VembuBDR\log\server.log Example: C:\Program Files\Vembu\VembuBDR\log\server.log Linux Log Location: /<installation location>/vembubdr/Vembu/VembuBDR/log/server.log Example: /home/vembubdr/Vembu/VembuBDR/log/server.log

How to resolve the issues you run into when adding Endpoints:

1. Error 117073: Unable to find the Endpoint – {Hostname/IP}. Make sure the Endpoint is added to the BDRShield Server. — To resolve this issue, make sure you add the Endpoints details and save them on the backup server under the Data Sources menu
   
2. Error 117074: Unable to connect to the BDRShield Server. Make sure the BDRShield Server is up and running. — To resolve this issue, make sure you have specified the valid backup server IP address/DNS name and BDRShield service is up and running.
   
3. Error 117076: BDRShield Server isn’t compatible with the BDRShield Delegation Service (BDS) version running on the target host. Make sure the BDS runs the same or lower version than BDRShield Server. — To resolve this issue, ensure the BDRShield Delegation Service runs on the same or lower version than the BDRShield Server.
   
4. Error 117072: Unable to register the target host as another host with the same BIOS UUID added already. Hosts with unique BIOS UUID can only be added/registered to the BDRShield Server. — You can only add Endpoints that have unique BIOS UUID.
   
5. Error 117011: Unsupported Operating System for backup. — Check the supported OS here.