Servosity Cloud Spin-ups
Servosity offers the ability to boot your systems in the cloud should the need arise. We also offer four free hours of cloud spin-up tests quarterly. While this can be an indispensable tool in your arsenal to ensure your clients experience minimal downtime, there are some restrictions and requirements that need to be met in order to ensure we're able to successfully boot your systems in the cloud.
Requirements:- No boot volumes larger than 4TB (Due to AWS limitations, GPT volumes must be converted to MBR.)
- Only supported Windows Operating systems (See our Platforms page for more information)
- Ability to allow RDP to be enabled
Considerations:
- Company's with multiple domains are not supported for a single Cloud Spin-up
- Each domain can be requested as an individual test
A Rule of Thumb: 8 hours per TB Restored To The Cloud.
While it might not take the full 8 hours, it is safe to quote out 8 hours per TB restored to the cloud. This includes having to downloading the data, restoring it to the volume, and making the needed changes to allow it to boot in a cloud VM.
Failback Can Take Longer Than Failover.
During failover (production-to-cloud) we quote roughly 8 hours per TB restored. However, there are some additional factors to consider when it comes time to failback (cloud-to-production). Since data has changed while using the cloud VMs, you'll need to backup those changes. Depending on the size of the volumes and the amount of data changed, backing up those volumes could take longer than the restore. Additionally, if you need the cloud VMs to remain viable while failing back, the restore will need to be split up into chunks which could take longer than a standard restore.
The Cloud Environment Will Closely Mimic The Production Environment.
This consideration can be a bit more vague, but just as important as the others. For example, if your production environment is on a domain and using a Domain Controller, that Domain Controller will need to be spun up as well to allow other machines to log in using their domain accounts. If the Domain Controller is going to be excluded for any reason, you will need to ensure that there is a local account present on any domain attached machine you wish to log into during the cloud spin-up.
If you have any questions regarding the information covered in this article, please reach out to support@servosity.com for assistance!