[Veritas-bu] Where is the 6.5.3 Oracle Agent?
lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server ls -1 | grep 6.5|grep ORA NB_ORA_51_2_M_274695.linux64.tar NB_ORA_51_7_M.hpia64_302615.tar NB_ORA_6.5.1_294667.tar NB_ORA_6.5.2_304438.tar lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server While all of the other 6.5.3 packages are there? lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server ls -1 | grep 6.5.3 NBLU_6.5.3.UNIX_1of3_314651.zip NBLU_6.5.3.UNIX_2of3_314652.zip NBLU_6.5.3.UNIX_3of3_314653.zip NBLU_6.5.3.WINia64_314616.zip NBLU_6.5.3.WINx64_314617.zip NBLU_6.5.3.WINx86_314618.zip NB_6.5.3.ONLINE_README_JA_316556.zip NB_6.5.3.ONLINE_README_ZH_316558.zip NB_6.5.3.alpha_5_314578.tar NB_6.5.3.hp_ux_314579.tar NB_6.5.3.hpia64_314580.tar NB_6.5.3.linuxR_ia64_314582.tar NB_6.5.3.linuxR_x86_314583.tar NB_6.5.3.linuxS_ia64_314584.tar NB_6.5.3.linuxS_x86_314585.tar NB_6.5.3.linux_314581.tar NB_6.5.3.rs6000_314586.tar NB_6.5.3.solaris_314587.tar NB_6.5.3.solaris_x86_314588.tar NB_6.5.3.winnt.IA64_314589.exe NB_6.5.3.winnt.x64_314590.exe NB_6.5.3.winnt.x86_314591.exe NB_6.5.3_DebugSymbols.winnt.x64_314663.exe NB_6.5.3_JA_316437.tgz NB_6.5.3_ZH_316454.tgz NB_BBS_6.5.3_314593.tar NB_BMR_6.5.3_314594.tar NB_CLT_6.5.3_314595.tar NB_DB2_6.5.3_314597.tar NB_DMP_6.5.3_314598.tar NB_INX_6.5.3_314599.tar NB_JAV_6.5.3.winnt.IA64_314601.exe NB_JAV_6.5.3.winnt.x86_314602.exe NB_JAV_6.5.3_314600.tar NB_LOT_6.5.3_314603.tar NB_LUA_6.5.3_314604.tar NB_NOM_6.5.3.winnt.x86_314606.exe NB_NOM_6.5.3_314605.tar NB_SAP_6.5.3_314607.tar NB_SNC_6.5.3_314609.tar NB_VLT_6.5.3_314610.tar NB_VMS_6.5.3_314611.zip NB_VxAT_6.5.3_314659.zip NB_VxAZ_6.5.3_314660.zip Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Where is the 6.5.3 Oracle Agent?
Justin, If the Oracle agent did not change from the prior release, Symantec does not re-kit and re-release a new version. As far as I know, there is not a 6.5.3 Oracle agent; we're using the 6.5.2 agents in our environment. --Larry On Wed, Jan 7, 2009 at 6:02 AM, Justin Piszcz jpis...@lucidpixels.com wrote: lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server ls -1 | grep 6.5|grep ORA NB_ORA_51_2_M_274695.linux64.tar NB_ORA_51_7_M.hpia64_302615.tar NB_ORA_6.5.1_294667.tar NB_ORA_6.5.2_304438.tar lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server While all of the other 6.5.3 packages are there? lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server ls -1 | grep 6.5.3 NBLU_6.5.3.UNIX_1of3_314651.zip NBLU_6.5.3.UNIX_2of3_314652.zip NBLU_6.5.3.UNIX_3of3_314653.zip NBLU_6.5.3.WINia64_314616.zip NBLU_6.5.3.WINx64_314617.zip NBLU_6.5.3.WINx86_314618.zip NB_6.5.3.ONLINE_README_JA_316556.zip NB_6.5.3.ONLINE_README_ZH_316558.zip NB_6.5.3.alpha_5_314578.tar NB_6.5.3.hp_ux_314579.tar NB_6.5.3.hpia64_314580.tar NB_6.5.3.linuxR_ia64_314582.tar NB_6.5.3.linuxR_x86_314583.tar NB_6.5.3.linuxS_ia64_314584.tar NB_6.5.3.linuxS_x86_314585.tar NB_6.5.3.linux_314581.tar NB_6.5.3.rs6000_314586.tar NB_6.5.3.solaris_314587.tar NB_6.5.3.solaris_x86_314588.tar NB_6.5.3.winnt.IA64_314589.exe NB_6.5.3.winnt.x64_314590.exe NB_6.5.3.winnt.x86_314591.exe NB_6.5.3_DebugSymbols.winnt.x64_314663.exe NB_6.5.3_JA_316437.tgz NB_6.5.3_ZH_316454.tgz NB_BBS_6.5.3_314593.tar NB_BMR_6.5.3_314594.tar NB_CLT_6.5.3_314595.tar NB_DB2_6.5.3_314597.tar NB_DMP_6.5.3_314598.tar NB_INX_6.5.3_314599.tar NB_JAV_6.5.3.winnt.IA64_314601.exe NB_JAV_6.5.3.winnt.x86_314602.exe NB_JAV_6.5.3_314600.tar NB_LOT_6.5.3_314603.tar NB_LUA_6.5.3_314604.tar NB_NOM_6.5.3.winnt.x86_314606.exe NB_NOM_6.5.3_314605.tar NB_SAP_6.5.3_314607.tar NB_SNC_6.5.3_314609.tar NB_VLT_6.5.3_314610.tar NB_VMS_6.5.3_314611.zip NB_VxAT_6.5.3_314659.zip NB_VxAZ_6.5.3_314660.zip Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Larry Fahnoe, Fahnoe Technology Consulting, fah...@fahnoetech.com 952/925-0744 Minneapolis, Minnesota www.FahnoeTech.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Where is the 6.5.3 Oracle Agent?
Thanks Larry. Justin. On Wed, 7 Jan 2009, Larry Fahnoe wrote: Justin, If the Oracle agent did not change from the prior release, Symantec does not re-kit and re-release a new version. As far as I know, there is not a 6.5.3 Oracle agent; we're using the 6.5.2 agents in our environment. --Larry On Wed, Jan 7, 2009 at 6:02 AM, Justin Piszcz jpis...@lucidpixels.com wrote: lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server ls -1 | grep 6.5|grep ORA NB_ORA_51_2_M_274695.linux64.tar NB_ORA_51_7_M.hpia64_302615.tar NB_ORA_6.5.1_294667.tar NB_ORA_6.5.2_304438.tar lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server While all of the other 6.5.3 packages are there? lftp ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server ls -1 | grep 6.5.3 NBLU_6.5.3.UNIX_1of3_314651.zip NBLU_6.5.3.UNIX_2of3_314652.zip NBLU_6.5.3.UNIX_3of3_314653.zip NBLU_6.5.3.WINia64_314616.zip NBLU_6.5.3.WINx64_314617.zip NBLU_6.5.3.WINx86_314618.zip NB_6.5.3.ONLINE_README_JA_316556.zip NB_6.5.3.ONLINE_README_ZH_316558.zip NB_6.5.3.alpha_5_314578.tar NB_6.5.3.hp_ux_314579.tar NB_6.5.3.hpia64_314580.tar NB_6.5.3.linuxR_ia64_314582.tar NB_6.5.3.linuxR_x86_314583.tar NB_6.5.3.linuxS_ia64_314584.tar NB_6.5.3.linuxS_x86_314585.tar NB_6.5.3.linux_314581.tar NB_6.5.3.rs6000_314586.tar NB_6.5.3.solaris_314587.tar NB_6.5.3.solaris_x86_314588.tar NB_6.5.3.winnt.IA64_314589.exe NB_6.5.3.winnt.x64_314590.exe NB_6.5.3.winnt.x86_314591.exe NB_6.5.3_DebugSymbols.winnt.x64_314663.exe NB_6.5.3_JA_316437.tgz NB_6.5.3_ZH_316454.tgz NB_BBS_6.5.3_314593.tar NB_BMR_6.5.3_314594.tar NB_CLT_6.5.3_314595.tar NB_DB2_6.5.3_314597.tar NB_DMP_6.5.3_314598.tar NB_INX_6.5.3_314599.tar NB_JAV_6.5.3.winnt.IA64_314601.exe NB_JAV_6.5.3.winnt.x86_314602.exe NB_JAV_6.5.3_314600.tar NB_LOT_6.5.3_314603.tar NB_LUA_6.5.3_314604.tar NB_NOM_6.5.3.winnt.x86_314606.exe NB_NOM_6.5.3_314605.tar NB_SAP_6.5.3_314607.tar NB_SNC_6.5.3_314609.tar NB_VLT_6.5.3_314610.tar NB_VMS_6.5.3_314611.zip NB_VxAT_6.5.3_314659.zip NB_VxAZ_6.5.3_314660.zip Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Larry Fahnoe, Fahnoe Technology Consulting, fah...@fahnoetech.com 952/925-0744 Minneapolis, Minnesota www.FahnoeTech.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NetBackup 6.5.x oddity: st 0:0:0:0: reservation conflict
Anyone ever seen this before? I have 4 servers, 2 old and 2 new, all run 6.5.2a, now 6.5.3 as of this morning. I see this error occur in the logs a few moments after midnight, every night. I did notice mt-st was not installed on the machines that were getting this error, so I installed that and we'll see if the issue recurs for tomorrow; however, was curious if anyone had seen this? The first host has two directly-attached fiber drives: Jan 4 00:02:19 host1 kernel: st 0:0:0:0: reservation conflict Jan 5 00:01:19 host1 kernel: st 0:0:0:0: reservation conflict Jan 5 00:01:47 host1 kernel: st 1:0:0:0: reservation conflict Jan 6 00:01:18 host1 kernel: st 1:0:0:0: reservation conflict Jan 6 00:02:18 host1 kernel: st 0:0:0:0: reservation conflict Jan 7 00:01:18 host1 kernel: st 0:0:0:0: reservation conflict Jan 7 00:02:20 host1 kernel: st 1:0:0:0: reservation conflict The second host has one directly-attached fiber drive: Jan 1 00:00:45 host2 kernel: st 0:0:0:0: reservation conflict Jan 2 00:02:13 host2 kernel: st 0:0:0:0: reservation conflict Jan 3 00:00:44 host2 kernel: st 0:0:0:0: reservation conflict Jan 4 00:00:45 host2 kernel: st 0:0:0:0: reservation conflict Jan 5 00:00:45 host2 kernel: st 0:0:0:0: reservation conflict Jan 6 00:00:44 host2 kernel: st 0:0:0:0: reservation conflict Jan 7 00:00:44 host2 kernel: st 0:0:0:0: reservation conflict The two servers are setup identical for the most part as the other two with the exception noted above for sotware. For hardware they are using newer HBAs etc. However, in 6.5.x I also see the SCSI reservation option has changed: In 6.0MP7: Go to Master Server Properties - Media [x] Enable SCSI reserve / release In 6.5.x: Go to Master Server Properties - Media [x] Enable SCSI reserve (o) SPC-2 SCSI reserve ( ) SCSI Persistent reserve 1. Do you think the issue was caused by the absence of the mt-st package on the two hosts? 2. Or, are the two newer servers (with newer/different qlogic fiber cards), do they need a specific settings, perhaps SCSI Persistent reserve and not SPC-2 SCSI reserve? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 6.5.x oddity: st 0:0:0:0: reservation conflict
On Wed, 7 Jan 2009, Justin Piszcz wrote: Anyone ever seen this before? I have 4 servers, 2 old and 2 new, all run 6.5.2a, now 6.5.3 as of this morning. I see this error occur in the logs a few moments after midnight, every night. I did notice mt-st was not installed on the machines that were getting this error, so I installed that and we'll see if the issue recurs for tomorrow; however, was curious if anyone had seen this? The first host has two directly-attached fiber drives: Jan 4 00:02:19 host1 kernel: st 0:0:0:0: reservation conflict Jan 5 00:01:19 host1 kernel: st 0:0:0:0: reservation conflict Jan 5 00:01:47 host1 kernel: st 1:0:0:0: reservation conflict Jan 6 00:01:18 host1 kernel: st 1:0:0:0: reservation conflict Jan 6 00:02:18 host1 kernel: st 0:0:0:0: reservation conflict Jan 7 00:01:18 host1 kernel: st 0:0:0:0: reservation conflict Jan 7 00:02:20 host1 kernel: st 1:0:0:0: reservation conflict The second host has one directly-attached fiber drive: Jan 1 00:00:45 host2 kernel: st 0:0:0:0: reservation conflict Jan 2 00:02:13 host2 kernel: st 0:0:0:0: reservation conflict Jan 3 00:00:44 host2 kernel: st 0:0:0:0: reservation conflict Jan 4 00:00:45 host2 kernel: st 0:0:0:0: reservation conflict Jan 5 00:00:45 host2 kernel: st 0:0:0:0: reservation conflict Jan 6 00:00:44 host2 kernel: st 0:0:0:0: reservation conflict Jan 7 00:00:44 host2 kernel: st 0:0:0:0: reservation conflict The two servers are setup identical for the most part as the other two with the exception noted above for sotware. For hardware they are using newer HBAs etc. However, in 6.5.x I also see the SCSI reservation option has changed: In 6.0MP7: Go to Master Server Properties - Media [x] Enable SCSI reserve / release In 6.5.x: Go to Master Server Properties - Media [x] Enable SCSI reserve (o) SPC-2 SCSI reserve ( ) SCSI Persistent reserve 1. Do you think the issue was caused by the absence of the mt-st package on the two hosts? 2. Or, are the two newer servers (with newer/different qlogic fiber cards), do they need a specific settings, perhaps SCSI Persistent reserve and not SPC-2 SCSI reserve? Justin. Minor addition: It is occuring on all four servers, the kernel ring buffer aka (dmesg) was filled up with other miscellaneous items, I will change the SCSI reserve to be persistent and see if the errors persist. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] socket read and write error
If the clients are UNIX or Linux you can try doing login from the master to the client then doing a check to see from which IP or hostname the login appears on the client. If it shows IP instead of hostname it might be a sign the IP isn't recognized as the master's hostname. -Original Message- From: monalisa.ku...@wipro.com [mailto:monalisa.ku...@wipro.com] Sent: Wednesday, January 07, 2009 9:11 AM To: Jeff Lightner; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] socket read and write error Hi, Thanks fr the reply bt we have not made any change in the n/w but all the bkps except the catalog are failing fr all clients.The customer is saying tht they have not done any chnge to their n/w bt from last week the bkp is failing.I can tell you tht it is running with NBU version 5.0 and solaris as the master server Os. thanks regards, Monalisa Kundu | ES-Practice Engineer | Wipro No.30, Divyasree Mission Road, Ist Main, S.R.Nagar Bangalore-560026 Mobile No.:09731398129 -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jeff Lightner Sent: Wednesday, January 07, 2009 6:15 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] socket read and write error I saw a lot of these recently (and status 25 as well). It was because our master had two NICs in our backup LAN IP range and the routing we'd setup had gotten screwed up. I was able to solve it temporarily by adding the master server twice to /etc/hosts on the clients that were failing using both the IPs from the NICs on the master. That way regardless of which IP the traffic came from the client would see it as the master. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of monalisa Sent: Wednesday, January 07, 2009 1:32 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] socket read and write error can anyone tell me what can be the reason of socket read and write error with error code 23 and 24 in NBU. +-- |This was sent by monalisa.ku...@wipro.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Tape media destruction questions.
Had a few questions. 1. How do you handle it? 2. You can send tapes off-site to Iron Mountain, degauss them before you send them off-site, that is one option. 3. How much are the machines that securely and physically destroy the tape media? 4. If they're physically destroyed, how do you deal with the tape shards, how do you dispose of the material? How do others on this list deal with bad tapes (with thousands of errors etc) how do you properly dispose of them? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Tape media destruction questions.
I the past when I have had to get rid of a bunch of old media. I did some net searching and found a company that specifically dealt with this as well as equipment recycling. They agreed a price for the amount of tapes that I had; collected them and then they were confidentially destroyed. I believe they were put in a furnace. We were then issued with a certificate of destruction as proof. This avoided any messing around with degaussing, erasing etc. James Justin Piszcz wrote: Had a few questions. 1. How do you handle it? 2. You can send tapes off-site to Iron Mountain, degauss them before you send them off-site, that is one option. 3. How much are the machines that securely and physically destroy the tape media? 4. If they're physically destroyed, how do you deal with the tape shards, how do you dispose of the material? How do others on this list deal with bad tapes (with thousands of errors etc) how do you properly dispose of them? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Systems Administrator Backups Storage Team Wellcome Trust Sanger Institute Wellcome Trust Genome Campus Hinxton, Cambridge. CB10 1SA -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Tape media destruction questions.
On Wed, Jan 7, 2009 at 8:43 AM, Justin Piszcz jpis...@lucidpixels.comwrote: 1. How do you handle it? 2. You can send tapes off-site to Iron Mountain, degauss them before you send them off-site, that is one option. Iron Mountain also offers a tape destruction service. For a fee, of course. 3. How much are the machines that securely and physically destroy the tape media? 4. If they're physically destroyed, how do you deal with the tape shards, how do you dispose of the material? That's why we pay a fee to have it done. So we don't have to deal with the garbage. We have never to worry about degausing tapes because for starters, we encrypt all of them. Even if they sit on a pallet here waiting for enough tapes to be sent out for destruction, we're still okay. That's one of the many advantages with an encrypt ALL of the tapes policy. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Tape media destruction questions.
You might want to degauss even before sending out to such a company. At least one poster on this list noted how he had gotten used tapes that were supposedly wiped but on checking he found other people's data. As for us we degauss any bad tapes after images have expired in NBU. We don't destroy until then on the off chance we'll need to send to someone like Pivar to try to extract what can be extracted. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of James Osbourn Sent: Wednesday, January 07, 2009 9:55 AM To: Justin Piszcz Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Tape media destruction questions. I the past when I have had to get rid of a bunch of old media. I did some net searching and found a company that specifically dealt with this as well as equipment recycling. They agreed a price for the amount of tapes that I had; collected them and then they were confidentially destroyed. I believe they were put in a furnace. We were then issued with a certificate of destruction as proof. This avoided any messing around with degaussing, erasing etc. James Justin Piszcz wrote: Had a few questions. 1. How do you handle it? 2. You can send tapes off-site to Iron Mountain, degauss them before you send them off-site, that is one option. 3. How much are the machines that securely and physically destroy the tape media? 4. If they're physically destroyed, how do you deal with the tape shards, how do you dispose of the material? How do others on this list deal with bad tapes (with thousands of errors etc) how do you properly dispose of them? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Systems Administrator Backups Storage Team Wellcome Trust Sanger Institute Wellcome Trust Genome Campus Hinxton, Cambridge. CB10 1SA -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] nbu 6.5.1 lifecycle policy issue
Regarding the error you are getting - you might want to open a trouble ticket with Symantec. For the error: Caught CORBA SystemException from SSmgrOperations: system exception, ID 'IDL:omg.org/CORBA/NO_PERMISSION:1.0' OMG minor code (0), described as '*unknown description*', completed = NO 1. There are several binary updates available ( I have rev 6 of nbpem ) 2. Check your daemons (on unix) nbstserv has a tendency to core dump/stop and cause these errors. 3. Be aware you can overload the database! I had set up a script that would deactivate all my SLP: for i in `/usr/openv/netbackup/bin/admincmd/nbstl -L | grep -i name | cut -c38-` do echo Now deactivating $i /usr/openv/netbackup/bin/admincmd/nbstlutil inactive -lifecycle $i done and I found that you can overload the database with too many changes, and cause this type issue as well. Hope one of these helps you! BTW - symantec has recommended to me that I should go to 6.5.3! I put the nbpem rev 6 (ETRACK 1448343)on our ftp site for you. The significant changes in here for your environment are timer conflict corrections that can impact correct rescheduling of due dates and recognition of schedule changes. We still urge you to upgrade to 6.5.3 as soon as possible, for several other SLP issues are resolved in that release. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Tape media destruction questions.
I use a company to do it. Was Media Recovery - Now known as dataSPAN. 1) They will degauss onsite before the tapes leave your building 2) They may buy the tapes from you after that (they clean and sell them as used - because they are degaussed before they leave your site they are good to go) 3) They will also physically destroy them and take care of the disposal of the leftovers in proper environmentally fashion. 4) You can get a certificate that says you had so many tapes or cd's destroyed for audit compliance. I have used them for years. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: Wednesday, January 07, 2009 8:43 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Tape media destruction questions. Had a few questions. 1. How do you handle it? 2. You can send tapes off-site to Iron Mountain, degauss them before you send them off-site, that is one option. 3. How much are the machines that securely and physically destroy the tape media? 4. If they're physically destroyed, how do you deal with the tape shards, how do you dispose of the material? How do others on this list deal with bad tapes (with thousands of errors etc) how do you properly dispose of them? Justin. ___ 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] Tape media destruction questions.
The government requires that tapes be smelt but I don't know what they are supposed to smell like :-) Bob Stump Fidelity National Information Services -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of judy_hinchcli...@administaff.com Sent: Wednesday, January 07, 2009 9:50 AM To: jpis...@lucidpixels.com; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Tape media destruction questions. I use a company to do it. Was Media Recovery - Now known as dataSPAN. 1) They will degauss onsite before the tapes leave your building 2) They may buy the tapes from you after that (they clean and sell them as used - because they are degaussed before they leave your site they are good to go) 3) They will also physically destroy them and take care of the disposal of the leftovers in proper environmentally fashion. 4) You can get a certificate that says you had so many tapes or cd's destroyed for audit compliance. I have used them for years. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: Wednesday, January 07, 2009 8:43 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Tape media destruction questions. Had a few questions. 1. How do you handle it? 2. You can send tapes off-site to Iron Mountain, degauss them before you send them off-site, that is one option. 3. How much are the machines that securely and physically destroy the tape media? 4. If they're physically destroyed, how do you deal with the tape shards, how do you dispose of the material? How do others on this list deal with bad tapes (with thousands of errors etc) how do you properly dispose of them? Justin. ___ 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 _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Tape media destruction questions.
I wondered what they did with the leftovers. I just never got into the details. Was told they were deposed of in the proper way. I have seen the claw thing that breaks/shreds/crushes the tapes into small bits. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Stump, Bob A Sent: Wednesday, January 07, 2009 10:49 AM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Tape media destruction questions. The government requires that tapes be smelt but I don't know what they are supposed to smell like :-) Bob Stump Fidelity National Information Services -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of judy_hinchcli...@administaff.com Sent: Wednesday, January 07, 2009 9:50 AM To: jpis...@lucidpixels.com; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Tape media destruction questions. I use a company to do it. Was Media Recovery - Now known as dataSPAN. 1) They will degauss onsite before the tapes leave your building 2) They may buy the tapes from you after that (they clean and sell them as used - because they are degaussed before they leave your site they are good to go) 3) They will also physically destroy them and take care of the disposal of the leftovers in proper environmentally fashion. 4) You can get a certificate that says you had so many tapes or cd's destroyed for audit compliance. I have used them for years. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: Wednesday, January 07, 2009 8:43 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Tape media destruction questions. Had a few questions. 1. How do you handle it? 2. You can send tapes off-site to Iron Mountain, degauss them before you send them off-site, that is one option. 3. How much are the machines that securely and physically destroy the tape media? 4. If they're physically destroyed, how do you deal with the tape shards, how do you dispose of the material? How do others on this list deal with bad tapes (with thousands of errors etc) how do you properly dispose of them? Justin. ___ 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 _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ 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] Tape media destruction questions.
On Wed, Jan 7, 2009 at 10:48 AM, Stump, Bob A bob.a.st...@fnis.com wrote: The government requires that tapes be smelt Sounds fishy to me :-) http://en.wikipedia.org/wiki/Smelt .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] nbu 6.5.1 lifecycle policy issue
David McMullin wrote: Regarding the error you are getting you might want to open a trouble ticket with Symantec. For the error: Caught CORBA SystemException from SSmgrOperations: system exception, ID 'IDL:omg.org/CORBA/NO_PERMISSION:1.0' OMG minor code (0), described as '*unknown description*', completed = NO ![if !supportLists]1. ![endif]There are several binary updates available ( I have rev 6 of nbpem ) ![if !supportLists]2. ![endif]Check your daemons (on unix) nbstserv has a tendency to core dump/stop and cause these errors. ![if !supportLists]3. ![endif]Be aware you can overload the database! I had set up a script that would deactivate all my SLP: for i in `/usr/openv/netbackup/bin/admincmd/nbstl -L | grep -i name | cut -c38-` do echo Now deactivating $i /usr/openv/netbackup/bin/admincmd/nbstlutil inactive -lifecycle $i done and I found that you can overload the database with too many changes, and cause this type issue as well. Hope one of these helps you! BTW symantec has recommended to me that I should go to 6.5.3! I put the nbpem rev 6 (ETRACK 1448343)on our ftp site for you. The significant changes in here for your environment are timer conflict corrections that can impact correct rescheduling of due dates and recognition of schedule changes. We still urge you to upgrade to 6.5.3 as soon as possible, for several other SLP issues are resolved in that release. Thanks for the update. I did open a call with Symantec and they came back with the same solution. Upgrade to 6.5.3. However, we just completed the upgrade to 6.5.1. from 5.1 and have all the clients at 6.5.1. Upgrade was painful and so don't want to change to 6.5.3.. Might end up sticking with old vault. +-- |This was sent by s.me...@ieee.org via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Duplication job
Hello, We have duplicated some tapes using catalog backup. After duplication, when we search the images from the original copy, It says skipping media id xx it has already two copies. What is the reason? Duplication process can expire the images on the primary copy? Regards, ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] nbu 6.5.1 lifecycle policy issue
On Wed, Jan 7, 2009 at 11:09 AM, smehta netbackup-fo...@backupcentral.comwrote: Thanks for the update. I did open a call with Symantec and they came back with the same solution. Upgrade to 6.5.3. However, we just completed the upgrade to 6.5.1. from 5.1 and have all the clients at 6.5.1. Upgrade was painful and so don't want to change to 6.5.3.. Not and day difference between the upgrade from 5.1 to 6.x and 6.5.1 to 6.5.3. You can leave your clients at 6.5.1 and upgrade the master to 6.5.3 and this will help with your master server issues with minimum pain. The vast majority of my clients are still 6.5.1. Some are even 6.0. To upgrade to 6.5.3,. you only need to do your master and your NOM server. Media servers can be done, but don't need to be. Clients only need to be done if you have a specific requirement for an individual client (e.g. Exchange Granular Restore).If you chose to upgrade a client, however, its media server also needs to be upgraded. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] nbu 6.5.1 lifecycle policy issue
We're running 6.5.1 and not having this issue. Also FYI - Upgrade from 6.5.1 to 6.5.3 would not be as painful as the one you just went through. From 5.1 to 6.0 there was a major change in the way things were done. We upgraded from 6.0 to 6.5 with no real issues. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of smehta Sent: Wednesday, January 07, 2009 12:09 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] nbu 6.5.1 lifecycle policy issue David McMullin wrote: Regarding the error you are getting - you might want to open a trouble ticket with Symantec. For the error: Caught CORBA SystemException from SSmgrOperations: system exception, ID 'IDL:omg.org/CORBA/NO_PERMISSION:1.0' OMG minor code (0), described as '*unknown description*', completed = NO ![if !supportLists]1. ![endif]There are several binary updates available ( I have rev 6 of nbpem ) ![if !supportLists]2. ![endif]Check your daemons (on unix) nbstserv has a tendency to core dump/stop and cause these errors. ![if !supportLists]3. ![endif]Be aware you can overload the database! I had set up a script that would deactivate all my SLP: for i in `/usr/openv/netbackup/bin/admincmd/nbstl -L | grep -i name | cut -c38-` do echo Now deactivating $i /usr/openv/netbackup/bin/admincmd/nbstlutil inactive -lifecycle $i done and I found that you can overload the database with too many changes, and cause this type issue as well. Hope one of these helps you! BTW - symantec has recommended to me that I should go to 6.5.3! I put the nbpem rev 6 (ETRACK 1448343)on our ftp site for you. The significant changes in here for your environment are timer conflict corrections that can impact correct rescheduling of due dates and recognition of schedule changes. We still urge you to upgrade to 6.5.3 as soon as possible, for several other SLP issues are resolved in that release. Thanks for the update. I did open a call with Symantec and they came back with the same solution. Upgrade to 6.5.3. However, we just completed the upgrade to 6.5.1. from 5.1 and have all the clients at 6.5.1. Upgrade was painful and so don't want to change to 6.5.3.. Might end up sticking with old vault. +-- |This was sent by s.me...@ieee.org via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Duplication job
On Wed, Jan 07, 2009 at 07:16:26PM +0200, Asiye Yigit wrote: We have duplicated some tapes using catalog backup. After duplication, when we search the images from the original copy, It says skipping media id xx it has already two copies. What do you mean by search the images? What commands are you running that generate that output? -- Darren ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU 6.5.3 on Windows and VMWARE Backups
Thanks. When I do my restore test, I will let you know. For now it is going to be 3 - FullVM and File for Incrementals Cheers MK --- On Tue, 1/6/09, bob944 bob...@attglobal.net wrote: From: bob944 bob...@attglobal.net Subject: Re: [Veritas-bu] NBU 6.5.3 on Windows and VMWARE Backups To: veritas-bu@mailman.eng.auburn.edu Cc: mikeki...@yahoo.com Date: Tuesday, January 6, 2009, 8:56 AM I am configuring VCB backups for NBU 6.5.3, for FlashBackup-Windows policy, there are 4 options for backup types under Snapshot Client Options. These are 0 - File 1 - FullVM 2 - Mapped FullVM 3 - FullVM and File for Incrementals From reading the docs, Option 3 - FullVM and File for Incrementals, looks like best of both world, it will let me restore single files and restore full guest VM. It also allows incremental level backups. Is there any disadvantage when using it compraed to other types. I am trying to avoid running 2 or more backups to completely protect a VM. 3 is the correct choice; it does exactly what the manual says it does: a snapshot backup of the vmdk for a full (and from which you can restore individual files or the whole VM), and a normal, file-based backup for incrementals. Set up the schedules in the same policy, throw windows and clients at it and it will work like you expect NetBackup to work. It worked as advertised in my test environment, though my restore testing was minimal. An aside: Restoring files to VMs is, to somebody not used to VMware, kludgy, so do read up on how to restore and test that part before you need it. ___ 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
