Ask the Experts Q&A session: Managing Domino - Upgrading and Migrating - 03 June 2014 (Audio Replay & Q&A)
IBM hosted an Ask the Experts Q&A session on June 3, 2014. The topic was "Managing Domino - Upgrading & Migrating." Darla Black gave a short demo and she was joined by John Paganetti and several other members of the Domino Support and Development teams for Q&A.
- 55:36 minutes long (materials referenced in demo are linked below)
- Q&A starts at 10:22
- Roadmaps & Supportability
- Domino on 64-bit platforms
- iNotes & Notes Traveler
- SSL & HTTP
- Smart Upgrade & Policies
- General Administration & How to
Roadmaps & Supportability
Q1a. When installing Domino 9.0.1 Fix Pack 1 code, I'm getting "unable to update JVM type".
Currently there is a JVM hotfix available for this issue. The hotfix will also resolve the issue with other processes running. It will also resolve an issue that occurs at times if you re-run the 901FP1 installer, it could lead to other unexpected problems. So the roadmap from 9.0.1 is to request and apply the hotfix that's available through Support, and then apply Fix Pack 1.
Q1b. Is the JVM hotfix ready or will it take some time once I request?
It's currently available for Win 64-bit or 32-bit.
- Domino 9.0.1 Fix Pack 1 installer returns "WARNING: JVM was not upgraded" message (technote 1675089)
Note: This issue is not occurring on all systems. When you do install 901 Fix Pack 1, look at the final messages. Where you expect to see 901 Fix Pack was installed successfully, if you see a comment about JVM was not upgraded, then that would be a good time to contact Support and request the JVM fix.
Q2. What template version should the mail files be at when upgrading to Domino 9 (mail server)?
- Up to you and your plans to upgrade the Notes client. Domino can be upgraded to 9.0.1 Fix Pack 1 and then you can upgrade Notes clients at a later time and at that point decide what Mail template you would like to use.
- Typically the version chain of command would go Server >= Client >= Template. Usually it's best to not have a client using a higher template version, but clients and servers and certainly handle older templates.
- This should help you with the planning - Supported configurations for IBM Notes & Domino 9.x (technote 1628675)
Q3. When upgrading on an AIX box, do you follow the documentation for 8.5.3? Is it exactly the same?
Just double-check supported AIX Versions
Index of system requirements for Notes, Domino, Domino Administrator, Domino Designer & Notes Traveler
Q4. Is directly upgrading from Domino 7.x to Domino 9.0.1 supported?
Only thing to be careful about is OS support. When jumping from 7.0x to 9.0x, many times the OS that the 7.0.x was running on is not supported.
Q5. I am on 8.5.3 Fix Pack 6. Can I just upgrade to 9.0.1?
Yes, you can upgrade to 9.0.1.
Q6. Going from 8.5.2 to 9.0.1. We'd load 9.0.1 and do a Fix Pack and we should be good to go from that point?
Yes. Since Fix Pack 1 is the latest maintenance release that we have you would upgrade 901 and then apply the Fix Pack on top of it.
Q7. We're currently running 8.5.2 Domino on IBM i. When we upgrade to 9.0.1, will all of our clients be able to be managed, in the newer version of Domino, while we're in the process of upgrading clients?
Yes. You can upgrade your servers and not do anything else and your clients will still be accessing Domino just fine.
Q8. I've very recently taken over Domino administration for my program and I got about 1/2 hour introduction before I had to run it. We've got to apply Fix Pack 1 to 9.0. We're running Windows 2000 server. I can't find any information on install instructions. I'm looking for one basic document with basic steps on how to apply a Fix Pack.
It really is that simple. All you have to do is (1) Put the executable on your server, (2) down your server, (3) run the executable. Then it's going to take you through a nice easy wizard that will ask you a couple questions. It's going to look for the location of your Domino server. It should find that from the registry. So assuming your Domino server is installed properly, then it will be able to locate the installation path/directory of your server and it literally is five clicks later and your Fix Pack is installed.
Note: Since you're new to Domino, just FYI that to uninstall a Fix Pack, you just run the same executable and it's smart enough to revert.
Q9. I have found on many of my Windows servers, when I'm going to do an upgrade or a Fix Pack, I am setting the Windows services to manual and rebooting server so there's no hook on the Domino server, but I've found that I need to rename nnotes.dll and ndgts.dll or else the upgrade will fail.
- I've seen this before. It's usually the Windows Management Service. You can find the Process Explorer (there's a SysInternal tool that you can load on your machine). You bring everything down, run Process Explorer, and then you search to see who has nlnotes in use and quit that (e.g, something like your Backup service).
- In some cases it's the Windows Mgmt service. I've been able to go into registry, search for and delete every reference to notesstat and reboot, then that Windows Mgmt serivce doesn't access it anymore and I'm able to run all my installs just fine. I've tried stopping that service and that works as well, but what you want to do if you end up stopping the Windows Mgmt service and you run your install, you're still going to want to reboot your machine because I've found that the machine will actually reboot itself some times even though you maybe paused that service and restarted it, Windows doesn't like that you do that. We're still trying to determine why that happens. (Note: Regarding deleting the notesstat references, when you run the install, it will put all of those back in.)
Q10a. For upgrading your address book, we have about 60 servers we plan to upgrade over a year. Is it fine to upgrade the address book on your Hub servers and leave it as template 9? Will it affect any other severs when it's replicated across?
- It shouldn't. Take a look at the 8.5.3 cookbook, all the basic principles apply to 9x. I like to upgrade my Admin server to 9.0.1x and let it be the one that takes the new design in the names.nsf, and I let that replicate freely out in our internal development domains where we have down-level 6.5.6, 7.0, 8.0, 8.5.x servers. I let that template go to all of those servers and it works just fine.
- Now in some enterprises, one thing you have to be aware when you're going to a new major release of a template, is that there's two critical view design changes that some times can happen - ($Users) and ($ServerAccess). If you have a very large names.nsf with lots of users, when that design replicates to one of the other servers, those views have to be totally rebuilt on the next access. It could take some time to rebuild those views, so if anyone is trying to access the servers while the views are being rebuilt, they'll get denied because they have to be there to do authentication.
- So if you don't have that many users (like less than tens of thousands), then everything should be just fine and the views should get rebuilt pretty quick, just a little blip so do it at night. I refer to this as an uncontrolled rollout where you just let the design roll out. There's a way to do a more controlled rollout described in the cookbook. where you bring down the server and pull over the new design from the other server and then do the Updall Processing. Down-level support on servers with the latest mail templates is something we always test for and make sure it works OK.
Q10b. When I'm busy upgrading the next servers and they already have the v9 template, during the upgrade it asks "Do you want to upgrade your address book." Should I say yes or no to that option?
What I like to do, is there's a setting "Refresh Design on Admin server database only." I like to check that to turn that on. So that all it needs to do is occur on the Admin server of the Domino Directory, which is usually your Admin server. And I only like to replace the design there. There's no sense to ping-ponging it all over the place and just let it replicate out from your Admin server.
Back to top
Domino on 64-bit platforms
Q11. Is 32-bit Domino 9.0.1 Fix Pack 1 officially supported on 64-bit Win2012 R2 (VM)?
Yes, that is supported
Q12. I have a 32-bit Domino installation that I would to install a 64-bit Windows 2012 R2 server. Is that officially supported?
Yes, you can run 32-bit Domino on a 64-bit Windows machine. You need to be at 9.0.1 or 8.5.3 Fix Pack 5 (or later).
Domino support for Windows Server 2012 (technote 1617697)
Q13. Is there something important to consider when upgrading from Domino 8.5.3 32-bit Linux to Domino 9.0.1 64-bit Linux? I am thinking of DAOS, translog, etc.?
- Not concerning DAOS and TRANSLOG; however, all views and all FT indexes will be rebuilt on first access.. So you should try and get that done before starting Domino 9.0.1 the first time.
- DBMT task is great for getting that done in timely fashion
Q14. I need to migrate Lotus Domino 32-bit 8.5.3 FP3 physical server to virtual machine Windows 2008 SP2 Lotus Domino 8.5.3 FP6 64-bit. 32 bit program files folder having so many customized DLL’s. May I move full Lotus\Notes folder to Windows 2008 server and then run 64-bit server, will it work?
-> Steps to upgrade a 32-bit Domino server to 64-bit server on Windows platform (technote 1506430)
- The 32-bit .dlls are very likely not going to work with a 64-bit version of Domino. Contact the vendor/developer of these 3rd party .dlls and obtain a 64-bit compliant version of each one. May be worth asking if you still need those .dlls at all.
- If you are upgrading an application server, make sure and test your LotusScript agents on the 64-bit system. We got hit with some issues from older agents that had to be altered for 64-bit systems to run correctly.
- Upgrading from 32 to 64-bit, make sure to check compatibility of 3rd party apps like anti-virus, backup software, and monitoring tools.
- Also check compatibility of any connectors like SQL, DB2, etc.
Q15. We're upgrading from 8.5.3 32-bit to Domino 9 64bit? Do I have to uninstall all my Fix Packs at 8.5.3, install 8.5.3 64-bit, and then upgrade to Domino 9? What do you recommend? As long as the OS that you're on currently supports 64-bit, you should be able to go directly to 9.0 and install 64-bit Domino right on top of Domino 8.5.3 32-bit.
- Any time you go from 32-bit to 64-bit, all of your view indexes currently built are going to have to be rebuilt on first access and all your full-text indexes are going to get rebuilt. So what I like to do is after I've done an upgrade from 32-to 64 is either run Updall against everything (which will rebuild all the currently built views and full-text indexes) (in 901 you could actually use the DBMT task to do that as well (more efficiently too).
- After upgrade to 901, I'll usually issue DBMT -Updall Threads 8 (8 for if I have 8 processor threads) . I always do my ODS conversion early as well (in 9.0.1 there's a new ODS 52). So if going to 9.0.1, you would set CREATE_R9_DATABASES=1. And also on that DBMT command line w/ the -Updall Threads 8, I'd also do a -Compact Threads 8 and let that go through everything and once that's complete you should be able to start your server and be good to go.
Q16. I am in a position to upgrade 32-bit Lotus Domino from Windows 2003 to Lotus Domino 64-bit on Windows 2008, in 32-bit Lotus Domino. I am finding JVM out of memory issues more. If I migrate to 64-bit, will it resolve?
Can't say for sure but migrating to 64-bit is certainly the direction we are encouraging and doing so may give you some relief.
Back to top
iNotes & Notes Traveler
Q17. We're running Traveler 8.5.3 on a Windows Domino server. Any issues with that or will it be backwards compatible as well?
The Traveler server version should match the Domino server version. But if you're just upgrading the users' mail server, then your Traveler server doesn't have to match the backend.
Q18a. We currently have Traveler and our mail on one server. We have to migrate the whole thing off and in doing so we want to split our mail onto a separate server. I'm running in to some issues because the mail. I did set up a new server for mail and migrated a couple mailboxes but the mail is still going through the original server.
You created a new server and you created new replicas of the mail files over on that new server and you want mail to be delivered to that new server, you have to make sure the Person document has been updated in the Domino Directory to reflect that new server.
Q18b. The Person document has been updated, but I'm noticing on the mail logs that mail is arriving on the original server and being re-directed to the new server.
You'll probably need to look at your mail routing rules. It's probably something in your mail routing configuration that would need to be fixed. Click here to open a Service Request (PMR).
Q19. I've got some issues with how do I set up the redirects so our iNotes users get directly to the new server, but the Traveler people still get to the old server. The Help that's there is not clear to me as to what I need to do to get Traveler traffic to go to one server and iNotes traffic to another
If you're using the same external IP address when they are coming in and it's being routed, on the server that's now the home mail server you would list the iNotes redirection database as the home URL for that server. So that when a request comes in to it, after the user authenticates they are sent to their mail file. But your firewall or proxy server would have to have rules set to send the request either to Traveler or to the mail server if you are using the same external address to connect to both servers.
Q20. On 8.5.2, we have some users accessing their mail in a Web browser. Is this iNotes?
Yes. All mail templates come equipped to be accessed via the Web, which is called iNotes . You simply need the HTTP task running on your server.
Back to top
SSL & HTTP
Q21. In 9.0.1, the way I understand it is, the HTTP server is now acting as a proxy in front of Domino for all the Web services. The question I have is load related to that proxy, because you're now really running a proxy server on the same machine as you're running your primary Domino server. Running Traveler, running iNotes from that machine. I haven't been able to find anything that really discusses what that does to the overall load on the machine and the differences then between running your 8.5 standard Domino install running iNotes and that.
In 9x, you can choose to install the optional IHS SSL proxy in front of your Domino server, but by no means is it a required option. It's there to allow Domino to be FIPS compliant and use greater than a SHAW-1 SSL certificate. That is provided so that you can do that higher level SSL security for the Domino server. If you choose not to go that way, then you could use any type SSL proxy server in front of Domino. It doesn't have to be installed on the same box as Domino. To allow you to do FIPS compliance out of the box starting in 9 we did add the IHS component that can be installed.
As far as any specific numbers impacted in that, I'm not aware of anything that we have out as to what the overall impact is. I'm not aware of any numbers.
Q22. Were there any plans to upgrade the SSL component within Domino itself or is it going to remain a proxy option? The only reason I ask because the overhead of managing two machines instead of just one.
- There is an enhancement request out to do that but it is still in enhancement stage. If that does come to bear, it's not something that would be in the near future. Right now IBM is developing the two separate HTTP stacks, so right now to get Domino up since the IHS server already had that capability, the decision was made to just include that component. We're logging customer requests against that enhancement request to show the need and customer desire for that capability within the native Domino stack.
- The only thing that I know of to consider when we're talking about load and load balancing IBM HTTP server on the same box as the Domino server is the number of threads. And the domino.com file allows you to customize the number of threads that you have running. The Domino server's HTTP thread count is going to be 3x the number of HTTP threads. That's something to watch out for, it to make sure your server has enough threads. There's plenty of debugging and logging you can turn on to tell you how many threads you need. It shouldn't be any different. It should be able to handle the load it's just a matter of how many threads we have available to handle the number of users and the amount of work that's going on.
Q23. Did the speaker just say if we use IHS install option it increases 3x HTTP threads on Domino box?
What i was saying is that the default number of IHS threads is already 3x the default number of Domino HTTP threads. To start, it should be OK to leave things as is, with these default, unless we get errors that we are running out of threads.
Back to top
Smart Upgrade & Policies
Q24. Can we have a discussion of Smart Upgrade and SMU by the experts?
Yes, now scheduled for August 30th! Follow the link below for details.
Q25. Has anyone been able to upgrade Notes clients with Smart Upgrade (on Windows 7) when the users are not admins?
- You can build a Smart Upgrade Kit and package the installer with the Windows Admin credentials. SUSetRunAsWizard works very nice!
- When users aren't admins, we recommend using our SUSetRunAsWizard, which ships with Notes. It runs the install with an Admin wrapper. If you're having issues using it, please open a PMR and we can help you out! The SUSetRunAsWizards only purpose is to run an install with elevated rights. NOTE: Since it was designed well before Windows 7, there are a few bugs you might encounter that we can help you out with if you open a PMR.
- Make sure to use the latest version of the SUSetRunAsWizard. Check out this site: http://www-10.lotus.com/ldd/installblog.nsf
-> Using the Smart Upgrade Run-As Wizard
Q26. We have users on 8.5.2 and we give them new computers with an 8.5.3 image (single user client installs). We'll take their notes.ini, names, bookmark, desktop, and user ID and plop it down in the same directory structure on the new PC. We're finding that many of the people don't have their mail templates updated to the 8.5.3 mail template, even though we have that option set in our Desktop Settings Policy document. What has to happen for that policy to kick in so that it will automatically upgrade the users to their new template?
I would have to go back and study exactly what you could do with policies. You know you can go in with the Administrator client and you can see what template everybody is using on the server. I would see those who aren't running the most recent template and I would run the Convert task on the server and bring them up to date automatically. Then it would replicate down to any local replicas that they have.
I'd have to look back and familiarize myself more with the policy setting that says 'use this particular template' and when that gets applied. I don't know if that's just after the first time the client gets upgraded or if that's something you could push down to the client (I didn't think you could do that.)
Q27. In the Desktop Settings document, it asks you to put in the Release number that they're at and then the template that you want them to go to. Do you have to include Fix Packs or will a base release version pick up any other machines that have a Fix Pack included?
You want to put an asterisk (wildcard) in the policy to pick up any Fix Packs. Because what that picks up is the Fault Recovery Build line in the notes.ini file, and that does include Fix Packs. So what you can do either manually specify Fix Packs in the Desktop Settings document or you can do just something like Release 9.0.1* (or something like that).
Back to top
Installing the OpenSocial component
-> Configuring Domino Open Social Component
-> OpenSocial Component Deployment cookbook
Q28. We're interested in incorporating OpenSocial. It sounds to me like we would be running another server for OpenSocial. Is that correct?
For the pieces, the Shindig server and to serve up the social components, yes. You don't have to put it on every single server, you just have to have it on one or a couple servers that your client can access.
Q29. Are there bandwidth concerns or anything like that with regard to having OpenSocial in the mix? We've got a lot of branch locations on our WAN. Currently we have everything centrally located in one data center that everything comes back to.
You would probably have to test it out. You could always, if you had to, put a Shindig server in each geographic location, if need be. But the WAN should be fast enough that you could centralize and just have people accessing it through there.
I would say test it and see how it works and if it looks good you could do it that way. Otherwise, you have the option of each region having it's own Social Component Shindig server.
Q30. We are running a two-node Domino cluster. If we decide to install the Domino Social component, do we have to install it on both nodes of the cluster?
It is recommended to have servers in the cluster run the same version of Domino since the cluster functionality will try to keep the databases in sync.
Back to top
General Administration & How to
Q31. Is there a recommended order to run the three maintenance commands? (ie. Fixup, then Updall, then Compact)?
- Typically Fixup first, followed by Updall, then Compact. You do not have to run file maintenance in that order but it helps.
- I recommend running Compact, studying the logs to see if anything failed and then run Fixup on any failed ones. Then re-run Compact followed by Updall. Doing it this way saves some cycles on running Fixup on everything.
- For a detailed description of maintenance, see technote 7006573 - Administrator's guide to Domino Server maintenance
Q32. In a clustered environment, is one of the cluster nodes still considered the Administrative server?
Yes, but there isn't a setting to reflect this designation. Normally, the Administration server of the Domino Directory will have this assignment; otherwise, the first server placed in the cluster is considered the Admin server for the cluster.
Q33. When you talk about FTPing, do you recommend pushing or pulling those files? Should I pull them from the new server or push them from the old server?
- I don't think it matters; I've done both. BUT you want to make sure is that you have the Domino servers on both sides down when you're transferring any .nsf files (to avoid corruption).
- Also, don't transfer over the FTIs. Those you'll want to recreate on the new server.
Q34. How do we set the template to only be refreshed from the administrative server?
Database properties. See the Admin Help topic: To change design properties
Q35. Isn't Outlook supported for a limited subset of users in Domino 9. How would I define limited subset?
- It's a special program.
- "IBM mail support for Microsoft Outlook" (IMSMO) is a Limited Availability feature for Domino mail as of Notes/Domino 9.0.1. IMSMO is also known by its beta code name "Hawthorn". Please contact your sales rep who can help determine if this solution will fit your needs. (per this forum post -> http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=27F16852044EEED985257CEA007D20BC#704906ACF54F2B5985257CEB00738349)
Q36. Indirect files rock! but now we have multi-threaded compact so not use them that often anymore
DBMT supports IND files and so does multi-threaded Compact for that matter.
Q37. Regarding Sametime and Sametime Advanced. What do I need to look for as far as when I do the upgrade as to what would still be working and wouldn't be working after moving from 852 to 901.
We don't have anybody on the call to cover that question. Would recommend opening a PMR w/ the ST team for assistance. Click here to open a Service Request (PMR).
Q38. How do I get access to Passport Advantage?
For information about enrolling for Passport Advantage, go to http://www.ibm.com/software/passportadvantage/
Q39. Is there an active community within IBM for people who administer Domino?
Back to top
Original publication date
Translate this page: