This page will walk you through the main steps required to manually back up and restore the state of a Pachyderm cluster in production. Details on how to perform those steps might vary depending on your infrastructure and cloud provider / on-premises setup. Refer to your provider’s documentation.
Pachyderm state is stored in two main places:
- An object-store holding Pachyderm’s data.
- A PostgreSQL instance made up of one or two databases:
pachydermholding Pachyderm’s metadata and
dexholding authentication data.
Backing up a Pachyderm cluster involves snapshotting both the object store and the PostgreSQL database(s), in a consistent state, at a given point in time.
Restoring it involves re-populating the database(s) and the object store using those backups, then recreating a Pachyderm cluster.
- Make sure that you have a bucket for backup use, separate from the object store used by your cluster.
- Depending on the reasons behind your cluster recovery, you might choose to use an existing vs. a new instance of PostgreSQL and/or the object store.
Manual Back Up Of A Pachyderm Cluster #
Before any manual backup:
- Make sure to retain a copy of the Helm values used to deploy your cluster.
- Then, suspend any state-mutating operations.
- Backups incur downtime until operations are resumed.
- Operational best practices include notifying Pachyderm users of the outage and providing an estimated time when downtime will cease.
- Downtime duration is a function of the size of the data be to backed up and the networks involved; Testing before going into production and monitoring backup times on an ongoing basis might help make accurate predictions.
Suspend Operations #
Pause any external automated process ingressing data to Pachyderm input repos, or queue/divert those as they will fail to connect to the cluster while the backup occurs.
Suspend all mutation of state by scaling
pachdand the worker pods down:
Before starting, make sure that your context points to the server you want to pause by running
pachctl config get active-context.
To pause Pachyderm:
If you are an Enterprise user: Run the
pachctl enterprise pausecommand.
Alternatively, you can use
Before starting, make sure that
kubectlpoints to the right cluster.
kubectl config get-contextsto list all available clusters and contexts (the current context is marked with a
kubectl config use-context <your-context-name>to set the proper active context.
kubectl scale deployment pachd --replicas 0 kubectl scale rc --replicas 0 -l suite=pachyderm,component=worker
Note that it takes some time for scaling down to take effect;
watchcommand to monitor the state of
pachdand worker pods terminating:
watch -n 5 kubectl get pods
Back Up The Databases And The Object Store #
This step is specific to your database and object store hosting.
If your PostgreSQL instance is solely dedicated to Pachyderm, you can use PostgreSQL’s tools, like
pg_dumpall, to dump your entire PostgreSQL state.
Alternatively, you can use targeted
pg_dumpcommands to dump the
dexdatabases, or use your Cloud Provider’s backup product. In any case, make sure to use TLS. Note that if you are using a cloud provider, you might choose to use the provider’s method of making PostgreSQL backups.
A production setting of Pachyderm implies that you are running a managed PostgreSQL instance.
- To back up the object store, you can either download all objects or
use the object store provider’s backup method.
The latter is preferable since it will typically not incur egress costs.
Resuming operations #
Once your backup is completed, resume your normal operations by scaling
pachd back up. It will take care of restoring the worker pods:
Enterprise users: run
pachctl enterprise unpause.
Alternatively, if you used
kubectl scale deployment pachd --replicas 1
Restore Pachyderm #
There are two primary use cases for restoring a cluster:
- Your data have been corrupted, preventing your cluster from functioning correctly. You want the same version of Pachyderm re-installed on the latest uncorrupted data set.
- You have upgraded a cluster and are encountering problems. You decide to uninstall the current version and restore the latest backup of a previous version of Pachyderm.
Depending on your scenario, pick all or a subset of the following steps:
- Populate new
dex(if required) databases on your PostgreSQL instance
- Populate a new bucket or use the backed-up object-store (note that, in that case, it will no longer be a backup)
- Create a new empty Kubernetes cluster and give it access to your databases and bucket
- Deploy Pachyderm into your new cluster
Restore The Databases And Objects #
- Restore PostgreSQL backups into your new databases using the appropriate method (this is most straightforward when using a cloud provider).
- Copy the objects from the backed-up object store to your new bucket or re-use your backup.
Deploy Pachyderm Into The New Cluster #
Finally, update the copy of your original Helm values to point Pachyderm to the new databases and the new object store, then use Helm to install Pachyderm into the new cluster.
Connect ‘pachctl’ To Your Restored Cluster #
And check that your cluster is up and running.