使用舊版的 Azure MigrateWork with the previous version of Azure Migrate

此文章提供使用舊版 Azure Migrate 的相關資訊。This article provides information about working with the previous version of Azure Migrate.

Azure Migrate 服務有兩個版本:There are two versions of the Azure Migrate service:

  • 目前的版本:使用此版本來建立 Azure Migrate 專案、探索內部部署電腦,以及協調評量與移轉。Current version: Use this version to create Azure Migrate projects, discover on-premises machines, and orchestrate assessments and migrations. 深入了解此版本的新功能。Learn more about what's new in this version.
  • 先前版本:如果您使用的是舊版 Azure Migrate (僅支援內部部署 VMware VM 的評量),則您現在應該使用目前的版本。Previous version: If you're using the previous version of Azure Migrate (only assessment of on-premises VMware VMs was supported), you should now use the current version. 先前的版本專案在本文中稱為「傳統專案」。The previous version projects are referred to as Classic projects in this article. 傳統 Azure Migrate 即將于2024年2月淘汰。Classic Azure Migrate is retiring in Feb 2024. 在2024年2月之後,將不再支援傳統版本的 Azure Migrate,並且會刪除傳統專案中的清查中繼資料。After Feb 2024, classic version of Azure Migrate will no longer be supported and the inventory metadata in classic projects will be deleted. 如果您仍然需要使用傳統 Azure Migrate 專案,這就是您可以執行的作業:If you still need to use classic Azure Migrate projects, this is what you can and can't do:
    • 您無法再建立移轉專案。You can no longer create migration projects.
    • 我們建議您不要執行新的探索。We recommend that you don't perform new discoveries.
    • 您仍然可以存取現有的專案。You can still access existing projects.
    • 您仍然可以執行評量。You can still run assessments.

版本之間的升級Upgrade between versions

您無法將舊版中的專案或元件升級至新版本。You can't upgrade projects or components in the previous version to the new version. 您需要建立新的 Azure Migrate 專案,並將評量與移轉工具新增到其中You need to create a new Azure Migrate project, and add assessment and migration tools to it. 使用教學課程來了解如何使用可用的評量和移轉工具。Use the tutorials to understand how to use the assessment and migration tools available. 如果您已將 Log Analytics 工作區連結至傳統專案,可以在刪除傳統專案之後,將其連結加至目前版本的專案。If you had a Log Analytics workspace attached to a Classic project, you can attach it to a project of current version after you delete the Classic project.

尋找舊版的專案Find projects from previous version

尋找舊版的專案,如下所示:Find projects from the previous version as follows:

  1. 在 Azure 入口網站 > [所有服務] 中,搜尋並選取 [Azure Migrate]。In the Azure portal > All services, search for and select Azure Migrate.
  2. 在 Azure Migrate 儀表板上,會有可以存取舊 Azure Migrate 專案的通知與連結。On the Azure Migrate dashboard, there's a notification and a link to access old Azure Migrate projects.
  3. 按一下連結以開啟傳統專案。Click the link to open Classic projects.

刪除舊版的專案Delete projects from previous version

尋找並刪除舊版的專案,如下所示:Find and delete projects from the previous version as follows:

  1. 在 Azure 入口網站 > [所有服務] 中,搜尋並選取 [Azure Migrate]。In the Azure portal > All services, search for and select Azure Migrate.
  2. 在 Azure Migrate 儀表板上,會有可以存取舊 Azure Migrate 專案的通知與連結。On the Azure Migrate dashboard, there's a notification and a link to access old Azure Migrate projects.
  3. 按一下連結以開啟傳統專案。Click the link to open Classic projects.
  4. 選取您想要刪除的專案,並將其刪除。Select the project you would like to delete and delete it.

建立評估Create an assessment

在入口網站中探索到 VM 之後,您可以將它們分組並建立評量。After VMs are discovered in the portal, you group them and create assessments.

  • 在入口網站中探索到 VM 後,您就可以立即建立內部評量。You can immediately create as on-premises assessments immediately after VMs are discovered in the portal.
  • 針對以效能為基礎的評量,建議您至少先等候一天的時間,再建立以效能為基礎的評量,以取得可靠的大小建議。For performance-based assessments, we recommend you wait at least a day before creating a performance-based assessment, to get reliable size recommendations.

建立評量,如下所示:Create an assessment as follows:

  1. 在專案的 [概觀] 頁面中,按一下 [+建立評估]。In the project Overview page, click +Create assessment.
  2. 按一下 [檢視全部] 來檢閱評估屬性。Click View all to review the assessment properties.
  3. 建立群組,並指定群組名稱。Create the group, and specify a group name.
  4. 選取您想要新增至群組的機器。Select the machines that you want to add to the group.
  5. 按一下 [建立評估] 以建立群組和評估。Click Create Assessment, to create the group and the assessment.
  6. 建立評估之後,在 [概觀] > [儀表板] 中檢視該評估。After the assessment is created, view it in Overview > Dashboard.
  7. 按一下 [匯出評估],將其下載為 Excel 檔案。Click Export assessment, to download it as an Excel file.

