[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
[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
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
[Veritas-bu] nbu 6.5.1 lifecycle policy issue
Hi, I have set up all my lifecycle policies. But when I try to inactivate the policies during the busy hours i get the following 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 Any ideas? Thanks +-- |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
