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'ing
Moving MSMQ on Windows Server 2012 for EV11
There is no way to use a GUI to move MSMQ on Windows Server 2012. You can move MSMQ using PowerShell. NOTE: In the example below I have created a new MSMQ folder on G:\. The path is G:\MSMQ. You do not need to create the MessageFiles, TransactionLogs or Storage folders as they will be created automatically. To move MSMQ perform the following actions:
Netbackup - Transfer dedup storage to another storage media server
Hi All. I have a LUN from an HP P2000 storage presented to my media server. So it appears as a partition on my media server. This server is configured as a storage server in my Netbackup. and a "pure disk" disk pool and storage unit is created from it. So we are writing to this dedup disk (storage unit) since long time. Now we are bringing a new media server, and we want to transfer this dedup to it. off course we will present this LUN to the new server, so it will appear as a partition on it. But how to do this transfer between servers in Netbackup, so the current data in this dedup will remain readable and restorable in Netbackup. Any hints or Ideas ? Thanks,
Job priorities are not granular enough
This is a feature request. As verified with support, job priorities are all linked at the server level, which is definitely not granular enough for my needs. For example,if you have multiple stages or sub-jobsfor eachserver, such as backup to disk full/incremental based on daily/weekly/monthly schedule, duplicate to disk/tape, or separate verify jobs, you cannot prioritize anything beyond the main server job over other entire server jobs. Theproblem becomes much more apparentwhen you have multi-terabyte jobs that take most of the week to complete. Add on another dozen or so servers that need backed up (some of those comprised of multiple terabytes of data as well) and you have an extremelyfinite backup window and this is where better job priorities would play a huge role. For instance, it would be nice to be able to prioritizelarge verify jobs lower than thesmaller ones since they take much less time to complete, but still have the actual backup to disk job be a higher priority level. Or to be able to prioritize certain full backup to disk jobs in one order, but have a linked duplicate to tape job be a different priority level entirely. I don't think I need to try and recreate all of the different scenarios of why this feature would be beneficial. It seems like this should already be part of the software, but it isn't for some reason.
