Synchronizer-Mount Availability Check

Description

The mount availability check at OMN will only be executed on the server which starts the synchronizer.

It checks whether the local path (in this case the relative path will not be used) of an RNC (Root Node Configuration) is a mounted volume or not. Only in case the local path exists and is a mounted volume, the mount availability check returns true.

The check will only be executed once on startup and will then never be recalculated.

Examples

Success - RNC is a mount and exists

Mount on synchronizer:

  • /omn/data

    • Contains the folder MAM

RNC

  • local path: /omn/data/

  • relative path: MAM/

Because /omn/data is mounted on the synchronizer, the DTSFiles for /omn/data and /omn has got different volume IDs. Also because /omn/data/MAM exists on the synchronizer, the mount availability check returns true.

Failure - RNC is not a mount

Mount on synchronizer:

  • /omn/data

    • Contains the folder MAM

RNC

  • local path: /omn/data/MAM/

  • relative path: null

Because /omn/data/MAM and the parent /omn/data are available on the same volume, the mount availability check returns false.

Failure - Mount is not available

Mount on synchronizer:

  • /omn/data

    • It is not mounted. But the path exist

RNC

  • local path: /omn/data/

Because /omn/data exists but is not mounted, the volume id of /omn and /omn/data is the same. That’s why the mount availability check returns false.

Conclusion

Because the mount availability check always checks the volume id of the server, you will need to configure the RNC depending on how the volumes are mounted!

So the main goal is to check if the volume is really mounted or not.

Welcome to the AI Chat!

Write a prompt to get started...