Merging NetWare servers is an interesting proposition, but I'm afraid I'm not
qualified to really comment on it. :-)>
Good Luck
Jerry Lawson
jlawson AT thehartford DOT com
______________________________ Forward Header __________________________________
Subject: Re: Netware Server Volume Reorganisation
Author: INTERNET.OWNERAD at SNADGATE
Date: 5/5/97 5:14 PM
Actually, I didn't find it in any V1 manual either, but I do have the V2
manuals, so I tried the command anyway and it seemed to work. Perhaps
it's a feature of an added PTF or something.
Do you have any comments about the merging of two separate Netware
servers onto one?
Dianne Sharp
Operations Analyst
ISS CUSTOMER SUPPORT
Ext 4208
>----------
>From: Jerry Lawson[SMTP:jlawson AT THEHARTFORD DOT COM]
>Sent: Monday, 05 May, 1997 11:46PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Netware Server Volume Reorganisation
>
>---------------------------- Forwarded with Changes
>---------------------------
>From: INTERNET.OWNERAD at SNADGATE
>Date: 5/5/97 12:37AM
>To: Jerry Lawson at ASUPO
>*To: *ADSM-L at SNADGATE
>Subject: Re: Netware Server Volume Reorganisation
>-----------------------------------------------------------------------------
>--
>Dianne -
>
>It appears not - I still have V1 manuals on CD, and couldn't find anything
>that looked relevant - another good reason to migrate to V2.
>
>I'm not sure how it would work for you, but when we went to V2, the cost was
>actually less than what we were paying for V1, due to the cost of the clients
>dropping from $5 to $2. I don't remember where the break even point was, but
>I seem to remember that it was less than 200 clients.
>
>Jerry Lawson
>jlawson AT thehartford DOT com
>
>
>______________________________ Forward Header
>__________________________________
>Subject: Re: Netware Server Volume Reorganisation
>Author: INTERNET.OWNERAD at SNADGATE
>Date: 5/5/97 12:37 AM
>
>
>I should have mentioned that we are running ADSM Server V1 for MVS.
>Does this option exist for V1?
>
>>----------
>>From: Jerry Lawson[SMTP:jlawson AT THEHARTFORD DOT COM]
>>Sent: Monday, 05 May, 1997 3:33PM
>>To: ADSM-L AT VM.MARIST DOT EDU
>>Subject: Netware Server Volume Reorganisation
>>
>>---------------------------- Forwarded with Changes
>>---------------------------
>>From: INTERNET.OWNERAD at SNADGATE
>>Date: 5/4/97 8:24PM
>>To: Jerry Lawson at ASUPO
>>*To: *ADSM-L at SNADGATE
>>Subject: Netware Server Volume Reorganisation
>>----------------------------------------------------------------------------
>>-
>>--
>>Dianne -
>>
>>There is also a rename filespace command that should do what you want to do.
>>
>>Jerry Lawson
>>jlawson AT thehartford DOT com
>>
>>
>>______________________________ Forward Header
>>__________________________________
>>Subject: Netware Server Volume Reorganisation
>>Author: INTERNET.OWNERAD at SNADGATE
>>Date: 5/4/97 8:24 PM
>>
>>
>>Our engineers are planning a reorganisation of the Netware server
>>volumes and I'm wondering about the impact on our ADSM backups.
>>The volume structure is changing (e.g.)
>>from : SYS to : SYS
>> SYS1 DPMT
>> COMMON
> > APPS
>>
>>The bulk of data in the current SYS1 volume will be moved to APPS.
>>
>>Is there a way of RENAMING a filespace (e.g. CORP\SYS1 to CORP\APPS)?
>>Otherwise, I think the entire APPS directory will be backed up during
>>the next incremental, as ADSM will treat all the files as new. Also,
>>the inactive versions of the files will not be
>>
>>My other problem is that we have 2 Netware servers which will be merging
>>and I'm trying to understand how we can deal with this. The two
>>servers, AUCK12 and ENGOPS, will be copied to a new server called ISS.
>>I know I can do a RENAME NODE, but if I do this, will it also rename the
>>filespaces? (i.e. If I rename AUCK12 to ISS, will the filespaces be
>>called ISS\SYS: or remain as AUCK12\SYS:)?
>>
>>Does anyone else have any experience with this sort of thing?
>>
>>
>>Dianne Sharp
>>Operations Analyst
>>ISS CUSTOMER SUPPORT
>>Ext 4208
>>
>
|
