cancel
Showing results for 
Search instead for 
Did you mean: 

Policy is not present, still backup is goig on

prakash_sharma
Level 4
Certified

Hi All,

We don't know some one deleted policy since not showing in policy manager

which did run yesterday & backup is successful on 10/15/2013 08:47:42

but not run today on user request i started investigating

verbosity of the master is at lower end so don't know how to investigate

but tried below thing

- NBAC is not implemented so wont able to confirm which user or super user deleted

- admin log are not kept for yesterday so can not conclude whether bppldelete is done

- bperror -all -U showing backup restarted & even it is in progress

- below are the logs of last successful backup which run by nbpem i.e backup type showing schedule & backup which is restarted from activity monitor

(though the policy does not exists. unable to seen in java console plus confirm by command line bpplcliet for that particulate client )

 

Here is the question why this is abnormal behavior of the netbackup though the policy does not exist backup is getting

successful on restart of last backup

Master server NBU 7.5.0.4

Client 6.5.0.4 windows

------------------------------------------------------

JOb On 15th Oct 2013 

10/15/2013 02:00:00 - Info nbjm (pid=20141) starting backup job (jobid=252598) for client ntwprddb, policy DAKC_D_ntwprddb, schedule DAKC_D_ntwprddb
10/15/2013 02:00:00 - Info nbjm (pid=20141) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=252598, request id:{65F66F7E-350F-11E3-8090-002128FA0260})
10/15/2013 02:00:00 - requesting resource netback8-hcart2-robot-tld-3_mpx
10/15/2013 02:00:00 - requesting resource dakcmstnetbkp.NBU_CLIENT.MAXJOBS.ntwprddb
10/15/2013 02:00:00 - requesting resource dakcmstnetbkp.NBU_POLICY.MAXJOBS.DAKC_D_ntwprddb
10/15/2013 02:00:09 - granted resource  dakcmstnetbkp.NBU_CLIENT.MAXJOBS.ntwprddb
10/15/2013 02:00:09 - granted resource  dakcmstnetbkp.NBU_POLICY.MAXJOBS.DAKC_D_ntwprddb
10/15/2013 02:00:09 - granted resource  DD0477
10/15/2013 02:00:09 - granted resource  Drive041
10/15/2013 02:00:09 - granted resource  netback8-hcart2-robot-tld-3_mpx
10/15/2013 02:00:10 - estimated 321884035 kbytes needed
10/15/2013 02:00:10 - Info nbjm (pid=20141) started backup (backupid=ntwprddb_1381782609) job for client ntwprddb, policy DAKC_D_ntwprddb, schedule DAKC_D_ntwprddb on storage unit netback8-hcart2-robot-tld-3_mpx
10/15/2013 02:00:11 - Info bpbrm (pid=4578) ntwprddb is the host to backup data from
10/15/2013 02:00:11 - Info bpbrm (pid=4578) telling media manager to start backup on client
10/15/2013 02:00:11 - Info bptm (pid=4608) using 262144 data buffer size
10/15/2013 02:00:11 - Info bptm (pid=4608) using 64 data buffers
10/15/2013 02:00:11 - Info bpbrm (pid=4578) spawning a brm child process
10/15/2013 02:00:11 - Info bpbrm (pid=4578) child pid: 12329
10/15/2013 02:00:12 - Info bpbrm (pid=4578) sending bpsched msg: CONNECTING TO CLIENT FOR ntwprddb_1381782609
10/15/2013 02:00:12 - connecting
10/15/2013 02:00:13 - Info bptm (pid=12327) setting receive network buffer to 262144 bytes
10/15/2013 02:00:13 - Info bpbrm (pid=4578) start bpbkar on client
10/15/2013 02:00:13 - connected; connect time: 0:00:00
10/15/2013 02:00:13 - begin writing
10/15/2013 02:00:14 - Error bpbrm (pid=12329) from client ntwprddb: ERR - cannot create cpr_info file
10/15/2013 02:00:14 - Info bpbkar (pid=0) Backup started
10/15/2013 02:00:14 - Info bpbrm (pid=4578) Sending the file list to the client
10/15/2013 08:47:41 - Info bpbrm (pid=4578) media manager for backup id ntwprddb_1381782609 exited with status 0: the requested operation was successfully completed
10/15/2013 08:47:42 - end writing; write time: 6:47:29
10/16/2013 06:27:06 - job 252598 was restarted as job 253646
the requested operation was successfully completed  (0)


Job on 16th Oct after restarted

