Backup Strategy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I think the answer to that problem is to back up from a machine that has the native Gluster client mount the data that needs to be backed up - that way you don't have to worry about replicas and attributes.

Of course this seems to indicate that you would need to restore the same way ... but I'm not positive about that.

James Burnash, Unix Engineering

-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Mohit Anchlia
Sent: Wednesday, March 09, 2011 1:39 PM
To: Sabuj Pattanayek; gluster-users at gluster.org
Subject: Re: Backup Strategy

One confusion I have is when maintaining multiple bricks on multiple
physical volume and a replica also how do we do effective backups?

So if I have 4 node glusterfs cluster and replica of 2 then how do I
effectively do the backups such that I don't backup multiple copies or
overwrite files when doing backups.

On Wed, Mar 9, 2011 at 10:34 AM, Sabuj Pattanayek <sabujp at gmail.com> wrote:
> If you want to do backup to disk then I highly recommend backuppc .
>
> On Wed, Mar 9, 2011 at 12:16 PM, Mohit Anchlia <mohitanchlia at gmail.com> wrote:
>> I would like to hear from experienced users of glusterFS about how
>> they are currently doing backups. I am looking at solutions but not
>> sure which one to use and how to effectively use them. First thing
>> comes to my mind is using rsync.
>>
>> Please advice.
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users


DISCLAIMER: 
This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. 
NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux