Many client have question on proper backup and restore for the UIM product.
This will be completely unique to each customer based on some of the following
-topology and architecture of systems.
-the underlying hardware technology
-business tolerance for risk and down time.
UIM 20.3 /20.4.x
Each client's backup needs will be different as their installation will be different. Support can not provide detailed backup for any client.
If you need help creating a backup and restore strategy we will need to engage our services department.
That being said below are some general guide lines on this.
The details of this will greatly very depending on your business rules and tolerance for risk.
Main components to backup:
1) Primary UIM server. i.e the entire nimsoft directory.
2) The UIM database.
3) OC Server. i.e the entire nimsoft directory.
4) CABI server. i.e the entire nimsoft directory.
5) Tunnel connector hubs i.e the entire nimsoft directory.
6) If you are not using templates or super packages then each robot entire nimsoft directory.
Many clients these days are using Virtual machines and so are relying on VM snapshots to deal with backup and restore issue.
This would need be discussed with your internal admin teams.
How often you do backups, how long they are retained and how often you test them will be a internal business decision based on
your companies risk tolerance for loss of data or being down.
Clients will need to work with their DBA for the best strategy on backing up the database. In addition, clients should also work with the system / VM admins on the proper backup strategies for the operating systems hosting the UIM infrastructure.