[Veritas-bu] test

2010-03-29 Thread Abhishek Dhingra1
Test Rgds A D Email : abhishek.dhin...@in.ibm.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] Error 50 for all backups

2010-03-29 Thread NBU
Dear Forum, Frequently getting error 50 for all active backups. NBU 6.5.5-- any suggestions pls. +-- |This was sent by qureshiu...@rediffmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com.

Re: [Veritas-bu] Error 50 for all backups

2010-03-29 Thread WEAVER, Simon (external)
Hi Status 50 can be a little random. Here is a Guide on Status 50, although it covers 5.x you would need to enable logging on the Client (If its windows then c:\PRogram files\Veritas\Netbackup\logs\BPCD and BPBKAR as an example). You may need to provide more info (ie: Platform of clients,

[Veritas-bu] What is SLP_Multiple_Lifecycle?

2010-03-29 Thread smpt
Hi to all, Does anyone know what SLP_Multiple_Lifecycle is? Suddenly many SLP with that name appear and I cannot find what it is. I found that even there is not such SLP configured, there is a SLP policy with that name at the class_internal directory. But only for version 6.5.5 and 7.0, not for

Re: [Veritas-bu] What is SLP_Multiple_Lifecycle?

2010-03-29 Thread Kendall, Scott
6.5.5 groups, or batches, SLP duplications differently than previous versions. You can read about it in the 6.5.5 Release Notes and I think there is an updated SLP best Practices for 6.5.5 as well. Basically, if duplications get batched together from multiple SLPs because NetBackup thinks

[Veritas-bu] Error 50 for all backups

2010-03-29 Thread NBU
Hi, Client OS are Win2008/2003/Solaris 9/10 etc Master is on Solaris 10 +-- |This was sent by qureshiu...@rediffmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com.

Re: [Veritas-bu] Error 50 for all backups

2010-03-29 Thread WEAVER, Simon (external)
Ok anything logged in the Windows Clients? Did you enable logging, as per the document I sent over to you? Anything changed in your NetBackup environment? For example, clients upgraded to a newer version or Maintenance Pack? Usually, from own experience, I see this when the NetBackup processes