<div dir="ltr">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.<div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Read more about the differences between these options here: <a href="http://www.rackspace.com/knowledge_center/article/rackspace-cloud-backup-vs-cloud-server-image-backups">http://www.rackspace.com/knowledge_center/article/rackspace-cloud-backup-vs-cloud-server-image-backups</a></div>
<div><br></div><div>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.</div>
<div><br></div><div>Can anyone suggest an off-rackspace backup solution we could use in addition to these services?</div><div><br></div><div>All the best,</div><div><br></div><div>-louis</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Aug 19, 2014 at 5:21 PM, Michael Scherer <span dir="ltr"><<a href="mailto:mscherer@redhat.com" target="_blank">mscherer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le mardi 19 août 2014 à 22:19 +0100, Justin Clift a écrit :<br>
<div class="">> On 13/08/2014, at 10:01 PM, Justin Clift wrote:<br>
> <snip><br>
> > These pieces spring to mind immediately:<br>
> ><br>
> > * Gluster Forge (repo data + all Gitorious config)<br>
> ><br>
> > Unless we're sure Gitorious AS is backing it up well enough.<br>
> ><br>
> > * Gluster Wiki<br>
> ><br>
> > * Jenkins (configuration, and all of the build artifacts)<br>
> ><br>
> > The user list + authentication for Jenkins is its hosts /etc/passwd<br>
> > file, so backing up the auth info for the local box will capture<br>
> > that ok.<br>
> ><br>
> > * Gerrit<br>
> ><br>
> > * Our Mailman mailing lists (config and data)<br>
><br>
><br>
> * The <a href="http://www.gluster.org" target="_blank">www.gluster.org</a> apache and varnish configuration<br>
><br>
> * The <a href="http://download.gluster.org" target="_blank">download.gluster.org</a> website (no idea which) configuration<br>
<br>
</div>IMNSHO, configuration should not need to be backed up by using a<br>
configuration management system. But that's only if we decide to use<br>
one.<br>
<div class="HOEnZb"><div class="h5">--<br>
Michael Scherer<br>
Open Source and Standards, Sysadmin<br>
</div></div><br>_______________________________________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org">Gluster-infra@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-infra" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-infra</a><br>
<br></blockquote></div><br></div>