暂时无法在支持网站上提交享有定期维护的产品表单。 如果您需要我们立即提供帮助,请与技术支持部门联系。 对于由此给您带来的不便,我们深表歉意。
获得即时帮助
完成注册
登录
请求定价
联系销售人员
您已选择一个产品捆绑包。 您能否选择单个产品以便我们更好地满足您的请求。 *
技术支持工程师目前正忙,无法回应您的消息。 如果需要即时服务,请通过我们的服务请求表提交请求。
以下文章可根据您的描述解决您的问题。
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.
The following sections can help you get the most out of Enterprise Reporter:
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:
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:
A discovery is resolved to a number of tasks. Each task is then automatically assigned to a node in the cluster by the server, depending on the node’s availability. If you are collecting from many targets at the same time, you can increase performance by adding more nodes to the cluster and by ensuring that each node is configured to allow the node to optimize how many concurrent tasks it can process (by setting the maximum number of concurrent tasks to a value of zero).
You can see the amount of time it took to run each instance of the discovery in the history view. If you drill down, you can see how the time was distributed across the targets, and what node did the processing. This information can aid in your decisions about how to scale up your deployment.
Adding nodes and optimizing concurrent tasks can only speed things up if there are multiple tasks to assign to the node. When a large amount of data is collected from an individual target, only one task will be created. In that case, you can improve performance by increasing the CPU, the available disk space, and the memory of the node host computer, or by looking at other factors, such as network latency.
The discovery type determines what the targets are and helps you decide on your options for speeding up collections. Clusters that handle large targets will benefit from increasing the CPU, available disk space and memory of the node host computers, or being dedicated to a smaller number of discoveries. The following table outlines how each discovery type is broken down into tasks:
Active Directory®
Each domain, or per object type by domain
Azure Active Directory
Each tenant
Azure Resource
Computer
Each computer
Exchange®
The Exchange Organization, or per object type, or per object type per server
Exchange Online™
The Office 365 tenant
File Server Analysis
Microsoft SQL
Microsoft Teams
NTFS
Each computer or per share by computer
OneDrive
Registry
您可以在附属支持站点上查找适用于戴尔*产品*的在线支持帮助。单击“继续”,转至适用于*产品*的正确支持内容和帮助。
The document was helpful.
选择评级
I easily found the information I needed.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
Quest Software门户不再支持IE 8、9和10,建议将您的浏览器升级到最新版本的Internet Explorer或Chrome。
要升级到IE 11,请单击此处
要升级到Chrome,请单击此处
如果继续使用IE 8、9和10,您将无法充分利用我们所有出色的自助服务功能。