This article offers insight into determining an acceptable timeframe for hosting virtualizations on a Datto appliance and planning for recovery.
A proper amount of urgency in redeploying production resources is critical to a smooth transition between failover and complete recovery.
Recovery and planning
The most common reason for spinning up a local virtualization on a Datto device is to achieve the lowest possible amount of downtime for critical resources in the event of a production server failure.
In some disaster recovery scenarios, a client may request to keep a server virtualized on the Datto for an extended period of time due to required approvals from onsite IT staff, hardware shipments, SLAs, or scheduling conflicts.
However, continuing to host a production server on a Datto outside of circumstances pertaining to reasonable delays in required approvals, procuring hardware, or labor allocation may compromise the Datto's ability to perform critical functions such as screenshot validation and offsite synchronization.
For this reason, using a Datto in a fashion more akin to a production hypervisor than a disaster recovery tool is not a supported use of the product. Datto recommends a disaster recovery plan tailored to each client's needs that minimizes the time spent between disaster recovery and full recovery.