Thank you you both GertjanA and plaudone1 for taking the time to reply in good detail.
As an example, so I understand you correctly;
- A file is created on the \\server\share1
- EV archives file based on archive criteria
- Replaces file with a placeholder
- 6 months later, user opens the placeholder to restore the file
- File is successfully restored by EV and opened by end user.
- The file is then moved to a new location \\server\share2
- EV then runs the archive task
- File is then rearchived, but the file location in the EV DB stays as the original share \\server\share1 ?
I have searched for one of the files, and as you mention, it has been restored to what looks like its original location. Is there an attribute attached to a file that tells EV 'this file has already been archived and lives here in the DB' (technical way of putting it!) ?
My concern now, is that if User A has spent 2 years reorganising folder structures in the share that EV is archiving, then I come along and restore EV data, EV then restores as it was 2 years ago, users are not going to be able to find there data as its technically undoing the folder structure and reverting back 2 years.
Please correct me if I am wrong...
Many thanks in advance.