• June 24, 2022

Using ICFIXOBS to get rid of OBS and NSI suspensions

In the last post on April 29th we discussed OBS suspensions, why they occur and how to minimize them. NSI suspensions are similar to OBS suspensions but for IFS objects. When you see OBS or NSI suspensions and they have not disappeared after the next continuous or scheduled sync check, you can manually delete the objects on the backup node (if they truly do not exist on the source) but depending on how many objects are out of sync this could take some time.

If you would like an easier method, a tool called ICFIXOBS has been created. One caveat on this tool is that while it has gone through some extensive internal testing, it has not gone through the same QA process as the iCluster product, so there may be some bugs. The tool is also not officially supported by anyone except the author of the tool. Instructions are included in the zip file for the tool, but basically FTP the save files to the backup node into savefiles and restore all objects to a library in your library list. Source code can also be included if you would like to make your own modifications, or see how the command is working.

The ICFIXOBS command will repair these obsolete objects by either deleting them from the backup node, (which is the default) or optionally sending them from the backup node to the primary node. Most importantly the command will check before it takes any action to ensure that the object truly does not exist on the primary node before it does anything. If the object does exist (it’s a temporary NSI or OBS) it will skip the object. It will also clean up the metadata for NSI suspensions or run a second sync check for *CHKOBSLETE to remove the obsolete out of sync conditions.

The command must be run on the backup node ONLY and as part of the process will start *REXEC servers on both primary and backup nodes. Note that the group does not have to be active for the command to work, and it does not take into account latency, so it should be run at time when latency is minimal.

The command requires iCluster 7.1 TR1 but is NOT required at TR2 as the TR2 release will eliminate NSI suspensions and allow OBS out of sync conditions to be repaired through the auto repair capability of the sync check command.

Here is what the command looks like.


If you would like this tool please comment on this post (below) or email mwarkentin@rocketsoftware.com.


[box type=”note” border=”full”]Stay current with iCluster with this weekly webinar![/box]

iCluster Tech Tuesday 0 Posts

iCluster TechTuesday is a set of posts covering technical tips and techniques to help get the most out of your Rocket iCluster installation.


Leave a Comment

Your email address will not be published.