BUG REPORT: NDMP incremental backup running as a full backup
We have the same error reported in the article https://www.veritas.com/support/en_US/article.000011201, is there any solution already known to fix the problem?
Information about my backup:
- NetBackup version 7.6.1
- Full backup performed on Saturday finished in status 0
- Incremental backup made on Monday finished in status 0 (previous backup to the problem).
- Incremental backup performed on Tuesday is the problem. This backup copying this all again the same data expected to complete.
We need to know which backup job (bpbrm PID) we're looking at in bpbrm.
There seem to be different NDMP backups that ran on this day. Some level 0, some level 2 and also level 7.
e.g.
08:53:29.039 [6860.9932] <2> logparams: -backup -S cansbkp03 -c cansfile01.sa.agcocorp.com -ct 19 -ru root -cl CAN_NAS_MAN -sched Semanal_NAS -bt 1477392807 -dt 0 -st 0 -b cansfile01.sa.agcocorp.com_1477392807 -mediasvr cansbkp05 -jobid 930985 -jobgrpid 930984 -masterversion 760000 -maxfrag 1048576 -bpstart_time 1477393108 -reqid -1477392692 -mt 3 -to 0 -stunit cansbkp05-hcart2-robot-tld-5-cansfile01.sa.agcocorp.com -rl 3 -rp 2678400 -eari 0 -cj 1 -D 14 -rt 8 -rn 5 -pool Semanal_NAS -use_ofb -use_otm -jm -secure 1 -kl 1 -rg other -fso -stream_count 1 -stream_number 1 -dmplevel 0 -connect_options 16974338Herewith couple of TNs that may help:
NDMP backups - What triggers an Incremental versus a Full backup ?
http://www.veritas.com/docs/000009728NDMP backup levels
http://www.veritas.com/docs/000076815PS:
Please upload files in .txt format rather than .log (e.g. bpbrm.txt).
.txt files can be viewed online, even on a mobile device.
Not the case with .log....
THANKS!Have you had a chance yet to look at the TNs that I've posted yesterday?
You will see that /etc/dumpdates on the filer determines which dumplevel to use.
If the Full was still running, it means that /etc/dumpdates on the filer was not yet updated with details of successful Full backup.
