Your Manila CephFS Share Backups Belong to S3

The presentation discusses the use of Kubernetes and shared file systems for storage and the backup process for manual SFS shares.

• Kubernetes is heavily used for storage, with around 65 projects deploying 159 production Kubernetes clusters storing around 74 terabytes of manual SFS storage
• Manual SFS is a scalable distributed storage system that offers three interfaces: object store, block devices, and shared file systems
• The presentation focuses on the backup process for manual SFS shares, which involves six steps: stopping the application, creating a snapshot, creating a volume from the snapshot, backing up the intermediate volume, and removing the volume and snapshot
• The backup process relies on the manual CSI driver, which handles cluster-wide and node-local operations
• The CSI driver relies on third-party drivers to carry out the mount on the node and expose it to the consumer ports

The presenter mentions that restoring 65 terabytes of data could take many hours, but there is no other way to recover lost data. They also mention the Canister project, which allows users to define their own workflows and declare specific needs for their applications.

Backups. Boring and mundane, until you lose your application data and need it back. Our Kubernetes users at CERN make extensive use of CephFS-backed storage managed by the OpenStack Manila service. Streamlining and automating the process of backups gives them a chance to prepare so that–should a disaster strike–they can recover. In this talk we will delve into the work we have done to make Velero, CephFS, Manila and an S3 store cooperate together, and bring an application back into life. Expect code snippets and demos. By the end of this session, you should have a clear overview of how each component contributes to our current backup and restore workflow in Kubernetes, and how you can integrate this setup into your clusters too.Click here to view captioning/translation in the MeetingPlay platform!