The back up process for Redis Enterprise Cloud data depends on your plan:

  • Flexible and Annual can use the Backup icon on the View Database screen or schedule regular backups.

  • Paid Fixed plans run scheduled backups every 24 hours.

  • Free plans do not back up automatically.

    (To back up Free plan data, connect to the database and use a process appropriate for the connection. For example, you can use the DUMP and RESTORE commands with Redis CLI.)

Here, you’ll learn how to store backups using different cloud providers.

Back up to Amazon Simple Storage Service (AWS S3)

To use an S3 bucket for storing backups, sign in to your AWS Management Console and follow these steps:

  1. Go to the AWS S3 Management Console in: Services > Storage > S3

  2. Configure the permissions for your S3 bucket:

    • For a new bucket:

      1. Click Create Bucket.
      2. Enter a name and region for the bucket and click Next.
      3. Set the bucket properties that are required by your company standards, and click Next.
      4. Set Public access properties according to your company standards, and click Next.
      5. Review the properties, and click Create bucket.
      6. Find your bucket in the bucket list, and click on the bucket name.
      7. In Permissions > Access Control, click Add account:
        1. In the Account field enter: fd1b05415aa5ea3a310265ddb13b156c7c76260dbc87e037a8fc290c3c86b614
        2. Select the Write objects, Read bucket permissions, and Write bucket permissions, and click Save.
    • For an existing bucket, click on the S3 bucket and go to the Permissions tab.

      1. Click Add account.
      2. In the Access for other AWS accounts section, enter:
        1. In the Account field enter: fd1b05415aa5ea3a310265ddb13b156c7c76260dbc87e037a8fc290c3c86b614
        2. Select the permissions that you need.
      3. Click Save.

After the permissions are set for your bucket, set the Backup Path to the path of your S3 bucket and click Apply. For example, if the name of your bucket is backups-bucket, use the path: s3://backups-bucket

Back up to Google Cloud Storage (GCS)

For Google Cloud Platform (GCP) console subscriptions, store your backups in a Google Cloud Storage bucket:

  1. Sign in to Google Cloud Platform console.

  2. In the admin console menu, locate the Storage section than select Cloud Storage > Browser.

  3. Create or select a bucket.

  4. Select the overflow menu (three dots, stacked) and then select the Edit Bucket Permissions command.

  5. Select the Add members button and then add:

    service@redislabs-prod-clusters.iam.gserviceaccount.com

  6. Set Role to Storage Legacy | Storage Legacy Bucket Writer.

  7. Save your changes.

  8. Verify that your bucket does not have a set retention policy.

    To do so:

    1. View the details of your bucket.

    2. Select the Retention tab.

    3. Verify that there is no retention policy.

    If a policy is defined and you cannot delete it, you need to use a different bucket.

Use the bucket details Configuration tab to locate the gsutil URI. This is the value you’ll assign to your resource’s backup path.

Back up to Azure Blob Storage

To store your backup in Microsoft Azure Blob Storage, sign in to the Azure portal and then:

  1. Create an Azure Storage account

  2. Create a container

  3. Manage storage account access keys

Set your resource’s Backup Path to the path of your storage account.

The syntax for creating the backup varies according to your authorization mechanism. For example:

abs://:storage_account_access_key@storage_account_name/container_name/[path/]

Where:

  • storage_account_access_key: the primary access key to the storage account
  • storage_account_name: the storage account name
  • container_name: the name of the container, if needed.
  • path: the backups path, if needed.

To learn more, see Authorizing access to data in Azure Storage

Back up to an FTP Server

To store your resource backups on an FTP server, set its Backup Path using the following syntax:

<protocol>://[username]:[password]@[hostname]:[port]/[path]/

Where:

  • protocol: the server’s protocol, can be either ftp or ftps.
  • username: your username, if needed.
  • password: your password, if needed.
  • hostname: the hostname or IP address of the server.
  • port: the port number of the server, if needed.
  • path: the backups path, if needed.