Cloud Migration

Most IT architects are increasingly involved in determining optimal workload placement.  Should workloads stay on premise?  Move to a cloud hosting provider? Deploy in a public or private cloud?  The top three criteria for deciding which workloads to deploy, where and at what time are – security, performance requirements and cost.  Making workload placement and deployment decisions should always start with understanding workload requirements.

By providing full-lifecycle workload monitoring, analysis, modeling and generation solutions, we empower IT architects and engineers to accurately emulate real-world application workload performance in private and public cloud environments.  Many of our customers are moving data from on premise to cloud service providers. Through their methodical consideration and weighing of factors related to cost, security, and availability, they use Virtual Instruments to determine the best storage tiers based on workload performance requirements.  Public and private clouds are just types of tiers.

Virtual Instruments’ WorkloadWisdom solution can help you fully characterize all of your workload profiles and simulate what-if and worst case scenarios by generating load against various cloud storage protocols.  You will know the performance impact of deploying in the cloud before final deployment decisions are made – eliminating surprises and enabling you to fully understand the cost/performance trade-offs.

Virtual Instruments’ VirtualWisdom App-centric Infrastructure Performance Management solution can help you accurately benchmark your workload performance requirements before you migrate. And, if you are migrating to a private cloud instrumented with VirtualWisdom, you can ensure that your SLAs are being met, or help your provider understand where they need to make adjustments to deliver on what is promised

Save millions of dollars and mitigate performance risks by testing application workload performance as data is sent to the cloud.

Cloud Migration Use Cases

• Disaster Recovery (DR): By far, the most popular use of cloud storage is for DR. Typically, you’ll replicate to a cloud provider.  DR can be slow or it can be fast, but performance limitations are usually bandwidth related.  Performance indicators like latency aren’t usually a factor.
• Primary Storage: Cloud is often used as primary storage with on-premises caching, while the primary copy of the data is in the cloud. In this model the on premise access is considered the hub of the deployment.  With highly dispersed workforces, or when file sharing is the use case, the cloud is the hub.
• Tiering: cloud tiering is becoming more common. Many storage systems enable you to automatically move data between tiers based on user defined criteria. Tiering, whether in the cloud or not, brings its own special testing requirements. Specifically, many tiering tools don’t adjust data placement more frequently than once a day, so your test periods need to be aware of that.
• Development and testing: For cost control and provisioning speed, many developers are purchasing cloud resources as development progresses. Stress testing can happen early in the dev cycle, due to the ease of scaling cloud resources.

Public Cloud Protocols support

• Amazon S3
• Microsoft Azure SMB
• OpenStack Swift