Forum Discussion

K_G's avatar
K_G
Level 6
14 years ago
Solved

system mailbox

hi,

in exchange 2010 DAG environments.

there are 3 cas server and 4 mbx servers.

all of the dbs are running in one mbx for example(this is up to customer choise.)

admin guide says that;

 

Note: If you use database availability groups (DAGs) in your Exchange Server 2010
environment, you must create each Enterprise Vault system mailbox in a database
that is replicated across the DAG.
 
but i couldnt create 4 system mbx for every mbx server,because there are alot of dbs and sometimes all of the dbs are running on just 1 server.
so what is best practise?
(if mbx server have no db when configuring ,i couuldnt configure because i souldnt select sysmbx ,but as you know i can pass this node 1 day after ,so it should be ready for archiving.)
please give me details of DAG configuration of EV for system mailbox creation.i couldnt understand above explonation in admin guide.
 
thanks...
  • I tried this in different environment and then eveytime it sends an warning event,like;

    system mbx is located different db and server ,please lacate the related server,it causes performance problem.(because of the db changes)

     

     

    Use of the Exchange Server 2010 database availability groups and

    Exchange Server mailbox archiving

    Exchange Server 2010 uses database availability groups (DAGs) to provide

    automatic database level recovery from failures of mailbox servers or individual

    mailbox databases. When one database in a DAG fails, Exchange makes active

    another passive copy of the database on a different mailbox server.

    To ensure that the mailboxes you enable for archiving are always available to

    Enterprise Vault, you must set up archiving for all the DAG member servers. You

    must also target all the DAG member servers within one Enterprise Vault site.

    It is possible to add an Exchange mailbox archiving task for a server, only when

    it hosts an active Exchange database. Your environment might contain Exchange

    2010 servers that act only as disaster recovery (DR) servers, and do not normally

    host active DAG member databases. These servers must be set up for Exchange

    server archiving because active DAG member databases can fail over to them.

    However, while these servers are not hosting active databases, you cannot set

    them up for Exchange mailbox archiving.

    To set up Exchange mailbox archiving for a DR-only server

    1 Fail over an active database to the DR-only server. This must be a database

    that contains an Enterprise Vault system mailbox.

    2 Add the DR-only server as an Exchange mailbox archiving target.

    3 Add an Exchange mailbox archiving task for the DR-only server.

    4 Fail back the database to the original host server.

  • Exchange 2010 requires a mailbox on each server that is an archive target, including every member of a DAG.  1 mailbox per server.  You will not need 4 per.  You will need to setup targets & tasks for all members of the dag.  The system mailboxes you create should be created in a DAG that resides on all mbx server.

     

    eg:

    SRV1_EVSYSMbx

    SRV2_EVSYSMbx

    SRV3_EVSYSMbx

     

    -Joe

  • i have 4 mbx server target .(every day can change the targets so all targets should be ready.)

    when i run to configuration wizard.

    i selected first mbx sys mbx in the wizard,but what about the other mbx targets?

    there are no db inside right now,and  system mbx couldnt selected .

    what i happen now?

    thanks...

  • I tried this in different environment and then eveytime it sends an warning event,like;

    system mbx is located different db and server ,please lacate the related server,it causes performance problem.(because of the db changes)

     

     

    Use of the Exchange Server 2010 database availability groups and

    Exchange Server mailbox archiving

    Exchange Server 2010 uses database availability groups (DAGs) to provide

    automatic database level recovery from failures of mailbox servers or individual

    mailbox databases. When one database in a DAG fails, Exchange makes active

    another passive copy of the database on a different mailbox server.

    To ensure that the mailboxes you enable for archiving are always available to

    Enterprise Vault, you must set up archiving for all the DAG member servers. You

    must also target all the DAG member servers within one Enterprise Vault site.

    It is possible to add an Exchange mailbox archiving task for a server, only when

    it hosts an active Exchange database. Your environment might contain Exchange

    2010 servers that act only as disaster recovery (DR) servers, and do not normally

    host active DAG member databases. These servers must be set up for Exchange

    server archiving because active DAG member databases can fail over to them.

    However, while these servers are not hosting active databases, you cannot set

    them up for Exchange mailbox archiving.

    To set up Exchange mailbox archiving for a DR-only server

    1 Fail over an active database to the DR-only server. This must be a database

    that contains an Enterprise Vault system mailbox.

    2 Add the DR-only server as an Exchange mailbox archiving target.

    3 Add an Exchange mailbox archiving task for the DR-only server.

    4 Fail back the database to the original host server.

  • Hello,

    I did this. I also gave the "send as" permissions for my VSA. But, when I add my first MBX server with my first system mailbox (the one I used to create the profile on the EV Server on Outlook), It's fine. But when I add the second MBX server with my second system mailbox I have those errors :

    The Task 'Exchange Mailbox Archiving Task for MBX02' failed to log on to Exchange server MBX02 using mailbox 'SMTP:systemmailbox02@company.com'. Please ensure the mailbox has not been hidden, that the server is running and that the Vault account has sufficient permissions on the server.

    So it's abviously a permission problem, do I need to give anything else than Send As permission for VSA on this second system mailbox account?

    Many thanks!

  • Best to start a new thread Renaud. However run the deployment scanner and be sure to input MBX02 as an exchange target, it is a quick way of checking EV is happy.