From owner-svn-doc-all@FreeBSD.ORG Thu Jan 30 22:34:34 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6BFDEB14; Thu, 30 Jan 2014 22:34:34 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4BA201DE3; Thu, 30 Jan 2014 22:34:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0UMYYS9069544; Thu, 30 Jan 2014 22:34:34 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0UMYYDK069543; Thu, 30 Jan 2014 22:34:34 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201401302234.s0UMYYDK069543@svn.freebsd.org> From: Dru Lavigne Date: Thu, 30 Jan 2014 22:34:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43702 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 22:34:34 -0000 Author: dru Date: Thu Jan 30 22:34:33 2014 New Revision: 43702 URL: http://svnweb.freebsd.org/changeset/doc/43702 Log: Last pass through this chapter. Rename Amanda to Third-Party Backup Utilities. Add some examples of utils. This section is light-weight and could probably use another paragraph or two. Rename Emergency Repair Procedure to Emergency Recovery. Tighten up this section and put the emphasis on the newer installation media option as opposed to the older livefs option. Make editorial note to close PR48101 in 06/15 when 8.4 is EOl'd. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 22:29:47 2014 (r43701) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Jan 30 22:34:33 2014 (r43702) @@ -1682,7 +1682,7 @@ cd0: Attempt to query device size failed 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 media or the high-density tapes available today. + to another type of media or to the high-density tapes available today. These defaults must be overridden on the command line. @@ -1828,156 +1828,81 @@ cd0: Attempt to query device size failed - <application>Amanda</application> + Third-Party Backup Utilities backup software - Amanda - - - Amanda - - Amanda (Advanced Maryland - Network Disk Archiver) is a client/server backup system, - rather than a single program. An - Amanda server will backup to a - single tape drive any number of computers that have - Amanda clients and a network - connection to the Amanda server. A - common problem at sites with a number of large disks is that - the length of time required to backup to data directly to tape - exceeds the amount of time available for the task. - Amanda solves this problem by using - a holding disk to backup several file systems - at the same time. Amanda creates - archive sets: a group of tapes used over a - period of time to create full backups of all the file systems - listed in Amanda's configuration - file. The archive set also contains nightly - incremental, or differential, backups of all the file systems. - Restoring a damaged file system requires the most recent full - backup and the incremental backups. - - The configuration file provides fine grained control of - backups and the network traffic that - Amanda generates. - Amanda will use any of the above - backup programs to write the data to tape. - Amanda is not installed by - but is available as either a port or package. + The &os; Ports Collection provides many third-party + utilities which can be used to schedule the creation of + 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, + Bacula, + rsync, and + duplicity. + - Emergency Restore Procedure - - - Before the Disaster + Emergency Recovery - There are four steps which should be performed in - preparation for any disaster that may occur. + In addition to regular backups, it is recommended to + perform the following steps as part of an emergency + preparedness plan. bsdlabel - First, print the bsdlabel of each disk using a command - such as bsdlabel da0 | lpr. Also print a - copy of /etc/fstab and all boot - messages. + Create a print copy of the output of the following + commands: + + + + gpart show + + + + more /etc/fstab + + + + dmesg + + livefs CD - Second, burn a livefs CD. This CD - contains support for booting into a &os; - livefs rescue mode, allowing the user to - perform many tasks like running &man.dump.8;, - &man.restore.8;, &man.fdisk.8;, &man.bsdlabel.8;, - &man.newfs.8;, &man.mount.8;, and more. The livefs CD image - for &os;/&arch.i386; &rel2.current;-RELEASE is - available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. + 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. - Livefs CD images are not available for - &os; &rel.current;-RELEASE and later. In addition to - the CD-ROM installation images, flash drive installation - images may be used to recover a system. The - memstick image for - &os;/&arch.i386; &rel.current;-RELEASE is available - from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img. + 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. - Third, create backup tapes regularly. Any changes that - made after the last backup may be irretrievably lost. - Write-protect the backup media. - - Fourth, test the livefs CD and the + Next, test the rescue shell and the backups. Make notes of the procedure. Store these notes - with the CD, the printouts, and the backups. 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 an extra - livefs CD and the latest backup at a - remote location, where a remote location is - not the basement of the same building. - A remote location should be physically separated from the + 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. - - - - After the Disaster - - First, determine if the hardware survived. Thanks - to regular, off-site backups, there is no need to worry - about the software. - - If the hardware has been damaged, the parts should be - replaced before attempting to use the computer. - - If the hardware is okay, insert the - livefs CD and boot the computer. The - original install menu will be displayed on the screen. - Select the correct country, then choose - Fixit -- Repair mode with CD-ROM/DVD/floppy or - start a shell. then select - CD-ROM/DVD -- Use the live file system - CD-ROM/DVD. - restore and the other needed programs - are located in /mnt2/rescue. - - Recover each file system separately. - - - mount - - root partition - - bsdlabel - - - newfs - - - Try to mount the root partition - of the first disk using mount /dev/da0a - /mnt. If the bsdlabel was damaged, use - bsdlabel to re-partition and label the - disk to match the label that was printed and saved. Use - newfs to re-create the file systems. - Re-mount the root partition of the disk read-write using - mount -u -o rw /mnt. Use the backups - to recover the data for this file system. Unmount the file - system with umount /mnt. Repeat for each - file system that was damaged. - - Once the system is running, backup the data onto new - media as whatever caused the crash or data loss may strike - again. Another hour spent now may save further distress - later. -