Quantcast
Channel: Symantec Connect - Backup and Recovery - 讨论
Viewing all articles
Browse latest Browse all 5766

Symantec NetBackup of SQL Databases

$
0
0
我需要解决方案

Hi,  I need some community advice!

Running Symantec Netbackup 7.5.0.5 on Windows Server 2008R2

SQL Server is 2008 on Windows Server 2008R2

ALL Netbackup Policies work perfectly

 

Have been doing manual backups of the SQL Databases, which has worked grewat, but they are still on that system.  Would like to incorporate the feature from NetBackup to back them up to my regular storage devices.

 

Long story - short.

 

Created the Storage Unit   -   then the policy.   NetBackup already backs up the SQL Server full and differentials with no problem.\

In the attributes of the policy I called SQLDatabases,  I chose the SQLServer as my client  and in the backup selections tab, I chose the batch (.bch) file that lists each one of the 34 databases.

I assumed that Netbackup would just pick the first database and walk the dog,  going through ALL of thewm as it wrote.  Not so easy, I found.

 

The job fails every time.  Even ran the Netbackup MS SQL CLient which only connects to Virtual SQL 05 when run from the NetBackup Master Server.

If I run it from the SQL Server, it automatically picks up the SQL10 databases.   Makes no sense.

 

The .bch file SQLDatabases looks like this:

 

OPERATION BACKUP

DATABASE "BREEZE"

NBSERVER "GORDSNBMASTER.GORDBCBL.US.MIL"

MAXTRANSFERSIZE 6

BLOCKSIZE 7

NUMBUFS 2

ENDOPER TRUE

 

Then it looks identical for 33 other clients.   The administrators guide doesn't clarify these last 3 of 4 settings for max transfer size, blocksize or numbufs, so I changed the above to the defaults of 0,1 and 1 respectively.

 

What other information do you need to get some ideas of how to help me fix this!

 

It does not read the SQL10 databases and ends with errors everywhere.

 

Any help is much appreciated.


Viewing all articles
Browse latest Browse all 5766

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>