---
id: aa5472ed-1425-4411-88b5-111886bc4a4a
---
# Redis missing backup incident.
---

The Redis missing backup incident refers to a situation where Redis, a popular in-memory data structure store, has not been backed up for a certain period of time. This could lead to data loss or corruption in the event of a system failure or other issues. The incident typically requires immediate attention to ensure that the data is properly backed up and that any potential issues are resolved quickly to avoid further complications.

### Parameters
```shell
export PATH_TO_REDIS_RDB="PLACEHOLDER"

export REDIS_HOST="PLACEHOLDER"

export BACKUP_DIRECTORY="PLACEHOLDER"

export BACKUP_FILENAME="PLACEHOLDER"

export REDIS_BACKUP_FILE="PLACEHOLDER"
```

## Debug

### Check if Redis is running on the instance
```shell
sudo systemctl status redis-server.service
```

### Check if Redis backup is enabled in the Redis configuration file
```shell
sudo grep -i save /etc/redis/redis.conf
```

### Check the size of Redis RDB file
```shell
sudo du -sh ${PATH_TO_REDIS_RDB}
```

### Check if Redis backup script is scheduled to run
```shell
sudo crontab -l | grep redis-backup.sh
```

### Check if the Redis backup script is running correctly
```shell
sudo tail -f /var/log/syslog | grep redis-backup.sh
```

### Backup failure: If the backup process fails for any reason, Redis may not be properly backed up. This could be due to issues with the backup software, connectivity issues, or other technical issues.
```shell


#!/bin/bash



# Set variables

REDIS_HOST=${REDIS_HOST}

BACKUP_DIR=${BACKUP_DIRECTORY}

BACKUP_FILE=${BACKUP_FILENAME}



# Check Redis connectivity

redis-cli -h $REDIS_HOST ping >/dev/null 2>&1

if [ $? -ne 0 ]; then

    echo "ERROR: Could not connect to Redis at $REDIS_HOST"

    exit 1

fi



# Check backup directory exists

if [ ! -d "$BACKUP_DIR" ]; then

    echo "ERROR: Backup directory $BACKUP_DIR does not exist"

    exit 1

fi



# Check backup file exists

if [ ! -f "$BACKUP_DIR/$BACKUP_FILE" ]; then

    echo "ERROR: Backup file $BACKUP_DIR/$BACKUP_FILE does not exist"

    exit 1

fi



echo "SUCCESS: Redis backup at $BACKUP_DIR/$BACKUP_FILE is present"

exit 0


```

## Repair

### commands to force redis to generate a new backup

```shell
bash

#!/bin/bash



# Stop the Redis service

sudo systemctl stop redis



# Rename the existing backup file

sudo mv ${REDIS_BACKUP_FILE} ${REDIS_BACKUP_FILE}.bak



# Force Redis to generate a new backup file

sudo redis-cli save



# Start the Redis service

sudo systemctl start redis


```



The Redis missing backup incident refers to a situation where Redis, a popular in-memory data structure store, has not been backed up for a certain period of time. This could lead to data loss or corruption in the event of a system failure or other issues. The incident typically requires immediate attention to ensure that the data is properly backed up and that any potential issues are resolved quickly to avoid further complications.


This incident type refers to a situation where a SQL Server database is not marked for replication sync, which means it may not be synced with its backup. This can result in data loss or inconsistencies between the primary database and its backup. It is important to address this issue promptly to ensure data integrity and prevent potential downtime or data loss.


SQL Server database not marked for replication sync.

The Redis too many masters incident occurs when there are too many master nodes in a Redis cluster, leading to connection issues and potential data loss. This can happen due to misconfiguration, network issues, or other factors, and requires immediate attention to prevent further damage.


Redis too many masters incident

