1st, there are two ways to restore MySQL data, but depend on the backup 
method employed.
1 - back up the database files themselves while the database
   is quiescent (not in use or shutdown).
2 - use the mysqldump command to dump the database to
   a set of files that you then back up.

I have not heard of an agent for NBU for Mysql. If there is one someone 
else many have better knowledge of that, but in short it would operate 
basically the same as the mysqldump backup and mysqlimport restore. That 
would mean that your data is just stored as a long string of sql 
statements that can be replayed back into a database.

We use both methods, depending on client needs and whether the database 
can be shut down for the backup. With method number 1 you just need to 
put the data files back and point your instance of mysql at the database 
files. 2 is simple enough and does not require the database to be shut 
down.

As for what tapes are needed for a restore. ... In the GUI there is a 
button to show what tapes will be needed in the Restore section.

You can also use the command line
'bpimagelist -media -client <client> -d <date> -e <date>' to get the same.

HTH

Cheers!

--Chris

>Hello.
>
>Running NBU 5.0.  Have some wintel clients with SQL agent installed.
>
>Is is true that the SQL restore using the agent can only be done client
>side and not form the NBU master console?
>
>Also the issue I ran into, was that the DBA performing the restore had
>to run restore jobs and then kill them off to give the tape number
>needed for the restore. I then have to retrived said tapes from off
>site.
>
>Is there a better way using the native NBU master gui to perform this
>function or do SQL installs require them to be done from the master
>client.
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>  
>