Hi everybody.
For some test purposes I do often the following as described in the
bacula documentation:
cd /usr/local/bacula/bin
./bacula stop
./drop_bacula_tables
./make_bacula_tables
cd <directory to the volumes>
rm -rf <volume files>
mt -f /dev/nst0 rewind
mt -f /dev/nst0 weof
./bacula start
Now it should all removed and I can start with a fresh system.
The funny situation is that, that the clients must save information
about any old
backup run anywhere, but where?
When I did a status client=CCRM0004-fd before the removal then I get
the information about my runs in the last 3 days. 3 days ago were the
last removal.
Then I do the removal now.
After restarting bacula and run a status client=CCRM0004-fd again then I
will
get the information about old backup run 3 days ago as before the
removal.
Can anyone tell me where the bacula server or the bacula client is
storing
old information about old backup runs?
br Robert
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
