Storage and backups

Where files are kept

File storage decides where uploaded files go. Choose one of three:

• Local: on your own server, in a folder you can set.
• Amazon S3: your own bucket, with its region and access keys.
• Cloudflare R2: your own bucket, with your account ID and keys.

Other S3-compatible services can be used with a custom endpoint. Use Test to check the connection before you save.

Opening files safely

When files are kept in S3 or R2, IPBases opens each one through a signed link that works for a limited time only, so a forwarded link stops working on its own. Your bucket stays private.

Database backups

Backups exports your database on a schedule you set, compresses it with gzip (usually much smaller) and saves it through the same storage as your files, so with S3 or R2 the copy is kept away from the server.

• Scheduled backups enabled: switch the schedule on or off.
• Schedule: when it runs. Add the command shown on the page to cPanel › Cron Jobs.
• Retention (days): backups older than this are deleted automatically.

Run backup now makes a copy straight away. Each backup can be downloaded or deleted from the list.

Google Drive

Google Drive can copy files and backups to the firm’s Drive, so the team has a familiar copy outside IPBases. See Files and Google Drive.

How it connects

This part of IPBases takes information from the parts on the left and changes what appears in the parts on the right. When you change one of them, check the other.