Re: 810 to 515 migration
- From: ga <noemail@xxxxxxxxxxxxxx>
- Date: Mon, 03 Dec 2007 10:24:12 -0600
Chuck,
Thanks for the confirmation. The only things I am leery about in this
migration (which is a fairly small box so I am not too worried) are:
1. I am not sure what "reconciliation" I will have to do to fix
resource names. It appears to me that this will mainly be used to
reconcile issues where configuration objects (lines, controllers
and/or devices) don't have valid labels??? If all labels are valid,
may not have to even do this step??? I mean, even though I will have
more hard drives, more main storage cards, etc., as long as my
existing configuration objects (lines/controllers/devices) tie to
labels that are valid for that hardware type, I should be okay?? It
looks to me like everything matches except that I might have to change
a few items that point to say CMN06 instead of CMN04.
2. Not sure about the issues with iseries access. Right now on the
old box the system name is the serial number. If I migrate that and
leave it I am thinking everything with iseries access will find the
new system. If I decide to make the system name on the new box the
new system serial number, then I will most likely have to do the
following on PC's: change the hosts and lmhosts file; create or
modify the connection to point to the new system name; possibly change
the client emulator sessions to point to the new system name, and
lastly, I have a few pc's I use cwblogon in a bat file, and I'm
guessing those also would need changed. I am kind of leaning toward
just migrating the old system name, even though it is the old serial
number and worrying about that later, if at all. It's really just an
identifier as near as I can tell, and since we are a single company
and don't connect to several different as/400's not sure it's worth
changing...
It also appears I might have to go back through the restore of
libraries a couple of times in the event I have logical files built
over physicals in more than one library, where one of the physical
files may be in a library that hasn't be restored yet when it restores
the logical.
Like I said, this is a pretty small system/migration and I can't see
there is much else to be concerned with. The new box really doesn't
have much installed on it already - I figured it'd have all os and
everything else on it, but it doesn't. Since it was ordered with
fc0205 I think they just do a real skeleton install.
I have my license keys for the new box ready to go. I assume by
following the migrate chapter in backup/recovery that all my subsystem
descriptions, libraries, files, folders, will all come across like
they were on the old.
If you have any other thoughts or suggestions you'd care to share, I'd
be interested in hearing them.
Thanks again for your responses to questions on this group!!
ga
CRPence <crpence@xxxxxxxxxxxx> wrote:
Yes. Apx D of the B&R Gd, Step 5, having selected option-2, is the
start of a /scratch install/. Scratch Install is the expression used to
describe clearing the disks; i.e. /nothing/ will be on the disks, prior
to install and restore activity. The actual initialization of the disks
occurs in the Step 6 of the instructions; the panel presented for Step
6, above Step 6a, is the warning of the disks being cleared. To best be
sure the warning is heeded, Enter does not [accidentally] get past that
panel.
Regards, Chuck
ga
nospam@xxxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: 810 to 515 migration
- From: CRPence
- Re: 810 to 515 migration
- References:
- 810 to 515 migration
- From: ga
- Re: 810 to 515 migration
- From: CRPence
- 810 to 515 migration
- Prev by Date: Re: 810 to 515 migration
- Next by Date: Re: 810 to 515 migration
- Previous by thread: Re: 810 to 515 migration
- Next by thread: Re: 810 to 515 migration
- Index(es):
Relevant Pages
|
|