On Friday 2016-11-18 00:08:36 Paul J R wrote:
> I dont need a consistent full, any backup it manages to do is a plus.
> I've tried splitting it into multiple job sets but the way the dataset
> changes makes it fairly resistant cause the data changes its name as it
> gets older.
> 
> Recovering the data when it gets broken isnt difficult (the last time
> was via a windows machine connected to it with samba that got
> cryptolocker'ed), it just gets synced back across the internet (which is
> a little painful on the internet link for a couple of days). Any backup
> data I have is simply a plus that means that particular chunk of data
> doesnt have to be re-pulled. Unfortunately unless it completes a backup
> it doesnt even record what it managed to backup:
> 
> This backup had run for four hours and chewed thru quite a decent chunk
> of data, but it never recorded the files it backed up (though this was
> only a test):
> 
> +-------+-----------------------+---------------------+------+-------+--
> --------+--------------+-----------+
> | JobId | Name                  | StartTime           | Type | Level |
> 
> JobFiles | JobBytes     | JobStatus |
> +-------+-----------------------+---------------------+------+-------+--
> --------+--------------+-----------+
> | 38    | NAS02-Job             | 2016-11-15 17:33:24 | B    | F     |
> 
> 0        | 0            | A         |
> 
> Part of the reason why I was hoping to do it with bacula is it'll keep
> some of the history that gets lost when it is reconstructed from bare
> metal (which really isnt important either in reality, just handy to
> have).
> 
> One thing i did try was moving the data to be backed up out of the way,
> getting bacula to run (which completed the full backup) then moving the
> data back into place which then meant bacula did the next one as
> incremental, but that really didnt have any success either as it didnt
> complete the incremental and didnt record what it backed up.


Perhaps you could make use of LVM snapshot feature and do the consistent
backup on the snapshot.

Of course, you would need some extra space which should be calculated
from the size and the frequency of the files that get changed during the
expected snapshot life.

-- 
Josip Deanovic

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to