Error - Failed To Recover Nbdb On 5
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : DR scenario will recover most everything, but not ... VOX : Backup and Recovery : NetBackup : DR scenario will recover most everything, but not ... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page DR scenario will recover most everything, but not *db jim_dalton Level 6 10-29-2012 09:05 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content HI Folks Im thinking this is a NB bug but anyway theres a lot of folks in the forum with experience that may be able to shed some light. Scenario: Sol10 Sparc master, NB7504. Some other media servers, including a Windows box in the DR site. Also at DR site: Sol10 x86DR master server, shut down most of the time. Previously tested: catalog written by Sol10 sparc master recovered onto Sol10 x86 master in DR. No problems. Both masters have the same name. 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. And now I'm testing it. I've got my override to tell it that it needs to not use the originalmedia server: FORCE_RESTORE_MEDIA_SERVER =
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup Appliance : Problem Recovering Netbackup Catalog VOX : Backup and Recovery : NetBackup Appliance : Problem Recovering Netbackup Catalog Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top https://vox.veritas.com/t5/NetBackup/DR-scenario-will-recover-most-everything-but-not-db/td-p/563198 Bookmark Subscribe Printer Friendly Page Problem Recovering Netbackup Catalog Alberto_Colombo Level 4 Partner Accredited 05-31-2012 03:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, i've a question about restoring FULL Netbackup 7.1 Catalog using N5000 Appliance (in DR site) Here is my setup: One NetBackup Master Server 7.1.0.3 with RHEL 5.6 on a Virtual https://vox.veritas.com/t5/NetBackup-Appliance/Problem-Recovering-Netbackup-Catalog/td-p/502638 Machine (vmware) - it's a CLONE of our Master Netbackup PROD server (same ip - same hostname) one N5000 with FW 1.4.1.1 one N5020 with FW 1.4.1.1 we have a SLP in our PROD env which manage catalog backup: 1) catalog is backupped on N5020 and 2) then is duplicated on N5000 in our DR site we have tried to restore one catalog backup from N5000 in this way: 1. Create the disk storage server for the storage using the disk storage server wizard on the master server you are recovering to 2. Create the disk pool for the storage using the disk pool wizard at this point our Netbackup Master DR Clone can see N5000. Now, we ran the command ‘nbcatsync -sync_dr_file
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In https://vox.veritas.com/t5/NetBackup/catalog-full-recovery-failed-with-error-code-2850/td-p/612495 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/catalog-restore-failing-after-upgrade-to-6-5-4-100787/ Do you mean VOX : Backup and Recovery : NetBackup : catalog full recovery failed with error code 2850 VOX : Backup and Recovery : NetBackup : catalog full recovery failed error - with error code 2850 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page catalog full recovery failed with error code 2850 demo4119 Level 6 Partner Accredited Certified 05-22-2013 08:54 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content error - failed when i do a catalog recovery using the3 copies of hot catalog backup , it will failed with error code 2850 during the database restore. and when i run a bprecover -r -nddbit failed with error code 83 Kindly advise how can i ensure that the dr file im using it working copy. Labels: 7.5 Backup and Recovery NetBackup Recovering Windows Server (2003-2008) 0 Kudos Reply 4 Replies had you chech this tech StefanosM Level 6 Partner Accredited Certified 05-22-2013 09:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content had you chech this tech note: http://www.symantec.com/business/support/index?page=content&id=TECH191623&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1369238881573d3c467GEM0uILvmRUq9e4Nk1G4z0d46GYOika from what storage you are restoring the databade? tape, basic disk, advanced disk or deduplication? 0 Kudos Reply What do you mean by "3 copies watsons Level 6 05-22-2013 03:23 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content What do you mean by "3 copies of hot catalog backup"? Usually you just need to select 1 drfile (based on your recovery date/time point) from the catalog di
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » Symantec NetBackup » Catalog restore failing after upgrade to 6.5.4 The time now is Sun Oct 09, 2016 6:38 pm View previous topic | View next topic Page 1 of 1 Catalog restore failing after upgrade to 6.5.4 Author Message mdglazerman Joined: 04 Feb 2008 Posts: 148 Catalog restore failing after upgrade to 6.5.4 We upgraded to 6.5.4 about 4 months ago and have just started preparing for our first DR test at this version level (previous successful tests at 6.5.1). We have a support call open with datalink because we have so far been unable to restore our catalog to our test master server. The catalog restore (initiated with bprecover -wizard) restores all the client images (25GB or so) but pukes every time with the following error… 12:58:19.201 [13861] <16> bprecover: ERR - Failed to find last NBDB backup image record for client nbumaster01.sun.spartech.com with policy NBU_CATALOG_HOT (227) 12:58:19.221 [13861] <16> bprecover: Failed to recover catalog (227) Has anyone out there seen anything similar since upgrading to 6.5.4 ? As a point of reference our test master server is configured and patched exactly like our production box. Our worry is that besides issues in testing, we may have exposed a huge hole in our production restore capabilities with regard to a master server loss. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spar