Short of prestaging the data, two things you can do to optimize restores: 1) bump up resourceutilization to allow more client threads 2) bump up maxnummp on the node definition to allow more concurrent tape drives
>>> [EMAIL PROTECTED] 01/11/06 6:11 PM >>> Hi folks, I'm working on our internal "late night admin guide," and one of the things I'm thinking of is how can I get TSM prepared to do a restore. Here's what I mean: let's say I know that there is going to be some filesystem maintenance on a client. Since we've been burned by that kind of operation in the past, I'd like TSM to prefetch the appropriate data from tape and have it ready to go (on disk) for a restore. Archives would do the trick except that uses the client, potentially during business hours. Backupsets look like they might work but they're kind of rigid... can a backupset be restored followed by restoring the latest incrementals? So I could create a backupset on Friday before the procedure on Saturday, and then be able to restore the incremental we took before beginning the disk operation after that? Am I out of my tree? Do people do this? Thanks, --Jim
