Re: [Bacula-users] Restore single Job from two different Storages
2011-01-24 19:19:22
Just giving a Feedback, after installing Bacula from scratch and restarting all of my Backups Jobs again, now Bacula is Doing The Right Thing:
Run Restore job JobName: job.restore Bootstrap: /var/lib/bacula/dir.ptibacula-dir.restore.1.bsr
Where: /mnt/backup/restore/ Replace: always FileSet: fs.default Backup Client: client.ptibd-dmz Restore Client: client.localhost Storage: st.tpc When: 2011-01-24 21:55:21
Catalog: cat.default Priority: 10 Plugin Options: *None*
OK to run? (yes/mod/no): yes Job queued. JobId=51
24-Jan 21:56 dir.ptibacula-dir JobId 51: Start Restore Job job.restore.2011-01-24_21.56.13_07
24-Jan 21:56 dir.ptibacula-dir JobId 51: Using Device "dev.tpc" 24-Jan 21:56 st.ptibacula-st JobId 51: 3307 Issuing autochanger "unload slot 12, drive 0" command. 24-Jan 21:58 st.ptibacula-st JobId 51: 3304 Issuing autochanger "load slot 5, drive 0" command.
24-Jan 21:59 st.ptibacula-st JobId 51: 3305 Autochanger "load slot 5, drive 0", status is OK. 24-Jan 21:59 st.ptibacula-st JobId 51: Ready to read from volume "000005L4" on device "dev.tpc" (/dev/tpc-tape).
24-Jan 21:59 st.ptibacula-st JobId 51: Forward spacing Volume "000005L4" to file:block 19:0. 24-Jan 22:02 st.ptibacula-st JobId 51: End of Volume at file 21 on device "dev.tpc" (/dev/tpc-tape), Volume "000005L4"
24-Jan 22:04 st.ptibacula-st JobId 51: 3307 Issuing autochanger "unload slot 5, drive 0" command. 24-Jan 22:05 st.ptibacula-st JobId 51: 3304 Issuing autochanger "load slot 11, drive 0" command.
24-Jan 22:05 st.ptibacula-st JobId 51: 3305 Autochanger "load slot 11, drive 0", status is OK. 24-Jan 22:05 st.ptibacula-st JobId 51: Ready to read from volume "000011L4" on device "dev.tpc" (/dev/tpc-tape).
24-Jan 22:05 st.ptibacula-st JobId 51: Forward spacing Volume "000011L4" to file:block 4:0. 24-Jan 22:06 st.ptibacula-st JobId 51: End of Volume at file 4 on device "dev.tpc" (/dev/tpc-tape), Volume "000011L4"
24-Jan 22:06 st.ptibacula-st JobId 51: acquire.c:117 Changing read device. Want Media Type="LTO3" have="LTO4" device="dev.tpc" (/dev/tpc-tape) 24-Jan 22:06 st.ptibacula-st JobId 51: Media Type change. New read device "dev.tpa" (/dev/tpa-tape) chosen.
24-Jan 22:07 st.ptibacula-st JobId 51: Ready to read from volume "000002L3" on device "dev.tpa" (/dev/tpa-tape). 24-Jan 22:07 st.ptibacula-st JobId 51: Forward spacing Volume "000002L3" to file:block 1:0.
24-Jan 22:08 st.ptibacula-st JobId 51: End of Volume at file 3 on device "dev.tpa" (/dev/tpa-tape), Volume "000002L3" 24-Jan 22:08 st.ptibacula-st JobId 51: End of all volumes. 24-Jan 22:08 dir.ptibacula-dir JobId 51: Bacula dir.ptibacula-dir 5.0.3 (30Aug10): 24-Jan-2011 22:08:48
Build OS: i686-redhat-linux-gnu redhat JobId: 51 Job: job.restore.2011-01-24_21.56.13_07 Restore Client: client.localhost Start time: 24-Jan-2011 21:56:15
End time: 24-Jan-2011 22:08:48 Files Expected: 2,523 Files Restored: 2,523 Bytes Restored: 1,955,791,042 Rate: 2597.3 KB/s FD Errors: 0
FD termination status: OK SD termination status: OK Termination: Restore OK
YEY!! :)
Maybe the issue before was because I upgraded Bacula from 3.0.3 to 5.0.3, but I can't confirm it...
2011/1/10 Rodrigo Renie Braga <rodrigorenie AT gmail DOT com>
Well, thank you very much for your time, and as for the FullPool directive, I already change it to do this in the Job section in my new fresh install, as soon as I get the results, I'll post it here...
Thanks again!
On 01/10/11 14:21, Rodrigo Renie Braga wrote:
> Yes, it does (see the following configuration). One more thing... I was
> using the latest 3.0 version of Bacula and I updated it to 5.0.3
> (Clients and Director). Could this be the problem? Just to make sure,
> I'm creating a fresh install of Bacula 5.0.3 just to see if this problem
> remains...
>
> Pool {
> Name = pool.tpa.full
> Pool Type = Backup
> Storage = st.tpa
> Volume Use Duration = 28d
> Volume Retention = 90d
> Maximum Volumes = 21
> Recycle = yes
> AutoPrune = yes
> Scratch Pool = scratch.tpa
> RecyclePool = scratch.tpa
> Cleaning Prefix = "CLN"
> }
>
> Pool {
> Name = pool.tpb.diff
> Pool Type = Backup
> Storage = st.tpb
> Volume Use Duration = 6d
> Volume Retention = 30d
> Maximum Volumes = 4
> Recycle = yes
> AutoPrune = yes
> Scratch Pool = scratch.tpb
> RecyclePool = scratch.tpb
> Cleaning Prefix = "CLN"
> }
That all looks good to me.
One comment here:
> Schedule {
> Name = sch.tpa
> Run = Level=Full Pool=pool.tpa.full 1st sun at 01:00
> Run = Level=Differential FullPool=pool.tpa.full Pool=pool.tpb.diff
> 2nd-5th sun at 01:00
> Run = Level=Incremental FullPool=pool.tpa.full Pool=pool.tpb.inc
> mon-sat at 01:00
> }
Schedule-level Pool overrides have been deprecated because they could
not be made to work reliably in all cases. There were just too many
cases in which it would do the wrong thing (for instance, when promoting
jobs). You should be using the Full Pool, Differential Pool,
Incremental Pool directives in your Job or JobDefs resources.
This won't affect the problem you're seeing, though.
--
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|