Netbackup 7.6.0.3 not excluding folders

[yobole]

We have recenltly upgarded to Netbackup 7.6.0.3 . I have a client running windows 2003 with the netbackup agent also upgraded to version  7.6.0.3

However the backup jobs seems to be backing up all drives and not excluding the folders specified in the Exclude list unders Client properties 

This was working on previous version ? we have thus put upgarding all clients on hold 

Any ideas ??

[Nicolai]

Please verify the exclude list is still present on the client.

If the client was re-installed instead of upgraded the exclude list likely overwritten with default values.

Also verify if the exclude list is policy specific, that the master server policythe same.

[yobole]

Yes the exlude list is still  present and the agent was upgraded

The list is NOT policy specific as its listed Under All Policies and ALL shcedules

[Nicolai]

We need the log bpkar log from the client. With the right debug level it will show how the exclude list is being parsed.

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

If you choose to post the bpbkar log, attach it as a file to a post. Do not post the debug text directly.

Pls note: if a policy specific exclude list exist - Netbackup will pick that.

[Marianne]

Please ensure bpbkar folder exists on the client under <install-path>\veritas\netbackup\logs.

No need to increase logging level.

After next backup, copy the log file in this folder to bpbkar.txt and upload as File Attachment.

The log will show us if Exclude List is found and how it is applied.

[watsons]

I will also try with recreating a test policy (exactly as that one) to verify, if necessary remove the folders from exclude list and add them back again.

Recently I came across some policies having problem due to policy corruption.. that's why.

[yobole]

Out of curiosity ..Does anyone actually have this working on 7.6.0.3?

[Nicolai]

Working in my lab. Can you show us the exclude list  ?

[yobole]

ok After a support call to symantec  The files are actually excluded but what confused us was the fact that the excluded volumes actually have now started appearing in the activity monitor which never used to happen untill we upgraded to 7.6.0.3

Symantec claim this is by design and do not know why they did not use to appear in previous versions ..?????????????????????????

[Marianne]

You did not tell us which version you have upgraded from.

This has been default behaviour for a long-long time.

The folder name is backed up but the contents excluded.

bpbkar will confirm.

[yobole]

We have upgraded from 7.6.0.2 and still have clients on 7.6.0.2 which do NOT have the excluded volume in the activity monitor ...

we only just started seeing this behaviour on the two 7.6.0.3 clients we upgraded

[klp]

We have also encountered this same problem for clients upgraded last week.  It's building a directory list in the excluded area, but not backing up anything.  It becomes a problem because we are now getting a status 71  "none of the files in the file list exist " for a subdirectory of the exluded list that is an NFS mount.  Also because this policy is set for multitream, many more jobs are being created than previously.

The master is Solaris 10 nbu 7.6.0.3;  the client is Solaris 11 nbu 7.6.0.3 (upgraded from 7.6.0.2)

root@mgssppsh08:/usr/openv/netbackup# cat exclude_list

/zones/

/proc/

root@mgssppsh08:/usr/openv/netbackup# cat include_list

/zones/snapshots/

[watsons]

Only saw this in "Late breaking news": http://www.symantec.com/docs/TECH215894  but it's for Linux system, maybe have the support verify if that affects WIndows as well?

[Nicolai]

This tech note is about something else.

It is the exclude list on the VMware backup host being applied running VMware backups.

exclude list is for file system backup only - in this case is was also read and applied doing VMware backup. Simple programming error - ignoring the exclude list is a option to bpbkar.