Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

which client agents are licensed?

Created: 06 Feb 2013 • Updated: 17 Mar 2013 | 8 comments
ecnivnaj's picture
This issue has been solved. See solution.

Hi ALL,

How will i know if my client in backup exec is licensed and not trialed?

Thanks,

Vince

Comments 8 CommentsJump to latest comment

Backup_Exec's picture

Hi

Please check below link

http://www.symantec.com/docs/HOWTO11649

Also you can go to help -about -license information to know which agent and option is licensed or trialware

Also as you have not sepecified the BE version here ,Below link describes how agents and options are licensed in BE 2012

http://www.symantec.com/docs/TECH178479

Hope that helps

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

SOLUTION
ecnivnaj's picture

is there a way which client server/computer uses the license.

Sample Scenario:

i am backing up 2 clients with SQL server and i am using BE 2012. I have only installed the media server license. so i deployed agents on the two client servers, now both of them is in trial. Eventually i have acquired 1 license for Apps and DB and decided to installed it on the media server. can i specify which client will used the license and the other one remain as trial?

Thanks,

Vince

Backup_Exec's picture

Hi

First of all when you install BE 2012 only with Media server license & SQL license in trialware then with that you can backup SQL on any server there is no limitation for next 60 days

About you question now if you want to protect 2 SQL server on 2 different servers , then yes you would need 2 SQL licenses for it and if you only have got one then you would be able to only protect one SQL server and other server job will fail with license violation error. So would recommend you to purschase additional license for SQL as you can cannot keep the other server in trial.

I have also added licesne portflio PDF for more licensing information for BE 2012 in my first comment

Hope that helps

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

ecnivnaj's picture

if i have one license for the SQL can i select which client will use the license or not?

Backup_Exec's picture

Hi

 

You can decide that by only backing up one SQL server out of 2 ,so whichever you use to backup first would work fine the other backup would fail.

THanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

CraigV's picture

...is this new functionality built into BE now? From previous experience, a license key unlocked an application agent, and if you were unscrupulous as an end-user, and didn't want to pay extra licenses for other application servers, you would be able to install RAWS on x-number of servers and back them up with that 1 license.

The license # on your license agreement sheet would indicate how many you bought from Symantec, and were technically allowed to use...

So if not, and I don't think this IS new functionality in BE, then you are totally wrong. The OP would actually be able to backup both SQL servers with 1 license key and both would succeed! In which case you need to check and see how this works in a production environment before guessing...

Thanks!

Alternative ways to access Backup Exec Technical Support:

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

Backup_Exec's picture

Hi

With 1 single SQL licesne if you are backing up 2 SQL server then this would cause jobs to fails intermittently with licesne violation error ,so to be ethically licensed and for stability of your backup ensure you have 2 SQl licenses purchased if you will be backing up 2 SQL server.

 

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

pkh's picture

If you have only one SQL licence and is only backing up one of the servers, it is a good practice to uninstall the remote agent from the other SQL server.  This will clearly show to anybody concerned that you are not using the SQL licence on the second SQL server.