Restoration using native operating system backup command took 10 hr for 300GB,while backup done in 1 half hr.
how to improve the performance for the tape drive?
Pinned topic Restoration using native operating system backup command took 10 hr for 300
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-02-09T14:53:12Z at 2011-02-09T14:53:12Z by QSECOFR
QSECOFR 100000QNP855 Posts
Re: Restoration using native operating system backup command took 10 hr for 3002011-02-09T14:53:12ZThis is the accepted answer. This is the accepted answer.A restore operation normally takes anywhere from 1-2 times as long as the save. Performance issues can sometimes be simple or extremely complex.
These are what determine the speed of the restore:
- Tape device
- Tape device firmware
- Connection type (scsi/fibre)
- Fibre switch config/traffic
- IOA speed
- System i and component microcode (PTFs)
- Save/restore command and parameter values such as only restoring new members, access path rebuild, ASP etc.
- Memory pool
- DASD disk response
- processor (not usually processor)
- media type
- media recoverable errors
1) What was the save command/parameter values?
2) What is the restore command/parameter values?
3) What type of tape library/drive and media is used?
4) Any Product Activity Log entries or WRKPRB entries?
5) Media Session statistics will give any gaps in time and any media errors
6) If V6R1 or above, /QSR/QSR/fr and fr.old are the save/restore flight recorders
7) Any errors in the joblog (at higher releases, I believe it gives the timestamps and blocks restored)
8) Restoring to same system with same drive or different?
If you have a support contract, it would probably be best to contact your support.