Configuring a Host Path Storage Destination

This topic describes how to install Velero and configure a host path as your storage destination for backups.

note

If Velero is already installed, you can update your storage destination in the admin console.

For Kubernetes installer clusters with the Velero add-on, you must update the default internal storage settings in the admin console because internal storage is insufficient for full backups.

For more information about updating storage, see Updating Settings in the Admin Console.

Prerequisites

Complete the following items before you perform this task:

• Review the limitations and considerations. See Limitations and Considerations in About Backup and Restore.

• Install the velero CLI. See Installing the Velero CLI.

• The host path must be a dedicated directory. Do not use a partition used by a service like Docker or Kubernetes for ephemeral storage.

• The host path must exist and be writable by the user:group 1001:1001 on all nodes in the cluster. For example, in a Linux environment you might run sudo chown -R 1001:1001 /backups to change the user:group permissions.

  If you use a mounted directory for the storage destination, such as one that is created with the Common Internet File System (CIFS) or Server Message Block (SMB) protocols, ensure that you configure the user:group 1001:1001 permissions on all nodes in the cluster and from the server side as well.

  You cannot change the permissions of a mounted network shared filesystem from the client side. To reassign the user:group to 1001:1001 for a directory that is already mounted, you must remount the directory. For example, for a CIFS mounted directory, specify the uid=1001,gid=1001 mount options in the CIFS mount command.

Install Velero and Configure Host Path Storage in Online Environments

To install Velero and configure host path storage in online environments:

1. Run one of the following commands to install Velero, depending on the version of the velero CLI you are using:

   • Velero v1.10 and later:

     velero install \
       --no-default-backup-location \
       --no-secret \
       --use-node-agent --uploader-type=restic \
       --use-volume-snapshots=false \
       --plugins velero/velero-plugin-for-aws:v1.5.3

   • Velero versions earlier than v1.10:

     velero install \
       --no-default-backup-location \
       --no-secret \
       --use-restic \
       --use-volume-snapshots=false \
       --plugins velero/velero-plugin-for-aws:v1.5.3

2. Configure the Restic DaemonSet specification if your cluster uses one of the following Kubernetes distributions:

   • RancherOS
   • OpenShift
   • Microsoft Azure
   • VMware Tanzu Kubernetes Grid Integrated Edition

   For information about how to configure the Restic DaemonSet for these distributions, see Configure Restic DaemonSet spec in the Velero documentation.

3. Run the following command to configure the host path storage destination:

   kubectl kots velero configure-hostpath --namespace NAME --hostpath /PATH

   Replace:

   • NAME with the namespace where the admin console is installed and running
   • PATH with the path to the directory where the backups will be stored

   For more information about required storage destination flags, see velero in Reference.

Install Velero and Configure Host Path Storage in Air Gapped Environments

To install Velero and configure host path storage in air gapped environments:

1. Run velero version --client-only to check the version of the velero CLI that you installed as part of Installing the Velero CLI.

2. Run one of the following commands to install Velero, depending on the version of the velero CLI you are using:

   • Velero v1.10 and later:

     velero install \
       --no-default-backup-location \
       --no-secret \
       --use-node-agent --uploader-type=restic \
       --use-volume-snapshots=false \
       --plugins velero/velero-plugin-for-aws:v1.5.3

   • Velero versions earlier than v1.10:

     velero install \
       --no-default-backup-location \
       --no-secret \
       --use-restic \
       --use-volume-snapshots=false \
       --plugins velero/velero-plugin-for-aws:v1.5.3

   note

   It is typical for the velero and node-agent (restic) Pods to be in the ErrImagePull or ImagePullBackOff state after you run the velero install command because Velero does not support passing registry credentials during installation. In the app manager v1.94.0 and later, this situation resolves itself after you complete the instructions to configure the storage destination.

   If you are on an earlier version of app manager, Replicated recommends that you upgrade to app manager v1.94.0 or later. Otherwise, you must patch the Velero deployment manually and add the image pull secret to access the registry.

3. Configure the Restic DaemonSet specification if your cluster uses one of the following Kubernetes distributions:

   • RancherOS
   • OpenShift
   • Microsoft Azure
   • VMware Tanzu Kubernetes Grid Integrated Edition

   For information about how to configure the Restic DaemonSet for these distributions, see Configure Restic DaemonSet spec in the Velero documentation.

4. Run the following command to configure the host path storage destination:

   kubectl kots velero configure-hostpath \
     --namespace NAME \
     --hostpath /PATH \
     --kotsadm-registry REGISTRY_HOSTNAME \
     --kotsadm-namespace REGISTRY_NAMESPACE \
     --registry-username REGISTRY_USERNAME \
     --registry-password REGISTRY_PASSWORD

   Replace:

   • NAME with the namespace where the admin console is installed and running
   • PATH with the path to the directory where the backups will be stored
   • REGISTRY_HOSTNAME with the registry endpoint where the images are hosted
   • REGISTRY_NAMESPACE with the registry namespace where the images are hosted
   • REGISTRY_USERNAME with the username to use to authenticate with the registry
   • REGISTRY_PASSWORD with the password to use to authenticate with the registry

   For more information about required storage destination flags, see velero in Reference.

Configure Host Path Storage in the Admin Console

Alternatively, when the admin console and application are already installed, you can start in the admin console to install Velero and configure a host path storage destination.

To install Velero and configure host path storage for existing clusters:

1. From the admin console, click Snapshots > Settings and Schedule.

2. Click Add a new storage destination.

   The Add a new destination dialog opens and shows instructions for setting up Velero with different providers.

3. Click Host Path.

   

4. In the Configure Host Path dialog, enter the path to the directory where the backups will be stored. Click Get instructions.

   

   A dialog opens with instructions on how to set up Velero with the specified host path configuration.

5. Follow the steps in the dialog to install Velero and configure the storage destination.

   

6. Return to the admin console and either click Check for Velero or refresh the page to verify that the Velero installation is detected.

Next Steps

• (Existing Clusters Only) Configure Velero namespace access if you are using minimal RBAC. See Configuring Namespace Access and Memory Limit.
• (Optional) Increase the default memory limits. See Configuring Namespace Access and Memory Limit.
• Create or schedule backups. See Creating and Scheduling Backups.

Additional Resources

• Troubleshooting Backup and Restore