01-12-2011 01:57 PM
Hi Folks,
This time I'm having an issue trying to restore a Sybase DB.
The backup was taken without compression at Sybase level (DUMP) but with the compression option at NetBackup Policy.
The restore in NetBackup ends in Status 0:
root@nbumaster # bpdbjobs -report -jobid 410438 -all_columns 410438,2,3,0,,,preprod,nbumaster,1294756648,0000000157,1294756805,,1,,9216,0,,100,24082,sybase1,,,,90000,sybase2,nbumaster,,,,,,1,/SYB_6900.DB.D.0.26587.08-01-2011.21:38:27,1,24082,,,1294756648,0000000157,1294756805,0,the requested operation was successfully completed,17,01/11/11 09:37:28 - begin Restore operation,01/11/11 09:37:30 - 1 images required,01/11/11 09:37:30 - media XXX038 required,01/11/11 09:37:34 - restoring image clientdb_1294540885,01/11/11 09:37:37 - requesting resource XXX038,01/11/11 09:37:37 - granted resource XXX038,01/11/11 09:37:37 - granted resource IBM.ULT3580-TD3.001,01/11/11 09:37:39 - started process bptm (24114),01/11/11 09:37:39 - mounting XXX038,01/11/11 09:37:43 - connected,01/11/11 09:38:08 - mounted; mount time: 000:00:29,01/11/11 09:38:08 - positioning XXX038 to file 18,01/11/11 09:39:57 - positioned; position time: 000:01:49,01/11/11 09:39:57 - begin reading,01/11/11 09:40:03 - end reading; read time: 000:00:06,01/11/11 09:40:04 - restored image clientdb_1294540885 - (the requested operation was successfully completed(0)),01/11/11 09:40:04 - end Restore operation; operation time: 000:02:36,9216,0,,9216000,,,,,,,,nbumaster,XXX038,,,,,,,,,,,,, root@nbumaster # bpdbjobs -report -jobid 410437
But in Sybase this is the log
2> go Backup Server session id is: 33. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server. Backup Server: 4.132.1.1: Attempting to open byte stream device: 'sybackup::SYB_6900.DB.D.0.4859.08-01-2011.00:40:31 -SERV nbumaster -CLIENT clientdb -CLASS Database2::00' Backup Server: 4.10.2.1: Label validation error: first label not VOL1. Backup Server: 6.31.2.4: Volume rejected. Backup Server: 1.14.2.2: Unrecoverable I/O or volume error. This DUMP or LOAD session must exit. Backup Server: 4.125.1.1: Archive API information for device='sybackup::SYB_6900.DB.D.0.4859.08-01-2011.00:40:31 -SERV nbumaster -CLIENT clientdb -CLASS Database2::00': Vendor application name='VERITAS NetBackup for SYBASE', Library version=600000, Message= Aborted by Backup Server. Backup Server: 6.32.2.3: sybackup::SYB_6900.DB.D.0.4859.08-01-2011.00:40:31 -SERV nbumaster -CLIENT clientdb -CLASS Database2::00: volume not valid or not requested (server: , session id: 33.) Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This DUMP or LOAD session must exit. Msg 8009, Level 16, State 1: Server 'SYB_MENSUAL', Line 1: Error encountered by Backup Server. Please refer to Backup Server messages for details. 1>
NOTE: I tried with the compress:: option in the LOAD syntax but since the DUMP wasn's taken with that parameter it doesn't work.
The courious thing is that If I do the same backup but with no compression at Policy Level the restore works fine.
I checked the NetBackup for Sybase Admin Guide and also the NetBackup 6.5 release Notes and they says Compression is allowed, but no further documentation.
Please let me know if someone have seen this.
PLATFORM: Master-Media Sol 10, NetBackup 6.5.4 / Client Sol 10, NetBackup 6.5.4 + Sybase 12.5
Solved! Go to Solution.
01-31-2011 06:55 AM
As I supposed from the very beginning, it was something (unknown from me) at Sybase side.
I planned a new restore session to be able to collect all necessary logs and traces to open a Symantec case and Guess what?... Yeah, every single restore worked perfectly.
I was pleased to see NBU working fine (as I supossed) but Sybase guys were in panic because they didn't know what happen (at least they "looked like").
Thanks anyway.
01-31-2011 06:55 AM
As I supposed from the very beginning, it was something (unknown from me) at Sybase side.
I planned a new restore session to be able to collect all necessary logs and traces to open a Symantec case and Guess what?... Yeah, every single restore worked perfectly.
I was pleased to see NBU working fine (as I supossed) but Sybase guys were in panic because they didn't know what happen (at least they "looked like").
Thanks anyway.