[Gluster-infra] Backup strategy for our infrastructure?

[Louis Zuckerman]

IMHO we should start with whatever backups the rackspace cloud platform
provides.  It would be nice to also have off-rackspace backups, but I dont
know how/where we could store them.

Rackspace has two options that look good to me.  Simplest is scheduled
server images.  These are whole-server snapshots, which should be easiest
to restore just by launching a new server from an image.  Rackspace does
not recommend this as a complete backup strategy but I think it would be
sufficient for starters.  It's definitely the easiest to set up.

Next would be Rackspace's backup service, which requires installing the
backup agent daemon -- a simple package install followed by setting a
username & API key.  I don't know how restores work with this option, but I
will try it soon & follow up with more info.

Read more about the differences between these options here:
http://www.rackspace.com/knowledge_center/article/rackspace-cloud-backup-vs-cloud-server-image-backups

In order to "kick the tires" on these two alternatives, I have set them
both up on my SonarQube server, the one called gluster-sonar in the RS
control panel.  I'll check back after a few days to see how the backups are
going, and test a restore from both services to compare.

Can anyone suggest an off-rackspace backup solution we could use in
addition to these services?

All the best,

-louis



On Tue, Aug 19, 2014 at 5:21 PM, Michael Scherer <mscherer at redhat.com>
wrote:

> Le mardi 19 août 2014 à 22:19 +0100, Justin Clift a écrit :
> > On 13/08/2014, at 10:01 PM, Justin Clift wrote:
> > <snip>
> > > These pieces spring to mind immediately:
> > >
> > > * Gluster Forge (repo data + all Gitorious config)
> > >
> > >   Unless we're sure Gitorious AS is backing it up well enough.
> > >
> > > * Gluster Wiki
> > >
> > > * Jenkins (configuration, and all of the build artifacts)
> > >
> > >   The user list + authentication for Jenkins is its hosts /etc/passwd
> > >   file, so backing up the auth info for the local box will capture
> > >   that ok.
> > >
> > > * Gerrit
> > >
> > > * Our Mailman mailing lists (config and data)
> >
> >
> > * The www.gluster.org apache and varnish configuration
> >
> > * The download.gluster.org website (no idea which) configuration
>
> IMNSHO, configuration should not need to be backed up by using a
> configuration management system. But that's only if we decide to use
> one.
> --
> Michael Scherer
> Open Source and Standards, Sysadmin
>
> _______________________________________________
> Gluster-infra mailing list
> Gluster-infra at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-infra
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-infra/attachments/20140820/f18a2d1e/attachment-0001.html>