Oui, j'ai besoin d'une solution
Hi All
I have a Fail-over test at one of my customers using EV building blocks this weekend and I have question or rather a concern. Let me explain the setup and what we intend to do. This test is purely for data access, we won’t be archiving from the fail-over server
- The customer will be failing over there primary EV mailbox server to the another datacentre onto another live EV mailbox server.
- They use Centeras for VS storage so I’m not worried about that
- Each Index location on the 2 EV servers has a unique drive letter. So even though we are failing over to a live EV box this shouldn’t create a conflict
The questions I have are
- Am I missing something with my understanding above. I have done many fail-overs before but not to an active EV server so I concerned about any caveats about something I may not be aware of
- This is an old EV site, 10 years, and I noticed that in the Index locations most of the locations are Drive letters but someone originally created some Index locations with a UNC path and that path is pointing to the Host name of the server we are going to failing over from. Obviously this means we can’t present these Index locations. But what would be impact of this, will EV just log errors for the locations it can’t access? Also will it cause the Index service to fail if it can’t access these locations? Similar to how the Storage service fails if it can’t find a VS partition path. Even if the Index service fails this is okay as we are only testing opening of shortcuts
- Finally the Cache location is different on the 2 EV servers. I don’t see this as a major problem but I may be missing something around the impact this will have
Any input will be appreciated J