|
Lines 1467-1502
Link Here
|
| 1467 |
these are typically mount points for other filesystems or |
1467 |
these are typically mount points for other filesystems or |
| 1468 |
symbolic links into those filesystems.</para></note> |
1468 |
symbolic links into those filesystems.</para></note> |
| 1469 |
|
1469 |
|
| 1470 |
<para><command>dump</command>has quirks that remain from its early days in |
1470 |
<para><command>dump</command> has quirks that remain from its early days in |
| 1471 |
Version 6 of AT&T Unix (circa 1975). The default |
1471 |
Version 6 of AT&T Unix (circa 1975). The default |
| 1472 |
parameters are suitable for 9-track tapes (6250 bpi), not the |
1472 |
parameters are suitable for 9-track tapes (6250 bpi), not the |
| 1473 |
high-density media available today (up to 62,182 ftpi). These |
1473 |
high-density media available today (up to 62,182 ftpi). These |
| 1474 |
defaults must be overridden on the command line to utilize the |
1474 |
defaults must be overridden on the command line to utilize the |
| 1475 |
capacity of current tape drives.</para> |
1475 |
capacity of current tape drives.</para> |
| 1476 |
|
1476 |
|
| 1477 |
<indexterm><primary><filename>rhosts</filename></primary></indexterm> |
1477 |
<indexterm><primary><filename>.rhosts</filename></primary></indexterm> |
| 1478 |
<para>It is also possible to backup data across the network to a |
1478 |
<para>It is also possible to backup data across the network to a |
| 1479 |
tape drive attached to another computer with <command>rdump</command> and |
1479 |
tape drive attached to another computer with <command>rdump</command> and |
| 1480 |
<command>rrestore</command>. Both programs rely upon <command>rcmd</command> and |
1480 |
<command>rrestore</command>. Both programs rely upon <command>rcmd</command> and |
| 1481 |
<command>ruserok</command> to access the remote tape drive. Therefore, |
1481 |
<command>ruserok</command> to access the remote tape drive. Therefore, |
| 1482 |
the user performing the backup must have |
1482 |
the user performing the backup must be listed in the |
| 1483 |
<literal>rhosts</literal> access to the remote computer. The |
1483 |
<filename>.rhosts</filename> file on the remote computer. The |
| 1484 |
arguments to <command>rdump</command> and <command>rrestore</command> must be suitable |
1484 |
arguments to <command>rdump</command> and <command>rrestore</command> must be suitable |
| 1485 |
to use on the remote computer. (e.g. When |
1485 |
to use on the remote computer. When |
| 1486 |
<command>rdump</command>ing from a FreeBSD computer to an |
1486 |
<command>rdump</command>ing from a FreeBSD computer to an |
| 1487 |
Exabyte tape drive connected to a Sun called |
1487 |
Exabyte tape drive connected to a Sun called |
| 1488 |
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu |
1488 |
<hostid>komodo</hostid>, use:</para> |
| 1489 |
54000 13000 126 komodo:/dev/nrsa8 /dev/rda0a |
1489 |
|
| 1490 |
2>&1</command>) Beware: there are security implications to |
1490 |
<screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nrsa8 /dev/rda0a 2>&1</userinput></screen> |
| 1491 |
allowing <literal>rhosts</literal> commands. Evaluate your |
1491 |
|
|
|
1492 |
<para>Beware: there are security implications to |
| 1493 |
allowing <filename>.rhosts</filename> authentication. Evaluate your |
| 1492 |
situation carefully.</para> |
1494 |
situation carefully.</para> |
| 1493 |
|
1495 |
|
| 1494 |
<para>It is also possible to use <command>rdump</command> and |
1496 |
<para>It is also possible to use <command>dump</command> and |
| 1495 |
<command>rrestore</command> in a more secure fashion over |
1497 |
<command>restore</command> in a more secure fashion over |
| 1496 |
<command>ssh</command>.</para> |
1498 |
<command>ssh</command>.</para> |
| 1497 |
|
1499 |
|
| 1498 |
<example> |
1500 |
<example> |
| 1499 |
<title>Using <command>rdump</command> over <application>ssh</application></title> |
1501 |
<title>Using <command>dump</command> over <application>ssh</application></title> |
| 1500 |
|
1502 |
|
| 1501 |
<screen>&prompt.root; <userinput>/sbin/dump -0uan -f - /usr | gzip -2 | ssh1 -c blowfish \ |
1503 |
<screen>&prompt.root; <userinput>/sbin/dump -0uan -f - /usr | gzip -2 | ssh1 -c blowfish \ |
| 1502 |
targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz</userinput></screen> |
1504 |
targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz</userinput></screen> |
|
Lines 1525-1532
Link Here
|
| 1525 |
<command>tar</command>, which FreeBSD utilizes, supports remote |
1527 |
<command>tar</command>, which FreeBSD utilizes, supports remote |
| 1526 |
devices using the same syntax as <command>rdump</command>. To |
1528 |
devices using the same syntax as <command>rdump</command>. To |
| 1527 |
<command>tar</command> to an Exabyte tape drive connected to a |
1529 |
<command>tar</command> to an Exabyte tape drive connected to a |
| 1528 |
Sun called <hostid>komodo</hostid>, use: <command>/usr/bin/tar |
1530 |
Sun called <hostid>komodo</hostid>, use:</para> |
| 1529 |
cf komodo:/dev/nrsa8 . 2>&1</command>. For versions without |
1531 |
|
|
|
1532 |
<screen>&prompt.root; <userinput>/usr/bin/tar cf komodo:/dev/nrsa8 . 2>&1</userinput></screen> |
| 1533 |
|
| 1534 |
<para>For versions without |
| 1530 |
remote device support, you can use a pipeline and |
1535 |
remote device support, you can use a pipeline and |
| 1531 |
<command>rsh</command> to send the data to a remote tape |
1536 |
<command>rsh</command> to send the data to a remote tape |
| 1532 |
drive.</para> |
1537 |
drive.</para> |