...
EmpowerID houses all data, including configuration data, application integration data, SSO and Federation configuration, directory sync configuration rules, and security roles in the Microsoft SQL Identity Warehouse database. Workflow source code and customizations are stored in an external repository on the EmpowerID servers and in a GIT repository. No server configuration data outside of the standard installation data is unique between servers. Backing up the system consists primarily of obtaining a Full SQL database backup and backups of the workflow git repository. If the customer has specific Recovery Point Objectives (RPO) and Recovery Time Objectives (RTO) that must be met for their business continuity plan, these objectives should be used to guide how granular the point in time backups of the Identity Warehouse should be configured. Disaster recovery can be obtained by simply having additional servers installed in a DR site and restoring the workflow repository along with an SQL server configured into an SQL High availability group within the Microsoft SQL configuration. Using SQL’s point-in-time restore process, a system can be easily restored to any specific minute in time depending on how your point-in-time backups (PITR) are done. All user authentication and authorization data are also stored in the Identity Warehouse. All passwords are stored in a one-way hashed encrypted format and are uniquely salted. Passwords that are stored for purposes of subsequent retrieval and use by agents are encrypted via server certificate and then the hash is encrypted. EmpowerID also supports Microsoft’s full database encryption if desired.