diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.xml b/en_US.ISO8859-1/books/handbook/disks/chapter.xml index fcbe022a47..e27603357f 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.xml @@ -1621,18 +1621,18 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c - Hardware or software RAID, which minimizes or avoids - downtime when a disk fails. + Hardware or software RAID, which + minimizes or avoids downtime when a disk fails. - Typically, a mix of backup techniques is used. For - example, one could create a schedule to automate a weekly, full + Typically, a mix of backup techniques is used. For + example, one could create a schedule to automate a weekly, full system backup that is stored off-site and to supplement this backup with hourly ZFS snapshots. In addition, one could make a - manual backup of individual directories or files before making + manual backup of individual directories or files before making file edits or deletions. - + This section describes some of the utilities which can be used to create and manage backups on a &os; system. @@ -1651,47 +1651,47 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c The traditional &unix; programs for backing up a file - system are &man.dump.8;, which creates the backup, and + system are &man.dump.8;, which creates the backup, and &man.restore.8;, which restores the backup. These utilities - work at the disk block level, below the - abstractions of the files, links, and directories that are created - by file systems. Unlike other backup software, - dump backs up an entire file system and - is unable to backup only part of a file system or - a directory tree that spans multiple file systems. - Instead of writing files and directories, dump - writes the raw data blocks that comprise files and - directories. + work at the disk block level, below the abstractions of the + files, links, and directories that are created by file + systems. Unlike other backup software, + dump backs up an entire file system and is + unable to backup only part of a file system or a directory + tree that spans multiple file systems. Instead of writing + files and directories, dump writes the raw + data blocks that comprise files and directories. - + If dump is used on the root directory, it will not back up /home, - /usr or many other - directories since these are typically mount points for other - file systems or symbolic links into those file - systems. + /usr or many other directories since + these are typically mount points for other file systems or + symbolic links into those file systems. - - When used to restore data, - restore stores temporary files in - /tmp/ by default. When using a recovery - disk with a small /tmp, set - TMPDIR to a directory with more free space in - order for the restore to succeed. - When using dump, be aware that some quirks remain from its - early days in Version 6 of AT&T &unix;,circa 1975. The - default parameters assume a backup to a 9-track tape, rather than - to another type of media or to the high-density tapes available today. - These defaults must be overridden on the command line. + When used to restore data, restore + stores temporary files in /tmp/ by + default. When using a recovery disk with a small + /tmp, set TMPDIR to a + directory with more free space in order for the restore to + succeed. + + When using dump, be aware that some + quirks remain from its early days in Version 6 of + AT&T &unix;,circa 1975. The default parameters assume a + backup to a 9-track tape, rather than to another type of media + or to the high-density tapes available today. These defaults + must be overridden on the command line. .rhosts - It is possible to backup a file system across the network to a - another system or to a tape drive attached to another computer. - While the &man.rdump.8; and &man.rrestore.8; utilities can be - used for this purpose, they are not considered to be secure. + It is possible to backup a file system across the network + to a another system or to a tape drive attached to another + computer. While the &man.rdump.8; and &man.rrestore.8; + utilities can be used for this purpose, they are not + considered to be secure. Instead, one can use dump and restore in a more secure fashion over an @@ -1708,7 +1708,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz - This example sets RSH in order to write the + This example sets RSH in order to write the the backup to a tape drive on a remote system over a SSH connection: @@ -1730,26 +1730,27 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c Several built-in utilities are available for backing up - and restoring specified files and directories as needed. + and restoring specified files and directories as + needed. A good choice for making a backup of all of the files in a - directory is &man.tar.1;. This utility dates back to Version 6 of AT&T - &unix; and by default assumes a recursive backup to a local tape - device. Switches can be used to instead specify the name of - a backup file. + directory is &man.tar.1;. This utility dates back to Version + 6 of AT&T &unix; and by default assumes a recursive backup + to a local tape device. Switches can be used to instead + specify the name of a backup file. tar This example creates a compressed backup of the current - directory and saves it to + directory and saves it to /tmp/mybackup.tgz. When creating a backup file, make sure that the backup is not saved to the same directory that is being backed up. - Backing Up the Current Directory With + <title>Backing Up the Current Directory With <command>tar</command> - + &prompt.root; tar czvf /tmp/mybackup.tgz . @@ -1761,11 +1762,11 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c backup to restore. - Restoring Up the Current Directory With + <title>Restoring Up the Current Directory With <command>tar</command> &prompt.root; tar xzvf /tmp/mybackup.tgz - + There are dozens of available switches which are described in &man.tar.1;. This utility also supports the use of exclude @@ -1778,26 +1779,25 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c cpio - To create a backup using a specified list of files and + To create a backup using a specified list of files and directories, &man.cpio.1; is a good choice. Unlike - tar, - cpio does not know - how to walk the directory tree and it must be provided the list of files - to backup. + tar, cpio does not know + how to walk the directory tree and it must be provided the + list of files to backup. For example, a list of files can be created using - ls or find. This example - creates a recursive listing of the current directory which is - then piped to cpio in order to create an - output backup file named + ls or find. This + example creates a recursive listing of the current directory + which is then piped to cpio in order to + create an output backup file named /tmp/mybackup.cpio. Using<command>ls</command> and <command>cpio</command> to Make a Recursive Backup of the Current Directory - + &prompt.root; ls -R | cpio -ovF /tmp/mybackup.cpio - + backup software @@ -1807,24 +1807,24 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c POSIX IEEE - A backup utility which tries to bridge the features provided by - tar and cpio is &man.pax.1;. Over the - years, the various versions of tar and - cpio became slightly incompatible. &posix; - created pax which - attempts to read and write many of the various + A backup utility which tries to bridge the features + provided by tar and cpio + is &man.pax.1;. Over the years, the various versions of + tar and cpio became + slightly incompatible. &posix; created pax + which attempts to read and write many of the various cpio and tar formats, plus new formats of its own. The pax equivalent to the previous - examples would be: - + examples would be: + - Backing Up the Current Directory With + <title>Backing Up the Current Directory With <command>pax</command> &prompt.root; pax -wf /tmp/mybackup.pax . - + @@ -1839,70 +1839,67 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c backups. Many of these applications are client/server based and can be used to automate the backups of a single system or all of the computers in a network. - + Popular utilities include - Amanda, + Amanda, Bacula, rsync, and - duplicity. - + duplicity. Emergency Recovery - In addition to regular backups, it is recommended to - perform the following steps as part of an emergency - preparedness plan. - - bsdlabel - + In addition to regular backups, it is recommended to + perform the following steps as part of an emergency + preparedness plan. - Create a print copy of the output of the following - commands: - - - - gpart show - - - - more /etc/fstab - - - - dmesg - - + + bsdlabel - livefs CD - Store this printout and a copy of the installation media - in a secure location. Should an emergency restore be - needed, boot into the installation media and select - Live CD to access a rescue shell. This - rescue mode can be used to view the current state of the - system, and if needed, to reformat disks and restore data - from backups. + Create a print copy of the output of the following + commands: - - The installation media - for &os;/&arch.i386; &rel2.current;-RELEASE does not - include a rescue shell. For this version, instead - download and burn a Livefs CD image from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. - + + + gpart show + - Next, test the rescue shell and the - backups. Make notes of the procedure. Store these notes - with the media, the printouts, and the backups. These notes - may prevent the inadvertent destruction of the backups while - under the stress of performing an emergency - recovery. + + more /etc/fstab + - For an added measure of security, store the latest backup at a - remote location which is - physically separated from the - computers and disk drives by a significant distance. + + dmesg + + + + livefs CD + Store this printout and a copy of the installation media + in a secure location. Should an emergency restore be + needed, boot into the installation media and select + Live CD to access a rescue shell. This + rescue mode can be used to view the current state of the + system, and if needed, to reformat disks and restore data + from backups. + + + The installation media for + &os;/&arch.i386; &rel2.current;-RELEASE does not + include a rescue shell. For this version, instead + download and burn a Livefs CD image from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. + + + Next, test the rescue shell and the backups. Make notes + of the procedure. Store these notes with the media, the + printouts, and the backups. These notes may prevent the + inadvertent destruction of the backups while under the stress + of performing an emergency recovery. + + For an added measure of security, store the latest backup + at a remote location which is physically separated from the + computers and disk drives by a significant distance.