Netbackup keeps doing Full Backups

[vluu]

Hi,

I have a Netbackup Server Policy that has two Windows 2003 server as clients. One of the server keeps performing full backups everyday, when the other server behaves properly since they are sharing the same policy.

I have manual schedule full backups to see if this would correct itself, nothing has changed on the server side, it was working before. We are running Netbackup 6.5 Release Update 3 Hot fix 1. Any Ideas???

Thanks

[Anonymous]

Where I would start here is to compare between the clients behaving correctly and those not.
And compare the Client Configuration on the client.

You should look into using the bpgetconfig command.

# bpgetconfig -M <clientname>

The maybe run a diff on the settings.

Check that both servers are the same configuration within the Master servers client configs

# bpclient -client <clientname>

[Will_Restore · Accepted solution]

<install_path>\VERITAS\NetBackup\db\images\<client>\STREAMS

This happened to us on older version and might apply here too
http://seer.entsupport.symantec.com/docs/304269.htm

[J_H_Is_gone]

can you give the schedue info?

I want to see how big each window is and what you have your frequency set to.

As well has now long does it take the backup for each server to run.

My first thought is you have an issue with the size of the window and the frequency.

[vluu]

Hi Stuart, WRobbins, and J Hinchcliffe,

Firstly, thanks for your replies and being patient as i am a Netbackup newbie. Here some new info, noticed that the Full backup occurs every Monday on the problem server. I have re-installed the netbackup client.

Stuart - the bpgetconfig command produce the client configs and here are the differences:

Server working properly settings:
LIST_FILES_TIMEOUT = 300
Buffer_Size = 32
Policy_Type = 13
Client_Version = 500
VERSIONINFO = "WindowsNET" "5" "nt" "Netbackup" "6.0" 600000

Problem Server:
LIST_FILES_TIMEOUT = -1
Buffer_Size = 16
Policy_Type = 0
Client_Version = 31
Client_Version = 500
VERSIONINFO = "Windows2003" "5" "nt" "Netbackup" "6.5" 650000
 

I am not sure what I should belooking for but what concerns me is the Policy_type..can you provide any details?

WRobbins - I see the Stream files but haven't got I clue what to llok for or where to start..any insights?

J Hinchcliffe - attach is the Schedule, please let me know if you see anything out of order?

[vluu]

Hi again,

Anybody have any advice for me concerning this problem?

Also want to mention that both servers which are part of the same policy are using Veritas Replication Exec, If that matters since only one server keeps doing full.

Thanks,
Vinh

[CJett]

Hey Vinh, can you please post your schedule image again?  It appears to be broken.

[Stumpr2]

Stuart - the bpgetconfig command produce the client configs and here are the differences:

Server working properly settings:
LIST_FILES_TIMEOUT = 300
Buffer_Size = 32
Policy_Type = 13
Client_Version = 500
VERSIONINFO = "WindowsNET" "5" "nt" "Netbackup" "6.0" 600000

Problem Server:
LIST_FILES_TIMEOUT = -1
Buffer_Size = 16
Policy_Type = 0
Client_Version = 31
Client_Version = 500
VERSIONINFO = "Windows2003" "5" "nt" "Netbackup" "6.5" 650000


The differences  of policy_type
12 = NT-Windows
0 = standard for UNIX/Linux

Check the hardware configuration applied to the problem client in the policy client lists

[vluu]

Hi,

Bob - The policy _type for the policy that these two servers are part of is the "MS-Windows-NT". would you know how I can make the policy_type the same? Sorry for the stupid question?

