CobianSoft

I run into this problem recently but do not understand why it happen ( started with version 11 but still present with reflector )
I have a scheduled job that start at 22:00 and ends about one hour and hal later , this job do a full backup to a NAS share .
The job create a folder named docs with the date like "doc-2021-12-01"
At the end of the job i will expect to have the date/time of this folder with the last date/time it was accessed , or at least when the job is started , but all the folder have the same date/time like this :

2021-11-18 13:04 doc_2021-11-24/
2021-11-18 13:04 doc_2021-11-25/
2021-11-18 13:04 doc_2021-11-26/
2021-11-18 13:04 doc_2021-11-29/
2021-11-18 13:04 doc-2021-11-30/
2021-11-18 13:04 doc-2021-12-01/
2021-12-02 11:57 doc-2021-12-02/

On the example above the ones which have the "_" between the name and the date are the old ones from V11 the new one with "-" were done with Reflector

In the last row there is an example of a running backup that have the correct date of the time the job is started but at the and of the process the data will transform as this :

2021-11-18 13:04 doc_2021-11-24/
2021-11-18 13:04 doc_2021-11-25/
2021-11-18 13:04 doc_2021-11-26/
2021-11-18 13:04 doc_2021-11-29/
2021-11-18 13:04 doc-2021-11-30/
2021-11-18 13:04 doc-2021-12-01/
2021-11-18 13:04 doc-2021-12-02/

How can this happen ?

Are you using some parameter on your destination? Or have you altered the date time format on the advanced tab? As default, it should include the time stamp as well.

Hi Luis

I changed the timestamp format as : yyyy-MM-dd
And checked the "Do not separate the Timestamp ..."

As i can understand it looks like it take the time job had modified ( or at least is a great coincidence )
I can remember on 18/11 i modified the Job , yesterday i modified it again and the result is this :

2021-12-02 14:46 doc_2021-11-24/
2021-12-02 14:46 doc_2021-11-25/
2021-12-02 14:46 doc_2021-11-26/
2021-12-02 14:46 doc_2021-11-29/
2021-12-02 14:46 doc-2021-11-30/
2021-12-02 14:46 doc-2021-12-01/
2021-12-02 23:25 doc-2021-12-02/

In the las row there is a different date because i made a script to run at the end of the job that do a "touch" of the folder
But the question is why it looks like it change the date of all folder in this share ?

The date taken is the date (and time) exactly when the task starts to copy the files. Så the last directory is created after midnight (2021-12-02)

AndreaZCS wrote: ↑02 Dec 2021, 12:23 ...
At the end of the job i will expect to have the date/time of this folder with the last date/time it was accessed ,
...

Apologies if this is not relevant ... Windows stopped updating the Last Accessed date several versions ago ...

https://www.opentechguides.com/how-to/a ... -time.html

Yes, in such case the Last modified should be used.

cobian wrote: ↑03 Dec 2021, 16:00 The date taken is the date (and time) exactly when the task starts to copy the files. Så the last directory is created after midnight (2021-12-02)

May be i did not explain it well ....
The problem is not the name of the folder that's OK.
The problem , for me , is the date/time the OS of the NAS sees the folder of the job
The above backup was done by a job started yesterday 05/12 at 04:30 AM , normally the job should last about 1:30

this is what i can see today if i issue an 'ls -l' from the shell of the NAS :2021-11-18 13:04 doc-2021-12-05/

So i will expect to see the folder date/time something like this :

2021-12-05 04:30 doc-2021-12-05/ or at least 2021-12-05 06:00 doc-2021-12-05/

I am sure at the start of the job the folder has the correct date/time of the creation , but at the end of the job , as you can see , have this date/time : 2021-11-18 13:04

The job , we can see from the name of the folder , was done "doc-2021-12-05"
Why at the end it have this date : 2021-11-18 13:04

And is the software that do this ...

These are 2 different times. The first one (the ACTUAL) time of the folder is the time the folder was created (often the first thing that's done). The second date (the NAME of the folder) is taken from the time the files are being copied. There could be some discrepancy here as we are seeing.

Yes I know ,
But the real question is why it looks like the program at the end of the job change the time property of the folder to a specifical date/time ?

Options-Engine-Copy timestamps is checked by default.