Local-only backups fail with a quota error after moving a DS-Client to a replicated DS-System

Modified on Mon, 28 Sep at 12:26 PM

Local-only backups fail with a quota error after moving a DS-Client to a replicated DS-System

Machine-distilled from a resolved support ticket on 2026-09-28. Source ref: 55f77af8bc15. Verify before relying on it.

Applies to: DS-Client and DS-System environments using DS-System replication, where DS-Clients are licensed with local-only storage capacity. Version not confirmed in the ticket.

Symptom: After a DS-Client is switched to a different DS-System (for example a failover or data centre change to a replicated DS-System), local-only backups fail with a quota error. The local-only quota shown in the DS-Client is lower than the licensed amount or missing.

Cause: The licence's local-only capacity value is not replicated between DS-Systems, even though other DS-Tools settings are. When the DS-Client connects to the other DS-System, that DS-System does not have the correct local-only capacity, so the quota is enforced incorrectly.

Resolution: 1. Confirm the licensed local-only capacity for the affected DS-Client. 2. On the DS-System the DS-Client now connects to, manually set the local-only capacity in the licence settings to the correct value. 3. Check that the DS-Client now shows the expected local-only quota, then rerun the failed local backups. 4. To stop this happening again, add a check or reapply of local-only capacity values to the runbook for every DS-System switchover or data centre change, because this setting is not carried across by replication.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article