Greetings.
I am looking for feedback from someone who has experience with Netbackup backing up Informix.
We are in the process of migrating from another storage manager to Netbackup 7.1.0.2 running against Informix 11.50FC9.( almost 1 TB in size )
The issues I am seeing are
- 1. Netbckup Lost track of the Informix Objcts for a period of time -
I backed it up
I verified it successfully
I went to restore it and got the following
2011-12-15 19:39:05 28748 28746 XBSA Error: (BSAGetObject) A system error occurred. Aborting XBSA session.
-
Signal13 (Broken pipe: write to pipe with no readers ) errors during backup - This indicates that the associated netbackup process has died. These don’t seem to be resolved by CLIENT_READ_TIMEOUT
“2011-12-22 09:11:59 6674 6381 (-43080) Process 6674 received signal 13. Process will exit after cleanup.
2011-12-22 09:13:06 6674 6381 XBSA Error: (BSAEndData) A system error occurred. Aborting XBSA session.”
-
BSASend Data errors during backup – possibly the same as above
“2011-12-21 03:17:17 1961 5945 XBSA Error: (BSASendData) A system error occurred. Aborting XBSA session. 2011-12-21 03:17:17 1961 5945 XBSA Error: (BSAEndData) A system error occurred. Aborting XBSA session.”
-
Restore failure after 99% of space has been restored – timeout reading back from the storage manager
“2011-12-18 17:37:02 7586 6273 (-43296) WARNING: BAR_TIMEOUT Storage Manager Progress may be stalled.
2011-12-18 17:40:03 7586 6273 XBSA Error: (BSAEndData) A system error occurred. Aborting XBSA session.
2011-12-18 17:40:10 7586 6273 Process 7586 6273 completed.”
-
Netbackup Scheduler on the Admin Console not running Scheduled jobs for Informix although it can run the job manually
-
I also noticed when I installed the client software that it installs and configures bpcd to run - standalone ( is this right ) ? and that the startup script it places in /etc/init.d starts it like this.
I have tried setting CLIENT_READ_TIMEOUT but it doesn't seem to be having any effect.
Kind reagrds
Evan
