Freelancers Network
 
skill list top cap
Homepage
Join the Freelancer's Network
Update your details
Find a freelancer
Post a project
Find a project
Projects Archive
Post a job
Find a job
Jobs Archive
See Dan's Pages
See Andy's Pages
Link to this site
Resources
Join/Leave Forum
Forum Messages
+Additions+ Adverts
Advertising
Contact Us
Subscribe to our newsletter - enter your email address and hit return
Freelancers.net is owned and operated by Andy Stowell and Dan Winchester
skill list end cap
guru web hostcom

Find me again on Freelancers.net

Re: FN-FORUM: Happy New Year, and question about backing up website data

date posted 2nd January 2007 13:09


On 2 Jan 2007, at 10:07, Duncan Glendinning wrote:

> Right, I am wondering whether there is an "easy" way to back up web
> sites' data (including possibly the MySQL as well). I have several
> sites I manage for clients, not all with the same hosting
> companies, and am trying to ut down on standard FTP-ing to back up.

Hi, Duncan

Best practice would suggest that the code and permanent templates
which drive your customers' websites should already be in a version
control system like Subversion. This (when done properly) gives you
a record of change control, versioning, and improved documentation at
the time of deployment. Backups of your customers' sites then comes
for free.....

When it comes to the MySQL data, it depends on the size of the
database. The traditional methods are :

- The command 'mysqldump' to produce a text file which can be re-
imported into a clean mysql database when you do a restore. You need
to manually record in your own documentation any of the database
system user privileges.. mysqldump can run on a remote server that is
exclusively used to back up the databases, if you have remote access
to the mysql server. However, this locks the tables that you are
dumping from so will cause a performance drop off during the backup
run, and is unsuitable for huge databases as a result (unless of
course you replicate the database to another server which is
exclusively used for backing up)

or
- Stopping the database and backing up the innodb/myisam table
space files. This is hard (but possible) to script reliably.

As I mentioned, these are traditional ways, there are 'better' ways
if you are using innodb - see InnoDB Hot Backup.

mysqlhotcopy is a more fully featured, modern way to backup the db.
http://dev.mysql.com/doc/refman/5.0/en/mysqlhotcopy.html


Replication & mysqldump works for one of my clients, but another one
with a 130GB database uses replication + OS level copy to good effect.


The MySQL 5.1 application promises a backup API which will make
things better in the long run.

As ever, this is something I can help with if your needs are complex.

-a

--
Regards, Andy Davidson
Consultant Systems and Network Engineer, Devonshire IT Limited
http://www.devonshire.it/ - 0844 704 704 7 - Sheffield, UK




Messages by Day
January 31st 2007
January 30th 2007
January 29th 2007
January 28th 2007
January 27th 2007
January 26th 2007
January 25th 2007
January 24th 2007
January 23rd 2007
January 22nd 2007
January 21st 2007
January 20th 2007
January 19th 2007
January 18th 2007
January 17th 2007
January 16th 2007
January 15th 2007
January 14th 2007
January 13th 2007
January 12th 2007
January 11th 2007
January 10th 2007
January 9th 2007
January 8th 2007
January 7th 2007
January 6th 2007
January 5th 2007
January 4th 2007
January 3rd 2007
January 2nd 2007
January 1st 2007


Messages by Month
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007


Messages by Year
2008
2007
2006
2005
2004
2003
2002
2001
2000