Domino 11.0.1 FP3 has been released and I added FP3 to our Docker Community GitHub project in the develop tree today. To update my servers I have created custom image. I first ran the standard ./build.sh domino. Afterwards I used the new domino_container script to build an add-on image containing my NashCom Tools and pushed it to my JForg registry. From there I can pull it on any of my servers.

Domino V12 Beta 3 introduces a Backup & Restore which is designed for easy integration with 3rd party backup solutions. The server tasks "backup" and "restore" are accompanied by a new dominobackup.ntf/nsf which holds all the configuration, logs and a database inventory. There is an admin friendly Notes based UI which allows you to restore databases with many options including restoring deleted documents and folders into the original database. The solution is intended to complement existing backup solutions and to make it easier for customers and partners to integrate with existing backup solutions which are not Domino aware today.

If you are using a home lab and want to test with many different hosts, having a wild-card DNS entry can be helpful. This will not work with Let's Encrypt DNS-01 challenges, because it would need DNS TXT records, which are not yet available in a way they can be consumed at MyDNS today. Still https://www.mydns.jp/#about is a very interesting option today, because of the sub-domain you can point to your server. And they have a very simple to use HTTP request option to update your IP.

Borg Backup https://borgbackup.readthedocs.io/en/stable/quickstart.html is a great solution for optimized backup repositories either local or a remote location. It supports encrypted repositories local or remote, compression and deduplication! Now that I moved some of my servers into containers running on Podman, I looked into backup options inside the container. For now I am preparing our Docker repository to include the Borg Backup option.

During a Domino 11.0.1 migration on AIX we ran into an abnormal process termination. This is the most ugly situation you can run into, because the process will just crash and often not leave any hint behind what went wrong. Depending on the platform you either see the parent process cashing with a "child died" signal (Linux/UNIX) -- in this case the agent scheduler process -- or the server process monitor crashing (W64). In some cases you can still find information in memcheck about the running agent. Finding the info there is quite complicated.