Exclude list is not working with ALL_LOCAL_DRIVES

[Brais]

Hello,

     Client Version: NBU 6.0

     Client OS: Win2k

     Master Verion: NBU 6.5.4  

     Master OS: Solaris 9

     I've a policy with backup selection set to ALL_LOCAL_DRIVES and allow multiple data streams. I've added a exclude list to F:\. However, this backup  stream starts, thus fails.

     After searching the net for info, I found this link http://www.symantec.com/connect/forums/exclude-list-not-working-w2k8-nb-656#comment-6198541. There, they propose several workarounds, which are not valid in my case. The only thing that seems ok for me is this patch http://www.symantec.com/business/support/index?page=content&id=TECH152708, see also http://www.symantec.com/business/support/index?page=content&id=TECH144007 but it is for versions 6.5.6 or higher.

How can I solve this issue, any help would be appreciated. 

Regards.

[mph999]

With the backup not running, goto here :

/usr/openv/netbackup/db/images/<client name>

or

veritas\netbackup\db\images\<client_name>

There should be a file STREAMS<policy_name> and .lck file, mv these out of the way and then re-run the backup.

Does it now work ???

Thanks,

Martin

[Brais]

Thank you, but it didnt work.

I launched a test backup and it has just created a new .lck file.

The error I get while trying to backup f: drive is 23.

Any idea?

[MKT]

6.0 GA is a very old release, I'd upgrade the client to 6.5 GA then apply 6.5.4. This may fix it or at least narrow the scope of what might be wrong.

[Marianne]

"However, this backup  stream starts, thus fails."

It is perfectly normal for a backup job to be generated. When ALL_LOCAL_DRIVES exist in Backup Selection, combined with Allow Multiple Data Streams, the 'Local Drives' will be discovered when the job is activated. The Exclude List is applied afterwards. This normally results in a backup job for the excluded drive letter, resulting in a successful backup of 32 Kb.

Please post client's bpbkar log on the client.

[Brais]

Hello and thanks for your reply,

I can not test it right now, the backup is not failing atm.

I know that exclussion list is applied after the discover of drives. What I would like is to do not start the backup of the drive I excluded (not even a 32k thing), because it will be shown as failed. Is it possible?

PD: If the backup will fail again, I'll post bpbkar log here.

Regards.

[Marianne]

The backup should NOT fail. It should result in a successful backup of 32Kb. The only way (to my knowledge) to prevent streams to be generated is to replace ALL_LOCAL_DRIVES with specific drive letters. What error code does it fail with?

[Brais]

The stream is failing with error 21 (socket open failed). All stremas finish ok, but drive f: stream fails.

Regards.