Unscheduled full backups

Technically, NW only knows one reason: it does not find a full in the media db 
any more (as reported by Jim).

Nobody can tell you right away why previous fulls can not be recognized any 
longer:
  - One possibility is an accidental overwrite (relabel) process
  - Aomebody probably just deleted the save sets or volumes from the media index
  - The media db could also become currupt (most unlikely with NW 7.3+).

You can verify the existing backups with mminfo, for example

     mminfo -q "client=<name>, savetime>-1year" -r 
"client,name,level,savetime,sumsize" -ot

This should sched a light.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER