[rear-users] Recovery of Datebases

[Cal Sawyer]

Agreed.  This is a mandatory 2-step DR process.  What's more, if you're 
in a league of operations where you need db replication or if your dbs 
are mission-critical (whatever that might mean to you), surely your 
databases live on a separate disk/disk partition - because they should.  
You can easily exclude a dbdata-related partition in the rear 
configuration.  There's no point in hot rear-ing databases that are 
being even moderately used - when you come back to restoring your month 
(or year or minutes) old image, any db data you preserved in the rear 
archive will be hopelessly/uselessly out of date anyhow.

At the very least, stop/quiesce your database server before pulling a 
rear archive if you're intending to restore to a new system immediately. 
afterwards.

- cal

  On 18/07/13 11:01, danny.petterson at accenture.com wrote:
> Hi again,
>
> Sounds to me you need MySQL replication (master/slave) running regardless of ReaR backup. A restore, using any backup/restore framework will have the issue your talk about, and can only be solved by some kind of live replication....
> Greetings from
>   
> Danny Petterson
>   
>
> "Shadows and Dust"
>
> R.I.P. Jeff Hanneman 1964-2013
>
> -----Original Message-----
> From: rear-users-bounces at lists.relax-and-recover.org [mailto:rear-users-bounces at lists.relax-and-recover.org] On Behalf Of Rudolf Bastiansen
> Sent: 18. juli 2013 11:13
> To: Relax-and-Recover users list
> Subject: Re: [rear-users] Recovery of Datebases
>
> Hi,
>
> but when I make a dump I will get also an inconsistency because I have only current state of the DB. I need something like a DB-Replication with rear.
> Is that possible?
>
> Thanks again. :)
>
> ----- Ursprüngliche Mail -----
> Von: "danny petterson" <danny.petterson at accenture.com>
> An: rear-users at lists.relax-and-recover.org
> CC: rear-users at lists.relax-and-recover.org
> Gesendet: Donnerstag, 18. Juli 2013 10:12:50
> Betreff: Re: [rear-users] Recovery of Datebases
>
> Hi,
>
> Wouldn't the simplest way just be to do a mysqldump just before the rearbackup?
>
> Kind regards
> Danny Petterson
>
>  From Mobile device
>
> On 18/07/2013, at 09.46, "Rudolf Bastiansen" <rbastiansen at tng.de> wrote:
>
>> Hello,
>>
>> I have a question! ;)
>>
>> When I want to recover e.g. a MySQL-Database I could only recover the current state of the DB. The problem is that I could get some serious troubles.
>> The DB could be inconsistent after a succesful recovery when other systems want to write or read data in or from the DB.
>>
>> Does rear support any "sync"-feature or an "lifetime"-dump so that I could my DB up to date?
>>
>> Thanks! :-D
>> _______________________________________________
>> rear-users mailing list
>> rear-users at lists.relax-and-recover.org
>> http://pikachu.3ti.be/mailman/listinfo/rear-users
>>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.
>
> Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
> _______________________________________________
> rear-users mailing list
> rear-users at lists.relax-and-recover.org
> http://pikachu.3ti.be/mailman/listinfo/rear-users
>
> --
> --
> i.A. Rudolf Bastiansen, Fachinformatiker TNG Stadtnetz GmbH, Helpdesk Projensdorfer Str. 324, D-24106 Kiel, Germany
> phone: +49 431 7097-50, fax: +49 431 7097-555 mailto:rbastiansen at tng.de http://www.tng.de
> -
> Register: Amtsgericht Kiel HRB 6002 KI
> Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg, Dr. Thomas Rohwer, Sven Schade, Dr. Sven Willert Tax-Id (Steuernr.): 1929112637, VAT-Id (USt-Id): DE225201428
>
>
> -
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in
> error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> _______________________________________________
> rear-users mailing list
> rear-users at lists.relax-and-recover.org
> http://pikachu.3ti.be/mailman/listinfo/rear-users
> _______________________________________________
> rear-users mailing list
> rear-users at lists.relax-and-recover.org
> http://pikachu.3ti.be/mailman/listinfo/rear-users