Re: [Bacula-users] Bacula Client Status

2013-04-15 Thread Novosielski, Ryan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Be aware that some of the stuff you're talking about is just the last N jobs that occurred and what their status was. After a time, they will not be the most recent jobs and will drift off the end of that listing. On 04/15/2013 08:32 AM, Kenny Noe wro

Re: [Bacula-users] Bacula Client Status

2013-04-15 Thread Kenny Noe
Dan, Thanks for the reply. New jobs mostly run OK. I get a few "cancels" every so often and try to place tracing them down near the top of the Pri list. I'll investigate further. Came in this mornig and had a few mins to review the job status and everything is clear / cleaned up. I didn't do

Re: [Bacula-users] Bacula Client Status

2013-04-12 Thread Dan Langille
On 2013-04-08 09:16, Kenny Noe wrote: > Hello, > > When I check my client status on my server it reports multiple > instance of the same job running.  These jobs span back several days. >  However when I lookup the job via the "list jobid={id number] the > job is shown as "A" (canceled) A copy/pas

[Bacula-users] Bacula Client Status

2013-04-08 Thread Kenny Noe
Hello, When I check my client status on my server it reports multiple instance of the same job running. These jobs span back several days. However when I lookup the job via the "list jobid={id number] the job is shown as "A" (canceled) How can I clean up the client status list? Or should I eve