More and more valuable information is created and stored in digital format. At the same time, the risk of losing or ruining this data is growing. It\u2019s even painful to imagine that you can lose a web project, order information from an online store or database. The damage is huge – not only financial, but also temporary, because you have to start all over again.<\/p>\n\n\n\n
To secure against such incidents, file backup is used. In this article, we will analyze the rules that will allow you to build a simple system for copying and storing data.<\/p>\n\n\n\n
First of all, you need to understand that a copy of a file located on the same media as the original, for example, on one computer in a neighboring folder, is not a backup. In the event of a hardware failure, both files may be damaged.<\/p>\n\n\n\n
Hence the first rule<\/em> : copies must be placed on different physical media.<\/p>\n\n\n\n Hard drive or\u00a0cloud storage is\u00a0suitable\u00a0.\u00a0In the case of the cloud, you can configure automatic backup of files.\u00a0<\/p>\n\n\n\n Be sure to take into account another danger. If you store copies on different media, but geographically in one place, then the data may be lost due to some kind of cataclysm – loss, theft, accident, fire, flood, electromagnetic pulse.<\/p>\n\n\n\n Hence the second rule<\/em> : copies should be placed in different, remote from each other, places – cabinets, safes, rooms, houses, cities, countries.<\/p>\n\n\n\n It should also be noted that if the backup contains confidential data, then it must be encrypted or located on a secure medium.<\/p>\n\n\n\n It may seem that the more copies, the better. This approach is rather wasteful, because all copies need to be stored somewhere and somehow taken into account.<\/p>\n\n\n\n On the one hand, the unit cost of data storage is decreasing every year. Megabytes and gigabytes of disk space are getting cheaper. On the other hand, the storage of data on any media has its own cost, therefore it is unreasonable to duplicate and store redundant data. In addition, keeping a record of a large number of copies is troublesome, because you need to make sure that if necessary you can easily and quickly find the right one.<\/p>\n\n\n\n What is the optimal number of backups? In practice, the rule has long been established: \u201c 3\u20132\u20131<\/strong> \u201d. It means the following:<\/p>\n\n\n\n The answer to this question for each information system is individual and depends on how often changes are made to files. First of all, you need to ask yourself: for how long will data loss be critical? – and based on these numbers calculate the number of copies.<\/p>\n\n\n\n It should be borne in mind that it is risky to rely on fresh copies only, as they may contain errors that were not noticed on time. It is safer to make copies at intervals for a certain period. However, it is worth remembering that it takes time and computational resources to complete the data copying procedure, therefore it is too irrational to carry it out too often.<\/p>\n\n\n\n In most cases, archiving regular office data is sufficient once a day. If there are few workers in the office and the work is moderately intense, data can be archived less often.<\/p>\n\n\n\n The issue of copying and storing data has already been sufficiently developed, so there are various techniques that can improve the efficiency of backups.\u00a0<\/p>\n\n\n\n Copying data is not enough. You also need to make sure that the copy does not contain errors and from it, if necessary, you can easily restore the lost information.<\/p>\n\n\n\n There is no single methodology for checking the integrity of a backup, since all data is different and has its own specifics, purpose, structure, and format.<\/p>\n\n\n\n For zip or rar files, you can run the archive test procedure. Any errors will be displayed in the Diagnostic Messages window. For other files, you need to use a special utility to check the checksum and compare it with the checksum of the original file.<\/p>\n\n\n\n In order to save space on the media, the idea may arise – to delete the previous copy after each next file backup. Do not do this, as you run the risk of replacing the correct, earlier copies with copies with logical errors in the data. Practice proves that errors are not always detected quickly.<\/p>\n\n\n\n For example, if someone in the database of an online store deletes several orders or user accounts, this may appear after a few weeks. If during this time a backup copy of the database was made, and the previous one was deleted, then the original data will disappear forever.<\/p>\n\n\n\n To prevent such situations, it is customary to save not one but several last copies, for example, in one to two weeks. It is assumed that in this period, possible hidden errors should be detected.<\/p>\n\n\n\n In addition to binding to past days, the storage depth can be indicated by the number of copies themselves. For example, store the last five or seven. In this case, at the next copy, delete the oldest copy.<\/p>\n\n\n\n To quickly find and restore the desired backup, you need to keep a simple and clear account. To do this, you can apply your system for naming media, folders, files. For example, use some key name and return date:<\/p>\n\n\n\n Depending on the needs, the order in the file name may be different:<\/p>\n\n\n\n The return date is good because in the usual sorting of files and folders by name, they line up in the correct chronological order.<\/p>\n\n\n\n Physical storage media can be marked, for example, by day of the week, name or number.<\/p>\n\n\n\n Contrary to all the rules of copying and storing information, it is worthwhile to understand that even one copy is better than no copy. If you have a lot of heterogeneous data that needs to be updated regularly, then it makes sense to draw up a backup schedule – even if it is very simple – and follow it in the future.<\/p>\n","protected":false},"excerpt":{"rendered":" More and more valuable information is created and stored in digital format. At the same time, the risk of losing or ruining this data is growing. It\u2019s even painful to imagine that you can lose a web project, order information from an online store or database. The damage is huge – not only financial, but also temporary, because […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1,2],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/posts\/203"}],"collection":[{"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/comments?post=203"}],"version-history":[{"count":0,"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/posts\/203\/revisions"}],"wp:attachment":[{"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/media?parent=203"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/categories?post=203"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zeslecp.com\/blog\/wp-json\/wp\/v2\/tags?post=203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Rule 3\u20132\u20131<\/h3>\n\n\n\n
<\/h3>\n\n\n\n
How often to update backups?<\/h3>\n\n\n\n
How to verify the backup?<\/h3>\n\n\n\n
How long do backups last?<\/h3>\n\n\n\n
How not to get lost in the archive of copies?<\/h3>\n\n\n\n
What is the result<\/h3>\n\n\n\n