logo
Alauda Cache Service for Redis OSS
English
简体中文
English
简体中文
logo
Alauda Cache Service for Redis OSS
Navigation
Introduction
Release Notes
Lifecycle Policy
Install
Upgrade
Architecture

Guides

Create Instance
Deleting Instance
User Management
Parameter Configuration
Access Methods
Update Specification
Scheduling Configuration
Backup & Restore Instance
Monitoring and Alerts
Log
Start & Stop Instance
Restart Instance

Disaster Recovery

Introduction
Setup
Failover
Limitations and Risks

HowTo

Client Connection

How to Access Sentinel Instance
How to Access Cluster Instance
Shard Scaling in Cluster Mode
Patch Version Upgrade
How to Initialize Cluster Shard Slots

Trouble Shooting

Discovery and Handling of BigKey

API Reference

Kubernetes APIs

Redis APIs

Redis
RedisUser
ActiveRedisConnection

Disaster Recovery#

Introduction

  • Overview
  • Architecture Description
  • Limitations and Risks

Setup

  • Source side
  • Target side

Failover

  • Disaster Recovery Cluster Switch
  • Client-side Disaster Recovery Switch

Limitations and Risks

  • Only IP connection addresses are currently supported
  • The provided link address of the source instance must be highly available
  • Currently only Redis 6.0 is supported, other versions do not support enabling disaster recovery
  • After the Redis instance enables disaster recovery, it cannot be turned off
  • Enabling disaster recovery will increase the pressure on storage. It is recommended to use local SSD as storage
  • To build a disaster recovery network, the Redis instances at both ends need to ensure that the architecture is the same
  • A Redis disaster recovery instance as a source can have at most 15 target instances
  • The following Redis 6.0 write commands do not currently support disaster recovery
  • After the source fails, the first thing to do is to disconnect from the source
📝 Edit this page on GitHub
Previous PageRestart Instance
Next PageIntroduction