如果您想要以最新的效能資料更新現有的評量,則可以對評量使用 [重新計算] 命令來更新它。If you would like to update an existing assessment with the latest performance data, you can use the Recalculate command on the assessment to update it.

檢閱評量Review an assessment

評量有三個階段:An assessment has three stages:

  • 評量會從適用性分析開始,以確定機器是否與 Azure 相容。An assessment starts with a suitability analysis to figure out whether machines are compatible in Azure.
  • 調整大小估計。Sizing estimations.
  • 每月成本預估。Monthly cost estimation.

機器必須先通過前一個評量,才可前往下一階段。A machine only moves along to a later stage if it passes the previous one. 例如,如果機器未通過適用性檢查,就會標示為不適合 Azure,而不會再去計算大小與成本。For example, if a machine fails the suitability check, it’s marked as unsuitable for Azure, and sizing and costing isn't done.

檢閱 Azure 移轉整備程度Review Azure readiness

評量中的 Azure 移轉整備程度檢視會顯示每部虛擬機器的整備狀態。The Azure readiness view in the assessment shows the readiness status of each VM.

整備程度Readiness StateState 詳細資料Details
可供 Azure 使用Ready for Azure 無相容性問題。No compatibility issues. 機器可以依原樣遷移到 Azure,它將會在 Azure 中開機並包含完整的 Azure 支援。The machine can be migrated as-is to Azure, and it will boot in Azure with full Azure support. 對於已準備好的 VM,Azure Migrate 會建議這些 VM 在 Azure 中該有的大小。For VMs that are ready, Azure Migrate recommends a VM size in Azure.
可有條件地供 Azure 使用Conditionally ready for Azure 該機器可能可以在 Azure 中開機,但可能沒有完整的 Azure 支援。The machine might boot in Azure, but might not have full Azure support. 例如,Azure 中不支援使用較舊版本 Windows Server 的機器。For example, a machine with an older version of Windows Server that isn't supported in Azure. Azure Migrate 會說明整備程度問題,並提供補救步驟。Azure Migrate explains the readiness issues, and provides remediation steps.
未備妥供 Azure 使用Not ready for Azure VM 將無法在 Azure 中開機。The VM won't boot in Azure. 例如,如果 VM 的磁碟超過 4 TB,便無法在 Azure 上託管。For example, if a VM has a disk that's more than 4 TB, it can't be hosted on Azure. Azure Migrate 會說明整備程度問題,並提供補救步驟。Azure Migrate explains the readiness issues, and provides remediation steps.
移轉整備程度未知Readiness unknown Azure Migrate 無法識別 Azure 整備程度,通常是因為資料無法使用。Azure Migrate can't identify Azure readiness, usually because data isn't available.

Azure VM 屬性Azure VM properties

整備程度考慮了許多 VM 屬性,以識別 VM 是否可以在 Azure 中執行。Readiness takes into account a number of VM properties, to identify whether the VM can run in Azure.

屬性Property 詳細資料Details 整備程度Readiness
開機類型Boot type 支援 BIOS。BIOS supported. 不支援 UEFI。UEFI not supported. 如果開機類型為 UEFI,便已有條件地就緒。Conditionally ready if boot type is UEFI.
核心Cores 機器核心 <= Azure VM 支援的核心數目上限 (128)。Machines core <= the maximum number of cores (128) supported for an Azure VM.

如果效能歷程記錄可用,則 Azure Migrate 會將已使用的核心數納入考量。If performance history is available, Azure Migrate considers the utilized cores.
如果評量設定已指定緩和因數,則會將使用的核心數目乘以緩和因數。If a comfort factor is specified in the assessment settings, the number of utilized cores is multiplied by the comfort factor.

如果沒有效能記錄,Azure Migrate 會使用配置的核心,而不套用緩和因數。If there's no performance history, Azure Migrate uses the allocated cores, without applying the comfort factor.
小於或等於限制便就緒。Ready if less than or equal to limits.
記憶體Memory 機器的記憶體大小 <= Azure VM 的記憶體上限 (Azure M 系列 Standard_M128m 上為 3892 GB  2)。The machine memory size <= the maximum memory (3892 GB on Azure M series Standard_M128m 2) for an Azure VM. 深入了解Learn more.

如果效能歷程記錄可用,Azure Migrate 會將已使用的記憶體數納入考量。If performance history is available, Azure Migrate considers the utilized memory.

