cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to change where synced data is stored locally with the Desktop App

Ability to change where synced data is stored locally with the Desktop App

It would be nice to be able to change the location of locally stored data for the Desktop App from the default of %appdata%/Local/EgnyteDrive to another location.  That folder is on the C:\ drive for Windows machines and cannot be moved.  This becomes a problem when most of my users only have 256GB C:\ drives, and need to regularly have 50-100GB of data synced locally.  All of my users have at least a 2TB external drive which would be far better suited for storing such large amounts of data.

My understanding is that this cannot be changed at the moment.  This is a problem.

4 Comments
Employee Kash Uppuluri
Employee
Status changed to: Considering

Am moving this to considering while we figure out the specifics of how this could be implemented. The only consideration is that you will need to define this for each local user on the machine.

Am curious to hear thoughts on how you would want to define the location to store synchronized files and how you would secure the content (eg. prevent one user on the machine from seeing another users content).

Today, we store this data in the user's profile directory so there are protections in place to prevent users from seeing the synchronized content of other users unless specifically given permission to do so.

mcaruso
Resident

I too also have users who have a 256 gb ssd for software but an internal 2 tb/1tb drive for file storage. It would be great to use the larger internal drive d as a storage location (like what desktop sync already does).

Seth Rice
Resident

We are also hitting a brick wall, with the files being stored locally in the user's home directory. We tend to avoid loading up the OS critical partitions with files unrelated to running the OS. With this current setup of storing the files in the home directory of a user, it means a sync could potentially eat up all that space on the C: drive. For example, grinding the system to a halt once it fills up from an overzealous sync. The home folders for users on the system we are running the sync on, are very small in size as well. Otherwise we would have setup the home directories elsewhere by default.

I think for concerns about security, when it comes to someone changing the default option. Adding a flag that pops up and says something like this would likely suffice.
"Notice: You are changing the storage path to a location with permissions available to others. Please audit the security settings manually to ensure the permissions are as you intend."

For us the number of folks accessing the system this is syncing to is very limited. NTFS can also do a good job on windows of locking those limited users access down, for the folders and files in question. It's also something admins know they need to audit and change anyways when setting up a new share or storage volume from scratch.

Anthony_Seattle
Vigilante

I always try and leave my C drive clean and keep data on a secondary hard drive.

Some of our users also can work with very large files and the ability to define the offline folder location would keep perforamance up on these machines.