https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMTc3IiwiaGFzaCI6Ijk5OGUxMzZjLWUxODctNDYyMS1iNjFjLWU4Yzc5M2M1NjZhOCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Moving Cloud replicas to another datastore

Purpose

A Service Provider may need to migrate replicated cloud VMs to a different datastore using Storage vMotion. This article describes which changes should be made on the Provider's Veeam Server to ensure non-disruptive migration.

Solution

Having performed svMotion, a SP should do the following:
  1. Open Cloud Connect Veeam Console
  2. Open Cloud Connect view
  3. In the inventory pane, click the Replica Resource node, select the necessary hardware plan in the working area and click Edit Hardware Plan on the ribbon or right-click the necessary hardware plan and select Edit Hardware Plan.
  4. At the Storage step of the wizard, select existing cloud datastore and choose Edit option.
  5. In the Datastore section, click Browse and select a new datastore where you migrated cloud replicas.
  6. Save new specified settings and finish the wizard to refresh the information about new cloud datastore for cloud replicas.
 
NOTE: When Veeam Backup & Replication saves new hardware plan settings to the configuration database, resources provided to tenants through the edited hardware plan will become temporarily unavailable to tenants. VM replicas in Failover state after partial site failover will also become temporarily inaccessible
KB ID:
2177
Product:
Veeam Cloud Connect
Version:
All
Published:
2016-10-12
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later