如果已指定緩和因數,則會將使用的記憶體乘以緩和因數。If a comfort factor is specified, the utilized memory is multiplied by the comfort factor.

如果沒有記錄,則會使用配置的記憶體,而不套用緩和因數。If there's no history the allocated memory is used, without applying the comfort factor.

在限制內便就緒。Ready if within limits.
存放磁碟Storage disk 已配置的磁碟大小必須小於或等於 4 TB (4096 GB)。Allocated size of a disk must be 4 TB (4096 GB) or less.

附加至機器的磁碟數目必須小於或等於 65,作業系統磁碟亦包含在內。The number of disks attached to the machine must be 65 or less, including the OS disk.
在限制內便就緒。Ready if within limits.
網路功能Networking 機器必須附加 32 個以內的網路介面卡。A machine must have 32 or less NICs attached to it. 在限制內便就緒。Ready if within limits.

客體作業系統Guest operating system

隨著 VM 屬性,Azure Migrate 也會查看內部部署 VM 的客體 OS,以識別 VM 是否可以在 Azure 中執行。Along with VM properties, Azure Migrate also looks at the guest OS of the on-premises VM to identify if the VM can run in Azure.

  • Azure Migrate 會考量 vCenter Server 中指定的 OS。Azure Migrate considers the OS specified in vCenter Server.
  • 由 Azure Migrate 探索是應用裝置為基礎,因此無法驗證 VM 內執行的作業系統是否與 vCenter Server 中所指定的相同。Since the discovery done by Azure Migrate is appliance-based, it does not have a way to verify if the OS running inside the VM is same as the one specified in vCenter Server.

會使用下列邏輯。The following logic is used.

作業系統Operating System 詳細資料Details 整備程度Readiness
Windows Server 2016 與所有 SPWindows Server 2016 and all SPs Azure 提供完整支援。Azure provides full support. 可供 Azure 使用Ready for Azure
Windows Server 2012 R2 與所有 SPWindows Server 2012 R2 and all SPs Azure 提供完整支援。Azure provides full support. 可供 Azure 使用Ready for Azure
Windows Server 2012 與所有 SPWindows Server 2012 and all SPs Azure 提供完整支援。Azure provides full support. 可供 Azure 使用Ready for Azure
Windows Server 2008 R2 與所有 SPWindows Server 2008 R2 and all SPs Azure 提供完整支援。Azure provides full support. 可供 Azure 使用Ready for Azure
Windows Server 2008 (32 位元和 64 位元)Windows Server 2008 (32-bit and 64-bit) Azure 提供完整支援。Azure provides full support. 可供 Azure 使用Ready for Azure
Windows Server 2003、2003 R2Windows Server 2003, 2003 R2 不支援,需要自訂支援合約 (CSA) 才能獲得 Azure 支援。Out-of-support and need a Custom Support Agreement (CSA) for support in Azure. 可有條件地供 Azure 使用,在移轉到 Azure 之前,請考慮升級作業系統。Conditionally ready for Azure, consider upgrading the OS before migrating to Azure.
Windows 2000、98、95、NT、3.1、MS-DOSWindows 2000, 98, 95, NT, 3.1, MS-DOS 不支援。Out-of-support. 機器可能可以在 Azure 中開機,但 Azure 不會提供 OS 支援。The machine might boot in Azure, but no OS support is provided by Azure. 可有條件地供 Azure 使用,建議在移轉到 Azure 之前升級作業系統。Conditionally ready for Azure, it is recommended to upgrade the OS before migrating to Azure.
Windows Client 7、8 及 10Windows Client 7, 8 and 10 Azure 僅對 Visual Studio 訂用帳戶提供支援。Azure provides support with Visual Studio subscription only. 可有條件地供 Azure 使用Conditionally ready for Azure
Windows 10 專業版桌面Windows 10 Pro Desktop Azure 對多租用戶主機權限提供支援。Azure provides support with Multitenant Hosting Rights. 可有條件地供 Azure 使用Conditionally ready for Azure
Windows Vista、XP ProfessionalWindows Vista, XP Professional 不支援。Out-of-support. 機器可能可以在 Azure 中開機,但 Azure 不會提供 OS 支援。The machine might boot in Azure, but no OS support is provided by Azure. 可有條件地供 Azure 使用,建議在移轉到 Azure 之前升級作業系統。Conditionally ready for Azure, it is recommended to upgrade the OS before migrating to Azure.
LinuxLinux Azure 認同這些 Linux 作業系統Azure endorses these Linux operating systems. 其他 Linux 作業系統可能可以在 Azure 中開機,但我們建議您在移轉至 Azure 之前,將作業系統升級為認可的版本。Other Linux operating systems might boot in Azure, but we recommend upgrading the OS to an endorsed version, before migrating to Azure. 如果版本受到認同,則可供 Azure 使用。Ready for Azure if the version is endorsed.

