cancel
Showing results for 
Search instead for 
Did you mean: 

Backing up Mysql on Version 9.1

Andrewg
Level 3
 I'm new to veritas and mysql.  I know in arcserve you have to have the sql agent installed to backup a full sql database.  I have selected the data folder to be backed up but noticed that none of the .mdb files are getting backed up.  I'm assuming this is because the mysql service is started and the files are showing as being shared.  Is there an easy way to get around this without having to purchase the sql agent?  

Thanks

Andrew
1 ACCEPTED SOLUTION

Accepted Solutions

lyon
Level 5
You have a couple option:

First the Veritas SQL agent will not backup MySQL.

If you want to back the files up directly you must make the following registry change on the Backup Exec server:
http://seer.support.veritas.com/docs/259152.htm

Once you make this change you should be able to backup the files but if the MYsql is running Im sure you will see them skipped in the job log.
You can create batch files to stop/start the mysql and place the batch files in the pre/post command in the Backup Job setup. Then it may grab them. Otherwise you will still need to make the registry change above and purchase the AOFO option.
http://support.veritas.com/docs/263784

Or, you can cause MySQL to create it's own backups, then use BE to copy them to archive. I do this with MSSQL and Oracle, works great for our situation

Lyon


View solution in original post

3 REPLIES 3

CraigV
Moderator
Moderator
Partner    VIP    Accredited
Hi Andrew,

You didn't say which version of BEWS you are using, but BEWS 12.5 ships with Advanced Open File Agent as free.
If you're using that version, go through the Licensing Wizard, and select it. Once done, make sure AOFO is selected for your job and run it again.

Laters!

Hemant_Jain
Level 6
Employee Accredited Certified

Please note that mysql is not supported as an application agent to backup the database. But, file level backup can be done by using Advanced Open File Option. SQL Agent will not support mysql backup.

Please mark it a solution, if this is useful.
Thanks

lyon
Level 5
You have a couple option:

First the Veritas SQL agent will not backup MySQL.

If you want to back the files up directly you must make the following registry change on the Backup Exec server:
http://seer.support.veritas.com/docs/259152.htm

Once you make this change you should be able to backup the files but if the MYsql is running Im sure you will see them skipped in the job log.
You can create batch files to stop/start the mysql and place the batch files in the pre/post command in the Backup Job setup. Then it may grab them. Otherwise you will still need to make the registry change above and purchase the AOFO option.
http://support.veritas.com/docs/263784

Or, you can cause MySQL to create it's own backups, then use BE to copy them to archive. I do this with MSSQL and Oracle, works great for our situation

Lyon