Update backup-restore docs

Author: deniseschannon

vcluster/manage/backup-restore.mdx

@@ -4,7 +4,7 @@ sidebar_label: Snapshot & Restore
 sidebar_position: 3
 ---
 
-There is multiple ways how to backup and restore a virtual cluster. vCluster provides a way to create a vCluster snapshot and restore the snapshot via its own CLI.
+There are multiple ways how to backup and restore a virtual cluster. vCluster provides a way to create a vCluster snapshot and restore the snapshot via its own CLI.
 
 :::warning
 If you are using an external database like MySQL or Postgresql that is **not** running inside the same namespace as vCluster, you need to create a separate backup for the datastore as well. Please refer to the appropriate docs for doing that.
@@ -13,27 +13,27 @@ If you are using an external database like MySQL or Postgresql that is **not** r
 ## Using vCluster CLI
 
 :::info
-This method requires vCluster version v0.24.0 or higher
+Only supported in vCluster v0.24.0+
 :::
 
-The easiest and recommended way to backup the etcd datastore of a vCluster is through the CLI. When using the CLI, vCluster creates a new pod to save the snapshot to the specified location. vCluster automatically determines the configured backing store. The following information is snapshotted:
+The recommended way to back up the etcd datastore of a vCluster is through the CLI. When using the CLI, vCluster creates a new pod to save the snapshot to the specified location. vCluster automatically determines the configured backing store. The following information is snapshotted:
 * Backing store data (e.g. etcd, sqlite)
 * vCluster helm release information
 * vCluster configuration (e.g. vcluster.yaml)
 
 :::info
-Currently the vCluster CLI backup method does not support backing up persistent volumes. If you require that please take a look at the velero backup method below.
+Currently the vCluster CLI backup method does not support backing up persistent volumes. If you are using persistent volumes in your virtual cluster, use the velero backup method below.
 :::
 
 ### Snapshot URL
 
 vCluster uses a snapshot URL to save the snapshot to a specific location. The snapshot URL is a string that contains the following information:
 
-* The protocol to use (e.g. `oci`, `s3`, `container`)
-* The location to save the snapshot (e.g. `oci://ghcr.io/my-user/my-repo:my-tag`, `s3://my-s3-bucket/my-snapshot-key`, `container:///data/my-snapshot.tar.gz`)
-* Optional flags to pass to the snapshot location (e.g. `skip-client-credentials=true`)
+* Protocol to use to take the snapshot (e.g. `oci`, `s3`, `container`)
+* Location to save the snapshot (e.g. `oci://ghcr.io/my-user/my-repo:my-tag`, `s3://my-s3-bucket/my-snapshot-key`, `container:///data/my-snapshot.tar.gz`)
+* Optional parameters to pass to the snapshot location (e.g. `skip-client-credentials=true`)
 
-The following protocols are supported:
+### Supported Protocols
 
 * `oci` - OCI image registry (e.g. docker hub or ghcr.io)
 * `s3` - s3 compatible bucket (e.g. AWS S3 or minio)
@@ -46,32 +46,53 @@ vcluster snapshot my-vcluster "oci://ghcr.io/my-user/my-repo:my-tag"
 
 #### oci
 
-The following flags are supported for the `oci` protocol:
+Snapshots can be saved to an OCI image registry. 
+
+Example:
+
+```bash
+echo $PASSWORD_ACCESS_TOKEN | docker login ghcr.io -u $USERNAME --password-stdin
+vcluster snapshot my-vcluster "oci://ghcr.io/my-user/my-repo:my-tag"
+```
+
+Alternative Options: Pass credentials as URL parameters.
+
 * `username` - The username to use to authenticate with the OCI image registry
 * `password` - The base64 encoded password to use to authenticate with the OCI image registry
 * `skip-client-credentials` - Do not use the local credentials to authenticate with the OCI image registry
 
-Example how to create a snapshot to an OCI image registry:
+Example with alternative options:
+
 ```bash
-vcluster snapshot my-vcluster "oci://ghcr.io/my-user/my-repo:my-tag"
+export OCI_USERNAME=my-username
+export OCI_PASSWORD=$(echo -n "my-password" | base64)
+vcluster snapshot my-vcluster "oci://ghcr.io/my-user/my-repo:my-tag?username=$OCI_USERNAME&password=$OCI_PASSWORD&skip-client-credentials=true"
 ```
 
 #### s3
 
-The following flags are supported for the `s3` protocol:
+Snapshots can be saved to a s3 compatible bucket.
+
+Example:
+
+```bash
+# 1. Login to AWS CLI to set your environment variables
+# 2. Take your snapshot
+vcluster snapshot my-vcluster "s3://my-s3-bucket/my-bucket-key"
+```
+
+Alternative Options: Pass credentials as URL parameters.
+
 * `access-key-id` - The base64 encoded access key id to use to authenticate with the s3 compatible bucket
 * `secret-access-key` - The base64 encoded secret access key to use to authenticate with the s3 compatible bucket
 * `session-token` - The base64 encoded session token to use to authenticate with the s3 compatible bucket
 * `region` - The region of the s3 compatible bucket
 * `profile` - The profile to use to authenticate with the s3 compatible bucket
 * `skip-client-credentials` - Do not use the local credentials to authenticate with the s3 compatible bucket
 
-Example how to create a snapshot to an s3 compatible bucket:
-```bash
-vcluster snapshot my-vcluster "s3://my-s3-bucket/my-bucket-key"
-
+Example with alternative options:
 
- # with custom credetials
+```bash
  export ACCESS_KEY_ID=$(cat my-access-key-id.txt | base64)
  export SECRET_ACCESS_KEY=$(cat my-secret-access-key.txt | base64)
  export SESSION_TOKEN=$(cat my-session-token.txt | base64)
@@ -80,8 +101,12 @@ vcluster snapshot my-vcluster "s3://my-s3-bucket/my-bucket-key"
 
 #### container
 
-Example how to create a snapshot to the vCluster container:
+Snapshots can be saved to a local file inside the vCluster container or another PVC. 
+
+Example:
+
 ```bash
+# Saved to the vCluster container
 vcluster snapshot my-vcluster "container:///data/my-snapshot.tar.gz"
 ```
 
@@ -95,7 +120,7 @@ vcluster snapshot my-vcluster "oci://ghcr.io/my-user/my-repo:my-tag"
 # create an OCI snapshot and mount an external image pull secret
 vcluster snapshot my-vcluster "oci://ghcr.io/my-user/my-repo:my-tag?skip-client-credentials=true" --pod-image-pull-secret=my-image-pull-secret
 
-# create an s3 snapshot
+# create an s3 snapshot 
 vcluster snapshot my-vcluster "s3://my-s3-bucket/my-snapshot-key"
 
 # create a snapshot to local vCluster pvc (if using embedded storage)