-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
To do a VirtualFull you do need to have all backups since the last Full
or VirtualFull available.
I recommend against production use of SQLite, unless you have less than
10 machines.
Normally there is no reason why an instance of MySQL/PostgreSQL cannot
be put in a VM that is running Bacula -- I do that all the time.
Best regards,
Kern
On 06/08/2014 11:04 AM, Steven Haigh wrote:
> Hi all,
>
> The one thing I can see tripping me up is that from what I understand,
> for a VirtualFull I will need access to ALL jobs since the last
> VirtualFull. In the case of a removable eSATA drive that won't be online
> all the time, I can't guarantee that access will be available to that
drive.
>
> At this stage, I have been using SQLite - simply to keep the entire
> system contained. I do have a MySQL server available - but the idea is
> to keep the backup system contained to a single VM.
>
> The ponderings of which direction to go is difficult :)
>
> On 08/06/14 18:31, Kern Sibbald wrote:
>>
>> Hello,
>>
>> I cannot help you with your overall design because I am more effective
>> writing new code than helping with implementations (very important).
>> However a couple of points, which are my personal opinions:
>>
>> 1. Your setup is medium size and would work fine with MySQL, but if you
>> can accept a short term learning curve and would like long term peace of
>> mind, I would use PostgreSQL to avoid performance problems later. It is
>> harder to setup correctly and tune in the beginning (performance is
>> pretty bad with the out of the box PostgreSQL configuration, but
>> longterm it performs in big installations *much* better than MySQL.
>>
>> 2. You need to carefully setup incrementals forever, but Bacula has
>> supported that feature from the beginning and if you take the time to
>> understand and use Virtual Full jobs and accurate backups (at least once
>> a week), Incrementals forever can be much more efficient compared to
>> normal backups. If you don't use accurate mode (at least occasionally)
>> and VirtualFulls, stay away from incrementals forever.
>>
>> 3. I also recommend using the Bacula "virtual" autochanger for disk
>> based systems. It is very robust and simple, but there is not a lot of
>> documentation on it.
>>
>> Best regards,
>> Kern
>>
>> On 06/08/2014 05:00 AM, Steven Haigh wrote:
>>> Hi guys,
>>
>>> So I'm starting from scratch again with my bacula config. I thought I'd
>>> try to get some pointers before I dive in head first again.
>>
>>> My setup consists of multiple virtual machines. Some over GigE, some
>>> over an ADSL connection (6000/800kbit). My aim is to transfer as little
>>> as possible over the ADSL connection - but enough to be able to restore
>>> if required.
>>
>>> I would like to use some local disk storage (say 40Gb), and have the
>>> rest go to a removable external eSATA drive. I'm thinking this could
>>> mainly be done via job migration when the internal storage starts to get
>>> full.
>>
>>> As some insight, my current setup has ~167 daily incremental backups and
>>> has used under 11Gb of space on the 'on disk' volumes. The amount of
>>> data changed per day isn't really huge.
>>
>>> Some more specific questions:
>>> 1) I want to try and avoid vchanger and use something that can use the
>>> eSATA drive properly - grow the number of volumes automatically to fill
>>> the entire eSATA drive. Bonus points for being able to just plug in a
>>> new eSATA drive and expand further.
>>
>>> 2) From my previous posts, I heard that daily incrementals forever may
>>> be a bad idea - the whole job based backup vs the file based backup that
>>> I'm used to with TSM. What would be the suggested route for backups
>>> being done? I obviously don't want to do Full backups over the ADSL
>>> connection every week / month.
>>
>>> 3) I'm starting from scratch with Bacula v7 and all systems are a
>>> mixture of RHEL6 and Fedora 20. Are there any gotchas I should be aware
>>> of straight up?
>>
>>> 4) Any general comments? :)
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlOULbQACgkQNgfoSvWqwEgggACePHxoe1dEW4tJCrpL0Eaqdi0s
oPIAn2nJTmtdm1DiryR/AGFe4gAK3RXM
=B64r
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
