Ensure availability and Performance of Exchange 2013
In order to ensure that your Microsoft Exchange environment is up and running, it is necessary to monitor its usage and growth to leverage capacity management.
Four points are critical when it comes to managing the availability of an application:
The main focus in the end user experience monitoring is based on how end-to-end applications appear to the end user:
- Availability: Are users able to access a specific service?
- Latency: How long does it take to send an email, is the time frame acceptable?
- Execution time: Are users able to do what they want?
A Database Availability Group (DAG) is the base component of the high availability and site resilience framework built into Microsoft Exchange. It hosts a set of databases and provides automatic database-level recovery from failures that affect individual servers or databases.
Managing the Database Availability Group is critical as it ensures High Availability. GSX is watching the DAG and send IT administrators proactive alerts for him to anticipate potential slow down and outages.
What does GSX do?
- There are two main built-in tests on replication health and single copy alerts
- Database Failover alert: receive an alert as soon as a failover occurs in the DAG
- DAG statistics: availability and usage of the database inside the DAG
- DAG availability status (DAG up or down) available on main view
- Test Replications
GSX Analyzer includes the following statistics: DAG, DAG usage, Database at DB, DAG Level and up/down, DAG Failover
GSX Monitor & Analyzer brings a perfect solution to manage the statistics collected. Everything comes out-of-the box without anything to configure.
Pre-configured templates are also available to define reports even quicker.
Here is the list of statistics directly available for trending and forecasting into GSX Analyzer.
These statistics are available in GSX Analyzer to track trends, view environmental health and see directly if there are any bottlenecks in the organization.
Most companies use a monitoring or reporting tool to alert them when something goes wrong inside their environment.
Alert information does not pinpoint the origin of the issue, leaving Administrators spend an increasing portion of their day gauging the severity and relevance of alerts they received, because they need to prioritize their actions according to the importance of the issue.
With GSX Monitor & Analyzer you will only receive the important notifications, to verify your high availability of your Exchange.
- Check the critical Windows Services and receive an alert if they are not working as expected. When a critical Windows Service is down, the corresponding entity (server, role or service) is considered down and a Server Down, Role Down or Service Down alert is sent.
- Get notified when there is an issue with the Transport Service, if there are emails not being delivered, or if a queue is suspended for example.
- Constantly check the availability of the DAG and scan on a regular basis the environment to ensure that all the tests are healthy. If not, the system will alert you that the Database Availability Group is down, describing the error or indicating the replication test that failed.
Correlate performance with growth of usage and capacity
GSX Analyzer provides all of these elements in a user- the satisfaction of friendly tool that allows IT Administrators to meet established availability and performance goals, and follow their Microsoft Exchange service delivery.
Knowing about the environment’s health can provide a big picture overview of the servers in a collaborative environment and compare the performance of SLAs and KPIs across all servers. This enables IT Administrators to rapidly identify issues with servers and prioritize them with further attention. Detecting bottlenecks at the service level or at the user level is critical to manage the availability of the infrastructure properly.
IT Administrators will be able to detect bottlenecks based on:
- Availability by Exchange services
- Performance: see which protocols are performing well, know which mail routing meet and don't meet the SLA's, etc.
- Usage: know which server sends or receives the largest amount of emails, see if the server has the maximum number of connections over a set amount of time