This issue occurs when the number of entities protected under a tenant reaches the configured entity limit.
For example, if the VMware entity limit for a tenant is configured as 1, only one VMware entity can be protected. Additional VMs are skipped and reported as failed because processing them would exceed the tenant's allocated entity limit.
Sign in to the BDRShield Backup Server using an administrator account, and then complete the following steps:
Navigate to Tenants > Manage Tenants.
Locate the affected tenant and click Edit.
Open the Unit Quota step.
Locate the applicable entity type as Virtual Machines.
Click the Edit icon beside the current limit.
Enter a new limit greater than both the current configured limit and the tenant's currently used entity count.
Alternatively, use Reset Quota Details to configure the entity type as Unlimited, when unrestricted usage is permitted.
Click Set.
Proceed through the remaining tenant configuration steps and click Save.
If the configured VMware entity limit is 1 and 46 VMs are selected for backup, increase the limit to at least 46. If more VMs may be added later, configure a suitably higher limit or set it to Unlimited.
Retry the failed backup job or wait for its next scheduled run.
Navigate to Reports > Backup Reports > Backup Job History.
Open the affected backup schedule and expand the VM List.
Confirm that the previously restricted VMs are processed successfully.
Verify that error 101051 is no longer reported.
The new limit must be higher than the tenant's currently used entity count.
Changing the limit does not automatically rerun the failed schedule. Retry the backup or wait for the next scheduled run.