(12.04.120-en_orig) IGEL UMS Maintenance Tasks
- Emese Pogany
- Harald Saller
There are a few items that are recommended to configure after your IGEL Universal Management Suite (UMS) server(s) are set up to make sure they are properly maintained and running as efficiently as possible. This article outlines some recommended configurations that should be made to make sure your UMS database and file structure are maintained properly.
Recommended Administrative Tasks (Scheduled Jobs)
There are multiple tasks that should be scheduled to properly maintain a UMS server/cluster and database.
As part of the tasks, you will be asked to provide a location to back up the data before deleting them. This can be done on a mapped (lettered) drive in Windows, or a mounted remote location on Linux if required.
Scheduling
It is recommended to schedule each task on a different day, two hours after any backups are made. This will give each task enough time to complete and allow for a rollback via the backup if data is removed that is required.
Recommended Tasks
| Task Name | Task Details | Task Notes | |
|---|---|---|---|
| 1 | Delete job execution data | UMS Administration > Administrative Tasks > Dialog Create Administrative Task > Action Delete job execution data | With this administrative task, you can delete the job execution results listed under Jobs > [job name]. For details, see (12.04.120-en_orig) Delete Job Execution Data. |
| 2 | Delete process events | UMS Administration > Administrative Tasks > Dialog Create Administrative Task > Action Delete process events | With this administrative task, you can delete the process events displayed under UMS Administration > UMS Network > Events > [timespan]. For details, see (12.04.120-en_orig) Delete Process Events. |
| 3 | Delete administrative task execution data | UMS Administration > Administrative Tasks > Dialog Create Administrative Task > Action Delete administrative task execution data | With this administrative task, you can delete the results of the execution of administrative tasks listed under UMS Administration > Global Configuration > Administrative Tasks > [task name]. For details, see (12.04.120-en_orig) Delete Administrative Task Execution Data. |
| 4 | Delete asset info history | UMS Administration > Administrative Tasks > Dialog Create Administrative Task > Action >Delete asset info history | With this administrative task, you can delete the stored asset information that is displayed under Devices > [device name]. For details, see (12.04.120-en_orig) Delete Asset Information History. |
| 5 | Delete logging data | UMS Administration > Administrative Tasks > Dialog Create Administrative Task > Action >Delete logging data | With this administrative task, you can delete the log messages that can be configured under UMS Administration >Â Global Configuration > Logging. For details, see (12.04.120-en_orig) Delete Logging Data. |
Example:
UMS Server Backups
Backup Schedule
It is recommended to schedule a backup at least once a week of the UMS database and local file repositories.
- This could be scheduled as frequently as once a day during device deployment or mass configuration changes.
This backup should be scheduled to occur at a minimum of two hours after any other Administrative Tasks are scheduled to run.
External Database
For external / third-party databases, such as Postgres and Microsoft SQL, you will need to utilize their respective backup options, or a third-party software to manage database backups.
For the internal IGEL database, see IGEL Embedded Database.
Local Files
For UMS, the IGEL database is the most critical component that needs to be backed up, and this should be handled via a third-party application connected to your external database. However, some local directories should be backed up outside of UMS. These locations are noted below.
| Directory | Usage |
|---|---|
%INSTALL_DIR%/RemoteManager/rmguiserver/webapps/ums_filetransfer | Contains all transfer files deployed via UMS including Universal Firmware Packages, wallpaper files, icon files, and SSL certificates, etc. |
UMS12 and later:
| Contains OS 12 application packages for the local UMS Web Proxy |
By default the IGEL install directory (%INSTALL_DIR%) will be located in one of the locations below. If UMS was installed to a different directory, please update the path accordingly.
| Operating System | Location(s) |
|---|---|
| Windows | C:\Program Files\IGEL\ or C:\Program Files(x86)\IGEL\ |
| Linux | /opt/IGEL/ |
IGEL Embedded Database
For the embedded database, there are a couple more items that are recommended to perform.
IGEL recommends moving to an external database for production environments, so this should only be required in POC / Lab environments. However, some smaller environments may still utilize the embedded database in production.
Local Database Optimization
If you are using the IGEL embedded database, it is recommended to run a database optimization at least every 3 months, and maybe more depending on the size of your environment. You can find more details on this process under (12.04.120-en_orig) Optimizing the Active Embedded DB, but keep in mind that this will halt services on UMS and the console will be unavailable until it completes.
Local Database Backup
If you are using the IGEL embedded database, then you will want to schedule an additional administrative task in UMS to perform this action.
| Task Name | Task Details | Notes |
|---|---|---|
| Database Backup | Creates a backup of the database, and other optional components. |
|