MySQL/MariaDB
To create a new application for MySQL database backup, go to the tab: Applications -> Instances
Then select the Create button. The Creating an Application Definition section will be displayed, which needs to be completed.
This is a description of how your script is going to be invoked - you need to specify:
Name - unique name of the application in the Storware Backup & Recovery system
Choose Node Config - select which node should perform the task
Backup policy - specify which backup policy should be used for this application
Command execution configuration - select a prepared template for MySQL backup or create a new one yourself
On the SSH access subtab, complete the following fields:
Host - set the address of the host where the MySQL instance exists
Port - set the host port
Next, select OS Credentials or create a new one and provide the following information:
Name - unique name of the OS Credentials
User - indicate a user for connecting to the ssh
Password - enter the connection password
SSH key path - alternatively you can specify the ssh key path for authorization
After saving the changes to the application, you need to configure the environment variables in the settings section of your application as needed.
When using the built-in script for database backup, define:
VP_MYSQL_DBLIST - a comma-separated list of database names to back up
VP_MYSQL_SCRIPTPATH - the path to the MySQL/MariaDB server where Storware Backup & Recovery can place and execute the backup script
VP_MYSQL_STOREPATH - the path to the MySQL/MariaDB server where Storware Backup & Recovery can place the temporary backup file. No other files should be stored in the given path since everything is removed after the backup is finished
VP_MYSQL_USER - login username to MySQL/MariaDB
VP_MYSQL_LOGFILE - the path to the Mysql/MariaDB server where Storware Backup & Recovery can place the log file from the backup job
VP_MYSQL_PASSWORD - the database user password
Note: After the new application is fully configured, save the changes and go to the Backup SLAs configuration.
Last updated