1 |
To generate a prepared Full Backup to be restored, submit a job in which you have selected the Restore, Extract Raw Full Backup… option on the Options tab. |
2 |
To shut down MySQL and copy the prepared Full Backup to the MySQL Server repository, submit a job in which you have selected the Shutdown MySQL Server and Copy Back… option on the Options tab. |
1 |
To generate a prepared Full Backup to be restored, submit a job in which you have selected the Restore, Extract Raw Full Backup… option on the Options tab. |
2 |
To apply the required Incremental Backups to the prepared Full Backup in the order in which they were backed up, submit the applicable number of jobs in which you have selected the Restore, Extract Incremental Backup… option on the Options tab. |
3 |
To shut down MySQL and copy the prepared Full Backup to the MySQL Server repository, submit a job in which you have selected the Shutdown MySQL Server and Copy Back… option on the Options tab. |
https://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/mysqlbackup.restore.html
When MySQL datafiles are restored, file and directory privileges are preserved. However, files might be written to disk as root user. After restoring a backup you may have to change the ownership of the restored files with the user and group of the MySQL Server, usually mysql. For example, to recursively change ownership in a typical installation of MySQL Server, where the data directory is located in /var/lib/mysql, the following command could be applied:
After changing permissions, the MariaDB Server can be restarted:
Check MySQL documentation for more details.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center