Remote and Local Database

User data is stored in both the local (client) database and a remote (server) database.

You can switch the primary database (local or remote) using the database switch control in the top-right of the main UI.

All page operations (create, delete, query, update) apply to the currently selected primary database.

How to switch the primary database

Path: Main menu > Settings > Database Switch or use the database switch button in the top-right of the UI.

Steps:

1. Click the database switch button and choose Local or Remote.
2. The system will prompt to reconnect and confirm saving the selection as the current session's primary database. After confirmation, a reconnection may occur and you might be required to log in again.
3. If switching to the remote database, ensure the network is reachable and remote login credentials are configured.

()

Synchronization and conflict handling

Synchronization supports one-way or two-way flows: remote→local or local→remote. Typical practice is to manage users centrally on the remote database and sync to clients.

When conflicts occur, they are recorded in a conflict log. Administrators should review conflicts and merge or roll back changes according to policy (for example, prefer remote changes or use timestamp-based resolution).

Backup and security

• Backups: Regularly back up local database files (default path is in the installation guide). Recommend daily incremental backups and weekly full backups, retaining at least 30 days of backups.
• Remote database: Confirm whether the remote server has automatic backups. Document backup owners and recovery procedures in your operations guide.
• Transport security: Remote connections should use secure channels (HTTPS/TLS or VPN) to avoid transmitting credentials in clear text.
• Password policy: Enforce strong passwords and periodic rotation; enable account lockout policies to prevent brute-force attacks.

()