Anonymous_User Absent Member.
Absent Member.
1070 views

Another question on migration (or maybe the same one)

I'm still unclear about migrating the DHCP server setups when I migrate
to a new server (using the migration tool). Netware 6.5 SP7 both sides
of it, replacing slowly-failing hardware.

It appears to me that I should be installing DHCP server on the target
server -- doing so is not a problem -- but I'm unclear as to what needs
to be migrated, and how, re. the DHCP configurations (scopes etc.) I am
only offered file migrations on the source server, no other objects as
most items are from the container above the server and/or located on
another server. So are there files I should be copying to transfer DHCP
server functionality, or is there a fix I should make after-the-fact
using DHCP Admin or Console1?

For example, apparently to migrate Groupwise functionality and have it
work properly, I need to install the product on the target server, even
though I can bring over configuration & email database files; the
migration doesn't recognize in some way that Groupwise server services
are running, so I'd have to otherwise manually identify all files to
move & try to reconstruct it.

Similarly, the question here is for the DHCP server: how do I ensure
the migration to the new server, what should I copy, what should I back
up? Or am I stuck with a post-migration run of DHCP admin & re-defining
everything?

Thanks.
Labels (1)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: Another question on migration (or maybe the same one)

Hi,

DE wrote:
>
> I'm still unclear about migrating the DHCP server setups when I migrate
> to a new server (using the migration tool). Netware 6.5 SP7 both sides
> of it, replacing slowly-failing hardware.
>
> It appears to me that I should be installing DHCP server on the target
> server -- doing so is not a problem -- but I'm unclear as to what needs
> to be migrated, and how, re. the DHCP configurations (scopes etc.)


Precisely nothing. All configuration of DHCP is stored in eDir, and that
doesn't change, and doesn't get migrated. The new server will take over
the full identity of the old one.


> For example, apparently to migrate Groupwise functionality and have it
> work properly, I need to install the product on the target server,


Precisely. You need to *install* the application (just as you need to
install DNS/DHCP on the new server). But you don't need to *configure*
it. Also, in case of Groupwise, of course you need to make sure to
migrate over the groupwise data.

> even
> though I can bring over configuration & email database files; the
> migration doesn't recognize in some way that Groupwise server services
> are running, so I'd have to otherwise manually identify all files to
> move & try to reconstruct it.


No. You don't need to fo any such task "manually". YOu migrate the data,
and then (re)install the Groupwise applications, pointing it at the
existing data.

> Similarly, the question here is for the DHCP server: how do I ensure
> the migration to the new server, what should I copy, what should I back
> up? Or am I stuck with a post-migration run of DHCP admin & re-defining
> everything?


Of course not. You install a pre-migration server, you migrate, then you
finalize the pre-migration server by installing the same products that
were running on the old server. That's it.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Another question on migration (or maybe the same one)

Massimo Rosen wrote:
> Hi,
>
> DE wrote:
>> I'm still unclear about migrating the DHCP server setups when I migrate
>> to a new server (using the migration tool). Netware 6.5 SP7 both sides
>> of it, replacing slowly-failing hardware.
>>
>> It appears to me that I should be installing DHCP server on the target
>> server -- doing so is not a problem -- but I'm unclear as to what needs
>> to be migrated, and how, re. the DHCP configurations (scopes etc.)

>
> Precisely nothing. All configuration of DHCP is stored in eDir, and that
> doesn't change, and doesn't get migrated. The new server will take over
> the full identity of the old one.
>
>
>> For example, apparently to migrate Groupwise functionality and have it
>> work properly, I need to install the product on the target server,

>
> Precisely. You need to *install* the application (just as you need to
> install DNS/DHCP on the new server). But you don't need to *configure*
> it. Also, in case of Groupwise, of course you need to make sure to
> migrate over the groupwise data.
>
>> even
>> though I can bring over configuration & email database files; the
>> migration doesn't recognize in some way that Groupwise server services
>> are running, so I'd have to otherwise manually identify all files to
>> move & try to reconstruct it.

>
> No. You don't need to fo any such task "manually". YOu migrate the data,
> and then (re)install the Groupwise applications, pointing it at the
> existing data.
>
>> Similarly, the question here is for the DHCP server: how do I ensure
>> the migration to the new server, what should I copy, what should I back
>> up? Or am I stuck with a post-migration run of DHCP admin & re-defining
>> everything?

>
> Of course not. You install a pre-migration server, you migrate, then you
> finalize the pre-migration server by installing the same products that
> were running on the old server. That's it.
>
> CU,


Thank you for clarifying. I am not expressing myself well but I do
understand the options with Groupwise, but I appreciate your clarifying
about the DHCP "data" (re. eDir).

I think the thing I've got in my mind, that causes me to have to
differentiate, is that with Groupwise, I can do a base install & then
(presumably) restore the "Groupwise System" from tape backup (Backup
Exec refers to it in those terms, but it includes domain, PO, etc. as
well as the data files.) From the failed migration, it was at least
easy to also see that groupwise-related files in, say, SYS:SYSTEM
weren't brought over by default. But for DHCP, from what you are
saying, I should only need to install the product & everything else will
migrate.

Thanks again, and sorry for being a bit slow with this, but for some
reason, I've never been involved in a migration before (just new servers
& upgrades, and most of that some years ago.)
0 Likes
Knowledge Partner
Knowledge Partner

Re: Another question on migration (or maybe the same one)

Hi,

