What to keep in mind for website backup

　　

Have you noticed that all of the PHP open source content management systems have the same nature:

1, are written in PHP programs, data are stored in the MySQL database, lamp is the best deployment environment.

2, the core procedures of its website are relatively fixed, such as joomla!, Dedecms, Phpwind, Ecshop and other core programs are relatively fixed, even if the program version number is inconsistent, the official also provides a perfect upgrade program.

3, the website template is independent, the user can make their own satisfaction according to their preferences template.

4, Phpcms system in the site of the migration, its principle is interlinked, but the method is slightly different. If you have not made great changes to the core program of the website, you can install the new Content Management System (CMS) directly in the newer PHP space, then restore the MySQL database, restore the site template files, and regenerate the files, these are the approximate steps of the site migration.

5, since it is open source, users can easily according to the official Help manual to complete the Content Management system (CMS) two times development.

According to the above analysis of the same point, we do the site data backup work, should be based on the characteristics of PHP open source content management system, clear those are important data, need our priority backup, those belong to secondary data, can be backed up. Avoid the cram of the work, in the event of a disaster only to find that the required data is not backed up intact. Is it a tragedy if such an event occurs? Therefore, we have analyzed the excellent open source content management system on the Internet, summed up a comparatively scientific method of data backup of the website, let the user distinguish primary and secondary, the preferred backup.

First, what data is the most important?

I think that MySQL data is the most important and should be backed up in priority (multiple methods). MySQL database is unique, is not "renewable resources", MySQL data stored in the entire site content, is the webmaster hard work, perennial accumulation of crystallization, lost (or damaged) will have to start again. The rest of the site template, the site core program is lost (or damaged) can be the original way to send money to do, but the site MySQL database lost, you can buy it back? You can't, so say, MySQL data is the most important.

Ii. scientific methods to back up website data

First understand the characteristics of their own open-source CMS system, and then develop a scientific and reasonable backup scheme, the efficient completion of the backup work. The best backup solution for Hong Kong/US PHP virtual hosting is:

A, the first backup MySQL database, on the multi-Backup forum, introduced a variety of MySQL database backup methods. Users can refer to the Empire Backup King website Migration Good helper and the MySQL database backup scheme under each PHP application to get help information.

B, back up the site template. This is to spend the effort and money of things, is the site's "face", very important, ranked second. If you forget the site template files in which directory, you can go to the official website of the open source system to check the Help manual, you can easily find.

C, if the site has been developed two times (or modified the core program), then please back up your changed files.

D, webmaster to do a site is definitely to do SEO optimization, please make your optimization rules and related information (such as site keywords, website description information, etc.) back up.

E, if your site has a pseudo-static function, please back up the. htaccess file, the URL structure of the entire site depends on it, lost will be very troublesome

F, other things backup, such as 404 error page, 301 jump and other small things back up

Third, I am lazy, do not want to be so troublesome, direct, simply to do a whole station backup not on it

I also support this view, but what is the purpose of our backup? Just after the disaster, give the website "Second Life" and give yourself a chance to make a mistake. The sly Rabbit has three caves, why can't we do a backup more? What if your first backup was an accident? I am a cautious man. I'm a shouts. So I recommend a cautious scenario: using multiple backups

Through the online automatic recovery and migration of multi-backup, only a few simple FTP parameters can be completed automatically, which greatly saves the operation time and solves the problems of recovery failure caused by technical bottleneck. So choose Multi-Backup is the wise choice! Use multiple backups, whether it's a database backup or a file backup!

What to keep in mind for website backup