• 1 Post
  • 54 Comments
Joined 3 months ago
cake
Cake day: August 14th, 2024

help-circle

  • For ableton, you can run it in wine and it can work well enough to do things. It’s an OK experience at best and flat out doesn’t work at worst. Kiss your VST plugins goodbye with that though, gotta stick to the built ins which do all work when it’s working overall.

    Otherwise, check out bitwig studio, made by ex ableton devs and natively runs in Linux. Still gonna be hit or miss on 3rd party plugins but the app is on par with ableton as an experience. Price in the same range too. Best short explainer is ableton meets logic in terms of usability.










  • Borg backup is gold standard, with Vorta as a very nice GUI on machines that need it. Otherwise, all my other Linux machines are running in proxmox hypervisors and have container/snapshot/vm backups regularly through proxmox backup server to another machine. All the backup data is then replicated regularly, remotely via truenas scale replication tasks.









  • For clarity, the recommendation is specifically 3 copies of your data, not 3 backups.

    3-2-1 backup; 3 copies of the data, 2 types of storage devices, 1 off-site storage location.

    So in a typical homelab case you would have your primary hot data, the actual device being used to create and manage that data, your desktop. You’d regularly backup that data into warm storage such as a NAS with redundancy (raid Z1, Z2, etc). Followed by regular but slower intervals of backups to a remote location, such as a duplicate NAS with a secure tunnel or even an external drive(s) sitting at a friend or family member’s house, bank vault, wherever. That would be considered cold storage (and should be automated as such if it’s constantly powered).

    My own addition to this is that at least one of the hot / warm devices should be on battery backup in case of power events. I’ll always advocate that to be the primary machine but in homelab the server would be more important and the NAS would be part of that stack.

    Cloud is not considered a backup unless the data owner is also the storage owner, for general reliability reasons related to control over the system and storage. Cloud is, however, a reasonable temporary storage for moves and transfers.