The bsr installation packages are available for Windows and Linux, separated into rpm packages for CentOS (RHEL) 6.4 and later and deb packages for Ubuntu 16.04 LTS and later. To obtain the installation packages, please contact Mantech Technical Lab.(bsr@mantech.co.kr)

Cautions

BSR conflicts with DRBD for system resource usage when installed and operated together. If DRBD was previously installed on your system, it should be removed.

Windows

Install

You can easily install it by running the installer for Windows and following the steps guided by the installation wizard. Once the installation is complete, you'll need to reboot your system.

Install information

After a successful installation, the directory will be organized as shown below.

bin

The location of the binary programs that make up BSR.

etc

The path to the configuration files.

jre

The path to the Java runtime environment for the installation package.

bsrservice

The path to the bsr service binary.

The bsr service performs initialization tasks for performing replication. Careful control of the service is required because replication can be interrupted if the service is interrupted.

Windows bsr uses TCP loopback ports 5678 and 5679 for netlinks and services. To change these ports, you must change the value of the key in the following registry path and restart the system.

Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bsr\

Keys: netlink_tcp_port, daemon_tcp_port

Update

If you reinstall a new version of a package with BSR installed, the update installation is done automatically.

You can also reinstall the program after deleting it from Control Panel, but be sure to restart the system after deletion. If you proceed directly to reinstalling the program without restarting, you should be careful because the system crashes due to abnormal installation.

Uninstall

You can delete the BSR package from Programs and Features in Control Panel. You must reboot the machine after deletion.

Replacing a NIC

If you replace a lan card after installing BSR, you must reapply the contents of Disable TCP Delayed ACK using the bsrcon /nodelayedack <resource> command.

Linux

Install - RHEL

Utility

[root@bsr-01 x86_64]# rpm -ivh bsr-utils-1.6-A3.el7.x86_64.rpm

Kernel Module

[root@bsr-01 bsr]# rpm -ivh kmod-bsr-1.6_3.10.0_957-A3.el7.x86_64.rpm

Secure Boot

If Secure Boot is disabled on your system, you don't need to set up Secure Boot.

The public key is installed in the /etc/pki/mantech/ path during the kernel module installation process. In order to enroll that public key in the UEFI console, we first import it as follows.

#mokutil --import /etc/pki/mantech/bsr_signing_key_pub.der

input password:

input password again:

Reboot after specifying the password. At reboot time, enroll the corresponding public key in the UEFI console.

Install - Ubuntu

Required Packages

The Ubuntu package uses Dynamic Kernel Module Support (DKMS), which requires the installation of the following packages.

root@ubuntu:/home/mantech# apt-get install git build-essential debhelper dkms docbook-xsl help2man python-all python-dbus python-gobject dh-systemd flex autoconf automake

Utility

root@ubuntu:/home/mantech# dpkg -i bsr-utils_1.6-A3_amd64.deb

Kernel Module

root@ubuntu:/home/mantech# dpkg -i bsr-dkms_1.6-A3_all.deb

If the installation fails due to a dependency issue, you can use the command below to resolve the dependency issue and try again.

root@ubuntu:/home/mantech# apt-get -f -y install

Secure Boot

The dkms package automatically generates MOKs and code signing for third-party drivers at the end of the installation.

If SecureBoot is disabled on your system, skip this step.

The screen below is displayed during module installation to register the generated public key.

After selecting OK, enter the password that will be used for MOK registration.

After rebooting the system, enter the UEFI console and register the public key with the system.

Enroll MOK → Countinue → Yes → Password → Reboot

Module Load

After rebooting, load the BSR module and verify that it succeeded.

# modprobe bsr

# lsmod |grep bsr

bsr 52113408 0

libcrc32c 16384 4 nf_conntrack,nf_nat,bsr,xfs

[root@bsr-01 bsr]# modinfo bsr
filename: /lib/modules/3.10.0-957.el7.x86_64/extra/bsr/bsr.ko
license: GPL
alias: block-major-147-*
license: GPL
version: 1.6-A3
description: bsr - Block Sync and Replication v1.6-A3
author: Man Technology Inc. bsr@mantech.co.kr
retpoline: Y
rhelversion: 7.6
srcversion: F4B39BD44212C22841949F8
depends: libcrc32c
vermagic: 3.10.0-957.el7.x86_64 SMP mod_unload modversions
signer: Man Technology Inc.: BSR Secure Boot Key
sig_key: D6:97:B5:89:F6:BC:A4:D5:28:02:25:57:4E:55:51:9F:F0:8F:EC:74
sig_hashalgo: sha256
parm: minor_count:Approximate number of bsr devices (1-255) (uint)
parm: disable_sendpage:bool
parm: allow_oos:DONT USE! (bool)
parm: debug_fast_sync:bool
parm: enable_faults:int
parm: fault_rate:int
parm: fault_count:int
parm: fault_devs:int
parm: two_phase_commit_fail:int
parm: usermode_helper:string

[root@bsr-01 x86_64]# bsradm -V
BSRADM_BUILDTAG=GIT-hash:\ 35649dbca524e37a7a8fcddb199db17efb8b7aba\ build\ by\ root@bsrc76,\ 2020-08-25\ 13:46:17
BSRADM_API_VERSION=2
BSR_KERNEL_VERSION_CODE=0x000000
BSR_KERNEL_VERSION=0.0.0
BSRADM_VERSION_CODE=0x000000
BSRADM_VERSION=1.6-A3

If the BSR module fails to load, refer to the manual code signing process in the Secure Boot Signing in Ubuntu article to walk through the signing process.

Service Config.

If you want BSR to always start up automatically when the system starts, you must enable the BSR service and configure the svc-auto-up option. The default value of svc-auto-up is yes.

RHEL 6
- chkconfig bsr on
- service bsr start
RHEL 7 or Ubuntu
- systemctl enable bsr
- systemctl start bsr

resource r0 {
        ...
        on hostname {
          options {
                svc-auto-up yes;
          }
        }
        ...
}

Uninstall

Uninstalling goes through the following process

Stopping a Resource
Stop a service
Delete a kernel module
Delete a utility

RHEL

rpm -e kmod-bsr

rpm -e bsr-utils

Ubuntu

dpkg -r bsr-dkms

dpkg -r bsr-utils

Update

Updating is the act of deleting the version already installed and reinstalling the new version.

First, the product is uninstalled, followed by the following update process.

Utility Update

RHEL

[root@bsr-01 bsr]# rpm -Uvh bsr-utils-1.6-A4.el7.x86_64.rpm

Ubuntu

root@ubuntu:/home/mantech# dpkg -i bsr-utils_1.6-A4_amd64.deb

Kernel Module Update

RHEL

[root@bsr-01 bsr]# rpm -Uvh kmod-bsr-1.6_3.10.0_957-A4.el7.x86_64.rpm

Ubuntu

root@ubuntu:/home/mantech# dpkg -i bsr-dkms_1.6-A4_all.deb

Secure Boot

If the existing BSR module public key is already registered, no additional setup is required.

If the private-public key for code signing has been updated, you will need to perform the Secure Boot setup process described above again.