Using NetBackup for SQL Server Using batch files
Moving a database that contains full-text catalogs
NetBackup for Microsoft SQL Server extends the move template when a database contains a full-text catalog by including the following text:
Replace the full text catalog directory path
<C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\HisCatalog>
with a new directory path. Also remove the hash mark <#> which precedes the keyword
MOVE #TO #
"sysft_HisCatalog" "C:\Program Files\Microsoft
Modify the target directory path in the template. The name sysft_HisCatalog is the logical name of the file that contains the full-text directory named HisCatalog. NetBackup creates this name by prepending the catalog name with "sysft_".
Using batch files
NetBackup for SQL Server uses scripts called batch files for initiating backup and restore operations. A batch file uses the .bch extension and is typically executed from the install_path\DbExt\MsSql\ directory. Refer to the Appendix “Sample batch files” on page 181 for example batch files.
Overview of batch files
You will have to create a batch file if you start up operations with:
the Manage Scripts dialog box in NetBackup for SQL Server
the dbbackex command line
the NetBackup scheduler
You can easily create a fully functional batch file by selecting the Save option in the backup or restore dialog box and then clicking OK. The following sections, however, provide guidelines to help you to understand the contents of a batch file and how to modify or create one on your own.
Text format used in batch files
Batch files created by the SQL Server Agent interface are Unicode text. This permits inclusion of object names and image names that include non-English characters. If you create a batch file manually, use notepad or some other tool that generates plain text. If your batch file contains any non-English characters save it as Unicode.