...
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 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 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 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 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 Delete Logging Data. |
Example:
...
UMS Server 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 |
|---|---|
| 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 |
| Note |
|---|
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:
|
...
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. |
|