Validation of Architecture Sizing versus Company Needs

At the end of any migration or deployment, there is a final stress test that shows how the platform is able to support potential loads.

Companies need to know if the architecture that has been designed really fits the company’s needs.

These businesses can either ask the company that conducts the deployment / migration for information, or ask a third party company to have an unbiased, expert opinion.

In all cases, there is no magic necessary to have this information. This is what needs to happen:

  • Infrastructure of the customer needs to be discovered
  • Usage of the architecture needs to be analyzed
  • Validation or optimization of the architecture needs to be done to perfectly fit with the company’s needs without impacting the cost (and if possible, reduce it)

Validating the architecture services can lead to multiple other services if the customer trusts your data. And by using an independent tool that’s agentless and collects / tests information as a user, you will have the perfect tool to achieve this.

GSX’s Specific Approach

GSX is completely agentless, simple to install on-site or remotely and collects statistics on server loads. It also monitors infrastructure usage, mail flows, performance, storage and quota management as soon as it has automatically discovered the environment.

Collecting Statistics Remotely over a Set Period of Time

In order to analyze the usage, see how the users impact the servers, know how the storage is used and learn if the sizing is well done concerning the daily peaks of change (for example, at 8–9 am when everyone opens their laptop), you will need statistics over a set period of time.

Validating the architecture with a focus on the needs of the company would be nonsense if you only looked at a short period of time.  If a stress test has been designed to conduct testing only over a short period of time, it's not valuable because there is not enough context.

To provide a valuable recommendation, they need to see if the architecture really fits with the business. You need to collect information from at least two weeks in order to step back and see how things are going.

GSX Monitor & Analyzer can do exactly that without impacting the servers remotely at your site or at the customer's site. The solution constantly collects information, shows it in real-time and consolidates the data to deliver user-friendly reporting with a unique analysis of trends and forecasting features.

Environmental Health View

GSX Analyzer has an exclusive feature called “Environmental Health” which allows you to draw out the entire environment based on the statistics you want.

describe the image

You can map out the environment and compare servers in terms of:

  • Availability: for example, by Exchange or SharePoint role
  • Performance: see which protocol is performing well, used the most, if the mail routing meets the SLAs, which ones don’t, etc.
  • System: see which servers consume the most, RAM, CPU, know which disk is often full despite the regular compacting process, etc.

Since the reporting tool is really user-friendly and designed for anyone to use it, you can give the customer the ability to access the information. They will be able to see statistics and play with the reports to learn how the environment is growing and what is being used, overused or underused on Exchange, SharePoint, BlackBerry and IBM Domino platforms.

Conclusion

With an agentless and independent tool that collects statistics and tests multiple environments as a user, you can determine the health of the environment based on its usage.

We provide you with everything you need to give customers the best, most valuable services available for architecture validation.

Based on these reports, your recommendations will make a huge difference and offer your clients the chance to optimize their environment and maximize their investment.