What kind of hardware redundancy is in place? Are all the ssd’s local storage or is it on a nas\san storage? Are these rackmount servers or blades? What kind of density is per host? What kind of guarantee do I get that the host is not going to be overloaded/oversold?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
DO doesn’t use SSD for RAM, only disk storage. The SSD’s are local to the hypervisor, the droplets are allocated inside the hypervisor so to speak. <br> <br>I believe what the support is saying is if a RAID array in the hypervisor degrades too quickly to recover normally (by replacing a single drive for example) DO will move the droplets off the hypervisor to another one. <br> <br>At the end of the day, I always take responsibility for my own data security. DO’s setup is very good, much more reliable than a dedicated server, but any comprehensive data integrity strategy must include steps on your side as well as they suggest.
How you guys migrate your VM’s from other hypervisors if your provided VM’s run on a local storage… one point we can understand the VM’s degraded their performance but how they migrate? <br> <br>Another question please clarify this “The SSD’s are local storage and they use KVM which generally prevents RAM from being oversold” means r u guys using SSD’s for OS or used as for replacement of RAM??
All servers run hardware RAID with different RAID levels but in each case it requires multiple drive failures at the same time for any data loss to occur. In most cases when there is an issue usually a system becomes degraded and starts to exhibit anomalous behavior, at which point we determine that it is no longer healthy to keep it in production and open a maintenance window with customers and migrate their virtual machines to a new hypervisor. <br> <br>In an emergency case we may move the virtual machine without much prior notice if we believe it is imperative to clear out the hypervisor sooner. <br> <br>In regards to data storage we highly recommend to use several different levels for your backups. That includes enabling the internal backups that we provide, taking the occasional snapshot, and also implementing some sort of off-site backup yourself where you focus on moving the content and data that is the most essential to you.