Failure with VirtualFull causing next job to be a Full???

John Lockard <[email protected]>
Newsgroups gmane.comp.bacula.user
Message-ID <CAHDqrGe1ja2cJ5ZdUBWwLj9BjE6rnbNT=Cvj4pa6dLujww6=AQ@mail.gmail.com>
I've seen this a couple of times, and haven't created a small job to test,
but it appears that when I'm running a VirtualFull, and it fails for
whatever reason, the next time a job for that FileSet runs it gets elevated
to a Full and states that there is no previous Full.

Is this a normal reaction to a Failed Virtual Full?

Thanks,
-John

-- 
-- 
- Adaptability -- Analytical --- Ideation ---- Input ----- Belief -
-------------------------------------------------------------------
         John M. Lockard |  U of Michigan - School of Information
          Unix Sys Admin |      Suite 205 | 309 Maynard Street
      [email protected] |        Ann Arbor, MI  48104-2211
 www.umich.edu/~jlockard <http://www.umich.edu/%7Ejlockard> |
734-615-8776 | 734-763-9677 FAX
-------------------------------------------------------------------
- The University of Michigan will never ask you for your password -

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.