Skip to main content
Skip table of contents

_Backup/ Restore

This document is invalidated due to the dependencies on the  outcome of the procedure mentioned here. Please do not use it.




We need longhorn installed before proceeding with this setup.

Cert Manager


If you have not installed rancher, thus you might not have installed cert-manager. We need to install it first.




CODE
# If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart:
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.5.1/cert-manager.crds.yaml

# Add the Jetstack Helm repository
helm repo add jetstack https://charts.jetstack.io

# Update your local Helm chart repository cache
helm repo update

# Install the cert-manager Helm chart
helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.5.1


Start with cloning the repository from gitlab.


CODE
git clone -b develop https://gitlab.expertflow.com/kubernetes/cim-kubernetes.git

Navigate to backups directory

CODE
cd cim-kubernetes/backups

we now apply the kubernetes manifest to deploy minio.

CODE
kubectl apply -f minio-deploy.yaml

If you want to access minio console, edit the minio-service type: ClusterIP to type: NodePort in default namespace. Default username and password for Minio Console is:
expertflow
Expertflow123#


Configs in Longhorn UI

Go to the Longhorn UI. In the top navigation bar, click Settings. In the Backup section, set Backup Target to


CODE
s3://backupbucket@us-east-1/

And set Backup Target Credential Secret to:

CODE
minio-secret




Application Sub-component of applicationStatus
1Minio
  •  
2

MongoDB



  •  
3Postgres
  •  
4MonitoringGrafana
Prometheus
  •  
5Logging with LokiLoki
  •  
6Logging with EFKElasticsearch
  •  
Kibana
  •  

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.