...
A single resource configuration filename is typically created in the form /etc/bsr.d/<resource>.res. The resource name used here must be specified within the resource file. Naming is arbitrary and identifiable, but it must be in US-ASCII format and must not contain space characters. Also, every resource configuration must have at least one <host> subsection. All other configuration settings are inherited from the Common section or set to the default values in the bsr. Options with values common to both hosts can be specified directly in the parent <resource> section of the <host> at once, but can be simplified by stating them as in the following example.
Info |
---|
Specifying a node-id for each node is mandatory. |
|
The following attributes are required to be described in the Resources section
disk
Specifies the replication device. Specify as a backing device or volume letter, depending on the platform.
device
Specifies the BSR logical device information. It can be specified directly as a device name, such as /dev/bsr1, or as a minor number, such as minor 1;.
On Windows, only specifying a minor number with a letter is used. On Windows, you can specify a device minor number by using the C drive volume as volume 0 and incrementing the minor number by 1 for each increment of the letter value (D is 1, E is 2, F is 3, ...).
meta-disk
Describes meta-disk information.
on host section
This section describes the host information. node-id and connection information.
node-id
You can specify an arbitrary node ID starting from 0. It is recommended to specify a smaller number for the primary node.
connection
Specify the IP and port information.
Connections can also be described separately using the connection section, as shown below. This is often used in node replication configurations.
Code Block |
---|
resource "r0" {
device minor 1;
disk "/dev/sda7";
meta-disk internal;
on "alice" {
node-id 0;
}
on "bob" {
node-id 1;
}
connection {
host "alice" address 10.1.1.31:7789;
host "bob" address 10.1.1.32:7789;
}
} |
For specific descriptions of other sections, subsections, and individual options, see the configuration file contents in the appendix.
Configuration type
BSR provides flexible redundancy for your organization's critical data in a variety of configurations. Configurations that replicate within the local network are commonly referred to as mirror configurations, while those that replicate between remote locations are called disaster recovery (DR) configurations.
...