Error Message: Entity Restriction Limit Reached, You can't add agent further

The error may occur in the following scenarios.

1. Physical Servers and Endpoints  

During manual or automatic/bulk agent installation, the installation process displays the error and prevents the host from registering successfully.

2. Virtual Machines  

During a scheduled or manually initiated VM backup, the backup job may fail for newly added virtual machines. The Backup Report displays the following status:

• Status: Failed

• Message: Entity Restriction Limit Reached, You can't add agent further

3. Microsoft 365 and Google Workspace  

During backup execution, the job may fail to protect newly added user accounts when the tenant's assigned quota has been reached. The Backup Report displays the same error message.

Cause  

When a tenant is provisioned in BDRShield, the Administrator or MSP can assign a Unit Quota that defines the number of entities the tenant is permitted to protect.

If the number of entities exceeds the assigned quota, BDRShield enforces the applicable limit based on the workload type.

Note: Existing workload protection

Previously protected virtual machines and SaaS users can continue to be backed up even when the tenant reaches its quota. The restriction applies to newly added entities that exceed the applicable limit.

Server Proxies and Administrator-owned backup jobs do not consume tenant unit quotas.

How Unit Quotas Are Calculated  

In BDRShield, unit quotas are managed under Tenant Management → Unit Quota. Limits are tracked separately for each entity category.

• Servers and Endpoints: Each physical server, workstation, or endpoint configured with an agent.

• Virtual Machines: Each distinct virtual machine configured for backup across supported virtualization hosts.

• Microsoft 365: The number of distinct users protected across supported Microsoft 365 workloads, including mailboxes, groups, teams, and SharePoint sites, according to the applicable quota rules.

• Google Workspace: The number of distinct users protected across supported Google Workspace workloads, including mailboxes and shared drives, according to the applicable quota rules.

Solution  

To resolve this issue, the Administrator or MSP must increase the tenant's Unit Quota, if permitted, or remove unused entities to free up available capacity.

Method 1: Increase the Unit Quota  

Recommended when additional workload capacity is required.

1. Log in to the BDRShield Backup Server web console as an Administrator or MSP Operator.

2. Navigate to Tenants from the left navigation menu.

3. Locate the affected tenant.

4. Under the Actions column, click Edit.

5. Navigate to the Unit Quota tab or step.

6. Click the Pencil (Edit) icon next to the workload category that has reached its limit:

• Servers and Endpoints

• Virtual Machines

• Microsoft 365

• Google Workspace

7. Increase the numerical limit to accommodate the additional entities, or select Unlimited if this option is available and appropriate.

8. Click Save to apply the changes.

9. Retry the failed operation:

• Servers and Endpoints: Rerun the agent installer, either manually or through automatic/bulk deployment, to register the host.

• Virtual Machines: Rerun the applicable backup job from the Backup menu.

• Microsoft 365 and Google Workspace: Rerun the applicable backup job to protect the newly added accounts.

Important: BDRShield's Unit Quota configuration may restrict reducing quotas below configured levels. Verify the applicable quota policy before making changes, and allow sufficient capacity for planned workload growth.

Method 2: Free Up Entity Slots  

If you do not want to increase the tenant's quota, review the configured workloads and remove entities that are no longer required.

For Servers and Endpoints

1. Navigate to Inventory → Servers & Endpoints.

2. Locate decommissioned or obsolete machines registered under the affected tenant.

3. Delete or unregister the machines, as appropriate for your environment.

For Virtual Machines

1. Navigate to Backup → Edit Backup Job.

2. Edit the relevant virtualization backup job.

3. Deselect decommissioned or unnecessary virtual machines.

4. Save the changes.

For Microsoft 365 and Google Workspace

1. Navigate to Backup → Edit Backup Job.

2. Edit the relevant backup job.

3. Exclude offboarded or inactive accounts that no longer require protection, as appropriate.

4. Save the changes.

After freeing up capacity, retry the agent installation or backup job.

Note: Removing an entity from a backup job or inventory may affect its future protection and retention. Review the applicable backup and retention requirements before removing entities.

Need Further Assistance?  

If the tenant's Unit Quota shows available capacity but Error 117103 persists, verify the following:

1. The affected workload category has sufficient available quota.

2. The correct tenant and backup job are being checked.

3. The primary BDRShield server license permits the overall workload count.

4. The configured workload selection and inventory are consistent with the intended protection scope.

If the issue persists after these checks, contact BDRShield Support for further assistance. Include the error message, affected tenant, workload type, and relevant installation logs or Backup Report details when submitting the request.