LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated Linux-Complete-Backup-and-Recovery-HOWTO-REWRITE.adoc

This commit is contained in:
Jason S. Evans 2016-02-24 16:12:46 +01:00
parent 0ab3e99332
commit 0a268e330e
1 changed files with 28 additions and 128 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

156
LDP/users/Jason-Evans/Linux-Complete-Backup-and-Recovery-HOWTO-REWRITE.adoc
View File

@ -12,37 +12,14 @@ Outline:
***** Flickr
*** NAS/File Server
*** Physical Media
** Device Level & LVM
*** LVM -- https://www.howtoforge.com/linux_lvm_snapshots, http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html,
** Virtualization
== Revision History
[cols="<,<,<,<",options="header",]
|==========================================================================================================================================================
|Revision |Date |Person |Note
|Revision 3.0 |2016-02-24 |Revised by: Jason Evans |Complete rewrite
|Revision 3.0 |2016-02-24 |Revised by: Jason Evans |Complete rewrite which reorganized the document and added new technologies and deleted some of the old in order to keep the guide up to date.
|Revision 2.1 |2006-03-28 |Revised by: c^2 |Added notes for NTFS. Edited the To Do list. Started work on LVM and using http://www.finnix.org/[finnix].
|Revision 2.0 |2005-10-12 |Revised by: c^2 |Notes for Fedora Core 4. Removed notes for older versions of FC and Red Hat. Also, changes in the writeup and scripts to reflect using http://www.knoppix.org/[Knoppix] instead of http://www.toms.net/rb[tomsrtbt]. See the scripts for change notes. Changed some scripts so that long lines don't fall off the right side of printed pages (oops).
|Revision 1.8 |2005-02-19 |Revised by: c^2 |Added notes for Fedora Core 3
@ -56,137 +33,60 @@ Outline:
|Revision 1.0 |2002-07-24 |Revised by: c^2 |We now use bz2 compression in the first stage, have the run time option to check for bad blocks, and have a script that runs the entire first stage.
|==========================================================================================================================================================
[[intro]]
Introduction
------------
== Introduction
The normal bare metal restoration process is: install the operating system from the product disks. Install the backup software, so you can restore your data. Restore your data. Then you get to restore functionality by verifying your configuration files, permissions, etc.
The purpose of this document is to provide strategies for backing up individual files in a desktop or server configuration. This document will discuss backing up files using scripts and apps; putting the backups on a range of resources from file servers and NAS, Cloud storage, and physical media; and restoring the backed up files. This document will apply to physical servers and to virtual machines.
The process and scripts explained in this HOWTO will save re-installing the operating system. The process explained here will restore only files that were backed up from the production computer. Your configuration will be intact when you restore the system, which should save you hours of verifying configurations and data.
[[copyright]]
Copyright Information
~~~~~~~~~~~~~~~~~~~~~
== License Information
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
[[disclaimers]]
Disclaimers
~~~~~~~~~~~
== Disclaimers
No liability for the contents of this documents can be accepted by the
author, the http://www.tldp.org/[Linux Documentation Project] or anyone
else. Use the concepts, examples and other content at your own risk.
There may be errors and inaccuracies that may damage your system.
Proceed with caution, and, although errors are unlikely, the author take
no responsibility for them.
No liability for the contents of this documents can be accepted by the author, the http://www.tldp.org/[Linux Documentation Project] or anyone else. Use the concepts, examples and other content at your own risk. There may be errors and inaccuracies that may damage your system.
Proceed with caution, and, although errors are unlikely, the author take no responsibility for them.
All copyrights are held by their by their respective owners, unless
specifically noted otherwise. Use of a term in this document should not
be regarded as affecting the validity of any trademark or service mark.
All copyrights are held by their by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark.
Naming of particular products or brands should not be seen as
endorsements.
Naming of particular products or brands should not be seen as endorsements.
You are strongly recommended to take a backup of your system before
major installation and backups at regular intervals. In addition, you
are strongly recommended to use a sacrificial experimental computer when
mucking with the material, especially the scripts, in this HOWTO.
You are strongly recommended to take a backup of your system before major installation and backups at regular intervals. In addition, you are strongly recommended to use a sacrificial experimental computer when mucking with the material, especially the scripts, in this HOWTO.
== Credits
Thanks to Larisa Alekseeva for your guidance and help and to the Triangle Linux Users Group for helping me get started in Linux.
[[newversions]]
New Versions
~~~~~~~~~~~~
This document is derived from two articles originally published in http://www.linuxjournal.com/[Linux Journal]. My thanks to Linux Journal for reverting the rights to those articles, thereby helping make this HOWTO possible.
[cols="^,^,^",]
|=============================================================================
|15.1.2016 |v1.0 Converted and edited for TLDP |Jason Evans
|15.2.2016 |v1.1 Changed format to asciidoc and made corrections |Jason Evans
|=============================================================================
Thanks to Joy Y. Goodreau for excellent HOWTO editing, and to David Palomares for correcting the spelling of Salvador DalITILDE's name.
You can find this document at its link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO.html[home page] or at the http://www.tldp.org/[Linux Documentation Project] web site in many formats. Please comment to
Also, thanks to mailto:pon at iki dot fi[Pasi Oja-Nisula] for a bug fix and information on http://www.knoppix.org/[Knoppix].
Depending on your browser, you may have to hold down the shift button while you click on these in order to get them to download.
== Feedback
* link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO.chunky.html.tar.bz2[bzip2 compressed chunky (lots of small pages. Faster reading.) HTML].
* link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO.smooth.html.tar.bz2[bzip2 compressed smooth (one monster page -- no chunks. Easier to search.) HTML].
* link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO.ps.bz2[bzip2 compressed postscript (US letter format)].
* link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO.pdf.bz2[bzip2 compressed PDF (US letter format)].
* link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO.txt.bz2[bzip2 compressed raw ASCII text].
* Use the link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO.tar.bz2[source], Luke.
* link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/md5sums[MD5] and link:&myurl;/Linux-Complete-Backup-and-Recovery-HOWTO/sha1sums[SHA1] sums.
Feedback is most certainly welcome for this document. Without your corrections, suggestions and other input, this document wouldn't exist. Please send your additions, comments and criticisms to me at: .
To ensure that you got a good download, validate the files against the
checksums above. The easiest way to do this is to pull in the sha1sum or
md5sum files (or both), and run the appropriate program against it:
....
$ sha1sum -c sha1sums
....
or/and
....
$ md5sum -c md5sums
....
[[credits]]
Credits
~~~~~~~
This document is derived from two articles originally published in
http://www.linuxjournal.com/[Linux Journal]. My thanks to Linux Journal
for reverting the rights to those articles, thereby helping make this
HOWTO possible.
Thanks to Joy Y. Goodreau for excellent HOWTO editing, and to David
Palomares for correcting the spelling of Salvador DalITILDE's name.
Also, thanks to mailto:pon at iki dot fi[Pasi Oja-Nisula] for a bug fix
and information on http://www.knoppix.org/[Knoppix].
[[feedback]]
Feedback
~~~~~~~~
Feedback is most certainly welcome for this document. Without your
corrections, suggestions and other input, this document wouldn't exist.
Please send your additions, comments and criticisms to me at: .
[[translations]]
Translations
~~~~~~~~~~~~
== Translations
Not everyone speaks English. Volunteers are welcome.
[[Overview]]
Overview
--------
== Overview
The process shown below is not easy, and can be hazardous to your data.
Practice it before you need it! Do as I did, and __practice on a
sacrificial computer__!
The original target computer for this HOWTO was a Pentium computer.
Originally, it had a http://www.redhat.com[Red Hat] 7.1 Linux server or
workstation installation on one IDE hard drive. Since then, I have used
a number of computers, and they have been ugraded to Red Hat 8.0 and
http://fedora.redhat.com/[Fedora Cores 1, 3 and 4.]. The target computer
does not have vast amounts of data because the computer was set up as a
``sacrificial'' test bed. That is, I did not want to test this process
with a production computer and production data. Also, I did a fresh
installation before I started the testing so that I could always
re-install if I needed to revert to a known configuration.
The process shown below is not easy, and can be hazardous to your data. Practice it before you need it! Do as I did, and __practice on a sacrificial computer__!
The original target computer for this HOWTO was a Pentium computer. Originally, it had a http://www.redhat.com[Red Hat] 7.1 Linux server or workstation installation on one IDE hard drive. Since then, I have used a number of computers, and they have been ugraded to Red Hat 8.0 and
http://fedora.redhat.com/[Fedora Cores 1, 3 and 4.]. The target computer does not have vast amounts of data because the computer was set up as a ``sacrificial'' test bed. That is, I did not want to test this process with a production computer and production data. Also, I did a fresh
installation before I started the testing so that I could always re-install if I needed to revert to a known configuration.
___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
*Note*
The sample commands will show, in most cases, what I had to type to
recover the target system. You may have to use similar commands, but
with different parameters. It is up to you to be sure you duplicate your
setup, and not the test computer's setup.
___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
The basic procedure is set out in W. Curtis Preston,
http://www.oreilly.com/catalog/unixbr/[Unix Backup & Recovery], O'Reilly