We are having some major problems with restoring data from a NT server to a Windows 2000 server and then be able to use the data. See details below:
Background : We are migrating our main file server to a bigger and faster box, so we were using TSM to restore data from tape since we can't have any down time on the old server. We were able to do this successfully. All the data was restored , and the restore time was less than what we had expected (250 + gigs). After we had the data on the drive, we checked for fragmentation, and there was 99% fragmentation. we tried to defrag and were unable to. We've tested this out on different machines, with different backed up data and restored places, and the result is the same. After the restore, the part of the volume which was restore to, seems to be completed allocated as a huge giant file. Since we can't operate at 99% fragmentation, we decided to copy the files directly over - which worked fine. Can you shed some light as to what could be happening, and if there's anything we could do from our perspective to correct this ?
Also, there were problems with restoring proper securities. We are using 5.1.0 as the TSM client on both clients.
Any help would be greatly appreciated! :
Background : We are migrating our main file server to a bigger and faster box, so we were using TSM to restore data from tape since we can't have any down time on the old server. We were able to do this successfully. All the data was restored , and the restore time was less than what we had expected (250 + gigs). After we had the data on the drive, we checked for fragmentation, and there was 99% fragmentation. we tried to defrag and were unable to. We've tested this out on different machines, with different backed up data and restored places, and the result is the same. After the restore, the part of the volume which was restore to, seems to be completed allocated as a huge giant file. Since we can't operate at 99% fragmentation, we decided to copy the files directly over - which worked fine. Can you shed some light as to what could be happening, and if there's anything we could do from our perspective to correct this ?
Also, there were problems with restoring proper securities. We are using 5.1.0 as the TSM client on both clients.
Any help would be greatly appreciated! :