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

Expired image not clean from MSDP catalog

Created: 24 Sep 2012 • Updated: 01 Oct 2012 | 15 comments
wilsonchong's picture
This issue has been solved. See solution.

Hi,

In our environment, there is AIX cluster master server with fews media server and 2 units of MSDP configured, all run at NBU 7.1.0.4.

Recently for the image cleanup job always failed with error code 1. After look into the job details, found out when clean up the image from one of the MSDP server always failed with error code 174 (system call failed.)

Attached the job details and the bpdm log from the MSDP server.

Hope can get some help from here. I suspect is the catalog cleanup of the fragment in the MSDP disk in not completed, so leave some orphans.

Regards,

Wilson

 

Comments 15 CommentsJump to latest comment

Nicolai's picture

Does this file exist : 

10:38:42.197 [4372.1872] <16> 16130:bptm:4372:NTNBUPSG11: impl_get_imh_image_prop error (5 Input/output error) reading /NTNBUPSG11#1/2/NTCRDPMY04-PRIV/W2008_ALL_LOCAL_MY/NTCRDPMY04-PRIV_1345806008_C2_F1_R2.info

It's the one bpdm can't read.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

wilsonchong's picture

The file still exist in the MSDP catalog folder. Together with the HDR file, img file and the MAP file.

captain jack sparrow's picture

give a try on manual fragment removal using crcontrol

 

 Cheers !!!

CJS

 

wilsonchong's picture

May I know what is the full syntax for using the crcontrol command?

Thanks.

wilsonchong's picture

Hi Jack,

Thanks for all the info. I did tried to run the garbage collection and process the queue twice, but still the same result. The expired image info still remain in the MSDP catalog folder. So when the NetBackup image cleanup, always failed.

I also tried to run the nbdelete -allvolumes -force, always come back with error 174 (system call failed), which can't read the /NTNBUPSG11#1/2/NTCRDPMY04-PRIV/W2008_ALL_LOCAL_MY/NTCRDPMY04-PRIV_1345806008_C2_F1_R2.info

But I did confirmed the file still at the MSDP server, just don't know is the file is corrupt, so it can't read.

captain jack sparrow's picture

make it capt. jack pls ;-)

BTW did you tried reboot does it helps.. one of similar post where reboot helped in reclaiming garbage. as syntax given above takes time to process and reflect the same.

Check if it's possible to take reboot of MSDP

 Cheers !!!

CJS

 

SOLUTION
Nicolai's picture

You're issue look like this one: 

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

The T/N is valid version 7.0 and 7.0.1 and you are on 7.1.0.4. I think you need to log a call with Symantec.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

wilsonchong's picture

Thanks for the info. I also did look at the T/N before.

I also rebooted the server, but the result still the same.

A case had been logged, but still no response from the support.

captain jack sparrow's picture

get the case expedited or may be they are investigating in logs...(if it's bug found in your domain)

 Cheers !!!

CJS

 

Mark_Solutions's picture

Have you tried:

bpexpdate -backupid NTCRDPMY04-PRIV_1345806008 -d 0 -force

to see if that flushes it out?

 

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

wilsonchong's picture

When run the bpexpdate command, the results is "no entity found"

Mark_Solutions's picture

odd question i know but is NTCRDPMY04-PRIV in more than one policy and if so is it in exactly the same case on both policies?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

wilsonchong's picture

The client only in a single policy.

After reboot the MSDP server, the image cleanup without any error, but the orphans image info still remain in the MSDP catalog folder.

Attached the screenshot of the catalog folder in MSDP server. Can see the expired image info for 24-Aug-2012 still remained in there.

catalog.JPG
Mark_Solutions's picture

It will take a while for the garbage collection to run and complete before old fragments are removed.

It queue processing runs at midnight and mid day, after which the garbage collection should run to tidy things up

You may have to just give it a while (potentially even a coupld of days) for it to get as far as those fragments

If they dont dissapear after that then check with support before you think of deleting anything manually

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.