5/20/2023 0 Comments Prune old backups duplicacy![]() The long and short of it though was Duplicati’s database methodology was just not able to handle the instability, which really isn’t totally Duplicati’s fault. This was compounded by an ongoing issue I have with the Asustor NAS, which I might write another post on. The speeds were better, around 10-15MB/s, but even though it was relatively stable, being able to run a full backup for 12 days straight still proved to be impossible. Setting up duplicati was easy, there was a k8s-at-home helm chart for it. Duplicati itself seemed okay, so I then tried running Duplicati as a workload on my k8s cluster. ![]() It would take over a month to back up my data at that rate, but in theory further backups would be incremental. I had issues with the Duplicati database and the backup ran at 5MB/s. I chose this because ideally it meant the only network traffic was egress to the storage backend from the NAS, which should have increased efficiency. I originally opted to use Duplicati, which was available as an app on the Asustor NAS. And thus begins my tale of how to back up the data on my Asustor NAS. The Asustor can also do external backups via rsync, but this proved insufficient for my needs. Snapshots are not backups but they are handy for restoring previous data, and being able to do it down to the file/folder level is great. Restoring data from these snapshots is simple, the snapshot itself can be opened like a folder by selecting “Preview” and files can be copied to/from the snapshot using the web interface. The Asustor has 2 volumes, one on SSDs and one on HDDs. I configured these backups, have restored from them before and generally had no issue with them. This is simple, but it doesn’t allow for manipulating or restoring individual files, so a restore basically restores the entire volume to an earlier state in time. Once it’s in place, you can spin your workload back up. Longhorn recreates the PVC and populates it with the data from the selected backup. To restore, you simply delete the local volume and select the backup as a source to recreate the volume. Restores are fairly simple, although they require downtime. Updates to the backups are incremental by only uploading blocks that have changed since the last backup. Longhorn backups are pretty simple, you point Longhorn to an S3 bucket and it backs up the volumes at the block level. And then I have an Asustor AS6510T which provides access to its storage via NFS, SMB, AFP etc. First, there’s Longhorn, which stores the data locally on the workers which is then replicated and served across the network node-to-node communication. I have two main ways of storing data in my environment. Note: This post was originally posted on my personal blog.
0 Comments
Leave a Reply. |