The Database Management & Technical Maintenance module provides administrators with the tools necessary to manage backend data structures, perform database migration or replacement, and execute routine maintenance tasks.
Because database replacement completely overwrites existing project records, task histories, user logs, and system configurations, this operation is strictly safeguarded with administrative controls and backup requirements.
Key Capabilities
Database Replacement & Restoration: Import structured .sql or .bak database files to restore project environments or clear legacy data.
Automated Data Backup: Download full local snapshots of project records, user directories, and system logs prior to maintenance.
Integrity Validation: Verify data schema compatibility before executing replacement scripts.
Maintenance Mode Control: Lock user access during database migration to prevent data corruption.
🔒 Security & Access Permissions
🛑 CRITICAL RESTRICTION: The Replacing Database module is strictly restricted to System Administrators. Misuse of this module can result in irreversible data loss.
1.Enable System Maintenance Mode:
To prevent active users from writing data during database operations:
Log into Lynx PMIS with Administrator credentials.
Navigate to Administration → Replacing Database (or System Settings).
Toggle Maintenance Mode to ON.
Provide a maintenance notice message (e.g., "Lynx PMIS is undergoing scheduled database maintenance. Service will resume in 30 minutes."). Active users will see a read-only maintenance banner.
[IMAGE PLACEHOLDER: Maintenance Mode toggle switch and custom broadcast message input box]
2.Export a Local Safety Backup:
ALWAYS generate a current backup before replacing the active database.
On the Replacing Database panel, locate the Backup & Export section.
Click Generate Full System Backup.
Save the timestamped backup file (e.g., LynxPMIS_Backup_2026-08-24.bak) to a secure local or encrypted cloud storage location.
[IMAGE PLACEHOLDER: Backup export panel displaying backup generation button and download confirmation]
3.Upload & Validate New Database File:
Under the Database Replacement section, click Browse File and select the validated replacement file.
Click Validate Schema.
Lynx PMIS will run a pre-check verification:
✅ Schema Structure Compatibility
✅ License Allocation Mapping
✅ File Integrity Checksum
[IMAGE PLACEHOLDER: Database upload dialog with validation progress indicators and status checks]
4.Execute Replacement & Confirm:
Once schema validation passes, type the security confirmation phrase into the verification field:
REPLACE-DATABASE-CONFIRM
Enter your Admin Security PIN / Password.
Click Execute Database Replacement.
Wait for the progress indicator to reach 100%. Do not refresh or close your browser during this step.
[IMAGE PLACEHOLDER: Security confirmation modal requiring text entry and Admin credentials]
5.Verify System Integrity & Disable Maintenance Mode:
After completion, check the automated Migration Log for any warnings or error codes.
Spot-check key modules (Workspace, Projects, and S-Curves) to verify record restoration.
Navigate back to Replacing Database and toggle Maintenance Mode to OFF to restore standard user access.
[IMAGE PLACEHOLDER: Migration Log summary table displaying green success status]
In the event of an unexpected server disruption, internet disconnection, or validation error during database replacement:
🛡️ Automated Fail-Safe: Lynx PMIS creates an automated Rollback Point immediately before initiating replacement operations. If the import process is interrupted, the system automatically restores the last stable rollback point.
If the application becomes unresponsive, access the server recovery portal at [https://your-domain.com/admin/recovery](https://your-domain.com/admin/recovery).
Select Restore Last Rollback Point.
Upload the manual backup file generated in Step 2 if auto-rollback fails.
Contact technical enterprise support immediately.
💡 Schedule Operations Off-Peak: Always schedule database replacement or schema updates outside standard operating hours (e.g., weekends or late evenings) to minimize impact on site teams.
💡 Maintain Retainage History: Keep at least three consecutive monthly database backup snapshots stored in isolated offline storage for audit compliance and disaster recovery.
Database replacement queries and disaster recovery assistance:
📧 Emergency Support Email: lynxpmis.support@gmail.com
📞 Urgent Technical Desk: 019-3304704
⏰ 24/7 Admin Emergency Line: Contact your assigned enterprise support engineer directly.