jwhowell
ADSM.ORG Member
TSM 5.1.1, server on OS/390 2.10, NT and W2K clients. We just got back from a disaster recovery test. While the TSM server restore went very smoothly and we only had a few bobbles adjusting to a different hardware environment, recovering our NT server data from tapes was painfully, agonizingly, excruciatingly slow. The tapes we were using were the offsite copy storage pool, and the pool uses collocation. We keep at most 3 versions of any file and were not trying to restore inactive versions of files. It seemed as if TSM was scanning the tapes repeatedly in some cases; a few servers seemed to restore very quickly, while others took hours to restore a few hundred megabytes of data. Interestingly, the worst offender was a server with a few huge (tens of gigabytes) files. That one was mounting tape after tape.
While doing restores on our test LAN at home we used the backup pool (still tape) rather than the copy storage pool and never saw problems like this. Clearly TSM is doing things differently from the copy pool that it does the backup pool. Has anyone ever experienced a problem like this? Does anyone have any insight as to what might be going on and what we might do to avoid this in the future?
While doing restores on our test LAN at home we used the backup pool (still tape) rather than the copy storage pool and never saw problems like this. Clearly TSM is doing things differently from the copy pool that it does the backup pool. Has anyone ever experienced a problem like this? Does anyone have any insight as to what might be going on and what we might do to avoid this in the future?