The backups section still refers to the old SCSI devices.
Updated to reflect the current naming scheme. PR: 12184 Submitted by: Chris Costello <chris@calldei.com>
This commit is contained in:
Mike Pritchard
parent
f1f90ae08b
commit
5083d9c631
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=5068
3 changed files with 60 additions and 60 deletions
en/handbook/backups
en_US.ISO8859-1/books/handbook/backups
en_US.ISO_8859-1/books/handbook/backups
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: chapter.sgml,v 1.7 1999-05-25 18:43:24 dwhite Exp $
|
||||
$Id: chapter.sgml,v 1.8 1999-06-15 20:37:38 mpp Exp $
|
||||
-->
|
||||
|
||||
<chapter id="backups">
|
||||
|
|
@ -170,8 +170,8 @@
|
|||
blank tape, the operation will fail. The console messages should be
|
||||
similar to:</para>
|
||||
|
||||
<screen>st0(ncr1:4:0): NOT READY asc:4,1
|
||||
st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
||||
<screen>sa0(ncr1:4:0): NOT READY asc:4,1
|
||||
sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
||||
|
||||
<para>The tape does not contain an Identifier Block (block number 0).
|
||||
All QIC tape drives since the adoption of QIC-525 standard write an
|
||||
|
|
@ -230,7 +230,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
on the remote computer. (e.g. When <command>rdump</command>'ing from
|
||||
a FreeBSD computer to an Exabyte tape drive connected to a Sun called
|
||||
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000 13000
|
||||
126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</command>) Beware: there
|
||||
126 komodo:/dev/nrsa8 /dev/rda0a 2>&1</command>) Beware: there
|
||||
are security implications to allowing <literal>rhosts</literal>
|
||||
commands. Evaluate your situation carefully.</para>
|
||||
</sect2>
|
||||
|
|
@ -250,7 +250,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
supports remote devices using the same syntax as &man.rdump.8;. To
|
||||
&man.tar.1; to an Exabyte tape drive connected to a Sun called
|
||||
<hostid>komodo</hostid>, use: <command>/usr/bin/tar cf
|
||||
komodo:/dev/nrst8 . 2>&1</command>. For versions without remote
|
||||
komodo:/dev/nrsa8 . 2>&1</command>. For versions without remote
|
||||
device support, you can use a pipeline and &man.rsh.1; to send the
|
||||
data to a remote tape drive. (XXX add an example command)</para>
|
||||
</sect2>
|
||||
|
|
@ -264,7 +264,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
and pipe the data to other programs. This last feature makes
|
||||
&man.cpio.1; and excellent choice for installation media.
|
||||
&man.cpio.1; does not know how to walk the directory tree and a list
|
||||
of files must be provided thru <filename>STDIN</filename>.</para>
|
||||
of files must be provided through <filename>stdin</filename>.</para>
|
||||
|
||||
<para>&man.cpio.1; does not support backups across the network. You can
|
||||
use a pipeline and &man.rsh.1; to send the data to a remote tape
|
||||
|
|
@ -360,7 +360,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
preparation for any disaster that may occur.</para>
|
||||
|
||||
<para>First, print the disklabel from each of your disks
|
||||
(<command>e.g. disklabel sd0 | lpr</command>), your filesystem table
|
||||
(<command>e.g. disklabel da0 | lpr</command>), your filesystem table
|
||||
(<command>/etc/fstab</command>) and all boot messages, two copies of
|
||||
each.</para>
|
||||
|
||||
|
|
@ -389,8 +389,8 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
procedure. Store these notes with the bootable floppy, the
|
||||
printouts and the backup tapes. You will be so distraught when
|
||||
restoring that the notes may prevent you from destroying your backup
|
||||
tapes (How? In place of <command>tar xvf /dev/rst0</command>, you
|
||||
might accidently type <command>tar cvf /dev/rst0</command> and
|
||||
tapes (How? In place of <command>tar xvf /dev/rsa0</command>, you
|
||||
might accidently type <command>tar cvf /dev/rsa0</command> and
|
||||
over-write your backup tape).</para>
|
||||
|
||||
<para>For an added measure of security, make bootable floppies and two
|
||||
|
|
@ -468,7 +468,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device
|
|||
options NCONS=2 #1 virtual consoles
|
||||
options USERCONFIG #Allow user configuration with -c XXX
|
||||
|
||||
config kernel root on sd0 swap on sd0 and sd1 dumps on sd0
|
||||
config kernel root on da0 swap on da0 and da1 dumps on da0
|
||||
|
||||
controller isa0
|
||||
controller pci0
|
||||
|
|
@ -483,11 +483,11 @@ controller scbus0
|
|||
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
|
||||
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
|
||||
|
||||
device sd0
|
||||
device sd1
|
||||
device sd2
|
||||
device da0
|
||||
device da1
|
||||
device da2
|
||||
|
||||
device st0
|
||||
device sa0
|
||||
|
||||
pseudo-device loop # required by INET
|
||||
pseudo-device gzip # Exec gzipped a.out's
|
||||
|
|
@ -521,10 +521,10 @@ chmod 6555 /mnt/sbin/restore
|
|||
#
|
||||
cd /mnt/dev
|
||||
./MAKEDEV std
|
||||
./MAKEDEV sd0
|
||||
./MAKEDEV sd1
|
||||
./MAKEDEV sd2
|
||||
./MAKEDEV st0
|
||||
./MAKEDEV da0
|
||||
./MAKEDEV da1
|
||||
./MAKEDEV da2
|
||||
./MAKEDEV sa0
|
||||
./MAKEDEV pty0
|
||||
cd /
|
||||
|
||||
|
|
@ -583,7 +583,7 @@ chmod 644 /mnt/etc/passwd
|
|||
|
||||
<para>Recover each filesystem separately.</para>
|
||||
|
||||
<para>Try to &man.mount.8; (e.g. <command>mount /dev/sd0a
|
||||
<para>Try to &man.mount.8; (e.g. <command>mount /dev/da0a
|
||||
/mnt</command>) the root partition of your first disk. If the
|
||||
disklabel was damaged, use &man.disklabel.8; to re-partition and
|
||||
label the disk to match the label that your printed and saved. Use
|
||||
|
|
@ -591,7 +591,7 @@ chmod 644 /mnt/etc/passwd
|
|||
partition of the floppy read-write (<command>mount -u -o rw
|
||||
/mnt</command>). Use your backup program and backup tapes to
|
||||
recover the data for this filesystem (e.g. <command>restore vrf
|
||||
/dev/st0</command>). Unmount the filesystem (e.g. <command>umount
|
||||
/dev/sa0</command>). Unmount the filesystem (e.g. <command>umount
|
||||
/mnt</command>) Repeat for each filesystem that was
|
||||
damaged.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: chapter.sgml,v 1.7 1999-05-25 18:43:24 dwhite Exp $
|
||||
$Id: chapter.sgml,v 1.8 1999-06-15 20:37:38 mpp Exp $
|
||||
-->
|
||||
|
||||
<chapter id="backups">
|
||||
|
|
@ -170,8 +170,8 @@
|
|||
blank tape, the operation will fail. The console messages should be
|
||||
similar to:</para>
|
||||
|
||||
<screen>st0(ncr1:4:0): NOT READY asc:4,1
|
||||
st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
||||
<screen>sa0(ncr1:4:0): NOT READY asc:4,1
|
||||
sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
||||
|
||||
<para>The tape does not contain an Identifier Block (block number 0).
|
||||
All QIC tape drives since the adoption of QIC-525 standard write an
|
||||
|
|
@ -230,7 +230,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
on the remote computer. (e.g. When <command>rdump</command>'ing from
|
||||
a FreeBSD computer to an Exabyte tape drive connected to a Sun called
|
||||
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000 13000
|
||||
126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</command>) Beware: there
|
||||
126 komodo:/dev/nrsa8 /dev/rda0a 2>&1</command>) Beware: there
|
||||
are security implications to allowing <literal>rhosts</literal>
|
||||
commands. Evaluate your situation carefully.</para>
|
||||
</sect2>
|
||||
|
|
@ -250,7 +250,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
supports remote devices using the same syntax as &man.rdump.8;. To
|
||||
&man.tar.1; to an Exabyte tape drive connected to a Sun called
|
||||
<hostid>komodo</hostid>, use: <command>/usr/bin/tar cf
|
||||
komodo:/dev/nrst8 . 2>&1</command>. For versions without remote
|
||||
komodo:/dev/nrsa8 . 2>&1</command>. For versions without remote
|
||||
device support, you can use a pipeline and &man.rsh.1; to send the
|
||||
data to a remote tape drive. (XXX add an example command)</para>
|
||||
</sect2>
|
||||
|
|
@ -264,7 +264,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
and pipe the data to other programs. This last feature makes
|
||||
&man.cpio.1; and excellent choice for installation media.
|
||||
&man.cpio.1; does not know how to walk the directory tree and a list
|
||||
of files must be provided thru <filename>STDIN</filename>.</para>
|
||||
of files must be provided through <filename>stdin</filename>.</para>
|
||||
|
||||
<para>&man.cpio.1; does not support backups across the network. You can
|
||||
use a pipeline and &man.rsh.1; to send the data to a remote tape
|
||||
|
|
@ -360,7 +360,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
preparation for any disaster that may occur.</para>
|
||||
|
||||
<para>First, print the disklabel from each of your disks
|
||||
(<command>e.g. disklabel sd0 | lpr</command>), your filesystem table
|
||||
(<command>e.g. disklabel da0 | lpr</command>), your filesystem table
|
||||
(<command>/etc/fstab</command>) and all boot messages, two copies of
|
||||
each.</para>
|
||||
|
||||
|
|
@ -389,8 +389,8 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
procedure. Store these notes with the bootable floppy, the
|
||||
printouts and the backup tapes. You will be so distraught when
|
||||
restoring that the notes may prevent you from destroying your backup
|
||||
tapes (How? In place of <command>tar xvf /dev/rst0</command>, you
|
||||
might accidently type <command>tar cvf /dev/rst0</command> and
|
||||
tapes (How? In place of <command>tar xvf /dev/rsa0</command>, you
|
||||
might accidently type <command>tar cvf /dev/rsa0</command> and
|
||||
over-write your backup tape).</para>
|
||||
|
||||
<para>For an added measure of security, make bootable floppies and two
|
||||
|
|
@ -468,7 +468,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device
|
|||
options NCONS=2 #1 virtual consoles
|
||||
options USERCONFIG #Allow user configuration with -c XXX
|
||||
|
||||
config kernel root on sd0 swap on sd0 and sd1 dumps on sd0
|
||||
config kernel root on da0 swap on da0 and da1 dumps on da0
|
||||
|
||||
controller isa0
|
||||
controller pci0
|
||||
|
|
@ -483,11 +483,11 @@ controller scbus0
|
|||
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
|
||||
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
|
||||
|
||||
device sd0
|
||||
device sd1
|
||||
device sd2
|
||||
device da0
|
||||
device da1
|
||||
device da2
|
||||
|
||||
device st0
|
||||
device sa0
|
||||
|
||||
pseudo-device loop # required by INET
|
||||
pseudo-device gzip # Exec gzipped a.out's
|
||||
|
|
@ -521,10 +521,10 @@ chmod 6555 /mnt/sbin/restore
|
|||
#
|
||||
cd /mnt/dev
|
||||
./MAKEDEV std
|
||||
./MAKEDEV sd0
|
||||
./MAKEDEV sd1
|
||||
./MAKEDEV sd2
|
||||
./MAKEDEV st0
|
||||
./MAKEDEV da0
|
||||
./MAKEDEV da1
|
||||
./MAKEDEV da2
|
||||
./MAKEDEV sa0
|
||||
./MAKEDEV pty0
|
||||
cd /
|
||||
|
||||
|
|
@ -583,7 +583,7 @@ chmod 644 /mnt/etc/passwd
|
|||
|
||||
<para>Recover each filesystem separately.</para>
|
||||
|
||||
<para>Try to &man.mount.8; (e.g. <command>mount /dev/sd0a
|
||||
<para>Try to &man.mount.8; (e.g. <command>mount /dev/da0a
|
||||
/mnt</command>) the root partition of your first disk. If the
|
||||
disklabel was damaged, use &man.disklabel.8; to re-partition and
|
||||
label the disk to match the label that your printed and saved. Use
|
||||
|
|
@ -591,7 +591,7 @@ chmod 644 /mnt/etc/passwd
|
|||
partition of the floppy read-write (<command>mount -u -o rw
|
||||
/mnt</command>). Use your backup program and backup tapes to
|
||||
recover the data for this filesystem (e.g. <command>restore vrf
|
||||
/dev/st0</command>). Unmount the filesystem (e.g. <command>umount
|
||||
/dev/sa0</command>). Unmount the filesystem (e.g. <command>umount
|
||||
/mnt</command>) Repeat for each filesystem that was
|
||||
damaged.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: chapter.sgml,v 1.7 1999-05-25 18:43:24 dwhite Exp $
|
||||
$Id: chapter.sgml,v 1.8 1999-06-15 20:37:38 mpp Exp $
|
||||
-->
|
||||
|
||||
<chapter id="backups">
|
||||
|
|
@ -170,8 +170,8 @@
|
|||
blank tape, the operation will fail. The console messages should be
|
||||
similar to:</para>
|
||||
|
||||
<screen>st0(ncr1:4:0): NOT READY asc:4,1
|
||||
st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
||||
<screen>sa0(ncr1:4:0): NOT READY asc:4,1
|
||||
sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
||||
|
||||
<para>The tape does not contain an Identifier Block (block number 0).
|
||||
All QIC tape drives since the adoption of QIC-525 standard write an
|
||||
|
|
@ -230,7 +230,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
on the remote computer. (e.g. When <command>rdump</command>'ing from
|
||||
a FreeBSD computer to an Exabyte tape drive connected to a Sun called
|
||||
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000 13000
|
||||
126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</command>) Beware: there
|
||||
126 komodo:/dev/nrsa8 /dev/rda0a 2>&1</command>) Beware: there
|
||||
are security implications to allowing <literal>rhosts</literal>
|
||||
commands. Evaluate your situation carefully.</para>
|
||||
</sect2>
|
||||
|
|
@ -250,7 +250,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
supports remote devices using the same syntax as &man.rdump.8;. To
|
||||
&man.tar.1; to an Exabyte tape drive connected to a Sun called
|
||||
<hostid>komodo</hostid>, use: <command>/usr/bin/tar cf
|
||||
komodo:/dev/nrst8 . 2>&1</command>. For versions without remote
|
||||
komodo:/dev/nrsa8 . 2>&1</command>. For versions without remote
|
||||
device support, you can use a pipeline and &man.rsh.1; to send the
|
||||
data to a remote tape drive. (XXX add an example command)</para>
|
||||
</sect2>
|
||||
|
|
@ -264,7 +264,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
and pipe the data to other programs. This last feature makes
|
||||
&man.cpio.1; and excellent choice for installation media.
|
||||
&man.cpio.1; does not know how to walk the directory tree and a list
|
||||
of files must be provided thru <filename>STDIN</filename>.</para>
|
||||
of files must be provided through <filename>stdin</filename>.</para>
|
||||
|
||||
<para>&man.cpio.1; does not support backups across the network. You can
|
||||
use a pipeline and &man.rsh.1; to send the data to a remote tape
|
||||
|
|
@ -360,7 +360,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
preparation for any disaster that may occur.</para>
|
||||
|
||||
<para>First, print the disklabel from each of your disks
|
||||
(<command>e.g. disklabel sd0 | lpr</command>), your filesystem table
|
||||
(<command>e.g. disklabel da0 | lpr</command>), your filesystem table
|
||||
(<command>/etc/fstab</command>) and all boot messages, two copies of
|
||||
each.</para>
|
||||
|
||||
|
|
@ -389,8 +389,8 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
procedure. Store these notes with the bootable floppy, the
|
||||
printouts and the backup tapes. You will be so distraught when
|
||||
restoring that the notes may prevent you from destroying your backup
|
||||
tapes (How? In place of <command>tar xvf /dev/rst0</command>, you
|
||||
might accidently type <command>tar cvf /dev/rst0</command> and
|
||||
tapes (How? In place of <command>tar xvf /dev/rsa0</command>, you
|
||||
might accidently type <command>tar cvf /dev/rsa0</command> and
|
||||
over-write your backup tape).</para>
|
||||
|
||||
<para>For an added measure of security, make bootable floppies and two
|
||||
|
|
@ -468,7 +468,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device
|
|||
options NCONS=2 #1 virtual consoles
|
||||
options USERCONFIG #Allow user configuration with -c XXX
|
||||
|
||||
config kernel root on sd0 swap on sd0 and sd1 dumps on sd0
|
||||
config kernel root on da0 swap on da0 and da1 dumps on da0
|
||||
|
||||
controller isa0
|
||||
controller pci0
|
||||
|
|
@ -483,11 +483,11 @@ controller scbus0
|
|||
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
|
||||
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
|
||||
|
||||
device sd0
|
||||
device sd1
|
||||
device sd2
|
||||
device da0
|
||||
device da1
|
||||
device da2
|
||||
|
||||
device st0
|
||||
device sa0
|
||||
|
||||
pseudo-device loop # required by INET
|
||||
pseudo-device gzip # Exec gzipped a.out's
|
||||
|
|
@ -521,10 +521,10 @@ chmod 6555 /mnt/sbin/restore
|
|||
#
|
||||
cd /mnt/dev
|
||||
./MAKEDEV std
|
||||
./MAKEDEV sd0
|
||||
./MAKEDEV sd1
|
||||
./MAKEDEV sd2
|
||||
./MAKEDEV st0
|
||||
./MAKEDEV da0
|
||||
./MAKEDEV da1
|
||||
./MAKEDEV da2
|
||||
./MAKEDEV sa0
|
||||
./MAKEDEV pty0
|
||||
cd /
|
||||
|
||||
|
|
@ -583,7 +583,7 @@ chmod 644 /mnt/etc/passwd
|
|||
|
||||
<para>Recover each filesystem separately.</para>
|
||||
|
||||
<para>Try to &man.mount.8; (e.g. <command>mount /dev/sd0a
|
||||
<para>Try to &man.mount.8; (e.g. <command>mount /dev/da0a
|
||||
/mnt</command>) the root partition of your first disk. If the
|
||||
disklabel was damaged, use &man.disklabel.8; to re-partition and
|
||||
label the disk to match the label that your printed and saved. Use
|
||||
|
|
@ -591,7 +591,7 @@ chmod 644 /mnt/etc/passwd
|
|||
partition of the floppy read-write (<command>mount -u -o rw
|
||||
/mnt</command>). Use your backup program and backup tapes to
|
||||
recover the data for this filesystem (e.g. <command>restore vrf
|
||||
/dev/st0</command>). Unmount the filesystem (e.g. <command>umount
|
||||
/dev/sa0</command>). Unmount the filesystem (e.g. <command>umount
|
||||
/mnt</command>) Repeat for each filesystem that was
|
||||
damaged.</para>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue