Video Screencast Help

EV Auto Enabled Mailboxes

Created: 14 Jan 2014 • Updated: 15 Jan 2014 | 3 comments
KeirL's picture
This issue has been solved. See solution.

Hi everyone

I'm after a bit of clarification on what EV does from an Archive perspective when mailboxes move to different DAG member that is serviced by a different EV server.

When I create a provisioning group I need to assign a vault store to be used when auto enabling mailboxes that fall within this provisioning group. So I can choose a vault store that hosts most of the mailboxes for that provisioning group, but it's likely that these mailboxes will move to other DAG members over time. 

I understand that when the provisioning task is re-run, EV will determine that the mailbox has moved to a different DAG memeber that is managed by a different EV server and so the other EV server will archive the items for that users mailbox. 

I after clarification on the impact this has on the users Archive which was initially on a partition that is hosted on the first EV server (this is assuming that local NTFS volumes). Is the Archive a 'logical' entity that can be written across multiple vault stores and so will be written to a partition residing on the new EV server (which will be in a different vault store) or is the data sent over the network to the EV server that hosts the partition on which the users archive was originally created.

cheers

Operating Systems:

Comments 3 CommentsJump to latest comment

Advisor's picture

is the data sent over the network to the EV server that hosts the partition on which the users archive was originally created?

Answer: Yes the data will be sent across EV servers. The storage service which manages the vault store is responsible for storing the archived items using Storage Archive process.

SOLUTION
KeirL's picture

Great - thanks for the clarification

cheers

Advisor's picture

glad to help!