Q:What are the basic requirements for the infrastructure environment and network environment for deploying HBlock?
A: HBlock is required to be deployed on a server with a Linux operating system environment and must meet the minimum configuration requirements. Each server in HBlock can access other servers through the network. In addition, users need to ensure that internal applications can access the HBlock service.
Q:How many servers are needed to deploy HBlock in a cluster?
A:At least three servers. When HBlock stores data replicas, it will store the replicas in other nodes besides this node. This ensures that when the current node fails, the application can also ensure reliability by accessing the replica data of other nodes. At the same time, the system will reconstruct the data on the failed server and the damaged disk.
Q:Can the HBlock service start automatically after the server is restarted?
A: You can perform the following steps to enable the HBlock service to automatically start after the server is restarted.
1. Create a management script for the stor system service:
2. Set up the HBlock system service to run on startup:
chmod +x /etc/init.d/stor chkconfig --add stor chkconfig stor on
Q:How to restart the HBlock Cluster?
A: You need to manually restart the HBlock service of each server in the cluster. In order to ensure that the user's data is not affected, it is recommended to proceed with the following steps:
1. Stop the read-and-write operations of the Client application.
2. Client disconnects from iSCSI:
If client is Windows operating system, offline the disk first and then disconnect iSCSI Target.
If client is Linux operating system, execute the following command.
umount DIRECTORY_NAME_OR_PATH #Disconnect iscsiadm -m node -T iSCSI_TARGET_IQN -p SERVER_IP -u
3. Execute the command ./stor stop on each server where HBlock is located.
4. To restart the HBlock service, you can use one of the following methods:
Execute the command ./stor start on each server where HBlock is located.
Directly restart all servers where HBlock is located: You can refer to “Can the HBlock service start automatically after the server is restarted?”, ensure that all services of HBlock are automatically restarted when the server is restarted.
Q: How to configure HBlock access permissions?
1. Turn on the firewall: systemctl start firewalld.
l For IPv4 addresses: firewall-cmd --permanent --add-rich-rule=rule family=ipv4 source address=IP port protocol=tcp port=3260 accept.
l For IPv6 addresses: firewall-cmd --permanent --add-rich-rule="rule family=ipv6 source address=IP port protocol=tcp port=3260 accept".
3. Restart the Firewall: firewall-cmd --reload.
4. Automatically Starts at Boot: systemctl enable firewalld.service.