v2.0
- About MogDB Stack
- Quick Start
- Installation
- Tutorial
- Architecture
- References
- Client
- mgo
- mgo create
- mgo create mgorole
- mgo create mgouser
- mgo create cluster
- mgo show
- mgo show k8s
- mgo show mgorole
- mgo show mgouser
- mgo show cluster
- mgo show restore
- mgo delete
- mgo delete mgorole
- mgo delete mgouser
- mgo delete cluster
- mgo delete backup
- mgo delete k8s
- mgo scale
- mgo scaledown
- mgo switch
- mgo update
- mgo update mgorole
- mgo update mgouser
- mgo update cluster
- mgo version
- mgo addk8s
- mgo localk8s
- mgo backup
- mgo backup detail
- mgo restore
- mgo minio
- mgo minio object
- mgo minio object ls
- mgo minio object stat
- mgo minio object getf
- Server
- Client
- FAQ
- Release Note
Recovery Management
MogDB Operator provides the ability to recovery a cluster from a backup.
If you need to customize the recovery configuration, you need to modify the MogDB cluster manifest restore spec, please refer to resotre spec:
The configuration for restoring via physical backup is as follows, for details please refer to GSBaseBackupSource:
apiVersion: mogdb.enmotech.io/v1
kind: MogdbCluster
spec:
restore:
# Image for performing recovery
image:
# ID of the restore mark
restoreId:
# Name of the target cluster
clusterName:
# Physical backup source
GSBaseBackupSource:
type:
target:
The configuration for restoring via logical backup is as follows, for details please refer to GSDumpAllSource:
apiVersion: mogdb.enmotech.io/v1
kind: MogdbCluster
spec:
restore:
# Image for performing recovery
image:
# ID of the restore mark
restoreId:
# Name of the target cluster
clusterName:
# logical backup source
GSDumpAllSource:
type:
target: