Chatee ahora con Soporte
Chat con el soporte

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.

•
Backup the database on SQL Server
•
Restore the database from a backup to the new SQL Server
•
Connect Enterprise Reporter to the new database location
•
Verify that the database has been moved successfully

The following procedures assume that you have the following permissions:

•
SQL permissions to access SQL Server Management Studio on both the current and new SQL Server to backup and restore the SQL database.
•
Windows account permissions to copy the database file from one server to another, and to stop and start services on the Enterprise Reporter server.
To back up the Enterprise Reporter database (dbReporter) on SQL Server
1
Open Enterprise Reporter and stop all node services in the Configuration Manager.
2
On the Enterprise Reporter Server, stop the Quest Enterprise Reporter Server services (and the Quest Enterprise Reporter Node services if a node was deployed on the Enterprise Reporter server).
3
Start SQL Management Studio and connect to the SQL Server where the dbReporter database resides.
4
Expand the database node.
5
Right-click on the dbReporter database and select Tasks | Back up.
6
In the Back Up Database dialog, note the location and name of the dbReporter database backup and click OK.
To restore the Enterprise Reporter database (dbReporter) from a backup to the new SQL Server
1
Copy the .BAK file(s) to the new SQL Server.
2
Start SQL Management Studio on the new SQL Server.
3
Right-click on the database’s node and select Restore Database.
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.
To connect Enterprise Reporter to the new Database location
1
On the Enterprise Reporter server, stop the Quest Enterprise Reporter Server (and the Quest Enterprise Reporter Node if a node was deployed on the Enterprise Reporter server).
2
You may have more than one node deployed, so be sure to stop all node services.
3
On the Enterprise Reporter server, select All Programs | Database Wizard.
4
Choose Select/Upgrade Database and click Next.
5
Browse to (or type in the name of) the new SQL Server and make sure the Enterprise Reporter database name is correct (for example, dbReporter), and click Next.
6
Accept the defaults on the Security Groups screen 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.
10
Once you are returned to the Main Menu of the Database Wizard, click Close.
11
Start the Enterprise Reporter Server service.
12
Start all Enterprise Reporter node services.
To verify that the database has been moved successfully
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
•
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”.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación