Skip to content

Commit 06080ed

Browse files
Update recovery.md
1 parent 5dda516 commit 06080ed

File tree

1 file changed

+108
-108
lines changed

1 file changed

+108
-108
lines changed

docs/how-to/recovery.md

Lines changed: 108 additions & 108 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Manual Recovery
1+
# How to recover a destroyed deployment
22

33
## Overview
44
Let's consider a situation where we had a ArangoDeployment in Cluster mode (3 DbServers, 3 Coordinators, 3 Agents)
@@ -93,121 +93,121 @@ EOF
9393

9494
3. Now create PV and PVC for every directory listed above
9595

96-
- **Agents** - here is an example for `AGNT-pntg5yc8`(`f9rs2htwc9e0bzme` directory)
97-
98-
- PV
96+
- **Agents** - here is an example for `AGNT-pntg5yc8`(`f9rs2htwc9e0bzme` directory)
9997

100-
```yaml
101-
cat <<EOF | kubectl apply -f -
102-
apiVersion: "v1"
103-
kind: PersistentVolume
104-
metadata:
105-
labels:
106-
arango_deployment: cluster
107-
role: agent
108-
name: agent-pntg5yc8-f9rs2htwc9e0bzme
109-
spec:
110-
accessModes:
111-
- ReadWriteOnce
112-
capacity:
113-
storage: 1Gi
114-
local:
115-
path: /mnt/data/f9rs2htwc9e0bzme
116-
persistentVolumeReclaimPolicy: Retain
117-
storageClassName: my-local-ssd
118-
volumeMode: Filesystem
119-
nodeAffinity:
120-
required:
121-
nodeSelectorTerms:
122-
- matchExpressions:
123-
- key: kubernetes.io/hostname
124-
operator: In
125-
values:
126-
- minikube
127-
EOF
128-
```
98+
- PV
12999

130-
- PVC
131-
132-
```yaml
133-
cat <<EOF | kubectl apply -f -
134-
apiVersion: v1
135-
kind: PersistentVolumeClaim
136-
metadata:
137-
labels:
138-
app: arangodb
139-
arango_deployment: cluster
140-
role: agent
141-
name: agent-pntg5yc8
142-
spec:
143-
accessModes:
144-
- ReadWriteOnce
145-
resources:
146-
requests:
100+
```yaml
101+
cat <<EOF | kubectl apply -f -
102+
apiVersion: "v1"
103+
kind: PersistentVolume
104+
metadata:
105+
labels:
106+
arango_deployment: cluster
107+
role: agent
108+
name: agent-pntg5yc8-f9rs2htwc9e0bzme
109+
spec:
110+
accessModes:
111+
- ReadWriteOnce
112+
capacity:
147113
storage: 1Gi
148-
storageClassName: my-local-ssd
149-
volumeMode: Filesystem
150-
volumeName: agent-pntg5yc8-f9rs2htwc9e0bzme
151-
EOF
152-
```
114+
local:
115+
path: /mnt/data/f9rs2htwc9e0bzme
116+
persistentVolumeReclaimPolicy: Retain
117+
storageClassName: my-local-ssd
118+
volumeMode: Filesystem
119+
nodeAffinity:
120+
required:
121+
nodeSelectorTerms:
122+
- matchExpressions:
123+
- key: kubernetes.io/hostname
124+
operator: In
125+
values:
126+
- minikube
127+
EOF
128+
```
153129

154-
- **DbServers** - here is an example for `PRMR-9xztmg4t` (`vka6ic19qcl1y3ec` directory)
130+
- PVC
155131

156-
- PV
132+
```yaml
133+
cat <<EOF | kubectl apply -f -
134+
apiVersion: v1
135+
kind: PersistentVolumeClaim
136+
metadata:
137+
labels:
138+
app: arangodb
139+
arango_deployment: cluster
140+
role: agent
141+
name: agent-pntg5yc8
142+
spec:
143+
accessModes:
144+
- ReadWriteOnce
145+
resources:
146+
requests:
147+
storage: 1Gi
148+
storageClassName: my-local-ssd
149+
volumeMode: Filesystem
150+
volumeName: agent-pntg5yc8-f9rs2htwc9e0bzme
151+
EOF
152+
```
157153

