Re: [PLUG] 3-way data mirror?

[Lee Marzke <lee@marzke.net>]

If you don't track who made changes this seems like a disaster waiting
to happen,  so I also think a central CM repository is the way to go,  
so that
everyone can see who and why the change was make.

This requires the discipline to check out files before they are written.

This would certainly work well with the smaller files,  but for the 
large binaries one
improvement ( with Perforce at least ) is that each local site could run 
a cache
server that pulls changes across on a schedule,  so that many of the 
binaries
could be synced locally prior to someone needing them.

Perforce isn't in the repos, but a single 'p4d' executable is all that 
is required
on the colo side,  and of course you can tunnel the traffic with ssh.   
Conceivably
each site could be a single "user",  so the free product may work for 
you as well.

See my time-unlimited demo on VMTN: ( 2 users, 5 workspaces free )
http://www.vmware.com/appliances/directory/222433

Lee



On 12/12/2010 11:51 AM, Gavin W. Burris wrote:
> I would consider using revision control, like SVN, if your data files
> aren't too large, especially if the raw data doesn't change much.  The
> problem is that changes in binary files do not benefit from diffs, with
> each change requiring a complete upload/sync of the file.
> http://subversion.apache.org/
>
> Another option that would apply to future, more data intensive
> collaboration, would be iRODS.  This is a more comprehensive solution
> that builds a "data grid" for distributed projects.
> https://www.irods.org/index.php/What_is_iRODS%3F
>
> Cheers.
>
>
> On 12/12/2010 12:52 AM, JP Vossen wrote:
>    
> > I have a situation where I have 2 labs that need to keep ~150G of data
> > in sync, but they can't talk to each other.  They can talk to a 3rd
> > machine, which is also backed up, so...
> >
> > What I think I'd like to do is have:
> >
> >      Lab1<-->  COLO<-->  Lab2
> >
> > The problem is that lab1 and lab2 are both read-write, so there is a
> > real possibility of stepping on changes.  COLO is read-only.
> >
> > I'd try to just relay through the COLO, but that's also where the backup
> > will happen.  And I can't get the FW rules changed.
> >
> > Any better ideas?
> >
> > Any suggestions on tools?  I'd strongly prefer something already in the
> > CentOS-5 or EPEL repos.
> >
> > Thanks,
> > JP
> > ----------------------------|:::======|-------------------------------
> > JP Vossen, CISSP            |:::======|      http://bashcookbook.com/
> > My Account, My Opinions     |=========|      http://www.jpsdomain.org/
> > ----------------------------|=========|-------------------------------
> > "Microsoft Tax" = the additional hardware&  yearly fees for the add-on
> > software required to protect Windows from its own poorly designed and
> > implemented self, while the overhead incidentally flattens Moore's Law.
> > ___________________________________________________________________________
> > Philadelphia Linux Users Group         --        http://www.phillylinux.org
> > Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug
> >
> >      
>    


--
"Between subtle shading and the absence of light lies the nuance of iqlusion..."  - Kryptos

Lee Marzke,     lee@marzke.net                              http://marzke.net/lee/
IT Consultant, Global App Development, Software CM, VMware, VSphere, NetApp storage
voice: +1 484-961-0369     +1 800 393 5217                     sip://lee@4aero.com
fax:  +1 484-348-2230


begin:vcard
fn:Lee Marzke
n:Marzke;Lee
org:4AERO
adr:;;;Collegeville;PA;19426;US
email;internet:lee@marzke.net
title:Consultant
tel;work:800 393 5217
tel;fax:+1 484 348-2230
tel;cell:+1 484 961-0369
x-mozilla-html:TRUE
url:http://4aero.com
version:2.1
end:vcard

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug