Restoring the Multicloud Object Gateway

Follow these steps to restore the Multicloud Object Gateway.

About this task

If the Multicloud Object Gateway (MCG) is not in the Active state, and the backingstore and bucketclass is not in the Ready state, you need to restart all the MCG related pods, and check the MCG status to confirm that the MCG is back up and running.

Procedure

Restart all the pods related to the MCG.
```
oc delete pods <noobaa-operator> -n openshift-storage
```
```
oc delete pods <noobaa-core> -n openshift-storage
```
```
oc delete pods <noobaa-endpoint> -n openshift-storage
```
```
oc delete pods <noobaa-db> -n openshift-storage
```
<noobaa-operator>

Is the name of the MCG operator

<noobaa-core>

Is the name of the MCG core pod

<noobaa-endpoint>

Is the name of the MCG endpoint

<noobaa-db>

Is the name of the MCG db pod
If the RADOS Object Gateway (RGW) is configured, restart the pod.
```
oc delete pods <rgw-pod> -n openshift-storage
```
<rgw-pod>

Is the name of the RGW pod
Note: In OpenShift Container Platform 4.11, after the recovery, RBD PVC fails to get mounted on the application pods. Hence, you need to restart the node that is hosting the application pods. To get the node name that is hosting the application pod, run the following command:
```
oc get pods <application-pod> -n <namespace> -o yaml | grep nodeName
  nodeName: node_name
```