Data backup and disaster planning: Difference between revisions

From HPCWIKI
Jump to navigation Jump to search
(Add categories: Linux, Reference)
(Fix: remove --- horizontal lines (7 removed))
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Linux]] systems are widely used in servers and critical infrastructure, ensuring rapid recovery from failures is paramount. This page dives deep into the essentials of Linux system recovery, offering insights into effective backup strategies and disaster planning.
{{Status
|status=Draft
|owner=Knowledge Agent
|last_update=2026-07-16
|review=Pending
}}
 
{{TOC}}
 
== Overview ==
 
Data backup and disaster planning에 대한 기술 문서입니다.
 
=== Summary ===
 
* 무엇인가? - Data backup and disaster planning
* 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
 
 
== Purpose ==
 
이 문서가 존재하는 이유
 
* Goal: Data backup and disaster planning에 대한 기술 정보 제공
* Scope: Data backup and disaster planning의 개념, 사용법, 설정
* Non-goals: 다른 주제로의 확장
 
 
== Key Concepts ==
 
{| class="wikitable"
! Concept
! Description
! Related
|-
| Data backup and disaster planning
| HPC/서버 환경에서 중요한 기술 개념
| [[Linux]], [[Server]]
|}
 


== Types of Failures Affecting Linux Systems ==
== Detailed Explanation ==


[[Linux]] systems are widely used in servers and critical infrastructure, ensuring rapid recovery from failures is paramount. This page dives deep into the essentials of Linux system recovery, offering insights into effective backup strategies and disaster planning.
* '''Hardware Failures''': These include issues like hard drive crashes, memory corruption, or power supply failures.
* '''Hardware Failures''': These include issues like hard drive crashes, memory corruption, or power supply failures.
* '''Software Issues''': Software failures may involve bugs, accidental deletion of critical files, or system misconfigurations.
* '''Software Issues''': Software failures may involve bugs, accidental deletion of critical files, or system misconfigurations.
* '''Human Error''': Often overlooked, human error such as incorrect commands or improper handling of data can lead to significant disruptions.
* '''Human Error''': Often overlooked, human error such as incorrect commands or improper handling of data can lead to significant disruptions.
* '''Natural Disasters''': Events like floods, earthquakes, or fires can cause physical damage to systems, necessitating robust disaster recovery plans.
* '''Natural Disasters''': Events like floods, earthquakes, or fires can cause physical damage to systems, necessitating robust disaster recovery plans.
== Backup Strategies for Linux Systems ==
=== '''Incremental vs. Full Backups''' ===
* '''Incremental Backups''' save changes made since the last backup, conserving storage space and reducing backup time. However, recovery can be slower as it may require a series of incremental backups to restore the latest state.
* '''Incremental Backups''' save changes made since the last backup, conserving storage space and reducing backup time. However, recovery can be slower as it may require a series of incremental backups to restore the latest state.
* '''Full Backups''' involve copying all data to the backup storage. They require more storage space and longer to complete but make recovery fast and straightforward.
* '''Full Backups''' involve copying all data to the backup storage. They require more storage space and longer to complete but make recovery fast and straightforward.
=== '''Local vs. Remote Backups''' ===
* '''Local Backups''' are stored on the same network or physical location as the primary system. They offer quick access and restoration capabilities. However, they are vulnerable to site-specific disasters like fires or power outages.
* '''Local Backups''' are stored on the same network or physical location as the primary system. They offer quick access and restoration capabilities. However, they are vulnerable to site-specific disasters like fires or power outages.
* '''Remote Backups''' are stored offsite and are crucial for recovering from natural disasters or major incidents affecting the primary site. They might introduce complexities in [[terms]] of data transfer speeds and access times.
* '''Remote Backups''' are stored offsite and are crucial for recovering from natural disasters or major incidents affecting the primary site. They might introduce complexities in [[terms]] of data transfer speeds and access times.
=== '''Automated Backups''' ===
Linux offers several tools for automating backups, such as rsync for data synchronization and cron for scheduling automatic backup tasks. Automation ensures backups are performed consistently without human intervention, reducing the risk of missed backups due to oversight.
Linux offers several tools for automating backups, such as rsync for data synchronization and cron for scheduling automatic backup tasks. Automation ensures backups are performed consistently without human intervention, reducing the risk of missed backups due to oversight.
=== 3-2-1 backup model<ref>https://www.tutorialspoint.com/linux_admin/linux_admin_backup_and_recovery.htm</ref> ===
'''3''' copies of data, '''2''' different backup mediums, '''1''' copy of data offsite. 3-2-1 model involves a multiphase ''bare metal restore'' and ''data recovery [[plan]] using following''
'''3''' copies of data, '''2''' different backup mediums, '''1''' copy of data offsite. 3-2-1 model involves a multiphase ''bare metal restore'' and ''data recovery [[plan]] using following''
* dd to make and restore production disk-images of configured servers for Block-by-Block Bare Metal Recovery Images
* dd to make and restore production disk-images of configured servers for Block-by-Block Bare Metal Recovery Images
* rsync to make incremental backups of all user data
* rsync to make incremental backups of all user data
Line 31: Line 59:
* tar & gzip and 7zip to store encrypted backups of files with passwords and notes from administrators. Commonly, this can be put on a USB drive, encrypted and locked in a safe that a Senior Manager access. Also, this ensures someone else will know vital security credentials if the current administrator wins the lottery and disappears to a sunny island somewhere. 7zip is installed and ready be used with 256-bit AES encryption for our tarball archives.
* tar & gzip and 7zip to store encrypted backups of files with passwords and notes from administrators. Commonly, this can be put on a USB drive, encrypted and locked in a safe that a Senior Manager access. Also, this ensures someone else will know vital security credentials if the current administrator wins the lottery and disappears to a sunny island somewhere. 7zip is installed and ready be used with 256-bit AES encryption for our tarball archives.
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
#7z encryption example - 7zip uses AES 256-bit encryption with an SHA-256 hash of the password and counter, repeated up to 512K times for key derivation. This should be secure enough if a complex key is used.
#7z encryption example - 7zip uses AES 256-bit encryption with an SHA-256 hash of the pass... [내용 계속]
$7z a -p <output filename><input filename>
where,
a: add to archive, and -p: encrypt and prompt for passphrase
</syntaxhighlight>


