How to choose a backup strategy and software to quickly put the server into operation after a failure?

There is a server with an ESXi hypervisor on which there are several virtual machines, everything is located on a RAID10 disk array (I cite this information in order to suddenly have some advice that can take these features into account)

Virtual machines (Debian 8) perform the functions of a proxy server, a mail server, and a web server.

The web server contains sites and file storage.

As I understand it, you should first of all pay attention to the database, the list of installed packages (so as not to remember what was on the new server), configuration files. What else?

Does it make sense to use programs like Acronis to copy the entire raid? For example, on a laptop, I periodically start disk mirroring and, in the event of a failure, I have a whole system with all the contents.

Please give advice.

  • one
    But where exactly do you want to save all this? and you do not want to consider the option of using Infrastructure as Code? - Mikhail Vaysman
  • @MikhailVaysman keep vslsle keep backup? hard drives are no problem - while1pass
  • one
    +1, you need chef rather than image backup - etki
  • 2
    Roughly speaking, yes. In general, there is the "big four" CM - chef, ansible, puppet, saltstack - but in my personal opinion, you can only use it from the first. - etki
  • one
    @ while1pass backups should not be found in the same room (building, country, planet :) - it is dependent on the desired reliability) as the original data. otherwise, it is easier to add disks to an existing RAID or add another RAID. chef - great. as well as other named means. - Mikhail Vaysman

0