>From my notes: new files (not contained in the TSM Db) or files whose contents changed since the last backup. This includes - for WINDOWS - any of the following: - File size. - Date or time of last modification. - File attributes, except for the archive (A) attribute. - NTFS file security descriptors. ( Owner Security Identifier (SID), Group SID, Discretionary Access Control List (ACL), and System ACL.) (see TSM 5.1 - Windows - Backup-Archive Clients Installation and User's Guide - page 41) OR for UNIX: - File size - Date or time of last modification - Access Control List If only the following items change, they are updated without causing the entire file to be backed up: - File owner - File permissions - Last access time - Inode - Group ID (see TSM 5.1 - UNIX - Backup-Archive Clients Installation and User's Guide - page 58)
-----Ursprüngliche Nachricht----- Von: T. Lists [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 25. Juni 2003 17:51 An: [EMAIL PROTECTED] Betreff: what determines a file's eligibility for backup? For files on a windows system, what does TSM look at to determine if a file has been modified and therefore eligible to be backed up again? Is it only the modified date? I know I've had problems before with the sys admins doing recursive permissions changes on directories that causes all the files to be backed up again, but I don't know if that touches the modified date or not. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
