Enterprise Vault - Centera temp location
All,
We have two Centera - replication is uni-directional between the Centera clusters.
The EV will be installed on two node active passive (multi-site) Cluster using Windows Server 2008 R2 enterprise.
The Centera tem location is not on a shared SAN - it is on a SAN volume presented to Node A of the Windows cluster but asynchronous replication will run to the other side.
What if we have a site DR, while Centera and Windows Server 2008 will failover but the temp location wouldnt? Will Centera complain about it. What behaviour will EV have in this case?
i'm pretty sure the deallocation will not remove sql/indexing records though , because it does the SQL lookup first and then goes through the temp collections area grouping them in to 100 items or whatever it has in 15 seconds and then pushes to a clip.
what can happen is where you have a rolling allocation and deallocation if one of the items is missing.
So if you have item1, item2, item3 and item4 in the database, it puts them in to a collection and then pushes them to the centera.
If an item physically doesn't exist, like item3 for instance, it will then deallocate item1,2,3 and 4 and then try again once all the items have been stored, the collection entry is then given the clipID, otherwise it will allocate, reallocate, allocate again etc.
No new transactionID's will be created, especially since in EV9+ any pending items that have been stored, indexed etc, will keep the same transactionID as not to create duplicates.