Re: [Veritas-bu] Problem getting file server backed up. code 84
The 64k limit is an old one and was based on older drivers/windows. With the newer drivers and windows this number can be quite a bit larger. Check your readme's for the drivers/hba. len - Original Message - From: [EMAIL PROTECTED] To: Wooten, FH Frank (3934) @ IS [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Cc: [EMAIL PROTECTED] Sent: Friday, January 06, 2006 9:42 AM Subject: Re: [Veritas-bu] Problem getting file server backed up. code 84 Hello Frank if you windows box is writing to the tape drives, make sure that block size is 64k (65536) or less. Regards Michael On Fri, 6 Jan 2006 08:10:56 -0600, Wooten, FH Frank (3934) @ IS wrote Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. Thanks Frank -- Cybercity Webhosting (http://www.cybercity.dk) ___ 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] Problem getting file server backed up. code 84
Title: Message Frank Not knowing Unix much, are there any other errors being logged for other clients? In the Global Settings (Host Properties), have you tried to set the Master server properties to increase the schedule backup attempts to a few more tries? Thanks Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Wooten, FH Frank (3934) @ IS [mailto:[EMAIL PROTECTED] Sent: 06 January 2006 14:11To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Problem getting file server backed up. code 84 Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. Thanks Frank This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
Re: [Veritas-bu] Problem getting file server backed up. code 84
On Fri, Jan 06, 2006 at 08:10:56AM -0600, Wooten, FH Frank (3934) @ IS wrote: Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. I've seen at least 3 different classification of 84 errors: 1. Bad tape or tape drive. You've eliminated this. 2. A full disk staging unit. You're not using DSSUs. 3. Connectivity issues between media server and tape drive. This is where the fun happens... Check your switch ports for errors on the ports. I had this happen when I had my ISLs set for 2Gbps and found out later that the fibre wasn't capable of being driven at 2Gbps for that distance. I dropped my ISL speed to 1Gbps and it's working fine (still out of spec and giving me buffer credit issues but error-free from the backup point of view). My fibre is actually being replaced now. Have a good look at your SAN switch logs and the host error logs. When I had my issue, I was logging scsi errors on the hosts (even though the drives are on the other end of a fibre/scsi bridge). .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Problem getting file server backed up. code 84
Hello Frank if you windows box is writing to the tape drives, make sure that block size is 64k (65536) or less. Regards Michael On Fri, 6 Jan 2006 08:10:56 -0600, Wooten, FH Frank (3934) @ IS wrote Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. Thanks Frank -- Cybercity Webhosting (http://www.cybercity.dk) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Problem getting file server backed up. code 84
Title: UNIX RAW PARTITION RESTORE QUESTION I have seen this before when backing up up file/print server 1.2TB + data . The windows and some other servers with terabyte plus data have been configured as a SAN media servers . SAN media servers gives these servers direct access to DISK staging unit / Library ,so they don`t send data over network . We have dedicated GIG network for backups which always helps.You may want to consider putting your file server over GIG network and configure it as a SAN media server. Are you on 5.1 MP4 ? I guess not ... Shekhar Dhotre ICTStorage Engineering. v 404.846.7483 | f 404.848.1077 [EMAIL PROTECTED]48 Perimeter Center East | Atlanta, GA 30346 Remember the difference between a boss and a leader; a boss says "Go!" - a leader says "Let's go!" From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wooten, FH Frank (3934) @ ISSent: Friday, January 06, 2006 9:11 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Problem getting file server backed up. code 84 Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. Thanks Frank "This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country."
RE: [Veritas-bu] Problem getting file server backed up. code 84
Title: UNIX RAW PARTITION RESTORE QUESTION Also check the technote below . IBM CE replaced rives but we use to get same error. check your indexing on the drives and drive configuration just to make sure that they are in correct order .. http://seer.support.veritas.com/docs/272802.htm Shekhar Dhotre ICTStorage Engineering. v 404.846.7483 | f 404.848.1077 [EMAIL PROTECTED]48 Perimeter Center East | Atlanta, GA 30346 Remember the difference between a boss and a leader; a boss says "Go!" - a leader says "Let's go!" From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wooten, FH Frank (3934) @ ISSent: Friday, January 06, 2006 9:11 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Problem getting file server backed up. code 84 Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. Thanks Frank "This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country."
RE: [Veritas-bu] Problem getting file server backed up. code 84
A correction for the third condition is adding a larger value CLIENT_READ_TIMEOUT value to your bp.conf on your client. It'll make the media server more tolerant to slow conditions on the client. I find it especially valuable on my large database servers. I ahve a value of 10800 seconds per client as a matter of course now: CLIENT_READ_TIMEOUT = 10800 HTH -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ed Wilts Sent: Friday, January 06, 2006 7:41 AM To: Wooten, FH Frank (3934) @ IS Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Problem getting file server backed up. code 84 On Fri, Jan 06, 2006 at 08:10:56AM -0600, Wooten, FH Frank (3934) @ IS wrote: Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. I've seen at least 3 different classification of 84 errors: 1. Bad tape or tape drive. You've eliminated this. 2. A full disk staging unit. You're not using DSSUs. 3. Connectivity issues between media server and tape drive. This is where the fun happens... Check your switch ports for errors on the ports. I had this happen when I had my ISLs set for 2Gbps and found out later that the fibre wasn't capable of being driven at 2Gbps for that distance. I dropped my ISL speed to 1Gbps and it's working fine (still out of spec and giving me buffer credit issues but error-free from the backup point of view). My fibre is actually being replaced now. Have a good look at your SAN switch logs and the host error logs. When I had my issue, I was logging scsi errors on the hosts (even though the drives are on the other end of a fibre/scsi bridge). .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ 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] Problem getting file server backed up. code 84
that's good suggestion . I have it set to 7200. [EMAIL PROTECTED]:/usr/openv/netbackupcat bp.conf SERVER = master SERVER = media1 SERVER = usatl01lq207 #SERVER = media1_nbu #SERVER = master_nbu CLIENT_NAME = master KEEP_VAULT_SESSIONS_DAYS = 10 CLIENT_CONNECT_TIMEOUT = 1800 CLIENT_READ_TIMEOUT = 7200 BPSTART_TIMEOUT = 1800 BPEND_TIMEOUT = 1800 DISALLOW_CLIENT_RESTORE = NO SERVER_CONNECT_TIMEOUT = 60 #REQUIRED_INTERFACE = master_nbu ALLOW_MEDIA_OVERWRITE = DBR ALLOW_MEDIA_OVERWRITE = TAR ALLOW_MEDIA_OVERWRITE = CPIO ALLOW_MEDIA_OVERWRITE = ANSI [EMAIL PROTECTED]:/usr/openv/netbackup Shekhar Dhotre ICT Storage Engineering. v 404.846.7483 | f 404.848.1077 [EMAIL PROTECTED] 48 Perimeter Center East | Atlanta, GA 30346 Remember the difference between a boss and a leader; a boss says Go! - a leader says Let's go! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 06, 2006 12:11 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Problem getting file server backed up. code 84 A correction for the third condition is adding a larger value CLIENT_READ_TIMEOUT value to your bp.conf on your client. It'll make the media server more tolerant to slow conditions on the client. I find it especially valuable on my large database servers. I ahve a value of 10800 seconds per client as a matter of course now: CLIENT_READ_TIMEOUT = 10800 HTH -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ed Wilts Sent: Friday, January 06, 2006 7:41 AM To: Wooten, FH Frank (3934) @ IS Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Problem getting file server backed up. code 84 On Fri, Jan 06, 2006 at 08:10:56AM -0600, Wooten, FH Frank (3934) @ IS wrote: Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. I've seen at least 3 different classification of 84 errors: 1. Bad tape or tape drive. You've eliminated this. 2. A full disk staging unit. You're not using DSSUs. 3. Connectivity issues between media server and tape drive. This is where the fun happens... Check your switch ports for errors on the ports. I had this happen when I had my ISLs set for 2Gbps and found out later that the fibre wasn't capable of being driven at 2Gbps for that distance. I dropped my ISL speed to 1Gbps and it's working fine (still out of spec and giving me buffer credit issues but error-free from the backup point of view). My fibre is actually being replaced now. Have a good look at your SAN switch logs and the host error logs. When I had my issue, I was logging scsi errors on the hosts (even though the drives are on the other end of a fibre/scsi bridge). .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ 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 - This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy
RE: [Veritas-bu] Problem getting file server backed up. code 84
Possibly? Check the tape device drivers, ensure that the correct and current tape device drivers are installed. Veritas also supplies a set Of good drivers on there installation CD's under additional products. Block size is also very important for Windows - 64k as mentioned in previous Reply should be the Max. Eric Ljungblad -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 06, 2006 6:42 AM To: Wooten, FH Frank (3934) @ IS; veritas-bu@mailman.eng.auburn.edu Cc: [EMAIL PROTECTED] Subject: Re: [Veritas-bu] Problem getting file server backed up. code 84 Hello Frank if you windows box is writing to the tape drives, make sure that block size is 64k (65536) or less. Regards Michael On Fri, 6 Jan 2006 08:10:56 -0600, Wooten, FH Frank (3934) @ IS wrote Ok, I am having a huge problem getting a 400gb file server backed up. My master server is a unix and the file server is win2k3. I have a ESL9000 attached to a san switch that the file server is attached too. Problem with the job is it will run for 4 to 5 hours and then fail with a code 84 (media write error). I have eliminated the tapes being the problem cause I have used new tapes and still get this error. I am wondering if its something with the switch or if it's the drives. It happens on multiple drives not just one. Any help would be greatly appreciated. This is driving me nutts. Thanks Frank -- Cybercity Webhosting (http://www.cybercity.dk) ___ 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
