I just upgraded the Netbackup Agent for The SAP database to version 7.6.0.2 (Master and Media also the same version), the system run on HP-UX 11iv3 and clustered. Previously the backup running fine. I also tried the upgrade on the development system which was OK but the development is not a clustered system
After the upgrade I thought the backup was fine since NetBackup gave me no error exit (see the picture I attached) , but when I see the logs, it is strage:
11/03/2015 01:00:31 - Info nbjm (pid=7825) starting backup job (jobid=2065352) for client m1sap_db-bck, policy M1SAP01_DB_PRD_HOT, schedule Default-Application-Backup
11/03/2015 01:00:31 - Info nbjm (pid=7825) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2065352, request id:{39F82B48-8183-11E5-B915-6BCC2E7DA3D9})
11/03/2015 01:00:31 - requesting resource ESL02_EBS3_MPX
11/03/2015 01:00:31 - requesting resource ebsbck.NBU_CLIENT.MAXJOBS.m1sap_db-bck
11/03/2015 01:00:31 - requesting resource ebsbck.NBU_POLICY.MAXJOBS.M1SAP01_DB_PRD_HOT
11/03/2015 01:00:32 - granted resource ebsbck.NBU_CLIENT.MAXJOBS.m1sap_db-bck
11/03/2015 01:00:32 - granted resource ebsbck.NBU_POLICY.MAXJOBS.M1SAP01_DB_PRD_HOT
11/03/2015 01:00:32 - granted resource 400870
11/03/2015 01:00:32 - granted resource ESL02_Drive2
11/03/2015 01:00:32 - granted resource ESL02_EBS3_MPX
11/03/2015 01:01:12 - estimated 0 kbytes needed
11/03/2015 01:01:12 - Info nbjm (pid=7825) started backup (backupid=m1sap_db-bck_1446483672) job for client m1sap_db-bck, policy M1SAP01_DB_PRD_HOT, schedule Default-Application-Backup on storage unit ESL02_EBS3_MPX
11/03/2015 01:01:15 - Info bpbrm (pid=8842) m1sap_db-bck is the host to backup data from
11/03/2015 01:01:15 - Info bpbrm (pid=8842) telling media manager to start backup on client
11/03/2015 01:01:15 - Info bptm (pid=8845) using 262144 data buffer size
11/03/2015 01:01:16 - Info bptm (pid=8845) using 32 data buffers
11/03/2015 01:01:17 - Info bpbrm (pid=8842) spawning a brm child process
11/03/2015 01:01:17 - Info bpbrm (pid=8842) child pid: 19272
11/03/2015 01:01:17 - Info bpbrm (pid=8842) sending bpsched msg: CONNECTING TO CLIENT FOR m1sap_db-bck_1446483672
11/03/2015 01:01:17 - Info bpbrm (pid=8842) listening for client connection
11/03/2015 01:01:17 - connecting
11/03/2015 01:01:20 - Info bpbrm (pid=8842) INF - Client read timeout = 3600
11/03/2015 01:01:20 - Info bpbrm (pid=8842) accepted connection from client
11/03/2015 01:01:20 - connected; connect time: 0:00:00
11/03/2015 01:01:20 - begin writing
11/03/2015 01:01:20 - Info bpbrm (pid=8842) start bpbkar on client
11/03/2015 01:01:20 - Info bpbrm (pid=19272) from client m1sap_db-bck: TRV - Cannot lstat /export/sapmnt/PRD. Errno = 13: Permission denied
11/03/2015 01:01:20 - Info bpbrm (pid=19272) from client m1sap_db-bck: TRV - Cannot lstat /export/sapmnt/PRD. Errno = 13: Permission denied
11/03/2015 01:01:20 - Info dbclient (pid=18752) Backup started
11/03/2015 01:01:20 - Info dbclient (pid=18621) Backup started
11/03/2015 01:01:20 - Info bpbrm (pid=8842) Sending the file list to the client
11/03/2015 01:01:22 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata1: Permission denied
11/03/2015 01:46:26 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata3/sapdata10: Permission denied
11/03/2015 02:12:09 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata4/sapdata11: Permission denied
11/03/2015 02:21:47 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata5/sapdata12: Permission denied
11/03/2015 02:36:23 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata6/sapdata13: Permission denied
11/03/2015 02:47:54 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata2: Permission denied
11/03/2015 02:56:19 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata3: Permission denied
11/03/2015 03:03:51 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata4: Permission denied
11/03/2015 03:13:21 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata5: Permission denied
11/03/2015 03:30:44 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata6: Permission denied
11/03/2015 03:39:37 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata1/lvdata7: Permission denied
11/03/2015 04:09:39 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata1/lvdata8: Permission denied
11/03/2015 04:17:40 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata2/sapdata9: Permission denied
11/03/2015 04:33:29 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata3: Permission denied
11/03/2015 04:40:54 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata1/lvdata8: Permission denied
11/03/2015 04:48:23 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata5: Permission denied
11/03/2015 04:48:31 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata6: Permission denied
11/03/2015 04:51:00 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapdata/lvdata1: Permission denied
11/03/2015 05:00:23 - Error bpbrm (pid=19272) from client m1sap_db-bck: ERROR: V-3-20003: Cannot open /dev/vgsapora/lvoraprd: Permission denied
11/03/2015 05:00:23 - Info dbclient (pid=18621) done. status: 0
11/03/2015 05:00:24 - Info bpbrm (pid=8842) media manager for backup id m1sap_db-bck_1446483672 exited with status 0: the requested operation was successfully completed
11/03/2015 05:00:24 - end writing; write time: 3:59:04
the requested operation was successfully completed (0)
As you can see seemd it tried to backup the device instead of the mount point.
Is still a false alarm? Since the result of the backup is still ok, and I see the size of the backup more or less the same like yesterday (also on the picture I atached the 3/Nov/15 after the upgrade , 2/Nov/15 before the upgrade).