...
- Go to the backup directory in the master. By default:
- NMIS: <nmis>/backups
- OMK: <omk/conf/conf.d/backups>.
- The backup file should be file_name.nmis.version. For example, authentication.nmis.3
- Rename the file, removing the version. For example, authentication.nmis.
- Move the file to the external configuration folder. By default:
- NMIS: <nmis>/conf/conf.d
- OMK: <omk>/conf/conf.d
- For some of the changes to take effect, the corresponding daemon should be restarted. For example:
- service nmis9d restart
Cleanup Utilities
opHA has two utility tools to cleanup orphaned files and orphaned metadata:
- <omk>/bin> ./opha-cli.pl act=cleanup : The purpose is cleaning master files and metadata. Must be run from the master. Will check for:
- Metadata without a file associated in the file system
- Orphan files in the file system
- Backup files
- <omk>/bin> ./opha-cli.pl act=cleanup : The purpose is cleaning poller files. Will check for:
- Orphan backup files from OMK.
- Check for duplicated configuration items in OMK: This means that there is the same configuration item in different configuration external files. This could led us to errors, as the one which is loaded first is going to override the other.
- Check for duplicated configuration items in NMIS.
Important: cleanup utilities run in simulation mode by default. It is a good practice to run as simulation to check all the files that are going to be removed. simulate=f will remove all files and metadata.
New configuration Items
These are new configuration values:
...
- Backup files are saved, but it is not possible to rollback from the GUI. By default, configuration files have 2 backup files.
- Once you edit NMIS configuration, it is not possible to edit from the GUI. You will see a message when there are some configuration files overriding the local configuration.
- If the daemon is going to be restarted, it is not going to see the result on the log. But we can becheck the opHA landing page to see the daemons state.