Arno Lehmann wrote:
Hello,
On 11.10.2005 09:31, Danie Theron wrote:
Hi , sorry for the long post :)
No worries, I didn't read it :-)
(Only joking)
Wanted to do a test restore , and it seems either my catalog is doing
funny things , or I messed up in the Pool defs :
+-------+-------+----------+---------------------+----------------------+-----------+--------------+----------------+
| JobId | Level | JobFiles | StartTime |
VolumeName | StartFile | VolSessionId | VolSessionTime |
+-------+-------+----------+---------------------+----------------------+-----------+--------------+----------------+
| 2,389 | F | 46,653 | 2005-10-03 19:50:54 |
apollousersfull-0007 | 2 | 3 | 1,128,326,240 |
<removed some table output>
| 2,482 | I | 109 | 2005-10-10 21:32:39 |
apollousersincr-0011 | 0 | 3 | 1,128,959,605 |
+-------+-------+----------+---------------------+----------------------+-----------+--------------+----------------+
That's the list of backup jobs run for that client, right?
It used tapes -full-007, -diff-001, and -incr-0011 and -0014.
Now , correct me if I'm wrong , but shouldn't it use the latest full
, diff , as well as ALL the incr vols?
No, only the incremental ones that actually hold relevant data.
Imagine you only change one file each day, and that file is,
accordingly, the only one backed up daily. For a restore, you only
need the latest volume.
Yet if I do a list media :
*list media pool=apollousersincr
...
*list media pool=apollousersdiff
...
There are many volumes in these pools...
If I need to post my confs I can , but here are the defs for this
spesific Pool :
...
Not sure if I'm just paranoid , stupid , or missing something (it's
been a long day....)
Erm. Possibly :-)
Somehow you forgot to tell us of your problem - what sort of a restore
do you start, and which volumes does it want to use?
Well I used option '5: Select the most recent backup for a client' - and
yes ,seems I was just paranoid :p , it uses the right volumes so it
seems.I'm just baffled that it lists the -full-0007 volume more than
once (?).I guess it was more of a paranoia than an actual problem.....
If you want to verify what Bacula does, I found it helpful to do
things differently:
For example, doing a full restore. I look up the job ids of the last
full job, the relevant (i.e. latest) differential one, and all the
incrementals past that one.
Then I listthe volumes which contain data from these jobs. Up till
now, I could always stop here :-)
The next step would be to compare the file lists for incremental jobs
to see why incremental volumes don't need to be used - all files
stored in the relevant jobs should also exist in later incremental
backups.
AH ok that clears most paranoia (gee i'm using that a lot) , thank you
very much for your time.
Hope this helps,
Arno
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
