Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In addition to encrypting and compressing files during the migration process, the Source Agent also exports passwords for local user accounts to the destination server container. This includes passwords for domain accounts if those user accounts are associated with migrated services, COM+, or DCOM components. For information about changing the default password to a different password if required to migrate users not associated with services, see Default Password. For information about pre-requisites for COM+ and DCOM components, see https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/310804512/Understanding+Audit?search_id=d88f7ad2-8f35-487b-988a-d6edde738a34.

If you choose to install VirtaMove Source Agent on a source machine, it is enabled by default. The destination machine will automatically attempt to connect to Source Agent. For information about installing VirtaMove Source Agent on a source machine, see https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/310476970/Installing+VirtaMove+Software#Installing-VirtaMove-Source-Agent-and-Source-Monitor in the Installation Guide.

...

  • Port 9665 needs to be open in order to establish a connection to the VirtaMove Source Agent on the source machine.

  • Install VirtaMove Source Agent on the source machine.

VirtaMove Source Agent Service

The command line utility virtaagentsvc.exe is used to manage the service VirtaMove.Source.Agent. See https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/314146929/virtaagentsvc?search_id=8410cd45-666a-4ad5-b53e-10600b990983 for more information. The VirtaMove.Source.Agent service startup type is "Automatic" and the service is started automatically on reboot.

...

The key "RecvTimeout" specifies the maximum amount of time that the destination machine will wait to receive data from the VirtaMove Source Agent. The setting helps V-Migrate determine whether disconnection from VirtaMove Source Agent has occurred, and what action to take if this should be the case. For example, if the disconnection is detected during the "Migrating Application Data" phase of Pre-populate, the Admin Console will attempt to reconnect to the Source Agent until the connection is restored and then resume the migration.

...