I saw this even before I applied FP5. We're at NBU DC 4.5 FP5, on 
Solaris 8. The windows boxes that complain about no files on absent 
disks, are behind on patches, and this kind of behavior is not really 
surprising for a windows box. I stopped the annoying messages by 
excluding the drive letter in the exclude list on the client. Someday, 
we'll get to upgrade patches on that client, and then I'll remove the 
exclude list, to see if things change. Once NB5 comes out, I think we'll 
force downtime and upgrade everything at once. The disk my client was 
complaining over was the E: drive, which might have once existed on this 
system. The strange part is the problem just started happening one day. 
Thankfully, the error is mostly annoying, and no data was neglected or lost.

-Jon

>Hi there,
>
>We are running NBU DC 4.5 FP5 on Solaris 9.  Lately, we've been getting
>quite a few status 71's where its trying to backup disks that don't exist on
>the server (see below -- there is no G: drive on this particular server):
>
>----------------------------------------------------------------------------
>------------------------------
>Subject: Backup on Astroid - 71 
>
>Backup on client Astroid by root failed.
>
>Status = none of the files in the file list exist.
>
>File list
>---------
>G:\
>----------------------------------------------------------------------------
>-------------------------------
>
>Just curious if anyone has seen this behaviour before and what might cause
>it???
>
>Kevin Cavanagh
>