Been reading up on 4.2 Journal Backups.

Windows 2000 provides a journal file system (NTFS 5) but the TSM 4.2 client 
doesn't use it. (as I understand it) Instead it implements it owns journal 
service (daemon) that monitors the filesystems and updates a database when it 
changes. This seems odd, when NTFS 5 supports journaling and has an associated 
API.

Can someone from Tivoli explain why the client was implemented this way?

Regards

Andrew Webster



--
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.