DE wrote:
>
> I think the thing I've got in my mind, that causes me to have to
> differentiate, is that with Groupwise, I can do a base install & then
> (presumably) restore the "Groupwise System" from tape backup (Backup
> Exec refers to it in those terms, but it includes domain, PO, etc. as
> well as the data files.)


No. I think I understand you right the first time, and what you suppose
above is *not* the right way. You do not install a *new* system in
Groupwise, and your order is wrong. You *first* move the groupwise data,
in wahetver way (through the migration wizard, restore from backup,
whatever). ANd *then* you install the groupwise applications, but you do
*not* install a completely new groupwise system.

> From the failed migration, it was at least
> easy to also see that groupwise-related files in, say, SYS:SYSTEM
> weren't brought over by default.


That's correct. Nothing in the core OS directories gets directly
migrated over. The reason for this is that the original use of the
migration wizard was to move from older OS versions to newer ones. In
that case, it would be extremely dangerous to touch anything in the core
OS directories.

> But for DHCP, from what you are
> saying, I should only need to install the product & everything else will
> migrate.


Yes, and that's exactly the same for Groupwise. You first migrate the
Data, and then you (re)install the applications to the new server. But
only the apps. No settings, nothing.

If you have any questions around how to do that with Groupwise, I'd
suggest you ask over in the matching groupwise install group.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Another question on migration (or maybe the same one)

Massimo Rosen wrote:
> Hi,
>
> DE wrote:
>> I think the thing I've got in my mind, that causes me to have to
>> differentiate, is that with Groupwise, I can do a base install & then
>> (presumably) restore the "Groupwise System" from tape backup (Backup
>> Exec refers to it in those terms, but it includes domain, PO, etc. as
>> well as the data files.)

>
> No. I think I understand you right the first time, and what you suppose
> above is *not* the right way. You do not install a *new* system in
> Groupwise, and your order is wrong. You *first* move the groupwise data,
> in wahetver way (through the migration wizard, restore from backup,
> whatever). ANd *then* you install the groupwise applications, but you do
> *not* install a completely new groupwise system.
>
>> From the failed migration, it was at least
>> easy to also see that groupwise-related files in, say, SYS:SYSTEM
>> weren't brought over by default.

>
> That's correct. Nothing in the core OS directories gets directly
> migrated over. The reason for this is that the original use of the
> migration wizard was to move from older OS versions to newer ones. In
> that case, it would be extremely dangerous to touch anything in the core
> OS directories.
>
>> But for DHCP, from what you are
>> saying, I should only need to install the product & everything else will
>> migrate.

>
> Yes, and that's exactly the same for Groupwise. You first migrate the
> Data, and then you (re)install the applications to the new server. But
> only the apps. No settings, nothing.
>
> If you have any questions around how to do that with Groupwise, I'd
> suggest you ask over in the matching groupwise install group.
>
> CU,


I don't think we are communicating well, but that's OK ... it's done now.

FWIW, I think you & I are not connecting on this, because with
Groupwise, you have to have a way to deal with the NCF & CFG files, and
the .MTA and .POA as well, that reside in sys:\system and don't migrate
automatically. Those are separate from what I'd consider the groupwise
"data" (i.e. the actual mail data) which resides elsewhere.

Also, as far as I can tell, Backup Exec wouldn't let one restore what it
calls the "groupwise system" (i.e. the data) without gwtsa first being
present.

All this is very different from how the DHCP migration went -- just
re-installed the product & it apparently picked up the necessary info
from the directory. With Groupwise, despite the directory & ConsoleOne,
the CFG files are critical, as well as some NLMs.

In any case, it all went OK this time. I suspect the core problem the
last time was simply disabling login; this time, I knocked off the
insistent users who hadn't logged out, to avoid disabling login since I
couldn't just set up a more restricted network between the servers, and
it all went fine. I also made a point of using -the- Admin login
instead of one with equivalent rights.

Meanwhile, though, it was an enormously tedious process! I didn't
initially expect it to take that long, but with about 140GB total of
data to be migrated, it was many hours. Then some quirks to work out
with GWIA, but I'm finally done.

Thanks again for your help & clarification in this, especially for
pointing me to the wiki page, which contained a lot of good info.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Another question on migration (or maybe the same one)

Hi,

DE wrote:
>
> I don't think we are communicating well, but that's OK ... it's done now.
>
> FWIW, I think you & I are not connecting on this, because with
> Groupwise, you have to have a way to deal with the NCF & CFG files, and
> the .MTA and .POA as well, that reside in sys:\system and don't migrate
> automatically.


Correct. But they do get recreated when reinstalling the GW apps. That's
what the reinstall is supposed to do.

BTW, the GW files do *not* necessarily have to sit in sys:\system.
That's just a suggested default. If you have them installed into another
directory (even a completely different Volume), you don't have to worry
about them.

> Those are separate from what I'd consider the groupwise
> "data" (i.e. the actual mail data) which resides elsewhere.
>
> Also, as far as I can tell, Backup Exec wouldn't let one restore what it
> calls the "groupwise system" (i.e. the data) without gwtsa first being
> present.


If you're using GWTSA, and insist on restoring from backup, you're
making your life very unnecessary complicated.

> All this is very different from how the DHCP migration went -- just
> re-installed the product & it apparently picked up the necessary info
> from the directory.


No, it's exactly the same.

> With Groupwise, despite the directory & ConsoleOne,
> the CFG files are critical, as well as some NLMs.


No, the CFG files are *not* critical. They are virtually empty, *except*
that they contain the paths to the GW data, which get refilled through
the reinstall of the apps. The whole GW configuration is stored in the
GW databases and eDir.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.