Backup The Pc System Simple .
Posted 2023-05-22 05:19:24 by Public and Osamu Aoki ‐ 5 min read
Keep up your with your shalat waktu & backup the PC system simple .
Keep your backup system simple and backup your system often. Having backup data is more important than how technically good your backup method is.
-
Knowing what to backup and recover.
-
Data files directly created by you: data in "
~/" -
Data files created by applications used by you: data in "
/var/" (except "/var/cache/", "/var/run/", and "/var/tmp/") -
System configuration files: data in "
/etc/" -
Local programs: data in "
/usr/local/" or "/opt/" -
System installation information: a memo in plain text on key steps (partition, …)
-
Proven set of data: confirmed by experimental recovery operations in advance
-
Cron job as a user process: files in "
/var/spool/cron/crontabs" directory and restartcron(8). See Section 9.4.14, “Scheduling tasks regularly” forcron(8) andcrontab(1). -
Systemd timer jobs as user processes: files in "
~/.config/systemd/user" directory. Seesystemd.timer(5) andsystemd.service(5). -
Autostart jobs as user processes: files in "
~/.config/autostart" directory. See Desktop Application Autostart Specification.
-
-
-
Knowing how to backup and recover.
-
Secure storage of data: protection from overwrite and system failure
-
Frequent backup: scheduled backup
-
Redundant backup: data mirroring
-
Fool proof process: easy single command backup
-
-
Assessing risks and costs involved.
-
Risk of data when lost
-
Data should be at least on different disk partitions preferably on different disks and machines to withstand the filesystem corruption. Important data are best stored on a read-only filesystem. [4]
-
-
Risk of data when breached
-
Sensitive identity data such as "
/etc/ssh/ssh_host_*_key", "~/.gnupg/*", "~/.ssh/*", "~/.local/share/keyrings/*", "/etc/passwd", "/etc/shadow", "popularity-contest.conf", "/etc/ppp/pap-secrets", and "/etc/exim4/passwd.client" should be backed up as encrypted. [5] (See Section 9.9, “Data encryption tips”.) -
Never hard code system login password nor decryption passphrase in any script even on any trusted system. (See Section 10.3.6, “Password keyring”.)
-
-
Failure mode and their possibility
-
Hardware (especially HDD) will break
-
Filesystem may be corrupted and data in it may be lost
-
Remote storage system can't be trusted for security breaches
-
Weak password protection can be easily compromised
-
File permission system may be compromised
-
-
Required resources for backup: human, hardware, software, …
-
Automatic scheduled backup with cron job or systemd timer job
-
-
Keep your backup system simple and backup your system often. Having backup data is more important than how technically good your backup method is.