Last update: 26 of April of 2020
Table of contents
When we have already a site in operation does not finish the work of the hosting. The machines can fail, and fail, reason why we have to have methods to verify that it is working in addition to a backup copy system.
WordPress does not incorporate by defect any type of automatic backup copy system, reason why you have to depend on a tool of third parties for it.
At the time of realising a backup copy you have to have present that WordPress is compound of two completely differentiated elements: the files and the data. The part of files is stored in your servant, and FTP or any other method can be acceded by, and the data are stored in the data base. This means that at the time of making a backup copy you have to do it of the two parts, since one does not work without the other.
Where to make copies
At the time of making backup copies there are many methods for it. First she is the one of the own servant of the hosting. Normally the own suppliers offer the possibility of making a copy of all the contents lodged in the machine. Generally these copies are realised externally in a specific backup copy servant. In this case you must know his operation the hour as much to see how and when they are realised, as the form to recover the copy, if it can be partial, total, and if you have access to the data of a simple form.
One second form is manual, through operating system, so that I mount a system to you that makes a copy of all the files (for example in a ZIP) and on the other hand to make dump of the data base to obtain a copy of file SQL with all the data.
In order to finish, and most habitual (in addition to which the supplier can provide us) is to have plugin of backup copies. Plugins are many and generally we recommended you that you prove several until DES with which adapts to your needs. He is not the same to make a backup copy of a small site (200 Megabyte) that to do one great one (5 GB). The yield and response times of the servant could cause that the system is saturated and the copies are not realised, reason why we recommended to you that you prove the different systems until finding with which works better.
In addition, also it is important that when you make backup copies they are stored in at least two different places. One usually is the own servant where it is the website. Sometimes the site corrupts but it does not affect to the machine, reason why to have the files of form near and to fast disposition usually is helpful. The other case is the one to have them outside the servant, in an external place, and even outside the same network or supplier or country. The fact that it is in another different place would allow that although that supplier had a serious problem (and for example you would not have possibility of acceding to him) you could recover your site from an external place.
When to make copies
Copies you can do all that you want, although with moderation, as everything. Generally it will depend on how many changes you do in your website and with how much frequency to determine how many data you are arranged to lose in an extreme case.
For example, if you have a site in which you publish a content every week, and your visitors are publishing some commentaries, probably a daily backup copy is sufficient.
However, if for example you are mass media that publish a hundred of articles of daily form and are much interaction, most probable is than you want to do a copy every few hours.
In any case, the recommendable thing is at least to have a daily copy during one week, and later to store a weekly copy at least during a few months. This form you would make sure to have copies that go back between 3 and 6 months. Once again, it will depend on the size and configuration of your site.
To have monitoring tools is going to allow you to verify if the site works correctly, at many different levels.
One of the basic systems of monitoring is the one of knowledge that is active the site, in addition to small elements of speed of load or response times. Habitually external services of ping are used that with certain frequency calls to your website and verifies that it works and it is in line, and if the access is fast or slow. In case there is some problem, usually it sends some type of warning as a alert.
In addition, these services usually have some panels in whom to be able to analyze of historical form those times and possible falls of the service.
Generally the measurement of these data usually becomes of internal form since they affect mainly to the services that have the machine. So that a WordPress works at least we needed the servant with his operating system, the Web server, the PHP and the data base. In addition, we can have the systems of cache storage. Then the system of yield monitoring which analyzes is all this.
For example, some habitual data of the servant and operating system are the load of CPU and memory, the consumed bandwidth or the space and yield of the storage, in the part of the Web server the amount of requests and valid answers and you invalidate that they are given back, in the PHP the consumption of memory and execution and in the data base the size, the amount of consultations and those that are slow.