When utilizing Cloudinary's automatic backup feature, you can ask for the backed-up resources to be stored on your own private S3 or GCS bucket (available for all paid plans).
While it is a requirement that the backup partition is only managed by Cloudinary's backup mechanism, sometimes customers need to understand the structure of their data storage.
Below is an example of the general structure of a backed-up content path inside the backup bucket:
<S3/GCS-prefix>/res/<cloud-name>/<resource_type>/<type>/<public_id>/<version>.<format>
Some additional info and highlights:
- For the sake of redundancy, the
public_idis used as another folder level, and the version as the actual filename. - The backed-up content must remain untouched where it was stored by the automatic backup mechanism. Any change to this storage may break the internal consistency with our databases and result in data corruption.
- The aforementioned convention is subject to change at any time and is given for information purposes only.
Comments
3 comments
The variable names in this doc are not defined.
Hi.
The structure of the link that is exampled here is intentionally generic, as there could be many options.
I hope that is what you mean by your reply.
If not, please elaborate on what it is you are expecting to see, and we will be happy to help.
Can we access backup URL for a given resource? Is it exposed in the API?
Please sign in to leave a comment.