Hi Ana,
2015-05-19 6:58 GMT+02:00 Ana Emília M. Arruda <emiliaarr...@gmail.com>:
> (i'm supposing you will have on site2 just the volumes of resulting copy
> jobs), it could be interesting to not replicate the original backup jobs
> into your catalog on site2. This way bacula will promote the copy jobs to
> "normal" backup jobs. And you will not have backup jobs in your catalog for
> which you do not have the corresponding volumes. Before starting the use of
> Bacula from site2 you could simply delete from catalog in site2 all your
> jobs Type=F,D,I and all the copy jobs should be promoted to normal backup
> jobs.
>
>
I thought something like:
in site 2 have all the copy Job (incr. and diff) and create every month a
VirtualFull, so I don't need to use the site1 to restore a machine.
I have only to try!!
CIAO
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
