MS-SQL database backup fails with status 1 when 'SQLINSTANCE $ALL' is used in the batch file and the database instances belong to different versions of MS-SQL server.
|Article:TECH189674|||||Created: 2012-05-24|||||Updated: 2013-10-25|||||Article URL http://www.symantec.com/docs/TECH189674|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
MS-SQL server version 2000 and 2005 uses diffferent syntax to query the databases.
5/8/2012 10:34:12 AM - Info dbclient(pid=6592) DBMS MSG - ODBC return code <-1>, SQL State <S0002>, SQL Message <208><[Microsoft][SQL Native Client][SQL Server]Invalid object name 'master.sys.database_files'.>
NetBackup MS-SQL Database Agent
MS-SQL server version 2000 and 2005 uses diffferent syntax to query the databases. So, putting 'SQLINSTANCE $ALL' in the batch file used in the policy to backup databases belonging to different versions of MS-SQL servers causes this problem.
Any of the followings work for the above situation:
1. Use three different batch files to avoid 'SQLINSTANCE $ALL' and to use the instance names against each 'SQLINSTANCE' card.
2. Use two NetBackup policies, one to use a batch file with 'SQLINSTANCE $ALL' to backup MS-SQL 2005 server as the client, the other to backup MS-SQL 2000 server as the client.
Article URL http://www.symantec.com/docs/TECH189674