Enterprise File Storage - Migrate a volume to the vRack

View as Markdown

Find out how to migrate an Enterprise File Storage volume to an offer on the vRack private network using share replication, from the OVHcloud Control Panel or the API

Objective

This guide explains how to migrate a volume hosted on an OVHcloud Enterprise File Storage offer on the public network to a second Enterprise File Storage offer on the vRack private network, using the share replication feature. You can manage this feature from the OVHcloud Control Panel or via the OVHcloud API.

Warning

The share replication feature is in beta.

Requirements

An OVHcloud Enterprise File Storage offer on the public network (subscribed before January 2025), with a volume to migrate
An OVHcloud Enterprise File Storage offer attached to a vRack private network, in the same region as the source offer
Access to the or to the

OVHcloud Control Panel Access

Direct link:
Navigation path: Bare Metal Cloud > Enterprise File Storage

How it works

The migration takes place in three phases:

Replication — a replication link is created between the source volume and the destination service
Synchronisation — the data is automatically copied from the source volume to the destination volume
Finalisation (cutover) — the replication link is cut, which makes the destination volume independent and writable (it remains read-only until then)

Feature limitations

Share replication can only migrate an Enterprise File Storage volume on the public network to an Enterprise File Storage offer on the vRack private network, within the same region.

Instructions

Step 1 — Check service compatibility

OVHcloud Control Panel

OVHcloud API

On the source service, open the Volumes tab.
Tick the box for the volume(s) to migrate, then click Replicate volume(s) — or, from the ... menu of a row, click Replicate this volume.
In the Sync volume(s) on another Enterprise File Storage service window, the Target Enterprise File Storage field only lists compatible services: the OVHcloud Control Panel performs this check for you.

Info

If no target service is offered, the OVHcloud Control Panel directly displays an Order button so that you can subscribe to a compatible Enterprise File Storage offer (vRack private network, same region).

Check that your Enterprise File Storage offer on the vRack private network is eligible as the migration destination:

GET/storage/netapp/{serviceName}/shareReplicationServicesCompatibility

Parameters:

serviceName: unique identifier of the source service, which holds the volume to migrate
compatibleOnly (optional): if true, only compatible services are returned

This route returns the candidate services, each with its compatibility status (compatible, reason) and the identifier to use as the destination service:

[
  {
    "service": {
      "id": "{destinationServiceId}",
      "name": "MyDestinationService"
    },
    "compatible": true,
    "reason": null
  }
]

Info

If the list is empty or no service is marked compatible: true, you do not have any Enterprise File Storage offer on the vRack private network in the same region as your source service. Order an Enterprise File Storage offer with the vRack private network to continue.

Step 2 — Create the replication

OVHcloud Control Panel

OVHcloud API

In the same window, select the target service in the Target Enterprise File Storage field, then click Sync to start the replication.

From the source service, start the replication:

POST/storage/netapp/{serviceName}/shareReplication

Parameters:

serviceName: unique identifier of the source service
destinationServiceId: identifier of the destination service, retrieved in the previous step
sourceShareId: identifier of the volume to migrate
description (optional): description of the replication

Then retrieve the identifier of the replication you have created:

GET/storage/netapp/{serviceName}/shareReplication

[
  {
    "id": "{shareReplicationId}",
    "description": "",
    "status": "pending",
    "source": {
      "serviceID": "{sourceServiceId}",
      "shareID": "{sourceShareId}"
    },
    "destination": {
      "serviceID": "{destinationServiceId}",
      "shareID": null
    }
  }
]

Step 3 — Accept the replication from the destination service

OVHcloud Control Panel

OVHcloud API

On the destination service, open the Replications tab. The incoming replication appears with the status Pending approval.
From the ... menu of the row, click Accept replication.
Confirm by clicking Sync.

Info

The OVHcloud Control Panel automatically creates the destination volume with the NFS protocol and the size of the source volume — no additional parameters are required.

From the destination service, accept the replication (this action creates the volume that will host the replica):

POST/storage/netapp/{serviceName}/shareReplication/{shareReplicationId}/accept

Parameters:

serviceName: unique identifier of the destination service
shareReplicationId: identifier of the replication, retrieved in the previous step
share.name (optional): name of the destination volume
share.protocol: volume protocol (NFS)
share.size: volume size, in GB — must be greater than or equal to the size of the source volume
share.description (optional): description of the volume
share.mountPointName (optional): name of the mount point

The replication details then let you retrieve the identifier of the destination volume created:

GET/storage/netapp/{serviceName}/shareReplication/{shareReplicationId}

{
  "id": "{shareReplicationId}",
  "description": "",
  "status": "accepted",
  "replicaState": "out_of_sync",
  "createdAt": "2025-12-05T13:18:00Z",
  "source": {
    "serviceID": "{sourceServiceId}",
    "shareID": "{sourceShareId}"
  },
  "destination": {
    "serviceID": "{destinationServiceId}",
    "shareID": "{destinationShareId}"
  }
}

Step 4 — Monitor the synchronisation

OVHcloud Control Panel

OVHcloud API

In the Replications tab of the destination service, the status of the row changes automatically:

Synchronising — the data is being copied (equivalent to replicaState: out_of_sync).
Synced — the two volumes are synchronised (equivalent to replicaState: in_sync).

Query the replication details route again to monitor the progress of the data copy:

GET/storage/netapp/{serviceName}/shareReplication/{shareReplicationId}

replicaState: out_of_sync — the synchronisation is in progress; the progress field shows how far it has advanced.
replicaState: in_sync — the two volumes are synchronised.

Info

While the replication is active, any new write to the source volume temporarily sets replicaState back to out_of_sync, until the new data has been replicated.

Step 5 — Finalise the migration (cutover)

OVHcloud Control Panel

OVHcloud API

Once the Synced status is reached in the Replications tab, click Promote from the ... menu of the row.
A warning window reminds you that this action cuts the replication with the source volume and makes the promoted volume independent — this action is irreversible. Click Confirm.

The status of the row then changes to Promoting, then to Migrated.

Once replicaState is in_sync, finalise the migration by cutting the replication link from the destination service:

POST/storage/netapp/{serviceName}/shareReplication/{shareReplicationId}/cutover

Parameters:

serviceName: unique identifier of the destination service
shareReplicationId: identifier of the replication to finalise

This action ends the replication (status changes to completed once the promotion is complete) and makes the destination volume independent.

Expected result

The volume is now available on the Enterprise File Storage offer on the vRack private network, with all the data from the source volume.
The replication link has ended; the two volumes evolve independently.
The source volume remains unchanged: you can delete it once you have validated the migration.

To use the migrated volume, remount it on your clients from the vRack address of the new offer.

Go further

Managing Enterprise File Storage from the OVHcloud Control Panel

Enterprise File Storage - Clone a volume

Enterprise File Storage - Private network configuration

Enterprise File Storage - Connect a Public Cloud instance to an EFS Volume via vRack Private Network

Enterprise File Storage - Managing volumes

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analysed by our experts.

Join our community of users.

Was this page helpful?