Reducing Bitbucket API limits impact
Adding additional users to Xopero ONE
Xopero ONE lets you authenticate multiple organization accounts when backing up repositories. By distributing provider-imposed request limits across several accounts, the backup process is accelerated and the risk of throttling—minimized.
For step-by-step instructions on adding additional accounts to a backup, refer to the Throttling prevention section of the knowledge base.
Limiting the number of simultaneously secured repositories
To optimize performance, limit the number of repositories secured simultaneously by creating multiple backup plans for Bitbucket. Configure their schedules so that they run at defined intervals rather than all at once.
For example, if your organization contains 900 repositories, you can create four backup plans and assign 225 repositories to each. Depending on your needs, you may schedule these plans to run daily at 6-hour intervals, or configure each plan to run on a different day of the week.
Scheduling copies outside CI/CD task runtime
All CI/CD task activity also consumes query limits, which are shared with the Xopero ONE application. To avoid conflicts, it is recommended to schedule backups outside CI/CD operating hours— for example, during the night.
Excluding unnecessary metadata in the plan
When creating a backup plan, you can select which data should be secured. By default, all data types in the plan are included. However, if you know that certain elements—such as variables or pull requests—will not be needed for future recovery, you can deselect them from the list. Backing up less data reduces the number of sent queries and improves overall efficiency.
Last updated