After all the talk of how to decide on what version (32 vs 64 bit) of Domino you want to choose on Windows, I want to blog briefly on some good strategies to migrate a server from 32 to 64 bit.
My Assumptions for this article:
As discussed previously, 64 bit Domino requires a 64 bit OS and for this hypothetical case I am assuming that I am staying with the same OS type and only switching the version (32 -> 64 bit) so I do not have to take any change in disk format into account that is likely if you move from let’s say Windows to AIX.I am also assuming that I am not going to do any major upgrade of the Domino version – that would be a major change and require allot of planning and testing beyond what I want to go into in this short blog post.
Scenario 1: Switch the server
This one is easy – it is basically the same as if you are going to switch out the hardware (in-place upgrade). I would install the new server on a new piece of hardware, bring the old server down, move the data directory to the new server, rename the server, switch IP addresses (or IP reservations, whichever one it is your network does) and then bring the new server up with the original data.
The point in this switch/upgrade is that you have new hardware that you can install at your leisure, burn in and prepare. The only time-sensitive part is when you bring all the servers down, move the data and re-configure the new hardware. Hopefully the data is on a SANS and all you have to do is detach and re-attach the drives. I greatly prefer that to having to copy data from the old server to the server as that can add untold hours to a deployment schedule.
Scenario 2: In-place upgrade
This scenario basically only happens if you have no other piece of hardware that you could use and the in-place is the last straw of yours to try and get past some unspeakable evil from which you need to escape. Therefore I believe a disclaimer is in order:
Do not attempt this at home, don’t do it at the office either and if you are working for a client. Heck, if you value your sanity and don’t want to die from a heart attack don’t do this one at all! Only attempt this option if there is ABSOLUTELY no other way out.
The reason I say this is simple: garbage in = garbage out. Also, it is allot of changes on one physical machine so there is allot of opportunity to fail – two major changes on one physical machine and no good way to back out of the process if it does not work the way you are hoping for . Also, you are unlikely to be able to test this beforehand if something so you really can’t prepare for any eventuality. So again … avoid this one!
Now, if I absolutely had to do this – this is how I would do it: (rough draft)
- Have plenty of time available. If you think it will take 6 hours, triple the amount and add 10 hours for good measure. If it take long you will be tired and need rest. also, the server is unlikely to be new so is unlikely to be a fast process even if it goes well
- Make sure there is a GOOD, VALID backup and that the tapes are not old and that you can actually restore the server if you need to.
- If in any way possible, do a P2V into VMWare and test all of this first … it is insane and crazy, so testing is a must if there is any opportunity for it
- Keep a snapshot of that VMWare image around in case all hell breaks loose and it is the only thing you can offer your users to work with.
- Have enough free space on the Domino server for temp files, etc. Also make sure that the data partitions have at least 20% free space to accommodate size increases due to design changes
“ACTION!!!” – The upgrade itself
- Shut down Domino and run a manual compact against all files
- Run another back-up – just in case
- Upgrade the OS … pray to whatever Gods you believe in and hope for the best
- Run Domino, check if it runs and is accessible
- Take another back-up
- Pray, sleep, meditate and then … sacrifice a bucket of KFC chicken (like in the movie “Major League”). Also, prepare a bottle of Bourbon, crack it open and sacrifice one glass some alongside the chicken (it can only help)
- Uninstall Domino – you cannot install 64 bit over 32 … it is a disaster waiting to happen. Save the notes.ini first, you might need it
- Clean up the install directory, registry AND any temp folders etc. Reboot the server once
- Install Domino 64 bit – prepare for another sacrificial chicken bucket .. this time extra crispy would be advisable
- Attach/move/copy the data in and meditate, chant the mighty “OOOHHHMM” if that makes you feel better
- Start Domino and prepare your sacrifice
- ……… (waiting for all hell to break loose)
Let’s not go into details what to do if any one of these steps fail … there are too many to details to deal with. I am hoping that the numerous references to sacrifices (non-human) and heavy drink show you that this is more arcane magic than cool, logic guided technology. Again, I would not do this one unless there is absolutely no other way to deal with the issue.
There are many more detailed steps and planning necessary for an upgrade. Hiring somebody who has done it previously would be advisable …. You can hire me or one of my many gifted consulting colleagues to do this scary stuff for you. We already have the gray hair (if we have hair) and our digestive tracts are tough and can take the stress.
Filed under: 64 bit, Domino, Lotus Notes, Lotus Software, Upgrades & Migrations | Tagged: 32 bit, 64 bit, Administration, Domino, IBM Lotus Notes/Domino, Lotus Notes | 4 Comments »