홈
제품
Red Hat CodeReady Workspaces
2.6
Administration Guide
Chapter 8. Backup and disaster recovery

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 8. Backup and disaster recovery

This section describes aspects of the CodeReady Workspaces backup and disaster recovery.

8.1. External database setup
링크 복사

The PostgreSQL database is used by the CodeReady Workspaces server for persisting data about the state of CodeReady Workspaces. It contains information about user accounts, workspaces, preferences, and other details.

By default, the CodeReady Workspaces Operator creates and manages the database deployment.

However, the CodeReady Workspaces Operator does not support full life-cycle capabilities, such as backups and recovery.

For a business-critical setup, configure an external database with the following recommended disaster-recovery options:

High Availability (HA)
Point In Time Recovery (PITR)

Configure an external PostgreSQL instance on-premises or use a cloud service, such as Amazon Relational Database Service (Amazon RDS). With Amazon RDS, it is possible to deploy production databases in a Multi-Availability Zone configuration for a resilient disaster recovery strategy with daily and on-demand snapshots.

The recommended configuration of the example database is:

Expand

Parameter	Value
Instance class	db.t2.small
vCPU	1
RAM	2 GB
Multi-az	true, 2 replicas
Engine version	9.6.11
TLS	enabled
Automated backups	enabled (30 days)

8.1.1. Configuring external PostgreSQL
링크 복사

Procedure

Use the following SQL script to create user and database for the CodeReady Workspaces server to persist workspaces metadata etc:

CREATE USER <database-user> WITH PASSWORD '<database-password>'  
CREATE DATABASE <database>                                      
GRANT ALL PRIVILEGES ON DATABASE <database> TO <database-user>
ALTER USER <database-user> WITH SUPERUSER

CREATE USER <database-user> WITH PASSWORD '<database-password>'


CREATE DATABASE <database>


GRANT ALL PRIVILEGES ON DATABASE <database> TO <database-user>
ALTER USER <database-user> WITH SUPERUSER

Copy to Clipboard

Toggle word wrap

1: CodeReady Workspaces server database username
2: CodeReady Workspaces server database password
3: CodeReady Workspaces server database name

Use the following SQL script to create database for RH-SSO back end to persist user information:

CREATE USER keycloak WITH PASSWORD '<identity-database-password>' 
CREATE DATABASE keycloak
GRANT ALL PRIVILEGES ON DATABASE keycloak TO keycloak

CREATE USER keycloak WITH PASSWORD '<identity-database-password>'


CREATE DATABASE keycloak
GRANT ALL PRIVILEGES ON DATABASE keycloak TO keycloak

Copy to Clipboard

Toggle word wrap

1: RH-SSO database password

8.1.2. Configuring CodeReady Workspaces to work with an external PostgreSQL
링크 복사

Prerequisites

The oc tool is available.

Procedure

Pre-create a project for CodeReady Workspaces:
```
oc create namespace openshift-workspaces
```
```
$ oc create namespace openshift-workspaces
```
Copy to Clipboard Toggle word wrap

Create a secret to store CodeReady Workspaces server database credentials:

oc create secret generic <server-database-credentials> \
--from-literal=user=<database-user> \
--from-literal=password=<database-password> \
-n openshift-workspaces

$ oc create secret generic <server-database-credentials> \


--from-literal=user=<database-user> \


--from-literal=password=<database-password> \


-n openshift-workspaces

Copy to Clipboard

Toggle word wrap

1: Secret name to store CodeReady Workspaces server database credentials
2: CodeReady Workspaces server database username
3: CodeReady Workspaces server database password

Create a secret to store RH-SSO database credentials:

oc create secret generic <identity-database-credentials> \
--from-literal=password=<identity-database-password> \
-n openshift-workspaces

$ oc create secret generic <identity-database-credentials> \


--from-literal=password=<identity-database-password> \


-n openshift-workspaces

Copy to Clipboard

Toggle word wrap

1: Secret name to store RH-SSO database credentials
2: RH-SSO database password

Deploy Red Hat CodeReady Workspaces by executing the crwctl command with applying a patch. For example:
```
crwctl server:deploy --che-operator-cr-patch-yaml=patch.yaml ...
```
```
$ crwctl server:deploy --che-operator-cr-patch-yaml=patch.yaml ...
```
Copy to Clipboard Toggle word wrap

patch.yaml should contain the following to make the Operator skip deploying a database and pass connection details of an existing database to a CodeReady Workspaces server:

spec:
  database:
    externalDb: true
    chePostgresHostName: <hostname>                     
    chePostgresPort: <port>                             
    chePostgresSecret: <server-database-credentials>    
    chePostgresDb: <database>                           
spec:
  auth:
    identityProviderPostgresSecret: <identity-database-credentials>

spec:
  database:
    externalDb: true
    chePostgresHostName: <hostname>


    chePostgresPort: <port>


    chePostgresSecret: <server-database-credentials>


    chePostgresDb: <database>


spec:
  auth:
    identityProviderPostgresSecret: <identity-database-credentials>

Copy to Clipboard

Toggle word wrap

1: External database hostname
2: External database port
3: Secret name with CodeReady Workspaces server database credentials
4: CodeReady Workspaces server database name
5: Secret name with RH-SSO database credentials

Additional resources

8.2. Persistent Volumes backups
링크 복사

Persistent Volumes (PVs) store the CodeReady Workspaces workspace data similarly to how workspace data is stored for desktop IDEs on the local hard disk drive.

To prevent data loss, back up PVs periodically. The recommended approach is to use storage-agnostic tools for backing up and restoring OpenShift resources, including PVs.

8.2.1. Recommended backup tool: Velero
링크 복사

Velero is an open-source tool for backing up OpenShift applications and their PVs. Velero allows you to:

Deploy in the cloud or on premises.
Back up the cluster and restore in case of data loss.
Migrate cluster resources to other clusters.
Replicate a production cluster to development and testing clusters.

Note

Alternatively, you can use backup solutions dependent on the underlying storage system. For example, solutions that are Gluster or Ceph-specific.

Additional resources

맨 위로 이동

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 8. Backup and disaster recovery

8.1. External database setup
링크 복사

8.1.1. Configuring external PostgreSQL
링크 복사

8.1.2. Configuring CodeReady Workspaces to work with an external PostgreSQL
링크 복사

8.2. Persistent Volumes backups
링크 복사

8.2.1. Recommended backup tool: Velero
링크 복사

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat 소개

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 8. Backup and disaster recovery

8.1. External database setup링크 복사링크가 클립보드에 복사되었습니다!

8.1.1. Configuring external PostgreSQL링크 복사링크가 클립보드에 복사되었습니다!

8.1.2. Configuring CodeReady Workspaces to work with an external PostgreSQL링크 복사링크가 클립보드에 복사되었습니다!

8.2. Persistent Volumes backups링크 복사링크가 클립보드에 복사되었습니다!

8.2.1. Recommended backup tool: Velero링크 복사링크가 클립보드에 복사되었습니다!

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat 소개

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

8.1. External database setup
링크 복사

8.1.1. Configuring external PostgreSQL
링크 복사

8.1.2. Configuring CodeReady Workspaces to work with an external PostgreSQL
링크 복사

8.2. Persistent Volumes backups
링크 복사

8.2.1. Recommended backup tool: Velero
링크 복사