Chatee ahora con Soporte
Chat con el soporte

Foglight for Virtualization Enterprise Edition 8.9.3 - Installing Foglight on Windows with an External MySQL Database

Before Installing Foglight Installing Foglight
Preparing to install Installing a new version of the Management Server Installed directories Foglight settings HP patch checking tool Uninstalling Foglight Upgrading the Management Server Installing Foglight FAQ
Running the Management Server Installing and Upgrading Cartridges Installing Agents

Option 2 - Run SQL scripts to configure the database

If you clicked Create during the database installation step, the SQL scripts in the <foglight_home>\scripts\sql directory are prepared with the provided configuration options. There are four SQL files for each database type ([dbtype]):

•
[dbtype]_drop_db.sql
•
[dbtype]_create_db.sql
•
[dbtype]_create_schema.sql
•
[dbtype]_populate_db.sql

You can review these scripts before running them.

You must run the configured scripts against the database using a third-party tool.

To perform manual database configuration:
•
Run the .sql scripts by issuing the following commands in the order shown:
a
mysql -u<DBA_username> -p<DBA_password> --force < <foglight_home>\scripts\mysql_drop_db.sql
 
* 
NOTE: When a user does not exist in the current database, the script generates “DROP USER failed” errors messages. These errors can be safely ignored.
b
mysql -u<DBA_username> -p<DBA_password> < <foglight_home>\scripts\mysql_create_db.sql
c
mysql -u<foglight_username> -p<foglight_password> < <foglight_home>\scripts\mysql_create_schema.sql
This script must be run using the Foglight Database Account User ID that you set in Step 12: Foglight repository database type. The default Foglight Database Account User ID is foglight.
d
mysql -u<foglight_username> -p<foglight_password> < <foglight_home>\scripts\mysql_populate_db.sql
This script must be run using the Foglight Database Account User ID that you set in Step 12: Foglight repository database type. The default Foglight Database Account User ID is foglight.

Example (for Foglight only):

a
mysql -uroot -ppassword --force < C:\Quest\Foglight\scripts\mysql_drop_db.sql
 
* 
NOTE: When a user does not exist in the current database, the script generates “DROP USER failed” errors messages. These errors can be safely ignored.
b
mysql -uroot -ppassword < C:\Quest\Foglight\scripts\mysql_create_db.sql
c
mysql -uroot -ppassword < C:\Quest\Foglight\scripts\mysql_create_schema.sql
d
mysql -uroot -ppassword < C:\Quest\Foglight\scripts\mysql_populate_db.sql

After you have run all four scripts, you can start the Management Server. Proceed to Starting and stopping the Management Server.

Initializing and tuning the database

Initializing and tuning the database

The following sections describe how to initialize and tune your database:

•
Initializing the database
•
Tuning an external MySQL database for Foglight

Initializing the database

For external databases, once the database has been successfully initialized, you can run Foglight.

Tuning an external MySQL database for Foglight

If you are running the Management Server with an external MySQL® database in a production environment, you may want to tune your database to ensure that it is not under-resourced. The table below lists the tunable settings in the <mysql_install_path>\my.ini file.

 
* 
NOTE: Database tuning is an advanced-user activity. Changing settings for your MySQL database incorrectly can result in problems with your Foglight installation, such as serious performance problems with the Management Server.

 

Table 3. Tuning an external database - tunable settings
my.ini setting
Recommended Value
Comments

innodb_additional_mem_pool_size

20M

Additional memory pool used by InnoDB to store metadata information.

innodb_buffer_pool_size

512M

InnoDB uses a buffer pool to cache both indexes and row data. The larger you set this the less disk I/O is needed to access data in tables. Note that on 32-bit systems you might be limited to 2 to 3.5G of user level memory per process, so do not set it too high. Also, ensure that the host has enough real memory free for specified buffer pool size. Performance will degrade substantially if the buffer pool uses virtual memory.

innodb_flush_log_at_trx_commit

2

Value 2 means that the transaction log is only flushed to the OS cache rather than to disk at each commit. The log file is still flushed to disk approximately once per second.

innodb_log_buffer_size

8M

The size of the buffer InnoDB uses for buffering log data.

innodb_log_file_size

128M

Size of each log file in a log group. You should set the combined size of log files to about 25 to 100% of your buffer pool size to avoid unneeded buffer pool flush activity on log file overwrite. Note that a larger log file size will increase the time needed for the recovery process.

max_connections

50 or more

The maximum amount of concurrent sessions the MySQL® server will allow.

tmp_table_size

32M

Maximum size for internal (in-memory) temporary tables.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación