Set Up Backup

[samking]

Back up both the drupal install and the databases

[supermari0]

Prioritizing this after sitemap since we don't want the site to go kaboom. Would you be OK with me just downloading the whole site, encrypting it, and keeping it on my laptop and external hard drive? My laptop HD is also encrypted (although it's breakable -- Apple encryption sucks), so it should be pretty secure here.

[samking]

We don't have any private user data on the site, so that shouldn't be a problem.

I think that Andrew might also have been working on backup (as a part of working on creating a dev site) at the Code Jam. I think he put some notes in the CtC Website Google Docs folder at https://docs.google.com/document/d/1t63RI0yrd4sGxoEEzIf-AsEpjOUthYG3ux36mmYIqsk/edit.

There are two needs here:

1. Setup version control locally (local meaning on the server) so that we can see the development of the site and database over time in case we break something and want to revert it
2. Have a copy of everything (at a minimum, the most recent version of the site; ideally, the version control also in case we want to revert) offsite (ie, Google Drive or something) so that a server crash won't make the site go kaboom.

Addressing those two backup needs would also make running the dev site easier because we would have an easy way to pull a copy of the database to the dev site.

[supermari0]

SGTM. Here's the order I'll do things in since I have limited time:

1. Look at what Andrew has done and adjust below accordingly.
2. Try to set up version control (git). If it's too complicated because of the way Drupal does databases, I'll move that to later.
3. Clone or zip up site depending on whether (1) was successful within a timespan of about 2 hours.
4. Download/backup to hard drive.

I am guessing that it will not be a problem, but is there a specific time you would want me to do step 3? I don't want to hog bandwidth if we're near a limit or something.

On Wed, Jul 4, 2012 at 4:00 PM, samking < reply@reply.github.com

wrote:

We don't have any private user data on the site, so that shouldn't be a problem.

I think that Andrew might also have been working on backup (as a part of working on creating a dev site) at the Code Jam. I think he put some notes in the CtC Website Google Docs folder at https://docs.google.com/document/d/1t63RI0yrd4sGxoEEzIf-AsEpjOUthYG3ux36mmYIqsk/edit .

There are two needs here:

1. Setup version control locally (local meaning on the server) so that we can see the development of the site and database over time in case we break something and want to revert it
2. Have a copy of everything (at a minimum, the most recent version of the site; ideally, the version control also in case we want to revert) offsite (ie, Google Drive or something) so that a server crash won't make the site go kaboom.

Addressing those two backup needs would also make running the dev site easier because we would have an easy way to pull a copy of the database to the dev site.

---

Reply to this email directly or view it on GitHub: https://github.com/samking/Code-the-Change/issues/12#issuecomment-6769125

[samking]

Gandi.net is nice about our server utilization. I think we're using far less bandwidth than we're allotted and that they will give us more if we ask.

[supermari0]

Ack

On Wed, Jul 4, 2012 at 4:41 PM, samking < reply@reply.github.com

wrote:

Gandi.net is nice about our server utilization. I think we're using far less bandwidth than we're allotted and that they will give us more if we ask.

---

Reply to this email directly or view it on GitHub: https://github.com/samking/Code-the-Change/issues/12#issuecomment-6769438

[samking]

Ack?

[supermari0]

Acknowledged

Sent from my iPhone

On Jul 5, 2012, at 6:40 AM, samkingreply@reply.github.com wrote:

Ack?

---

Reply to this email directly or view it on GitHub: https://github.com/samking/Code-the-Change/issues/12#issuecomment-6778886

[samking]

Clearly, you have been dealing with too many networks. Fin.

[samking]

Backs up to dropbox.