Maintenance, backup and updates
Classic 2.0.0 provides settings maintenance, upgrade, uninstall retaining data, reattachment and backup/restore tools. Before maintenance, inventory versions, unsynced work and unresolved posting/printing results, and follow the matching release documentation.
Record versions and pending work
In System, record DG, contract and source versions, worker heartbeat and open commands. Help content has its own revision; do not confuse them. Stop new dispatch, confirm App synchronization and inventory UNKNOWN/IN_FLIGHT commands and manual-review print jobs for supervisors/operations.
Complete backup scope
Preserve the DG database, configuration and necessary secrets under controlled access. Local Odoo also requires a consistent-time Odoo database and filestore; coordinate external Odoo with its administrator. KPI CSV, copied Web pages or DG-only database backup are not complete system backups. Never put secret backups in public directories or issue reports.
Update and rollback principles
Operations should follow approved versions, component compatibility and official procedures, first validating restore in isolation. After schema changes, replacing only old program files is insufficient; restore compatible program, database and files together. Old-architecture scripts are not update entrances for the new version.
Checks after restarting
After database, DG server and worker recover, check source health, probe DONE, original commands and device sync. Resolve UNKNOWN using original receipts, not duplicate shipments. A historical restore may lag work already executed by external ERP or App; reconcile manually before dispatch resumes and never assume every pending item can be redone.
Classic update and backup tools
Run Setup again to modify settings, upgrade or reinstall using retained data. Uninstall keeps the data directory. Backup and recovery (https://github.com/eltonwangpx-wq/distributiongo-classic#backup-and-recovery-administrator-powershell) require the same host, role, paths and application package. Backups contain private keys: keep them protected. A Web-only backup does not include the remote database. ThousanAI starts enabled with a unique local key, without a bundled model API key; cloud questions require connectivity and privacy consent.
Is downloaded CSV a backup?
No. It is a report without complete orders, assignments, results, commands, settings and necessary files; it cannot restore DG.
May I rerun all pending commands after restore?
No. ERP or App may already have completed work absent from the backup. Verify receipts, goods and sync results before operations decide recovery.