10/16/2013 06:27:06 - Info nbjm (pid=20141) starting backup job (jobid=253646) for client ntwprddb, policy DAKC_D_ntwprddb, schedule DAKC_D_ntwprddb
10/16/2013 06:27:06 - Info nbjm (pid=20141) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=253646, request id:{E09082BC-35FD-11E3-AAE4-002128FA0260})
10/16/2013 06:27:06 - requesting resource netback8-hcart2-robot-tld-3_mpx
10/16/2013 06:27:06 - requesting resource dakcmstnetbkp.NBU_CLIENT.MAXJOBS.ntwprddb
10/16/2013 06:27:06 - requesting resource dakcmstnetbkp.NBU_POLICY.MAXJOBS.DAKC_D_ntwprddb
10/16/2013 06:27:08 - granted resource  dakcmstnetbkp.NBU_CLIENT.MAXJOBS.ntwprddb
10/16/2013 06:27:08 - granted resource  dakcmstnetbkp.NBU_POLICY.MAXJOBS.DAKC_D_ntwprddb
10/16/2013 06:27:08 - granted resource  DW0034
10/16/2013 06:27:08 - granted resource  Drive040
10/16/2013 06:27:08 - granted resource  netback8-hcart2-robot-tld-3_mpx
10/16/2013 06:27:08 - estimated 321884035 kbytes needed
10/16/2013 06:27:08 - Info nbjm (pid=20141) started backup (backupid=ntwprddb_1381885028) job for client ntwprddb, policy DAKC_D_ntwprddb, schedule DAKC_D_ntwprddb on storage unit netback8-hcart2-robot-tld-3_mpx
10/16/2013 06:27:09 - Info bpbrm (pid=9113) ntwprddb is the host to backup data from
10/16/2013 06:27:11 - Info bpbrm (pid=9113) telling media manager to start backup on client
10/16/2013 06:27:11 - Info bptm (pid=9121) using 262144 data buffer size
10/16/2013 06:27:11 - Info bptm (pid=9121) using 64 data buffers
10/16/2013 06:27:12 - Info bpbrm (pid=9113) spawning a brm child process
10/16/2013 06:27:12 - Info bpbrm (pid=9113) child pid: 17420
10/16/2013 06:27:13 - Info bpbrm (pid=9113) sending bpsched msg: CONNECTING TO CLIENT FOR ntwprddb_1381885028
10/16/2013 06:27:13 - connecting
10/16/2013 06:27:13 - Info bpbrm (pid=9113) start bpbkar on client
10/16/2013 06:27:13 - Info bptm (pid=17419) setting receive network buffer to 262144 bytes
10/16/2013 06:27:13 - connected; connect time: 0:00:00
10/16/2013 06:27:13 - begin writing
10/16/2013 06:27:14 - Info bpbkar (pid=0) Backup started
10/16/2013 06:27:14 - Info bpbrm (pid=9113) Sending the file list to the client

 

 

Thanks

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

watsons
Level 6

There is another way to check if policy was deleted - run nbauditreport (http://www.symantec.com/docs/HOWTO91455). The audit feature is usually enabled by default unless you have disabled it before.

Cases like this, I will normally run "bppllist -L -allpolicies" to confirm it's not a GUI (not showing up) issue. If policy is indeed gone, then I will run a "nbpemreq -updatepolicies" to ensure it won't be pick up again by scheduler. But if it is still running (like a ghost), then I will call support smiley

View solution in original post

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

All policy parameters are loaded into the jobs database when a backup starts. So, when you restart a backup, it simply uses the same parameters in the jobs database to rerun the backup.

I have in the past made changes to a policy after a backup has failed (changed STU) and restarted the failed backup. The backup was started using same (faulty) STU.
This is when I realized that the policy is not read when a backup is restarted.

watsons
Level 6

There is another way to check if policy was deleted - run nbauditreport (http://www.symantec.com/docs/HOWTO91455). The audit feature is usually enabled by default unless you have disabled it before.

Cases like this, I will normally run "bppllist -L -allpolicies" to confirm it's not a GUI (not showing up) issue. If policy is indeed gone, then I will run a "nbpemreq -updatepolicies" to ensure it won't be pick up again by scheduler. But if it is still running (like a ghost), then I will call support smiley

kumara
Level 3

Hi Prakash,

As Maria said, restarting a job will stick with the old policy parameters of that particular job. And you can use the below link in future to find what has been modified in the policy and which policy is deleted by following steps in this link.

http://www.symantec.com/business/support/index?page=content&id=TECH63422

Hope it would be helpful....

 

Regards,

Kumara