reneolsen
ADSM.ORG Member
I have a performance question regarding the use of the FROMNODE option.
First our configuration:
TSM server v. 5.1.5.1 running Windows 2000
Tape library 3584-L32 with 3 fibre drives
Novell clients v. 5.1.5.1
OS at node to restore from: NW 5.0 SP6, NSS v. 2 without compression
OS at node to restore to: NW 6.0 SP2, NSS v. 6 without compression
We have earlier tested the restore speed without the FROMNODE option. When data was moved to diskpool, we reached an average restore speed at 12GB/hour using only one session. Therefore we decided to use TSM to migrate a nodes data to another.
We moved the filespace of the node to diskpool (60GB). It was quick although it only used one drive (data resided on 7 volumes). The average speed was 28GB/hour.
Then we would restore using two sessions issuing the FROMNODE option. But now the restore times were very slow – approx. 1GB/hour adding the two sessions. The node we were restoring to, was the same on which we had an average restore time at 12GB/hour. Nothing changed in .OPT file.
Has anyone experienced the same, or has anyone an idea how to solve the problem or an explanation?
Regards,
Rene Olsen
Systems administrator
First our configuration:
TSM server v. 5.1.5.1 running Windows 2000
Tape library 3584-L32 with 3 fibre drives
Novell clients v. 5.1.5.1
OS at node to restore from: NW 5.0 SP6, NSS v. 2 without compression
OS at node to restore to: NW 6.0 SP2, NSS v. 6 without compression
We have earlier tested the restore speed without the FROMNODE option. When data was moved to diskpool, we reached an average restore speed at 12GB/hour using only one session. Therefore we decided to use TSM to migrate a nodes data to another.
We moved the filespace of the node to diskpool (60GB). It was quick although it only used one drive (data resided on 7 volumes). The average speed was 28GB/hour.
Then we would restore using two sessions issuing the FROMNODE option. But now the restore times were very slow – approx. 1GB/hour adding the two sessions. The node we were restoring to, was the same on which we had an average restore time at 12GB/hour. Nothing changed in .OPT file.
Has anyone experienced the same, or has anyone an idea how to solve the problem or an explanation?
Regards,
Rene Olsen
Systems administrator
