This is a discussion on Netbackup restore failed within the DB2 forums, part of the Database Server Software category; --> In our veritas netbackup for DB2 on AIX, the backup could be done successfully and the backup image would ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In our veritas netbackup for DB2 on AIX, the backup could be done successfully and the backup image would be listed using bplist on the AIX client. I have made several backup image, but only one image would be restored successfully. Restore with all the other images would get SQL2025N An I/O error "515" occurred on media "VENDOR". >From the netbackup log, we get readCommFile: ERR - timed out after 900 seconds while reading from / usr/openv/netbackup/logs/user_ops/dbext/logs/2412592.0.1176952663 11:33:39.373 [2412592] <32> serverResponse: ERR - could not read from comm file </usr/openv/netbackup/logs/user_ops/dbext/logs/ 2412592.0.1176952663> 11:33:39.373 [2412592] <16> RestoreFileObjects: ERR - serverResponse() failed 11:33:39.373 [2412592] <4> closeApi: entering closeApi. 11:33:39.373 [2412592] <4> closeApi: INF - EXIT STATUS 5: the restore failed to recover the requested files Does anyone has any idea on it? Thanks. |
| ||||
| 1. In the first line from the NetBackup "bpdb2" log, the 900 second (15 minute) timeout is the default for CLIENT_READ_TIMEOUT. CLIENT_READ_TIMEOUT should be longer than it takes to backup your largest tablespace, and should be set in the "/usr/openv/netbackup/ bp.conf" file on your client AND media server. For instance, to increase this to 30 minutes add: CLIENT_READ_TIMEOUT = 1800 2. The second line from the NetBackup 'bpdb2" log shows "could not read from comm file". This is the progress log that is stored on the client. All the NetBackup processes involved in the backup need access to this file. Make sure that the user that is backing-up DB2 has read/ write permissions to the "/usr/openv/netbackup/logs/user_ops/dbext/ logs" directory. 3. Also check connectivity between the client and the other servers in the configuaration (master and media). 4. All else fails, open a case with Symantec. Hope this helps. Brice Avila On Apr 18, 10:36 pm, edmundleu...@gmail.com wrote: > In our veritas netbackup for DB2 on AIX, the backup could be done > successfully and the backup image would be listed using bplist on the > AIX client. > > I have made several backup image, but only one image would be restored > successfully. Restore with all the other images would get > SQL2025N An I/O error "515" occurred on media "VENDOR". > > >From the netbackup log, we get > > readCommFile: ERR - timed out after 900 seconds while reading from / > usr/openv/netbackup/logs/user_ops/dbext/logs/2412592.0.1176952663 > 11:33:39.373 [2412592] <32> serverResponse: ERR - could not read from > comm file </usr/openv/netbackup/logs/user_ops/dbext/logs/ > 2412592.0.1176952663> > 11:33:39.373 [2412592] <16> RestoreFileObjects: ERR - serverResponse() > failed > 11:33:39.373 [2412592] <4> closeApi: entering closeApi. > 11:33:39.373 [2412592] <4> closeApi: INF - EXIT STATUS 5: the restore > failed to recover the requested files > > Does anyone has any idea on it? > > Thanks. |
| Thread Tools | |
| Display Modes | |
|
|