@cruunnerr I just noticed the question is not MM specific.

I have two Raspberries in production @home and I use raspiBackup which was mentioned already above by yawns to create backups every weekend - triggered by a crontask. I use rsync together with nfs and hardlinks to backup the whole systems and keep 12 backups (3 months). Hardlinks minimze the backup space used and reduce the backup time significantly because only new and changed data will be saved in every new backup. All constant data including the constant OS files will be saved only once and linked to in all backups created later on. To restore the backup I use my Linux box but you also can use your Raspberry running Raspbian if you don’t have a Linux box handy.
If you want to restore the backup from your Windows box you can create a dd backup with raspiBackup whi ch can be restored with win32diskimager. But then you don’t benefit from the nice rsync feature to use hardlinks and every backup run will save the whole SD card all the time and the backup will take much longer and you need more backup space.
I also should mention that you need an ext3 or ext4 filesystem on your backup space if you want to use hardlinks. You also can use a network drive connected via samba but then there is no hardlink support. But you can then create a tar backup which in general will be smaller than a dd backup.

@KirAsh4 In general I agree with you. Systems with an outdated level of security patches shouldn’t be used at all. They are welcome by botnets.

But if you create a backup on a regular base - let’s say every week - your backup will not be seriously vulnerable. If you have to restore the backup for any reasons the first activity has to be to update the OS to the latest security level and everything is fine. Even if the backup is a couple of months old this works. If the backup is older than one year the OS most probably is out of service and shouldn’t be used any more. So as long as you create a regular backup every month and keep only some older backup versions (e.g. 3) you’ll be fine.

But I also agree with you that depending on your OS experience you have you also can just save version.js on a regular base via rsync and setup the system from scratch to recover. But people with less OS experience who are happy they managed to setup and configured their box will be happy to just kick off the restore followed by ‘sudo apt-get update; sudo apt-get upgrade’ in order to recover.