ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 232
- Reaction score
- 5
- Points
- 0
Several questions here regarding modtime and change of status time (ctime) updates for directories and files. This is on Linux.
I run something like this:
q backup /var/cache/man/ -subdir=yes -fromdate=2020-02-19
I see a number of files reported. All good. I then run this:
q backup /var/cache/man/index.db -fromdate=2020-02-19 -detail -inactive
I see only one entry with a backup date of 2019-10-03 18:25:16 and the following additional time details:
Modified: 2018-11-03 03:41:47 Accessed: 2018-11-03 03:41:47 Inode changed: 2018-11-03 03:41:47
This concurs with the ctime and mtime (`ls -lcd --full-time filename`; `ls -ld --full-time filename`) reported by the OS.
1. Is TSM telling me that it was first backed up on 2019-10-03 18:25:16, but the modtime for the file changed on 2018-11-03 03:41:47 so it backed it up again? If so then why doesn't it report another entry with the new backup date?
2. Or is it instead telling me that only the modtime or ctime changed (e.g. maybe a permission change) but not the content so it simply reports the Inode changed date/time? If so, then we can assume that if the file is recovered then TSM will use that information to reset its modtime accordingly? That right? How do you know what date/time the database was updated with that information?
3. How does it determine that the file didn't change from 2019-10-03 18:25:16? It can't just compare the size, right? It's not using hashes is it?
But clearly, when the ctime or mtime changes for any file under /var/cache/man then the ctime or mtime on the 'man' directory itself should also change.
4. So why is it that when I run:
q backup /var/cache/man -subdir=yes -detail
I see only one entry from 2019-10-03? The OS reports a time and date as of today. This directory gets changed every day. Why does the query not report that?
I run something like this:
q backup /var/cache/man/ -subdir=yes -fromdate=2020-02-19
I see a number of files reported. All good. I then run this:
q backup /var/cache/man/index.db -fromdate=2020-02-19 -detail -inactive
I see only one entry with a backup date of 2019-10-03 18:25:16 and the following additional time details:
Modified: 2018-11-03 03:41:47 Accessed: 2018-11-03 03:41:47 Inode changed: 2018-11-03 03:41:47
This concurs with the ctime and mtime (`ls -lcd --full-time filename`; `ls -ld --full-time filename`) reported by the OS.
1. Is TSM telling me that it was first backed up on 2019-10-03 18:25:16, but the modtime for the file changed on 2018-11-03 03:41:47 so it backed it up again? If so then why doesn't it report another entry with the new backup date?
2. Or is it instead telling me that only the modtime or ctime changed (e.g. maybe a permission change) but not the content so it simply reports the Inode changed date/time? If so, then we can assume that if the file is recovered then TSM will use that information to reset its modtime accordingly? That right? How do you know what date/time the database was updated with that information?
3. How does it determine that the file didn't change from 2019-10-03 18:25:16? It can't just compare the size, right? It's not using hashes is it?
But clearly, when the ctime or mtime changes for any file under /var/cache/man then the ctime or mtime on the 'man' directory itself should also change.
4. So why is it that when I run:
q backup /var/cache/man -subdir=yes -detail
I see only one entry from 2019-10-03? The OS reports a time and date as of today. This directory gets changed every day. Why does the query not report that?