UNSOLVED

PatricJ

updated

8 years ago

P

PatricJ

1 Rookie

•

68 Posts

0

2678

July 20th, 2017 06:00

Networker 9.1 Pre/post Scripts Issue (with Enterprise Vault)

Hello,

i am trying to backup Enterprise Vault 11 and I am able to successfully set the backup mode using a powershell command. I even managed that a simple pre scirpt is executed by networker and the backup mode is set.

But the "default" save command is not run after the script has been started. I do not know how to send an exit 0 and networker uses this information to move on.

My pre-script looks like that:

nsr_pre_BACKUP_mode_EV.bat

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

@ECHO OFF

SETLOCAL

ECHO === SET BACKUP MODE ===

C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell -psconsolefile "C:\Program Files (x86)\Enterprise Vault\EVShell.psc1" -command "& {Set-VaultStoreBackupMode -Name hasenkamp -EVServerName evserver01 -EVObjectType Site}"

ECHO Errorlevel: %errorlevel%

EXIT /B 0

ENDLOCAL

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

I started the script with only the powershell command but that did not work either and now I am trying to figure out why the save command is not running

Anyone using pre/post scripts with Networker 9?

Regards

Patric

  • PatricJ

    1 Rookie

    •

    68 Posts

    1806

    0

    Posted July 20th, 2017 06:00

    When I start the workflow i see the following lines in the actions log:

    20.07.2017 15:33:03 EnterpriseVault_Tag system.name.local:All See the file D:\EMC NetWorker\nsr\logs\policy\EnterpriseVault\Tag\backup_EV_Tag_032437_logs\32438.log for command output

    20.07.2017 15:33:03 Probe result returned DISASTER_RECOVERY save set for client system.name.local.

    20.07.2017 15:33:03 hasenkamp40.hasenkamp.int:precmd                           started

    20.07.2017 15:33:03 nsr_pre_BACKUP_mode_EV.bat

  • PatricJ

    1 Rookie

    •

    68 Posts

    1806

    0

    Posted June 14th, 2018 01:00

    In the meantime I was teached that in case of pre/post scripts the permission of the system are really to take a deeper look into. In my case - starting networker nsrexecd service with a user that has the required permissions solved the problem.

    This also works sometimes with appliaction (module backups).

    Regards,

    Patric