Cluster repair failed, invalid nsf version

HCL Domino Domino Forum
,
1

Hello,

today I saw the following on a server cluster with configured symmetry (cluster repair)

*Reparatur fehlgeschlagen* - Datei Benutzer/username/test/Test1.nsf kann nicht repariert werden [Invalid NSF version]

This is german and translates to something like this:

*Repair failed* - file Benutzer/username/test/Test1.nsf could not be repaired [Invalid NSF version]

The repairing server is a Domino 11.0.1 whereas the donor server is a Domino 14.

Might the ODS version be the problem here? If it were, it is not documented.

Best regards,

Manuel

2

Yes, it looks like there is an ODS version issue. Make sure the ODS version is the same for both servers

3

The database doesn't exist on the Domino v11 server, only on the Domino v14 server. So how could be the ODS version the same?

4

Hello @Manuel Nientit if the database ODS version is less than the ODS 52 which is required for cluster symmetry and repair attempts to copy it from a cluster mate, it displays an error message in the console log indicating that the database cannot be repaired due to Invalid NSF version.
Preparing for a symmetrical cluster

You can use the following options to avoid this:
- Upgrade the database to the current ODS version using the compact -c <database> command.

Also if you would like you can disable repair for these databases to avoid this error message :
- Disable Repair for that database within the cluster by opening cldbdir.nsf and using Tools - Disable Repair on Selected Databases.
- Disable Repair for that database within the cluster by using the repair disable <database> command.

5

On the Domino v11 server, it doesn't exist.

On the Domino v14 server (the donor), the database has ODS 55.

6

Hello

I think the repair here checks the ODS version of the potential donor database before it tries to copy it and gives the error *Repair failed* - file ****/username/test/Test1.nsf could not be repaired [Invalid NSF version]. Need to check more on this.

This SPR VMRUC3LLMS has also been found which matches this error.

7

The server in question is 11.0.1FP6.

The SPR # VMRUC3LLMS you mentioned, should have been fixed in the 11.0.1 FP4 release.

8

Hello,

As per SPR, it is mentioned as fixed in FP4.

I would suggest collecting cluster repair diagnostic data and raise case with HCL support for further investigation about this issue.

To enable diagnostic logging, please open cluster configuration document -> Tuning tab -> Select "Repair Logging level" as "Diagnostic.

After setting the changes, restart AutoRepair task and execute following syntax command to initiate repair of the target database.

repair file Benutzer/username/test/Test1.nsf CN=Mail2/O=Renov

After collecting debug data, please provide the console log to support team for further investigation.

Regards,

Chaitanya Y

9

Hello @Thomas Bahn ,

The ODS version for the Donor server's database (Domino V14 Server) is ODS 55.
The default ODS version for the database on the Domino V11 server is ODS52. It can be upgraded to ODS 53 using the parameter "Create_R10_Databases=1".
ODS 55 was introduced in the Domino V12 version. Consequently, an "Invalid NSF version" error will be encountered on the Domino V11 server when attempting to access a database with ODS version 55.

Refer to the documentation at the following URL for details regarding ODS versions across different Domino Servers: https://help.hcl-software.com/domino/14.0.0/admin/inst_dominoondiskstructure_t.html
As the ODS version is higher than the current Domino Server version supported, you have a few options:
1) Upgrade the existing Domino server version from 11 to version 12 or 14 to handle a database with ODS version 55.

2) Downgrade the database's ODS version to 53 by issuing the following command on the Domino 14 server:
load compact <database> -r
For information on controlling the ODS version, please visit the following article:
https://help.hcl-software.com/domino/14.0.0/admin/upgrading_ods_on_servers.html

3) Disable the repair for the mentioned particular database with ODS version 55.
This can be done within the cluster by opening cldbdir.nsf and using Tools - Disable Repair on Selected Databases. Alternatively, use the command "repair disable <database>" to disable repair for that database within the cluster.
I hope this information is helpful to you. If this answer is beneficial, please accept it to benefit others with the same problem or query.

Regards,
Pramod

10

It is possible to have replicas on both servers with different ODS, but the for repair the ODS of the donor is relevant and must be supported by the receiving server's version, right?

Why?