...
...
Failovers in
...
| Info |
|---|
Database failovers are sometimes associated with maintenance windows (patching, restarting mailbox servers, etc.) A database will failover any time the connection to the active database is severed. Database failover testing will be part of regular operational maintenance of Exchange but would only occur within published maintenance windows. During maintenance windows unless otherwise specificed Tufts email is available throughout the entirety of the maintenance. |
- Clients currently connected will need to reconnected for OWA this represents a simple re-sign in, for cached client connections this should be automatically negotiated and worse case scenario is a client restart of the mail application
- In some cases an email application left open during the maintenance window will require a restart of the application to clear cached mailbox information. This is rarely required.
- Clients that were actively working during the maintenance window may have seen a disconnection from Exchange for 30 seconds shortly followed by a reconnection to the new database location in TAB.
- In some cases a mobile device may require a restart, of the 10 devices used to test the change (4 BES, 6 Activesync), none required one.
- If you believe you are seeing unexpected behavior that warrants escalation, please submit tickets to UITSC@tufts.edu so we can track and coordinate our efforts.
- Some Mac Mail clients will disassociate thier local cached copy of the mailbox and require a mailbox rebuild or worst case mailbox remapping to resolve.
- Root cause of this is unknown at this point, there have been 3 instances recognized across the university during failover testing.
- In the March 14th failover test (2012) there were no detected instances of this bug which was seen on November 19th.
- Root cause of this is unknown at this point, there have been 3 instances recognized across the university during failover testing.
Automatic Account Generation
...