Migrate to another server

Sometimes you'll find yourself in the position to migrate a WriteBackExtreme installation to a different server.

If you need to move your WriteBackExtreme installation to a new server, follow the steps below based on your operating system. This ensures both your application files and repository database are safely transferred and functional.

---

🪟 Windows Migration Steps

1. Back up the current installation

   • Create a full backup of your WriteBackExtreme directory

   • Back up the repository database

2. Transfer to the new server

   • Copy the entire WriteBackExtreme directory to the new machine

   • (Optional) If the repository database is hosted locally, migrate it to the new server as well

3. Launch the application

   • Run WriteBackExtreme.exe on the new server

4. Update database settings if needed

   • If your repository database location or credentials changed, update them in the configuration pane

5. Re-enable the Windows Service (if used)

   • Toggle the service setting off and back on to re-register the Windows service on the new host

6. Update your DNS

   • Point your (sub)domain DNS records to the new server IP

7. Prevent duplicate connections

   • Stop WriteBackExtreme on the original server to avoid simultaneous repository access

---

🐧 Linux Migration Steps

1. Back up the current installation

   • Back up /usr/local/share/writebackextreme

   • Back up your repository database

2. Prepare the new server

   • Run the WriteBackExtreme installation script to set up dependencies

3. Transfer application files

   • Copy the backed-up /usr/local/share/writebackextreme directory to the new server

4. Update configuration (if needed)

   • Edit wbe.config.yaml to reflect any changes in the database location or credentials

5. Start the WriteBackExtreme service

   • Use systemctl or your preferred service manager to launch the application

6. Update your DNS

   • Point your (sub)domain DNS records to the new Linux server

7. Prevent duplicate connections

   • Shut down WriteBackExtreme on the previous server to avoid conflicting access to the same repository