We have just stumbled upon the fact that we cannot restore inactive Security settings with the TSM Solaris Client. With this client, when a security change is made to a file and an incremental backup is done, another version of the file is not sent to TSM, the existing file is updated with the new security settings. This results in the inability to restore inactive security settings. With NetWare, NT, and Windows 2000 clients a new version of the file is sent to the TSM server on an incremental backup when security is changed. This results in the ability to restore an inactive file with the appropriate security settings. We opened a problem with Tivoli on this, and they said this is working as designed. They said this is how TSM works with all Unix clients. Does anyone know why the different Tivoli Clients are not consistend in the way they handle securty changes to files? Does anyone see this as a big problem for the unix clients? (You can restore an inactive version of a file but always get the most recent security settings.) Thanks, Tim Rushforth City of Winnipeg
