Page MenuHomeFreeBSD
Files F142853757

D43948.id135065.diff
No OneTemporary
Actions

D43948.id135065.diff
View Options

diff --git a/documentation/content/en/books/handbook/advanced-networking/_index.adoc b/documentation/content/en/books/handbook/advanced-networking/_index.adoc
--- a/documentation/content/en/books/handbook/advanced-networking/_index.adoc
+++ b/documentation/content/en/books/handbook/advanced-networking/_index.adoc
@@ -2221,7 +2221,7 @@
When a failure occurs, the backup server will pick up the failed master machine's IP address.
[[carp-10x]]
-=== Using CARP on FreeBSD 10 and Later
+=== Using CARP
Enable boot-time support for CARP by adding an entry for the [.filename]#carp.ko# kernel module in [.filename]#/boot/loader.conf#:
@@ -2299,89 +2299,6 @@
CARP functionality can be controlled via several man:sysctl[8] variables documented in the man:carp[4] manual pages.
Other actions can be triggered from CARP events by using man:devd[8].
-[[carp-9x]]
-=== Using CARP on FreeBSD 9 and Earlier
-
-The configuration for these versions of FreeBSD is similar to the one described in the previous section, except that a CARP device must first be created and referred to in the configuration.
-
-Enable boot-time support for CARP by loading the [.filename]#if_carp.ko# kernel module in [.filename]#/boot/loader.conf#:
-
-[.programlisting]
-....
-if_carp_load="YES"
-....
-
-To load the module now without rebooting:
-
-[source,shell]
-....
-# kldload carp
-....
-
-For users who prefer to use a custom kernel, include the following line in the custom kernel configuration file and compile the kernel as described in crossref:kernelconfig[kernelconfig,Configuring the FreeBSD Kernel]:
-
-[.programlisting]
-....
-device carp
-....
-
-Next, on each host, create a CARP device:
-
-[source,shell]
-....
-# ifconfig carp0 create
-....
-
-Set the hostname, management IP address, the shared IP address, and VHID by adding the required lines to [.filename]#/etc/rc.conf#.
-Since a virtual CARP device is used instead of an alias, the actual subnet mask of `/24` is used instead of `/32`.
-Here are the entries for `hosta.example.org`:
-
-[.programlisting]
-....
-hostname="hosta.example.org"
-ifconfig_fxp0="inet 192.168.1.3 netmask 255.255.255.0"
-cloned_interfaces="carp0"
-ifconfig_carp0="vhid 1 pass testpass 192.168.1.50/24"
-....
-
-On `hostb.example.org`:
-
-[.programlisting]
-....
-hostname="hostb.example.org"
-ifconfig_fxp0="inet 192.168.1.4 netmask 255.255.255.0"
-cloned_interfaces="carp0"
-ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24"
-....
-
-The third machine, `hostc.example.org`, is configured to handle failover from either of the master hosts:
-
-[.programlisting]
-....
-hostname="hostc.example.org"
-ifconfig_fxp0="inet 192.168.1.5 netmask 255.255.255.0"
-cloned_interfaces="carp0 carp1"
-ifconfig_carp0="vhid 1 advskew 100 pass testpass 192.168.1.50/24"
-ifconfig_carp1="vhid 2 advskew 100 pass testpass 192.168.1.51/24"
-....
-
-[NOTE]
-====
-Preemption is disabled in the [.filename]#GENERIC# FreeBSD kernel.
-If preemption has been enabled with a custom kernel, `hostc.example.org` may not release the IP address back to the original content server.
-The administrator can force the backup server to return the IP address to the master with the command:
-
-[source,shell]
-....
-# ifconfig carp0 down && ifconfig carp0 up
-....
-
-This should be done on the [.filename]#carp# interface which corresponds to the correct host.
-====
-
-Once the configuration is complete, either restart networking or reboot each system.
-High availability is now enabled.
-
[[network-vlan]]
== VLANs
diff --git a/documentation/content/en/books/handbook/disks/_index.adoc b/documentation/content/en/books/handbook/disks/_index.adoc
--- a/documentation/content/en/books/handbook/disks/_index.adoc
+++ b/documentation/content/en/books/handbook/disks/_index.adoc
@@ -1245,21 +1245,21 @@
[NOTE]
====
-If `dump` is used on the root directory, it will not back up [.filename]#/home#, [.filename]#/usr# or many other directories since these are typically mount points for other file systems or symbolic links into those file systems.
+If `dump` is used on the root directory, it will not back up [.filename]#/home#, [.filename]#/usr#, or many other directories since these are typically mount points for other file systems or symbolic links into those file systems.
====
When used to restore data, `restore` stores temporary files in [.filename]#/tmp/# by default.
-When using a recovery disk with a small [.filename]#/tmp#, set `TMPDIR` to a directory with more free space in order for the restore to succeed.
+When using a recovery disk with a small [.filename]#/tmp#, set `TMPDIR` to a directory with more free space for the restore to succeed.
When using `dump`, be aware that some quirks remain from its early days in Version 6 of AT&T UNIX(R),circa 1975.
The default parameters assume a backup to a 9-track tape, rather than to another type of media or to the high-density tapes available today.
These defaults must be overridden on the command line.
-It is possible to backup a file system across the network to a another system or to a tape drive attached to another computer.
+It is possible to backup a file system across the network to another system or a tape drive attached to another computer.
While the man:rdump[8] and man:rrestore[8] utilities can be used for this purpose, they are not considered to be secure.
-Instead, one can use `dump` and `restore` in a more secure fashion over an SSH connection.
-This example creates a full, compressed backup of [.filename]#/usr# and sends the backup file to the specified host over a SSH connection.
+Instead, one can use `dump` and `restore` more securely over an SSH connection.
+This example creates a full, compressed backup of [.filename]#/usr# and sends the backup file to the specified host over an SSH connection.
.Using `dump` over ssh
[example]
@@ -1271,7 +1271,7 @@
....
====
-This example sets `RSH` in order to write the backup to a tape drive on a remote system over a SSH connection:
+This example sets `RSH` in order to write the backup to a tape drive on a remote system over an SSH connection:
.Using `dump` over ssh with `RSH` Set
[example]
@@ -1282,6 +1282,11 @@
....
====
+[TIP]
+====
+Systems using the crossref:zfs[,Z file system (ZFS)] can make use of man:zfs[8] for creating snapshots, as well as crossref:zfs[zfs-zfs-send,sending and receiving] them to/from remote systems.
+====
+
=== Directory Backups
Several built-in utilities are available for backing up and restoring specified files and directories as needed.
@@ -1404,7 +1409,14 @@
The FreeBSD Ports Collection provides many third-party utilities which can be used to schedule the creation of backups, simplify tape backup, and make backups easier and more convenient.
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.
+Popular utilities include:
+
+ * Amanda (package:misc/amanda-server[] and package:misc/amanda-client[]),
+ * Bacula (package:sysutils/bacula13-server[] and package:sysutils/bacula13-client[]),
+ * Bareos (package:sysutils/bareos-server[] and package:sysutils/bareos-client[]),
+ * package:net/rsync[],
+ * package:sysutils/duply[], and
+ * package:sysutils/duplicity[].
=== Emergency Recovery
@@ -1414,6 +1426,7 @@
* `gpart show`
* `more /etc/fstab`
+* `pkg prime-list`
* `dmesg`
Store this printout and a copy of the installation media in a secure location.
@@ -1550,7 +1563,8 @@
FreeBSD offers a feature in conjunction with crossref:config[soft-updates,Soft Updates]: file system snapshots.
-UFS snapshots allow a user to create images of specified file systems, and treat them as a file.
+UFS snapshots allow a user to create images of specified file systems, and treat them as a file. If you are using the crossref:zfs[,Z file system (ZFS)], refer to crossref:zfs[zfs-zfs-snapshot,"Managing Snapshots"] on how to use snapshots.
+
Snapshot files must be created in the file system that the action is performed on, and a user may create no more than 20 snapshots per file system.
Active snapshots are recorded in the superblock so they are persistent across unmount and remount operations along with system reboots.
When a snapshot is no longer required, it can be removed using man:rm[1].
@@ -2381,30 +2395,25 @@
A state change on the CARP interface is an indication that one of the nodes failed or came back online.
These state change events make it possible to run a script which will automatically handle the HAST failover.
-To catch state changes on the CARP interfaces, add this configuration to [.filename]#/etc/devd.conf# on each node:
+To catch state changes on the CARP interfaces, add this configuration to [.filename]#/etc/devd.conf# on each node, while replacing `<vhid>` with the virtual host id and `<ifname>` with the associated interface name:
[.programlisting]
....
notify 30 {
- match "system" "IFNET";
- match "subsystem" "carp0";
- match "type" "LINK_UP";
+ match "system" "CARP";
+ match "subsystem" "<vhid>@<ifname>";
+ match "type" "MASTER";
action "/usr/local/sbin/carp-hast-switch primary";
};
notify 30 {
- match "system" "IFNET";
- match "subsystem" "carp0";
- match "type" "LINK_DOWN";
+ match "system" "CARP";
+ match "subsystem" "<vhid>@<ifname>";
+ match "type" "BACKUP";
action "/usr/local/sbin/carp-hast-switch secondary";
};
....
-[NOTE]
-====
-If the systems are running FreeBSD 10 or higher, replace [.filename]#carp0# with the name of the CARP-configured interface.
-====
-
Restart man:devd[8] on both nodes to put the new configuration into effect:
[source,shell]
@@ -2526,6 +2535,8 @@
To reduce the time needed for recovery, a journal-enabled UFS or ZFS file system can be used instead.
====
+Instead of using the highly available storage locally, it can also be shared to other computers on a network via crossref:network-servers[network-nfs,NFS], crossref:network-servers[network-iscsi,iSCSI], man:sshfs[1], or programs in ports (i.e. package:net/samba419[]).
+
More detailed information with additional examples can be found at http://wiki.FreeBSD.org/HAST[http://wiki.FreeBSD.org/HAST].
=== Troubleshooting

File Metadata

Mime Type
text/plain
Expires
Sun, Jan 25, 4:55 AM (3 h, 14 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
27926121
Default Alt Text
D43948.id135065.diff (10 KB)

Event Timeline