Next, you want to get a feel for your recovery time objectives, or how long your applications can be offline without impacting critical business processes. Typical times are usually measured anywhere from a few minutes to an hour or more. Obviously, the less demanding an application recovery time is, the more suited it is for a virtualized DR solution. This is because there will be a few moments when a failover from one VM to another takes place, and because a virtualized DR solution usually doesn't maintain the memory state of the failed machine, unlike most clustered solutions. So virtualized database server might not be a good candidate here, but a virtualized Web server could be a better bet.
Once these are taken care of, you begin the Site Recovery setup process, using a series of graphical-based wizards that will take you through the various steps involved to create a plan, add the remote site, link the local and remote storage pools together, and test to make sure the plan actually does work. Site Recovery will automatically make periodic disk snapshots of the protected VM.