Here's the policy details:
Policy Name: CanGA_Servers
Options: 0x0
template: FALSE
c_unused1: ?
Names: (none)
Policy Type: MS-Windows-NT (13)
Active: yes
Effective date: 05/06/2005 10:06:11
Client Compress: no
Follow NFS Mnts: no
Backup netwrk drvs:no
Collect TIR info: no
Mult. Data Stream: no
Perform Snapshot Backup: no
Snapshot Method: (none)
Snapshot Method Arguments: (none)
Perform Offhost Backup: no
Backup Copy: 0
Use Data Mover: no
Data Mover Type: 2
Use Alternate Client: no
Alternate Client Name: (none)
Use Virtual Machine: no
Enable Instant Recovery: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR Info: no
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Client Encrypt: no
Checkpoint: yes
Interval: 30
Residence: CanTRNBU01-hcart-robot-tld-0
Volume Pool: SSGA
Server Group: *ANY*
Granular Restore Info: no
Generation: 29
Client/HW/OS/Pri: CantrGAFS1DR PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri: CanmoGAFS1DR PC Windows2003 0 0 0 0 ?
Include: ALL_LOCAL_DRIVES
Include: Shadow Copy Components:\
Exclude: (none defined)
Schedule: Monthly
Type: FULL (0)
Calendar sched: Enabled
SPECIFIC DATE 0 - 05/30/2008
Friday, Week 3
EXCLUDE DATE 0 - 06/06/2008
EXCLUDE DATE 1 - 01/16/2009
EXCLUDE DATE 2 - 01/17/2009
EXCLUDE DATE 3 - 01/15/2010
EXCLUDE DATE 4 - 01/16/2010
EXCLUDE DATE 5 - 01/21/2011
EXCLUDE DATE 6 - 01/22/2011
EXCLUDE DATE 7 - 01/20/2012
EXCLUDE DATE 8 - 01/21/2012
Maximum MPX: 10
Synthetic: 0
PFI Recovery: 0
Retention Level: 9 (infinity)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 000:00:00
Monday 000:00:00 000:00:00
Tuesday 000:00:00 000:00:00
Wednesday 000:00:00 000:00:00
Thursday 000:00:00 000:00:00
Friday 020:00:00 044:00:00 140:00:00 164:00:00
Saturday 000:00:00 000:00:00
Schedule: Yearly
Type: FULL (0)
Calendar sched: Enabled
SPECIFIC DATE 0 - 01/16/2009
SPECIFIC DATE 1 - 01/15/2010
SPECIFIC DATE 2 - 01/21/2011
SPECIFIC DATE 3 - 01/20/2012
Maximum MPX: 10
Synthetic: 0
PFI Recovery: 0
Retention Level: 9 (infinity)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 000:00:00
Monday 000:00:00 000:00:00
Tuesday 000:00:00 000:00:00
Wednesday 000:00:00 000:00:00
Thursday 000:00:00 000:00:00
Friday 020:00:00 044:00:00 140:00:00 164:00:00
Saturday 000:00:00 000:00:00
Schedule: Weekend
Type: CINC (4)
Frequency: 7 day(s) (604800 seconds)
EXCLUDE DATE 0 - 02/20/2009
EXCLUDE DATE 1 - 02/21/2009
EXCLUDE DATE 2 - 03/20/2009
EXCLUDE DATE 3 - 03/21/2009
EXCLUDE DATE 4 - 04/17/2009
EXCLUDE DATE 5 - 04/18/2009
EXCLUDE DATE 6 - 05/15/2009
EXCLUDE DATE 7 - 05/16/2009
EXCLUDE DATE 8 - 06/19/2009
EXCLUDE DATE 9 - 06/20/2009
EXCLUDE DATE 10 - 07/17/2009
EXCLUDE DATE 11 - 07/18/2009
EXCLUDE DATE 12 - 08/21/2009
EXCLUDE DATE 13 - 08/22/2009
EXCLUDE DATE 14 - 09/18/2009
EXCLUDE DATE 15 - 09/19/2009
EXCLUDE DATE 16 - 10/16/2009
EXCLUDE DATE 17 - 10/17/2009
EXCLUDE DATE 18 - 11/20/2009
EXCLUDE DATE 19 - 11/21/2009
EXCLUDE DATE 20 - 12/18/2009
EXCLUDE DATE 21 - 12/19/2009
EXCLUDE DATE 22 - 01/15/2010
EXCLUDE DATE 23 - 01/16/2010
Maximum MPX: 10
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 000:00:00
Monday 000:00:00 000:00:00
Tuesday 000:00:00 000:00:00
Wednesday 000:00:00 000:00:00
Thursday 000:00:00 000:00:00
Friday 020:00:00 044:00:00 140:00:00 164:00:00
Saturday 000:00:00 000:00:00
Schedule: Daily
Type: INCR (1)
Frequency: 1 day(s) (86400 seconds)
EXCLUDE DATE 0 - 08/15/2008
EXCLUDE DATE 1 - 08/16/2008
EXCLUDE DATE 2 - 09/19/2008
EXCLUDE DATE 3 - 09/20/2008
EXCLUDE DATE 4 - 10/17/2008
EXCLUDE DATE 5 - 10/18/2008
EXCLUDE DATE 6 - 11/21/2008
EXCLUDE DATE 7 - 11/22/2008
EXCLUDE DATE 8 - 12/19/2008
EXCLUDE DATE 9 - 12/20/2008
EXCLUDE DATE 10 - 01/16/2009
EXCLUDE DATE 11 - 01/17/2009
Maximum MPX: 10
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 020:00:00 032:00:00 020:00:00 032:00:00
Monday 020:00:00 032:00:00 044:00:00 056:00:00
Tuesday 020:00:00 032:00:00 068:00:00 080:00:00
Wednesday 020:00:00 032:00:00 092:00:00 104:00:00
Thursday 020:00:00 032:00:00 116:00:00 128:00:00
Friday 000:00:00 000:00:00
Saturday 020:00:00 032:00:00 164:00:00 176:00:00 008:00:00

