Additional Domino server - system databases from CD or other media

Hi all,

I'm in the process of setting up an additional Domino (11.0.1FP2 / Win2019) server in a domain.

Due to different parties implied and the new server being at a different location, I have a firewall issue which makes that the new server cannot reach the existing server using the NRPC (1352) protocol.

Due to that, I get the "server is not responding" during the set-up of the additional server, logic until here...

My thought was that the option "get system databases from CD or other media" was made for this kind of situations, that I could basically take a replica of names.nsf, events4.nsf, ddm.nsf and admin4.nsf from the old server, copy it to a location on the new server and select this option to set up my new server, with or without connectivity to the existing server.

Am I wrong? Because it clearly doesn't work.

I select this option, choose the path of the system databases and click click next. Result:

You must specify a valid server name (they mean server name of an existing one).

Then I enter the name of the existing server, optionally with it's IP address, while I know it won't respond, yet. Result:

The server is not responding...

I think I had this situation in the past, with 8.5.x or so, where the new server couldn't reach the existing server but the other direction (existing server -> new server) was working, so I used this option to set up and start the server and after that I was able to replicate from the existing server.

Do I remember this wrong or did something change between those versions?

Thanks for your help.

Greetings!

Hello

System databases from CD onle prevents that the databases has to be replicated but a connection to an exiting server is still needed.

As far as I know this was in all previous version the same

This is how you can setup an additional server in the domain without a connection:
- install the server software but don't startup the server
- create a new server on the administrative server
- copy names.nsf, the new id file, just from the windows explorer (shutdown for that moment de admin server otherwise names can be corrupted)
- make a copy of the notes.ini file to your desktop machine
- search and replace the administrative server name -> new name (not everywhere check)
- check the path's in the notes.ini
- put all files, names, id, notes.ini in the right place on the new server
Give it a shot, start the new server

Hi Thibaud !!

As Mathias told you, this option will only prevent you from replicating all databases from scratch, from an existing server to this new one. But the first thing you have to fix here is your problem with the firewall you mentioned...

Remember that you are configuring an "additional Domino Server" here...So the 1352 port can't be blocked, otherwise the connection/communication to other Domino servers will not occur and you will have several problems.

Best regards.

Wiliam Dias

Hello,

Please check if the below steps helps.


When you get the system databases like (names.nsf, events4.nsf, ddm.nsf and admin4.nsf) from the current server on a CD or other media. Along with these files you can also get the notes.ini, server.id (additional), admin.id & cert.id from the existing server in the Domain.

Once you carry these files you can follow any of the below approach.

I. Configure the server as first server in a Domain using the above ID files i.e server.id (additional), admin.id & cert.id and later use copied data from the CD or other media.

While configuring choose the below options.

a) "I want to use an existing server ID file" use browse button to choose the server.id (additional) and provide password if any.
b) "I want to use an existing certifier ID file" use browse button to choose the cert.id and provide password.
c) Domino Domain name - Provide existing Domain name same as your working server in Domain in another location. Example if the existing one is Acme then mention the
Domain as Acme.
d) "I want to use an existing Administrator ID file" use browse button to choose the admin.id and provide password. Optional you can create a new administrator ID file too.
e) With this configure the server.
f) Now don't start the Domino server. Just copy paste these system databases (names.nsf, events4.nsf, ddm.nsf and admin4.nsf) which are on the CD or other media to the DATA directory. It will prompt files exist with that name choose "Replace the files in the destination"
g) Final steps is to start the Domino server and verify.


II. Using the existing system databases and notes.ini on the new server machine.

Example of the installed server path on new machine.
Data : D:\HCL\Domino\data
Program: D:\HCL\Domino

a) Copy paste these files server.id, names.nsf, events4.nsf, ddm.nsf and admin4.nsf from CD or other media to the Data directory where the Domino server is installed on the new machine.

Copy it to D:\HCL\Domino\data

b) Copy past the notes.ini file CD or other media to the Domino program directory use option "Replace the files in the destination" when prompted.

Copy it to D:\HCL\Domino

e) Open the notes ini and make sure you change the below paths in the notes.ini that will point to the current server informations. Also make if you wanted to remove unwanted parameter which are not required on this new machine server also make sure if any IP address has to be changed ini parameters to map to new server please do so.

NotesProgram=D:\HCL\Domino
Directory=D:\HCL\Domino\data

Admin=CN=Domino Admin/O=Lotus

KeyFileName=D:\HCL\Domino\data\server.id
KeyFileName_Owner=CN=MyServer/O=Lotus

ServerKeyFileName=server.id
ServerKeyFileName_Owner=CN=MyServer/O=Lotus

ServerName=MyServer/Lotus
MailServer=CN=MyServer/O=Lotus

f) With these changes done, Final steps is to start the Domino server and verify.


Thank you.

Regards

Shrikant J

Even if you can setup the new server with the steps provided earlier: If it is an additional server and added to the names.nsf, quite some processes (e.g. adminP) rely on regular replication.

What is the business case for such an isolated "additional" server?

There's no business case and it also won't be an isolated server.

It's just that we have a very short deadline and the firewall provider is a large company with slow change request processes and my goal was to get the server up and running already, without the need to have the connectivity to the existing server. We also suspect the flow existing server -> new server already to be open, so replication should work when initiated from the existing server, but for that you need the new server alive :-).

Thanks for your answers, everyone!