Hyper-V
  • 16 May 2022
  • 7 Minutes to read
  • Dark
    Light
  • PDF

Hyper-V

  • Dark
    Light
  • PDF

CTERA recommends making a backup of the 6.x edge filer before starting the migration.

After upgrading to a 7.x edge filer, you cannot downgrade it to a 6.x edge filer. CTERA recommends keeping the 6.x edge filer in reserve, in case the migration fails for any reason.

Note

Before migrating an edge filer to a 7.x CTERA Edge Filer, connect the 7.x edge filer to the same CTERA Portal as the 6.x edge filer.

Make sure both the CPU and memory settings for the 7.x edge filer are the same as for the 6.x edge filer.

Upgrade Prerequisite Check

At the end of the procedure, you should be able to connect to the 7.x edge filer using the same IP that was used to connect to the 6.x edge filer. Assigning this IP should be automatic as part of the procedure. In some cases, due to factors external to CTERA this is not he case. CTERA recommends making sure that the 7.x edge filer can be accessed with the IP as follows:

  • Shutdown the 6.x edge filer and start up the 7.x edge filer and set it up to use the IP Address, Subnet Mask, Default Gateway and DNS of the 6.x edge filer.
  • Make sure that the 7.x edge filer login page is accessible.
  • Shutdown the 7.x edge filer and power on the 6.x edge filer.

If the 7.x edge filer is not accessible, you need to check why not. Possible issues include the switch could only be given one MAC address, so the 7.x edge filer could not use the IP that had been assigned to the 6.x edge filer. For help, contact CTERA support.

Upgrade Procedure

To replace a 6.x edge filer with a 7.x edge filer:

  1. Delete any Hyper-V snapshots.
  2. Make a copy of the 6.x edge filer cloudsync.db and save it to a public share, so it is accessible.
  3. Login to the 6.x edge filer.
  4. In the CONFIGURATION tab, select Cloud Services > Status in the navigation pane, and then sign in to the portal.
  5. In the CONFIGURATION tab, select Cloud Drive > Cloud Drive in the navigation pane, and then click Suspend.
  6. If the edge filer is configured as a Sync Gateway (and not a Caching Gateway):
    1. Click Settings.
      The Cloud Drive Settings window is displayed.
      image.png
    2. Select the Advanced option and change the Operation Mode to Caching Gateway.
      image.png
    3. Click Save.
  7. The procedure continues with one of the following options:

When the cache size on the 6.x edge filer is small or a new edge filer can be populated in a few hours:

  1. Before powering on the 7.x edge filer, change the IP, so it is not the same as the 6.x edge filer IP.
  2. Power on the 7.x edge filer.
  3. Make sure both the 6.x and 7.x edge filers are connected to the same portal.
    • Check that the edge filer is connected to the portal in the both the 6.x and 7.x edge filers, under Cloud Services > Status.
  4. Wait for the 7.x edge filer to be fully synced with the portal. View the sync status in the Cloud Drive > Cloud Drive in the edge filer to determine when the syncing has completed.
    Note

    The time for the 7.x edge filer to be fully synced with the portal is dependent on how much data needs syncing.

  5. Validate that the 7.x edge filer has been synced correctly, by looking at the number of folders and files on both the 6.x and 7.x edge filers.
  6. Prevent user access to the 6.x edge filer.
  7. In the 6.x edge filer, in the CONFIGURATION tab, select Cloud Drive > Cloud Drive in the navigation pane, and then click Suspend.
  8. In the CONFIGURATION tab, select System > Configuration Tools in the navigation pane, and then click Export to save the edge filer configuration to an XML file.
  9. In the CONFIGURATION tab, select Cloud Services > Status in the navigation pane, and then sign out from the portal.
  10. Disconnect the 6.x edge filer.
Note

Do not delete the content of the 6.0.x edge filer but keep it for around 30 days so that it can be brought back on line as a failback or temporary backup.

  1. Continue with Complete the Upgrade.

When it will take a long time to populate the 7.x edge filer:

  • When the cache size is large.
  • The portal storage node is in a cloud, such as AWS or Azure.
  • There is high latency between the edge filer and the portal.
  1. In the CONFIGURATION tab, select System > Configuration Tools in the navigation pane, and then click Export to save the edge filer configuration to an XML file.
    image.png
  2. In the CONFIGURATION tab, select Cloud Services > Status in the navigation pane, and then sign out from the portal.
  3. Access the edge filer CLI interface.
    1. Select any option under System In the navigation menu (for example System > Network).
    2. In the address bar of your browser, delete the string that appears after the final ":" (for example, network if you clicked Network in the previous step) and type cli in its place.
    3. Press Enter.
      The CLI Execution page is displayed.
    4. Enter the following command: show /config/cloudsync/portalSettings
    5. Note the result of the command, and especially the number at the beginning.
      The result is similar to the following: "200.8.9d5c2940-7c6b-4a8a-bc1b-ef511fe97481"
  4. Shutdown the 6.x edge filer.
    1. In the status bar, click image.png and then click Shutdown.
      A confirmation message is displayed.
    2. Click Yes.
      The CTERA Edge Filer shuts down.
  5. Login to the Hyper-V console that manages both the 6.x edge filer and the 7.x edge filer.
    image.png
  6. Right-click the 6.x edge filer virtual machine and click Settings.
    image.png
  7. Select the hard drive, vhd file, under the SCSI controller and note the location of this drive. This is the drive with the edge filer data.
  8. Click Remove.
    image.png
    The drive is removed from the virtual machine only. It is not deleted.
  9. Click Apply and then OK.
  10. In the Hyper-V Manager, right-click the 7.x edge filer virtual machine and click Settings.
  11. Click SCSI Controller and click Add to add a hard drive.
    image.png
  12. Click Browse and go to the location of the vhd file from step 5 and click Open.
    image.png
  13. Click Apply and then OK.
  14. Right-click the 7.x edge filer virtual machine and click Start.
  15. Login to the 7.x edge filer and click Cancel when the Setup Wizard starts, with the Name this Edge Filer window.
  16. Continue with Complete the Upgrade.

Complete the Upgrade

  1. In the 7.x edge filer, in the Configuration view, select System > Configuration Tools in the navigation pane, and then click Import, to import the XML file you exported.
    image.png
    Note

    Fields that are no longer valid in the XML are removed and the import procedure reports warnings for these fields, which can be ignored.

  2. If you moved the vhd file, as described in When it will take a long time to populate the 7.x edge filer, access the edge filer CLI interface.
    1. Select any option under System In the navigation menu (for example System > Network).
    2. In the address bar of your browser, delete the string that appears after the final ":" (for example, network if you clicked Network in the previous step) and type cli in its place.
    3. Press Enter.
      The CLI Execution page is displayed.
    4. Enter the following command: show /config/cloudsync/portalSettings
    5. Make sure that the number at the beginning of the result is the same as the number returned when you previously executed the CLI show /config/cloudsync/portalSettings ("200..."). If the output does not show the same number, do not continue and contact CTERA Support.
  3. Refresh the user interface.
  4. In the Configuration view, select Cloud Drive > Cloud Drive in the navigation pane.
    image.png
  5. Click Unsuspend.

The database on the 7.x edge filer is built and files are synced from the portal.

Direct all the users to the 7.x edge filer. Users can now access and work on the 7.x edge filer.

If, for whatever reason, the migration did not complete successfully, you can try using the copy of cloudsync.db saved to a public share. If this does not work, revert back to the 6.x edge filer and contact CTERA support.


Was this article helpful?