Thanks

[vluu]

The client configs are the same now for both servers in the same policy. Unfortunately, the problematic server is still backing up everything on the server, even though the schedule is differential incrementals.

I spoke with Veritas Replication Exec, but they do not believe that Replication Exec is changing the file attributes. We went through the setup and everything looks fine on VRE.

Any other clue, as this is affecting our backups becauseit is occupying drives and tapes, causing other backup jobs to timeout.

Thanks Again

[Stumpr2]

Tripwire or virus software touching the files?

[vluu]

Server is running Symantec Antivrus 10.1.6.6000. But again, symantec is also running on the non-problematic server.

[J_H_Is_gone]

in the client settings of client properties - is it set to ?

Incremental - based on timestamp or based on archive bit?  are both servers set the same?

[vluu]

For both servers, client properties is set to archive bit

[dfinley]

This is a possibilty, can you verify the archive bit actually gets turned off after successful full & differential incremental backups? If so, check the same files before your next incremental and see if something is turning it back on.

I recently uncovered a problem with one of our servers that was seeing 100's of GBs each day getting backed up although I knew nowhere near that much data was changing. This server is a file repository for remote branches, and each night it gets fed the changes from the remotes using scheduled tasks and the xxcopy utility. I discovered this utility has been turning the archive bit back on for many files even though they hadn't changed or been copied at all. It appears to be a bug with one of the switches on the xxcopy utility that copies ntfs permissions along with the files.

[Pravs]

either the ctime/mtime of all files are changing or PEM might be culprit here. PEM might be scheduling it as a FULL backup only. your bpbkar logs will be able to tell that if it was started as Full backup or incremental.

[Marianne]

There was a suggestion 4 weeks ago to have a look at the STREAMS file for the problematic client.
My suggestion is to delete all STREAMS files in client image folder before next full backup and see what happens with incremental that follows.

[vluu]

Hi Pravs and Marianne,

Pravs - I had turned on the bpbkar logs but when I open it, its gibberish to me, meaning format it not clean, can't read in notepad or wordpad. Do I need a special program.

Marianne - have not had a chance to try your recommendation yet.

At the moment , I am trying this from what I found on KB sight:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/26b40b71a625ce0a88257091004bb5bc?OpenDocument

On my third netbackup tech support engineer, and none of them knew about this doc. Go figure! Hopefully it will work. I'll keep you informed.

Thanks again.

[Pravs]

Hi Vluu,
you don't nee any special editor to read logs. wordpad must be fine enough though I prefer Textpad. If oyu can't read it Tech support should read it and tell you the problem.

The article you found on KB might be applicable to you if your antivirus is really changing the mtime of yyour files. Hope it helps you.