Redis Backups Fail Due to Missing File (statefile.json)

Products

• Redis for VMware Tanzu

Issue/Introduction

"timestamp":"1619114408.036848068",
"source":"ServiceBackup",
"message":"ServiceBackup.WithIdentifier.Perform backup completed with error",
"log_level":2,
"data":{"backup_guid":"58c16e7b-133a-4c0d-9ce3-7f9060dcb322",
"error":"exit status 3",

{"timestamp":"1619114471.038774967","source":"ServiceBackup","message":"ServiceBackup.error sending service alert","log_level":2,"data":{"error":"Get /v2/info: unsupported protocol scheme \"\""}}

A bug was introduced between Redis versions 2.1.4 and 2.1.8 (and potentially similarly timed releases of 2.2.x and/or 2.3.x) which causes Redis backups to fail with the error message above.

A commit deprecated dedicated instances, and with it, the creation of the statefile.json file. The file is no longer necessary but some code still depends on it. 

This issue did not affect on-demand plans. It only affected backups of shared-redis plans on newer deployments of the Redis for Tanzu Application Service tile.

In the following Redis for Tanzu Application Service versions, backups were configured through a persistent statefile.json created by the Redis for Tanzu Application Service tile:

• v2.2.2
• v2.2.1
• v2.2.0
• v2.1.4
• v2.0.6

This is not true for later Redis for Tanzu Application Service versions. However, backups of shared-redis plans for these later versions still depended on the existence of that statefile.json file.
This meant installations of Redis for Tanzu Application Service that had created this file, and later been upgraded, persisted the file and worked as expected. Meanwhile, newer installations of Redis for Tanzu Application Service failed to backup shared-redis instances.

Resolution

Please contact Tanzu Support and provide this KB Article ID to assist with the resolution.