Indexing Backupmode start and stop script
I have the following script in place on the indexing servers:
Set Backup Mode
date /t
time /t
%SystemRoot%\SysWow64\WindowsPowerShell\v1.0\powershell -psconsolefile "D:\Program Files (x86)\Enterprise Vault\EVShell.psc1" -command "& {Set-IndexLocationBackupMode server1}"
date /t
time /t
Clear Backup Mode
date /t
time /t
%SystemRoot%\SysWow64\WindowsPowerShell\v1.0\powershell -psconsolefile "D:\Program Files (x86)\Enterprise Vault\EVShell.psc1" -command "& {clear-IndexLocationBackupMode server1}"
date /t
time /t
The set Indexing script and clear scripts both fail with the following error:
D:\Program Files (x86)\Enterprise Vault>C:\Windows\SysWow64\WindowsPowerShell\v1.0\powershell -psconsolefile "D:\Program Files (x86)\Enterprise Vault\EVShell.psc1" -command "& {Set-IndexLocationBackupMode server1}"
Set-IndexLocationBackupMode : Unable to notify the indexing service on
computer 'server1.domain.com' of backup mode changes for index
locations. Check that indexing service is running on computer
'server1.domain.com' and start the service if necessary.
At line:1 char:4
+ & {Set-IndexLocationBackupMode server1}
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (Symantec.Enterp...ationBac
kUpMode:SetIndexLocationBackUpMode) [Set-IndexLocationBackupMode], FaultEx
ception`1
+ FullyQualifiedErrorId : UnableToSetIndexLocationBackupMode,Symantec.Ente
rpriseVault.PowerShell.Commands.SetIndexLocationBackUpMode
I can confirm that the services are not stopped during this period.
I am unable to find a reason for this failure. Any ideas on this?
Thank you GertjanA.
Yes, the EV shell opens fine.
The current script was created with the help of the transform script.
After looking further into this, I found 41397 at the time of the error:
Log Name: Symantec Enterprise Vault Source: Enterprise Vault Date: 14.06.2018 05:02:36 Event ID: 41397 Task Category: Index Admin Service Level: Error Keywords: Classic User: N/A Description: Some index volumes may not have the correct backup mode set. This can result in inconsistent backups. Restart Indexing service to correct this problem. Indexing service entry id: 141F96C0C1FCB4049AB42726927711DD71710000eito-kvs Exception: Failed Index Volume => Id: 2014765 Error: Failed to read index volume metadata Failed Index Volume => Id: 2016460 Error: Failed to read index volume metadata Failed Index Volume => Id: 2016795 Error: Failed to read index volume metadata Failed Index Volume => Id: 2017303 Error: Failed to read index volume metadata Failed Index Volume => Id: 2017761 Error: Failed to read index volume metadata Failed Index Volume => Id: 2018040 Error: Failed to read index volume metadata Failed Index Volume => Id: 2018917 Error: Failed to read index volume metadata Failed Index Volume => Id: 2033838 Error: Failed to read index volume metadata Failed Index Volume => Id: 2034226 Error: Failed to read index volume metadata Failed Index Volume => Id: 2053144 Error: Failed to read index volume metadata Failed Index Volume => Id: 2064210 Error: Failed to read index volume metadata Failed Index Volume => Id: 2065847 Error: Failed to read index volume metadata Failed Index Volume => Id: 2071389 Error: Failed to read index volume metadata Failed Index Volume => Id: 2073650 Error: Failed to read index volume metadata Failed Index Volume => Id: 2075703 Error: Failed to read index volume metadata Stack Trace: at Symantec.EnterpriseVault.Indexing.Admin.EVIndexAdminUtils.InvokeHelper(Object COMInterface, Action act, String context, LoggingMode loggingMode, Boolean rethrow) at Symantec.EnterpriseVault.Indexing.Admin.IndexAdminCOM.NotifyIndexServiceBackupModeChangeEx(String indexServiceEntryId, Boolean backup, Boolean wait)
So I will recreate the repository on these servers and check again.
