# IQON DB archive created Purpose: record the verified database archive created after direct SSH/MySQL access was provided. Created: 2026-05-20 Updated: 2026-05-20 ## Status `VERIFIED`: DB archive exists remotely and locally, and gzip integrity passed. ## Vault storage The provided access credentials were stored in Vaultwarden under these item names: 1. `REG.RU hosting panel SSH SFTP - iqon.com server71` 2. `REG.RU FTP - iqon.com server71` 3. `REG.RU MySQL - iqon.com u0012812_default` No credential values are stored in this report. ## Database actually archived The live WordPress configuration uses: | Field | Value | |---|---| | DB name | `u0012812_iqon` | | DB user | `u0012812_iqon` | | DB host | `localhost` | Note: this differs from the separately provided MySQL credential whose database name was `u0012812_default`. The live site archive was created from the WordPress DB in `wp-config.php`. ## Archive paths | Location | Path | |---|---| | Remote server | `/var/www/u0012812/data/backups/iqon-u0012812_iqon-20260520-231601.sql.gz` | | Local temporary copy | `/private/tmp/iqon-u0012812_iqon-20260520-231601.sql.gz` | ## Verification evidence 1. Remote `mysqldump --no-tablespaces` completed successfully. 2. Remote `gzip -t` completed successfully. 3. Remote archive size was approximately `469K`. 4. Local `scp` completed successfully. 5. Local `gzip -t` completed successfully. 6. Local archive size was approximately `468K`. 7. SQL header matched `MySQL dump 10.13`. 8. SQL header matched `Database: u0012812_iqon`. ## Failed attempts retained for context 1. The provided `u0012812_default` MySQL credential did not authenticate for the target dump path used first. 2. A direct dump with default options failed because shared hosting lacked `PROCESS` privilege and the client attempted unsupported column statistics. 3. The successful command used `--no-tablespaces` and the actual WordPress DB credentials from `wp-config.php`. ## Remaining operational note The archive is stored in `/private/tmp` locally, which is temporary storage. If long-term retention is required, move the archive to an encrypted backup location outside the git repository.