如果版本未受到認同,則有條件地可供使用。Conditionally ready if the version is not endorsed.
其他作業系統Other operating systems

例如,Oracle Solaris、Apple macOS 等、FreeBSD 等。For example, Oracle Solaris, Apple macOS etc., FreeBSD, etc.
Azure 並未認可這些作業系統。Azure doesn't endorse these operating systems. 機器可能可以在 Azure 中開機,但 Azure 不會提供作業系統支援。The machine may boot in Azure, but no OS support is provided by Azure. 可有條件地供 Azure 使用,建議在移轉到 Azure 之前安裝支援的作業系統。Conditionally ready for Azure, it is recommended to install a supported OS before migrating to Azure.
在 vCenter Server 中作業系統指定為 其他OS specified as Other in vCenter Server Azure Migrate 無法在此情況下識別作業系統。Azure Migrate cannot identify the OS in this case. 整備程度未知。Unknown readiness. 請確保 Azure 支援 VM 內執行的作業系統。Ensure that the OS running inside the VM is supported in Azure.
32 位元作業系統32-bit operating systems 機器可能可以在 Azure 中開機,但 Azure 可能不會提供完整支援。The machine may boot in Azure, but Azure may not provide full support. 可有條件地供 Azure 使用,在移轉到 Azure 之前,請考慮將機器的作業系統從 32 位元作業系統升級至 64 位元作業系統。Conditionally ready for Azure, consider upgrading the OS of the machine from 32-bit OS to 64-bit OS before migrating to Azure.

檢查大小Review sizing

Azure Migrate 大小建議取決於評量屬性中指定的大小調整準則。The Azure Migrate size recommendation depends on the sizing criterion specified in the assessment properties.

  • 如果大小調整是以效能為基礎,則大小調整建議會考量 VM (CPU 與記憶體) 與磁碟 (IOPS 與輸送量) 的效能歷程記錄。If sizing is performance-based, the size recommendation considers the performance history of the VMs (CPU and memory) and disks (IOPS and throughput).
  • 如果大小調整準則是「如內部部署」,則 Azure 中的大小建議是以 VM 內部部署的大小為基礎。If the sizing criterion is 'as on-premises', the size recommendation in Azure is based on the size of the VM on-premises. 磁碟大小調整是以評量屬性中指定的儲存體類型為基礎 (預設為進階磁碟)。Disk sizing is based on the Storage type specified in the assessment properties (default is premium disks). Azure Migrate 不會考量 VM 和磁碟的效能資料。Azure Migrate doesn't consider the performance data for the VM and disks.

檢閱成本估計Review cost estimates

成本估計會顯示在 Azure 中執行 VM 的計算和儲存總成本,以及每部電腦的詳細資訊。Cost estimates show the total compute and storage cost of running the VMs in Azure, along with the details for each machine.

  • 在計算成本估計時,會使用 VM 機器的大小建議與其磁碟和評量屬性。Cost estimates are calculated using the size recommendation for a VM machine, and its disks, and the assessment properties.
  • 系統會彙總群組內所有 VM 之計算和儲存的每月預估成本。Estimated monthly costs for compute and storage are aggregated for all VMs in the group.
  • 成本估計用於執行內部部署 VM 以作為 Azure 基礎結構即服務 (IaaS) VM。The cost estimation is for running the on-premises VM as Azure Infrastructure as a service (IaaS) VMs. Azure Migrate 不會考慮平台即服務 (PaaS) 或軟體即服務 (SaaS) 成本。Azure Migrate doesn't consider Platform as a service (PaaS), or Software as a service (SaaS) costs.

檢閱信賴評等 (以效能為基礎的評量)Review confidence rating (performance-based assessment)

每個以效能為基礎的評量都與信賴評等相關聯。Each performance-based assessment is associated with a confidence rating.

  • 信賴評等的範圍介於一顆星到五顆星之間 (一顆星是最低的,五顆星是最高的)。A confidence rating ranges from one-star to five-star (one-star being the lowest and five-star the highest).
  • 會根據計算評量所需的資料點可用性,為每個評量指派信賴評等。The confidence rating is assigned to an assessment, based on the availability of data points needed to compute the assessment.
  • 評量的信賴評等可協助您評估 Azure Migrate 提供的大小建議之可靠性。The confidence rating of an assessment helps you estimate the reliability of the size recommendations provided by Azure Migrate.
  • 信賴評等不適用於「現狀」的內部部署評量。Confidence rating isn't available for "as-is" on-premises assessments.

