Data Domain: Migration Send Fails due to Destination Hostname Mismatch
Summary: Migration send may fail with active critical alerts when the destination hostname specified in the migration command does not match the destination hostname defined in the replication context. Ensure the hostname used in the migration send command matches the destination system hostname configured in the replication context. ...
Symptoms
Migration send fails with errors similar to:
WARNING: _cmd_migration_are_serious_alerts_active() 1088 : Send cannot continue, found serious alert active. MSG-DDSH-00017: command "migration send all destination-host DATADOMAIN-migration.example.com" exited with code: 33
Active alert:
EVT-REPL-00005: Replication destination not configured
Cause
The migration was initiated using the destination hostname: DATADOMAIN-migration.example.com.
Example:
migration send all destination-host DATADOMAIN-migration.example.com
However, the destination replication context was created using: DATADOMAIN.example.com.
Example:
Replication configuration example: repl.000.dst_host = DATADOMAIN.example.com
During migration, Tech Refresh migration searches for an existing replication context based on the destination hostname configured in the context (dst_host). Since the migration command specified a different hostname, no matching replication context could be found.
Example log entries:
no matching context for DATADOMAIN-migration.example.com Replication (DATADOMAIN-migration.example.com) not configured on the replica
As a result, the migration send operation fails and reports that replication is not configured.
Resolution
Configure local host entries for the migration hostnames to use the preferred interfaces and avoid hostname conflicts.
Examples:
net hosts add x.x.x.220 datadomain01-migration.example.com datadomain01-migration net hosts add x.x.x.61 DATADOMAIN-migration.example.com DATADOMAIN-migration
To resolve the issue, use one of the following options:
- Execute the migration send command using the same hostname that was used when the destination replication context was created.
- Recreate the destination replication context using the desired hostname and corresponding host entries.
dst_host value in the replication context. This allows Tech Refresh migration to locate the correct destination replication context and complete the migration successfully.
Additional Information
Data Domain: How to use migration with and without Replication (Log in as a registered Dell Support user is required to view this article.)