Welcome to the Open Enterprise Server Cool Solutions Community

This is a continuation of my OES2 Rolling Cluster Upgrade from NetWare guides.

The purpose of this document is to list the steps necessary to perform a Rolling Cluster Upgrade from NetWare 6.5.8 to OES2 SP2 Linux as it pertains to GroupWise.

This is currently unsupported by the Novell GroupWise team, so use at your own risk.

If you have ever rebooted a SLES server and were presented with a Grub prompt, you’ll agree that this is not the time to start learning GRUB.

The purpose of Novell Cool Solutions is to disseminate information that contributors provide and share what they think is Cool. To continue with this purpose and tradition, I have compiled a list of what I think are Cool Tips and Shortcuts that have greatly improved the efficiency of my life with Linux.
I hope you think they are Cool Solutions too!

This is part 1 of my OES2 SP2 Rolling Cluster Upgrade from NetWare guides. This first part covers basic strategy, things to know BEFORE you start upgrading, common problems you may encounter, and how to get your first node converted to OES2 SP2 Linux for a mixed cluster upgrade/conversion. Forthcoming parts will cover the actual migrating/upgrade of some of the services as they pertain to a rolling cluster upgrade.

You’ve followed all the best practices and documentation. Your eDirectory trees are healthy and replicating with no errors. Time is in synchronization and ndsrepair shows no errors or external references hanging out there.

So, what do you do when eDirectory gets a request to remove 20,000 members from a group and replicates the change to all of the replicas?

How to backup an OES2 cluster (NSS volumes) using Commvault.

We've been fighting to get Commvault to run in a clustered environment. The Commvault documentation is sketchy at best and different manuals give different procedures. This is the full installation and configuration procedure.

After the upgrade from vSphere 4.0x to vSphere 4.1 or ESXi 4 to ESXi4.1 apache on a OES 2 server wouldn't start with the error: apache2 could not bind to address 0.0.0.0:631 after vSphere upgrade

As you all probably know TCP port 631 is for IPP print, or for us Novell guy's iPrint. iPrint is started with apache (the website that is). But if iPrint cannot start, apache wouldn’t start also. So what's blocking TCP port 631?

Problems mounting /boot? After booting does your /boot appear empty? Here is a complete fix without disabling multipath completely.

Learn how the Novell recommended BorderManager replacement for Linux environments can accelerate delivery of your Web content and more. -- Novell Connection Magazine article by Ken Baker.