Blog

Home > Failed To > Failed To Recover Nbdb 13

Failed To Recover Nbdb 13

You may also refer to the English Version of this knowledge base article for up-to-date information. images were successfully restored 2) i've used nbcatsync -sync_dr_file it changed the disk media id # nbcatsync -sync_dr_file /dati/INFO_DR/Catalog_bck_1340794951_FULL All media resources were located Run the commandbprecover -r -nbdbto recover only the NBDB This 'two stage' approach is required on UNIX and Linux because the catalog recovery process restores the bp.conf before restoring NBDB and How to recover a catalog backup from a Standard or... this contact form

Stop and restart NetBackup by running the following command: UNIX:   /usr/openv/netbackup/bin/goodies/netbackup stop /usr/openv/netbackup/bin/goodies/netbackup startWindows:   \NetBackup\bin\bpdown   \NetBackup\bin\bpupIf a remote EMM server is being used, start NetBackup on the remote EMM server before No Yes How can we make this article more helpful? Because this was a PARTIAL recovery of the NetBackup catalog, any remaining files included in the catalog backup can be restored using the the Backup, Archive, and Restore user interface. If you specified a DR file for a full backup, a message similar to the following is displayed: vm2.symantecs.org_1318222845 All media resources were located Do you want to recover the entire

Could you anyone help getting this fixed. Stop NetBackup by running the following command: UNIX:   /usr/openv/netbackup/bin/goodies/netbackup stopWindows:   \NetBackup\bin\bpdown  2. 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 i'll post here when i'll have some news, regards, Alberto 0 Kudos Reply Alberto There is a posssible Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified ‎06-21-2012 03:46 AM Options Mark

Create/Manage Case QUESTIONS? Sorry, we couldn't post your feedback right now, please try again later. Also at DR site: Sol10 x86DR master server, shut down most of the time. A better way, would be to use nbcatsync, which should correct the media ids in the catalog.

So it may be that you have to do the following: 1. Solution Formal Resolution:Symantec Corporation has acknowledged that the above mentioned issue (ET 3110650) is present in the current version(s) of the product(s) mentioned at the end of this article. Solved! https://vox.veritas.com/t5/NetBackup/DR-scenario-will-recover-most-everything-but-not-db/td-p/563198 Handy NetBackup Links View solution in original post 0 Kudos Reply 4 Replies Accepted Solution! "media open error" Please Marianne Moderator Partner Trusted Advisor Accredited Certified ‎09-17-2011 12:32 AM Options Mark

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Unable to recover catalog through duplicate disk c... Go to Solution. NBDB restore (EMM Database).  It tries to use only copy number 1 for this operation Error Message When this issue occurs, the admin log at VERBOSE 0 will show the following Article:000018488 Publish: Article URL:http://www.veritas.com/docs/000018488 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in

nbcatsync -backupid image_id (To fix the disk media IDs in the image headers) i’ve read here: http://www.symantec.com/business/support/index?page=content&id=TECH160521 that nbcatsync is not recommended in our case (in DR, Netbackup Master Clone can 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 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Thank You!

Import phase 1 started Tue 29 May 2012 05:49:00 PM CEST INF - Create DB information for path @aaaab. weblink You may also refer to the English Version of this knowledge base article for up-to-date information. Sorry, we couldn't post your feedback right now, please try again later. Can you identify the image-id for the catalog backup?

You can however recover 'ALL' the files in /usr/openv/netbackup/db/staging to and bring up the NBDB from that, so you were on the right lines, but it's not a single file. 0 I do feel it ought to be documented, maybe thats just me expecting too much. as soon as we'll have another chance to do a DR test, i want to do as follow: i've find out (and i want to try it out when we will http://getbetabox.com/failed-to/failed-to-recover-from-nfs4err-stale-nfs4err-stale.html status: 83: media open error 06/28/2012 15:11:17 - Error bpbrm (pid=27107) client restore EXIT STATUS 83: media open error 06/28/2012 15:11:17 - restored from image srvnbms.client.it_1340794840; restore time: 0:00:07 06/28/2012 15:11:17

However, if you do not freeze the media that contains the backups more recent than the date of the catalog from which you recovered, NetBackup may overwrite that media. Add the media that are required for the recovery to the devices. I think cat_export > edit the 'header file' and cat_import should do it.

Understanding types of server form factors between...

I think the problem is when Marianne Moderator Partner Trusted Advisor Accredited Certified ‎08-04-2015 03:43 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a If NetBackup is configured as a highly available application (cluster or global cluster), freeze the cluster before starting the recovery process to prevent a failover. Veritas does not guarantee the accuracy regarding the completeness of the translation. No problems.

Start the bprecover wizard by entering the following command: bprecover -wizard The following is displayed: Welcome to the NetBackup Catalog Recovery Wizard! Email Address (Optional) Your feedback has been submitted successfully! Start the Sybase ASA server by running the following command: UNIX:(in a BASH shell) source /usr/openv/db/vxdbms_env.sh  /usr/openv/netbackup/bin/nbdbms_start_stop startWindows (NBU 6.X):  \NetBackup\bin\bpup -e ASANYs_VERITAS_NBWindows (NBU 7.X):   \NetBackup\bin\bpup -e SQLANYs_VERITAS_NB 6. his comment is here DNS Amplification Attack Before...

Now, we ran the command ‘nbcatsync -sync_dr_file ’ to synchronize the disaster recovery file to the new disk pool: All media resources were located Primary Disk Media No Yes How can we make this article more helpful? what i did was, I imported CA0080 into my other Master(cmsxxxx),duplicated the catalog images to disk andmounted the disk path to auspxxxxserver. Using catalog backup and recovery to transfer NetB...

This procedure can include the following tasks: Importing the backups from the backup media into the catalog Write protecting the media Ejecting the media and setting it aside Freezing the media If no catalog backup images exist in the catalog, a PARTIAL catalog recovery will only restore the NetBackup catalog files backed up in that incremental backup.