(ve) Updates: Historical Server Status + Upgrade Auto-Migrations

Today we’re happy to bring you a few quick updates regarding some recent feature enhancements to our (ve) Server platform.

Historical Server Status

Six months ago, we introduced an (mt) exclusive feature– Realtime Server Status for (ve) Server, which displays a live updating chart of current resource usage of several metrics for your (ve). Recently, we’ve enhanced this feature to include historical data. Historical stats are available in hour, day, week, month, 3 month and year views, so you can always look back and see how your server has been performing over time right from your AccountCenter, or through a simple API call from our upcoming ProDev API.

Update: (dv) 4.0 servers now have access to Real-time & Historical status system via the AccountCenter and the ProDev API.

Upgrade Auto-Migrations

One of the biggest advantages (ve) Server has over Xen-based servers is the ability to instantly upgrade your server’s resources without downtime… as long as the resources are available on your host machine. For most incremental upgrades, our users can easily upgrade without worrying about downtime associated with a full migration because we plan to keep extra resources available on our host machines for this purpose. In some cases, users need to scale past the available resources on their host box.

When we launched (ve), this migration required a support ticket and manual intervention by our operations team. We’re very pleased to announce that we now have fully automated migrations available in the rare case a user needs more resources than their host machine can handle… and the best part… you can schedule it right from your AccountCenter so you know exactly when your server will be experiencing the short downtime associated with the migration. To summarize, (ve) users can now grow from the smallest 512MB instance all the way up to the giant 32GB instance with minimal downtime and absolutely no hassle.

To learn more about (ve) Server, visit the product page, or join the discussion in the (mt) User Forums.