1.Enabling System Maintenance Mode:

Before running updates, lock system access to prevent users from making concurrent database edits:

1. Log into Lynx PMIS with System Admin credentials.

2. Navigate to Administration → Database Management & Maintenance.

3. Toggle Maintenance Mode to ON.

4. Enter a user notice (e.g., "Scheduled maintenance in progress. System access will resume at 14:00."). Active users will see a top notification banner blocking data entry.

[IMAGE PLACEHOLDER: Maintenance mode toggle panel showing custom message input field]

2.Generating a Local Pre-Maintenance Backup:

ALWAYS download a complete backup file prior to performing technical database updates.

1. On the maintenance dashboard, scroll to the Backup & Snapshots section.

2. Click Generate Full System Backup.

3. Download the generated .bak or .sql file to secure, encrypted storage.

[IMAGE PLACEHOLDER: Backup generation button with download link and file timestamp]

3.Uploading & Validating Database Files:

1. Under the Database Replacement tab, click Select File and locate your new database script.

2. Click Validate Schema File.

3. Wait for Lynx PMIS to run automated checks:

   • ✅ Schema Version Compatibility

   • ✅ License Key & User Account Alignment

   • ✅ Checksum Verification

4. 
   

[IMAGE PLACEHOLDER: Schema validation progress bar displaying green verification ticks]

4.Executing Replacement & Confirming Restoration:

1. Once schema validation returns a Pass status, enter the safety confirmation string:

CONFIRM-DATABASE-REPLACE

2. Enter your Admin Security Password.

3. Click Execute Database Replacement.

4. Keep your browser window open until the progress bar reaches 100%.

[IMAGE PLACEHOLDER: Confirmation modal requiring safety phrase entry and password verification]

5.Post-Maintenance Verification & Reactivation:

1. Review the System Maintenance Log for any post-execution warnings or errors.

2. Verify core data integrity by spot-checking active projects in the Projects & S-Curves modules.

3. Return to Database Management & Maintenance and toggle Maintenance Mode to OFF to restore full user access.

[IMAGE PLACEHOLDER: System maintenance log table showing successful migration confirmation]

💡 Technical Maintenance Best Practices

💡 Schedule During Off-Peak Hours: Always schedule database replacement or schema maintenance during off-peak hours (e.g., weekends or late evenings) to prevent operational disruption.

💡 Maintain Backup Retention Policies: Retain at least three consecutive monthly backup snapshots in secondary storage to satisfy auditing requirements and enable disaster recovery.

❓ Frequently Asked Questions (FAQ)

Q1: What happens if the database replacement process is interrupted?

A: Lynx PMIS creates an automated Pre-Execution Rollback Point. If the connection or script fails midway through execution, the system automatically reverts to the rollback point to maintain service stability.

Q2: How often should automated database backups be created?

A: System Administrators should configure daily automated background backups, along with executing a manual backup before any server update or database replacement.

📞 Support & Assistance

For emergency disaster recovery or database migration assistance:

• 📧 Emergency Support Email: lynxpmis.support@gmail.com

• 📞 Technical Hotline: 019-3304704