Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Question on SQL licensing and jobs

Created: 16 Jul 2013 | 9 comments

Hi guys,

Quick question regarding SQL licensing.

We have recently added a second drive to our media server in light of jobs taking to long to complete. The idea is to backup non critical data to this second drive and keep it onsite.

Part of this was to split our SQL instance over the two tapes, so the test databases are kept on site.

Every so often though the main database backup is failing with the error;

"before you can backup this resource you must purchase and install a license key for the appropriate backup exec agent".

But it's not every day and I can't work out any sort of pattern.

What I need to know is, does the license for the SQL server only work for one job at a time? My understanding is that we are licensed for one SQL instance, so it shouldn't matter how many jobs we split this over, we are only backing up the one instance?

Thanks in advance,

Jason

Operating Systems:

Comments 9 CommentsJump to latest comment

CraigV's picture

Hi Jason,

The license is on a per-server basis. It doesn't care how the DBs are split on the 1 server. If you've selected another server with an SQL installation, then you might get this issue.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

JasonRUK's picture

Hi Craig,

Thanks for the speedy reply.

Have you any idea why we may be intermittently getting this license error then? It failed today and Friday for example, but not on Tuesday, Wednesday or Thursday last week?

We've only been getting the issue since adding the 2nd drive and setting up this second set of jobs, it's run fine for years previously.

Cheers,

Jason

CraigV's picture

...you shouldn't. I've backed up multiple SQL servers with 1 SQL license added to a media server (we did own the correct # of SQL agent licenses) and never got this issue.

Have you tried to repair the BEDB using BEutility.exe? Might be a bit of corruption in the BEDB causing this.

The error you're getting is addressed in the TNs below, but I don't think any of them relate to your issue:

http://www.symantec.com/business/support/index?pag...

http://www.symantec.com/business/support/index?pag...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

mustansir's picture

Are u backing up data to tapes is it robotic library to which u have added a new tape drive ..than u would need a library expansion option license for the same....try uninstalling all the liceses including backup exec base license and than repair install and then re install all the licenses and check...

pkh's picture

If he does have a second tape drive and does not have an additional LEO licence, the second tape drive will not operate.  The error message has nothing to do with tape drives.

mustansir's picture

Jason please upload job log on forum lets go through it once and see what we can find....@ pkh please dont be so sure abt the error I have seen in many cases second tape drive working with leo error...as far as error is concerned it will be determined only after looking at the job log...

mustansir's picture

Jason please upload job log on forum lets go through it once and see what we can find....@ pkh please dont be so sure abt the error I have seen in many cases second tape drive working with leo error...as far as error is concerned it will be determined only after looking at the job log...

CraigV's picture

...are you a Symantec employee?

Thanks!

EDIT: and please don't post the same question over and over again...rather PM the OP instead.

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

JasonRUK's picture

Hi guys,

Thanks for the replies.

It isn't a robotic tape drive, just a second stand alone tape drive.

I've not had the error since the 16th of July now so that's 2 weeks without the error, I'm going to leave it for the time being, we are only backing up one SQL server and when it has failed it's always on the new selection list, the non-critical data, so not the end of the world.

If it crops up again I will post the job log for further analysis.

Thanks guys,

Jason