Skip to main content

S3 Backup

Comments

1 comment

  • Aleksandar Kostadinov

    Hi,

    If you were backing up your resources and switched the location of those backups from our backup storage to yours, or from one S3 bucket to another, what's likely happened is that the 'initial backup' job did not copy assets to the new S3 bucket because there's already a backup present according to our database. This is an uncommon situation, but it does sometimes occur when customers are changing their backup strategy.

    Effectively, when you switch to use S3 backups we don't purge the previously-existing backups in our own storage and the 'initial' backup job skips those files because the prior backup copy is detected. The number of backed up files reported by the job is the count of all backed-up files, not all files recently added to the backup.

    We do have a roadmap item to resolve this situation automatically, but at the moment it requires manual intervention.

    If you'd like the backups only in your the new S3 bucket, I recommend that with your permission, we perform the following steps:

    * Disable the S3 backup
    * Purge the existing backups from our records
    * Re-enable the S3 backup to the bucket of your choice
    * Restart the initial backup job.

    This has two side-effects which you should consider before we proceed:

    1. While we'll have additional off-site backups of all of your account resources throughout the process, you will lose the backed-up copies of files which you've already deleted
    2. Only the current version of your resources will be backed up, so if you were using backups to retain access to previous versions of overwritten files, those won't be available in the new backup location.

    If you'd like me to perform the steps above, please let me know, and for verification purposes please send an email to support@cloudinary.com and which includes the last four characters of the API secret for your Ccloudinary account as a form of verification.

    Best regards,

    Aleksandar

    0

Post is closed for comments.