Status 42 on VMware backups (somewhat inconsistent)
Solaris Master - 7.6.0.3
3 x 5220 appliance media servers - 2.6.0.3
Appliances are the VMware Backup Hosts
All VMware backups are done via SAN transport mode
Job details from a "represent...
I deleted all the old files and then retried the backup that was recently failing. And it worked. I'm going to be cautiously optimistic that perhaps my "Status 42" issues will be less prevalent with this discovery.
Anyone know why these files get left behind? The backup I retried left behind the following files:
densyma02p:/usr/openv/netbackup/online_util/fi_cntl # ll total 21744 -rw-r--r-- 1 root root 2473 Nov 20 14:58 bpfis.fim.<host>_1416520694.1.0 -rw-r--r-- 1 root root 2058 Nov 20 14:58 bpfis.fim.<host>_1416520694.1.0.NBU_DATA.xml -rw-r--r-- 1 root root 21 Nov 20 15:05 bpfis.fim.<host>_1416520694.1.0.NBU_DATA.xml.BID -rw-r--r-- 1 root root 22406 Nov 20 14:58 bpfis.fim.<host>_1416520694.1.0.VM_ObjInfoXML.xml -rw-r--r-- 1 root root 734 Nov 20 14:58 bpfis.fim.<host>_1416520694.1.0.changeid.xml -rw-rw-rw- 1 root root 284 Nov 20 15:10 <host>_1416520694_copy1.lock
I'm inclined to stick a cron job on the appliance to clean up this directory daily, but would like to avoid such a modification if I can manage to. I really dislike doing these types of "one off" fixes on the appliances.
