One of my users finaly want's to upgrade his clients from level 1 to level2
and this poses some
problems. He has +1000 clients  and he is the sole user of that server. He
is going to upgrade his OS and ADSMclient at te same time using NDM (OS2
v2.11 and ADSMclient v1 to OS2 v3 and ADSMclient v2). He also want's to be
able to fall back in case of problems wich is not untinkable since he is
also upgrading his OS. The problem arises from the fact that once a node
connects using client v2 the server knows this and refuses afterwards to
work with the same node using client v1 wich in turn eliminates an easy
falback.To complicate tings he is going to do the upgrade in waves of 50
clients. Does somebody know an elegant way to do suchs a fallback because
the 2 possibility's i found are quite the oposite.
 They are: -1 Which is realy the rude way and only possible because he is
the sole user of that ADSMserver: To take a backup of the ADSMdatabase that
can be restored in case of a fallback. From an operational point a
nightmare since he want's to be able to fal back during a period of 5 day's
but he is prepared to accept it. (Strange how flexible the bureaucrats are
sometimes at the wrong time)
                -2 To rename the nodes that need to be upgraded, ad them
again and in case of a falback do some renaming of nodes. Here the
disadvantage is that i have to do 50 fullbackups wich aren't kneeded and
afterwards there are a lot of extra nodes and filespaces that have to be
deleted which means a fragmentated database and you all know how fast
DBDUMP DBLOAD works.
Greetings, Koen.