AWS

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.

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.
      
   2. Select the Advanced option and change the Operation Mode to Caching Gateway.
      
   3. Click Save.
6. 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. See When the cache size on the 6.x edge filer is small or a new edge filer can be populated in a few hours.
   • When it will take a long time to populate the 7.x edge filer. See When it will take a long time to populate the 7.x edge filer.

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. In the AWS Management Console select Services and under Under Compute, select EC2.
   The EC2 Dashboard is displayed.
2. In the navigation pane, click Instances > Instances.
   The Instances screen is displayed.
3. Right-click the 7.x edge filer Instance ID and select Start instance from the drop-down menu.
4. 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.
5. Wait for the 7.x edge filer to be fully synced with the portal global file system. 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 global file system is dependent on how much data needs syncing.

6. 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.
7. Prevent user access to the 6.x edge filer.
8. In the 6.x edge filer, in the CONFIGURATION tab, select Cloud Drive > Cloud Drive in the navigation pane, and then click Suspend.
9. 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.
10. In the CONFIGURATION tab, select Cloud Services > Status in the navigation pane, and then sign out from the portal.
11. Disconnect the 6.x edge filer.

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.
   
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 and then click Shutdown.
      A confirmation message is displayed.
   2. Click Yes.
      The CTERA Edge Filer shuts down.
5. From your Amazon Web Services account, sign in to the AWS Management Console.
6. In the AWS Management Console select Services and under Compute, select EC2.
   The EC2 Dashboard is displayed.
7. In the navigation pane, click Instances > Instances.
   The Instances screen is displayed.
8. In the lower half of the screen, click the Storage tab.
   
9. Click the data volume.
   Note

   The volume used for the edge filer software is 15GB. Do not choose this volume.

   The volume and volume details are displayed.
10. Make a note of the volume ID and name.
11. Click Actions > Detach Volume.
12. Click Yes, Detach to confirm detaching the volume.
13. In the navigation pane, click Elastic Block Store > Volumes.
14. Select the volume you detached.
15. Click Actions > Attach Volume.
    The Attach Volume window is displayed.
    
16. In the Instance field enter the edge file instance ID or name. As you enter characters he possible options are displayed.
17. Click Attach.
18. In the navigation pane, click Instances > Instances.
    The Instances screen is displayed.
19. Right-click the 7.x edge filer Instance ID and select Start instance from the drop-down menu.
20. 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.
    
    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.

21. Refresh the user interface.
22. In the Configuration view, select Cloud Drive > Cloud Drive in the navigation pane.
    
23. 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..