This incident type refers to an issue with Redis replication, which means that there is a problem with the synchronization of data between Redis instances. This issue could impact the availability and performance of the system and may require immediate attention to restore the replication and ensure data consistency. The incident could be caused by various factors, such as network problems, hardware failures, or configuration issues. The incident must be investigated and resolved as soon as possible to avoid any data loss or downtime.


Redis replication broken incident.

This incident type refers to a situation where Redis, a popular in-memory data structure store, has rejected connections. This could happen due to various reasons such as server overload, network issues, or misconfiguration. When this occurs, it can cause disruptions in the performance of applications that rely on Redis for data storage or caching. Thus, it requires immediate attention and resolution to minimize the impact on the applications and users.


Redis Rejected Connections Incident

The Redis missing master incident occurs when the Redis cluster has no node marked as master. This can cause problems with the Redis service and may result in service disruptions or failures. It is important to address this issue promptly to ensure the smooth operation of the Redis service.


Redis missing master incident

```shell
export PATH_TO_REDIS_RDB="PLACEHOLDER"

export REDIS_HOST="PLACEHOLDER"

export BACKUP_DIRECTORY="PLACEHOLDER"

export BACKUP_FILENAME="PLACEHOLDER"

export REDIS_BACKUP_FILE="PLACEHOLDER"
```


### Check if Redis is running on the instance

```shell
sudo systemctl status redis-server.service
```

### Check if Redis backup is enabled in the Redis configuration file

```shell
sudo grep -i save /etc/redis/redis.conf
```

### Check the size of Redis RDB file

```shell
sudo du -sh ${PATH_TO_REDIS_RDB}
```

### Check if Redis backup script is scheduled to run

```shell
sudo crontab -l | grep redis-backup.sh
```

### Check if the Redis backup script is running correctly

```shell
sudo tail -f /var/log/syslog | grep redis-backup.sh
```

### Backup failure: If the backup process fails for any reason, Redis may not be properly backed up. This could be due to issues with the backup software, connectivity issues, or other technical issues.

```shell


#!/bin/bash



# Set variables

REDIS_HOST=${REDIS_HOST}

BACKUP_DIR=${BACKUP_DIRECTORY}

BACKUP_FILE=${BACKUP_FILENAME}



# Check Redis connectivity

redis-cli -h $REDIS_HOST ping >/dev/null 2>&1

if [ $? -ne 0 ]; then

    echo "ERROR: Could not connect to Redis at $REDIS_HOST"

    exit 1

fi



# Check backup directory exists

if [ ! -d "$BACKUP_DIR" ]; then

    echo "ERROR: Backup directory $BACKUP_DIR does not exist"

    exit 1

fi



# Check backup file exists

if [ ! -f "$BACKUP_DIR/$BACKUP_FILE" ]; then

    echo "ERROR: Backup file $BACKUP_DIR/$BACKUP_FILE does not exist"

    exit 1

fi



echo "SUCCESS: Redis backup at $BACKUP_DIR/$BACKUP_FILE is present"

exit 0


```


### commands to force redis to generate a new backup

```shell
bash

#!/bin/bash



# Stop the Redis service

sudo systemctl stop redis



# Rename the existing backup file

sudo mv ${REDIS_BACKUP_FILE} ${REDIS_BACKUP_FILE}.bak



# Force Redis to generate a new backup file

sudo redis-cli save



# Start the Redis service

sudo systemctl start redis


```


Redis missing backup incident.

Overview

Parameters

Debug

Check if Redis is running on the instance

Check if Redis backup is enabled in the Redis configuration file

Check the size of Redis RDB file

Check if Redis backup script is scheduled to run

Check if the Redis backup script is running correctly

Backup failure: If the backup process fails for any reason, Redis may not be properly backed up. This could be due to issues with the backup software, connectivity issues, or other technical issues.

Repair

commands to force redis to generate a new backup

Learn more

Related Runbooks

SQL Server database not marked for replication sync.

Redis too many masters incident

Redis replication broken incident.

Redis Rejected Connections Incident

Support