• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle







  • 3-2-1 means 3 copies total on 2 different media with 1 copy off-site. An easy way to implement would be make a local copy outside of your NAS/RAID(different NAS or external HDD) and create a copy of that somewhere in the cloud or hosting(backblaze for example)

    You should probably not look at your whole storage when thinking about Backup, but create different logical pools. For example I have 3 pools: media files, personal files&photos, app config files for my docker.

    I don’t backup the media files because I can reacquire them, I have a very strict backup policy for my personal files and a more relaxed policy for my config files.

    I use duplicacy to manage a local copy and a cloud copy and do restore tests sometimes. Duplicacy can also manage retention of its snapshots so I can keep years old versions of my personal files but only a few weeks worth of config












  • For the Microsoft SaaS, PaaS and Is as services you don’t have to worry about regular updates at all, it’s for the most part completely invisible to the customer unless someone screws up.

    There are some instances of planned maintenance where the customer can take action to assure smooth operations. In azure you can check/configure notifications under the “service health” menu. Upcoming planned maintenance or unplanned issues would show up here with instructions on what to do. Sometimes, but very rarely, there are maintenance tasks where your services might require a restart, you can then plan that restart yourself or get a rug pull on the deadline, usually 1-2 months after the notification.