The data should be "the same" as on my machine, that I can dismiss my server and point to new machine in the end.
Based on your comments, your best option would be Database Mirroring or Log shipping.
You have to evaluate your RPO and RTO. Since you are using VPN to your actual machine - meaning it is point-to-point connection :
If you go with Database Mirroringgo with Database Mirroring :
You have to use Asynchronous mode. Also, if you are not running in the same Active Directory, you’ll also need to factor in the time to re-create and tie out the accounts when calculating the RTO value.
RPO: As of last good synchronization
RTO: (Time of failure + Time of client redirect to New System ) - Time of last good synchronization
If you go with Log Shipping (min will be 1 min)go with Log Shipping (min will be 1 min) :
Because the log file is copied to a Windows share, this solution requires both networking access and an Active Directory integration.
RPO: As of last good log backup application to the secondary system.
RTO: (Time of failure + Time of client redirect to New System ) - Time of last good synchronization
Refer to this excellent article by Buck Woody : Microsoft Windows Azure Disaster Recovery Options for On-Premises SQL ServerMicrosoft Windows Azure Disaster Recovery Options for On-Premises SQL Server
