Separated Deployment

• In both separated and independent deployment modes, you can run the systemd command to start BoostIO. If you want the bio_daemon process to be taken over by the OS and automatically restart when a fault or exception occurs, you can use this method. For details about the configuration, see the official documentation.
• In both separated and independent deployment modes, BoostIO has an independent bio_daemon process. It is specified that only one bio_daemon process can exist on each physical node to ensure data consistency.

You need to start the BoostIO process bio_daemon and then the JuiceFS process. During the startup of the JuiceFS process, the BoostIO SDK library is automatically loaded. The bio_daemon process can be manually started in the background.

You are advised to use this method if you want to monitor the bio_daemon process to immediately locate and rectify faults or exceptions. This method is suited for application development and function debugging scenarios.