High availability is an option that eliminates a single point of failure in a

domain and provides minimal service interruption in the event of failure

Resilience. The ability of application services to tolerate transient network

failures until either the resilience timeout expires or the
external system failure is fixed.
-Failover. The migration of an application service or task to
another node when the node running the service process becomes unavailable.
-Recovery. The automatic completion of tasks after a service is interrupted.
Automatic recovery is available for PowerCenter Integration Service and
PowerCenter Repository Service tasks. You can also manually recover
PowerCenter Integration Service workflows and sessions.
Manual recovery is not part of high availability.

What happens in event of of a manual recovery

On the physical machine that hosts node_2, you will run infasetup updategatewaynode
to point to the mirrored instance of D_dom_DB.
You will start the Repository Service R_repo_2.
You will create a new Integration Service I_isvc_2 that points to R_repo_2.
You will use Workflow Manager to connect to R_repo_2. You will assign all of the
workflows to the Integration Service I_isvc_2.
How long should this take? Between when someone notices that the first node has an
issue, and when the scheduled jobs start running again, say about an hour.
Once this is all complete, you would face no issues.

The following discusses why depending on a workaround like this is not advisable:

All of the jobs that were running at the time of the failure are lost (not just
need to be recovered).
Everything in the second set of steps requires human intervention. Is it still
cheaper to build your own workaround instead of getting HA?
This approach cannot be done unplanned, especially when a lot of stakeholders are
involved.
It will require an extra server, possibly an extra license,
not to mention all of the mirroring to be done on the database side.
It will also require scripting, testing, and practice.
By the time that you have devoted all of the resources to getting this right,
you might have been better off with the HA license.

why manual HA is not recommended:

It is unsupported by Informatica. We have provided functionality (that has been

through the QA process) for this exact purpose,
and will not be supporting personal workarounds.
This is a hack (an inelegant but effective solution to a computing problem).
It is not recommended to make your production environment depend on a hack.