Are Parent_start_notify and Parent_end_notify still valid on Netbackup 7.7.1?

[AnthonyTsang]

Dear all experties,

Are Parent_start_notify and Parent_end_notify still valid on Netbackup 7.7.1?

I found 7.5.0.5 master server still work. After updated to 7.7.1, those script seems not to be executed.

I tried to add some steps to create log for verify the script whether to be executed. As last, nothing log generated.

I use this method to stop service before backup. Now the DFSR service cannot stop which cause backup failed with error code 90.

Anyone have solution?

[Nicolai]

The scrips are still supported 7.7.x , see page 145 in the document below

https://download.veritas.com/resources/content/live/SFDC/101000/000100624/en_US/NetBackup772_AdminGuideII_Server.pdf?__gda__=1456532261_b88172f308d97b6c2e6101fa76563e8a

[Marianne]

NBU Admin Guide was not updated for NBU 7.7.1, so 7.7 manual is still valid:

NetBackup Administrator's Guide, Volume II

The section about parent_start_notify script is still exactly the same - so, if this script is still on your master server in netbackup\bin folder and was not overwritten by the upgrade, then it will still be executed.

Not sure how you are stopping services on a client with a scrip that only runs on a master server?
Please explain?

Only bpstart_notify and bpend_notify runs on a client.

Any reason why you want to stop DSFR service before starting the backup?

This practice is not recommended.

See this Best Practice TN:

Backup and Restore of Microsoft DFSR data using Symantec NetBackup 
http://www.veritas.com/docs/000095710

[AnthonyTsang]

I set the backup selection using "streams" to split serveral backup streams at the same time in order to less the backup window.

But this method, I cannot use bpstart_notify and bpend_notify , it is because each stream will also trigger the bpstart_notify and bpend_notify.

That why I use below command to control stop DFSR before backup

parent_start_notify script

============================================================

@if "%6" == "" goto BadParams
@if "%2" == "DFC-WHBITD02" goto servicestop
@if "%7" == "" goto GoodParams
:BadParams
@echo %DATE% parent_start_notify expects 6 parameters: %* >> %OUTF%
@goto EndMain

:servicestop
@REM Start service on remote
@echo "Launch script_parent_start"
date /t         > c:\temp\testservicestop.log
time /t         >> c:\temp\testservicestop.log
sc \\whbitd02 stop dfsr >> c:\temp\testservicestop.log
@ping 127.0.0.1 -n 10 -w 1000 > nul
@echo "Service stop" >> c:\temp\testservicestop.log
date /t         >> c:\temp\testservicestop.log
time /t         >> c:\temp\testservicestop.log
@echo "End script_parent_start" >> c:\temp\testservicestop.log

===============================================================

parent_end_notify.cmd

================================================================

@if "%7" == "" goto BadParams
@if "%2" == "DFC-WHBITD02" goto servicestart
@if "%8" == "" goto GoodParams
:BadParams
@echo %DATE% parent_end_notify expects 7 parameters: %* >> %OUTF%
@goto EndMain

:servicestart
@REM Start service on remote
@echo "Launch script_parent_start"
date /t         >> c:\temp\testservicestop.log
time /t         >> c:\temp\testservicestop.log
sc \\whbitd02 start dfsr >> c:\temp\testservicestop.log
@echo "Service start" >> c:\temp\testservicestop.log
date /t         >> c:\temp\testservicestop.log
time /t         >> c:\temp\testservicestop.log
@echo "End script_parent_stop" >> c:\temp\testservicestop.log

====================================================================

[Marianne]

Why do you feel it is necessary to stop DFSR service? Why not split into multiple streams via Shadow Copy Components as per above TN?

[sdo]

I don't see any use of:

    2>&1

...on the end of any of the command lines, so it is possible that one of the commands is generating some error text on stderr, which is gobbled up (and not logged), and this will confuse the client execution process.

N.B:  The notify scripts must run utterly silently, with absolutely no output to stdout or stderr.

[Nicolai]

"Online" backup of DFS-R via ShadowCopyComponents run fine as long as you :

• Don't run local file system backup at the same time as DFS-R backup - doing so may result in status 50
• Don't use more than 1-2 stream to backup the DFS-R area.