Is it worth making a site mirror for the following purposes?

Question

Backup

Good afternoon, there is a site that was hacked and everything on it was deleted. Restored from a backup, which took some time. The authorities want to make a mirror of the site and redirect to it if the main site is unavailable/broken/empty for some reason. How reasonable is such a decision? The fact is that the site is updated almost every day, and accordingly, you will have to manually update this mirror as well. Hypothetically, you can make the mirror automatically update from backups of the main site, but then there is a risk that at some point a backup with a broken site will be created and uploaded to the mirror, as a result, both sites will still not work. That is why, it seems to me, updating the mirror is only possible manually. And since it involves the human factor, then this is a bad idea, because. may, for example, forget to update this spare site. And over time, completely forget about it, because. Affairs usually and so on throat.
The site is flooded with advertising in Yandex and Google, about 1000 visitors a day, and it is extremely important that the site works stably. It seems to me that there are some other ways to ensure its safety and reliability, and I will once again share, at least in general terms, which way to look and what steps to take to secure the site?

Answer 1

The solution is not entirely reasonable, because both the main site and the mirror can potentially be hacked. Firstly, it would be good to figure out how the site was hacked, what is the reason and what can be learned from it.
If the problem is in web security due to self-written code: do an audit, fix holes, scan (acunetix/metascan/detectify). Install WAF if there are no resources to fix it.
If they penetrated through something else (for example, forgotten ports on a VPS), then close them from everyone using a CDN. As a last resort, move to another hosting.
And if you raise a copy, then it is so that the redirect to it occurs imperceptibly for the user, through the balancer. For example, this scheme:
Cloudflare -> Balancer -> Site 1, Site 2
At the same time, it is better not to store anything sensitive on the balancer, including access to sites and backups. It is better to do them on a separate server.