Coverage displaying 2 different filesystems twice.

Can you show a df -k output from the client too?

Here are the parts of interest I hope.

/tmp                   (/dev/vg00/lvol4       ) : 10163272 total allocated Kb
                                                   9847088 free allocated Kb
                                                    316184 used allocated Kb
                                                         4 % allocation used
/usr/openv/netbackup/logs (/dev/vg01/nbulogslv   ) : 18358400 total allocated Kb
                                                  11438984 free allocated Kb
                                                   6919416 used allocated Kb
                                                        38 % allocation used
/usr/openv             (/dev/vg01/openvlv     ) : 15378664 total allocated Kb
                                                   2948072 free allocated Kb
                                                  12430592 used allocated Kb
                                                        81 % allocation used
/usr                   (/dev/vg00/lvol7       ) :  7386144 total allocated Kb
                                                   4568128 free allocated Kb
                                                   2818016 used allocated Kb
                                                        39 % allocation used

Also I have checked the policy and both duplicated entries on the report only exist in the policy.

sorry

Also I have checked the policy and both duplicated entries on the report only exist once in the policy.

Paul,

I don't think it's anything to do with the policy as running bpmount -i on the client shows the duplicate results for those 2 filesystems and bpmount -i does not check policies. I wonder if this is a Volume Manager issue or a bpmount issue.

Can you check if there is a /usr/openv/netbackup/include_list file on the client with those duplicate filesystems listed?

If not you could try using tusc on the bpmount to see what it's doing. You may need to raise a call with Symantec if it's causing issues for you.

... and it happened directly after OS patches were added ...

Were any of teh patches related to filesystems ?

Martin

That's a good point mph999, I missed that the client is also the master, I guess the clue was in the separate filesystem /usr/openv/netbackup/logs/ . A list of the patches and what they patch may be useful for trouble shooting this.

Hi and thank you for your input,

re - /usr/openv/netbackup/include_list  there is no file on the system (now systems involved see below)

However I have had a chance to dig deeper and found that there we have other servers showing a similar behavior.

Different filesystems are involved also.

All effected servers are patched to 7504.

All servers still at 656 awaiting upgrade are not effected.

We also have 2 servers that have not had the OS patches that are still at 656 (currently not effected)

I have upgraded one of these and the symptom appeared  - Must be 75 causing this.

Raising a call.

Must be NBU 7.5 with HP-UX combination. Not seeing the same on RHEL with 7.5.0.4.

Hi all,

Just posting a quick update,

We also have the symptoms on our Linux clients (Actually worse as "/" is reported 4 times) and it appears after both upgrades and new installs.

However I recently during a fresh install I made the following discovery,  The symptoms only appeared when we placed our exclude_list file into the /usr/openv/netbackup directory.

When I remove the exclude list the symptoms disappear.

Looks like something new in the bpmount command perhaps interrogating the exclude_list ?

Looks like something new in the bpmount command perhaps interrogating the exclude_list ?

Well it certainly does look there: http://www.symantec.com/business/support/index?page=content&id=TECH141363

Do the entries in the exclude_list correspond directly to the duplications you're seeing in bpmount -i ?