[Veritas-bu] Error code 233 premature eof encountered
Hi folk, Anybody encountered problem below before. Would like to check if the error message means that it has problem opening the catalog ? 00:14:40.582 [12683] 2 logconnections: BPDBM CONNECT FROM 10.84.14.41.36024 TO 10.84.14.41.13721 00:14:41.182 [12683] 2 get_long: (2) premature end of file (byte 1) 00:14:41.183 [12683] 2 db_getdata: get_string() failed: I/O error (5) premature end of file encountered (-9) 00:14:41.202 [12683] 2 db_end: no DONE from db_getreply(): premature eof encountered 00:14:41.203 [12683] 2 db_IMAGE: db_end() failed: premature eof encountered 00:14:41.206 [12683] 16 write_backup: cannot add fragment to image database, error = premature eof encountered 00:14:41.208 [12683] 2 send_brm_msg: EXIT clientname_1200327043 233 VNBU 4.5 error code 233: Master Server (Media Server) : Solaris 8 VNBU version: 4.5GA Tape library: Sun L100 Tape drives: 5 x Seagate LTO1 - The size of data written on the backup that failed with error 233 varies among different clients. Some of them backup 10 GB then failed, some of them only backup few MB then failed. - The error 233 is not specific to particular clients nor particular media ID nor particular tape drive The NBU catalog is stored in NFS from NetApps and it has been running for years without problem. Currently the NBU catalog size is about 80GB Any ideas or suggestion are strongly wellcome ??? Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error code 233 premature eof encountered
Currently NBU Catalog stores in NFS about 80GB out of 100GB - Original Message - From: Bobby Williams [EMAIL PROTECTED] To: [EMAIL PROTECTED]; 'veritas-bu' veritas-bu@mailman.eng.auburn.edu Sent: Friday, January 25, 2008 11:14 PM Subject: Re: [Veritas-bu] Error code 233 premature eof encountered Has the nfs server filled up? Is there space left? Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 25, 2008 10:11 AM To: veritas-bu Subject: [Veritas-bu] Error code 233 premature eof encountered Hi folk, Anybody encountered problem below before. Would like to check if the error message means that it has problem opening the catalog ? 00:14:40.582 [12683] 2 logconnections: BPDBM CONNECT FROM 10.84.14.41.36024 TO 10.84.14.41.13721 00:14:41.182 [12683] 2 get_long: (2) premature end of file (byte 1) 00:14:41.183 [12683] 2 db_getdata: get_string() failed: I/O error (5) premature end of file encountered (-9) 00:14:41.202 [12683] 2 db_end: no DONE from db_getreply(): premature eof encountered 00:14:41.203 [12683] 2 db_IMAGE: db_end() failed: premature eof encountered 00:14:41.206 [12683] 16 write_backup: cannot add fragment to image database, error = premature eof encountered 00:14:41.208 [12683] 2 send_brm_msg: EXIT clientname_1200327043 233 VNBU 4.5 error code 233: Master Server (Media Server) : Solaris 8 VNBU version: 4.5GA Tape library: Sun L100 Tape drives: 5 x Seagate LTO1 - The size of data written on the backup that failed with error 233 varies among different clients. Some of them backup 10 GB then failed, some of them only backup few MB then failed. - The error 233 is not specific to particular clients nor particular media ID nor particular tape drive The NBU catalog is stored in NFS from NetApps and it has been running for years without problem. Currently the NBU catalog size is about 80GB Any ideas or suggestion are strongly wellcome ??? Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error code 233 premature eof encountered
Currently NBU Catalog on NFS is about 80GB out of 100GB - Original Message - From: Bobby Williams [EMAIL PROTECTED] To: [EMAIL PROTECTED]; 'veritas-bu' veritas-bu@mailman.eng.auburn.edu Sent: Friday, January 25, 2008 11:14 PM Subject: Re: [Veritas-bu] Error code 233 premature eof encountered Has the nfs server filled up? Is there space left? Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 25, 2008 10:11 AM To: veritas-bu Subject: [Veritas-bu] Error code 233 premature eof encountered Hi folk, Anybody encountered problem below before. Would like to check if the error message means that it has problem opening the catalog ? 00:14:40.582 [12683] 2 logconnections: BPDBM CONNECT FROM 10.84.14.41.36024 TO 10.84.14.41.13721 00:14:41.182 [12683] 2 get_long: (2) premature end of file (byte 1) 00:14:41.183 [12683] 2 db_getdata: get_string() failed: I/O error (5) premature end of file encountered (-9) 00:14:41.202 [12683] 2 db_end: no DONE from db_getreply(): premature eof encountered 00:14:41.203 [12683] 2 db_IMAGE: db_end() failed: premature eof encountered 00:14:41.206 [12683] 16 write_backup: cannot add fragment to image database, error = premature eof encountered 00:14:41.208 [12683] 2 send_brm_msg: EXIT clientname_1200327043 233 VNBU 4.5 error code 233: Master Server (Media Server) : Solaris 8 VNBU version: 4.5GA Tape library: Sun L100 Tape drives: 5 x Seagate LTO1 - The size of data written on the backup that failed with error 233 varies among different clients. Some of them backup 10 GB then failed, some of them only backup few MB then failed. - The error 233 is not specific to particular clients nor particular media ID nor particular tape drive The NBU catalog is stored in NFS from NetApps and it has been running for years without problem. Currently the NBU catalog size is about 80GB Any ideas or suggestion are strongly wellcome ??? Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error code 233 premature eof encountered
Currently the NBU catalog size in NFS is 80GB out of 100GB - Original Message - From: Bobby Williams [EMAIL PROTECTED] To: [EMAIL PROTECTED]; 'veritas-bu' veritas-bu@mailman.eng.auburn.edu Sent: Friday, January 25, 2008 11:14 PM Subject: Re: [Veritas-bu] Error code 233 premature eof encountered Has the nfs server filled up? Is there space left? Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 25, 2008 10:11 AM To: veritas-bu Subject: [Veritas-bu] Error code 233 premature eof encountered Hi folk, Anybody encountered problem below before. Would like to check if the error message means that it has problem opening the catalog ? 00:14:40.582 [12683] 2 logconnections: BPDBM CONNECT FROM 10.84.14.41.36024 TO 10.84.14.41.13721 00:14:41.182 [12683] 2 get_long: (2) premature end of file (byte 1) 00:14:41.183 [12683] 2 db_getdata: get_string() failed: I/O error (5) premature end of file encountered (-9) 00:14:41.202 [12683] 2 db_end: no DONE from db_getreply(): premature eof encountered 00:14:41.203 [12683] 2 db_IMAGE: db_end() failed: premature eof encountered 00:14:41.206 [12683] 16 write_backup: cannot add fragment to image database, error = premature eof encountered 00:14:41.208 [12683] 2 send_brm_msg: EXIT clientname_1200327043 233 VNBU 4.5 error code 233: Master Server (Media Server) : Solaris 8 VNBU version: 4.5GA Tape library: Sun L100 Tape drives: 5 x Seagate LTO1 - The size of data written on the backup that failed with error 233 varies among different clients. Some of them backup 10 GB then failed, some of them only backup few MB then failed. - The error 233 is not specific to particular clients nor particular media ID nor particular tape drive The NBU catalog is stored in NFS from NetApps and it has been running for years without problem. Currently the NBU catalog size is about 80GB Any ideas or suggestion are strongly wellcome ??? Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error code 233 premature eof encountered
Has the nfs server filled up? Is there space left? Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 25, 2008 10:11 AM To: veritas-bu Subject: [Veritas-bu] Error code 233 premature eof encountered Hi folk, Anybody encountered problem below before. Would like to check if the error message means that it has problem opening the catalog ? 00:14:40.582 [12683] 2 logconnections: BPDBM CONNECT FROM 10.84.14.41.36024 TO 10.84.14.41.13721 00:14:41.182 [12683] 2 get_long: (2) premature end of file (byte 1) 00:14:41.183 [12683] 2 db_getdata: get_string() failed: I/O error (5) premature end of file encountered (-9) 00:14:41.202 [12683] 2 db_end: no DONE from db_getreply(): premature eof encountered 00:14:41.203 [12683] 2 db_IMAGE: db_end() failed: premature eof encountered 00:14:41.206 [12683] 16 write_backup: cannot add fragment to image database, error = premature eof encountered 00:14:41.208 [12683] 2 send_brm_msg: EXIT clientname_1200327043 233 VNBU 4.5 error code 233: Master Server (Media Server) : Solaris 8 VNBU version: 4.5GA Tape library: Sun L100 Tape drives: 5 x Seagate LTO1 - The size of data written on the backup that failed with error 233 varies among different clients. Some of them backup 10 GB then failed, some of them only backup few MB then failed. - The error 233 is not specific to particular clients nor particular media ID nor particular tape drive The NBU catalog is stored in NFS from NetApps and it has been running for years without problem. Currently the NBU catalog size is about 80GB Any ideas or suggestion are strongly wellcome ??? Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Error code 233 premature eof encountered
Hi folks, VNBU 4.5 error code 233: Master Server (Media Server) : Solaris 8 VNBU version: 4.5GA Tape library: Sun L100 Tape drives: 5 x Seagate LTO1 - The size of data written on the backup that failed with error 233 varies among different clients. Some of them backup 10 GB then failed, some of them only backup few MB then failed. - The error 233 is not specific to particular clients nor particular media ID nor particular tape drive bptm, bpdbm,bpbrm logs shown below cannot add fragment to image database, error 233 = premature eof encountered 00:14:40.582 [12683] 2 logconnections: BPDBM CONNECT FROM 10.84.14.41.36024 TO 10.84.14.41.13721 00:14:41.182 [12683] 2 get_long: (2) premature end of file (byte 1) 00:14:41.183 [12683] 2 db_getdata: get_string() failed: I/O error (5) premature end of file encountered (-9) 00:14:41.202 [12683] 2 db_end: no DONE from db_getreply(): premature eof encountered 00:14:41.203 [12683] 2 db_IMAGE: db_end() failed: premature eof encountered 00:14:41.206 [12683] 16 write_backup: cannot add fragment to image database, error = premature eof encountered 00:14:41.208 [12683] 2 send_brm_msg: EXIT sgcsgsuebiz19_1200327043 233 00:14:41.209 [12683] 2 bct_clear_active: Set BCTable entry 3 to inactive, ACTIVE_GC count decremented to 3 1. Changed all the tape drives and put in all new tapes 2. Rebuild device list and confirmed the Master server is the first entry in bp.conf 3. Confirmed the class or policy NOT has a comma sign in it name 4. NOT TIR backup 5. Completed #bpdbm -consistency 2 check without and bad images error, The check taken about 4 hours 6. Backup policies started, mount tape, positioning and start writing then the failed with error code 233 again, the written size to tape is always varies, sometime 2MB, sometime 2GB etc... Would like to highlight the backup images /usr/openv/netbackup/db is pointing to NFS mount of /appnas/netbackup/db, currently used up 74GB of 94GB of space Search thru' all Veritas support sites, web to no avail, escalated to Veritas Support still pending for response from almost month Could anyone shed some ideas/thinking etcI am more than willing to try it out to fix the problem Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Error code 233 premature eof encountered
Hi folks, VNBU 4.5 error code 233: Master Server (Media Server) : Solaris 8 VNBU version: 4.5GA Tape library: Sun L100 Tape drives: 5 x Seagate LTO1 - The size of data written on the backup that failed with error 233 varies among different clients. Some of them backup 10 GB then failed, some of them only backup few MB then failed. - The error 233 is not specific to particular clients nor particular media ID nor particular tape drive bptm, bpdbm,bpbrm logs shown below cannot add fragment to image database, error 233 = premature eof encountered 00:14:40.582 [12683] 2 logconnections: BPDBM CONNECT FROM 10.84.14.41.36024 TO 10.84.14.41.13721 00:14:41.182 [12683] 2 get_long: (2) premature end of file (byte 1) 00:14:41.183 [12683] 2 db_getdata: get_string() failed: I/O error (5) premature end of file encountered (-9) 00:14:41.202 [12683] 2 db_end: no DONE from db_getreply(): premature eof encountered 00:14:41.203 [12683] 2 db_IMAGE: db_end() failed: premature eof encountered 00:14:41.206 [12683] 16 write_backup: cannot add fragment to image database, error = premature eof encountered 00:14:41.208 [12683] 2 send_brm_msg: EXIT sgcsgsuebiz19_1200327043 233 00:14:41.209 [12683] 2 bct_clear_active: Set BCTable entry 3 to inactive, ACTIVE_GC count decremented to 3 1. Changed all the tape drives and put in all new tapes 2. Rebuild device list and confirmed the Master server is the first entry in bp.conf 3. Confirmed the class or policy NOT has a comma sign in it name 4. NOT TIR backup 5. Completed #bpdbm -consistency 2 check without and bad images error, The check taken about 4 hours 6. Backup policies started, mount tape, positioning and start writing then the failed with error code 233 again, the written size to tape is always varies, sometime 2MB, sometime 2GB etc... Would like to highlight the backup images /usr/openv/netbackup/db is pointing to NFS mount of /appnas/netbackup/db, currently used up 74GB of 94GB of space Search thru' all Veritas support sites, web to no avail, escalated to Veritas Support still pending for response from almost month Could anyone shed some ideas/thinking etcI am more than willing to try it out to fix the problem Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
