[Labs-l] Incremental backups or alternative

[Petr Bena]

Source code should be definitely hosted in git repositories, as for
databases, if we had some more advanced db's on labs such as postgres,
there are features like
http://www.postgresql.org/docs/9.2/static/continuous-archiving.html
which can handle this kind of problems.

On Fri, Jun 19, 2015 at 12:04 PM, Ricordisamoa
<ricordisamoa at openmailbox.org> wrote:
> Hi Marek,
>
> I'd advise using a version control system, such as Git, at least for code
> and important data that cannot be recreated from scratch.
>
>
> Il 19/06/2015 11:56, Marek Blahus ha scritto:
>>
>> Hello,
>>
>> if there are no incremental backups of our tools' code and data and no
>> plan to introduce that (?), what can I do to make sure that I won't loose
>> another ten days' worth of volunteer work next time a disk failure occurs at
>> the Labs?
>>
>> Currently, I think of scheduling a daily rsync to my computer or another
>> non-WMF server. Is that the best idea? (I am not very keen on doing that,
>> though, because I know it would make much more sense to have this solved at
>> Labs themselves.) What do you other people do to prevent data loss in
>> outages like this one?
>>
>> Marek Blahuš
>>
>> _______________________________________________
>> Labs-l mailing list
>> Labs-l at lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/labs-l
>
>
>
> _______________________________________________
> Labs-l mailing list
> Labs-l at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l