158-
```yaml
159-
cat <<EOF | kubectl apply -f -
160-
apiVersion: "v1"
161-
kind: PersistentVolume
162-
metadata:
163-
labels:
164-
arango_deployment: cluster
165-
role: dbserver
166-
name: dbserver-9xztmg4t-vka6ic19qcl1y3ec
167-
spec:
168-
accessModes:
169-
- ReadWriteOnce
170-
capacity:
171-
storage: 1Gi
172-
local:
173-
path: /mnt/data/vka6ic19qcl1y3ec
174-
persistentVolumeReclaimPolicy: Retain
175-
storageClassName: my-local-ssd
176-
volumeMode: Filesystem
177-
nodeAffinity:
178-
required:
179-
nodeSelectorTerms:
180-
- matchExpressions:
181-
- key: kubernetes.io/hostname
182-
operator: In
183-
values:
184-
- minikube
185-
EOF
186-
```
154+
- **DbServers** - here is an example for `PRMR-9xztmg4t` (`vka6ic19qcl1y3ec` directory)
187155

188-
- PVC
156+
- PV
189157

190-
```yaml
191-
cat <<EOF | kubectl apply -f -
192-
apiVersion: v1
193-
kind: PersistentVolumeClaim
194-
metadata:
195-
labels:
196-
app: arangodb
197-
arango_deployment: cluster
198-
role: dbserver
199-
name: dbserver-9xztmg4t
200-
spec:
201-
accessModes:
202-
- ReadWriteOnce
203-
resources:
204-
requests:
158+
```yaml
159+
cat <<EOF | kubectl apply -f -
160+
apiVersion: "v1"
161+
kind: PersistentVolume
162+
metadata:
163+
labels:
164+
arango_deployment: cluster
165+
role: dbserver
166+
name: dbserver-9xztmg4t-vka6ic19qcl1y3ec
167+
spec:
168+
accessModes:
169+
- ReadWriteOnce
170+
capacity:
205171
storage: 1Gi
206-
storageClassName: my-local-ssd
207-
volumeMode: Filesystem
208-
volumeName: dbserver-9xztmg4t-vka6ic19qcl1y3ec
209-
EOF
210-
```
172+
local:
173+
path: /mnt/data/vka6ic19qcl1y3ec
174+
persistentVolumeReclaimPolicy: Retain
175+
storageClassName: my-local-ssd
176+
volumeMode: Filesystem
177+
nodeAffinity:
178+
required:
179+
nodeSelectorTerms:
180+
- matchExpressions:
181+
- key: kubernetes.io/hostname
182+
operator: In
183+
values:
184+
- minikube
185+
EOF
186+
```
187+
188+
- PVC
189+
190+
```yaml
191+
cat <<EOF | kubectl apply -f -
192+
apiVersion: v1
193+
kind: PersistentVolumeClaim
194+
metadata:
195+
labels:
196+
app: arangodb
197+
arango_deployment: cluster
198+
role: dbserver
199+
name: dbserver-9xztmg4t
200+
spec:
201+
accessModes:
202+
- ReadWriteOnce
203+
resources:
204+
requests:
205+
storage: 1Gi
206+
storageClassName: my-local-ssd
207+
volumeMode: Filesystem
208+
volumeName: dbserver-9xztmg4t-vka6ic19qcl1y3ec
209+
EOF
210+
```
211211

212212
### Create ArangoDeployment with previously created PVC
213213

@@ -276,7 +276,7 @@ status:
276276
persistentVolumeClaim:
277277
name: cluster-dbserver-31akmzrp
278278
persistentVolumeClaimName: cluster-dbserver-31akmzrp
279-
EOF
279+
EOF
280280
```
281281

282282
That's it! Now you can use ArangoDB with restored data.

0 commit comments

Comments
 (0)