Azure, GCP, Nutanix, and OpenStack/KVM
  • 16 May 2022
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Azure, GCP, Nutanix, and OpenStack/KVM

  • 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 Procedure

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

  1. Make a copy of the 6.x edge filer cloudsync.db and save it to a public share, so it is accessible.

  2. Login to the 6.x edge filer.

  3. In the CONFIGURATION tab, select Cloud Services > Status in the navigation pane, and then sign in to the portal.

  4. In the CONFIGURATION tab, select Cloud Drive > Cloud Drive in the navigation pane, and then click Suspend.

  5. 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.
  6. 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.
  7. 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.
    The time for the 7.x edge filer to be fully synced with the portal is dependent on how much data needs syncing.

  8. 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.

  9. Prevent user access to the 6.x edge filer.

  10. In the 6.x edge filer, in the CONFIGURATION tab, select Cloud Drive > Cloud Drive in the navigation pane, and then click Suspend.

  11. 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

  12. In the CONFIGURATION tab, select Cloud Services > Status in the navigation pane, and then sign out from the portal.

  13. Disconnect the 6.0.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.

  14. 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.

  15. Refresh the user interface.

  16. In the Configuration view, select Cloud Drive > Cloud Drive in the navigation pane.
    image.png

  17. 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?

What's Next