BEFORE YOU BEGIN
Check before you begin
This guide covers the inspected Linux SQL → MySQL agent workflow. mysql_dump and mysql_binlog have different prerequisites; MariaDB is a separate engine/method. A menu option is not end-to-end acceptance for every storage engine, GTID/replica topology or arbitrary point-in-time recovery.
Live verification limit: no new MySQL screen was captured in this inspection; PostgreSQL screenshots were not substituted. Steps are based on local Agent Policy and MySQL restore templates. Dump/binlog chains, target forms and data acceptance require separate validation in the installed release. No instance/policy, backup/restore or binlog purge operation was performed.
- Engine, agent/master releases and instance identity
- Database scope, method and access privileges
- Full base, log chain and repository access
- Isolated destination, collisions and application acceptance
011. Define release, instance and database scope
With the DBA, record MySQL server/client and agent/master releases, host/port, instance and test database. Inventory extensions, charset/collation, roles/privileges and application dependencies. Use small test data for initial acceptance; do not equate cluster/replica topology with a standalone source.
Expected resultMethod, selection and acceptance evidence are recorded.
022. Verify agent and native-tool access
Validate access from the correct Linux agent to MySQL, mysql/mysqldump/mysqlbinlog tool paths, release compatibility and repository capacity. Scope credentials and required privileges with the DBA. A running agent does not establish database discovery or binlog access.
Expected resultMethod, selection and acceptance evidence are recorded.
033. Select the engine and method under SQL
Select Agent, Policy Name and Storage in Agent Policy → Create Agent Policy. Under SQL → MySQL match MySQL Dump Full Only (mysql_dump) or MySQL Dump Full + Binary Log Incremental (mysql_binlog) to the DBA plan. A default binlog selection does not mean prerequisites are ready.
Expected resultMethod, selection and acceptance evidence are recorded.
044. Check Clients selection and consistency
Select the test database under the instance and compare the summary. Validate expected table/routine/trigger/event scope for Single Transaction and Routines & Events with the DBA. The Single Transaction description does not automatically resolve nontransactional tables or concurrent DDL effects; test user/grant coverage separately.
Expected resultMethod, selection and acceptance evidence are recorded.
055. Record physical and log-chain prerequisites
For mysql_binlog validate log_bin, server_id and binlog retention. Full-dump coordinates must align continuously with subsequent log files/positions or GTIDs. Do not change source binlog purging before backup acceptance. No binlog replay or point-in-time recovery was executed in this inspection.
Expected resultMethod, selection and acceptance evidence are recorded.
066. Plan scheduling and initial backup acceptance
Check scheduling and retention actually exposed for the engine/method in Advanced Settings and Schedules. Compare Full-base and dependent log/differential/incremental-chain retention with capacity; do not assume every method applies to each engine. In an approved small test, record task result, repository output and catalog method together.
Expected resultThe selection and relevant acceptance evidence are recorded.
077. Complete database and application acceptance
Use the separate engine restore guide to validate database startup, schema, sample queries, row counts and application access on an approved isolated target. Active, Last Backup or a success notification alone is not content acceptance. Record backup identity, method, time and the required chain in the report.
Expected resultThe selection and relevant acceptance evidence are recorded.
COMMON QUESTIONS
Does a successful task mean the application is ready?
Not by itself. Engine integrity, required log chains, data queries and application access need separate validation; HA/topology acceptance is assessed separately.