No problem on Garuda Linux

:wink:

Timeshift-Autosnap is your friend. :slight_smile:

For more security I backup my /@home data with rsync.

rsync -Hrtpgoahhupv --stats --delete --delete-excluded --exclude-from="/home/sgs/.local/bin/exclrsync" --log-file="/home/sgs/rsync/rsync.log.$dd" $from $to

I am always open for suggestions for improvement :wink:

4 Likes

Until a few years ago i ran openSUSE Tumbleweed for 5 months. For maybe 3 of those months i used btrfs, & ergo its Snapper-Rollback capability for its system files. I used luckyBackup for my data, then later replaced it with BackInTime.

From oS TW to Manjaro, with ext4, & this was when i started using Timeshift for system files. Still used BackInTime for my data.

Now using Arch, but still with Timeshift for system files & BackInTime for my data.


In various fora over the past few years i have read advice by some people, regarding Timeshift, that i consider to be very bad. Some people think they can use Timeshift for both their system AND data backups. IMO this is extremely dangerous – if ever they choose/need to restore an older TS snapshot, they will be returning not only to the older system files BUT ALSO to all their data as existed when the snapshot was taken. That is, all their data that changed or was added afterwards, will be completely lost.

I shall not make a blanket statement that one might not be able to somehow workaround the hazard. All i will say is that if one blindly uses only TS, for everything, with no clever workaround, then they will eventually lose data. IMO the better policy is:

  • TS for system
  • BiT [etc] for data
3 Likes