== Advanced Backup Techniques and Tools ==


=== '''Snapshot Technologies''' ===
== Best Practices ==
Filesystem snapshots, such as those offered by LVM (Logical Volume Manager), Btrfs or ZFS, provide a way to capture the state of a filesystem at a particular point in time. These can be incredibly useful for creating quick backups without downtime.


=== '''Cloud-based Backup Solutions''' ===
* 최신 버전 사용 권장
Leveraging cloud storage for backups provides flexibility and scalability. However, it’s vital to consider data security and [[privacy]] issues, ensuring that data is encrypted both in transit and at rest.
* 공식 문서 참고
* 테스트 환경에서 먼저 검증


=== '''Encryption and Security''' ===
Encrypting backup data is crucial to prevent unauthorized access. Use strong encryption standards and secure your backup locations physically and digitally.


== Tools ==
== References ==


* [https://relax-and-recover.org/ Relax-and-Recover (ReaR)] is a GPL licensed setup-and-forget ''Linux bare metal disaster recovery'' solution. It is easy to set up and requires no maintenance so there is no excuse for not using it. Orcle provides good usage and guide on [https://docs.oracle.com/en/operating-systems/oracle-linux/backup/backup-ol-backup-rear-about.html#ol-backup-rear-test this page.] With [https://drlm.org/about/ DRLM] you can, easily and centrally, deploy and manage ReaR installations for all your GNU/Linux systems in your DataCenter(s).
* [https://wiki.hpcmate.com Data backup and disaster planning]
* [https://www.portalprogramas.com/en/bera-backup.php Bera Backup] is a tool that makes back-up copies of folders and files of the server and of the server settings, everything necessary for '''restoring the original system exactly'''.<ref>https://github.com/oslcixug/bera-backup</ref>


== References ==
<references />
[[Category:Linux]]


[[Category:Reference]]
== Related Pages ==
 
* [[Linux]]
* [[Server]]
* [[Hardware]]
* [[Network]]
 
 
[[Category:Server]]
== Knowledge Graph ==
 
Related
 
→ [[Linux]]
→ [[Server]]
→ [[NFS]]
→ [[Glusterfs]]
→ [[ZFS]]
→ [[LVM]]
→ [[HBA/RAID controller]]
 
[[Category:Guide]]

Latest revision as of 11:28, 17 July 2026

Template:Status

Template:TOC

Overview

Data backup and disaster planning에 대한 기술 문서입니다.

Summary

  • 무엇인가? - Data backup and disaster planning
  • 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
  • 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시


Purpose

이 문서가 존재하는 이유

  • Goal: Data backup and disaster planning에 대한 기술 정보 제공
  • Scope: Data backup and disaster planning의 개념, 사용법, 설정
  • Non-goals: 다른 주제로의 확장


Key Concepts

Concept Description Related
Data backup and disaster planning HPC/서버 환경에서 중요한 기술 개념 Linux, Server


Detailed Explanation

Linux systems are widely used in servers and critical infrastructure, ensuring rapid recovery from failures is paramount. This page dives deep into the essentials of Linux system recovery, offering insights into effective backup strategies and disaster planning.

  • Hardware Failures: These include issues like hard drive crashes, memory corruption, or power supply failures.
  • Software Issues: Software failures may involve bugs, accidental deletion of critical files, or system misconfigurations.
  • Human Error: Often overlooked, human error such as incorrect commands or improper handling of data can lead to significant disruptions.
  • Natural Disasters: Events like floods, earthquakes, or fires can cause physical damage to systems, necessitating robust disaster recovery plans.
  • Incremental Backups save changes made since the last backup, conserving storage space and reducing backup time. However, recovery can be slower as it may require a series of incremental backups to restore the latest state.
  • Full Backups involve copying all data to the backup storage. They require more storage space and longer to complete but make recovery fast and straightforward.
  • Local Backups are stored on the same network or physical location as the primary system. They offer quick access and restoration capabilities. However, they are vulnerable to site-specific disasters like fires or power outages.
  • Remote Backups are stored offsite and are crucial for recovering from natural disasters or major incidents affecting the primary site. They might introduce complexities in terms of data transfer speeds and access times.

Linux offers several tools for automating backups, such as rsync for data synchronization and cron for scheduling automatic backup tasks. Automation ensures backups are performed consistently without human intervention, reducing the risk of missed backups due to oversight. 3 copies of data, 2 different backup mediums, 1 copy of data offsite. 3-2-1 model involves a multiphase bare metal restore and data recovery plan using following

  • dd to make and restore production disk-images of configured servers for Block-by-Block Bare Metal Recovery Images
  • rsync to make incremental backups of all user data
  • Cpio, copy in/out, is a file archiver utility to create and extract archives or copy files to another place.
  • tar & gzip and 7zip to store encrypted backups of files with passwords and notes from administrators. Commonly, this can be put on a USB drive, encrypted and locked in a safe that a Senior Manager access. Also, this ensures someone else will know vital security credentials if the current administrator wins the lottery and disappears to a sunny island somewhere. 7zip is installed and ready be used with 256-bit AES encryption for our tarball archives.

<syntaxhighlight lang="bash">

  1. 7z encryption example - 7zip uses AES 256-bit encryption with an SHA-256 hash of the pass... [내용 계속]


Best Practices

  • 최신 버전 사용 권장
  • 공식 문서 참고
  • 테스트 환경에서 먼저 검증


References


Related Pages

Knowledge Graph

Related

→ Linux → Server → NFS → Glusterfs → ZFS → LVM → HBA/RAID controller

Retrieved from "http://wiki.hpcmate.com/index.php?title=Data_backup_and_disaster_planning&oldid=3288"