Skip to main content
ONTAP tools for VMware vSphere 10

Migrate the VASA Provider and update the SRA in ONTAP tools

Contributors netapp-jani jani
PDFs

Use this task to migrate the VASA Provider from ONTAP tools for VMware vSphere 9.xx to 10.6 and update the Storage Replication Adapter (SRA) on the VMware Live Site Recovery appliance.

Migrate the VASA Provider

Before you begin

Ensure that ONTAP tools for VMware vSphere 10.6 is deployed and that the target vCenter Server and storage backends are ready for migration.

  1. To enable Derby port 1527 on the existing ONTAP tools for VMware vSphere appliance, enable the root user, log in to the CLI through SSH, and run the following command:

    iptables -I INPUT 1 -p tcp --dport 1527 -j ACCEPT

  2. Deploy the OVA for ONTAP tools for VMware vSphere 10.6.

  3. Add the vCenter Server instance that you want to migrate to ONTAP tools for VMware vSphere 10.6. Refer to Add a vCenter Server instance for more information.

  4. Onboard the storage backend locally through the vCenter Server APIs for the ONTAP tools plug-in. Refer to Add a storage backend using the vSphere Client interface for more information.

  5. Obtain an access token to authenticate REST API requests. Use the following example, replacing the variables with values specific to your environment.

    curl --request POST \
  --location "https://$FQDN_IP_PORT/virtualization/api/v1/auth/vcenter-login" \
  --header "Content-Type: application/json" \
  --header "Accept: */*" \
  -d '{"username": "$MYUSER", "password": "$MYPASSWORD", "vcenter hostname": "$MYVCENTER"}'

    Copy and save the access token returned in the response.

  6. Issue the following migration API call from Swagger or Postman.

    curl -X POST `\https://xx.xx.xx.xx:8443/virtualization/api/v1/vcenters/{vcguid}/migration-jobs`

    You can access Swagger through this URL: https://$FQDN_IP_PORT/, for example: https://10.67.25.33:8443/.

    HTTP method and endpoint

    This REST API call uses the following method and endpoint.

    HTTP method

    Path

    POST

    /api/v1

    Processing type

    Asynchronous

    Curl example

    curl -X POST 'https://<OTV-NG-IP>:8443/virtualization/api/v1/vcenters/<vcguid>/migration-jobs' \
  --header 'x-auth: <auth_token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "otv_ip": "xx.xx.xx.xx",
    "vasa_provider_credentials": {
      "username": "xxxxx",
      "password": "******"
    },
    "database_password": "******"
  }'

    Request body for other release migration:

    {
  "otv_ip": "xx.xx.xx.xx",
  "vasa_provider_credentials": {
    "username": "xxxxx",
    "password": "*******"
  }
}

    JSON output example

    The system returns a job object. Save the job identifier to use it in the next step.

    {
  "id": 123,
  "migration_id": "d50073ce-35b4-4c51-9d2e-4ce66f802c35",
  "status": "running"
}

Check migration status

  1. Use the following URI in Swagger to check the status:

    curl `\https://xx.xx.xx.xxx:8443/virtualization/api/jobmanager/v2/jobs/<JobId>?includeSubJobsAndTasks=true`

    Use the 'id' value returned from the migration job in the previous step. After the job completes, review the migration report in the job response.

Register and verify the migrated VASA Provider

  1. Register the VASA Provider with ONTAP tools for VMware vSphere. For instructions, see Register the VASA Provider.

  2. Verify the VASA Provider registration:

    1. In the vSphere Client, navigate to the vCenter Server.

    2. Select Configure > Storage Providers.

    3. Confirm that the VASA Provider registered in the previous step appears online.

  3. Stop ONTAP tools for VMware vSphere storage provider 9.10/9.11/9.12/9.13 VASA Provider service using these steps:

    1. In ONTAP tools 9.x, open the web console.

    2. Log in using the maint credentials.

    3. Enter 1 to select the Application Configuration menu.

    4. Enter 5 to stop the VASA Provider and SRA services.

    5. In the vSphere Client, navigate to the vCenter Server and select Configure > Storage Providers.

    6. Select the offline VASA Provider for ONTAP tools 9.x and select Remove.

      After the old VASA Provider is stopped, the vCenter Server fails over to ONTAP tools for VMware vSphere. All datastores and VMs become accessible and are served from ONTAP tools for VMware vSphere.

  4. Migrated NFS and VMFS datastores appear in ONTAP tools for VMware vSphere 10.6 after the datastore discovery job, which may take up to 30 minutes. Check their visibility on the overview page.

