S3 storage, uploads and bulk backup actions

How backup storage works

Backups are stored in an S3-compatible bucket that you own (AWS S3, MinIO, DigitalOcean Spaces, Wasabi, Backblaze B2 and similar). You configure it once per project in Project Settings, on the Storage tab, and every instance of the project uses it. The Backups tab in the Console lists what is in that bucket, and the Upload button there stays disabled until a bucket is configured.

Because the bucket is yours, it may also hold files that have nothing to do with CICDoo. The Backups tab marks those clearly so you do not delete or restore them by mistake.

Connecting an S3 bucket to a project

You need the Project settings permission in a workspace.

1. Open the project in the Console and click Project Settings at the bottom of the sidebar.
2. Open the Storage tab. The card is titled S3-Compatible Storage Configuration.
3. Fill in the fields:
   • S3 Bucket Name: the bucket all instances of this project use.
   • Region / Location: for AWS a region such as us-east-1, for other providers their location value.
   • Access Key ID and Secret Access Key: credentials with access to the bucket.
   • Custom Endpoint URL (Optional): the endpoint of a non-AWS provider, for example a MinIO or Spaces URL. Leave it empty for AWS S3.
   • Use SSL/TLS (HTTPS): keep it ticked unless your endpoint only speaks plain HTTP.
   • Keep local backup copy on the server: by default the backup archive is removed from the server once S3 confirms it holds a complete copy. Tick this to keep both copies.
   • Backup Retention (days): how many days backups are kept before automatic deletion.
4. Click Test Connection to check the details.
5. If the bucket does not exist yet, click Create Bucket to create it with these credentials.
6. Click Save Changes at the top of the page.

Note: Retention clean-up runs as part of each instance's own successful backup and only removes that instance's older backups. Instances without a backup schedule never clean up, so use bulk delete (below) to tidy them.

Uploading files to the bucket from Project Settings

1. On the Storage tab, make sure the bucket name and both keys are filled in.
2. Click Upload Files.
3. Pick one or more files. They are uploaded straight to your bucket, with a progress dialog you can cancel.

Uploading a backup from the Backups tab

Use this to bring in a backup taken elsewhere, for example an Odoo database backup, so you can restore it on an instance. You need the Backups permission.

1. Open the instance in the Console and click the Backups tab.
2. Click Upload. If the button is greyed out, no bucket is configured yet.
3. In the Upload Backup dialog, choose a .zip file. It must contain dump.sql, dump.pgc or dump_dir/, optionally with a filestore/ folder. Backups downloaded from this tab and Odoo database backups both have this shape.
4. Wait for the progress bar to finish. Click Cancel Upload to stop it.
5. The file appears in the list as an uploaded backup. Restoring it is a separate step, see Backups and restore.

Note: If the upload fails with a message about the ETag header, add ETag to the ExposeHeaders of your bucket's CORS configuration and try again.

Searching and filtering the list

1. In the Backups tab, type part of a file name in the Search object keys box to narrow the list.
2. Click Filters to open the Filter backups dialog.
3. Pick any of Project, Instance, Repository, Branch and Type. Type can be Full backup, Database only, Uploaded backup, Platform file or Other object.
4. Click Apply. Reset clears the dialog and Cancel closes it without changes.
5. Applied filters appear as chips under the search box. Click the x on a chip to remove one, or Clear all to remove them all.

The list loads in pages. Click Load more at the bottom to fetch the next page. If a note says results come from the metadata index, which is still scanning the bucket, a matching file may not appear yet; try again later.

Deleting several backups at once

You need the Backups permission.

1. In the Backups tab, tick the checkbox on each backup you want to remove, or tick Select all to select every selectable row loaded so far. Rows not yet loaded with Load more are never included.
2. The bar shows how many rows are selected and their total size. Click Clear to start over.
3. Click Delete selected.
4. In the confirmation dialog, type delete and click Delete.

If some files could not be deleted, a message tells you how many, and they stay selected so you can retry.

Badges you may see

• Unattributed: the file is in your bucket but is not a recognised CICDoo backup. It cannot be bulk-selected. To delete or restore it, act on it alone and type its full file name to confirm.
• Platform file: a file that belongs to another CICDoo feature, such as an agent task attachment. It cannot be bulk-selected.
• Checking...: CICDoo has not finished identifying the file yet.
• A badge with a stage and branch, such as Production with a branch name, marks a backup taken on another instance of the project.

Related: Backups and restore, Project environments, extensions and deletion, Member permissions and resource access.

If you get stuck, open a support ticket from the Tickets page or the chat widget.