Failed To Recover Nbdb 5
Did you include the DR file as well?But that failure looks a bit strange..[www.symantec.com][seer.entsupport.symantec.com]Etrack Incident = ET834802Description:Catalog recovery from a hot catalog backup would fail with thefollowingerror when the entry for Scenario: Sol10 Sparc master, NB7504. The steps we’ve done are: 1. Handy NetBackup Links 0 Kudos Reply Hi MvdB The only issue I can jim_dalton Level 6 10-30-2012 06:13 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print http://homecomputermarket.com/failed-to/failed-to-recover-nbdb-13.html
I have copied the catalog backup (disk stu) from production master to the Test Master server (without DRFILE). Please wait... 23:49:52 ERR - Failed to recover NBDB on testnbmaster2 (5) Thanks in advance, PD Labels: 7.5 Backup and Recovery Central Admin Server Option NetBackup 0 No Yes Did this article save you the trouble of contacting technical support? Inventory the robot or add the media for standalone drives.13.
No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES C:\Program Files\Veritas\NetBackup\bin>nbdb_admin -auto_start BMRDBSuccessfully added BMRDB to databases.conf. 9. I do feel it ought to be documented, maybe thats just me expecting too much.
Rebuilding the DR server OSat present, also just to make sure I understood all the details and restrictions correctly... But right at the end I have issues: It wont restore anything from /usr/openv/db/staging eg BMRDB, BMRDATA , (the kind of stuff you need at DR!) , theres maybe 20 files Thanks, Prati 0 Kudos Reply IP can be different, but Marianne Moderator Partner Trusted Advisor Accredited Certified 02-04-2013 11:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed You have to copy this across (the DR file).
Ensure that DR site does not run ANY backups, else production tapes WILL be overwritten because EMM database was not restored and all media is seen as NEW/Available. we've been down a week trying to recover.Any suggestions appreciated. Only thing I can think of 1) is to let it fail, then re-run bprecover -nbdb with the FORCE_RESTORE put back, or 2) Recover the NBDB files via browsing that catalog https://vox.veritas.com/t5/NetBackup/NBU-7-5-catalog-recovery-error/td-p/517993 but should work as the only info you need for the are the images header/ .f files which I think you have recovered.
SeeAbout recovering the NetBackup catalog. i'm running out of ideas, any help is appreciated!!! Handy NetBackup Links 0 Kudos Reply js- this is a catalog jim_dalton Level 6 10-30-2012 03:49 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Same hostname (if original server used shortname, you also need to use shortname on new server) 2.
Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem DOCUMENTATION: How to create a blank NetBackup NBDB database for the recovery of my response Veritas does not guarantee the accuracy regarding the completeness of the translation. If you have received this email in error please notify the sender immediately, and do not copy or forward it.Reply Quotejpiszcz Catalog restore failing after upgrade to 6.5.4September 22, 2009 05:25PM Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : total meltdown - unablle to recover nbdb Subscribe to RSS Feed Mark Topic as
For me, this works. navigate here When it installs it has to communicate with itself by the real Masters name, as it can resolve this to itself it will work and will also restore the catalog etc. Thank You! This would occur when there were two NICs in the master server."Failed to find last NBDB backup image record for client serverNamewith policy policyName (227)"Has anything changed in your environment besides
WDoing the steps in the recovery section of the troubleshooting manual, I get this on step 11, page 570.##> /usr/openv/netbackup/bin/admincmd/bprecover -r -nbdbERR - Failed to find last NBDB backup image record Simply add all media to DR robot, Run Device Config wizard, followed by inventory. Actually We've need to migrate from master1 attached to tape library1(end of life) to master2 attached to tape library2(new) and thats why need to make sure that catlog recovery works so http://homecomputermarket.com/failed-to/failed-to-parse-source-failed-to-resolve-schema-nsuri-location-persistence.html Error fron bprecover: 17:24:58 (20.001) INF - TAR EXITING WITH STATUS = 0 17:24:58 (20.001) INF - TAR RESTORED 360028 OF 360028 FILES SUCCESSFULLY 17:24:58 (20.001) INF - TAR KEPT 0
I have copied the catalog backup (disk stu) from production master to the Test Master server (without DRFILE). For online catalog recovery, run the following command on the master server: UNIX: /usr/openv/netbackup/bin/admincmd/bprecover -r -nbdbWindows: Start the Device Manager service.
then on the restore server you have to have the same thing with thesame hostname as well, or else it won't work.3.
Regards, Alberto 0 Kudos Reply catalog restore not working Alberto_Colombo Level 4 Partner Accredited 06-28-2012 06:31 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : DR scenario will recover most everything, but not ... We'd blown away the netbackup install on the remote test server and hadn't recreated this link. Symantec Corporation is committed to product quality and satisfied customers.
Email Address (Optional) Your feedback has been submitted successfully! To start the database, run the command: C:\Program Files\Veritas\NetBackup\bin>bpup -e SQLANYs_VERITAS_NB NetBackup 7.0 -- Startup Utility NetBackup services are about to be started.Do you wish to proceed? (y/n) yStarting services Start Handy NetBackup Links 0 Kudos Reply There is a little cheat if it Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified 02-04-2013 11:44 AM Options Mark as New Bookmark Subscribe Subscribe to this contact form I'm sorry if I wasn't clear in specifiying our requirement earlier...
If the directory does not exist, create it and retry the restore. the restore of images finished successfully. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Go to Solution.
So it may be that you have to do the following: 1. Remove NBDB and BMRDB from auto_start option C:\Program Files\Veritas\NetBackup\bin>nbdb_admin -auto_start NONESuccessfully removed NBDB from databases.confSuccessfully removed BMRDB from databases.conf 4. To force database recovery, run the command (please note, the NBDB.log will not be created until step 10): C:\Program Files\Veritas\NetBackupDB\win64>dbsrv11 "C:\Program Files\Veritas\NetBackupDB\data\NBDB.db" -f If BMR is used , force recovery of Stop NetBackup if it is not already stopped: C:\Program Files\Veritas\NetBackup\bin\bpdown -v 2.
Please wait...Import phase 1 started Tue Aug 20 12:58:24 2013 INF - unable to obtain disk volume information(2007031): My_STU: NEW_stu(DataDomain)@Server INF - Error obtaining disk media id information : error (142) Great ... However as aboveI've got a media server (the Windows box) at my DR site and I've configged a policy to write the catalog to that. Email Address (Optional) Your feedback has been submitted successfully!
As Marianne suggest check bptm but bpdm as well. 0 Kudos Reply Recovery successfull muru Level 2 09-17-2011 05:15 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Verify that all NetBackup processes are stopped: C:\Program Files\Veritas\NetBackup\bin\bpps Manually kill any remaining NetBackup processes. 3. if /usr/openv -> /mypartition2. No Yes Did this article save you the trouble of contacting technical support?
Did you include the DR file as well?But that failure looks a bit strange..[www.symantec.com][seer.entsupport.symantec.com]Etrack Incident = ET834802Description:Catalog recovery from a hot catalog backup would fail with thefollowingerror when the entry for To test if the database is operational, run the command: C:\Program Files\Veritas\NetBackup\bin>nbdb_ping which should return something similar to the following: Database [NBDB] is alive and well on server [NB_master1]. 11. My feeling is that whilst it does the restore, it restores bp.conf, and when it has done that, it no longer has the FORCE_RESTORE_MEDIA_SERVER entry for the media servers I no If the nbdb_move command was used to relocate NetBackup database files, re-create the directories where the files were located at the time of the catalog backup. The default location is: UNIX: