**Issue** : The pod fails to start the application and it is not
able to consume data mounted from the backup/recovery appliance.
This is happening due to the differences in the `user ID`
with which all the application processes ran on the
source machine---from where the data was captured---and
the one with which they are run on the Pod.

**Solution** : Explicitly set the security context for a pod and specify
the appropriate user ID value for **runAsUser** field in the
pod's YAML file. For example, if the MySQL application on
the source host ran all the processes with the user ID of 997,
then it is recommended to set the security context for the pod
to use the same user ID 997. This could be done by specifying
the following steps in the "spec" section of the Pod's YAML file.

See [Configure a Security Context for a Pod or Container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod)
for more information.