Re: Migrating Pathworks 5 to Advanced Server 7
From: Thomas Wirt (twnews_at_kittles.com)
Date: 01/22/04
- Next message: norm.raphael_at_metso.com: "Fw: CLUSTER INTERCONNECT values"
- Previous message: Greg Cagle: "Re: 500.000 AMD64's shipped..."
- In reply to: John Belicka: "Migrating Pathworks 5 to Advanced Server 7"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 22 Jan 2004 10:57:33 -0800
This is a complicated thing if you are trying to avoid recreating all of
your shares. At minimum you would need to upgrade to 6.0C (I think).
>From there you can upgrade to AS 7.3. You could probably upgrade on
the VAX to PW 6.0C, install PW 6.0C on the Alpha, move your file system
(with identical volume labels) to the Alpha, replace the LANMAN DBs on
the Alpha with the ones from the VAX (this involves replacing the files
in just the right way), then upgrading the Alpha to AS 7.3.
If you do not wish to do this, then you can simply install AS 7.3 on
your Alpha (make sure that you have a 07.03 license) and add shares to
match your old setup. There should not be any issues about domain. You
can join an existing domain (perhaps the domain of the VAX) or create a
new domain. Just remember that if you wish to join a domain that is a
part of your corporate network, you will need an administrator of that
domain to add your computer to the domain.
Hope this helps at least a little.
Thomas Wirt
Systems Manager
Kittle's Home Furnishings
Indianapolis, IN
jbelicka@shaw.ca (John Belicka) wrote in message news:<ffd7b0f0.0401111115.33d557ca@posting.google.com>...
> I'm looking for advice on how to proceed with the following:
>
> Situation:
> I have a VAXcluster running Pathworks 5.0f (patched) as well as a
> standalone development VAX also running the same version of Pathworks.
>
> The standalone has unique file and print shares but is somehow setup
> to get it's authentication from the VAXcluster Pathworks domain.
>
> On the other side of the room I'm setting up the equivalent config
> using Alphaservers. These will be running VMS 7.3-1 and Advanced
> server 7.3.
>
> DECNET IV and Plus are in use with Multinet being the common IP stack.
> I believe Pathworks is currently running using DECnet IV.
>
>
> Requirement:
> As this is a hardware/software replacement only at this time, could I
> get some fundamental feedback on how to best configure the new
> environment to look as much like the old as possible.
>
> I believe we want to set up our own domain with a trusted domain on
> the development box. Participation with an in-house NT (soon to be
> W2003 AD domain)needs be very basic only - we share printers and allow
> WIN-users access to shares obviously. I haven't discussed shared
> authentication with the WIN-side of the IT group at this point.
>
>
> Please keep in mind I'm NOT a PWks guru, just a VMS systems manager
> who has inheritted the maintenance (for now) of a required
> configuration. So I'm after an overview commentary and then pointers
> to the doc to execute on this migration. Later, well, we'll see about
> later...
>
> Thanks in advance
> John B
- Next message: norm.raphael_at_metso.com: "Fw: CLUSTER INTERCONNECT values"
- Previous message: Greg Cagle: "Re: 500.000 AMD64's shipped..."
- In reply to: John Belicka: "Migrating Pathworks 5 to Advanced Server 7"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
