I am running netbackup 6.5 in linux From yesterday onwards backups are not starting as per schedules. All services are running and no jobs in queue, however not jobs are generated as per schedule. There is a potential issue, i am unable to find out what is the issue is.... Please let me know why the scheduels are not been started. i have 3 sites affected with same issue. Kinldy advice.

You need to explain what you mean by can't start backups. I think you mean that nothing appears in Activity Monitor, but you need to confirm this. If it is as I think .... Is nbpem running ? Try nbpemreq -subsysyems 1 screen Do you get any output (should be 'many pages' worth) If things are 'urgent' - have you tried stopping and starting NBU services ?

Schedule backups are not starting

shinoj_online
Level 2
12 years ago
i have tried to start a manual backup however the backups are not starting.

i have initiated couple of manual backups and those backups are not visible in activity monitor.

Kinldy help
BTLOMS
Level 5
12 years ago
Can your media servers communicate with the Robot/Tape library? Can your Master communicate with the Media servers?

Try creating a disk based storage and try a backup to that. Maybe a local drive on the media server as a test.
mph999
Level 6
12 years ago
You need to explain what you mean by can't start backups.

I think you mean that nothing appears in Activity Monitor, but you need to confirm this.

If it is as I think ....

Is nbpem running ?

Try nbpemreq -subsysyems 1 screen

Do you get any output (should be 'many pages' worth)

If things are 'urgent' - have you tried stopping and starting NBU services ?
mph999
Level 6
12 years ago
Is it possible someone has run nbpemreq -suspend_scheduling You can tell from the output of nbpemreq -subsystems 23 screen To be honest, just easier to run: nbpemreq -resume_scheduling - it won't do any harm
Marianne
Level 6
12 years ago
I agree with Martin - try to restart NBU.

Before you do that, check disk usage on the master. If disk is full where EMM resides, NBU will terminate EMM to prevent database corruption.

PS:
PLEASE upgrade your environment ASAP as NBU 6.5 ran out of support over a year ago.
jim_dalton
Level 6
12 years ago
Has anything else changed? From reading it , it used to work just fine then one day it stopped.

So has anything else been changed?

Policies are active? Server is good, disk space aplenty, nothing hogging cpu/disk?

Theres plenty to check, so a restart of nb - controlled - could be good, but also consider the server as a whole.

Jim
Stumpr2
Level 6
12 years ago
So if you are starting jobs but they never show up in the queue then you probably have a library/storage unit problem. BASICS. start with the basics and prove all the hardware as good at the Operating System (OS) level by using robtest to move/load tapes. the mount command and tar to see if you can get a tape loaded and read/write to it. If robtest dont work then dont be afraid to physicall using your hands to put a tape in the tape drive. Prove you can read/write to a tape and then start checking the library robotics.
sri_vani
Level 6
12 years ago
Looks like vnetd problem:

Please verify this link:

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

verify this command /usr/openv/netbackup/bin/bpcompatd -alive
u may see an error "authentication failed"

Compare the files within /usr/openv/var/vnetd folder with a known good installation of Netbackup on another linux Master server. Many of the files were either corrupt or missing.

If it is a vnetd issue please try below solution:

Copy and replace the entire contents of /vnetd folder from any other working Master server and then restart the NBU services.
RadovanTuran
Level 4
12 years ago
Hi.

1. I'm surprised by the answers about the issues with the library and s.o. During initial phase NBU doesn't know what robot will be used finally. Job is started, put to the queue and then master is going to seek for resources based on policy/STU and s.o. In case of any issue with robot there has to be either failed job or job in waiting state.

2. With the command "nbpemreq -predict_all -date <mm/dd/yyy hh:mm:ss> -policy_filter <policy>" you can see what is scheduled for this policy. If there are no jobs, you can have old stuck jobs that are not in jobdb anymore but NBU stil think that they didn't finish and cannot start new job. Check whether in output of "nbpemreq -jobs screen all" are not some old jobs. Then contact Symantec - they will navigate you to stop NBU, delete some explicit files and folders and start NBU.
Anyway. It will not be - probably - your issue as with these symptomps you can stil run backup manually.

3. Check if there are no trunning a lot of bprd processes on master. (I hope it's bprd, don't remember exactly). Just run "bpps" and if there is few hundreds of jobs of the same daemon BUT without any command line argumens (like details about particular backup job) it can be an issue. Restart of NBU on master helps.

4. Or really you have corrupted NBU installation as described in previous answer.
Stumpr2
Level 6
12 years ago
I'm surprised by the answers about the issues with the library and s.o....

yeah, come to think of it that was a 5.x issue with bpsched not stating jobs when a storage unit was not available because all the drives were in a DOWN state.