I observed in my setup that after every backup the tapes are rewinded to start. It is causing backup performance very low. I am using Scalar i500 library. I configured it with jbconfig and did not bypass autoconfiguration. I was in the hope that it will automatically take non rewinding device path.
Since I am new to AIX environment I do not know which path to use.
It is normal that if volume went from idle to done state then upon next "contact" NW will verify label first and the move forward X file and record numbers to position on first next empty spot. Since drive operations as such are slow there is an impact on speed, but this is nothing new and this limitation comes from HW design itself.
Why do you think it is rewinded? Your device may go idle and writing done state... if new operation is requested then NW will by default check label first despite volume being checked first time it was loaded. In some cases this may look as rewinding. Can you paste the log from the server so we can see this more clearly?
I checked the daemon but there is no such entry which is related to tape movement. As the tape was already mounted to the drive. When backup started in the monitoring window I am able to see the message of rewinding the tape and then moving forward x number files.
After every backup the number of file count gets increase. It takes around 10 mins to start the backup. However there is only 55 GB of data in the tape currently. I am wondering that if the data on tape will be in TB then how much time it will take to actuallyy start the backup.
ble1
6 Operator
•
14354 Posts
•
56186 Points
538
0
Posted December 5th, 2009 09:00