Backup of SQL 2K with Backup Exec 8.6 SQL agent

Backup of SQL 2K with Backup Exec 8.6 SQL agent

Post by Mikael Jense » Sat, 09 Mar 2002 17:00:04



HEELP...
It keeps failing on my model db
<c/p from log file>
An error occurred on a query to filegroup model..PRIMARY.
^ ^ ^ ^ ^
Could not find filegroup 'PRIMARY' in sysfilegroups for database 'model'.
^ ^ ^ ^ ^
Unable to open the item model?PRIMARY - skipped.
</ c/p from log file>

Backup mode is set on full... PLEASE HELP

--

Take a guess :-)

 
 
 

Backup of SQL 2K with Backup Exec 8.6 SQL agent

Post by Eezy » Sat, 09 Mar 2002 19:22:26


I have the same scenario as yours.  I then decided to log
calls to both manufaturers and here is a workaround:

BackupExec: Select the databases only and not the
sysfilegroups especially for the model and msdb.  They are
aware of the problem and this is why they advise uses to
go about it.

Microsoft:  Explained to me the usage of the msdb and
model and why they should be backed up.  Could not comment
on the behaviour in BackupExe but suggested I use SQL
server to run another backup, just in case.  And make sure
that you backup to the tape, the backup from SQL.  I hope
this helps, and I have decided to go this way and save
myself time.

>-----Original Message-----
>HEELP...
>It keeps failing on my model db
><c/p from log file>
>An error occurred on a query to filegroup model..PRIMARY.
>^ ^ ^ ^ ^
>Could not find filegroup 'PRIMARY' in sysfilegroups for
database 'model'.
>^ ^ ^ ^ ^
>Unable to open the item model?PRIMARY - skipped.
></ c/p from log file>

>Backup mode is set on full... PLEASE HELP

>--

>Take a guess :-)

>.


 
 
 

1. Veritas Backup Exec w/SQL agent vs SQL 7 SP4

I am (and have been successfully for 1+ year) using
Veritas Backup Exec 8.6 with SQL 2000 Agent against 4 SQL
7.0 Servers on my Network.  All running SP4.  Recently all
the SQL Agent backups have failed.  When attempting a
manual backup via BE 8.6 I receive an error popup the
instant I click on the SQL DB icon in in the server
selection that reads:

"A communications failure has occurred."

In the Event Log I get this error each time the SQL Agent
backup fails:

"An error occurred while attempting to log in to the
following server: "SERVERNAME".
 OS error message: "".
 DBLIB error message: "Db-library network communications
layer not loaded.".
 Server error message: "".

HFNETCHK is run in a batch file each night against a list
of our 50 servers.  Each server has the patches installed
regularly to keep up to date with HFNETCHK.  I believe
that this is a problem from a recent patch as nothing has
changed with EITHER of my 2 backup servers (2 data centers
in 2 cities, neither can backup either cities SQL 7 server
via the BE SQL Agent but BOTH CAN backup the SQL 2000
servers) The SQL 2000 servers are pretty new and installed
by a consultant that did not install our standard security
patches, registry edits, and does not get the hfnetchk
treatment daily.

Any clues?

Possible problem:  recently installed SQL 7 SP 4 on (might
be wrong but I'm pretty sure) all of these boxes and
HFNETCHK says it is not up to date, "Service pack
installed is SQL 7 Gold.  The latest service pack is SQL 7
SP 4" or something to that effect on each server in
question.  I reapplied SP4 to one of the machines, checked
HFNETCHK again and it says the same thing still.

Thanks in advance.

Robb

It does not occurr with 2 SQL 2000 servers

2. Run filemaker script on sql server data?

3. Backup of database tables through Seagate Backup Exec 7.2 SQLserver agent

4. SQL Server Driver for JDBC

5. Why use Veritas Backup Exec for SQL 2k?

6. How to continue parsing a delimited text file after an error is encountered?

7. Backup Exec SQL Agent

8. 7X24 DBA's with Fragmentation Problems and Uptime Restrictions..

9. Backup Exec SQL agent

10. Seagate Backup Exec Agent for MS SQL Server

11. Veritas - Backup Exec - Agent for MS SQL Server????

12. Veritas Backup Exec SQL Agent

13. Restoring SQL Database from Backup Exec w/agent installed