Administering the Environment
5.2. Backing Up the Enterprise Manager Database
You should back up the Enterprise Manager database on a regular schedule or after a significant configuration change. The backup can be used in case of a problem with the Management Server. In that case, you can install the Management Server software on the new system, restore the database, and restart the Enterprise Manager services.
For the Enterprise Manager database, some maintenance is performed automatically by the software installation process, but additional manual maintenance is required.
5.2.1. Database Backup Overview
During initial software installation, the following databases are created:
• Event Log (emdb) – Stores event records that can be viewed from the Enterprise Manager portal
• Portal Configuration (liferaydb) – Stores portal accounts, privileges and other settings
• CIM Server repository (pegasusroot, rootcimv2, rootpginternal, rootpginterop) – Stores information required by the Pegasus CIM Object Manager
• Stealth Configuration repository (rootuisstealth2) – Stores Stealth configuration information, including static items (such as COIs, roles, and systems) and dynamic items (such as Management Server statistics)
When you upgrade the version of Enterprise Manager software, the content of the databases is automatically maintained. The Event Log and Portal Configuration databases are unchanged. However—if required due to a repository definition change—the other two databases change as follows:
• The CIM Server repository database is replaced (the old definition is no longer needed).
• The Stealth Configuration repository database is recreated.
Note: Before removing existing software, the repository is backed up to the folder C:\ProgramData\Unisys\Stealth\EnterpriseMgmt\RepositoryBackups\rootuisstealth2.
When the updated software is installed, the backup file is processed to restore content of the repository. Note that these backups do not replace the need for manual full database backups.
5.2.2. Certificate Backup Overview
During the software installation, the Management Certificate is created, which is used to encrypt sensitive data stored in the repository. A copy of this certificate is required if it is necessary to restore the repository.
You should save both the public and private keys for the certificate to a secure location, and if needed, you can reinstall the certificate in the Windows Certificates Personal store for the Management Server administrator user. See5.2.3 Backing up the Database and Saving Certificatesfor information about saving the certificate.
5.2.3. Backing up the Database and Saving Certificates
As with any database, full backups are critical to maintaining the integrity of your Management Server and Stealth network configuration in catastrophic failures, such as storage unit failure or server hardware failure. These backups must be stored safely so that they are available, should recovery be necessary. All repository backup files generated during the software upgrade process must also be safely backed up for possible future use. These might be needed to restore content during software installation.
Full backups of all databases should be performed
• Before and after an Enterprise Manager Software upgrade
• Before and after any significant configuration changes
• On a regular periodic schedule
It is recommended that backups be organized by software level. (For more information, see5.2.4 Restoring the Database.)
Stealth Management services that access the databases must be temporarily stopped during backup or recovery. Database backup or recovery can be performed using any tools or mechanisms you have in place.
If you choose to, you can use the MySQL utilities installed with the Enterprise Manager software to perform a backup, as follows:
1. Access Computer Management and access Services.
2. Stop the Pegasus CIM Object Manager service.
3. Verify that the Unisys Stealth COI Management service also stopped, and if it did not, stop that service as well.
4. Open a command prompt using the Run as administrator option.
5. Change to the C:\Program Files\MySQL\MySQL Server 5.6\bin directory.
6. Execute the following commands using appropriate MySQL user name and password, and the file name of your choice for the output file. (For example, for the Event Log database backup, you could name the output file “emdbbackup.”)
Notes:
• Be sure to use two hyphens before the user, password, and database entries. (For example, type - -user, rather than -user.)
• The MySQL root password might be the same password that you used to log on to the Management Server, or it might be a unique password. You created this password when you launched the Management Server instance.
• In the following commands, italicized text designates a variable, such as “MySQL root password” and “output-file-name-1.”
Enter the following commands:
• mysqldump --user=root --password=MySQL root password --databases pegasusroot rootcimv2 rootpginternal rootpginterop rootuisstealth2 > output-file-name-1
• mysqldump --user=root --password=MySQL root password --databases emdb > output-file-name-2
• mysqldump --user=root --password=MySQL root password --databases liferaydb > output-file-name-3
7. Restart the Pegasus CIM Object Manager and Unisys Stealth COI Management services.
8. Store the output files in an appropriate location.
9. Export the Management Certificate, including the public and private keys, and store it with the output files. The Management Certificate is located in the store for the user name that you used to log on to the Management Server when you installed the software (the user account that the Stealth Enterprise Manager services run under).
See5.4.2 Exporting a Certificatefor more information about how to export certificates.
Note: You can back up other certificates, if you choose to; however, only the Management certificate is used to encrypt data in the repository and must be backed up. (Other certificates can be recreated if needed.) See3.3 Certificates Overviewfor more information on certificates.
5.2.4. Restoring the Database
Note: Databases should only be restored from backups generated from the current level of Enterprise Manager software.
The following procedure describes how to restore your database and your existing configurations. In the event that your database needs to be restored, do the following:
1. If you are installing the Management Server software on a new system, install the saved certificate in the Windows Certificates Personal store for the Management Server administrator user.
2. When you are asked “Do you want to restore a previously saved Stealth Enterprise
Note: After you complete this procedure, both the database and configuration will be restored, which is why you should not restore the configuration during the installation process.
3. On the Management Server, stop the Pegasus CIM Object Manager and Unisys Stealth COI Management services.
Note: If the database is being restored on a new system, you must import the Management Certificate you created during the initial installation and saved during the Backup Procedure. See5.4 Working with Certificates (Importing and Exporting)for more information on how to import this certificate.
4. Open a command prompt, and browse to the C:\Program Files\MySQL\MySQL Server 5.6\bin directory.
5. For each database that you need to restore, execute the following command using appropriate user name, password, and file name values (using the files you created during the Backup Procedure).
Note: Be sure to use two hyphens before the user and password entries. (For example, type - -user, rather than -user.)
mysql.exe --user=MySQL user name --password=MySQL root password
< output-file-name
6. Start the Pegasus CIM Object Manager and Unisys Stealth COI Management services.