Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ sidebar_class_name: host-nodes private-nodes standalone

You can use [Velero](https://velero.io/) to back up virtual clusters.

Ensure your cluster supports [volume snapshots](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) to allow Velero to backup persistent volumes and persistent volume claims that save the virtual cluster state. Alternatively, you can use [Velero's restic integration](https://velero.io/docs/v1.9/restic/) to back up the virtual cluster state.
Ensure your cluster supports [volume snapshots](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) to allow Velero to backup persistent volumes and persistent volume claims that save the virtual cluster state. Alternatively, you can use [Velero's file system backup](https://velero.io/docs/main/file-system-backup/) with the Node Agent to back up the virtual cluster state.

### Back up a vCluster

Expand Down Expand Up @@ -81,23 +81,23 @@ You can use Velero inside vCluster to protect your workloads and data. To use Ve
2. After enabling `hostpath-mapper`, install the Velero CLI (as described above), connect to your vCluster, and install Velero inside the virtual cluster:

```bash title="Velero inside the virtual cluster"
velero install --provider <provider> --bucket <bucket_name> --secret-file <your_secret_file> --plugins velero/velero-plugin-for-<provider>:<semver> --use-restic
velero install --provider <provider> --bucket <bucket_name> --secret-file <your_secret_file> --plugins velero/velero-plugin-for-<provider>:<semver> --use-node-agent
```

:::note
Replace `provider`, `bucket_name`, `secret-file`, and other placeholders with the correct values for your environment.
Replace `provider`, `bucket_name`, `secret-file`, and other placeholders with the correct values for your environment. Velero uses Kopia as the default file system backup tool.
:::

3. After installation is complete, check the status of the Velero resources:

```bash title="Verify the status of the Velero resources"
$ kubectl get all -n velero
NAME READY STATUS RESTARTS AGE
pod/restic-5szkb 1/1 Running 0 118s
pod/node-agent-5szkb 1/1 Running 0 118s
pod/velero-75c5479dfd-4x7sl 1/1 Running 0 118s

NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/restic 1 1 1 1 1 <none> 118s
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/node-agent 1 1 1 1 1 <none> 118s

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/velero 1/1 1 1 119s
Expand All @@ -106,10 +106,10 @@ You can use Velero inside vCluster to protect your workloads and data. To use Ve
replicaset.apps/velero-75c5479dfd 1 1 1 119s
```

4. Create a backup using `restic`:
4. Create a backup using file system backup:

```bash title="Create a backup with restic"
velero backup create test1 --default-volumes-to-restic
```bash title="Create a backup with file system backup"
velero backup create test1 --default-volumes-to-fs-backup
```

5. Wait for the backup to complete. Once complete, you should see the following output:
Expand Down