These are standard procedures and not really much to do with Sage.  For the database then it's down to your MSSQL backup strategy and transaction logging.   If it's full server "image" you want, then that's VM snapshots or whatever system you prefer.

Thanks Stephen, just wondering if anyone in the community has or knows of any successful implementation  of Sage across two databases for redundancy. Given that it is not documented or supported by Sage and SQL + snapshots are tricky, i was just curious if anyone in the community has had success before I go down that road.

Thanks Stephen, just wondering if anyone in the community has or knows of any successful implementation  of Sage across two databases for redundancy. Given that it is not documented or supported by Sage and SQL + snapshots are tricky, i was just curious if anyone in the community has had success before I go down that road.

We tell all our clients it's not worth the trouble.  Even our largest clients with hundreds of users and full-time IT staff go with nightly backups.

thank you for the honest response!