ECS: GeoDrive: How to change a data cache drive

Before beginning, ensure that you have the following:

• Bucket name
• aws_access_key_id
• aws_secret_access_key
• Confirm that all files have been stubbed.   
• A Geodrive recovery is initiated to read the files back from ECS to the new-configured data path (Cache Directory).

2. Delete local files:  This only removes the GeoDrive managed files from the local cache. Files are still on ECS and are inaccessible until completion of reconfiguration after recovery.
3. Leave local files: Unlink files from ECS and delete the local stubs. (This option that is mostly used is when a customer is uninstalling GeoDrive and recalling all files from ECS to the local GeoDrive server.)
   1.  This guide illustrates Drive Letter Changes. Select "Delete local Files."
4. Reference:
   1. Page 37 in PDF Document
   2. Link: Uninstalling GeoDrive

 
 

Reference:

1. 1. Page: 11 in pdf
   2. Link:  Step 2 Configuring the GeoDrive Folder

1.  Required option: (must be configured) select "write all files and directories to cloud in lower case."  This helps alleviate performance and naming conflicts, UNIX, and LINUX file systems are case-sensitive. Constant conversion of files to match the Windows naming scheme has been seen to impact performance with frequent syncs.
2. Configure versioning if the site wants to use object versioning.

8. Configure "Advanced" options per customer requirements (see further below regarding Versioning).

1. Page: Page 14 in GeoDrive Documentation link
2. Link:  GeoDrive Advanced options field description

1. Reference - ECS Data Access Guide

1. 3. Add life cycle rules based on the customer's use case for:
   4.  Delete Markers 
   5.  Clean up for incomplete MPU (Multipart-Upload).