Hi all,
We backup several sybase 12.01 databases with the netbackup 3.4 sybase module.
Client is patched. Backups and restores
of most database are fine. But unfortunately, we're unable to RESTORE our
biggest database (42GB).
The logs are below. The restore terminates about halfway. From the NBU client
point of view, it looks like a tape- or
network problem (I think) (recv returned 0 while reading ...), but nothing is
logged about that on the server.
Any clues what might be going on/wrong here ?
Thanks for your time, Joost.
--
The sybase load logging says this when the restore is about halfway:
> Oct 26 18:41:03 2001: Backup Server: 4.124.2.1: Archive API error for
> device='<truncated>:
> Vendor application name='VERITAS NetBackup for SYBASE', Library
> version=340000, API routine=syb_read(),
> Message= Restore failed - syb_read: ERR - BSAGetData() failed with error -
> System detected error, operation
> aborted.. Please refer to sybackup log for more info.
> Oct 26 18:41:03 2001: Backup Server: 4.125.1.1: Archive API information for
> device='<truncated>':
> Vendor application name='VERITAS NetBackup for SYBASE', Library
> version=340000, Message= Aborted by Backup Server.
> Oct 26 18:41:03 2001: Backup Server: 6.32.2.3: <truncated>: volume not valid
> or not requested
> (server: , session id: 11.)
> Oct 26 18:41:03 2001: Backup Server: 1.14.2.4: Unrecoverable I/O or volume
> error. This DUMP or LOAD session must
> exit.
The NetBackup client then, says this:
> 15:35:24 [23968] <6> syb_read: INF - Restore for stripe 0 started
> 18:41:03 [23968] <16> readFromServer: ERR - recv() returned 0 while reading
> 65536 bytes on 19 socket
> 18:41:03 [23968] <16> dbc_get: ERR - failed reading data from server, bytes
> read = -1
> 18:41:03 [23968] <4> closeApi: INF - EXIT STATUS 5: the restore failed to
> recover the requested files
> 18:41:03 [23968] <16> BSAGetData: ERR - Could not do a dbc_get().
> 18:41:03 [23968] <16> syb_read: ERR - BSAGetData() failed with error - System
> detected error, operation aborted.
> 18:41:03 [23968] <16> dbc_close: ERR - terminated by the application,
> cleaning up
> 18:41:03 [23968] <4> closeApi: INF - EXIT STATUS 5: the restore failed to
> recover the requested files
And then, the server says that the restore failed and that the operation
completed succesfully:
> Restore started Fri Oct 26 15:33:24 2001
> 15:33:26 (806.xxx) Restore job id 806 will require 1 image.
> 15:33:26 (806.xxx) Media id 000061 is needed for the restore.
> 15:33:30 (806.001) Restoring from image created Fri Oct 19 20:07:26 2001
> 15:33:32 (806.001) INF - Data socket = greta.pica.nl.4997
> 15:33:32 (806.001) INF - Name socket = greta.pica.nl.4996
> 15:33:32 (806.001) INF - New data socket = greta.pica.nl.4998
> 15:33:32 (806.001) INF - Waiting for mount of media id 000061 on server greta.
> 15:33:32 (806.001) INF - Use shared memory = 0
> 15:33:32 (806.001) INF - Restore id = 806.001
> 15:33:32 (806.001) INF - Client read timeout = 300
> 15:33:33 (806.001) INF - Media mount timeout = 0
> 15:33:33 (806.001) INF - client = gerrit
> 15:33:33 (806.001) INF - requesting_client = gerrit
> 15:33:33 (806.001) INF - browse_client = gerrit
> 15:35:18 (806.001) INF - Waiting for positioning of media id 000061 on server
> greta.
> 15:35:20 (806.001) INF - Beginning restore from server greta to client gerrit.
> 18:41:01 (806.001) /GERRIT.cbs.D.0.6463.19-10-2001.20:07:52 was not restored.
> 18:41:03 INF - Server status = 0
> 18:41:03 (806.001) Status of restore from image created Fri Oct 19 20:07:26
> 2001 = network connection timed out
> 18:41:05 (806.xxx) INF - Status = the requested operation was successfully
> completed.
The script we use for all our restores is below. Other restores done with an
equivalent script are fine
> time isql -Usa -P$SERVER_SA_PASSWORD -o ~cbs_syb/log/load_cbs_test_joost.log
> <<END
> LOAD DATABASE cbs_tst
> from 'sybackup::GERRIT.cbs.D.0.6463.19-10-2001.20:07:52 -SERV greta -CLASS
> sybase-cbs -SCHED Default-Policy'
> go
> END
|
