The great thing about this particular symptom is if you're paying
attention you notice it right away.  If you see your DB BCV mount backup
in about 10 minutes you know something is amiss.   I've seen this a few
times when after I've had to reboot our NetBackup server and neglected
to remount the BCV copy we'd automatically mounted after split earlier.
We can't just add them to fstab because we might not want them to mount
depending on the state of the BCV (syncing etc...) at the time of the
boot.

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of David
Rock
Sent: Saturday, September 09, 2006 12:35 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] backup 1K files that can't be restored? (was
Re:Fame at last.)

* Rob Worman <rob at worman.org> [2006-09-08 17:28]:
> There is one sentence that confuses me about Ms. Fisher's
> recent CW article:
> 
>  "One major issue Veritas users cited with NetBackup 6.0 is 
>  that when a backup job indicates it's complete, it often has 
>  only backed up 1K files, so there's no data to restore. "
> 
> Whoa, that DOES sound scary.  Backed up files that can't
> be restored?!?
> 
> But what does that sentence really mean?  Especially the 
> reference to "only backed up 1K files"?  Is that meant to
> symbolize "1000 files"?
> 

Another example of a similar symptom is a backup of a mountpoint where a
filesystem is supposed to be mounted, but never did so the resulting
backup is only of the directory mountpoint itself.  Status 0, but no
files were backed up.

That also would not be NetBackup's fault.  It backed up exactly what you
told it to, there just wasn't anything there when it tried.  Note that
is different from a Status 71 where specific files were listed and were
not found.  

Both of these are common errors when doing user-directed database export
backups or bcv mounts.  The script to create the export or mount the bcv
fails, runs the backup on an empty directory and poof, a successful
failed backup.  User error or bad script design, not a NetBackup bug.

Some of the current reporting packages are capable of flagging such a
situation to alert you that _maybe_ something is wrong.

-- 
David Rock
david at graniteweb.com
_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu