Copying a datastore between two PCCs

Find out how to access a datastore copy of one PCC from another PCC via the OVHcloud API

Last updated 2nd April 2021

Objective

Following the incident that occurred in the SBG data centre, you can copy the datastores from a PCC in SBG3 to a destination PCC.

Find out how to access a datastore copy of one PCC from another PCC using the OVHcloud API.

Requirements

If your source PCC has HDS or PCI-DSS certification, your destination PCC must have the same active certification in order to retrieve the datastore.

For more information, please refer to our guide on Healthcare (HDS) or payment services (PCI DSS) compliance activation.

Instructions

If you are not familiar with using the OVHcloud API, please refer to our OVHcloud API first steps guide.

Step 1: Retrieving the datastore filerId

You must first target the filerId to migrate.

Log in to https://api.ovh.com/.

If you have already retrieved your access to the Strasbourg infrastructure, use the following call:

Enter the variable:

  • serviceName: the name of the source PCC located in SBG (e.g. pcc-192-0-2-15).

If, on the other hand, you have not yet retrieved your access to the Strasbourg infrastructure, use the following call:

Enter the variables:

  • serviceName: the name of the source PCC located in SBG (e.g. pcc-192-0-2-15).
  • datacenterId: the ID of the source datacentre (e.g. 1337).

Step 2: Launching the datastore copy

The destination PCC must be located in one of the following zones: RBX (Roubaix), LIM (Frankfurt) or ERI (London).

Once the filerId has been identified, use the following call to copy the datastore to the destination PCC:

Enter the variables:

  • serviceName: the name of the destination PCC (e.g. pcc-192-0-2-50).
  • datacenterId: the ID of the destination datacentre (e.g. 1515).
  • filerId: the filerId retrieved in the previous step (e.g.: 001234).

Data replication can take several hours. When the replication is complete, you will receive an email confirming that your copy has been successful.

Step 3: Knowing the status of the copy

In order to follow the datastore copy status, use the following API call:

Enter the variables:

  • serviceName: the name of the destination PCC (e.g. pcc-192-0-2-50).
  • datacenterId: the ID of the destination datacentre (e.g. 1515).

If a copy has been asked for, the API will return all the copy operations, waiting, in progress or done (progress percentage, current transfer size, task state, etc.).

Step 4: Accessing the copy from vSphere

In your vSphere interface, go to the Storage view.

ds_restore

Replication will then appear on all hosts in the destination data centre under the name restore-XXXXXX (XXXXXX being the source datastore number).

The recovered datastore is read-only.

For virtual machines, you need to save them in the vSphere inventory, then clone them to one of the datastores before you can start them.

Do not power on your VM before cloning them, otherwise the following error message appears "Unable to write the VMX file".

If you encounter the error message "Unable to write VMX file" or "Error caused by /vmfs/volumes/xxxx/xxx.vmdk file", follow these steps:

  • Copy the VM to one of your datastores.
  • Register the VM (if you have not already done so)
  • Clone the VM
  • Power on the VM.

Step 5: Delete the copy

Once the data has been retrieved, you can remove the copy of the filer by following the documentation for removing a datastore.

Go further

Join our community of users on https://community.ovh.com/en/.


Did you find this guide useful?

Please feel free to give any suggestions in order to improve this documentation.

Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.

Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.

Thank you. Your feedback has been received.


These guides might also interest you...

OVHcloud Community

Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Discuss with the OVHcloud community

In accordance with the 2006/112/CE Directive, modified on 01/01/2015, prices incl. VAT may vary according to the customer's country of residence
(by default, the prices displayed are inclusive of the UK VAT in force).