Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Enterprise Reporter 3.5 - Installation and Deployment Guide

Product Overview Installation Considerations for Enterprise Reporter Installing and Configuring Enterprise Reporter Managing Your Enterprise Reporter Deployment Troubleshooting Issues with Enterprise Reporter Appendix: Database Content Wizard Appendix: Encryption Key Manager Appendix: Log Viewer

Enterprise Reporter server and database considerations

You must choose a host computer for Enterprise Reporter server and a SQL Server to host the Enterprise Reporter database. Your decision affects the performance of the product.

The Enterprise Reporter server communicates directly with the database frequently. For best results, locate the Enterprise Reporter server physically close to the SQL Server.

The nodes also regularly connect to the database. The more nodes you have in your deployment, and the more discoveries you run, the greater the impact on the SQL Server. Choose a SQL Server with enough power to manage the connections and data transfer from the nodes. Check your Microsoft SQL Server documentation for more information on system requirements.

Enterprise Reporter supports a variety of SQL configurations. You can use a regular SQL instance, a SQL cluster, or a mirrored database. If your SQL deployment supports it, using clusters or mirrors allows for automatic failover recovery in the event that a SQL Server is down.

See also:

•
Failover recovery using SQL clusters

Failover recovery using SQL clusters

Using a SQL cluster instead of a single server allows for automatic failover recovery in the event that a SQL Server is down. Tasks are automatically passed to another SQL Server®. Your cluster can be configured with Always On.

Cluster Deployment Considerations

The following sections can help you get the most out of Enterprise Reporter:

•
Consider the Data to Collect Before Deploying Nodes
•
Fine Tune Each Cluster and Node
•
Optimize Node Setup
•
Plan Credential Use
•
Effectively Deploy Remote Nodes
•
Optimize Data Transfer

Consider the Data to Collect Before Deploying Nodes

There is a relationship between the design of your discoveries and the physical deployment of your clusters and nodes. By understanding what you want to collect, and what network and hardware resources you have available, you can deploy Enterprise Reporter in a way that makes sense for your environment.

When you create a discovery, you assign it to a cluster. The actual work of the collection can be done by any node in the cluster, load balanced by the Enterprise Reporter server. This means that each node should:

•
Be physically close to the targets in the discoveries you intend to assign to the cluster
•
Use credentials that can access most or all of the targets

You may not have this insight before you start using Enterprise Reporter, however you can modify your deployment at any time. If you are creating a discovery with targets that are not near the nodes of any of your clusters, consider creating a new cluster to support this.

See also:

•
Optimize Node Setup
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation