Veritas-bu
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Veritas-bu] Incrementals are backing up unmodified files

2002-06-12 14:19:27
Subject: [Veritas-bu] Incrementals are backing up unmodified files
From: valcarcel AT caracas.oilfield.slb DOT com (Rafael Valcarcel)
Date: Wed, 12 Jun 2002 14:19:27 -0400 
Thanks Jerald for your reply.

I also noticed GetFileSecurity + "Access denied" errors, but I found out 
that at least in my case it was associated with files/directories created 
by Win2000 clients on the NT 4.0 server. It seems that somehow those 
clients are able to set access control list that the NT don't know how to 
handle resulting in the error. I was able to get rid of the errors by 
fixing the permissions on those files / directories. After that I didn't 
have any GetFileSecurity errors in the log but the problem with the 
extra-files in the incrementals continued. This add a 20G (after 
compression!) overhead to each incremental that is a lot for the small L9 
library we are using. My current workaround is to just exclude this 
directory from the daily incrementals and back it up only on the weekly 
fulls. But the problem is quite annoying since it doesn't look like 
something so complex that could be broken: the netbackup client just needs 
to check the archive bit or modification date on the file (I have no 
problem to check this information by looking at the file properties!).

Regards.
Rafael Valcarcel.

At 10:59 AM 6/12/2002 -0600, Iverson, Jerald S. wrote:
>yes, i have the exact same problem on one drive on one server.  i can do a
>full backup, about 19 gig, and then do an incremental backup and it will get
>over 14 gig:
>
>id     class type       client  date       time        kbytes    #files
>drive
>357856 0 nt  full       walrus  2002/06/09 06:56:14     700,080  12,579 C:\
>358240 0 nt  cumulative walrus  2002/06/10 02:37:02     200,107      53 C:\
>
>357855 0 nt  full       walrus  2002/06/09 06:48:34     150,374     473 D:\
>358239 0 nt  cumulative walrus  2002/06/10 02:36:10         510       4 D:\
>357854 0 nt  full       walrus  2002/06/09 05:45:07   5,607,691  20,687 F:\
>358238 0 nt  cumulative walrus  2002/06/10 02:34:31           1       0 F:\
>357849 0 nt  full       walrus  2002/06/09 01:14:54  10,826,592   7,803 K:\
>358230 0 nt  cumulative walrus  2002/06/10 02:11:40           1       0 K:\
>
>357847 1 nt  full       walrus  2002/06/09 00:45:22  19,333,166  79,110 N:\
>358228 0 nt  cumulative walrus  2002/06/10 02:01:24  14,419,377  48,149 N:\
>
>
>i also tried going by the date instead of archive bit, but that didn't help.
>i created a logs\bpbkar directory on the client to log what was happening,
>and found:
>
>06/12/02 02:25:03 AM: [592]: INF -
>======================================================================
>06/12/02 02:25:03 AM: [592]: INF - OTM: will attempt enable for 'N:\'
>06/12/02 02:25:03 AM: [592]: INF -
>======================================================================
>06/12/02 02:25:03 AM: [592]: INF - OTM Enable Parameters
>06/12/02 02:25:03 AM: [592]: INF -
>----------------------------------------------------------------------
>06/12/02 02:25:03 AM: [592]: INF - CacheFileName: ''
>06/12/02 02:25:03 AM: [592]: INF - SizeofCacheFileMB: 150
>06/12/02 02:25:03 AM: [592]: INF - MaxSizeOfCacheFileMB: 250
>06/12/02 02:25:03 AM: [592]: INF - QuiescentWait: 5
>06/12/02 02:25:03 AM: [592]: INF - QuiescentTimeout: 60
>06/12/02 02:25:48 AM: [592]: INF - OTM Mapping: N:\ --> 0:
>06/12/02 02:25:48 AM: [592]: INF - OTM Cache File: C:\WINNT\TEMP\OTM197.tmp
>06/12/02 02:25:48 AM: [592]: INF -
>======================================================================
>06/12/02 02:25:48 AM: [592]: INF - OTM Create - decrementing count for: N:\
>06/12/02 02:25:48 AM: [592]: INF - OTM: enabled
>06/12/02 02:25:48 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:48 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:48 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 02:25:49 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>..... another several thousand lines...
>06/12/02 05:01:15 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 05:01:15 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 05:01:15 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 05:01:15 AM: [592]: WRN - GetFileSecurity Failed (WIN32 5: Access
>is denied. )
>06/12/02 05:01:18 AM: [592]: INF - OTM Destroy - destroyed snapshot
>06/12/02 05:01:18 AM: [592]: INF - OTM Cleanup - success
>06/12/02 05:01:18 AM: [592]: TAR - backup: 48744 files
>06/12/02 05:01:18 AM: [592]: TAR - backup: file data: 849771660 bytes 13
>gigabytes
>06/12/02 05:01:18 AM: [592]: TAR - backup: image data: 998114304 bytes 13
>gigabytes
>06/12/02 05:01:18 AM: [592]: TAR - backup: elapsed time: 9376 secs 1595214
>bps
>06/12/02 05:01:18 AM: [592]: INF - EXIT STATUS 0: the requested operation
>was successfully completed
>06/12/02 05:01:29 AM: [592]: INF - 'INF - Server status = 0' received
>06/12/02 05:01:29 AM: [592]: INF - EXIT - status = 0
>06/12/02 05:01:29 AM: [592]:
>06/12/02 05:01:29 AM: [592]: INF - Finished process
>06/12/02 05:01:29 AM: [592]: INF - Exiting C:\Program
>Files\VERITAS\NetBackup\bin\BPBKAR32.exe
>06/12/02 05:01:31 AM: [592]: INF - Closing log file: C:\Program
>Files\VERITAS\NetBackup\logs\BPBKAR\061202.LOG
>
>so when it gets the "access is denied", i'm guessing it can't read either
>the time or archive bit, so it backs up the file.  it doesn't make sense why
>it only happens on one drive on the server, when it works for the others.
>also,  it didn't do this initially, it just started happening last year.
>i've tried to do some research but haven't found anything yet.  it hasn't
>been a high priority, it only wastes some tape, and at least it is backing
>up too much, instead of not enough.
>
>good luck,
>jerald iverson
>
>-----Original Message-----
>From: valcarcel AT caracas.oilfield.slb DOT com
><mailto:valcarcel AT caracas.oilfield.slb DOT com>
>[mailto:valcarcel AT caracas.oilfield.slb DOT com]
>Sent: Wednesday, June 12, 2002 9:59 AM
>To: veritas-bu AT mailman.eng.auburn DOT edu
><mailto:veritas-bu AT mailman.eng.auburn DOT edu>
>Subject: [Veritas-bu] Incrementals are backing up unmodified files
>
>
>Hopefully someone out there has seen this before and can help me out.
>
>I am using Netbackup BusinesServer 3.4.1. One of the clients being backed-up
>is a NT 4.0 SP5.
>The problem I am having is that daily Incrementals are always backing-up
>every file in one of the
>subdirectories (F:\Users). These are files that have not being modified for
>a really long time, even
>for a year. The archive bit is not set. I even changed the Netbackup setting
>to use modification date
>rather than archive bit and same behavior.  It doesn't happen with other
>directories in the same disk,
>only with this one. No problem reported in the logs.
>
>Regards,
>Rafael.
>
>
>____________________________________________________________________
>Rafael Valcarcel
>Schlumberger - GeoQuest / VPI Project Analyst
>Edificio Banaven
>entre Av. Ernesto Blohm y la Estancia, Torre B,
>Piso 2, Ofc B-23, Urb. Chuao
>Caracas , Venezuela.
>Interfilial: 93-54400, Office:(58-212)9915311 (ext. 145), Office Fax:
>(58-212)959-6252,
>Email: valcarcel AT caracas.oilfield.slb DOT com,
>Pager Skytel: Operadora: (58-212)952-8644 PIN: 5837892
>____________________________________________________________________
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Veritas-bu] Netbackup client behind firewall !, Karunanidhi Subramanian
Next by Date:  [Veritas-bu] BP.CONF File, Brian_Drager AT Vanguard DOT com
Previous by Thread:  [Veritas-bu] Incrementals are backing up unmodified files, Iverson, Jerald S.
Next by Thread:  [Veritas-bu] Incrementals are backing up unmodified files, Greg Guenther
Indexes:  [Date] [Thread] [Top] [All Lists]