Hi Cyrus,
I would agree with the path that Miles has suggested. Create a backup of the JSS database and your CasperShare data if it's not on a separate partition, wipe the box, install 10.5, patch it, then install the new Casper and restore your files and database.
I personally felt that Leopard use to run poor on the older Xserves if you don't have Intel based servers.
The JSS documentation has a lot of the information on how to do the JSS portions.
As for a fail over solution. I house our primary Xserve on our main server floor, and I house a second in our backup center. I have the second server setup as a secondary distribution point with nightly sync. Inside of the CasperShare folder I also house the automated database backups so they are also automatically carried over to the second server. That's how I deal with at least making sure the files and database are somewhere else in the most lazy way possible.
However, this doesn't do anything for making sure the JSS has a fail over solution that's automatic. If the main JSS goes and I need something for the clients to talk to I'd have to install the JSS on the second server and make sure the DNS pointer gets updated. As it stands the clients aren't aware of a second server they can turn to if the primary is down.
I'm not saying how I do it here is the right way, and I'd love any suggestions on how to do it better. I know that there are several requests for failover of services into JAMF already, me included.
But who are we kidding...the JSS never goes down. ;)
Craig E
