From owner-svn-doc-head@FreeBSD.ORG Wed Apr 9 17:57:02 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 81A84A0A; Wed, 9 Apr 2014 17:57:02 +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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60CA318D8; Wed, 9 Apr 2014 17:57:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s39Hv2Ul059152; Wed, 9 Apr 2014 17:57:02 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s39Hv2oa059151; Wed, 9 Apr 2014 17:57:02 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404091757.s39Hv2oa059151@svn.freebsd.org> From: Dru Lavigne Date: Wed, 9 Apr 2014 17:57:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44508 - 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-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2014 17:57:02 -0000 Author: dru Date: Wed Apr 9 17:57:01 2014 New Revision: 44508 URL: http://svnweb.freebsd.org/changeset/doc/44508 Log: Editorial Review of Tape Backup chapter. The next commit will integrate it into the Backup Basics chapter. 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 Wed Apr 9 15:54:45 2014 (r44507) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Wed Apr 9 17:57:01 2014 (r44508) @@ -1680,78 +1680,66 @@ cd0: Attempt to query device size failed tape media - Tape technology has continued to evolve but is less likely - to be used in a modern system. Modern backup systems tend to - use off site combined with local removable disk drive - technologies. Still, &os; will support any tape drive that - uses SCSI, such as LTO and older devices such - as DAT. There is limited support for SATA + While tape technology has continued to evolve, + modern backup systems tend to combine + off-site backups with local removable media. + &os; supports any tape drive that + uses SCSI, such as LTO or + DAT. There is limited support for SATA and USB tape drives. - - Serial Access with &man.sa.4; - - - tape drives - - - &os; uses the &man.sa.4; driver, providing + For SCSI tape devices, &os; uses the &man.sa.4; driver and the /dev/sa0, /dev/nsa0, - and /dev/esa0. In normal use, only - /dev/sa0 is needed. - /dev/nsa0 is the same physical drive - as /dev/sa0 but does not rewind the - tape after writing a file. This allows writing more than one + and /dev/esa0 devices. The physical device name is + /dev/sa0. When + /dev/nsa0 is used, the backup application will + not rewind the + tape after writing a file, which allows writing more than one file to a tape. Using /dev/esa0 - ejects the tape after the device is closed, if - applicable. - + ejects the tape after the device is closed. + + This section summarizes how to configure and use a + SCSI tape device on &os;. - Controlling the Tape Drive with - &man.mt.1; + Using a Tape Drive for Backups tape media mt - &man.mt.1; is the &os; utility for controlling other + In &os;, mt is used to control operations of the tape drive, such as seeking through files on - a tape or writing tape control marks to the tape. - - For example, the first three files on a tape can be + a tape or writing tape control marks to the tape. For + example, the first three files on a tape can be preserved by skipping past them before writing a new file: &prompt.root; mt -f /dev/nsa0 fsf 3 - - - - Using &man.tar.1; to Read and - Write Tape Backups - - An example of writing a single file to tape using - &man.tar.1;: + + This utility supports many operations. Refer to + &man.mt.1; for details. + + To write a single file to tape using + tar, specify the name of the tape device + and the file to backup: &prompt.root; tar cvf /dev/sa0 file - Recovering files from a &man.tar.1; archive on tape into + To recovering files from a tar archive on tape into the current directory: &prompt.root; tar xvf /dev/sa0 - - - - Using &man.dump.8; and - &man.restore.8; to Create and Restore Backups - A simple backup of /usr with - &man.dump.8;: + To backup a UFS file system, use + dump. This examples backs up + /usr without rewinding the tape when + finished: &prompt.root; dump -0aL -b64 -f /dev/nsa0 /usr - Interactively restoring files from a &man.dump.8; file on + To interactively restore files from a dump file on tape into the current directory: &prompt.root; restore -i -f /dev/nsa0 @@ -1760,7 +1748,7 @@ cd0: Attempt to query device size failed Other Tape Software - Higher-level programs are available to simplify tape + Third-party programs are available to simplify tape backup. The most popular are Amanda and Bacula. These programs aim to make