Veritas Tech Talks: Introducing NetBackup 8.1.2 – Live VOX coverage
Welcome to the live-coverage summary feed of Veritas Tech Talks, happening now on the VOX homepage. Follow this discussion thread forepisode summaryhighlights being shared from the 4-part video series.We will share an episode summary at the end of each show, as a new comment. We welcome your questions – the NetBackup team is ready on hand to answer!
Introducing NetBackup support for Docker container workloads
Greetings everyone! Just wanted to let all of you know that we have officially released a NetBackup client for Docker containers. See this blog for the details on this announcement and where you can download the client. If you have any general questions about this new capability you can ask them here or reply to the blog. Have a nice day! Glen Simon,NetBackup Product MarketingTIL - Storing Filters in Activity Monitor
Today I learned I can store filters in the Activity Monitor window! Did you know you can store your commonly used filters (Activty Monitor only)? Top right side under Login Activity is a funnel and a down arrow triangle - that down arrow triangle opens up a small window that allows you to store your commonly used filters. I have 13 of these, to see specific jobs, or to select "media in use" or multiple attempts There is a current bug on NDMP backups with multiple attempts - store a filter that selects that host name with more than one attempt Select only status > 1 and NE 150 to see failures I only wish this was available in other views, I could use this in the media section! You can export them to a file, so you can import them when you upgrade - because you lose them!
Does postgres agent supports multiple databases backup?
Hello, I've been trying to backup two specific databases on my postgres server, but i saw only two ways of producing a backup. Either i backup a single instance by changing the parameterDB_INSTANCE_NAME onnbpgsql.conf file, or i change the variable value to *. Is there any way to backup two specific instances? Thanks in advance.Lessons learnt from DR migration to new hardware platform
Not so much as a discussion more of a "this is what caught me out" when I migrated from 2008R2 DL380 G8 to 2012R2 G10 on NetBackup 8.1.2. I hope this helps someone in the same position that I was in. So it should be a pretty simple build a vanilla corporate build. Stop all you backups, carry out a full catalogue. Shut old server down ensuring that you have the DR files and know where you backed up the catalogue to. Rename and re-IP new server to old server configuration. Install NetBackup software with same role os old server. Using the DR wizard to recover the server configuration. All pretty simple except for just one thing. The DR process installs a new CA. This now means all your clients and media servers now can no longer communicate with the master and report the the error "vnetd proxy encountered an error". Genius Looking at the sheer weight of the issue made me shudder as we have hundreds of client an the thought of having to visit each and every one would have kept me busy till christmas. The fix was buried deep in a Veritas knowledge base Article: 100043536 The command to restore your old CA prior to carrying out any restore from the DR wizard is as follows excerp from article: nbhostidentity -import -infile M:\NB_DR_FILE\NBCAT_nbmaster1_1531458511_FULL.drpkg Now you can run your DR wizard and presto you now have all your clients happily communicating with the new master server once you DR restore completes. I think that the propellor heads at Veritas need to add a checkbox to the DR wizard to ask if you want to restore your old CA. Might ulimately be mute since 8.2 you can use your own internal CA. Or did I just imagine it. :) Full articles URL: https://www.veritas.com/support/en_US/article.100043536 Happy DR'ingupdate_client scripting 8.1.2 -force option!
running update_clients, found a few issues : 1 - the script does NOT check for tmp space - if you do not have 4G space available in /tmp on the clients the install can fail - and leave the client messed up - I had to uninstall packages and delete the netbackup directory! 2 - sometimes the certificates get confused - if your client does not reconnect - vnetd error - you should run command "nbcertcmd -hostselfcheck" - make sure it is not revoked. 3 - you may have to run command "/usr/openv/netbackup/bin/nbcertcmd -getCertificate -host CLIENTNAME -server MASTERNAME" to re-establish connectivity. I have a linux box, it would not connect, vnetd issue, but all certificates showed ok, even after the above commands. Found out undocumented command 3 option -force - forces update of client certificate. "/usr/openv/netbackup/bin/nbcertcmd -getCertificate -host CLIENTNAME -server MASTERNAME -force" make a note of it!
Veritas Education Services NetBackup 8.1.2 administration training, now available
I’m pleased to announce open registration for a new Veritas Education Services course on NetBackup 8.1.2 administration. If you’re new to NetBackup, or would benefit from additional insight to the platform, this 5-day course will provide you with expert instruction on NetBackup configuration and management, including hands-on lessons on the new tools offered in NetBackup 8.1.2. With NetBackup 8.1.2: Administration, you’ll learn how to effectively monitor backup operations to ensure your organization’s data recovery objectives are met. Training is available in both Instructor-Led and Virtual Instructor-Led formats, and you may find a comprehensive course description here including the global class schedule and registration details. And for those looking to update their Veritas Certification credentials in NetBackup 8.1.2, stay tuned! We are developing the new NetBackup 8.1.2 Veritas Certified Specialist exams for release next quarter.ALERT - ISILON incrementals - succeed but backup no data! watch for attempt count!
This is NOT NB specific and is across all versions. Please be aware - there is an issue with Isilon TCP/IP and NetBackup - watch out for multiple tries on incremental backups very infrequently. Backup will complete successfully update the listing then fail and rerun successfully and backup nothing. What you see in NetBackup - incremental isilon backups succeed with multiple attempts - BUT 1st attempts find new data - backs up data - fails 2nd (or 3rd ) attempt completes with NO error - but backs up NO data! From Isilon support ( after 9 months of Veritas/Isilon fighting over whose fault it is... ) Summary After review, engineering has confirmed from the Network trace investigation that this issue is observed due to rare DMA slowness with reading from the received buffer (1-2% failure jobs). At the same time, the RST flag is sent by the Isilon node due to fast socket termination by the NDMP daemon without confirmation that all data was received by the DMA client exactly at the same slowness time on the DMA side. To improve this situation from the Isilon NDMP side, engineering is looking at the following NDMP changes: Сall shutdown() before close() The Dev team has already started this improvement in the Isilon NDMP code. Also, Engineering is working on a repro of this problem to have a lab where the code improvement can be validated. The current estimation is that the fix will take up to 4 weeks, assuming no issues. ( It has been 5 weeks now and no updated ETA... )
