iMS > JES Migration Scenario questions
Sorry if this is long winded, i am trying to "fill in the gaps" in SUN's documentaion on a iMS > JES Migration on new hardware.
Sun's documentation on "Upgrading to JES Messaging" in chapter 2 of the JES Msg admin guide says very little with regard to the user/group/pab data in the DS other than to "Change the LDAP attribute mailHost in the user entries to be moved" Also, the migration scenario described in this document, which assumes that Messaging Server 5.2 and 6 versions are not on the same machine, eg you are moving to new hardware as well as a new Msg-Serv, says nothing with regard to schema, eg 1 vs 2.
Can I assume that1)the DS with the user/group/pab data will stay put in the DS on the original host? and that2)the schema on the new JES's msg serv needs to be set for schema 1 as well?
Lets presume now that I will then later, after I have migrated all my users' mailboxes over to the JES Msg-Serv, want to move the user/group/pab directory data over to the new host onto the JES DS and deploy SSO (access manager etc). Will I be able to easily do this given my original iMS -JES Msg Migration? Meaning is the upgrading method described in ch 2 going to hinder me in my long term goal?
In an earlier thread Jay layed out the steps to move both DS data and mailstores all together to a new set of JES DS and Msg-serv, which on a small system would likely incur very little downtime I assume. I am wondering if this method is better if one wants to get to schema 2 and SSO, other than being a little more risky?
When building my JES Msg-Serv on the new hardware with SUN's documented migration scenario in mind, I assume I will want to choose schema 1 for the new Msg-Serv, as well as point it to the user/group/pab DS instance on the old host ? Will I also need to run the directory preparation script on my user/group data in the DS , or are user's directory entries from a 5.x instance completely compatible with a JES instance?
The mail domain in my case on the new JES system will need to be exactly the same as on the old system, eg. education.ucsb.edu. Will this fact require that I do anything unique in setting up the new JES Msg instance or will making a DNS change, pointing to the new server, be adequate once I move all my users over to the new system?
If I have missed some other documentation that covers some of these questions please let me know. I don't believe the schema migrate doc specifically addresses this though.
-john
[2545 byte] By [
goubeaux] at [2007-11-26 11:19:45]
# 1
> Sorry if this is long winded, i am trying to "fill in
> the gaps" in SUN's documentaion on a iMS > JES
> Migration on new hardware.
If you're going from one box to another box, we often call this a "migration", rather than an update.
>
> Sun's documentation on "Upgrading to JES Messaging"
> in chapter 2 of the JES Msg admin guide says very
> little with regard to the user/group/pab data in the
> DS other than to "Change the LDAP attribute mailHost
> in the user entries to be moved" Also, the migration
> scenario described in this document, which assumes
> that Messaging Server 5.2 and 6 versions are not on
> the same machine, eg you are moving to new hardware
> as well as a new Msg-Serv, says nothing with regard
> to schema, eg 1 vs 2.
Reason is that Messaging Server itself really doesn't care much about which one you use.Both are fully supported, and should be pretty transparent to the server.
>
> Can I assume that 1) the DS with the
> user/group/pab data will stay put in the DS on the
> original host? and that 2) the schema on the
> new JES's msg serv needs to be set for schema 1 as
> well?
If you decide to keep the data the same as it was, then, yes, schema 1 is your setting.
If you choose, you can later migate the DS from schema 1 to schema 2. Your choice.
>
> Lets presume now that I will then later, after I have
> migrated all my users' mailboxes over to the JES
> Msg-Serv, want to move the user/group/pab directory
> data over to the new host onto the JES DS and deploy
> SSO (access manager etc). Will I be able to easily
> do this given my original iMS -JES Msg Migration?
> Meaning is the upgrading method described in ch 2
> going to hinder me in my long term goal?
Configuration of your ldap user/group location is handled by configutil. You can change that any time you want.
PAB does change, when you move from old style webmail to UWC. In either case, if you migrate the data from one ldap box to another, you can change where Messaging looks for it.
>
> In an earlier thread Jay layed out the steps to move
> both DS data and mailstores all together to a new set
> of JES DS and Msg-serv, which on a small system
> would likely incur very little downtime I assume. I
> am wondering if this method is better if one wants to
> get to schema 2 and SSO, other than being a little
> more risky?
In my opinion, moving everything at once isn't risky, as it's still on the old box, if you need to fall back.........
The last three times I migrated systems, I set up new on new boxes, and used MoveUser or imsbackup/imsrestore to migrate my users mailboxes. I had pre-loaded ldap on the new box, so all that was really needed, was to move the mail. This works in any migration from 5.x to 6.x.
>
> When building my JES Msg-Serv on the new hardware
> with SUN's documented migration scenario in mind, I
> assume I will want to choose schema 1 for the new
> Msg-Serv, as well as point it to the user/group/pab
> DS instance on the old host ? Will I also need to run
> the directory preparation script on my user/group
> data in the DS , or are user's directory entries from
> a 5.x instance completely compatible with a JES
> instance?
>
> The mail domain in my case on the new JES system will
> need to be exactly the same as on the old system, eg.
> education.ucsb.edu. Will this fact require that I do
> anything unique in setting up the new JES Msg
> instance or will making a DNS change, pointing to the
> new server, be adequate once I move all my users over
> to the new system?
>
> If I have missed some other documentation that covers
> some of these questions please let me know. I don't
> believe the schema migrate doc specifically addresses
> this though.
>
> -john
# 2
Thanks Jay,
Ok, lemme see if I have it straight: So I can pretty easily import my original u/g data into the JES's msg-serv's DS instance at the time of user store moving to the new msg-serv, but if i choose, i can leave it on the old DS and move it later? I would then just need to change the user's mailhost value if i choose to leave it right?
My compelling reason to do it as a second step later (meaning after the dust settles) is that i have all kinds of other services accessing this directory data (non msg-serv), a lot of acis, and would prefer to not interrupt too many things at once.
If I leave the u/g/pab data on the original DS and not deploy UWC can the JES msg-serv access the pab data? I also assume that UWC requires schema 2 ?
Once I do end up moving the u/g/pab data onto the new jes version's DS are these the steps i would follow:
1 extract the data from DS
2 bring down the msg-serv
3 import the data into the new DS
4 change the msg-serv's u/g directory value
5 change the msg-serv's pab directory value
6 bring the msg-serv back up
7 turn of the old DS
-john
# 3
> 1 extract the data from DS
> 2 bring down the msg-serv
> 3 import the data into the new DS
> 4 change the msg-serv's u/g directory value
> 5 change the msg-serv's pab directory value
> 6 bring the msg-serv back up
> 7 turn of the old DS
I suggest the next scenario:
1.-Tour off messaging Server
2.-backup u/g/pab Information
3.-In other server install the new Version for DS
4.-run comm_dssetup.pl program Schema 1 is fine
5.-modify the u/g/pab entries to the new scenario (for example mailhost)
6.-import u/g/pab information to the new DS
7.-Install Messaging in the second server
8.-Configura Messaging Server (configura program) and setup as your usera and Group server the new DS (maybe you want to install a local DS instance as DS configuration server for messaging)
9.- configure messaging to use the same store as the original installation
Ram
# 4
> Thanks Jay,
>
> Ok, lemme see if I have it straight: So I can pretty
> easily import my original u/g data into the JES's
> msg-serv's DS instance at the time of user store
> moving to the new msg-serv, but if i choose, i can
> leave it on the old DS and move it later? I would
> then just need to change the user's mailhost value if
> i choose to leave it right?
If both servers access the same LDAP, then changing the user's mailhost is how both servers know which one handles that user, and how to route mail between them. You can migrate small numbers of people as needed.
>
> My compelling reason to do it as a second step later
> (meaning after the dust settles) is that i have all
> kinds of other services accessing this directory data
> (non msg-serv), a lot of acis, and would prefer to
> not interrupt too many things at once.
Not an uncommon issue, and one we do appreciate. I also would do things a step at a time, if possible.
>
> f I leave the u/g/pab data on the original DS and
> not deploy UWC can the JES msg-serv access the pab
> data? I also assume that UWC requires schema 2 ?
UWC does NOT require schema 2.
JES Messaging Server's native webmail will happily access your existing ldap PAB.
>
> Once I do end up moving the u/g/pab data onto the new
> jes version's DS are these the steps i would follow:
One caviat. . .
When you install the new Messaging Server, also install a "local" ldap, and use it for configuration. Changing the config ldap is a pain....
Other than that, please see inline below.
>
> 1 extract the data from DS
> 2 bring down the msg-serv
> 3 import the data into the new DS
> 4 change the msg-serv's u/g directory value
> 5 change the msg-serv's pab directory value
> 6 bring the msg-serv back up
> 7 turn of the old DS
Yep, looks fine to me.
>
>
> -john
