TSM Server: WinNT 3.7.3.0 TSM Client: WinNT 3.7.2.16 We have a customer who is restoring a large NTFS volume on their primary fileserver. During the restore process, the client has repeatedly failed with errors, preventing the completion of the restore. Additionally, NTFS permissions are also not being restored, with some errors logged on the client referring to this. During the initial attempt to restore the entire volume, Out-of-memory errors were seen on the client machine. A representative portion of the client's dsmerror.log file: 10/14/2000 02:24:41 TransWin32RC(): Win32 RC 998 from HlClose(): setFileSecurityInformation 10/14/2000 02:24:41 hlClose(): Win32 RC 19976352 occured restoring NTFS Security Attributes on object '�ͫ�'. 10/14/2000 02:24:41 hlClose(): Default NTFS Security Attributes have been set. 10/14/2000 02:28:11 File thought to be compressed was not Report how you got this 10/14/2000 02:28:12 File thought to be compressed was not Report how you got this 10/14/2000 02:35:02 TransWin32RC(): Win32 RC 1336 from HlClose(): setFileSecurityInformation 10/14/2000 02:35:03 hlClose(): Win32 RC 19976352 occured restoring NTFS Security Attributes on object '�ͫ�'. 10/14/2000 02:35:03 hlClose(): Default NTFS Security Attributes have been set. 10/14/2000 02:37:08 File thought to be compressed was not Report how you got this 10/14/2000 02:37:08 File thought to be compressed was not Report how you got this 10/14/2000 02:48:45 fioWrite(): Unrecoverable error: 23205 Bytes left in receive buffer with a BLOCK_EOF sdb type. 10/14/2000 02:48:45 Internal system error . Please check the TSM Error Log for any additional information. 10/14/2000 02:48:46 Internal system error . Please check the TSM Error Log for any additional information. <At this point in the restore, the client dies.> They have been able to make some progress by attempting piecemeal restores of individual directory branches on the volume, but it is requiring a lot of manual intervention. Any suggestions or thoughts? Ted Byrne
