Re: Problem migrating IXS

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

You didn't do the proper planning sad to say.  The issue is that the 
Windoze kernel that was required (and therefore installed) on your 2890 
model is not compatible with the processor on the new 4812 model.  You 
must reload windoze that's the only way out.  Once loaded though you can 
attach the old NWSSTG objects and copy any data that's on them but 
Windoze and your apps need to be reloaded.

Now should the B/R guide have helped you plan? No argument there!  
However there is information on the windows integration pages that 
describe this issue quite clearly.

As you likely have guessed Windoze does not have support for all 
processors in their kernel as does i5/OS, they only load what's needed 
now and there isn't a way to tell it to load more for use later. Bummer.

 - Larry

Pete Helgren wrote:
> It *seemed* like the Backup and Recovery guide steps would not only 
> migrate the basic OS from the "old" 270 but also the NWSD I had, but 
> after I migrated the objects from the 270 to 520, changed the resource 
> references in the NWSD and attempted to vary on the server, I got an 
> error: Resource name LIN05 not valid for reason code 10, secondary code 2.
>
> Basically it *acts* like it is going to start, I get the BIOS displays 
> and IBM logo showing, memory test, etc but then on the i5 console I get 
> the message.  It indicates that the 4812 is not compatible with the 
> original file server (which on the 270 is a 2890 I think).
>
> Is there a way to migrate this Windows 2000 Small Business Server 
> running on the IXS or is Bill Gates going to hand me the ONLY problem I 
> have in moving from this 270 to the i5 520?
>
> Thanks,
>
> Pete Helgren
>
>