針對以效能為基礎的大小調整,Azure Migrate 需要下列項目:For performance-based sizing, Azure Migrate needs the following:

  • CPU 的使用量資料。Utilization data for CPU.
  • VM 記憶體資料。VM memory data.
  • 針對連結至 VM 的每個磁碟,它都需要磁碟 IOPS 與輸送量資料。For every disk attached to the VM, it needs the disk IOPS and throughput data.
  • 針對連結至 VM 的每張網路介面卡,Azure Migrate 都需要網路輸入/輸出。For each network adapter attached to a VM, Azure Migrate needs the network input/output.
  • 如果上述任一項目都無法使用,則大小建議 (以及信賴評等) 可能不可靠。If any of the above aren't available, size recommendations (and thus confidence ratings) might not be reliable.

根據可用資料點的百分比,下表摘要說明了可能的信賴評等。Depending on the percentage of data points available, the possible confidence ratings are summarized in the table.

資料點的可用性Availability of data points 信賴評等Confidence rating
0%-20%0%-20% 1 顆星1 Star
21%-40%21%-40% 2 顆星2 Star
41%-60%41%-60% 3 顆星3 Star
61%-80%61%-80% 4 顆星4 Star
81%-100%81%-100% 5 顆星5 Star

影響信賴評等的評量問題Assessment issues affecting confidence ratings

由於許多原因,評量可能沒有所有可用資料點:An assessment might not have all the data points available due to a number of reasons:

  • 您未在評估期間分析您的環境。You didn't profile your environment for the duration of the assessment. 例如,如果您建立的評量將效能持續時間設定為 1 天,您必須至少等待一天後再開始探索,才能收集到所有資料點。For example, if you create the assessment with performance duration set to one day, you must wait for at least a day after you start the discovery, or all the data points to be collected.
  • 部分 VM 在評量計算期間關閉。Some VMs were shut down during the period for which the assessment was calculated. 如果有任何 VM 電源在某段期間內關閉,Azure Migrate 就無法收集該期間的效能資料。If any VMs were powered off for part of the duration, Azure Migrate can't collect performance data for that period.
  • 部分 VM 是在評量計算期間內建立的。Some VMs were created in between during the assessment calculation period. 例如,如果您使用上個月的效能歷程記錄建立評量,但在一周前於環境中建立了多部 VM,則新 VM 的效能歷程記錄將不會持續整段期間。For example, if you create an assessment using the last month's performance history, but create a number of VMs in the environment a week ago, the performance history of the new VMs won't be for the entire duration.

注意

如果任何評量的信賴評等低於五顆星,請至少等待一天,讓設備分析環境,然後重新計算評量。If the confidence rating of any assessment is below five-stars, wait for at least a day for the appliance to profile the environment, and then recalculate the assessment. 否則,以效能為基礎的大小調整可能不可靠。If you don't performance-based sizing might not be reliable. 如果您不想重新計算,建議您變更評量屬性來切換至內部部署大小調整。If you don't want to recalculate, we recommended switching to as on-premises sizing, by changing the assessment properties.

使用相依性視覺效果建立群組Create groups using dependency visualization

除了手動建立群組之外,還可以使用相依性視覺效果建立群組。In addition to creating groups manually, you can create groups using dependency visualization.

  • 在執行評量前,若想要透過交叉檢查機器相依性的方式,對信賴等級較高的群組進行評估,通常會使用此方法。You typically use this method when you want to assess groups with higher levels of confidence by cross-checking machine dependencies, before you run an assessment.
  • 相依性視覺效果可協助您有效地規劃移轉至 Azure。Dependency visualization can help you effectively plan your migration to Azure. 它可協助您確保不會遺留任何項目,且當您在移轉至 Azure 時,不會發生意外的中斷。It helps you ensure that nothing is left behind, and that surprise outages do not occur when you are migrating to Azure.
  • 您可以探索所有需要一起移轉的交互相依系統,以及識別執行中的系統是否仍為使用者提供服務,還是應該解除委任而非移轉。You can discover all interdependent systems that need to migrate together and identify whether a running system is still serving users or is a candidate for decommissioning instead of migration.
  • Azure Migrate 使用了 Azure 監視器中的 [服務對應] 解決方案來啟用相依性視覺效果。Azure Migrate uses the Service Map solution in Azure Monitor to enable dependency visualization.

注意

在 Azure Government 中無法使用相依性視覺效果。Dependency visualization is not available in Azure Government.

若要設定相依性視覺效果,請將 Log Analytics 工作區與 Azure Migrate 專案建立關聯、在您要將相依性視覺化的電腦上安裝代理程式,然後使用相依性資訊建立群組。To set up dependency visualization, you associate a Log Analytics workspace with an Azure Migrate project, install agents on machines for which you want to visualize dependencies, and then create groups using dependency information.

