Migrating data between vaults

Overview
The data migration service allows for vault level data migration. Objects are copied from a source vault to a target vault. Objects on the source vault are not deleted. The vault proxy feature enables seamless access to objects on both source and destination during migration.
Purpose
Terminology and components
Workflow
Data Migration follows a simple workflow.
Data migration using the manager
Data Migrations and Vault Proxies are configured using the Manager GUI and/or REST API. This section summarizes the main configuration steps for a configuration that includes a vault proxy and source vault rename.
Performance implications during migration
Latency increases due to migration processing and proxying of client requests. Throttling may be used to limit the impact of migration, but will increase the time required to complete the migration. Throttling will not impact the additional latency incurred for proxied read and delete operations because this depends on the network between the source and target pools.
Blocked state
A migration may enter a blocked state. This occurs when all of the attempts to list the source vault fail (default is five attempts).
Halted with failures state
A migration may halt with failures. This occurs when all of the copy attempts (default is five copy attempts for each object) for at least one object fail.
Limitations

Parent topic: Concepts