Checking client conn status 1

[NavinB]

Hi,

Is there any command which can be run from the server(master or media) to see if the client's netbackup service is working or not(i.e connection status info) so that backups do not fail due to conn prob or becoz service is not started on the client.

Thanks,
Navin

 

[creakyjoe]

i guess you could achieve this with scripting, and i guess pre/post notify scripts, BUT wouldn't it be easier to just have email notification for all backups, good or bad. What i've been doing for last 5yrs is have every backup mail completed or failed status's. Then in our mail client (MS Outlook) we just have a simple rule that chucks the completed mails in the bin, and only passes thru failed backups. I can see your train of thought but at the very least, a backup failing could actually give you what you need anyway. We use Blackberry's and as long as NetBackup is managed well (he says confidently, lol) the annoyance is minimal. That's just my personal way of doing things as it's simple (we have no tape operators, night shifters or anything so i have to wear multiple hats as support, user, etc)

Rich

 

[NavinB]

Thanx for the info u have provided....but the soln is post-failure...What I need is pre-failure cmd or script(just to check conn link or netbkp service is running) so that I am sure that imp servers backup will be done without any comm problem.....

 

[creakyjoe]

to me, reporting on a 'potential' comms problem would still require resolution of sorts. ie you could have a pre-bkup script checking comms, but surely that would still need some resolution. So in this case the backup wouldn't fail and you'd be alerted to a problem, but you still gota fix the comms problem then still get backup to run.


Outside of scheduled backups, all of my reporting scripts (ie nightly backup stats, tapes used etc) do a loop to check NetBackup itself is running, before producing potentially incorrect reports or zero reports. But it's not quite foolproof yet and a bit basic.

Rich

 

[NavinB]

U r right that " reporting on a 'potential' comms problem would still require resolution of sorts"
But atleast I would be aware before the prob occurs...
See I had this weekly bkp running every friday night...On Sat I had to make some changes but since bkp was not done...I had to postpone things.....
So any cmd or script for checking ???

 

[creakyjoe]

well i work in the Unix world so anything except the kitchen sink can be magic'd up by a script or two. (However if i recall correctly) you'in the the Windows world so scripting isn't as easy!

Rich

 

[NavinB]

U r right again....I am talking abt windows server and clients...However if u do have script for unix pls tell me....becoz anyway the master server is soon to be moved to unix box....

 

[Vela]

Usually when we add new client's to our configuration I create a policy and make sure it's deactivated so it doesn't kick off any backups-

Once we think the config is good I'll add it in to the policy then switch to the Host Properties>Clients tab and refresh. The new client will now be at the bottom of the list and you can click on it to see if it connects. 9 times out of 10 if it connect's here you can back it up.

This doesn't gaurantee that OTM or VSP is working properly or some other random error may occur during backup though-

Also to test connectivity between the client and master you can use blclntcmd. You can try blcntcmd ? to see the switches you can use-

Hope this helps

Ryan

 

[NavinB]

Thanks Ryan.....This was the cmd I was looking for....
One more thing..in the Clients tab I found out that there were two entries for the same client..one in small case and other in caps....Both were under two different policies...Does that make any diff to the master server....(the host properties were same but in the status of backups both showed diff results)

 

[creakyjoe]

Hi Navin, in response to you original recent thread on this subject "Status 41: network connection timed out" -

http://www.tek-tips.com/viewthread.cfm?qid=1027355,

where i and others were trying to help you about; i pointed towards the troubleshooting manual as status 41 can be a pain in the backside. You said you had tried everything in the manual relevant to status 41 to no avail.

However in this thread you were pointed towards 'blclntcmd' which you say is what you were after. That command is part and parcel of status 41 troubleshooting, well it is in my old 3.4 manuals anyway. I Didn't point you straight at 'bpclntcmd' as had assumed you had tried that as part of the previous thread;
I would recommend you consider the official training - it's very good; i self-taught myself netbackup before attending the Enterprise course, it was still a good course as it proved i had picked everything up correctly; it would help you understand how it all works/hangs together

Rich

 

[NavinB]

Hi Rich...
I agree that I had written that I tried everything acc to ts guide (which was the latest one)..so I couldn't find the 'bpclntcmd' cmd....and came to know today only from old manuals(3.4....)....
I'm still in the learning phase(self-taught method)...and this forum is too helpful at this stage.....

 

[creakyjoe]

learning phase" lol, bless him!.
- don't knock self-teaching, i've been doing the same for 5yrs now. straight in the deep end from many years computer operations into Unix self-teaching. Talk about steep learning curve. Having no-one to learn from/be mentored by worked well as i just had to get thru all the server disasters, projects and meetings. At least for the last couple years there's 2more admins to help out.
Trouble is when does the damn learning ever stop!

(i still work from 3.4 manuals and a goldfish memory btw).

Have a good weekend

 

[Vela]

Sorry, I meant to write bpclntcmd, lol


The master won't care if you have duplicate client's in the several different policies.

Also and easy way to clena up clients that may be in duplicate polices is to go to the policies tab, then select the Summary of all polices tab, then selct clients, then you can sort by client and it will give you a quick view of client's you may be backing up more than once which could waste tapes and drive time/usage


Ryan