_ no
SQL dumps of a single working schema
ยท prefix
Backups
Remaining in the working scheme
Restore completely replaces the current schema data
Dumps
Engine
Engine, number of entries, size and maintenance.
Engine, volume and approximate number of rows of each table of the working scheme.
Download a copy
Posts
from
Importing tables
Migrations
Don't close the tab. If the connection is lost, AVE.cms will check the saved state of the task.
The operation has not yet started
Optimize
Optimize everything
Convert to InnoDB
Before launching, AVE.cms will automatically create a backup copy. Do not close the page until the operation is completed.
Preparation
Preparing for recovery
Search by table name
Full backup
Check
Checking the selected file
The working scheme uses InnoDB
Backup
Backups
No backups yet
Own and downloaded SQL dumps of the database.
Created
Safety copy
Scheme
The scheme is current
Tables
MyISAM tables
tables support transactions and failover.
Tables with prefix
Table
Tables
Current schema tables
File
Backup files
stored in
These are tables transferred from Legacy with the old engine. Before transferring to InnoDB, make a full backup: the operation may temporarily block writing to large tables.
SQL commands:
, copy date:
, records:
, errors:
, lines:
. Automatic rollback failed; use a safety backup
. The original base is returned from the safety copy
. Tables:
\s*\(/is',
);
foreach ($patterns as $type => $pattern) {
if (preg_match($pattern, $statement, $match)) {
return array('type' => $type, 'table' => (string) $match[1]);
}
}
throw new \RuntimeException('Dump contains an unsupported SQL command');
}
public static function enumFallbacks($ddl)
{
$fallbacks = array();
foreach (preg_split('/\r\n|\r|\n/', (string) $ddl) as $line) {
if (!preg_match('/^\s*
", current base - "
B
The base has been restored
The database was restored from
Database
Database: service
Database: view
OPTIMIZE will be performed on all tables of the current prefix.
A gzip dump of a single working schema will be created.
will be deleted without the possibility of recovery.
Unapplied built-in partition migrations will be performed and rights will be synchronized. This operation does not read data from backups.
Backup created:
Backup deleted
There are too many SQL commands in the dump
Attention:
Returning the original database
Restoring tables
Restore
Restore the database from a copy?
Restoring the database
The restore takes longer than expected. Refresh the page and check the status of the database.
The restore will replace all tables in the current installation with the data from the backup.
Restore failed:
Recovery not started
Recovery stopped
Recovery prepared
Restore aborted:
All kernel migrations have already been applied
All tables imported and cache cleared
Operation in progress
GB
Done
Done:
The dump was created in the database "
To restore, select the full dump created by AVE.cms
Another backup is already being created
Another restore is already in progress
Restore job not found
The restore job belongs to another user
Running recovery is deprecated. Check your copy again
The backup directory is not writable
KB
The table command is duplicated in the dump:
Copy uploaded
Copy uploaded and verified:
MB
Let's start importing the backup copy
Failed to complete backup download
Failed to complete dump file
Failed to download copy:
Failed to change table engine:
Failed to disable foreign key checking
Failed to prepare recovery
Failed to prepare the current schema for recovery
Failed to get recovery status.
Failed to apply kernel migrations:
Failed to check ENUM values in dump command
Failed to verify backup
Failed to read backup file
Failed to create backup:
Failed to create recovery job directory
Failed to create dump file
Failed to save downloaded file
Failed to save recovery state
Failed to delete file
not specified
Unknown operation
Unknown table
Incorrect recovery ID
No tables to process
No tables to back up
Update runtime
Maintaining tables, kernel migrations, creating, restoring and deleting backups.
Waiting for a protected process to start
Optimize all tables?
Clear caches and module registry
Error
Loading error
Network error
Translated:
Translate
Convert MyISAM to InnoDB?
Preparing a working diagram
Only .sql and .sql.gz files are supported
The prefix in the header is different from the current one; the actual table names have already been checked.
Applied kernel migrations:
Apply
Apply kernel migrations?
Backup verification is outdated. Run it again
Checking the source file
View tables and backups.
The working base has not changed yet
Backup size is invalid
The unpacked dump exceeds the allowed size
Backup verified
The server did not open the recovery stream
System
First, create a full backup. ALTER TABLE may temporarily block the record, so in production, perform the operation in the maintenance window.
Connection lost. Check the list of backups after refreshing the page.
Create
Create a backup?
Creating a safety copy
Recovery state
The state is saved automatically
tables
There are no MyISAM tables left
tables)
table
The table does not apply to the current installation:
Tables transferred to InnoDB:
TB
The current data will be replaced, but before that a safety backup will be automatically created.
Delete
Delete backup?
Deleting the tables of the current installation
The file has changed since verification. Restore canceled
The file has changed since verification. Check again
File not found
Backup file not loaded
Backup file not found
File: