지금 지원 담당자와 채팅
지원 담당자와 채팅

Enterprise Reporter 3.5 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding answers and getting help Overview of Enterprise Reporter Communications and Credentials Required Using the Credential Manager Setting Up Your First Collection Computers (Nodes) Modifying Your Deployment Configuring Global Settings Customizing the Configuration Manager View
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery (Name) Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your on-premises discoveries
Choosing your Active Directory Scopes Choosing your Computer Scopes Choosing Your Exchange Scopes Choosing Your File Storage Analysis Scopes Choosing Your Microsoft SQL Scopes Choosing Your NTFS Scopes Choosing Your Registry Scopes
Step 2b: Choose scopes for your cloud discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Disaster Recovery

The following backup/restore procedure is the Enterprise Reporter strategy for disaster recovery. This strategy will help ensure that Enterprise Reporter will be available for use as soon as possible. With regularly scheduled backups of the Enterprise Reporter database, recovery requires re-installing Enterprise Reporter, restoring the data, restoring a registry key, and restarting Enterprise Reporter.

Topics:  
•
Backing up Enterprise Reporter
•
Deploying Enterprise Reporter to another computer after a disaster
•
Checking the Enterprise Reporter configuration after recovery

Backing up Enterprise Reporter

One SQL Server database is created and used by Enterprise Reporter and should be included with the regular SQL Server backup. This Discovery Management database has a default name of dbReporter.

Deploying Enterprise Reporter to another computer after a disaster

If the original computer is unavailable due to disaster or hardware failure, Enterprise Reporter may need to be deployed on a new computer. The Enterprise Reporter database will be required.

To deploy Enterprise Reporter on a new computer
1
Build a recovery computer with the same name as the previous computer on which to install Enterprise Reporter.
The recovery computer must have the same name as the previous Enterprise Reporter computer so that the agents and nodes that are still active in the environment can continue to use the computer name to contact the Enterprise Reporter services.
2
Recover the Enterprise Reporter database.
This step may or may not be needed depending on how the initial configuration of Enterprise Reporter was done. For example, if the database was created on a common SQL Server® and the Enterprise Reporter server was on a separate computer, then the database is still available for use. If SQL Server® was installed on the same computer where Enterprise Reporter was installed, and that computer was damaged, then SQL Server® must be installed on the recovery computer and the Enterprise Reporter database must be restored on the recovery computer or on another SQL Server®.
3
If you have recovered the Enterprise Reporter database, you will need to import the encryption key from the backup file using the Enterprise Reporter Encryption Key Manager and the password that was entered when the encryption key was created. For more information, see Appendix: Encryption Key Manager and Importing a key file ..
* 
NOTE: If the encryption key backup file is unavailable, you may use the Enterprise Reporter Encryption Key Manager to erase the encrypted passwords used by the Enterprise Reporter Credential Manager. After using this feature, the passwords for all credentials must be re-entered using the Enterprise Reporter Credential Manager.
4
Install Enterprise Reporter on the recovery computer.
5
Start the Database Wizard.
6
Click Select/Upgrade Existing Database in the Database Wizard to allow Enterprise Reporter to make all of the necessary connections to the database and click Next.
7
Enter the database server and the database name (or accept the default of dbReporter). Select the connection type (Windows or SQL, depending on the initial configuration) and click Next.
8
In Configure Security Groups, it is recommended to leave the default setting unless another configuration was selected during the initial install. Click Next.
9
Once the database processing has finished, click Finish.
* 
NOTE: If SQL Server is installed on the same recovery computer as Enterprise Reporter, review the popup message about upgrading Enterprise Reporter. Select “I understand and wish to continue”.

Checking the Enterprise Reporter configuration after recovery

Start the Configuration Manager and check the health of the recovered Enterprise Reporter configuration.

To check the Enterprise Reporter Configuration after a recovery
1
Start the Configuration Manager.
2
Select Information.
Review and confirm all of the settings that Enterprise Reporter is currently using.
3
Click the Discovery Nodes tab.
All the nodes are displayed.
4
Remove any node with a status of Faulted by selecting the node and clicking Remove Node.
5
Select Yes on the popup message.
6
Select Discovery Management and click Manage Discoveries.
All of the discoveries should be available for use.
 
* 
NOTE: If a Shared Data Location is being used with the Clusters, then delete files located in the share as the data in this share will be out of date and will cause errors in the data in reports.

 

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택