Your use of the VM Replication Service is subject to the following additional terms.
VM Replication utilises third party software as a managed solution that is purpose built for VMware and allows:
• Replication of Virtual Machines from one Rackspace datacentre (source) to another Rackspace datacentre (target),
• Customers to initiate testing of replicated VMs on a hypervisor located at a secondary target site.
• Customers to initiate VM failover from one Rackspace datacentre to another Rackspace datacentre. This includes halting replication, powering off the primary source site VM, powering on the secondary target site VM, and configuring DNS and networking setting to allow secondary target site VM connectivity.
Service Level Agreement:
Customer environments utilising the VM Replication service are governed by the Service Level Agreements contained in the Product Terms applicable to each of those environments (or other such Service Level Agreement if applicable). While there are no additional Service Level Agreements available for the VM replication offering due to the differences in every environment, the variability in the amount of data to be replicated and required procedures for restoration, Rackspace agrees to notify you in the event that a replication, failover test, or failover event fails to complete successfully. Rackspace will open a support ticket within four (4) hours of Rackspace’s initial notification to you that a replication, failover test or failover event has failed to complete successfully.
VM Replication is not a full Disaster Recovery or High Availability solution. It is intended to be a component in a customer managed and executed disaster recovery and failover plan. As such, Rackspace takes no responsibility for, and does not guarantee any disaster recovery capabilities as a result of your use of any of the features of the VM Replication Service. Rackspace accepts no responsibility for Customer’s data loss. Upon receipt of Customer’s sign off on the failover test, Rackspace accepts no responsibility for failed replication of virtual machines. Rackspace recommends that for maximum protection, customers do not run “active” or “powered on” VMs on the replication target hypervisor. If active VMs on the replication target hypervisor exist during failover, the resulting over allocation of resources could cause the entire hypervisor (and associated VMs) to fail. Should you decide to provision active VMs on hypervisors that are replication targets, it is your responsibility, not Rackspace’s, to power down existing VMs and ensure that the environment is not over allocated at any time as part of a Disaster Recovery plan.
RACKSPACE MAKES NO WARRANTY OR GUARANTEE WHATSOEVER REGARDING THE VM REPLICATION SERVICE AND TO THE EXTENT PERMITTED BY APPLICABLE LAW, DISCLAIMS ANY AND ALL WARRANTIES INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.