與 Log Analytics 工作區建立關聯Associate a Log Analytics workspace

若要使用相依性視覺效果,請將 Log Analytics 工作區與移轉專案建立關聯。To use dependency visualization, you associate a Log Analytics workspace with a migration project. 您只能在建立移轉專案的相同訂用帳戶中,建立或連結工作區。You can only create or attach a workspace in the same subscription where the migration project is created.

  1. 若要將 Log Analytics 工作區連結至專案,請在 [概觀] > [基本資訊] 中,按一下 [需要設定]。To attach a Log Analytics workspace to a project, in Overview, > Essentials, click Requires configuration.
  2. 您可以建立新的工作區,或是連結現有的工作區:You can create a new workspace, or attach an existing one:
  • 若要建立新的工作區,請指定名稱。To create a new workspace, specify a name. 工作區會在與移轉專案相同之 Azure 地理區的區域中建立。The workspace is created in a region in the same Azure geography as the migration project.
  • 當您連結現有的工作區時,您能以和移轉專案相同的方式,從相同訂用帳戶中所有的可用工作區中挑選。When you attach an existing workspace, you can pick from all the available workspaces in the same subscription as the migration project. 系統只會列出那些在支援的服務對應區域中建立的工作區。Only those workspaces are listed which were created in a supported Service Map region. 若要連結工作區,請確定您有該工作區的「讀者」存取權。To attach a workspace, ensure that you have 'Reader' access to the workspace.

注意

您無法變更與移轉專案相關聯的工作區。You can't change the workspace associated with a migration project.

下載並安裝 VM 代理程式Download and install VM agents

在您設定工作區之後,您要在待評估的每部內部部署機器上下載並安裝代理程式。After you configure a workspace, you download and install agents on each on-premises machine that you want to evaluate. 此外,如果您的機器沒有網際網路連線,則需要下載並安裝 Log Analytics 閘道In addition, if you have machines with no internet connectivity, you need to download and install Log Analytics gateway on them.

  1. 在 [概觀] 中,按一下 [管理] > [機器],並選取所需的機器。In Overview, click Manage > Machines, and select the required machine.
  2. 在 [相依性] 資料行中,按一下 [安裝代理程式]。In the Dependencies column, click Install agents.
  3. 在 [相依性] 頁面上,在您要進行評量的每部 VM 上下載並安裝 Microsoft Monitoring Agent (MMA) 與相依性代理程式。On the Dependencies page, download and install the Microsoft Monitoring Agent (MMA), and the Dependency agent on each VM you want to assess.
  4. 複製工作區識別碼與金鑰。Copy the workspace ID and key. 在內部部署機器上安裝 MMA 時,需要用到這些識別碼與金鑰。You need these when you install the MMA on the on-premises machine.

注意

若要自動安裝代理程式,您可以使用部署工具 (例如 Configuration Manager) 或合作夥伴工具 Intigua,它提供適用於 Azure Migrate 的代理程式部署解決方案。To automate the installation of agents you can use a deployment tool such as Configuration Manager or a partner tool such a, Intigua, that provides an agent deployment solution for Azure Migrate.

在 Windows 電腦上安裝 MMA 代理程式Install the MMA agent on a Windows machine

在 Windows 電腦上安裝代理程式:To install the agent on a Windows machine:

  1. 按兩下下載的代理程式。Double-click the downloaded agent.
  2. 在 [歡迎] 頁面中按 [下一步]。On the Welcome page, click Next. 在 [授權條款] 頁面上,按一下 [我同意] 以接受授權。On the License Terms page, click I Agree to accept the license.
  3. 在 [目的地資料夾] 中,保留或修改預設的安裝資料夾 > [下一步]。In Destination Folder, keep or modify the default installation folder > Next.
  4. 在 [代理程式安裝選項] 中,選取 [Azure Log Analytics] > [下一步]。In Agent Setup Options, select Azure Log Analytics > Next.
  5. 按一下 [新增] 以新增 Log Analytics 工作區。Click Add to add a new Log Analytics workspace. 貼上您從入口網站複製的工作區識別碼和金鑰。Paste in the workspace ID and key that you copied from the portal. 按 [下一步] 。Click Next.

您可以從命令列或使用自動化方法 ( 例如 Configuration Manager ) 來安裝代理程式。You can install the agent from the command line or using an automated method such as Configuration Manager. 了解更多有關如何使用這些方法來安裝 MMA 代理程式。Learn more about using these methods to install the MMA agent.

在 Linux 電腦上安裝 MMA 代理程式Install the MMA agent on a Linux machine

