> For the complete documentation index, see [llms.txt](https://docs.cloudback.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudback.it/managing-backups/bulk-operations.md).

# Bulk Operations

Efficiently manage multiple repositories in Cloudback by applying backup settings in bulk, including schedules, storage options, and retention policies.

Bulk operations allow you to perform actions on multiple repositories at once. This feature is useful when you need to manage many repositories efficiently.

## How to Perform Bulk Operations

To perform bulk operations:

1. Open the **Dashboard** in Cloudback.
2. Use the search bar or filters to find the repositories you want to modify.
3. Select the repositories by checking the checkboxes next to them.
4. Click the **Edit** button in the toolbar to open the Bulk Operations window.

The changes you make in the Bulk Operations window will be applied to all selected repositories.

![Bulk operations](https://2781059148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQEI7SjBF2CddqNXZpCoE%2Fuploads%2Fgit-blob-8f576ba3ae57b64f0f9ca2e4bb1869887424194b%2Fbulk-operations.png?alt=media)

## Available Bulk Operations

You can modify the following settings for multiple repositories at once:

* `State` - Schedule / Not Scheduled. This setting allows you to enable or disable the automated daily backups for multiple repositories.
* `Schedule` - Set a custom schedule for multiple repositories. You can choose from the predefined schedules or create a new one using [Backup Schedules](/managing-backups/setting-backup-schedules.md) page.
* `Storage` - Set a storage for backup archives, could be `Cloudback` or a custom storage created by a user.
* `Retention policy` - Backup archive retention policy - determines how long the backup archives are kept before they are deleted.

Each selector defaults to **"Don't change"**, meaning only settings you explicitly modify will be applied. Selectors left at "Don't change" will not affect the selected repositories.

## Results and Error Reporting

After applying bulk changes, Cloudback displays a results summary showing how many repositories were updated successfully. If any repositories could not be updated, a table lists each failure with the repository name and the associated error message.

Bulk operations are processed per repository. If one repository fails (for example, due to an access control issue), the remaining repositories are still updated. Partial failures are possible and will be reported in the results screen.

## Learn More

* [Cloudback Managed Storages](/storage-configuration/cloudback-managed-storages.md)
* [Customer Managed Storages](/storage-configuration/customer-managed-storages.md)
* [Backup Schedules](/managing-backups/setting-backup-schedules.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cloudback.it/managing-backups/bulk-operations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.