NetBackup 7.5- Client Exclude *.mdf fails on FULLs / works on Incremental backups

[Kwinter]

When backing up SQL server, the client is configured with exclude *.mdf, *.ndf, *.ldf  files and with incremental backups, NB does avoid it, but with full backups it backs it up.

This is weird, and it slows down our backups and eats up media disk space.

Any ideas where to look would be greatly appreciated.

Thanks

[revarooo]

Is the exclude list set-up based on schedules? If so you may have a exclude skipping the files on the incremental but not on the full schedule.

[Anonymous]

This could be possible with the above? Or without even the Exception which really means INCLUDE.

So check out your client settings.

[Mark_Solutions]

Agree with revaroo - can't think of anything else that would cause this

Exclude lists are strange things and you need to be aware of how they work.

By default you get one that looks something like this:

C:\Program Files\Veritas\NetBackup\bin\*.lock
C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
C:\Program Files\Veritas\NetBackupDB\data\*
C:\Program Files\Veritas\Volmgr\misc\*
 

This applies to all schedules and all policies

But you may want to add one for certain schedules and / or certain policies which NetBackup allows you to do.

Now the list looks like this:

C:\Program Files\Veritas\NetBackup\bin\*.lock
C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
C:\Program Files\Veritas\NetBackupDB\data\*
C:\Program Files\Veritas\Volmgr\misc\*
CLASS:Windows_Policy
SCHED:Weekly_Schedule
*.mdf
 

But when the Windows_Policy with the Weekly_Schedule runs it excludes the *.mdf but ignores the others - in effect it will only use oine exclude list at a time.

That is why you have copy and paste buttons in the client excludes area so that you can make sure all relevant exclusions are set for all appropriate Policies / Schedules

If in doubt take a look in the clients registry under HKLM\Software\Veritas\NetBackup\CurrentVersion\config\ where the "exclude" key holds the list - the values shown above are copied directly from that key. If you see a CLASS then that means Policy (it is what they used to be called), if you see a SCHED then that refers to a Schedule

Hope this makes sense and helps

[Kwinter]

Great help.  my Exclude is for a windows cluster as the client.  it is setup to exclude "All Policies".  I am going to check the registry and test with specific schedules (like to avoid doing that).  attached is a screen shot.

[Mark_Solutions]

Dont forget to check the exclusions for each node - check both registries or host properties for each node name rather than the virtual name

[Kwinter]

here's the attachment now.

[Mark_Solutions]

cannot see the full list in your screen shot but i do see 2 exceptions which will always get backed up

Is there anything when you scroll further down - otherwise post the exclude registry values from each node

[Kwinter]

There are two windows 2008 R2 systems making up this cluster and in their client exclusion is the same configuration too.

(right now active node = vm-n1)

Windows cluster:  vm-c
---------------------------------

*.ldf
*.mdf
*.ndf
C:\Program Files\Veritas\NetBackup\bin\*.lock
C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
C:\Program Files\Veritas\NetBackupDB\data\*
C:\Program Files\Veritas\Volmgr\misc\*
CLASS:Schedule_Cluster_Server_VM-HDCSQLPROD03
C:\
 

Node 1:   vm-n1
----------------------

*.ldf
*.mdf
*.ndf
C:\Program Files\Veritas\NetBackup\bin\*.lock
C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
C:\Program Files\Veritas\NetBackupDB\data\*
C:\Program Files\Veritas\Volmgr\misc\*
CLASS:Schedule_Cluster_Server_VM-HDCSQLPROD03
C:\

Node 2:   vm-n2
----------------------

*.ldf
*.mdf
*.ndf
C:\Program Files\Veritas\NetBackup\bin\*.lock
C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
C:\Program Files\Veritas\NetBackupDB\data\*
C:\Program Files\Veritas\Volmgr\misc\*
CLASS:Schedule_Cluster_Server_VM-HDCSQLPROD03

 

[Mark_Solutions]

Based on the above, due to:

CLASS:Schedule_Cluster_Server_VM-HDCSQLPROD03
C:\

When the policy Schedule_Cluster_Server_VM-HDCSQLPROD03 runs only the C drive will be excluded.

When it fails over to node 2 nothing gets excluded when that policy runs

Nothing here to differentiate between schedules though.

#edit#

please show us both "Include" registry keys

[Kwinter]

here's the screen shots of the entire exclude list for the "cluster".

[Anonymous]

A cluster. Ah it all makes sense.

In Host Properties of the admin console section you can select multiple Clients (CTRL+CLICK) and set excludes/includes for ALL at once if this helps.

[Kwinter]

here is the includes for both members and the cluster.

[Kwinter]

sorry, I just checked last night incremental and it backed up the database file.

[Mark_Solutions · Accepted solution]

So what is the policy name? The one policy will only exclude the C drive.

Is the client also on 7.5?

Thanks

[Kwinter]

The policy:      Schedule_Cluster_Server_VM-HDCSQLPROD03

This policy backs up the Windows Cluster.

This policy is setup to avoid the c:\ drive.  but backup all other drives.

The C:\ backup is controlled by another policy, which explicitly backs up just the C:\   (both nodes).

All clients and server is running NetBackup 7.5 MP3.

[Mark_Solutions]

You need to add the *.mdf etc to the specific exclusion list - you can use the Copy and Paste options in the clients host properties (or just open the reg key up and paste them in its list (carefully)