14
5
Fork
You've already forked techstack-support
0

Backup solutions #5

Open
opened 2023年02月19日 21:49:15 +01:00 by fnetX · 4 comments
Owner
Copy link

In Codeberg-Infrastructure/planning#4 we tracked the creation of a new backup solution.

The current state is that we rsync-mirror updated repositories into an offsite location, and we are improving that experiment.

However, if someone has experience to suggest a more viable solution for our current tech stack (CephFS) and / or might even be available to produce them, please feel free to comment.

In https://codeberg.org/Codeberg-Infrastructure/planning/issues/4 we tracked the creation of a new backup solution. The current state is that we rsync-mirror updated repositories into an offsite location, and we are improving that experiment. However, if someone has experience to suggest a more viable solution for our current tech stack (CephFS) and / or might even be available to produce them, please feel free to comment.

with ceph you can mirror a pool between two ceph clusters. so having an backup/archive ceph-cluster would then ease the backup process.

Because rsync is Filebased, it will iterate over the whole file tree and trash all your caches while reading through everything. the Ceph-Pool-Mirror approach works on a lower level and only transfers the changed blocks.

with ceph you can mirror a pool between two ceph clusters. so having an backup/archive ceph-cluster would then ease the backup process. Because rsync is Filebased, it will iterate over the whole file tree and trash all your caches while reading through everything. the Ceph-Pool-Mirror approach works on a lower level and only transfers the changed blocks.
Author
Owner
Copy link

@iQ do you have some references at hand on how to get started? I didn't yet find some information on how we could mirror the CephFS (data and meta) pools.

@iQ do you have some references at hand on how to get started? I didn't yet find some information on how we could mirror the CephFS (data and meta) pools.

I can take care of deploying and maintaining Proxmox Backup based solution for data survivability.

For data availability the type of mirror proposed by @iQ sounds OK for guaranteeing data availability, but PBS can still be used for survivability.

I do it already in my daily work (1.5T data). I have a setup based in:

  • A main PBS server used for storing the backups
  • A second PBS server mirroring the backups from the main
  • A third copy (encrypted) stored in a couple of external USB btrfs raid1 drives

If interested, we can discuss the details in Matrix.

I can take care of deploying and maintaining Proxmox Backup based solution for data survivability. For data availability the type of mirror proposed by @iQ sounds OK for guaranteeing data availability, but PBS can still be used for survivability. I do it already in my daily work (1.5T data). I have a setup based in: - A main PBS server used for storing the backups - A second PBS server mirroring the backups from the main - A third copy (encrypted) stored in a couple of external USB btrfs raid1 drives If interested, we can discuss the details in Matrix.

@iQ do you have some references at hand on how to get started? I didn't yet find some information on how we could mirror the CephFS (data and meta) pools.

Depending on your usage, either CephFS Mirroring or RBD Mirroring was probably meant here.

> @iQ do you have some references at hand on how to get started? I didn't yet find some information on how we could mirror the CephFS (data and meta) pools. Depending on your usage, either [CephFS Mirroring](https://docs.ceph.com/en/latest/dev/cephfs-mirroring/#) or [RBD Mirroring](https://docs.ceph.com/en/latest/rbd/rbd-mirroring/#) was probably meant here.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg-Infrastructure/techstack-support#5
Reference in a new issue
Codeberg-Infrastructure/techstack-support
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?