Run the patch migration

  1. Perform the patch migration API call using Swagger or Postman:

    HTTP method and endpoint

    This REST API call uses the following method and endpoint.

    HTTP method

    Path

    PATCH

    /api/v1

    Processing type

    Asynchronous

    Use the following URI in Swagger:

    curl  -X PATCH  `\https://xx.xx.xx.xx:8443/virtualization/api/v1/vcenters/<vcenter_id>/migration-jobs/<migration_id>`

    HTTP method and endpoint

    This REST API call uses the following method and endpoint.

    HTTP method

    Path

    PATCH

    /api/v1

    Processing type

    Asynchronous

    Use the following URI in Swagger:

    curl  -X PATCH  `\https://xx.xx.xx.xx:8443/virtualization/api/v1/vcenters/<vcenter_id>/migration-jobs/<migration_id>`

    Curl example

    curl  -X PATCH  `\https://xx.xx.xx.xx:8443/virtualization/api/v1/vcenters/56d373bd-4163-44f9-a872-9adabb008ca9/migration-jobs/d50073ce-35b4-4c51-9d2e-4ce66f802c35`

    JSON output example

    {
  "id": 123,
  "migration_id": "d50073ce-35b4-4c51-9d2e-4ce66f802c35",
  "status": "running"
}
    Note Use the 'migration_id' value returned in Step 7 as <migration_id> in the PATCH API call. The request body is empty for patch operation.
    Note UUID is the migration UUID returned in response to the post-migrate API.

After running the patch migration API, all VMs comply with the storage policy.

After migration

After completing the migration and registering ONTAP tools 10.6 with vCenter Server, follow these steps:

  • Wait for Discovery to complete, and the system refreshes the certificates automatically on all the hosts.

  • Wait before starting datastore and virtual machine operations. The waiting time depends on the number of hosts, datastores, and virtual machines. If you do not wait, you might see occasional failures.

After upgrading, if the virtual machine's compliance state is outdated, reapply the storage policy using the following steps:

  1. Go to the datastore and select Summary > VM Storage policies.

  2. The system shows the compliance status under VM storage policy compliance as Out-of-date.

  3. Select the Storage VM policy and the corresponding VM.

  4. Select Apply.

  5. The compliance status under VM storage policy compliance shows as compliant.

Related information

Update the storage replication adapter (SRA)

Before you begin

Before you migrate the SRA, verify the following:

  • In the recovery plan, the protected site is the location where the VMs are currently running, and the recovery site is the location where the VMs will be recovered.

  • In the VMware Live Site Recovery appliance interface, one site appears in the protected state and the other site appears in the recovery state.

  • In the recovery plan, the CLEANUP and REPROTECT buttons are disabled, and the TEST and RUN buttons remain enabled.

Note Do not begin migration if the failover has been completed but the re-protection is pending. Ensure that the re-protection process is completed before proceeding with the migration. If a test failover is in progress, clean up the test failover and start the migration.

  1. Follow these steps to delete the ONTAP tools SRA adapter for VMware vSphere 9.xx in VMware Site Recovery:

  2. Go to the VMware Live Site Recovery configuration management page.

    1. Go to the Storage Replication Adapter section.

    2. From the ellipsis menu select Reset configuration.

    3. From the ellipsis menu select Delete.

  3. Perform these steps on both protection and recovery sites.

    1. Enable ONTAP tools for VMware vSphere services

    2. Configure ONTAP tools for VMware vSphere 10.6 SRA adapter using the steps in Configure SRA on the VMware Live Site Recovery appliance.

    3. On the VMware Live Site Recovery interface, run Discover Arrays and Discover Devices. Confirm devices display as before migration.