Timeline for Unix/Linux backup account that does not update LAST ACCESS files metadata
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 27, 2019 at 17:16 | answer | added | Chris Davies | timeline score: 0 | |
| Jun 27, 2019 at 17:08 | comment | added | Chris Davies | Please be patient! I don't know what timezone you're in, but the west coast USA is only just starting, and Australia/China/New Zealand, etc. are (probably) still asleep. Those in UK/Europe will have been working all day and may only now be able to start considering a response to your question. | |
| Jun 27, 2019 at 16:20 | comment | added | Simon Favre | Anyone ? Am I all alone with this question as a lot of people is concerned ? :) | |
| Jun 27, 2019 at 8:04 | history | edited | Simon Favre | CC BY-SA 4.0 |
added 454 characters in body
|
| Jun 27, 2019 at 7:13 | comment | added | Simon Favre | Thanks for your answer roaima. Actually, here is the deal : - The Unix/Linux server is hosting CIFS shares and is a production server accessed by other systems/services. - A Windows server connecting to the Unix/Linux one thru CIFS shared will open files to backup/search in their content. - The goal is to avoid update LAST ACCESS metadata on opened files because there might be an archiving solution that would rehydrate files and/or consider files as being updated. I hope it's better with these informations | |
| Jun 27, 2019 at 6:35 | review | First posts | |||
| Jun 27, 2019 at 6:43 | |||||
| Jun 27, 2019 at 6:30 | history | asked | Simon Favre | CC BY-SA 4.0 |