立即与支持人员聊天
与支持团队交流

InTrust 11.6.1 - Contingency Planning Guide

InTrust Agent Recovery

Agent Failure (Target Computer is Over Firewall)

Backup Copy

Solution
Target computer backup available

Restore target computer from the backup. Agent will be recovered and restarted automatically. You should manually establish agent-server connection, as described in Installing Agents Manually.

No backup

Recover the target computer and re-install the agent. For details, see the Deploying Agents topic in the Deployment Guide.

Agent Failure (Target Computer is Not Over Firewall)

Backup Copy Solution
Target computer backup available

Recover target computer from the backup. After that:

  • If agent was installed automatically, then it will be recovered, and agent-server connection will be re-established automatically after the heartbeat interval, or when gathering process starts.
  • Otherwise, agent-server connection must be re-established manually, as described in the Establishing a Connection with the Server topic in Installing Agents Manually.
No backup

Recover a target computer with the same name.

  • If installed automatically, an agent will be recovered and re-connected with the server when gathering process starts, or when site computers are enumerated for the monitoring.
  • If installed manually, an agent should be re-installed and re-connected manually.

Configuration Database Recovery

Configuration Database Failure

Backup Copy Solution
Database backup available

Restore the configuration database from the backup and apply changes (if any) made after the backup; restart each InTrust Server.

No backup

There is no way to restore configuration database.

All configuration data is lost. You must re-deploy InTrust Organization anew (create a new Configuration database, re-install all InTrust servers and configure all components).

Using the adccfgdb.exe Utility

The adccfgdb.exe utility is included in the InTrust Resource Kit to help you switch the configuration database for the InTrust server (on which you run the tool) from one SQL server to another. You can launch the utility, for example, if your original SQL server with the InTrust configuration database went down because of the system disk failure (but the database is safe), or to switch to another SQL server whenever needed.

Note: You can also use this utility to set new credentials for accessing your existing configuration database. For details about utility usage, run adccfgdb.exe without any arguments.

Use the utility as follows:

  1. Stop the Quest InTrust Server and Quest InTrust Real-Time Monitoring Server services.
  2. If SQL server is running and you just need to switch the InTrust configuration database to another SQL server, then detach this database on the current server, and attach it on the new server.
  3. If SQL server went down because of the system disk failure, then move all configuration database files to another SQL server and attach this database on that server.
  4. Launch the adccfgdb.exe utility on the InTrust server, as follows:
    adccfgdb.exe [/auth {SQL|NT}] [/server <sqlname>] [/database <dbname>] [/user <username>] [/password <pwd>|{*}]
    where
    /auth {SQL|NT}—authentication method to be used when connecting to the database
    /server <sqlname>—name of the SQL Server where the InTrust configuration database will reside
    /database <dbname>—database name
    /user <username>—user name to be used in SQL authentication mode
    /password <pwd> |{*}—password to be used in SQL authentication mode, or asterisk if the password will be supplied interactively

After the utility has finished running, open the properties of the configuration database available in InTrust Manager | Configuration | Data Stores, and specify the new configuration database location and/or access credentials.

Caution: The account you specify must be granted the same access rights on the SQL server and configuration database as before switching.

Audit Database Recovery

Audit Database Failure

Backup Copy

Solution
DB backup available

Restore Audit database from the backup.

No backup

To avoid re-configuring your gathering jobs, create the new Audit database in the following way:

  1. In InTrust Manager, select Configuration | Data Stores | Databases, and open your Audit database properties. Find out the database name, location, and access credentials.
  2. On the SQL Server specified as database location, create a new Audit database with the same name and access credentials using SQL Server tools. Verify connection settings by connecting to this database with the specified credentials.

Data can be imported to the new database from your repository.

.

Alert Database Recovery

Alert Database Failure

Backup Copy Solution
Database backup available

Restore Alert database from the backup.

No backup

All alert data is lost.

To create a new Alert database:

  1. In InTrust Manager, select Configuration | Data Stores | Databases, and open your Alert database properties. Find out the database name, location, and access credentials.
  2. On the SQL Server specified as database location, create a new Alert database with the same name and access credentials. Make sure the Monitoring Console web application account can access the new database.
  3. After you create a new Alert database, open the Monitoring Console Administration page (for example, from the Start menu), and on the Database tab check the credentials for database access.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级