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

Image Cleanup Status 174

Created: 06 Feb 2013 | 6 comments

**** Moved to new discussion from https://www-secure.symantec.com/connect/forums/image-cleanup-status-174 ****

Netbackup Master RHEL v7.1.0.4   Media Servers Windows 2008 R2 v7.1.0.4   client Win 2003 Sharepoint NB v7.1.0.4   Storage is Basic Disk, SAN attached to the Media Server dedicated to Sharepoint Farm GRT backups.

Help.  I'm also getting Status 174 but I think a little different.  Here is the whole Details from Activity Monitor:

02/06/2013 10:17:17 - Info nbdelete (pid=30253) deleting expired images. Media Server: utlp5179.ad.ama-assn.org Media: E:\BACKUP-SP
02/06/2013 10:17:17 - Info bpdm (pid=10892) started
02/06/2013 10:17:17 - started process bpdm (pid=10892)
02/06/2013 10:17:19 - Info bpdm (pid=10892) initial volume E:\BACKUP-SP: Kbytes total capacity: 1073737724, used space: 594400448, free space: 479337276
02/06/2013 10:17:19 - Critical bpdm (pid=10892) sts_delete_image of image appp5031_1360165313_C1_F4 failed: error 2060037 access not allowed
02/06/2013 10:17:19 - Critical bpdm (pid=10892) image delete failed: error 2060037: access not allowed
02/06/2013 10:17:20 - Info bpdm (pid=10892) ending volume E:\BACKUP-SP: Kbytes total capacity: 1073737724, used space: 594400448, free space: 479337276
media manager - system error occurred  (174)

I got all excited reading this post and finding the image name in Details.  I get one of these messages per day.  I went to the Media Server looking for the "access not allowed" image and none of them are there anywhere, from any day.  So it would seem they are getting cleaned but how and by what if the cleaning fails on the image and why then am I getting status 174 and access not allowed when the job gets done.

Comments 6 CommentsJump to latest comment

Marianne's picture

All I can suggest at this point in time is to ensure that bpdm and admin log folders exist on media server.
These logs (espescially bpdm) should tell us what exactly is happening on media server during cleanup.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

trs06's picture

I do not have an .../admin log file with the status 174 or for the dates I'm getting them but attached is a .../bpdm log.  I looked for a reason I could recognize as causing the problem but didn't find one.

AttachmentSize
020613.txt 65.34 MB
Marianne's picture

Exact same entries in bpdm log as in Job details:

 

10:17:19.914 [10892.8500] <16> 1143321:bptm:10892:utlp5179.ad.ama-assn.org: STSImageManager: unlink() failed on image file E:\BACKUP-SP\appp5031_1360165313_C1_F4.1360165313.img (Permission denied)

10:17:19.977 [10892.8500] <32> bp_sts_delete_image: sts_delete_image of image appp5031_1360165313_C1_F4 failed: error 2060037 

10:17:20.023 [10892.8500] <32> delete_image_disk_sts_impl: image delete failed: error 2060037: 
  
10:17:20.055 [10892.8500] <2> volume_cleanup_delete_fragment: deletion of appp5031_1360165313, copy number 1, fragment number 4, resume number 0 media id E:\BACKUP-SP failed 174

I can find no explanation of why files were actually removed without any evidence in the log file....

Any errors maybe in Event Viewer System or Application log?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

trs06's picture

When I was setting this up some time ago, I vaguely remember that I may have deleted the contents of the backup directory.  If I did, I did it manually and not through Netbackup.  If that were the case might that be the reason for the files to not be there and Netbackup subsequently throwing status 174 as it goes through the Catalog for expired images?

Topher-lab's picture

When images are manually deleted from disk, no update was ever sent to the NBU catalog, so we will still look for the images to delete. 

This issue presents more like the disk storage is no longer associated with that media server.  Is it possible that at some point in the past we ran a bpimage -oldserver <old media server name> -newserver utlp5179.ad.ama-assn.org ?

Otherwise, I would make sure that folder exists exaclty as it is cited in the detailed status on that media server: E:\BACKUP-SP

There is an additional item to review, and that is the "Log On As" for the media server's NetBackup services.  It is possible that we're running with an Account that no longer has rights to read, write, execute & list in that directory.

trs06's picture

The storage exists and is correct.  It is EMC VMAXe provisioned storage. The same server also has ~2.5 TB of F:\backup for a weeks retention of our Netbackup Catalog.  That storage is fine.  No issues, no errors and "clean up"s just fine.  I also checked permissions between the F and E drives and they are the same.  Of course, the same services and service accounts are running both Storage Units.  I will monitor the two logs you suggested and see if anything more turns up.

thx