?
Solved

Symantec BackupExec 11D - Database In Use

Posted on 2007-11-20
19
Medium Priority
?
2,068 Views
Last Modified: 2013-12-01
i have just switched to BackupExec 11D from 10.0. In 10.0 all SQL2000 databases backed up fine without error.

In 11D i get the following:

The item server\BEDB in use - skipped.

What am i missing?
0
Comment
Question by:Avatar261
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 8
  • 3
  • 2
  • +3
19 Comments
 
LVL 12

Expert Comment

by:David Scott, MCSE
ID: 20319868
i take it you are using sql agent to backup the sql db?  i am posting some links

http://seer.support.veritas.com/docs/275277.htm

https://forums.symantec.com/syment/board/message?board.id=115&message.id=8270

0
 
LVL 9

Expert Comment

by:cooledit
ID: 20326066
hi, there

if you got 2 min to test it out i would suggest to take out the license key and then try the jobs again.
That will basically bring BE11d back to trial version and under the trialversion all agents are available so then you know if this works you have a problem on the agent side missing licenses.

Cooledit
0
 
LVL 2

Author Comment

by:Avatar261
ID: 20327047
I detached the BEDB database after stopping the backupexec services, reatched it correctly with no double slashes then started the services.

I then checked the database file path and it has put double slashes back in!

Any ideas?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 12

Expert Comment

by:David Scott, MCSE
ID: 20327311
Ok, i have this same issue with one of my sql databases.  There is no fix that i am aware (at least last time i checked with Symantec).  So what i do is setup a backup job in enterprise manager and then use symantec to backup the database backups.  
0
 

Expert Comment

by:atkinsonit
ID: 20428142
I have the same issue with SQL 2005 and BE 11d rev.7170  I've upgraded the BE SQL agents, in my logs I do not have double backslashes, only server\dabasename  Here's the log:

V-79-57344-33938 -
An error occurred on a query to database DBname.
V-79-57344-33938 - Write on "DBname_00__4c315e2e_2575_4f31_acaa_766253fa7cd6_" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
The item server\DBname in use - skipped.

How can there NOT be a resolution.  Whats the point of the SQL agent if it don't work! Thanks Symantec!
0
 
LVL 2

Author Comment

by:Avatar261
ID: 20428170
i actually raised a ticket with Symantec and they could not fix the issues.

He said to me something about it NOT needing to be backed up anyway as it is done as part of its daily course.

hmm, i am not sure.
0
 
LVL 12

Accepted Solution

by:
David Scott, MCSE earned 1000 total points
ID: 20428180
that sounds like a different issue.  we're talking about backup exec not being able to back it up b/c it has double backslashes.  
0
 
LVL 2

Author Comment

by:Avatar261
ID: 20428202
no, it is the same issue.

as i just said. There own support could not figure out why it kept putting in the extra slashes and then gave me the above response.
0
 
LVL 12

Expert Comment

by:David Scott, MCSE
ID: 20428209
check in enterprise manager and see if a task is setup to backup the dbs.  

if so then just include the backup files in your backup

if not set a task to backup the db, then backup the backup
0
 
LVL 12

Expert Comment

by:David Scott, MCSE
ID: 20428222
i'm refering to atkinson IT--regarding his errors
0
 

Assisted Solution

by:atkinsonit
atkinsonit earned 1000 total points
ID: 20441879
We do this as well, all of our dbs backup to .bak files then we back those up.  but the point of the SQL agent then becomes what?  Did we all purchase this and get ripped off because it can no longer backup online database files?  I do not have backslashes in my paths, yet I go thru the same runaround with them.

So we have to rely on a MSSQL backup job that can and will fail, then your nightly backup will be of no use.  To me this kind of "solution" is unacceptable.  Basically they should just say, our Agent won't work so here's a coupon to switch to our competitors software.  haha!

Does anyone else think this is unacceptable?  Has there been mention of any future real resolution?
0
 
LVL 12

Expert Comment

by:David Scott, MCSE
ID: 20442176
yes, i think its unacceptable. Symantec says it an issue with MS and they shouldn't have \\.  

I use the agent for other sql dbs and it works fine.  the db that i have a problem with isn't as important as the ones that work.  plus the most important db i backup, the vendor only supports backup exec so my hands are kind of tied.  
0
 

Expert Comment

by:xxxomxxx
ID: 20569186
Capslockassasin found the solution to be a registry change on the Symantec Backup Exec server.  In the registry key HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase look for the values Server Database Path and Server Database Log Path.  If these values have trailing backslashes like so:

Server Database Path=E:\Microsoft SQL Server\MSSQL\Data\
Server Database Log Path=D:\Microsoft SQL Server\MSSQL\Data\

then remove them so that they appear like this instead:

Server Database Path=E:\Microsoft SQL Server\MSSQL\Data
Server Database Log Path=D:\Microsoft SQL Server\MSSQL\Data

You should now find that the documented solution from Symantec works properly.

0
 
LVL 12

Expert Comment

by:David Scott, MCSE
ID: 20618443
I am not finding those values on the backup exec server under that key.

on the sql server i am trying to backup, i am not even finding that key (perhaps b/c it is sql 2000?)

0
 

Expert Comment

by:xxxomxxx
ID: 20622989
i am using SQL 2000 Ent on W2k3Ent and the key change solved my problem, dunno why you cant find it...very strange. Did you search the registry?
0
 

Expert Comment

by:hpesoj
ID: 20662839
I am having the same issue, way too many databases are skipped.  And just like opie6373 those registry keys do not exist on my Backup Exec Server.  I do agree with others here, the whole point of purchasing the SQL agent is to give you the ability to do hot backups or backup while the database is live.  If you have to resort to backing up databases from the SQL server to .bak files and then back those up as regular files, then the SQL agent is pretty much useless.  You can do the same thing without the SQL agent.  Also, if a work around is to do a pre and post exec scripts to bring the databases up or down, make the SQL Agent useless.  This SQL Agent is worthless, no wonder so many people shy away from it.  You're better off using the backup tools Microsoft provides with SQL to do hot backups and just have Backup Exec backup those backups.  We're at the point where we just want our $$ back.
0
 
LVL 12

Expert Comment

by:David Scott, MCSE
ID: 20664645
Yeah, Symantec blames it on microsoft.  I'm just glad its not a mission critical database.  
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Workplace bullying has increased with the use of email and social media. Retain evidence of this with email archiving to protect your employees.
Microsoft will be releasing the Windows 10 Creators Update in just a matter of weeks. Are you prepared? Follow these steps to ensure everything goes smoothly and you don't lose valuable data on your PC.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

718 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question