Migrate from Mideye 5.x to 6.x — Database Migration

This guide covers migrating from Mideye Server 5.x to 6.x. For minor version upgrades (6.x to 6.y), see Upgrades.

Note

If you’re upgrading from Mideye Server 4.x, upgrade to version 5.x first, then follow this guide.

---

Migration options

Option 1: New server

Install v6 on a fresh server, migrate database, redirect clients. Recommended — minimal downtime, easy rollback.

Option 2: Side-by-side

Install v6 alongside v5 on the same server. Useful when hardware is limited.

---

Before you migrate

1. Review the Pre-install Checklist — Ensure your environment meets v6 requirements

2. Back up your v5 installation

   • Database (full export)
   • Configuration files
   • TLS certificates

3. Document your current configuration

   • RADIUS client IPs and shared secrets
   • LDAP profile settings
   • Authentication type configurations

4. Plan maintenance window — Users cannot authenticate during the switchover

Shared database clusters

If multiple Mideye Servers share the same database, special considerations are required due to encryption of RADIUS Shared Secrets in v6. See Shared Database for details.

---

Option 1: Install on a new server (recommended)

Installing v6 on a new server minimizes risk and allows easy rollback by switching back to the v5 server.

Migration steps

1. Export the v5 database

   MySQL/MariaDB

   mysqldump -u root -p mideye > mideye_v5_backup.sql

   SQL Server

   Use SQL Server Management Studio to create a full backup, or:

   BACKUP DATABASE [MideyeServer]
   TO DISK = 'C:\Backups\mideye_v5_backup.bak'

2. Prepare the new server

   • Install your operating system (see supported platforms)
   • Install the database server
   • Create an empty database for Mideye

3. Import the v5 database to the new server

   MySQL/MariaDB

   mysql -u root -p mideye < mideye_v5_backup.sql

   SQL Server

   RESTORE DATABASE [MideyeServer]
   FROM DISK = 'C:\Backups\mideye_v5_backup.bak'

4. Install Mideye Server 6

   Follow the installation guide for your platform:

   • RHEL / Rocky Linux
   • Debian / Ubuntu
   • Windows Server

5. Configure database connection

   Edit application-prod.yml to point to your migrated database:

   Linux

   sudo nano /opt/mideyeserver6/config/application-prod.yml

   Windows

   Edit C:\Program Files (x86)\Mideye Server 6\config\application-prod.yml

6. Complete the Configuration Wizard

   Access the web GUI and complete initial configuration:

   • Verify the setup challenge from the log file
   • Set the root password
   • Configure Switch connection (use your existing customer port)

7. Verify data migration

   Log in and confirm:

   • Users are visible
   • LDAP profiles are configured
   • RADIUS clients are listed
   • Authentication types are correct

8. Redirect RADIUS clients

   Update your VPNs, firewalls, and applications to point to the new v6 server IP address.

   Tip

   If using a load balancer, you can add the v6 server to the pool and drain the v5 server for a seamless transition.

9. Decommission v5 server

   Once v6 is confirmed working:

   • Stop the v5 service
   • Keep the server available for a rollback period (recommended: 1-2 weeks)
   • Then decommission

---

Option 2: Side-by-side installation

Install v6 on the same server as v5. Both versions cannot run simultaneously due to port conflicts.

Caution

This option has higher risk — if v6 has issues, you need to stop it and restart v5 on the same hardware.

Migration steps

1. Export the v5 database

   # MySQL/MariaDB
   mysqldump -u root -p mideye > mideye_v5_backup.sql

2. Create a new database for v6

   CREATE DATABASE mideye_v6;

3. Import v5 data into the new database

   mysql -u root -p mideye_v6 < mideye_v5_backup.sql

4. Stop Mideye Server 5

   Linux

   sudo systemctl stop mideyeserver5
   sudo systemctl disable mideyeserver5

   Windows

   Stop-Service "Mideye Server 5"
   Set-Service "Mideye Server 5" -StartupType Disabled

5. Install Mideye Server 6

   Follow your platform’s installation guide. The installer will detect v5 is present and install v6 in a separate directory.

6. Configure v6 to use the new database

   Edit application-prod.yml and update the database name to mideye_v6.

7. Start Mideye Server 6

   Linux

   sudo systemctl start mideyeserver6
   sudo systemctl enable mideyeserver6

   Windows

   Start-Service "Mideye Server 6"

8. Complete the Configuration Wizard and verify

Rollback procedure

If you need to revert to v5:

1. Stop Mideye Server 6
2. Re-enable and start Mideye Server 5
3. Your v5 installation uses the original database (unchanged)

---

Post-migration verification

After migrating, verify these items:

Check	How to verify
Users visible	Web GUI → Users
LDAP sync works	Web GUI → Directories → Test connection
RADIUS clients connected	Check client status indicators
Test authentication	Attempt a login from a test client
Logs recording	Web GUI → Logs → Authentication Logs
Switch connection	Green indicator in System Status

---

Troubleshooting

Database connection fails

Ensure application-prod.yml has the correct connection string:

MySQL/MariaDB

spring:
  datasource:
    url: jdbc:mariadb://localhost:3306/mideye_v6?sslMode=TRUST
    username: mideye
    password: your_password

SQL Server

spring:
  datasource:
    url: jdbc:sqlserver://localhost:1433;databaseName=MideyeServer;trustServerCertificate=true
    username: mideye
    password: your_password

RADIUS shared secrets not working

In v6, RADIUS shared secrets are encrypted in the database. If you’re migrating to a shared database cluster, all servers must use the same keystore.p12 file. See Shared Database.

Switch connection fails

Your existing customer port from v5 works with v6. Verify:

• Firewall allows outbound TCP to primary.mideye.com and secondary.mideye.com
• Port number is correct in the Configuration Wizard

---

Need help?

Contact support@mideye.com for migration assistance.