Error 101910: Backup Failed. Unable to initialize Backup Component.
Description:
This error occurs when the agent is unable to communicate with the internal TCP port used for inter-service communication. By default, the system uses port 5557. If this port is unavailable or already in use by another process or service, this error will be reported.
Resolution:
Verify port availability
Change the port (if required)
Path:
C:\Program Files\Vembu\VembuIntegrationService\conf\SGConfiguration.conf
Modify the MessageQueuePort attribute under the BackupCache tag as shown below:
<ObjectStorage>
<BackupCache Enabled="0" MessageQueuePort="5557" MemoryPoolCount="10" />
</ObjectStorage>
Restart services
Related Articles
Unable to Create VM Snapshot. Failed to Quiesce the VM.
KB ID: 105130 Details: BDRShield utilizes VMware snapshots for VM Backup & Replication. During the snapshot initiation for backup or replication, BDRShield ensures VM quiescing to maintain on-disk data consistency. However, users may encounter an ...
VMware Backup Failure: Unable to Retrieve queryChangedDiskAreas
KB ID: 105017 Issue: During VMware backups, encountering the error message "Unable to retrieve queryChangedDiskAreas even after CBT query retry" indicates a failure to track Changed Blocks of a virtual machine (VM) within BDRShield. Cause: The error ...
Troubleshooting Guide: BDRShield Backup Failed - Internal File System Error
KB ID: 102180 Issue: Backup operations have failed due to an internal file system error within BDRShield. This error occurs when a specific backup job in BDRShield possesses a negative chunk file ID value, resulting in job failure. Cause: The failure ...
SG0083: Error - Unable to Send Backup Details to Server
KB ID: 115109 Cause: When performing backup jobs, the error "Unable to send backup details to server" may occur. This error is typically associated with large backup data sizes or unstable network connectivity. Solution: To address this issue, please ...
Could Not Initialize" Error in BDRShield
KB ID: 57 Cause: The error occurs due to a failure to initialize when booting a VHD through Hyper-V. Solution 1: Ensure that Intel Virtualization Technology (Intel VT) or AMD-V (depending on the processor brand) is enabled in the host machine's BIOS. ...