What should you pay attention to when backing up your website?

Have you noticed that all PHP open source content management systems are the same:
1. They are all written in PHP programs, and the data are stored in the mysql database. LAMP is the best deployment environment.
2. The core programs of its website are relatively fixed, such as joomla!, dedecms, phpwind, ecshop and other core programs. Even if the program version numbers are inconsistent, the official provides a perfect upgrade solution.
3. The template of the website is independent, and users can make their own satisfactory template according to their own preferences.
4. When the phpcms system does website migration, the principles are the same, but the methods are slightly different. If you have not made major modifications to the core program of the website, you can directly install a new content management system (CMS) on the new PHP space, then restore the mysql database, restore the website template file, and regenerate the files. These are all for website migration. Approximate steps.
5. Since it is open source, users can easily complete the secondary development of the content management system (CMS) according to the official help manual.
Based on the same points analyzed above, when we are doing website data backup work, should we distinguish based on the characteristics of the PHP open source content management system, which data is important and needs to be backed up first, and which data is secondary and can be backed up later? . Avoid doing unprioritized work and only discovering that the required data is not fully backed up when a disaster occurs. Wouldn't it be tragic if such an incident happened? Therefore, we analyzed the excellent open source content management systems on the Internet and summarized a set of more scientific website data backup methods to allow users to distinguish between priorities and backup the best.
1. What data is the most important?
In my opinion, MYSQL data is the most important and should be backed up (in multiple ways) first. The MYSQL database is a unique and non-renewable resource. MySQL data stores the content of the entire website. It is the result of the hard work of the webmaster and accumulated over many years. If it is thrown away (or damaged), you have to start all over again. If the rest of the website templates and website core programs are lost (or damaged), you can pay for it and rebuild it as it was. However, if the website MySQL database is lost, can you buy it back with money? You can't, so mySQL data is the most important. .
2. Back up website data in a scientific way
First understand the characteristics of your own open source CMS system, and then formulate a scientific and reasonable backup plan to complete the backup work efficiently. The best backup solution for Hong Kong/US PHP virtual hosting is:
A. Prioritize backing up the mysql database. Multiple backup methods for the mysql database are introduced on the multi-backup forum. Users can refer to Imperial Backup King's website migration guide and mysql database backup solutions for each PHP application to obtain help information.
B. Back up the website template. This is something that has been spent hard work and money on. It is the "face" of the website. It is very important and ranks second. If you suddenly forget in which directory the website template file is stored, you can go to the official website of the open source system and check the help manual to find it easily.
C. If the website has undergone secondary development (or the core program has been modified), then please back up the files you changed.
D. When a webmaster wants to build a website, he must do SEO optimization. Please back up your optimization rules and related information (such as site keywords, website description information, etc.).
E. If your website has the pseudo-static function enabled, please back up the .htaccess file. The URL structure of the entire website depends on it. If it is lost, it will be very troublesome
F. Back up other things, such as 404 error pages, 301 jumps and other small things
3. I’m a lazy person and don’t want to take so much trouble. I can just back up the entire site directly
I also support this view, but what is the purpose of our backup? It is to give the website a "second life" after the disaster strikes and give ourselves a chance to make mistakes. The cunning rabbit still has three caves, why can't we make one more backup? What if something happens to your first backup? Are you looking forward to the sky and roaring? I am a cautious person. So I recommend a prudent solution: use multiple backups
Through the online automatic recovery and migration function of multiple backups, you only need to fill in a few simple FTP parameters to complete it automatically, which greatly saves operation time and solves problems such as recovery failures caused by technical bottlenecks. So choosing multiple backups is a wise choice! Regardless of database backup or file backup, use multiple backups!