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

Image cleanup status 174

Created: 12 Sep 2012 | 9 comments
styunin's picture

Hello,

I have some problem with deleting images from CIFS-share(DataDomain):

 

9/12/2012 4:32:55 PM - begin  
9/12/2012 4:32:55 PM - Info nbdelete(pid=17584) deleting expired images. Media Server: nbumaster Media: \\dd\CIFS\Backups      
9/12/2012 4:32:55 PM - Info bpdm(pid=8592) started             
9/12/2012 4:32:55 PM - started process bpdm (8592)
9/12/2012 4:32:57 PM - Info bpdm(pid=8592) initial volume \\dd\CIFS\Backups: Kbytes total capacity: 33665905152, used space: 16616655360, free space: 17049249792
9/12/2012 4:32:57 PM - Critical bpdm(pid=8592) sts_delete_image of image node05_1346119212_C1_F1 failed: error 2060037 access not allowed    
9/12/2012 4:32:57 PM - Critical bpdm(pid=8592) image delete failed: error 2060037: access not allowed      
9/12/2012 4:32:57 PM - Critical bpdm(pid=8592) sts_delete_image of image node01_1346119213_C1_F1 failed: error 2060037 access not allowed    
9/12/2012 4:32:57 PM - Critical bpdm(pid=8592) image delete failed: error 2060037: access not allowed      
9/12/2012 4:32:58 PM - Critical bpdm(pid=8592) sts_delete_image of image node04_1346119214_C1_F1 failed: error 2060037 access not allowed    
9/12/2012 4:32:58 PM - Critical bpdm(pid=8592) image delete failed: error 2060037: access not allowed      
9/12/2012 4:32:58 PM - Critical bpdm(pid=8592) sts_delete_image of image node03_1346119215_C1_F1 failed: error 2060037 access not allowed    
9/12/2012 4:32:58 PM - Critical bpdm(pid=8592) image delete failed: error 2060037: access not allowed      
9/12/2012 4:32:58 PM - Critical bpdm(pid=8592) sts_delete_image of image node02_1346119216_C1_F1 failed: error 2060037 access not allowed    
9/12/2012 4:32:58 PM - Critical bpdm(pid=8592) image delete failed: error 2060037: access not allowed      
9/12/2012 4:32:59 PM - Info bpdm(pid=8592) ending volume \\dd\CIFS\Backups: Kbytes total capacity: 33665905152, used space: 16616655360, free space: 17049249792
9/12/2012 4:32:59 PM - end ; elapsed time: 00:00:04
media manager - system error occurred(174)

Can you help to resolve this issue?

Comments 9 CommentsJump to latest comment

Marianne's picture

access not allowed

Is Media Server a Windows server?

Have you verified that NBU services are started with user id that has full access rights on the UNC path?

Check NBU Client Service as well as NBU Remote Manager and Monitor Service.

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

styunin's picture

Hello Marianne,

Yes Media Server is a Windows server(Windows 2008R2 Enterprise). And NBU Client Service and other have full access rights.

Marianne's picture

Please set logging level on master to 5 for bpdm process.

Ensure bpdm log folder exists. Check log file after next folder.
If you want us to look at this log for you, please rename log to bpdm.txt and post as attachment.

Another test: double check service account for NBU services. 
Next, logon to master as that service account.
Connect to UNC path. Test creation of some test files, then removal of those test files.

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

styunin's picture

Hello Marianne,

I can easily create and delete files and folders from that share. You can see log in attachment.

Thank you!

AttachmentSize
bpdm.txt 45.16 KB
Marianne's picture

Lots of (Permission denied) errors.

You need to confirm that logon accounts used for  NBU Client Service as well as NBU Remote Manager and Monitor Service have full access rights.

Please open these services, check logon account.
Next, logon to master with this account.

Open UNC path to images.

Check properties of one of the images listed in the bpdm log for which we are seeing 'Permission Denied'.

We also see (No such file or directory) errors.

Please navigate to path seen in bpdbm log and check/verify.

You may need your DD support team to assist with this issue.
NBU is reporting the issue, not causing it.
 

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

Mouse's picture

Double check you don't run NBU Services under LOCAL SERVICE account, it has no access to network shares.

styunin's picture

Thank you, I'll check this. But it worked 2 weeks ago.. I don't know what had changed.

styunin's picture

It's rather strange but now we have no errors in imagecleanup jobs. Unfortunately I don't know the reason.

Thank you.

trs06's picture

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.