The One Identity Manager (1IM) database is planned to be deployed onto Microsoft SQL Server which is setup for log shipping.
Does 1IM support Microsoft SQL Server log shipping?
Microsoft SQL Server log shipping is tolerated in 1IM but not recommended considering that it will cause performance loss. Microsoft SQL Server log shipping for database fail-over will not be actively supported by 1IM as there are too many manual steps in between (e.g. check database consistency of both databases). For this scenario, 1IM is assumed to be reading from and writing to only one defined SQL server instance, while all remaining instances are not accessible or read-only.
1IM database fail-over strategy depends on the requirement to have the redundancy on the JobService and whether there is a need for fail-safe on JobService hosts; In general it is recommended to include JobService as a consideration in the fail-over strategy of the system it is connecting to (i.e. DB, AD, other target systems).
On one side it is possible to configure a single JobService connecting to the DNS alias pointing to the current active DB entity while on a fail-over the DNS record will auto-switch to the mirrored entity.
For this approach, there are two disadvantages:
1. Distance between DB and JobService is higher
2. Host failure will cutoff the Jobservice from the entire system
Another approach would be to deploy the JobService to execute the DB jobs to be installed on the DB server itself, connecting to the local host. The main disadvantage to this approach is the manual startup of the service in case of a fail-over.
For detailed fail-over strategy for 1IM, it is important to have a detailed knowledge of the system and it is recommended to engage Professional Services who will be able to profile the existing environment and provide recommendation on the strategy.