If you are using virtual machines, you can copy the whole server. If not you could try with SQL Server Always ON tech to get a secondary replica. If you're using a SQL Server Std edition, secondary replica will be read-only. Due the SQL Server connection string has been hard-codified on X3 parameters, you cannot take advantage of  file-over technologies, but at least you have a duplicate of your SQL Server.

I'm using a 3rd party tool that allows me to run a replica of my servers in case of disaster.

Hi all, 

I'm agree with MCnets is the faster way, because if not you will need to do DB replications and File sytems replications, this will involve DB and SO license extra cost. 

But if your customer is looking for High Availability, then is better other options.

Regards,

Thanks, Mcnets Considering the 3rd party tool you use, can you pls share documentation to that so I can read

It's Veeam Backup & replication

You can read about it here

Thanks Mcnets