SetFN
SetFNDocsOctober 27, 2026

Moving to a New Server

This guide explains how to move SpaceBuilder installed on Linux to a new server. Copy the configuration folder and the data path to the new server, and then register the license again on the new server.

Before you begin

  • Work in the terminals of the existing server and the new server.
  • Access is interrupted during the move, so do it when few users are connected.
  • Check that the new server has enough storage space for the existing data.
  • We recommend using a user account with the same name and the same paths on the new server. If a path changes, you must edit the configuration file.

Check what to move

LocationContents
~/.config/SetFNConfiguration file, user accounts, and server settings data
Data pathFiles saved by teams and users

Check the data path on the existing server with the following command.

~/setfn-spacebuilder homepath get

Prepare the existing server

  1. Run Release License in License Management on the administrator home. A license is tied to a device, so you must release it before you can register it on the new server.
  2. Stop SpaceBuilder.
    sudo systemctl stop setfn-spacebuilder
  3. Copy the configuration folder and the data path to the same paths on the new server. The following example uses rsync.
    rsync -a ~/.config/SetFN/ <user>@<new server address>:~/.config/SetFN/
rsync -a <data path>/ <user>@<new server address>:<data path>/

Start on the new server

  1. Prepare the installer as described in Installing on Linux. Use the same version as the existing server. Check the version on the existing server with ~/setfn-spacebuilder version.
  2. If the data path differs from the existing server, edit the path in ~/.config/SetFN/config.yaml.
    server:
  homeFolder: <new data path>
  3. Set up auto-start as described in Installing on Linux, and start SpaceBuilder.
    sudo systemctl start setfn-spacebuilder
  4. Log in to the administrator page and register the license again in License Management.
  5. Change the address that users connect to so that it points to the new server. See Checking Your Access Address (Local/Internal Network) and Choosing an External Access Method.

Check the result

  • Check that you can log in with an existing account.
  • Check that the files in team folders and personal folders are visible.
  • Check the license status on the administrator home.
  • If you use an external vector DB such as Qdrant or Milvus, check in Knowledge Storage that the new server can connect to it.

Run it alongside the existing server

To keep running the existing server and run the copied server separately, run the following commands on the copied server before you start it for the first time.

~/setfn-spacebuilder admin vector-instance-id
~/setfn-spacebuilder admin prepare-clone <printed UUID>

The first command prints the current instance UUID. The second command assigns a new instance UUID to the copied server and sets aside the knowledge indexes that were copied with it. When you start the server, it rebuilds the knowledge indexes from the stored files.

You must also register a license on the copied server. The number of servers you can run depends on your plan.

Good to Know