sts_delete_image failed: error 2060046 and 2060013

Article:TECH143958  |  Created: 2010-11-11  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH143958
Article Type
Technical Solution


Environment

Issue



During the image cleanup process it maybe seen that multiple media servers with credentials to the same storage server may attempt to run the nbdelete process on those volumes.


Error



In Activity monitor there will be multiple image cleanup jobs running.  In these jobs you may see the ts_delete_image failed: error 2060046 and 2060013 in the details status of different jobs.  Please note in this jobs what storage volumes are being cleaned up in the operation to verify if this is the problem that is occurring.


Environment



Multiple Media server that have been setup and configured to perform backups to a storage server and disk volumes.  This environment will be utilizing the OpenStorage Technology (OST) feature of Netbackup.


Solution




Solution:

Bug: 2177640

Detail/Symptom(s):
Multiple Media server can potentially attempt to initiate image clean jobs against the same disk volumes.


Log Files:

The bpdm logs will show that the nbdelete process has started a cleanup on the same disk volumes during the same times between multiple media servers.

From Media Server A bpdm log date 090810:
03:07:26.549 [3158] <2> bpdm: INITIATING (VERBOSE = 0): -volume_cleanup -mst 6
-p @aaaac -jobid 8925119 -mediasvr Media Server A
03:07:29.071 [3158] <2> parse_resource_strings: DISKVOLUME 0 6 @aaaac 13
dd01-lsu-1 0
20:08:53.384 [3158] <2> bpdm: EXITING with status 0

 

From Media Server B bpdm log date 090810:
14:51:37.711 [27952] <2> bpdm: INITIATING (VERBOSE = 0): -volume_cleanup -mst 6
-p @aaaac -jobid 8936758 -mediasvr Media Server B
14:51:39.916 [27952] <2> parse_resource_strings: DISKVOLUME 0 6 @aaaac 13
dd01-lsu-1 0
The process continues on to the next day from the bpdm log dated 090910:
01:05:16.252 [27952] <2> bpdm: EXITING with status 0

 


Workarounds:
Contact Symantec Technical support to obtain the binary files associated to the mentioned etrack.

ETA of Fix:
Symantec has acknowledged that the above-mentioned issue (Etrack 2177640) is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers.

Symantec currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. A link to the patch or hotfix download will be added to this document when it becomes available. Please note that Symantec reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. 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.




Article URL http://www.symantec.com/docs/TECH143958


Terms of use for this information are found in Legal Notices