* 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