Backup strategies in Linux CLI - Step-by-Step Execution

Concept Flow - Backup strategies

Identify data to backup

↓

Choose backup type

↓

Full backup

↓

Store backup

↓

Verify backup

↓

Schedule backups

↓

Restore test

This flow shows how to select data, choose backup type, store backups, verify them, schedule regular backups, and test restores.

Execution Sample

Linux CLI

rsync -av /home/user/data/ backup_full_2024/
rsync -av --link-dest=backup_full_2024/ /home/user/data/ backup_incremental_2024/
ls backup_full_2024 backup_incremental_2024/

This script creates a full backup, then an incremental backup using rsync, and lists the backup files.

Execution Table

Step	Command	Action	Result/Output
1	rsync -av /home/user/data/ backup_full_2024/	Create full backup	backup_full_2024/ created
2	rsync -av --link-dest=backup_full_2024/ /home/user/data/ backup_incremental_2024/	Create incremental backup referencing full backup	Files copied or linked, incremental backup created
3	ls backup_full_2024 backup_incremental_2024/	List backup files	backup_full_2024 file1 file2 ...
4	Verify backup integrity	Check backup files exist and are readable	All files verified
5	Schedule backups with cron	Set automatic backup times	Cron job added
6	Test restore from backup	Restore files to test location	Files restored successfully
7	Exit	Backup process complete	No errors

💡 Backup and verification steps complete successfully

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
backup_full_2024/	does not exist	created	exists	exists	exists
backup_incremental_2024/	does not exist	does not exist	created	exists	exists
cron job	not set	not set	not set	set	set
restore test	not done	not done	not done	not done	done

Key Moments - 3 Insights

Why do we create a full backup before incremental backups?

The full backup contains all data needed. Incremental backups only save changes since the last full backup, so the full backup is the base. See execution_table steps 1 and 2.

What does the --link-dest option in rsync do?

It tells rsync to hard link unchanged files from the full backup to save space, making incremental backups efficient. This is shown in step 2.

Why is testing the restore important after backups?

Backups are useless if you cannot restore data. Testing ensures backups are valid and restorable, as shown in step 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after step 2?

A Full backup compressed file created

B Incremental backup created with files copied or linked

C Backup files listed

D Cron job scheduled

💡 Hint

Check the 'Result/Output' column for step 2 in execution_table

At which step is the backup integrity verified?

A Step 3

B Step 5

C Step 4

D Step 6

💡 Hint

Look for 'Verify backup integrity' in the 'Command' column

If the full backup file is missing, what happens to the incremental backup?

A Incremental backup cannot be restored properly

B Incremental backup becomes a full backup

C Incremental backup still works independently

D Backup schedule stops

💡 Hint

Refer to key_moments about the importance of full backup as base

Concept Snapshot

Backup strategies:
- Start with a full backup (all data)
- Use incremental backups to save changes
- Store backups safely
- Verify backups regularly
- Schedule automatic backups
- Test restore to ensure data safety

Full Transcript

Backup strategies involve first identifying the data to save. Then, create a full backup that contains all files. After that, incremental backups save only changes since the last full backup, saving space and time. Tools like tar and rsync help create these backups. The --link-dest option in rsync links unchanged files to avoid duplication. After backups, verify files exist and are readable. Schedule backups automatically using cron jobs. Finally, test restoring files to confirm backups work. This process ensures data is safe and recoverable.