Have you looked at this yet?
I use this to run an hourly backup of all data and and support files, then transmit them to both a second “hot spare” host and a storage host to keep multiple backups.
As for the rest of the server, I use a service that allows me to keep an image backup of a functioning server on hand. In the event of a disaster, I can open a ticket to have them restore the image to another server instance. Then I just restore one of my hourly data backups to be back online.
During the down time I just have the client switch their logins to the hot spare host until the primary host is rebuilt on new hardware.
So for example, if I have a primary host called myerpsystem.com then I would have a duplicate of that running all the time called backup.myerpsystem.com that the users can log into in the event of a major disaster. The hot spare is never more than an hour behind.
Maybe you can do something similar.
BKM