05-28-2015 09:49 AM
NBU 7.6.0.4 running on Linux. Different hostnames, only need the image data for possible restore in the future, not full catalog recovery.
bprecover –wizard fails with error 254 and Status 2818. Found this older thread looks to be the same issue
https://www-secure.symantec.com/connect/forums/catalog-restore-alternate-master-server
DR file is it not mentioned in Recovery without Import, much less the need to modify it. Seems like some steps are missing from the White Paper?
Solved! Go to Solution.
05-28-2015 10:14 AM
Hi Will,
So you're talking about the pdf linked to the following techdoc I assume: http://www.symantec.com/docs/TECH28722
Are you sure you're using the version attached to the above (as following the instructions in earlier versions of the document will not allow recovery to work).
7.5 changes to the recovery without import are:
One of the significant changes made in NetBackup 7.5 was to move the image metadata (the header files from the image database) into the relational database. This change was made both to improve performance and scalability and to allow for the introduction of new fields within the headers to support new features planned for future releases. This change has made it necessary to change the way in which partial catalog recovery works and exactly what gets recovered. This, in turn, may mean that existing disaster recovery procedures based on partial catalog recovery will need to be modified after upgrading to NetBackup 7.5. Prior to NetBackup 7.5 the partial catalog recovery option simply restores the complete flat file component of the catalog along with the license database and, in the case of UNIX and Linux environments, the bp.conf file. The relational database components are not restored. Starting with NetBackup 7.5 the default behavior of the partial catalog recovery option does two things: 1. Restores the image database component of the flat file database (/usr/openv/netbackup/db/images or the Windows equivalent) to its original location. 2. Restores the relational database to the designated relational database staging area. In order to complete the partial catalog recovery the image metadata must be exported from the copy of the relational database in the staging area and imported into the live relational database. This is achieved by running the following commands: 1. cat_export –all –staging –source_master 2. cat_import –all –replace_destination
05-28-2015 10:14 AM
Hi Will,
So you're talking about the pdf linked to the following techdoc I assume: http://www.symantec.com/docs/TECH28722
Are you sure you're using the version attached to the above (as following the instructions in earlier versions of the document will not allow recovery to work).
7.5 changes to the recovery without import are:
One of the significant changes made in NetBackup 7.5 was to move the image metadata (the header files from the image database) into the relational database. This change was made both to improve performance and scalability and to allow for the introduction of new fields within the headers to support new features planned for future releases. This change has made it necessary to change the way in which partial catalog recovery works and exactly what gets recovered. This, in turn, may mean that existing disaster recovery procedures based on partial catalog recovery will need to be modified after upgrading to NetBackup 7.5. Prior to NetBackup 7.5 the partial catalog recovery option simply restores the complete flat file component of the catalog along with the license database and, in the case of UNIX and Linux environments, the bp.conf file. The relational database components are not restored. Starting with NetBackup 7.5 the default behavior of the partial catalog recovery option does two things: 1. Restores the image database component of the flat file database (/usr/openv/netbackup/db/images or the Windows equivalent) to its original location. 2. Restores the relational database to the designated relational database staging area. In order to complete the partial catalog recovery the image metadata must be exported from the copy of the relational database in the staging area and imported into the live relational database. This is achieved by running the following commands: 1. cat_export –all –staging –source_master 2. cat_import –all –replace_destination
05-28-2015 10:19 AM
06-16-2015 06:47 AM
OK, got me there, but the important part (having to edit the file) is not mentioned anywhere. Haven't heard back from the site so not sure how it went yet.