Forum Discussion

Tim_Bizz's avatar
Tim_Bizz
Level 4
15 years ago
Solved

Backup Exec 2010

I have SQL 2000 SP4 on a Windows 2003 R2 64 bit Server

I am able to get the remote agent installed and it backups all other selections but the SQL Databases.  Error in the logs is

Database \DatabaseName was not found, or could not be accessed.
The item cgy-pipe-sql4.CAN.BJS\Databasename in use - skipped.

I do not understand why it keeps doing this.  I can see the Database in my Backup Server
and when I run the Backup I see it doing the DBCC check on the Databases with no issues.
2010
Agent for Microsoft SQL Server
Backup and Recovery
Backup Exec
Remote Agent for Windows Servers
  • Tim_Bizz's avatar
    Tim_Bizz
    15 years ago

    Found the Solution,

     

    I was checking up on an error in the log and it led me to another Forum posting in which they gave http://support.microsoft.com/?kbid=913100 as the solution.  Applied this patch and sure enough all is well again.  Thanks for all your help

  • Striker_303's avatar
    Striker_303
    Level 6
    15 years ago

    Please add backup exec account in the SQL with right of DBA creator, Sysadmin and server admin.

    Also check Event viewer on target sql server if this fails.

  • Ken_Putnam's avatar
    Ken_Putnam
    Level 6
    15 years ago

    This is from the flat file portion of your backup, right?  If so, since the SQL is running, BackupExec cannot access the mdf and ldf files.  All databases should be backed up using the appropriate Agent.

    I'm a little surprised that you even got the "in use - skipped" error.  Since v9, backup Exec has used AFE (Active File Exclusion) to skip files with known database extentions - normally with no error in the job log

  • Striker_303's avatar
    Striker_303
    Level 6
    15 years ago

    https://www-secure.symantec.com/connect/forums/sql-2000-backups-backupexec-10d-skipping-database-files

  • Tim_Bizz's avatar
    Tim_Bizz
    Level 4
    15 years ago

    Sorry for the late reply.

     

    BuiltIn Administrators have System Administrators, Database Creators, Server Administrators access within SQL Server.  From Backup Exec I have our ServiceAcct connecting to the SQL Server which has Domain admin access (apart of the Builtin Administrators group)

     

    We use a SQL agent for the Databases and then I have Deattached SQL Databases as well so I do a flat file backup of those with no AOFO.  The SQL Databases are what is being skipped but my flat file backup there is no issue at this time.  I use a backup Server which uses a remote agent/SQL Agent to connect to my SQL server to do the backup.

  • Tim_Bizz's avatar
    Tim_Bizz
    Level 4
    15 years ago

    I followed the link and tested the ALL SQL backup job and all SQL DB's were skipped.  Usually I do not create seperate jobs for both SQL and Flat File more or less because it had never caused an issue before.

  • Tim_Bizz's avatar
    Tim_Bizz
    Level 4
    15 years ago

    So here is the DBCC check for 1 of the Databases

    8957 :
    DBCC CHECKDB (DatabaseName) executed by CAN\serviceacct found 0 errors and repaired 0 errors.  Elapsed time: 0 hours 0 minutes 0 seconds.

    Is there any other Logs I can gather?  From the Backup Server I can Create/Delete, Update/Alter SQL databases with the Backup Exec Serviceacct.

  • Ken_Putnam's avatar
    Ken_Putnam
    Level 6
    15 years ago

    Is there any other Logs I can gather?  From the Backup Server I can Create/Delete, Update/Alter SQL databases with the Backup Exec Serviceacct.

    Again -

    Is this in the flat-file portion of the backup, or in the Agent portion?   it is the flat-file portion, correct?  As long as the SQLServer service is running you CANNOT backup SQL files as flat files

    If you are using the SQL Agent you will not get this, because the Agent is designed to backup an inuse database

  • Tim_Bizz's avatar
    Tim_Bizz
    Level 4
    15 years ago

    Again -

    We use a SQL agent for the Databases and then I have Detached SQL Databases as well so I do a flat file backup of those with no AOFO.  The SQL Databases are what is being skipped but my flat file backup there is no issue at this time.  I use a backup Server which uses a remote agent/SQL Agent to connect to my SQL server to do the backup.

    AS WELL

    I followed the link and tested the ALL SQL backup job and all SQL DB's were skipped.  Usually I do not create seperate jobs for both SQL and Flat File because it had never caused an issue before.

     

    So in summary I have tried the SQL agent route by only doing SQL Databases and it still comes up with Skipped Database issues.

     

     

     

  • Tim_Bizz's avatar
    Tim_Bizz
    Level 4
    15 years ago

    Is there any way of logging a Remote agent and maybe therefore Troubleshoot the issue a little more?