Converse agora com nosso suporte
Chat com o suporte

Enterprise Reporter 3.5.1 - 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

Moving the Enterprise Reporter database

The following summary outlines line how to move the Enterprise Reporter Database from one SQL Server to another SQL Server.

The following procedures assume that you have the following permissions:

4
Under Source, select Device, click the ellipsis (…).
5
Click Add and browse to the backup copies.
6
Click Add, select the .BAK file, and click OK twice.
7
Under Backup sets to restore, select Restore beside the backup name.
8
From the Restore database window, click OK to restore the database.
3
On the Enterprise Reporter server, select All Programs | Database Wizard.
4
Choose Select/Upgrade Database and click Next.
7
Click OK on the Database Maintenance Wizard popup that appears regarding replication.
8
Click Finish to initiate the database configuration.
9
Click OK upon completion.
1
Open Configuration Manager Information and confirm the database location.

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

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.

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®.
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.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação