Catalog DR Recovery file and email
Windows 2008r2 master and media servers, running Netbackup 7504.
I've spent the past couple days (as I've had time), reading articles, forum posts, etc, surrounding the fairly common issue of not receiving the DR file once a catalog backup completes. Sorry for beating a horse. I also dont receive alerts I have in place for long-running jobs, etc, but thats a secondary issue to the DR file. I have a Disaster Recovery rehearsal coming up, and need to get this working. I do receive the daily failure reports that I have configured....just not getting needed alerting or DR file. I know well the file path to where the catalog information gets saved, and I suppose I could cheat, and note the tape ID(s) of the last full successful catalog backup, but that's not kosher for DR.
Here's what I have already tried.
- Checked for installation of blat, and installation looks correct.
- I've located the nbmail.cmd file, and renamed it to mail_dr_info.cmd, checked that @REM did not exist in front of lines where it does not need to be, and confirmed that the SMTPrelay is set up.
- I created c:\testfile.txt, and was able to send that to my email address successfully.
- I confirmed that the correct email address was in the Catalog backup policy.
I ran a catalog backup, and it completed with status 0, but I received no email, and checked junk email as well.
Can I provide some additional info here? If so, please let me know.
P.S. A word of note - My catalog backup spawns 4 jobs.
- Parent job
- A "CATALOG_DRIVEN_BACKUP" job that always finishes with a status 1 due to BMRDB and NBAZDB staging error.
- A job backing up the DARS_DATA.db which generally completes with with status 0
- Another "CATALOG_DRIVEN_BACKUP" job generally finishes with status 0 (largest part of the backup, 750+gb).
Could it be that status 1 job with the BMRDB and NBAZDB issues causing it not to send the DR file email, since it also causes the Parent job to fail with status 1? If so, do I really even need those two for a catalog recovery?