Question

12 Followers
18
89b28f35085b7ac8f7548f500441b862?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

Preserve File Time and Date Stamps When Uploading Files via Web Interface

This is really a BIG DEAL.  I have NAS Local Cloud set up and it is great, however the web interface which I hoped I could use often with remote workers who wouldn't be accessing my local network is something I don't really want to use because file date and time stamps are modified any time anything is uploaded via the web interface.  Thus, I basically have to tell all users to never use the web interface, but only the local cloud for file uploading. If I have to do that, whats the point of the service versus just using an online back up service.

Since uploading is an important aspect of web storage, one of the major benefits of Egnyte is rendered semi useless because file dates can't be preserved when uploaded. 

Please make this a top priority.  I hope you can fix this soon as it will really be a major benefit to business users.

Steve Davis

Please sign in to add your answer.

14 answers

0
C25e4b5cfdee9ab86399fd24ddf3084c?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

I completly agree with Steve's comments.  We plan on assigning all our contractors standard user status making use of the local cloud impossible for them.  Timestamp preservation is very important.

Neil Passman

Neil Passman
0
004

Steve and Neil,

I have discussed your suggestion with products and I have two questions for you.

  1. If we do this the multi-version display will always show the latest version first (in terms of date). Is that alright?

  2. If your version policy is set to maintain the two latest versions, that will kick in when uploading. So, users need to be aware of how many versions they have set to save. Will this be too confusing for users?

For example, if one document (abc.doc) is uploaded on 9/18/10 it will be saved as the original. If another version is uploaded and dated 9/16/10, it will appear as a second version below the 9/18/10 document.

However, if a user's version policy is set to two, and a third 'abc.doc' dated 9/14/10 is uploaded, that version will automatically be deleted when the previously set version policy kicks in.

Thank you for your feedback and I look forward to hearing from you.

Emily Ganz
0
C25e4b5cfdee9ab86399fd24ddf3084c?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

Emily,

I don’t know how Egnyte handles file versioning but under the Windows NTFS and Unix file systems you are not allowed to have two or more files of the same name in the same directory. Using your example, if I attempted to copy abc.doc dated 9/14/10 to a directory that already contained abc.doc dated 9/18/10, Windows 7 would ask me to select one of the following options:

 

  • Copy and Replace (Replace the file in the destination folder with the file you are copying)

 

  • Don’t copy (No files will be changed. Leave this file in the destination folder)

 

  • Copy, but keep both files (The file you are copying will be renamed "abc (2).doc")

If I selected the third option I would have two files in the directory:

 

  • abc.doc (dated 9/18/10)

 

  • abc (2).doc (dated 9/14/10

Versioning occurs if I open abc.doc, make some modifications to this file and save it. In Windows 7, versioning is handled as part of the Backup and Restore function which would place a copy of the previous version of the file in a hidden area of the file system. The current version could then be replaced by the previous version by using the file properties screen.

Neil Passman

 

 

 

 

 

 

Neil Passman
0
Elogo

Hi Neil, Egnyte does not let you over write the file. It creates a new version when an existing file is modified. The versioning logic in the UI shows files based on date of modification, the latest one first. So the question is - if we allow file dates to be maintained during upload and say your account version policy is set by your admin to 2, the file uploaded on 09/1/4/10 may disappear due to the policy control. Will you be ok with that?

Jack Williams
0
C25e4b5cfdee9ab86399fd24ddf3084c?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

Hi Jack

My suggestion would be to provide the user with a screen giving him or her options as to the disposition of the files. Options could be similar to the ones provided by Windows 7 during a file copy and where there already is a file in the target directory with the same name. This would allow the user to even overwrite a newer version of the file with an older version if that is his or her choice.

I need to emphasize that timestamps are an essential part of the way we do business since our customer base operates in highly regulated industries and traceability is very important.

At the moment it appears there are two workarounds to this issue that we have tested and appear to work. Using the Local Cloud for file transfers as you suggested and transferring files and directories in a "zip" format (one of my system architects came up with this). This last option has the benefit of being usable with your web interface.

Neil Passman

Neil Passman
0
675941d9531da4e0b11bb2ae5cb63f25?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

The backup utility needs a way of being aware of and preserving date stamps, as well.  As is, every time it runs, it thinks it has a new version of a file (because the date today is not = to yesterday), so it writes a new "version" of the same file, whether it has actually been changed or not.  This quickly wipes out any real historical versions of the document and you wind up N copies of the same document, even if nothing in the document has actually changed.

Plus, when you go to restore an old document, you absolutely have to be able to figure out which one is the one from last month that you actually need.  With the date being set to when it got backed up, you can't tell.  Backup is almost useless this way.

Dean Black
0
A01e49606990342340438c8b9f9f4835?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

I completely agree with these comments.  The fact that Egnyte changes the file modified date to the date of upload when using the web interface or FTP renders those upload mechanisms worthless.  Egnyte should be preserving the last 5-10 versions of every file, but it all needs to be based on the file's actual creation/modification dates.  The upload date should be tracked in a separate field.

Eric Gurry
0
Elogo

We are working on adding an option in the web based java multi-uploader and in ftp upload, to preserve the time-stamps.

Jack Williams
0
675941d9531da4e0b11bb2ae5cb63f25?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

Hopefully this feature that you speak of, Jack, will also apply to the timestamps on the backups, as well.  It's the same timestamp manipulation problem across the board: in all of the interfaces to the Egnyte file store, there needs to be an option that allows the preserving of the source file's timestamp.

Dean Black
0
Elogo

Backup and Personal Local Cloud preserve the time stamp. Therefore, I am surprised by your experience. Can you please explain further?

Jack Williams
0
57ae7ba61213c9eca82090f38630e553?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

In Windows, if I copy a file from one folder to another, the date-time stamp is retained.  This is exactly what should happen when files are copied onto Egnyte.

Charles Groover
0
2fd6a2e533d4044757fd13d31e309613?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

We are in the process of deploying eGnyte in our small firm and I'm deeply concerned about the issues discussed here in this forum.  Preserving the original Date Created and Date Modified attributes is business critical.  Is there a road map and projected release date for the option to preserve time-stamps?  This is going to be a disastrous migration if we can't rely on time stamps, regardless of versioning. 

Terry Baresh
0
Egnyte-spark-logo

Terry - Please note that you can migrate files using specific upload methods and timestamps will be preserved.  Customers who want timestamps preserved usually use the Local Cloud or the Migration service.  Please check this link for more details. If you need specific guidance on your account, please log a ticket in our helpdesk and we will be happy to assist.

https://helpdesk.egnyte.com/entries/60368-file-upload-download-how-to-preserve-original-date-times-when-moving-files-to-egnyte

thanks, 

Rajesh

Rajesh Ram
0
B1c473a924d8c59704b39d8664f40087?default=https%3a%2f%2fassets.zendesk.com%2fimages%2fframe_user

I think the problem is if the file doesn't exist on the cloud server, and you upload an old file, this is marked with a new timestamp on the cloud, that it is diferent on the local server, causing an incoherence. I think if the file is changed when it is already in the cloud, logicaly, it must be stamped with the actual time, because if it is not, the versioning will not work. 

Suggerence:

When you upload a new file, if it doesn't exist in the cloud server, you would keep the original timestamp, and if it already exists in, then use the actual date.

So, this way you can upload the inital data using any available ways (web, java applet, ftp, webdav, etc) but you can provide versioning without modifications.

 

Fco. Javier

FRAMENET 3

Fco Javier Moreno