On 31.10.2018 at 10:37 wrote Sven Gehr:
> Hi@all,
> 
> I hope a "cosmetic" problem. After a crash I have new installed my kvm-host 
> (backup server) an bareos on it.
> 
> I import all my vm's with installed an configurate bareos-client.
> 
> My bareos server is empty and I will start new. When I run the status command 
> on my server I see:
> 
> *status client=tux.peka.lan-fd 
> Connecting to Client tux.peka.lan-fd at tux.peka.lan:9102
> 
> tux.peka.lan-fd Version: 17.2.6 (19 Jun 2018)  x86_64-pc-linux-gnu univention 
> Univention GNU/Linux 9.3 (stretch)
> Daemon started 31-Okt-18 10:25. Jobs: run=0 running=0.
>  Heap: heap=135,168 smbytes=29,432 max_bytes=29,821 bufs=75 max_bufs=78
>  Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s
> 
> Running Jobs:
> bareos-dir (director) connected at: 31-Okt-18 10:26
> No Jobs running.
> ====
> 
> Terminated Jobs:
>  JobId  Level    Files      Bytes   Status   Finished        Name 
> ======================================================================
>    581  Incr        777    2.194 G  OK       02-Okt-18 21:01 
> Backup-tux.peka.lan
>    583  Incr        401    182.6 M  OK       03-Okt-18 21:01 
> Backup-tux.peka.lan
>    585  Incr      6,843    5.454 G  OK       04-Okt-18 21:01 
> Backup-tux.peka.lan
>    587  Incr        802    2.403 G  OK       05-Okt-18 21:01 
> Backup-tux.peka.lan
>    589  Full    938,893    474.3 G  Error    12-Okt-18 04:48 
> Backup-tux.peka.lan
>    590  Incr      2,206    10.10 G  OK       12-Okt-18 04:51 
> Backup-tux.peka.lan
>    592  Incr      2,206    10.10 G  OK       12-Okt-18 04:52 
> Backup-tux.peka.lan
>    594  Incr      2,206    10.10 G  OK       12-Okt-18 04:53 
> Backup-tux.peka.lan
>    596  Incr      2,206    10.10 G  OK       12-Okt-18 04:54 
> Backup-tux.peka.lan
>    598  Incr        793    2.314 G  OK       12-Okt-18 21:01 
> Backup-tux.peka.lan
> ====
> 
> My bareos server has no jobs in db. How can I delete this old 
> status-information?

Yes, this is only a cosmetic problem. The old information will disappear
over time. Each daemon stores old job run status to show them via the
status command.

If think, the *.state file in /var/lib/bareos/ is stores this
information. Stopping the daemon, deleting /var/lib/bareos/*.state and
starting the daemon again, will solve this issue.

BTW: have you been able to recreate your Bareos Catalog via bextract or
even bscan?

regards,
Jörg

-- 
 Jörg Steffens                   joerg.steff...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-91
 http://www.bareos.com           Fax:   +49 221 630693-10

 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örg Steffens, P. 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 bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to