在 Linux 電腦上安裝代理程式:To install the agent on a Linux machine:

  1. 使用 scp/sftp 將適當的套件組合 (x86 或 x64) 傳輸到 Linux 電腦。Transfer the appropriate bundle (x86 or x64) to your Linux computer using scp/sftp.

  2. 使用 --安裝引數安裝套件組合。Install the bundle by using the --install argument.

    sudo sh ./omsagent-<version>.universal.x64.sh --install -w <workspace id> -s <workspace key>

了解更多 MMA 支援的 Linux 作業系統清單。Learn more about the list of Linux operating systems support by MMA.

將 MMA 代理程式安裝在由 Operations Manager 監視的電腦上Install the MMA agent on a machine monitored by Operations Manager

對於受 System Center Operations Manager 2012 R2 或更新版本監視的電腦,不需要安裝 MMA 代理程式。For machines monitored by System Center Operations Manager 2012 R2 or later, there is no need to install the MMA agent. 服務對應與 Operations Manager MMA 整合,以收集必要的相依性資料。Service Map integrates with the Operations Manager MMA to gather the necessary dependency data. 深入了解Learn more. 必須安裝相依性代理程式。The Dependency agent does need to be installed.

安裝相依性代理程式Install the Dependency agent

  1. 若要在 Windows 電腦上安裝相依性代理程式,請按兩下安裝檔案,並遵循精靈的指示。To install the Dependency agent on a Windows machine, double-click the setup file and follow the wizard.

  2. 若要在 Linux 電腦上安裝相依性代理程式,請使用下列命令以 root 身分安裝:To install the Dependency agent on a Linux machine, install as root using the following command:

    sh InstallDependencyAgent-Linux64.bin

注意

若適用於 VM 的 Azure 監視器文章中提供了部署相依性代理程式時所需的系統必要條件和方法概觀,則這些文章也適用於「服務對應」解決方案。The Azure Monitor for VMs article referenced to provide an overview of the system prerequisites and methods to deploy the Dependency agent are also applicable to the Service Map solution.

建立具有相依性對應的群組Create a group with dependency mapping

  1. 安裝代理程式之後,請移至入口網站,然後按一下[管理] > [機器]。After you install the agents, go to the portal and click Manage > Machines.

  2. 搜尋安裝代理程式的機器。Search for the machine where you installed the agents.

  3. 機器的 [相依性] 資料行現在應會顯示為 檢視相依性The Dependencies column for the machine should now show as View Dependencies. 按一下資料行以檢視機器的相依性。Click the column to view the dependencies of the machine.

  4. 機器的相依性對應會顯示下列詳細資料:The dependency map for the machine shows the following details:

    • 往返機器的輸入 (用戶端) 和輸出 (伺服器) TCP 連線Inbound (Clients) and outbound (Servers) TCP connections to/from the machine
      • 未安裝 MMA 與相依性代理程式的相依機器會依連接埠號碼分組。The dependent machines that do not have the MMA and dependency agent installed are grouped by port numbers.
      • 已安裝 MMA 和相依性代理程式的相依機器會以不同的方塊顯示。The dependent machines that have the MMA and the dependency agent installed are shown as separate boxes.
    • 在機器內執行的處理序,您可以展開每個機器方塊,以檢視處理序Processes running inside the machine, you can expand each machine box to view the processes
    • 系統會顯示機器屬性,包括 FQDN、作業系統、MAC 位址。Machine properties, including the FQDN, operating System, MAC address are shown. 您可以按一下每個機器方塊來檢視詳細資料。You can click on each machine box to view details.
  5. 您可以按一下時間範圍標籤中的持續時間,以檢視不同持續期間的相依性。You can view dependencies for different time durations by clicking on the time duration in the time range label. 根據預設,範圍是一小時。By default the range is an hour. 您可以修改時間範圍,或指定開始和結束日期,以及持續時間。You can modify the time range, or specify start and end dates, and duration.

    注意

    支援最多一小時的時間範圍。A time range of up to an hour is supported. 使用 Azure 監視器可在較長的持續期間內查詢相依性資料 (部分機器翻譯)。Use Azure Monitor logs to query dependency data over a longer duration.

  6. 找出您需要劃為同一群組的相依機器後,請使用 Ctrl + 按一下來選取對應中的多部機器,然後按一下 [群組機器]。After you've identified dependent machines that you want to group together, use Ctrl+Click to select multiple machines on the map, and click Group machines.

  7. 指定群組名稱。Specify a group name. 確認 Azure Migrate 已探索到相依機器。Verify that the dependent machines are discovered by Azure Migrate.

    注意

    如果 Azure Migrate 未探索到相依機器,您就無法將它新增至群組。If a dependent machine is not discovered by Azure Migrate, you can't add it to the group. 若要將這類機器新增至群組,您必須使用 vCenter Server 中的正確範圍,再次執行探索程序,並確定 Azure Migrate 已探索到機器。To add such machines to the group, you need to run the discovery process again with the right scope in vCenter Server and ensure that the machine is discovered by Azure Migrate.

  8. 如果您需要建立此群組的評估,請選取核取方塊來建立新的群組評估。If you want to create an assessment for this group, select the checkbox to create a new assessment for the group.

  9. 按一下 [確定] 以儲存群組。Click OK to save the group.

