RE: Very slow onbar restore

make sure BAR_MAX_BACKUP is not set to 1 and BAR_NB_XPORT_COUNT is not set to a low value, what about setting BAR_NB_XPORT_COUNT to 1000 or 2000, and BAR_MAX_BACKUP to 20. you may also need to check the tape library configuration, may be something is not configured right with the tape library, or a bad tape. -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]On Behalf Of Neil Truby Sent: Wednesday, May 26, 2004 11:07 AM To: informix-list@iiug.org Subject: Very slow onbar restore IDS 7.31 on HP-UX 11.11 The customer did a whole back-up onbar -b -w -L 0 on Saturday. Took about six hours. Netbackup 3.4.1 is used to backup to a tape device attached to another server on the network. Now they are doing a restore (onbar -r -p -w). Although it's running OK, it is so sllllooooowwwwww. For instance, if I zero out the stats, I see from onstat -D that the writes clock up at perhaps a few thousand a minute: about one-tenth of the rate I would expect. Using sar shows fast (sub 4ms) response times on the target disks. onstat -p also shows periods of inactivity, followed by a mass of writes,followed by more inactivity. onstat -g ses shows the ontape thread constantly waiting on condition. there is nothing useful in the onbar, Informix or system syslogs. I've added another cpu vp (it's using kaio), to no avail. All the above points towards a systemic problem with the tape stacker. But it's not a network one: the only network card configured on the target server shows instant response times to a ping to the server to which the stacker is connected. The customer has previously tested restores on identical hardware/OS/Informix/ Netbackup and they have flown through at the expected rates. The customer has also executed a file system restore using the same stacker (not the samne device obviously) with the expected fast restore times. The customer also reckons that she started the restore yesterday and it went at normal speeds until it failed with a tape positioning error. Any ideas? Suggestions gratefully received. IBM support call 403279 refers. thanks Neil sending to informix-list