Problems with Recovery without Import procedure
I am trying to use the "Recovery without Import" whitepaper to create a DR-only NBU configuration at our DR facility, and cannot get it to recognize the catalog that I've copied over (when I try to browse a client+file for recovery, it gives me the generic error that there are no files matching that timeframe and to to check my recovery time, client selection, etc).
Here's my setup:
Primary site:
Netbackup Enterprise 6.0MP4 on RHEL 4
(2) NBU media 6.0MP4 media servers on RHEL
FalconStor VTL and SIR (dedup) system for virtualized tape. VTL tapes are replicated to Recovery site VTL unit.
Recovery site:
same NBU systems as above, with SAME hostnames as above
Matching FalconStor VTL and SIR systems to "receive" the replicated virtual tape images.
Following the Recovery without Import document, I did the following:
* Configured special pool "DRreadonly" pool at Recovery site, for recovery-only tapes
* Configured the Recovery site storage unit for the VTL.
* No change for barcode rules, we use the default
* shutdown NBU at Recovery site
* Copied the client image directory /usr/openv/netbackup/db/images/<clientname> from the primary to the recovery site.
* Started NBU at Recovery site
* Inventoried the VTL robot, with the "Update volume configuration". Tapes were put into the DRreadonly pool.
NBU inventoried the VTL just fine (found the 2 test tapes I was expecting), and added them to the EMM database (vmquery -m <mediaid> works fine).
When I tried to search for a file to recover (on one of the clients with the copied catalog) and failed.
Looking at the logs on the master, bplist fails with "EXIT STATUS 227: no entity was found".
I've tried:
* Reducing my Recovery site to a single master/media server combo (with appropriate FORCE_RESTORE_MEDIA_SERVER entries)
* copying the policy that created the backup that I'm trying to recover (when I did this and restarted NBU, it immediately showed up in the Policies section of the admin GUI.)
One part of the Recovery without Import document that I may be mis-interpreting is "Merge the copied images into the catalog". Is this nothing more than copying /usr/openv/netbackup/db/images/* to the target system? Or is there more to it?
I'm a bit new to NBU, and am ALSO in the middle of converting our backups from Networker (ick) to NBU, so it's been a somewhat wild ride so far.
Any help would be appreciated. Thanks!
- After talking to a Symantec engineer (Thanks Alex), the problem was with the db/images directory format.(Very) old Netbackup used a directory format where files were saved in db/images/<clientname> directly. Newer versions (3.x I think) started nesting the image files under an additional directory level, based on time.(see http://seer.entsupport.symantec.com/docs/231879.htm, though the knowledge base wouldn't give me a hit with NBU 6.x, I found it on google).The fix:Change the contents of /usr/openv/netbackup/db/images/IDIRSTRUCT from "1" (old format) to "2" (new format). For some reason my DR-site install had a "1". Maybe since I didn't to an initial backup of the DR site, this never got setup correctly. In either case, it works now.
