Multiple tweaks.

PR:		docs/42125
Submitted by:	Martin Heinen <martin@sumuk.de>
This commit is contained in:
Ceri Davies 2002-08-28 21:18:20 +00:00
parent 6b04bdb5d5
commit d6598049e1
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=14068

View file

@ -1467,36 +1467,38 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
these are typically mount points for other filesystems or
symbolic links into those filesystems.</para></note>
<para><command>dump</command>has quirks that remain from its early days in
<para><command>dump</command> has quirks that remain from its early days in
Version 6 of AT&amp;T Unix (circa 1975). The default
parameters are suitable for 9-track tapes (6250 bpi), not the
high-density media available today (up to 62,182 ftpi). These
defaults must be overridden on the command line to utilize the
capacity of current tape drives.</para>
<indexterm><primary><filename>rhosts</filename></primary></indexterm>
<indexterm><primary><filename>.rhosts</filename></primary></indexterm>
<para>It is also possible to backup data across the network to a
tape drive attached to another computer with <command>rdump</command> and
<command>rrestore</command>. Both programs rely upon <command>rcmd</command> and
<command>ruserok</command> to access the remote tape drive. Therefore,
the user performing the backup must have
<literal>rhosts</literal> access to the remote computer. The
the user performing the backup must be listed in the
<filename>.rhosts</filename> file on the remote computer. The
arguments to <command>rdump</command> and <command>rrestore</command> must be suitable
to use on the remote computer. (e.g. When
to use on the remote computer. 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/nrsa8 /dev/rda0a
2>&amp;1</command>) Beware: there are security implications to
allowing <literal>rhosts</literal> commands. Evaluate your
<hostid>komodo</hostid>, use:</para>
<screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nrsa8 /dev/rda0a 2>&amp;1</userinput></screen>
<para>Beware: there are security implications to
allowing <filename>.rhosts</filename> authentication. Evaluate your
situation carefully.</para>
<para>It is also possible to use <command>rdump</command> and
<command>rrestore</command> in a more secure fashion over
<para>It is also possible to use <command>dump</command> and
<command>restore</command> in a more secure fashion over
<command>ssh</command>.</para>
<example>
<title>Using <command>rdump</command> over <application>ssh</application></title>
<title>Using <command>dump</command> over <application>ssh</application></title>
<screen>&prompt.root; <userinput>/sbin/dump -0uan -f - /usr | gzip -2 | ssh1 -c blowfish \
targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz</userinput></screen>
@ -1525,8 +1527,11 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<command>tar</command>, which FreeBSD utilizes, supports remote
devices using the same syntax as <command>rdump</command>. To
<command>tar</command> to an Exabyte tape drive connected to a
Sun called <hostid>komodo</hostid>, use: <command>/usr/bin/tar
cf komodo:/dev/nrsa8 . 2>&amp;1</command>. For versions without
Sun called <hostid>komodo</hostid>, use:</para>
<screen>&prompt.root; <userinput>/usr/bin/tar cf komodo:/dev/nrsa8 . 2>&amp;1</userinput></screen>
<para>For versions without
remote device support, you can use a pipeline and
<command>rsh</command> to send the data to a remote tape
drive.</para>