一旦建立群組之後,建議您在群組的所有機器上安裝代理程式,並將整個群組的相依性視覺化來調整群組。Once the group is created, it is recommended to install agents on all the machines of the group and refine the group by visualizing the dependency of the entire group.

從 Azure 監視器記錄查詢相依性資料Query dependency data from Azure Monitor logs

服務對應擷取的相依性資料可供在與 Azure Migrate 專案相關聯的 Log Analytics 工作區中查詢。Dependency data captured by Service Map is available for querying in the Log Analytics workspace associated with your Azure Migrate project. 深入了解可在 Azure 監視器記錄中查詢的服務對應資料表。Learn more about the Service Map data tables to query in Azure Monitor logs.

執行 Kusto 查詢:To run the Kusto queries:

  1. 安裝代理程式之後,請移至入口網站,然後按一下 [概觀]。After you install the agents, go to the portal and click Overview.
  2. 在 [概觀] 中,移至專案的 [Essentials] 區域,然後按一下 [OMS 工作區] 旁提供的工作區名稱。In Overview, go to Essentials section of the project and click on workspace name provided next to OMS Workspace.
  3. 在 Log Analytics 工作區頁面上,按一下 [一般] > [記錄]。On the Log Analytics workspace page, click General > Logs.
  4. 撰寫您的查詢以使用 Azure 監視器記錄收集相依性資料。Write your query to gather dependency data using Azure Monitor logs. 在下一節中尋找範例查詢。Find sample queries in the next section.
  5. 按一下 [執行] 以執行查詢。Run your query by clicking on Run.

深入了解如何撰寫 Kusto 查詢。Learn more about how to write Kusto queries.

範例 Azure 監視器記錄查詢Sample Azure Monitor logs queries

以下是您可以用來擷取相依性資料的範例查詢。Following are sample queries you can use to extract dependency data. 您可以修改查詢以擷取慣用的資料點。You can modify the queries to extract your preferred data points. 您可以在這裡取得相依性資料記錄中的完整欄位清單。An exhaustive list of the fields in dependency data records is available here. 這裡尋找更多範例查詢。Find more sample queries here.

摘述一組電腦上的輸入連接Summarize inbound connections on a set of machines

連線計量 VMConnection 表中的記錄不代表個別實體網路連線。The records in the table for connection metrics, VMConnection, do not represent individual physical network connections. 將多個實體網路連線分組為一個邏輯連線。Multiple physical network connections are grouped into a logical connection. 深入了解有關實體網路連線資料如何匯總到 VMConnection 中的單一邏輯記錄。Learn more about how physical network connection data is aggregated into a single logical record in VMConnection.

// the machines of interest
let ips=materialize(ServiceMapComputer_CL
| summarize ips=makeset(todynamic(Ipv4Addresses_s)) by MonitoredMachine=ResourceName_s
| mvexpand ips to typeof(string));
let StartDateTime = datetime(2019-03-25T00:00:00Z);
let EndDateTime = datetime(2019-03-30T01:00:00Z); 
VMConnection
| where Direction == 'inbound' 
| where TimeGenerated > StartDateTime and TimeGenerated  < EndDateTime
| join kind=inner (ips) on $left.DestinationIp == $right.ips
| summarize sum(LinksEstablished) by Computer, Direction, SourceIp, DestinationIp, DestinationPort

摘述一組機器之間的輸入連接上傳送及接收的資料量Summarize volume of data sent and received on inbound connections between a set of machines

// the machines of interest
let ips=materialize(ServiceMapComputer_CL
| summarize ips=makeset(todynamic(Ipv4Addresses_s)) by MonitoredMachine=ResourceName_s
| mvexpand ips to typeof(string));
let StartDateTime = datetime(2019-03-25T00:00:00Z);
let EndDateTime = datetime(2019-03-30T01:00:00Z); 
VMConnection
| where Direction == 'inbound' 
| where TimeGenerated > StartDateTime and TimeGenerated  < EndDateTime
| join kind=inner (ips) on $left.DestinationIp == $right.ips
| summarize sum(BytesSent), sum(BytesReceived) by Computer, Direction, SourceIp, DestinationIp, DestinationPort

後續步驟Next steps

深入了解最新版本的 Azure Migrate。Learn about the latest version of Azure Migrate.