---
title: Charmhub | Deploy Infra Backup Operator using Charmhub - The Open Operator
  Collection
description: Deploy the latest version of Infra Backup Operator on any cloud.
url: https://charmhub.io/infra-backup-operator/docs/explanation
---

# Infra Backup Operator

[Canonical Kubernetes](https://charmhub.io/publisher/containers "View all packages from Canonical Kubernetes")

* [Canonical Kubernetes](https://charmhub.io/publisher/containers "View all packages from Canonical Kubernetes")

Platform:

24.04

edge 11

```
juju deploy infra-backup-operator --channel edge
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

---

#### Relevant links

* [Homepage](https://github.com/canonical/infra-backup-operator)

---

#### Contacts

* [Submit a bug](https://github.com/canonical/infra-backup-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

# Explanation

## [Backup etcd / dqlite](https://charmhub.io/infra-backup-operator/docs/explanation#p-38582-backup-etcd-dqlite)

The Infra Backup Operator does not create backups of the underlying datastore (such as etcd or dqlite). While regularly backing up these databases is a recommended best practice for cluster operators, Velero will still capture all the essential Kubernetes resources required to restore a functional cluster in the event of a disaster. What will be lost in such scenarios are transient data such as events, logs, and other ephemeral Kubernetes metadata that are not critical for cluster recovery.

## [Non-kubernetes api resources](https://charmhub.io/infra-backup-operator/docs/explanation#p-38582-non-kubernetes-api-resources)

Velero works just on Kubernetes API level. This means that any kind of customization of kube-apiserver, auditing or other third-parties tools configuration files like [Falco](https://falco.org/) won’t be under the protection of the backup using this tool.

## [Charm lifecycle](https://charmhub.io/infra-backup-operator/docs/explanation#p-38582-charm-lifecycle)

This charm does not install workloads and its functionality focuses on leveraging the velero-backups endpoint and continuously monitoring the namespaces configured for backup. Any change in the charm’s configuration or in the Kubernetes cluster is automatically reflected in the set of resources included in the backup. If the configuration specifies a namespace that does not yet exist, no error will be raised. Once that namespace is created, it will automatically be included in the backup process.

---