The MySQL Connector
Archive MySQL databases during application decommissioning, version upgrades, or platform consolidation. Eliminate server costs while retaining every table and row in an open, queryable format.
🌟 Featured in Gartner® Hype Cycle™ for Data Management
Connectors
Data Governance
Enterprise Clients
Talk to a Connector Expert
MySQL Archiving for Application Lifecycle and Compliance
Archon’s MySQL Connector extracts tables, schemas, views, stored procedure metadata, and historical data from MySQL 5.6 through 8.x and archives them into open Parquet/Delta Lake format. Built for engineering and compliance teams retiring MySQL-backed web applications, migrating to cloud-managed databases, or managing multi-year regulatory data retention on application datasets.
MySQL powers a significant share of web applications, SaaS platforms, and line-of-business systems. When these applications reach end-of-life, the database history often carries ongoing obligations for transaction records, user data, and audit logs. Archon extracts and preserves this information so organizations can retire applications while maintaining access to required records.
- JDBC extraction from MySQL 5.6 through 8.x (Community and Enterprise)
- Tables, schemas, views, audit logs, and binary log records captured
- Stored procedure metadata, triggers, and schema structure preserved
- Cross-schema querying through Archon Analyzer after archive completion
- GDPR, PCI DSS, HIPAA, and CCPA retention policy support
Capabilities
Everything You Need for MySQL Data Operations
End-of-Life Version Data Extraction
MySQL 5.6 reached end-of-life in 2021, while MySQL 5.7 reached end-of-life in October 2023. Organizations storing regulated data on unsupported versions face increasing operational and governance risk. Archon extracts and archives that data, enabling safe instance retirement.
Application Database Archiving
Legacy web applications and line-of-business systems built on MySQL are decommissioned regularly. Archon archives the underlying database, including schema structure, audit tables, and historical transaction records, before the application is retired.
Cloud Migration Historical Data Offload
MySQL-to-Aurora, MySQL-to-Cloud SQL, and MySQL-to-RDS migrations use Archon to offload historical data to a Lakehouse before cutover, reducing migration scope while preserving retention requirements.
GDPR and CCPA Consumer Data Compliance
Consumer-facing applications using MySQL can address GDPR right-to-erasure and CCPA data deletion obligations through Archon's selective PII removal capability, applied to archived records while maintaining relational integrity.
Use Cases
How Enterprises Use the MySQL Connector
01 End-of-Support Instance Retirement
Organizations running MySQL 5.6 or 5.7, both beyond end-of-life, face security and governance concerns for regulated data. Archon archives historical information and enables instance retirement, eliminating ongoing infrastructure overhead.
02 Web Application Decommissioning
Web applications and SaaS platforms built on MySQL are frequently retired. Archon archives the application database, including schema, data, and audit trails, before shutdown, ensuring continued access to historical records.
03 Cloud Migration Historical Data Offload
MySQL-to-Aurora migrations use Archon to offload inactive historical tables to a Lakehouse before cutover, reducing Aurora sizing requirements while preserving long-term retention obligations.
04 GDPR Right-to-Erasure on Archived Records
Organizations managing customer data in MySQL can fulfill GDPR Article 17 obligations on archived records through Archon's selective PII field removal capabilities while preserving transaction integrity.
Technical Specifications
| Specification | Details |
|---|---|
| Connection Method | JDBC (MySQL Connector/J) |
| Supported Versions | MySQL 5.6, 5.7, 8.0, 8.x (Community and Enterprise) |
| Data Scope | Tables, schemas, views, stored procedures (metadata), triggers, audit logs, binary log records |
| Output Format | Parquet, Delta Lake, Avro, XML, CSV, TXT, TSV, Excel |
| Metadata Handling | Schema structure, stored procedure metadata, triggers, indexes, constraints |
| Transformation Rules | Schema normalization supported |
| Retention Management | GDPR, PCI DSS, HIPAA, CCPA retention schedules |
| Legal Hold | Database and table-level hold orchestration with audit trail |
| Deployment | On-premises · Cloud (AWS) · Hybrid |
| Security & Compliance | TLS 1.3 in transit · AES-256 at rest · WORM · Cryptographic hashing |
How It Works
Up and Running in 4 Steps
01
Connect to MySQL
Authenticate via JDBC to MySQL 5.6 through 8.x. Archon auto-discovers all databases, schemas, tables, views, stored procedures, and audit table structures.
02
Map & Configure
Define database and schema scope, binary log and audit table capture strategy, and jurisdiction-specific retention schedules. Configure PII masking for GDPR compliance.
03
Validate & Preview
Run a dry-run against sample MySQL databases. Quality report flags null primary keys, broken foreign key references, and binary log extraction anomalies.
04
Archive & Monitor
Execute full extraction. Cryptographic hashes and trusted timestamps applied per table. Data searchable via Archon Analyzer immediately on ingestion.FAQ
Common Questions About the MySQL Connector
-
1. Does Archon support MySQL versions that have reached end-of-life?
Yes. Archon extracts from MySQL 5.6, 5.7, 8.0, and 8.x, including unsupported versions that organizations are preparing to retire.
-
2. Can Archon archive MySQL binary log records for change data capture?
Yes. Archon captures binary log records alongside base table data, preserving the full change history with operation type, timestamp, and before/after row images.
-
3. How does Archon handle MySQL databases across multiple instances?
Archon supports multi-instance extraction with a single configuration, normalizing schema differences across MySQL versions and delivering a unified archive.
-
4. Can Archon archive MySQL without impacting live application performance?
Yes. Archon uses read-only JDBC extraction with configurable parallelism and throttling controls, minimizing impact on production workloads.
-
5. Does Archon support GDPR right-to-erasure on archived MySQL consumer records?
Yes. Archon supports selective PII field removal from archived MySQL records while preserving the transaction and relational structure required for compliance.
Retiring a MySQL-backed application?
Talk with an Archon specialist about preserving historical data, reducing legacy infrastructure costs, and maintaining compliance access after application decommissioning.
