[Cialug] Most reliable backup solution

[Kenneth Younger]

On that second topic, I've been working to implement GitHub's boxen
<https://boxen.github.com/>, which is basically a puppet-driven desktop
management system for OS X.

It's not kink-proof, but I think it has promise. There are others based on
Chef, too:

https://github.com/kitchenplan/kitchenplan
https://github.com/pivotal-sprout/sprout-osx-apps


On Thu, Feb 12, 2015 at 9:49 AM, Matthew Nuzum <newz at bearfruit.org> wrote:

> Yeah, that's a good idea. For me, there are two things stopping me:
>
> I think that both Chef and Puppet are boring. I try to read the docs and
> tutorials and my eyes glaze over (I'm open to suggestions that are short
> and practical).
>
> I should have mentioned in the original post that it'd be great to find
> something that scales up to the desktop as well, though I guess your
> suggestions work there too, though that takes some fun out of the Software
> Center.
>
> On Thu, Feb 12, 2015 at 9:37 AM, Kenneth Younger <kyounger at gmail.com>
> wrote:
>
> > What about building servers completely with Puppet/Chef/other CM tool? If
> > you build the scripts well enough originally, then you can generally
> remove
> > ongoing dealings with that list other than #2. Also, it can help with
> > scaling (if and when you need it). I used to think CM was just for
> > people/orgs that needed to provision 100's of servers and complex
> > infrastructure, when I started viewing it as a way to manage
> infrastructure
> > entirely with code (DRY, version control!, etc), it started to make more
> > sense even on a single server system.
> >
> > Which is why I've been studying up on Puppet recently. But I'm not saying
> > Puppet is better than Chef or any of the others, it's just what I picked,
> > and I may change in the future. (CM tool decisions are the new vi/emacs
> > flame wars topics it seems...)
> >
> >
> > On Thu, Feb 12, 2015 at 9:24 AM, Matthew Nuzum <newz at bearfruit.org>
> wrote:
> >
> > > Most of the backup solutions I've used involved rsync and a remote file
> > > store. The restore process looks like this:
> > >
> > >   1a. Install OS and updates
> > >   1b. Install required packages (hopefully I get them all)
> > >   1c. Configure software (by restoring /etc)
> > >   2. Restore data
> > >   3. Restart services and we're live
> > >
> > > The effort to do steps 1a - 1c are pretty laborious. In the case of a
> web
> > > server, it takes far longer than restoring the data.
> > >
> > > I've used time-machine for Mac OS and it works pretty slick. If you
> > > experience a failure or data loss, you boot off of the installation
> > media,
> > > at the installation screen choose to restore from backup, choose the
> > backup
> > > location and it restores the OS, the Apps and your data in one swoop.
> > >
> > > I was wondering last night if there is a better way to do my server
> > backup
> > > than what I'm using. I know about CrashPlan, but essentially, it is
> still
> > > going to be the same steps above, if I understand correctly.
> > >
> > > --
> > > Matthew Nuzum
> > > newz2000 on freenode, skype, linkedin and twitter
> > >
> > > ♫ You're never fully dressed without a smile! ♫
> > > _______________________________________________
> > > Cialug mailing list
> > > Cialug at cialug.org
> > > http://cialug.org/mailman/listinfo/cialug
> > >
> > > --
> > > Kenneth Younger III
> > > Founder, Sheer Focus Inc.
> > > e: kenny at sheerfocus.com
> > > p: (515) 367-0001
> > > t: @kenny <http://twitter.com/kenny>
> > >  <http://cialug.org/mailman/listinfo/cialug>
> > >
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > http://cialug.org/mailman/listinfo/cialug
> >
>
>
>
> --
> Matthew Nuzum
> newz2000 on freenode, skype, linkedin and twitter
>
> ♫ You're never fully dressed without a smile! ♫
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>
> --
> Kenneth Younger III
> Founder, Sheer Focus Inc.
> e: kenny at sheerfocus.com
> p: (515) 367-0001
> t: @kenny <http://twitter.com/kenny>
>  <http://cialug.org/mailman/listinfo/cialug>
>