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 and Incremental Backup restore scenarios of MariaDB

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 the MariaDB service and copy the prepared Full Backup to the MariaDB 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 MariaDB Server by entering the applicable command at a command prompt. Before restarting the MariaDB Server, note that if you are running MariaDB 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 in MariaDB

If you are using Mariadb-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 Mariadb-backup utility 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://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/

When MariaDB 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 MariaDB Server, usually mysql. For example, to recursively change ownership in a typical installation of MariaDB 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 mariadb.service
sudo systemctl status mariadb.service
 

Check MariaDB documentation for more details.

Start services in Windows environments

Use the Windows Services Console to start the MariaDB service, typically named MariaDB. Check MariaDBdocumentation for more details.

Using advanced restore procedures for MySQL Standard/Community

This topic describes other restore operations that you can perform with the plug-in for the MySQL Standard/Community option.

•
Renaming a database during a restore
•
Restoring to a different MySQL Instance on the same server
•
Recovering to an alternate MySQL Server
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating