[Veritas-bu] Re: Veritas-bu digest, Vol 1 #4839 - 4 msgs
On Wed, 2006-02-08 at 09:46 -0600, [EMAIL PROTECTED] wrote: Date: Wed, 8 Feb 2006 18:43:08 +0400 From: Naidu V. T. [EMAIL PROTECTED] To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Email Notification from Netbackup 5.1 (Windows) Hi All, We have one Master Server Netbackup 5.1 on Windows 2003 and 7 SAN Media Servers all on Windows except one media server on Solaris. Our customer Wants email notification only when backups have failed. Can anybody suggest Me how to notify only failed jobs. Regards V.T.Naidu If you go to my website at http:/www.gurski.com/netbackup.php and select the windows command menu option, you will find several scripts available, including the one you want... Enjoy -- Ed Gurski [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] running out of memory on Solaris 8 master servers
On Wed, Dec 21, 2005 at 08:51:45AM -0700, King, Cheryl wrote: I have two Solaris 8 master servers running NetBackup 5.1 MP3S2. They keep running out of memory after a few months. I'm wondering if anyone else has this problem and if they fixed it. It started some time after going to v5.1 I think. Maintenance hasn't fixed it. We've been seeing this as well on Solaris 9 with NBU 5.0. We're currently at MP6. Any ideas on what's causing it or how I could find out what's causing it? When it runs out of memory it's always during regular backups. Backups take memory so they're victims. We see a nice jump in swap utilization every time our main windows open at 6pm. Since I haven't seen any discussion about this on this list I'm assuming regular scheduled backups isn't the cause. The only way to get back swap space is to boot the server. Add swap :-). That's our workaround until we can upgrde the server with a new box (unfortunately our 420 is maxed out for memory already). We run the rman Oracle instance on our master server and it appears to be part of the culprit. We had it off for a while and we were much better. We don't know if it's the straw that breaks the camel's back or if it's the cause. NetBackup really doesn't like to run out memory (not that I blame it much) - all the jobs terminate with a 150. Are other Solaris admins experiencing the same issues? Does NetBackup just take that much memory to run? I have heard that NBU 6 takes a lot of memory than NBU 5 but haven't been able to validate that yet. .../Ed I ran into this problem on Solaris 9 and the problem kept getting worse. It is now somewhat resolved What was casuing the problem --- there are possibly two culprits -- 1) bpschedule takes up a huge chunk of processor and nothing gets started --- There is a fix in 5.1 MP4 according to Symantec/Veritas 2) NIC Trunking --- this was our problem and there is no immediate fix. I spoke with Sun engineers at length --- I got two solutions --- one was to update to the latest patch --- which doesn't work and has since been pulled. The other is to downgrade to the previous patch level. Now my NBU servers were brand new V440's so I trunked them. The problem is the downgraded trunking software does not work. So I am running on a single NIC on my Master server. The 2 media servers are not affected --- It's a volume related issue --- so it explains your observation. I was able to acquire a spare V440 and will be testing Solaris 10 which I am assured by SUN has better trunking software and the TCP/IP stack is about 30% faster. I do have a script that I run to determine if the kernel is taking too much memory --- it should normally take less than 15%, but once it starts growing you know you have a problem. I empathize with you since it worked on this problem for 2 months and could not find anything. I finally called our solution provider and we were able to get both Sun and Symantec involved... I hope this helps -- Ed Gurski [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 5.1 MP4 Vault eject failures
On Thu, 2005-12-15 at 13:11 -0600, [EMAIL PROTECTED] wrote: Date: Thu, 15 Dec 2005 12:10:00 -0600 From: Lien, Mitch [EMAIL PROTECTED] To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Netbackup 5.1 MP4 Vault eject failures Hi. We have a Vault duplication job that duplicates Virtual tapes (using a EMC CDL) onto standard tapes (using 9940B drives/L700 Tape Lib). Within the Vault Profile, we have 00_009_TLD as the source Volume Group. This volume group is used by our EMC CDL (Virtual Tape library). The destination tape library we are duplicating to has a Volume Group of 00_002_TLD. This volume group is used by our STK L700 tape library and has not been entered into the Vault profile at all. When we run the Vault duplication everything is working correctly with the exception of the eject process. The tapes that are suppose to be getting ejected are not and we are seeing the following in the detail.log of the Vault session: 13:40:53.646 [8218] GenMediaEjectList(): media M01212 selected but not in robot group '00_009_TLD', skipping eject 13:40:53.646 [8218] GenMediaEjectList(): media M01443 selected but not in robot group '00_009_TLD', skipping eject 13:40:53.646 [8218] GenMediaEjectList(): media M01657 selected but not in robot group '00_009_TLD', skipping eject 13:40:53.646 [8218] GenMediaEjectList(): media M02162 selected but not in robot group '00_009_TLD', skipping eject We think the issue has something to do with the source Volume Group of 00_009_TLD mentioned above, but are not sure. The first tape, M01212, is in the 00_002_TLD volume group and we do not know why it cares that it is not in the 00_009_TLD group. Any help would be appreciated. Thanks. Mitch Mitch: If you are running on a Unix master server then the problem is a lock file that was previously used but not removed. The lock file(s) are normally stored in /usr/openv/volmgr/misc. They will have lock as the suffix or the middle part of the filename. It is OK to delete them --- I've run into this wit 5.1 MP3 MP4. Symantec's solution is to delete them. If you're running windows, then it's probably in (instal_path)/volmgr/misc HTH -- Ed Gurski [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Custom Reporting in NB?
On Wed, 2005-11-02 at 12:09 -0600, Date: Wed, 02 Nov 2005 09:36:40 -0800 From: Rich McGee [EMAIL PROTECTED] To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Custom Reporting in NB? My question is rather simple. Is it possible to filter the generated e-mail backup reports so that only abnormal incidents are mailed? When people get used to seeing a dozen reports each morning, they tend to stop paying attention to exceptions. We're currently running NB V5.1, and our V6 kit arrived yesterday. Thanks! Rich McGee CSU San Bernardino Rich: If you are talking about backup_exit_notify that can be done to check your limit of failures before a message is sent. If your talking about a summary report, that is also possible. I have built several scripts for both Solaris and Windows that you might find useful. They are located at http://www.gurski.com/netbackup.php -- Ed Gurski [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
