01-20-2012 10:42 AM
After upgrading NetBackup or OpsCenter to 7.1.0.3, the database server process dbsrv11.exe, will be licensed / limited to use only one processor. This can cause the dbsrv11.exe process to use 100% of the CPU.
To determine that the system is affected by the issue, review the server.log file, which can be found in:
NetBackup: <install_path>\Veritas\NetBackupDB\log
OpsCenter: <install_path>\Symantec\OpsCenter\db\log
I. 12/29 20:31:55. 8 logical processor(s) on 2 physical processor(s) detected.
I. 12/29 20:31:55. Processor limit (licensed processors): 1
I. 12/29 20:31:55. Maximum number of physical processors the server will use: 1
Another option to check if the system is affected is to execute the dblic.exe command. This command can be found in the following paths:
NetBackup: <install_path>\Veritas\NetBackupDB\WIN64
OpsCenter: <install_path>\Symantec\OpsCenter\server\db\WIN64
Note: On a 32 bit system, replace "WIN64" in the paths above with "WIN32"
From the command prompt:
> dblic.exe dbsrv11.lic
The output on an affected system would look similar to this example output from a NetBackup 7.1.0.3 server:
SQL Anywhere Server Licensing Utility Version 11.0.1.2645
License read successfully.
Licensed processors: 1
User: Symantec
Company: Symantec Inc.
Install key: PEPEMJ98AABP7150593091370
This issue affects only Windows environments on NetBackup 7.1.0.3.
Symantec Corporation has acknowledged that the above-mentioned issue (Etrack 2659663) is present in the current version(s) of the product(s) mentioned in this article. Symantec is committed to product quality and satisfied customers. This issue is scheduled to be addressed in the following version of NetBackup:
When NetBackup 7.1.0.4 is available, please access the following link for download and readme information:
http://www.symantec.com/business/support/index?page=landing&key=15143
Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Workaround:
In a command prompt, browse to the directory containing the dblic.exe command:
NetBackup: <install_path>\VERITAS\NetBackupDB\WIN64
OpsCenter: <install_path>\Symantec\OpsCenter\server\db\WIN64
Note: If on a 32 bit system, replace "WIN64" with "WIN32"
Execute the following command for NetBackup:
> dblic.exe -l Processor -u 128 dbsrv11.lic "Symantec" "Symantec Inc."
For OpsCenter, execute this command:
> dblic.exe -l Processor -u 100 dbsrv11.lic "Symantec OpsCenter" "Symantec Corporation"
This would increase the number of Licensed Processor Count to 100 for OpsCenter and 128 for NetBackup. (These are the default values.)
Services will have to be recycled for the change to take effect.
Validate this solution by rerunning the dblic.exe dbsrv11.lic
command and observing changes in the output.
|
Source | ETrack |
Value | 2659663 |
Description |
After OpsCenter 7.1.0.3 upgrade: Processor limit (licensed processors): 1 |