11-04-2015 04:39 AM
Hi,
Working on EV 10.0.4 in a Clustered Environment. The Cluster is an N+1 MSCS Environment.
Have been noticing an odd behaviour in EV for quite some time now. For the moment, I do the most logical thing to do but then it is not supposed to be like that. The issue is related to Index Locations being in Backup Mode.
Every day there is an Incremental Backup of the Index Locations that happens early in the morning 5:30 AM IST. In spite of it when I check the EV Server System Status log (after a re-run), it shows that the Index Locations are in Backup Mode.
When I try to clear the Backup Mode via the EV Site, it say that ifailed to contact one of the Servers (everytime the same EV Server 02) with a "General Exception" Error.
On EV Server 02, I do see events suggesting that the Backup Mode was cleared on the same morning within minutes when the backup mode was set.
Please check the screenshots attached to this post.
Need help in troubleshooting this issue in the right manner.
11-04-2015 09:51 AM
So the indexes enter backup mode successfully but when its time for the system to take them out of backup mode it does not happen?
11-04-2015 10:08 AM
It works fine with Node 1? It might be worth rebuilding the second node...
11-04-2015 10:17 AM
Dark Knight,
Can you make sure node two is allowed to run scripts:
Before you run the script, you must set the PowerShell script execution policy, to allow only signed scripts to run. You only have to do this once.
To set the PowerShell script execution policy
Start the Enterprise Vault Management Shell.
Run the following command:
Set-ExecutionPolicy -executionPolicy AllSigned
From: https://www.veritas.com/support/en_US/article.HOWTO108641
11-04-2015 10:25 PM
How are you setting backup mode? If you use a bat file to set backupmode on the SITE, try setting it on the servers instead.
Please see this technote: http://www.veritas.com/docs/000018747
That might be the issue for you.
11-16-2015 11:26 PM
Hi,
Apologies for the late reply. I found something else while troubleshooting another issue but is related to this scenario.
http://www.veritas.com/docs/000018954 - Event 41397 logged while setting and clearing Backup Mode on Index Locations.
The scenario mentioned here in is exactly what I see in my environment.
The solution provided is easy provided it is a stand alone EV Server. But my environment is a clustered environment with 2 EV Servers running on 2N +1.
The solution is articulated in http://www.veritas.com/docs/000064598 - What is the purpose and functionality of the repository.xml file and index metadata utilized by the 64-bit indexing engine introduced in Enterprise Vault (EV) 10.0?
To be more precise;