Migration Fails with Failed to read *.tar.gz.* Error
Reference Number: AA-00404 Views: 591 Created: 10-27-2016 18:44 Last Updated: 10-27-2016 18:44

Symptoms:

While attempting to migrate a server, the operation fails with an error similar to the following:

Failed to read *.tar.gz.*

Applies To:

DynaCenter 6.3.0 and later

Background:

While unlikely, it is possible that when migrating a server workload across a network that is under a heavy load, packet loss can result from the network congestion. Because even one missing packet results in an incomplete image, the migration cannot complete successfully.

More Information:

DynaCenter provides a high integrity capture mode that runs additional integrity checks to validate the checksum of each image chunk to ensure that the image is complete. If you have experienced an issue migrating a server workload across a highly congested network, consider enabling high integrity capture mode; however, be aware that there will be a performance impact because of the additional integrity checks run on each image chunk.

There are two mechanisms for setting the high integrity image capture mode:

•  Globally, on the Management Workstation (MWS)

•  Locally, on the source server (the server being captured)

On the Management Workstation (MWS)

The high_integrity_capture setting in the oem.ini file located on the MWS controls the capture mode for any agent that has its high_integrity_capture set to mws_controlled (the default setting) at the time the agent registers with DynaCenter (either when the agent is first installed or whenever the agent service is restarted).

In the oem.ini file, the high_integrity_capture setting can be set to one of the following values:

•  False - (default) capture operations do not run in high integrity image capture mode

•  True - capture operations run in high integrity image capture mode

On the Source Server

The high_integrity_capture setting in the dpad.ini file located on the source server determines the capture mode for the agent running on that server.

In the dpad.ini file, the high_integrity_capture can be set to one of the following values:

•  mws_controlled - the capture mode is set during server registration using the high_integrity_capture value set in the oem.ini file on the MWS

•  False - the value configured in the oem.ini file is ignored and high integrity capture mode is disabled during server registration

•  True - the value configured in the oem.ini file is ignored and high integrity capture mode is enabled during server registration

Resolution:

To enable high integrity capture mode for a single server:

1.  On the source server where the DynaCenter Agent is installed, open the appropriate file, as follows:

•  Linux: /opt/race/etc/dpad.ini

•  Windows: C:\Program Files (x86)\DynaCenter\opt\race\etc\dpad.ini

2.  In the [agent] section, do one of the following:

•  If the high_integrity_capture setting already exists, edit the setting to high_integrity_capture = True.

•  If the high_integrity_capture setting does not already exist, add the following line to the section:

high_integrity_capture = True

3.  Save the changes to the file.

4.  Restart the agent service:

•  On Windows systems, run the following:

sc stop dpad
sc start dpad

•  On 6.x and earlier RHEL-based systems, run the following:

service dpad.rc restart

•  On 7.x RHEL-based systems, run the following:

systemctl restart dpad

5.  Retry the server workload migration.


To enable high integrity capture mode for all capture operations:

1.  On the MWS, open the following file:

/opt/race/share/conf/oem.ini

2.  In the [agent] section, change the high_integrity_capture setting:

[agent]
.
.
high_integrity_capture = True
.
.

3.  Save the changes to the file.

4.  Retry the server workload migration.