Scribd Logo
Upload

Welcome to Scribd!

  • 4 views

    Wegmans Revert Azure Migrate

    Uploaded by

    slinky1

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Wegmans Revert Azure Migrate

    Uploaded by

    slinky1
    4 views2 pages

    Original Title

    WegmansRevertAzureMigrate (3)

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    4 views2 pages

    Wegmans Revert Azure Migrate

    Uploaded by

    slinky1

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    Revert VMware to ASHCI Migration Procedure

    Monday, February 19, 2024 12:50 PM

    Failback or Revert Azure Migrated VM


    1. If a migrated VM to Azure stack needs to be reverted back to the Vmware copy, please follow these steps.
    a. If the Azure Stack VM never came online, and it's within the 2 hour migration maintenance window, then you can proceed with reverting.
    b. If the migrated VM did come online but had issues, then notify TechDB via Azure Stack HCI | Azure Stack Migrations | Microsoft Teams making them aware that this
    server must be reverted back. Wait for TechDB's consent to failing back to the VMware SQL VM.

    2. Login to Azure and PIM Elevate as Contributor and Windows Admin Center Admin roles
    3. Must use this link to access "Azure Migrate" private Preview https://aka.ms/HCIMigratePPVMW
    4. If the "Complete Migration" button was never triggered for this VM, then do so now so it gets removed from the Migration Proj ect.
    5. Power down the Azure Stack VM in Failover Cluster Manager
    6. Go into VMware vCenter and locate the old VM
    a. Rename the VM back to the original name by removing the "ONSTACK-" from the name
    b. Edit the settings of the VM so the network connection is checked to online at power up
    c. Power up the VM
    d. Confirm the VM is powered up and pingable
    e. Notify TechDB via Azure Stack HCI | Azure Stack Migrations | Microsoft Teams of the completed failback

    Cleaning up Azure Stack failed Migration


    1. In order to begin a new fresh migration process of the failed VM, you must perform the following cleanup steps.
    a. Login to Azure and PIM Elevate as Contributor and Windows Admin Center Admin roles
    b. Select Azure Stack HCI Cluster
    c. Click on "Virtual Machines" on the left side menu
    d. Locate the stopped VM that failed to migrate and confirm that it is still shutdown in Windows Failover Cluster Manager (Please be very careful to select the correct VM)
    e. Click "Delete" (This will delete the VM from the Azure Portal as well as remove it from Windows Failover Cluster Manager and Hyper-V)

    2. Deleting the VM does not remove the disks, so this must be done manually.
    a. Using windows explorer from your Admin Workstation, browse to each path below and search for the name of the reverted VM
    \\bdc-hci-c1-01\c$\ClusterStorage\UserStorage_1
    \\bdc-hci-c1-01\c$\ClusterStorage\UserStorage_2
    \\bdc-hci-c1-01\c$\ClusterStorage\UserStorage_3
    \\bdc-hci-c1-01\c$\ClusterStorage\UserStorage_4

    b. Delete every VHDX you find prefixed with your VM name (TST-MIM16-DB-01) The system will not allow you to delete any VHDX's that are in use so if the delete
    succeeds, then you found the correct VHDX's. Also note that the VHDX's can be stored on different UserStorage volumes, especially the newly created 4K S disk, so be

    General Information Page 1


    succeeds, then you found the correct VHDX's. Also note that the VHDX's can be stored on different UserStorage volumes, especially the newly created 4K S disk, so be
    sure to search all 4 paths above.

    3. Update the SQLMigrationTracker spreadsheet with a new planned migration date and remove any Done progress you previously made .
    4. You can now re-setup the Azure Migration process for this VM.

    General Information Page 2

    You might also like