Chat now with support
Chat with Support

NetVault Plug-in for MySQL 13.2 - User Guide

Introducing NetVault Plug-in for MySQL Installing and removing the plug-in Configuring the plug-in Backing up data Restoring data
Restoring data: an overview Restoring data Using advanced restore procedures for MySQL Standard/Community
Working with native MySQL replication Using the plug-in in a Failover Cluster environment Troubleshooting

Full Backup only restore scenarios

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.
3
Restart the MySQL Server by entering the applicable command at a command prompt. Before restarting the MySQL Server, note that if you are running MySQL in a Linux or Unix system, data files might be written to disk as root user. After restoring a backup you may have to change the ownership of the restored files. Ensure to read the section Additional step for Linux and UNIX environments.

 

Full and Incremental Backup restore scenarios

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.
4
Restart the MySQL Server by entering the applicable command at a command prompt. Before restarting the MySQL Server, note that if you are running MySQL in a Linux or Unix system, data files might be written to disk as root user. After restoring a backup you may have to change the ownership of the restored files. Ensure to read the section Additional step for Linux and UNIX environments.

Additional step for Linux and UNIX environments

If you are using MySQL Enterprise Backup in a Linux or UNIX environment, verify that the file-ownership and permissions information for the restored data matches what it was before the data was backed up. Because the mysqlbackup script does not record this information during the backup process, the file-ownership might be different after the restore is completed. For more information, see

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:

sudo chown -R mysql:mysql /var/lib/mysql
 

After changing permissions, the MariaDB Server can be restarted:

 
sudo systemctl start mysqld.service
sudo systemctl status mysqld.service

Check MySQL documentation for more details.

Start services in Windows environments

Use the Windows Services Console to start the MySQL service, typically named MySQL80. Check MySQL documentation for more details.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating