Upgrading to Systems Director 6.2.1? - Don't get caught out, like me!
nagger 100000MRSJ Visits (5859)
The smart guys would (before the upgrade) also stopped Systems Director (smstop) and saved the database (smsave) before attempting the upgrade - so the older version could be installed and the database recovered. And, of course, a complete backup of the LPAR - sorry "Virtual Server" in Director-speak - should be business as usual.I guess I am not that smart. Oh well, its my "crash and burn" Systems Director so I have lost little that can't be fixed up but I will have to manually disconnect the endpoints so they can reconnect to the new Director. Good news: I can now try the 6.2.0 install and update to 6.2.1 in one process from scratch from the new Systems Director 6.2.1 DVD - download early as it comes in at 4.2 GB.
More later ....