VMware Aria Suite Lifecycle 8.16

8.18 8.16 8.14 8.12
Português (Brasil) 简体中文 Deutsch Español Français Italiano 日本語 한국어 Nederlands 繁體中文 English

Migrate content from
VMware Aria Operations
 SaaS to
VMware Aria Operations
 on-prem

As a
VMware Aria Suite Lifecycle
 user, you can use the Migration Service to migrate contents from your
VMware Aria Operations
 SaaS deployment to your
VMware Aria Operations
 on-prem deployment. The following procedure shows how to migrate your content.
Verify that a
VMware Aria Suite Lifecycle
 administrator has performed the prerequisites listed on Using the Migration Service in VMware Aria Suite Lifecycle.
  1. On the
    My Services
     dashboard, click
    Migration Service
    .
  2. Click
    New Migration
    .
    A a series of migration configuration pages appear. After completing the information on each page, click
    Next
    .
    1. Enter the information for the Infrastructure.
      • Type a Migration name.
      • For Product Type, select
        VMware Aria Operations
        .
      • For Cloud Service, select the SaaS Content Management endpoint.
      • For On-Prem Destination, select the on-prem endpoint.
        If the product does not exist on-prem, click the
        +
         sign to deploy the product and then return to the Migration Service once the deployment has completed.
    2. Enter the information for Configuration.
      • Select a source user, such as your username.
      • Select a destination user, such as
        admin
        .
      • Select the destination password and click
        Validate
        .
        If the password does not exist, click the
        +
         sign to create a password and then select it.
      • Under
        Collector Configuration
        , if you want to deploy additional collectors, you can map existing cloud collectors to on-prem cloud collectors by deploying new on-prem
        VMware Aria Operations
         collectors.
    3. Enter the information for Content Management.
      • For Export, select all content types you would like to export from SaaS to on-prem.
      • For Import, select the behavior in case of a conflict.
        • Skip item(s)
        • Overwrite existing content
      • For
        Encrypt Password
        , you must set up a new password to export data for configurations such as integration accounts, http proxies, outbound settings, users, and authentication sources that have sensitive information. The password should be at least 14 characters long.
        If the password does not exist, click the
        +
         sign to create a password and then select the locker object.
    4. Enter the information for Integrations.
      • For User Details, provide user information necessary for downloading management packs from the VMware Marketplace during migration, that will be installed on the on-prem
        VMware Aria Operations
         instance.
      • Integration Details provides you insight on the adapters that are applicable, installed, unavailable and not applicable for your on-prem product.
        • Available Integrations. Shows all available and activated integrations from on-prem
          VMware Aria Operations
           instance. If any Management Packs are missing or not installed, they will be installed when the migration is triggered.
        • Installed Integrations. Integrations that are installed on the on-prem
          VMware Aria Operations
           instance.
        • Unsupported. Integrations that are not applicable for the on-prem
          VMware Aria Operations
           instance.
        • Installation Unavailable. Integrations that are not available for installation through
          VMware Aria Suite Lifecycle
          .
    5. Perform pre-validations to assess preparedness before migration.
      Click
      Validate
       to begin:
      • Version Check. Ensures
        VMware Aria Operations
         on-prem version is 8.14 or later. A best practice is to use the latest version.
      • Health Check. Checks to confirm that the on-prem
        VMware Aria Operations
         instance is healthy.
      • Sizing Compatibility Check. Checks for deployment sizing compatibility between the source and the destination, considering the count of objects and metrics.
        If the Sizing Compatibility Check fails, use
        VMware Aria Suite Lifecycle
         to perform a vertical scale up and run the pre-check again.
    6. Review the Summary page.
    7. Click
      Finish
       to start the migration.
To monitor the migration, click
Migration Service
Migration List
 and review the list of migrations.
Check information in the
Request Status
,
Migration Status
, and
Content Detail
 columns for the migration that you submitted.
  • Clicking a status under
    Request Status
     or
    Migration Status
     opens a
    Request Details
     page that displays the stages of the request submitted.
  • Clicking the info icon next to the status under
    Migration Status
    , opens a window that displays the status of the migration. If you select the
    click here
     link in the window, you are directed to log in to
    VMware Aria Operations
    . An
    Administration
    Content Management
     page automatically opens with a summary of the content migrated on the
    Import
     tab.
  • Clicking
    View
     under
    Content Detail
     opens the Content Pipeline details page and describes the status of the pipeline.

Content feedback and comments