Source:MySQL Backup: Difference between revisions

From SEPsesam
(Rewritten, ready for review.)
No edit summary
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<noinclude>{{draft}}
<noinclude><div class="noprint"><languages />
{{Copyright SEP AG‎|en}}
<br />
{{Navigation_latest|release=4.4.3|link=[[Special:MyLanguage/MySQL|MySQL]]}}</noinclude>''''


==Overview==
<translate>==Overview== <!--T:3--></translate>
<noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Additional resources</b></center>


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
</div></noinclude><span style="font-size:92%; line-height: 1.3em; color:grey;"><translate><!--T:9--> The procedures and  functions described here represent only some of the recommendations and examples for MySQL database backup. The provided database backup options are not part of SEP sesam, but only some of the options that can be used for backup. Detailed information about MySQL backup policies and strategies can be found in [https://dev.mysql.com/doc/ MySQL Documentation].</translate></span>
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:MySQL_Restore]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | See also: [[Special:MyLanguage/4_4_3:MySQL_Restore|MySQL Restore]]
|}


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
<translate><!--T:10-->
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]
The SEP sesam extension for MySQL and MariaDB is part of a client package and enables online backup of one or more MySQL databases. SEP sesam uses the <tt>mysqldump</tt> program to connect to the MySQL server and create the SQL dump file. The dump file produces a set of SQL statements required to re-create the database. For details on <tt>mysqldump</tt> program, see MySQL documentation [https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html mysqldump — A Database Backup Program].</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.
|}


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
==={{anchor|requirements}}<translate><!--T:11-->
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Troubleshooting_Guide#MySQL_backup]]
Requirements===  
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide#MySQL_Backup|MySQL troubleshooting]].
|}


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
<!--T:12-->
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=IBM_DB2]]
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | If you are using an older SEP sesam version, refer to [[Special:MyLanguage/MySQL|MySQL archive]].
*<translate><!--T:13--> Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#MySQL|support matrix]] for a list of supported MySQL/MariaDB versions.</translate>
|}</div></noinclude>
*<translate><!--T:14--> SEP sesam Server v. ≥ 4.4.3. Check the [[Special:MyLanguage/SEP_sesam_Requirements#hardware|hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]], [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]] and [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]].</translate>
*<translate><!--T:15--> [https://download.sep.de/ Download the SEP sesam Client package] on the MySQL database host (the MySQL backup module is already included in the client package).</translate>
*<translate><!--T:16--> A user account with sufficient privileges to perform backup and restore operations.</translate>
*<translate><!--T:17-->
SEP sesam MySQL backup module requires a license. For details, see [[Special:MyLanguage/Licensing|Licensing]]. </translate>


<span style="font-size:92%; line-height: 1.3em; color:grey;">The procedures and features explained herein provide only some of the recommendations and examples on how to back up the MySQL databases. Provided database backup options are not part of SEP sesam, they are merely some of the options that can be used for backup. For detailed information on MySQL backup policies and strategies, refer to [https://dev.mysql.com/doc/ MySQL Documentation].</span>
=={{anchor|add_client}}<translate><!--T:18-->
Installing and adding MySQL client to SEP sesam environment ==


SEP sesam extension for MySQL and MariaDB is a part of a client package and enables an online backup of one or more MySQL databases. SEP sesam uses <tt>mysqldump</tt> program for connecting to MySQL server and creating the SQL dump file. The dump file produces a set of SQL statements required to re-create the database. For details on <tt>mysqldump</tt> program, see MySQL documentation [https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html mysqldump — A Database Backup Program].
<!--T:19-->
Once you have [https://download.sep.de/ downloaded] and [[Special:MyLanguage/5 0 0:SEP sesam Quick Install Guide|installed]] the SEP sesam Client package, configure your MySQL client by adding it to the SEP sesam environment: '''Main selection''' -> '''Components''' -> '''Clients''' -> '''New Client''' -> add your MySQL client. For details, see [[Special:MyLanguage/5 0 0:SEP sesam Quick Install Guide|Quick Install Guide]] and [[Special:MyLanguage/Configuring_Clients|Configuring Clients]].</translate>


=={{anchor|requirements}}Requirements==
{{note|<translate><!--T:21--> Before proceeding, you should validate that you can back up to SEP sesam. Run a test ''Path'' backup manually to ensure that the backups work. For details on typical backup configuration, see [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]].</translate>}}
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:
*Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#MySQL|support matrix]] for the list of supported MySQL/MariaDB versions.
*SEP sesam Server v. ≥ 4.4.3. Check [[Special:MyLanguage/Hardware_requirements|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]].
*[https://download.sep.de/ Download the SEP sesam Client package] on the MySQL database host (MySQL backup module is already included in the client package).
*A user account with sufficient privileges to perform backup and restore operations.
*SEP sesam MySQL backup module requires a license. For details, see [[Special:MyLanguage/List_of_Licenses|List of Licenses]].  


=={{anchor|add_client}}Adding the MySQL client to SEP sesam environment ==
=={{anchor|database_bck}}<translate><!--T:22-->
Once you have [https://download.sep.de/ downloaded the SEP sesam Client package], configure your MySQL client by adding it to the SEP sesam environment: '''Main selection''' -> '''Components''' -> '''Topology''' -> '''New client''' -> add your MySQL client. For details, see [[Special:MyLanguage/Configuring_Clients|Configuring Clients]].
Configuring MySQL database backup ==
{{note|Before proceeding, you should validate that you can backup to SEP sesam. Run a test ''Path'' backup manually to ensure that the backups work. For details on typical backup configuration, see [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]].}}


=={{anchor|database_bck}}Configuring MySQL database backup ==
<!--T:23-->
Create a new backup task to back up a single database or the complete MySQL database. Note that you have to create a separate backup task for each database to be able to restore a single database.</translate>


Create a new backup task to back up a single database or the complete MySQL database. Note that you have to create a separate backup task for each single database you want to back up to be able to restore a single database.
<ol><li><translate><!--T:24--> From '''Main Selection''' -> '''Tasks''' -> '''By Clients''', select the ''MySQL'' client and click '''New Backup Task'''. The ''New Backup Task'' window opens.</translate></li>
<li><translate><!--T:25--> Specify the '''Source'''. Click the '''Browse''' button (big arrow) and select either the individual database or all MySQL databases you want to back up. You can also enter the source manually, as follows:</translate>
<ul><li><translate><!--T:26--> ''<DB_name>'': Backup of a single database (e.g., ''my_db'').</translate> </li>
<li>{{anchor|create_database}}<translate><!--T:27-->
''DB:<DB_name>'':Backup of a single database (e.g., ''DB:my_db'').  


<ol><li>From '''Main Selection''' -> '''Tasks''' -> '''By clients''', select ''MySQL'' client and click '''New backup task'''. The ''New backup task'' window opens.</li>
<!--T:69-->
<li>Specify the '''Source'''. Click the '''Browse''' button (big arrow) and select either the single database or all MySQL databases you want to back up. You can also enter the source manually, as follows:
Similar to the above example except that in this case the ''CREATE DATABASE'' statement is inserted; this is required for restoring a single database to a different location.</translate></li>
<ul><li>''<DB_name>'':</li> Backup of a single database (e.g., ''my_db'').
<li><translate><!--T:28--> ''all'': Backup of all MySQL server databases.</translate></li></ul>
<li>''DB:<DB_name>'':</li>Backup of a single database (e.g., ''DB:my_db''). Similar as in the example above, but in this case the ''CREATE DATABASE'' statement will be inserted.
<translate><!--T:29--> Note that if you select the source by browsing, the ''task type'' and ''task name'' are set automatically. If you enter the source manually, you have to enter the ''task name'' and select '''MySQL''' as the ''task type''.</translate></li>  
<li>''all'':</li>Backup of all MySQL server databases.</li></ul>
<translate><!--T:30--> [[Image:MySQL_bck_task.jpg|700px|link=]]</translate>
Note that if you select the source by browsing, the ''task type'' and ''task name'' are set automatically. If you enter the source manually, you have to enter the ''task name'' and select '''MySQL''' as the ''task type''.</li>  
<br clear=all><br />
[[Image:MySQL_bck_task.png|link=]]
 
<br clear=all>
<li>{{anchor|access}}<translate><!--T:31--> Enter the credentials to access the MySQL database. On SEP sesam version ''5.1.0.14 Apollon V2'' or higher, switch to the '''MySQL''' tab and enter the username (account) and password to access the MySQL database.</translate><br />  
<li>Switch to the '''MySQL''' tab and enter the user name (account) and password to access the MySQL database.</li>  
<translate><!--T:32--> On SEP sesam version ''5.1.0.7 Apollon'' or lower, switch to the '''Options''' tab and enter additional parameters in the '''Backup options''' field, if needed.</translate></li>
<li>Optionally, switch to the '''Options''' tab and enter additional parameters in the '''Save options''' field, if required.</li>
<ul><li><translate><!--T:33--> Enter the username and password to access the database. Enter the username and password for accessing the database. It is recommended to set the same permissions for backup and restore. For restore, you can also set them later under the ''Expert options'' in the [[Special:MyLanguage/4_4_3_Beefalo:Activities#restore|restore wizard]].</translate></li>
<ul><li><span style="color:red">Enter the user name and password to access the database. It is recommended that you set the same privileges for the backup and the restore. For the restore you can also set them later under the ''Expert options'' in the [[Special:MyLanguage/Activities_4.4#restore|restore wizard]].</span></li>
<pre> -a user=<DB_user>,password=<DB_user_password></pre>
<span style="color:red">-a user=<DB_user>,password=<DB_user_password></span>
<li><translate><!--T:36--> You can also specify user privileges in the {{Path|/etc/my.cnf}} file on the client side. This is required for browsing for the database.</translate></li>
<li><span style="color:red">You can also specify user privileges in the {{Path|/etc/my.cnf}} on the client side. This is required for browsing for the database.</span></li>
<pre> root@mysql:~# cat /etc/my.cnf
<span style="color:red">root@mysql:~# cat /etc/my.cnf
  [client]
  [client]
  user=root
  user=root
  password=secret
  password=secret
  root@mysql:~#</span>
  root@mysql:~#</pre>
<li><span style="color:red">Alternatively, you can use the configuration files to store the password, e.g., {{Path|/etc/my.cnf}} or {{Path|%WINDIR%\my.cnf}}:</span></li>
<li><translate><!--T:37--> Alternatively, you can use the configuration files to store the password, e.g., {{Path|/etc/my.cnf}} or {{Path|%WINDIR%\my.cnf}}:</translate></li>
<span style="color:red">[client]
<pre> [client]
  user=root
  user=root
  password=secret</span>
  password=secret</pre>
<li><span style="color:red">You can also specify another configuration file to store the password by using the <tt>defaults-file</tt> variable:</span></li>
<li><translate><!--T:38--> You can also specify another configuration file to store the password by using the <tt>defaults-file</tt> variable:</translate></li>
<span style="color:red">-a defaults-file=/var/opt/sesam/var/ini/sm_mysql.cnf</span>
<pre> -a defaults-file=/var/opt/sesam/var/ini/sm_mysql.cnf</pre>
<li>Use this option for better throughput during the MySQL database backup of the ''ISAM'' database type; do not use this option for the ''InnoDB'' database type:</li>
<li><translate><!--T:39--> Use this option for better throughput when backing up the MySQL database of the ''ISAM'' database type; do not use this option for the ''InnoDB'' database type:</translate></li>
-a opt
<pre> -a opt</pre>
<li>Specify this option for the consistent backup of the ''InnoDB'' tables:
<li><translate><!--T:40--> Specify this option for consistent backups of ''InnoDB'' tables:</translate></li>
</li>
<pre> -a single-transaction</pre>
-a single-transaction
<translate><!--T:41--> This option is useful only with transactional tables such as InnoDB; it dumps the consistent state of the database at the time when START TRANSACTION was issued without blocking any applications. Keep in mind that only InnoDB tables are dumped in a consistent state, while any MyISAM or MEMORY tables dumped while using this option may still change state.</translate>
This option is useful only with transactional tables such as InnoDB; it dumps the consistent state of the database at the time when START TRANSACTION was issued without blocking any applications. Keep in mind that only InnoDB tables are dumped in a consistent state, while any MyISAM or MEMORY tables dumped while using this option may still change state.
<li><translate><!--T:42--> You can combine different parameters in one statement:</translate></li>
<li>You can combine different parameters into one statement:</li>
<pre> -a user=<DB_user>,password=<DB_user_password>,opt,single-transaction</pre>
-a user=<span style="color:red"><DB_user>,password=<DB_user_password>,</span>opt,single-transaction
{{note|
{{Note|
*<translate><!--T:46--> Specify the <tt>mysqldump</tt> parameter without a double hyphen. SEP sesam translates the given parameter into the correct format when calling the MySQL program.</translate>
*Specify the <tt>mysqldump</tt> parameter without any double hyphen. SEP sesam translates the given parameter into the correct format when calling the MySQL program.
*<translate><!--T:47--> The line after the <tt>-a</tt> specification must not contain spaces.</translate>}}
*The line behind the <tt>-a</tt> specification may not contain any spaces.}}
</ul>
</ul>
[[image:MySQL_bck_task_options.png|link=]]
<translate><!--T:48--> [[image:MySQL_bck_task_options.jpg|700px|link=]]</translate>
<br clear=all>
<br clear=all><br />
<li>Click '''OK''' to create the task.</li>
<li><translate><!--T:49--> Click '''OK''' to create the task.</translate></li>
<li>If you want to start the newly created task immediately, right-click the name of the task and click '''Immediate Start'''. If you want to create a periodic backup, you have to create a schedule for your backup task: Click '''New schedule''' under '''Main Selection''' -> '''Scheduling''' -> '''Schedules''' and set up a schedule. For more details, see [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]].</li>
<li><translate><!--T:50--> If you want to start the newly created task immediately, right-click the name of the task and click '''Immediate Start'''. If you want to create a periodic backup, you have to create a schedule for your backup task: Click '''New Schedule''' under '''Main Selection''' -> '''Scheduling''' -> '''Schedules''' and set up a schedule. For more details, see [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]].</translate></li>
{{tip| You can also add your backup task to an existing schedule by double-clicking the backup task, selecting the tab '''Schedules''' and adding it to one or more schedules. Additionally, you can group your backup tasks to task groups. For details, see [[Special:MyLanguage/Adding_a_Task_to_the_Task_Group|Adding a Task to the Task Group]].}}
{{tip|<translate><!--T:52--> You can also add your backup task to an existing schedule by double-clicking the backup task, selecting the tab '''Schedules''' and adding it to one or more schedules. Additionally, you can group your backup tasks to task groups. For details, see [[Special:MyLanguage/Adding_a_Task_to_the_Task_Group|Adding a Task to the Task Group]].</translate>}}
<li>Once you have configured a schedule, you must create a new backup event for it. For general information on creating a backup event, see [[Special:MyLanguage/Creating_a_Backup_Event|Creating a backup event]].</li>
<li><translate><!--T:53--> Once you have configured a schedule, you must create a new backup event for it. For general information on creating a backup event, see [[Special:MyLanguage/Creating_a_Backup_Event|Creating a Backup Event]].</translate></li>
</ol>
You can view the status of your backup jobs by selecting '''Last backup state''' in the ''Main Selection'' window. The backup status overview provides detailed information on the last run of backup jobs, including the task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.
</ol>
</ol>


=={{anchor|special_bck}}Configuring MySQL special features backup (stored routines and triggers) ==
==={{anchor|monitoring}}<translate><!--T:67-->
Monitoring backup===
 
<!--T:68-->
You can view the status of your backup jobs in the GUI (''Monitoring'' -> ''Last Backup State'' or ''Job State'' -> ''Backups'') or [[Special:MyLanguage/SEP_sesam_Web_UI|SEP sesam Web UI]]. The backup status overview provides detailed information about the last run of backup jobs, including task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.</translate>
 
=={{anchor|special_bck}}<translate><!--T:57-->
Configuring MySQL special features backup (stored procedures and triggers) ==  


By default, SEP sesam does not back up stored routines (procedures and functions) nor triggers from the dumped databases. However, it is possible to define that these are also backed up by using the '''Save options''' field in the backup task properties.
<!--T:58-->
<ol><li>Double-click on the already configured MySQL backup task in the '''Main Selection''' -> '''Tasks by Clients'''.</li>
By default, SEP sesam does not back up stored procedures nor triggers from dumped databases. However, you can specify that these are also backed up by using the '''Backup options''' field in the backup task properties.</translate>
<li>Specify the relevant parameter for backing up stored routines or triggers: click the '''Options''' tab and enter the following in the '''Save options''' field:</li>
<ol><li><translate><!--T:59--> Double-click the already configured MySQL backup task in the '''Main Selection''' -> '''Tasks''' -> '''By Clients'''.</translate></li>
<ul><li>To back up the stored routines:</li>
<li><translate><!--T:60--> Specify the relevant parameters for backing up stored routines or triggers: click the '''Options''' tab and enter the following in the '''Backup options'''field:</translate></li>
-a routines
<ul><li><translate><!--T:61--> To back up the stored procedures:</translate></li>
<li>To include the triggers:</li>
<pre> -a routines</pre>
-a triggers
<li><translate><!--T:62--> To enable triggers:</translate></li>
<li>To back up the stored routines and triggers at the same time:</li>
<pre> -a triggers</pre>
-a routines -a triggers
<li><translate><!--T:63--> To back up the stored procedures and triggers at the same time:</translate></li>
[[image:MySQL_bck_task_special.png|link=]]
<pre> -a routines -a triggers</pre>
<translate><!--T:64--> [[image:MySQL_bck_task_special.jpg|700px|link=]]</translate>
<br clear=all>
<br clear=all>
</ul></ol>
</ul></ol>


==Known issues==
<noinclude><div class="noprint">{{Copyright}}</div></noinclude>
If you have problems with MySQL backup, check the [[Special:MyLanguage/Troubleshooting_Guide#MySQL|Troubleshooting Guide]].
 
==See also==
[[Special:MyLanguage/4_4_3:MySQL_Restore|MySQL Restore]]

Latest revision as of 15:41, 15 March 2024

The procedures and functions described here represent only some of the recommendations and examples for MySQL database backup. The provided database backup options are not part of SEP sesam, but only some of the options that can be used for backup. Detailed information about MySQL backup policies and strategies can be found in MySQL Documentation.

The SEP sesam extension for MySQL and MariaDB is part of a client package and enables online backup of one or more MySQL databases. SEP sesam uses the mysqldump program to connect to the MySQL server and create the SQL dump file. The dump file produces a set of SQL statements required to re-create the database. For details on mysqldump program, see MySQL documentation mysqldump — A Database Backup Program.

Requirements

To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:

Installing and adding MySQL client to SEP sesam environment

Once you have downloaded and installed the SEP sesam Client package, configure your MySQL client by adding it to the SEP sesam environment: Main selection -> Components -> Clients -> New Client -> add your MySQL client. For details, see Quick Install Guide and Configuring Clients.

Information sign.png Note
Before proceeding, you should validate that you can back up to SEP sesam. Run a test Path backup manually to ensure that the backups work. For details on typical backup configuration, see Standard Backup Procedure.

Configuring MySQL database backup

Create a new backup task to back up a single database or the complete MySQL database. Note that you have to create a separate backup task for each database to be able to restore a single database.

  1. From Main Selection -> Tasks -> By Clients, select the MySQL client and click New Backup Task. The New Backup Task window opens.
  2. Specify the Source. Click the Browse button (big arrow) and select either the individual database or all MySQL databases you want to back up. You can also enter the source manually, as follows:
    • <DB_name>: Backup of a single database (e.g., my_db).
    • DB:<DB_name>:Backup of a single database (e.g., DB:my_db). Similar to the above example except that in this case the CREATE DATABASE statement is inserted; this is required for restoring a single database to a different location.
    • all: Backup of all MySQL server databases.
    Note that if you select the source by browsing, the task type and task name are set automatically. If you enter the source manually, you have to enter the task name and select MySQL as the task type.
  3. MySQL bck task.jpg

  4. Enter the credentials to access the MySQL database. On SEP sesam version 5.1.0.14 Apollon V2 or higher, switch to the MySQL tab and enter the username (account) and password to access the MySQL database.
    On SEP sesam version 5.1.0.7 Apollon or lower, switch to the Options tab and enter additional parameters in the Backup options field, if needed.
    • Enter the username and password to access the database. Enter the username and password for accessing the database. It is recommended to set the same permissions for backup and restore. For restore, you can also set them later under the Expert options in the restore wizard.
    •  -a user=<DB_user>,password=<DB_user_password>
    • You can also specify user privileges in the /etc/my.cnf file on the client side. This is required for browsing for the database.
    •  root@mysql:~# cat /etc/my.cnf
       [client]
       user=root
       password=secret
       root@mysql:~#
    • Alternatively, you can use the configuration files to store the password, e.g., /etc/my.cnf or %WINDIR%\my.cnf:
    •  [client]
       user=root
       password=secret
    • You can also specify another configuration file to store the password by using the defaults-file variable:
    •  -a defaults-file=/var/opt/sesam/var/ini/sm_mysql.cnf
    • Use this option for better throughput when backing up the MySQL database of the ISAM database type; do not use this option for the InnoDB database type:
    •  -a opt
    • Specify this option for consistent backups of InnoDB tables:
    •  -a single-transaction

      This option is useful only with transactional tables such as InnoDB; it dumps the consistent state of the database at the time when START TRANSACTION was issued without blocking any applications. Keep in mind that only InnoDB tables are dumped in a consistent state, while any MyISAM or MEMORY tables dumped while using this option may still change state.

    • You can combine different parameters in one statement:
    •  -a user=<DB_user>,password=<DB_user_password>,opt,single-transaction
      Information sign.png Note
      • Specify the mysqldump parameter without a double hyphen. SEP sesam translates the given parameter into the correct format when calling the MySQL program.
      • The line after the -a specification must not contain spaces.

    MySQL bck task options.jpg

  5. Click OK to create the task.
  6. If you want to start the newly created task immediately, right-click the name of the task and click Immediate Start. If you want to create a periodic backup, you have to create a schedule for your backup task: Click New Schedule under Main Selection -> Scheduling -> Schedules and set up a schedule. For more details, see Creating a Schedule.
  7. SEP Tip.png Tip
    You can also add your backup task to an existing schedule by double-clicking the backup task, selecting the tab Schedules and adding it to one or more schedules. Additionally, you can group your backup tasks to task groups. For details, see Adding a Task to the Task Group.
  8. Once you have configured a schedule, you must create a new backup event for it. For general information on creating a backup event, see Creating a Backup Event.

Monitoring backup

You can view the status of your backup jobs in the GUI (Monitoring -> Last Backup State or Job State -> Backups) or SEP sesam Web UI. The backup status overview provides detailed information about the last run of backup jobs, including task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.

Configuring MySQL special features backup (stored procedures and triggers)

By default, SEP sesam does not back up stored procedures nor triggers from dumped databases. However, you can specify that these are also backed up by using the Backup options field in the backup task properties.

  1. Double-click the already configured MySQL backup task in the Main Selection -> Tasks -> By Clients.
  2. Specify the relevant parameters for backing up stored routines or triggers: click the Options tab and enter the following in the Backup optionsfield:
    • To back up the stored procedures:
    •  -a routines
    • To enable triggers:
    •  -a triggers
    • To back up the stored procedures and triggers at the same time:
    •  -a routines -a triggers

      MySQL bck task special.jpg

Copyright © SEP AG 1999-2024. All rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.