Install using the FSR software installation package provided by Mantech. The installation package is provided as a Windows and Linux installation package.(dev3@mantech.co.kr)

Components

The FSR software provides the following program components. Administrator privileges are required for installation and running the program.

FSR Filter Driver

Kernel filter driver for data replication that captures all the change I/O that occurs to the file to be replicated and forwards it to the FSR engine.

FSR Engine

It is a core engine that manages synchronization, replication, and configuration file management of FSR, and supports various platform environments.

FSR Service

It is a service that controls and manages the FSR resources.

FSR Utility

It is an command line interface program to control FSR.

Path

Install using the installation package provided. During installation, the FSR service (fsrservice) is registered as a service to start automatically at system startup.

The FSR installation adds the FSR_HOME and FSR_PATH environment variables to your system. FSR_HOME is the root path where FSR is installed and FSR_PATH is the% FSR_HOME%/bin path.

The default path where FSR is installed is:

Windows

C:\Program Files\fsr

Linux

/usr/bin

The following directory structure is created in this path:

directory	description
.install4j	Installer-related files are located.
bin	The executable file is installed.
buffer	Default file buffer path.
conf	Default configuration file path. System and resource configuration files are located.
db	The state of each resource is stored.
jre	JRE to run the installer.
logs	Log file path

Install

Windows

If you run the Windows installation package, you can easily install it through the wizard-type installation screen. There is no need to reboot the system and can be installed online without service interruption. This uninterrupted installation is the same for module updates or product removal.

Linux

Installation on Linux also provides online installation during service operation by default. However, in the case of Linux, you must first install the kernel filter framework module included in the FSR installation package, and then install the FSR clone package in order. The installation process is automatically performed by the installation package, and the installation method may differ slightly depending on the platform.

Red Hat series installs as rpm package and Debian series installs as deb package. In particular, the deb package uses the Dynamic Kernel Module Support (DKMS) method, which builds and installs modules directly on the target machine.

Updates, deletions can also be performed online without service offline.

SeLinux must be disabled before installation.
If the redirfs.ko module is already installed and running in the system, fsr installation will fail. This means that fsr cannot be operated because a product that is not compatible with fsr is installed on the system.

Secure Boot Support

Secureboot support is based on the signature of the fsr install module. Secure Boot support on Windows platforms is supported by signing its own SHA2 EV certificate, and Linux supports it in slightly different ways depending on the platform.

Windows

In Windows, the fsr module is distributed after obtaining EV certification from Microsoft in advance before distribution. No further action is required other than installing the fsr module as an installation package.

Linux

RedHat Family

Provides the public key for secure boot support in the package file (.run). You can use the kernel module in Secure Boot mode only by registering the provided public key.

Import fsr-module public-key
input password:
input password again:

The package installation process asks for a password for registration. The password is freely selectable and will be applied after rebooting. At this time, the registered public key is located in the /etc/pki/mantech/fsr_signing_key_pub.der path.

Debian Family

For the Debian family, the dkms package is used to build and install the module directly on the customer system. Therefore, private and public keys for secure boot are generated and registered in the customer system.

Private and public keys are automatically generated during package installation for user convenience.

Import fsr-module public-key
input password:
input password again:

In the process of registering the public key, the password required for registration is required and is applied after rebooting.
The generated and registered private key and public key are located in /etc/pki/mantech/fsr_signing_key.priv, /etc/pki/mantech/fsr_signing_key_pub.der path.