UNSOLVED
Probe problems
Hello,
I'm having trouble finding any helpful documentation on probe jobs. I have created a bat script to probe, let's call it nsrprobe.bat. It echo's a 0 or a 1 depending on our backup requirements. 0 for backup required. 1 for backup not required.
If the file doesn't exist, instead of reporting an error of it missing, the log shows "Savegroup info: Test_Probe is probing", then "Savegroup info: Test_Probe finished probing, backup is not needed"
If I make it exist, the log shows "Savegroup info: Test_Probe is probing" then "Savegroup info: Test_Probe waiting for 1 job(s) to complete.
The strange thing is, as part of my batch script I output the results to a text file. Whenever Networker "runs the probe" the text file never gets created, which makes me believe Networker isn't running the script at all.
The only probe example I can find online is a .sh script which doesn't help me at all as we run a Windows environment. I've tried running a vbs script instead of a bat but the log file shows me Savegroup failure alert: Test_Probe: error occurred during probing; check that probes exist and can be executed. The error you'd expect when the bat file doesn't exist...
Can someone point me in the right way?
vishwanathkrish
75 Posts
886
0
Posted May 11th, 2012 00:00
Hello,
You can refer the document "EMC NetWorker Probe Overview and Troubleshooting" for i the information related to Probe . this is available in the following path in EMC power link home page
Home >support >Technical Documentation and Advisories > Software ~ J-O ~ Documentation > NetWorker Family > Technical Notes
Regards,
Vish
Hi Craig,
I've tested this here to try to identify where there could be a problem. The results though were as I would expect them:
I created a small bat script called nsrtestprobe.bat and placed it in the .../nsr/bin directory on the client. I associated
it with a client in NMC and put in in a test group called ProbeTest.
If the exit status is 1 (file does not exist)
savegrp -vvvvv ProbeTest
32451:savegrp: vm-lego-28-84:C:\test level=incr
66816:savegrp: Custom backup probe for client vm-lego-28-84 started
nsrtestprobe.bat -s vm-lego-151 -g ProbeTest -c vm-lego-28-84 "C:\\test"
67050:savegrp: Custom backup probe for client vm-lego-28-84 finished with result: backup is not needed
67214:savegrp: ProbeTest finished probing, backup is not needed
80249:savegrp: Failed to process job completion attributes message: No save instance found with job id 448051
If the exit status is 0 (file exists)
savegrp -vvvvv ProbeTest
32451:savegrp: vm-lego-28-84:C:\test level=incr
66816:savegrp: Custom backup probe for client vm-lego-28-84 started
nsrtestprobe.bat -s vm-lego-151 -g ProbeTest -c vm-lego-28-84 "C:\\test"
67050:savegrp: Custom backup probe for client vm-lego-28-84 finished with result: backup is needed
67216:savegrp: ProbeTest finished probing, backup is needed
...
7341:savegrp: vm-lego-28-84:C:\test succeeded.
The test script I used is this (this is just a quick test for a lab envioronment and I take no responsibility for it):
@echo off
IF EXIST "C:\test" (
exit /b 0
) ELSE (
exit /b 1
)
Is this not what you are getting?
-Bobby
Thanks for the reply Bobby. It ended up being an issue with a command line EULA requiring acceptance but we couldn't detect this as Networker runs the script as the SYSTEM user.
Do you work with DPA too? I have an outstanding question in the DPA forum that I could do with your expertise:
coganb
736 Posts
886
1
Posted May 11th, 2012 00:00
Hi Craig,
Unfortunately, I don't think the document suggested by Vishwanath is going to help with this. That document is about the probing process during a backup operation and not about probe-based backups.
I'm not sure I have followed exactly the behaviour you are seeing with this. When you refer to the file not existing, are you talking about the nsrprobe.bat file itself not existing? You should try running the savgrp with -vvvv and -D9 and outputtting to a file and see if you can find a trace of the probe being found and run. This should help you assess whether NetWorker is not interpreting the results of the script correctly or if it's not running the script at all.
-Bobby