![NetApp AltaVault AVA400 Administration Manual Download Page 175](http://html.mh-extra.com/html/netapp/altavault-ava400/altavault-ava400_administration-manual_1669933175.webp)
NetApp AltaVault Cloud Integrated Storage Administration Guide
175
Beta Draft
Performing appliance data migration
Migrating data between appliances
3.
Once the target appliance is ready, data migration can be initiated on the source appliance. Data migration can
transmit both the metadata and the data or just the metadata. If only metadata is migrated, all data must have been
previously replicated to cloud storage by the source appliance. Migrating data and metadata requires additional
time, but allows AltaVault to have immediate access to data in cache for quick restore. If the data migration is
stopped or interrupted and restarted, then migration will continue from where it was interrupted.
(a). To transfer the data and metadata, use the following CLI commands on the source appliance to start data
migration:
<source appliance> > enable
<source appliance> # configure terminal
<source appliance (config)> # datamigration send dest-ip <ipaddress1,ipaddress2...>
(b). To exclude data and only send metadata to the target appliance, use the following CLI command.
<source appliance (config)> # datamigration send dest-ip <ipaddress1,ipaddress2...>
metadata-only
With metadata-only option, the data pinned on the source appliance will not be transfered to the target
appliance. Newly ingested data to pinned shares on the target appliance will continue to be pinned.
When data migration is performed with metadata-only option, the migration process completes faster than
migrating both the data and metadata. After metadata migration is complete, deduplication of new backup
and/or archival data to the target appliance will be similar to the source appliance. However, the metadata-
only option is not optimized for data restore on the target appliance as it has not transferred the locally cached
data.
One or more destination interface IP addresses can be provided as part of the data migration command. If
more than one destination interface IP address can be provided in comma-separated form as part of the data
migration across these interfaces
Note:
The metadata-only migration option is not supported in cases where the source appliance has cloud deduplication disabled.
In this case, the target appliance would receive the metadata for files in the local cache of the source, but not the actual data. The
datastore cache contains dedupe hashes of only those data segments that are cached locally. A metadata-only transfer of an appliance
that is configured with cloud dedupe turned off might cause data ingested into the new appliance to dedupe against data segments
found only in cloud.
4.
Once data migration is initiated on the source appliance, the tool will validate the state on the target appliance. This
step can take up to 5 minutes per shelf on the source appliance.To display the status of data migration, use the
following CLI command:
<source appliance (config)> # show datamigration status
5.
To stop data migration tool on the source appliance, use the following command:
<source appliance (config)> # datamigration send stop
6.
To stop data migration on the target appliance, use the following command:
<target appliance (config)> # datamigration receive stop
7.
To reset and restart data migration from the beginning, issue the following CLI commands on both on the source
and target appliances. After entry, repeat step 1 and step 2 to initiate a new data migration.
<target appliance (config)> # datamigration receive reset
Summary of Contents for AltaVault AVA400
Page 2: ...Beta Draft ...
Page 10: ...Beta Draft Contents ...