Frequently Asked Questions
How is RiverMeadow Migration different than server replication, scripting, templates and manual migration? What does it mean to migrate servers as-is?
RiverMeadow is an "as-is migration" solution that automates the collection, re-packaging/conversion and deployment of server images and their associated metadata/configuration into cloud and virtual environments. As-is migration offers automated migration of workloads without any pre-processing on the source machine or post-processing on the target machine. Other solutions entail some manual pre-processing or post-processing.
What is the difference between migrating workloads and servers? Aren't they the same?
Servers entail the OS, the applications and platforms (e.g. application servers, databases) associated with the workload. Workloads typically include the entire farm of servers (for scaling, failover), data storage (data may be stored on attached and/or networked storage) and the network and system configurations associated with the workload.
Does RiverMeadow SaaS support concurrent connections?
Yes – Multiple migrations can be processed concurrently in a single RiverMeadow SaaS account.
Does RiverMeadow require a proprietary environment to import servers into prior to migration (Or is RiverMeadow SaaS a proprietary platform)?
RiverMeadow provides a transient environment to support the conversion before servers are deployed into the target data center. No customer platform is required to support the migration.
What does it mean to migrate a server live?
It means that production servers can be migrated without havingn to take them down out of production during the migration. Once the migration is complete and the workload is configured and tested on the target machine, the customer can set up a change window to cut-over to the new VM deployed in the target data center.
How is RiverMeadow migration different from VMotion?
V-motion is a native, VMware-only capability designed for optimization and scaling in single-LAN, SAN-only homogeneous environments. RiverMeadow supports heterogeneous environments and enables a broader set of use cases, including migration from one hypervisor platform to another. RiverMeadow also supports migration across networks and across clouds.
What Platforms Does RiverMeadow Support?
RiverMeadow supports migration from physical, virtual and cloud platforms to cloud platforms. Supported OS, hypervisors and Clouds are:
- Source OS – Windows 2003/2008/2012, Linux
- Target Clouds – AWS VPC, VMWare vCloud Director, VMware vCloud Air, VMware vShpere, Verizon Cloud
Do I need to install anything? What about agents?
RiverMeadow is an agentless technology, so you will not need to install agents. RiverMeadow SaaS, will automatically deploy a Cloud Appliance and Target Worker(s) into the target data center to collect, convert and deploy the source image(s).
Why do some clouds show NA for CPU count?
Some cloud providers such as Rackspace do not currently provide the number of cpus as an option when specifying a new cloud instance. As such, when deploying a new cloud server, we display N/A in our field to indicate this information is not available for the specified cloud provider.
Can I migrate from local to local?
Yes, RiverMeadow supports migration from a local physical/virtual/cloud server to another local private cloud.
Can I migrate from cloud to local?
Yes, you can migrate from a public cloud to a local VMware environment.
Are there any hardware requirements?
No, it’s a true SaaS solution.
How long does it take to deploy an image to a server?
Deployment times are highly variable and depend on things like network bandwidth, throughput, disk IO and CPU speed for the server being provisioned and so forth. A benchmark deployment to provision a 10 GB VM in the same data center as the image library is 15 to 25 minutes. Deploying a very large image over a WAN or a slow/busy LAN can take an hour or more.