Forgotten Features : Replication Priorities

When your working with IBM Lotus Domino
you come across lots of little settings that have been added to the product
over the years to make life easier for the administrator or developer however
a lot of these settings are not covered in the standard Lotus training
courses. This series of blog postings aims to cover some of these ‘forgotten
features’ the first of which is Replication priorities.

No matter how big or small your Domino
environment, setting up your replication schedules can always be a bit
of a problem.  The users wants data replicated between servers faster
and the network guys want you to cut down on the amount of data that gets
pushed over the network during business hours. One solution is to setup
individual replication connection documents and set them to only replicate
certain databases however as you start rolling out new databases you’ll
find yourself editing replication connection documents to add the databases
in and possibly even forget about a server and wonder why the users complain
at a later date.

Wouldn’t it be nice to be able to setup
your replication documents and then just forget about them, well with replication
priorities this is exactly what you can do. First off you need to need
to decide on your schedule. I always try to go something like every 15
minutes for important databases, every hour for standard databases and
every 6 hours for unimportant databases. Once you know what your schedule
is going to be you then need to create 3 replication documents from your
spoke server to the hub.

For each replication document you need
to select one of the three replication priorities, either High, High &
Medium or High & Medium & Low. I also like to add a *.ntf to the
‘Do Not Replicate’ area of the High & medium replication document for
reasons you’ll see in a moment. When setting the schedule for each of the
documents don’t forget that for the H&M&L document it replicates
the high priority databases so it’s best to try avoid it clashing with
the H and H&M schedules.

Now that the replication documents are
setup how do you make full use of them. Well by default all databases will
be preset as medium in their replication settings so all you have to do
is decide what databases need to replicate more and what ones need to replicate
less. I would recommend putting the Domino Directory and AdminP database
into the high priority and any logging databases such as events4 into the
low priority. if you added the *.ntf into the H&M replication document
then they will be ignored as medium and will only replicate with the low
databases saving you a lot of effort in changing all templates to Low.

So once you have your replication priorities
setup and working as you roll out a new application you just need to set
the databases priority setting and it will automatically fall into the
right schedule, your users will be happy, your network person will be happy
and most importantly you have less to look after in the future.

Tagged with:
Posted in Uncategorized

Domino 8 on Linux

So IBM Lotus Domino 8 has been out for
a few days now and lately I’ve been thinking about replacing the OS on
my server with a Linux Distro and moving away from Windows 2003 Server.
With this in mind I loaded up a few virtual machines with different distro’s
and tried loading up the Domino server.

I tried OpenSUSE,SLES, RHEL5, CentOS5,
Fedora 8 and Ubuntu. Except Ubuntu all of these distros have reached DVD
size so make sure you have a good internet connection to download them,
I think downloading probably took up most of my testing time.

After you have installed your selected
distro make sure you apply all the updates, nearly each distro required
about 300Mb worth of updates. Then make sure you remove any smtp or web
servers that may have been installed as part of the base installation.
I found that most distro’s installed either Sendmail or Postfix which will
tie up the smtp port unless they are stopped.

Before starting the install make sure
you ‘su’ into the root account. On Ubuntu you’ll need to setup a root password
using the ‘sudo passwd’ command. I’d also advise running a ‘xhosts +local:’
command before running ‘su’ so that you can run in graphical mode install.

In truth I could only get the graphical
mode installer working in OpenSuse and SLES, no matter what I did I could
not get get it working in any of the other distros.

I did find that the installer does not
set the rights correctly on the installed files when testing on OpenSUSE.
Everything is owned by root so you need to reset them to be owned by your
‘notes’ user and group except for two files called ‘BindSock’ and ‘TuneKrnl’
which will need a special bit set so they continue to run as root.

After the install you can copy over
files from your old windows install of Domino, just make sure your set
the rights correctly on the files, then you can start up the server and
you should see your domino server console. A quick search of the web will
net you an autostart script which might need some tuning for your selected
distro. I’d recommend that you run the server in Java Console mode so you
can interact with it better.

Remember on RHEL and SLES are certified
by IBM for running your Domino server so while it will work in other distro’s
it won’t be supported.

Tagged with: ,
Posted in None

Happy Birthday Ed Brill

There was a young man from Highland Park

Who helped MS customers out of the dark

He said, "They fill you with FUD

And leave you with crud,

With a feature list that really is stark."

Happy Birthday Ed.

Tagged with:
Posted in Uncategorized

Sametime 7.5.1 CF1 Now Available

It would appear that the Sametime 7.5.1
CF1 release is now available from the Passport download site ( and probably
partnerworld download site also ).  In terms of the Mac sametime client
this release fixes
the
issues I found
in the previous
release. The dock icon now acts like a normal mac dock icon and the ‘About’
and ‘Preferences’ menu now appear to work. It should be noted that a full
reinstall of the Sametime mac client is needed to get these fixes, using
an update site won’t work.

A full fixlist is available here.

Tagged with: , ,
Posted in None
Archives