Hi,

did you also create an individual job for each of your filesets?
Because this should work and if you get a message for the job it will
show up in "list jobs" and you can "list joblog jobid=ID" to look what
went wrong.

Best Regards,
Andreas

Am 14.11.19 um 20:15 schrieb 'Chad Seys' via bareos-users:
> Hi all,
>   I've divided one of our network filesystems into many FileSets on one
> client.  It has 813 FileSets.  We have other clients as well, mostly one
> FileSet per client for a total of 855 FileSets.
>   Should I expect Bareos to be able to handle this many FileSets?
> 
>   The problem is that when the scheduled time for all the FileSets
> arrives, almost all are immediately rescheduled for the next scheduled
> time.  (e.g. when today at 12:30pm arrives, 'status dir' shows that they
> are now scheduled for tomorrow at 12:30pm)
>   The jobs show up in the webui as "failure", but there is no other
> message in the webui.
>   'status client' does not show the job ever existed.  (It does not
> appear in list of Terminated Jobs).
>   'list backups client=' also does not show the job.
>   Running the job manually works (after restarting the server daemons).
> 
> In the bareos.log file The below message is seen repeatedly.  (Note
> though that Full backups have been taken and an incremental is performed
> with manually run, so  that part is wrong.)
> 
> 14-Nov 12:31 bareos-dir JobId 5096: No prior or suitable Full backup
> found in catalog. Doing FULL backup.
> 14-Nov 12:31 bareos-dir JobId 5097: No prior Full backup Job record found.
> 14-Nov 12:31 bareos-dir JobId 5097: No prior or suitable Full backup
> found in catalog. Doing FULL backup.
> 14-Nov 12:31 bareos-dir JobId 5098: No prior Full backup Job record found.
> 
> Previous to adding the huge client backups were occurring as expected.
> 
> Anyone have ideas, other than trimming back the FileSets?  (It wouldn't
> make much sense to do this. There is so much data / too slow a network
> filesystem for a Full to complete in a reasonable amount of time.)
> 
> Thanks!
> Chad.
>  
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/bareos-users/f7e04b1e-1253-4941-b882-3707d6b47d12%40googlegroups.com
> <https://groups.google.com/d/msgid/bareos-users/f7e04b1e-1253-4941-b882-3707d6b47d12%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
  Andreas Rogge                             [email protected]
  Bareos GmbH & Co. KG                      Phone: +49 221-630693-86
  http://www.bareos.com

  Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
  Komplementär: Bareos Verwaltungs-GmbH
  Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/77d0fd37-5e07-3a0c-cdec-75673ec27d49%40bareos.com.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to