Anonymous_User Absent Member.
Absent Member.
2621 views

Reinstallation of NW 6.5 on the Same server

Hi

I need to re-install NW 6.5 on the same server(upgraded from NW5.1) in a
10 server tree.My reason for this is that I need to convert all the
volumes( SYS included)which are traditional to NSS.The customer doesnt
have the budget to buy Portlock software.

The backup software I am using is Bexec 9.2.

Is the following plan viable:

1. Backup the server.
2. trustbar all the volumes.
3. Backup the DS using NWCONFIG (backup b4 HW upgrade)copy *.BAK to pc
4. Trash the server and install NW 6.5 (bexec also) into its own tree.
5. Restore all volumes using the backup software.
6. Ensure servername and ID are identical to the old config.copy DS
backup file to SYS:SYSTEM.
7. Reboot server
8. Remove DS off the server.
9. Run nwconfig/directory option/directory backup and restore
options/restore NDS after hardware upgrade.
10. Restore trustees with trustbar.

Are all the steps in the correct order.Did i miss anything ??? 😞
Or is there an easier way 🙂

Thanks
Minesh
Labels (2)
0 Likes
12 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

Why not use the VCU.NLM that comes with NetWare instead?


mineshp@webmail.co.za wrote:
> Hi
>
> I need to re-install NW 6.5 on the same server(upgraded from NW5.1) in a
> 10 server tree.My reason for this is that I need to convert all the
> volumes( SYS included)which are traditional to NSS.The customer doesnt
> have the budget to buy Portlock software.
>
> The backup software I am using is Bexec 9.2.
>
> Is the following plan viable:
>
> 1. Backup the server.
> 2. trustbar all the volumes.
> 3. Backup the DS using NWCONFIG (backup b4 HW upgrade)copy *.BAK to pc
> 4. Trash the server and install NW 6.5 (bexec also) into its own tree.
> 5. Restore all volumes using the backup software.
> 6. Ensure servername and ID are identical to the old config.copy DS
> backup file to SYS:SYSTEM.
> 7. Reboot server
> 8. Remove DS off the server.
> 9. Run nwconfig/directory option/directory backup and restore
> options/restore NDS after hardware upgrade.
> 10. Restore trustees with trustbar.
>
> Are all the steps in the correct order.Did i miss anything ??? 😞
> Or is there an easier way 🙂
>
> Thanks
> Minesh

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

Another thing to consider is the time involved. What is the time worth?
If you go as you suggest, it could take a very long time. With
Portlock, it would take relatively little time at all. Plus, you now
can image all of your servers if you want.


mineshp@webmail.co.za wrote:
> Hi
>
> I need to re-install NW 6.5 on the same server(upgraded from NW5.1) in a
> 10 server tree.My reason for this is that I need to convert all the
> volumes( SYS included)which are traditional to NSS.The customer doesnt
> have the budget to buy Portlock software.
>
> The backup software I am using is Bexec 9.2.
>
> Is the following plan viable:
>
> 1. Backup the server.
> 2. trustbar all the volumes.
> 3. Backup the DS using NWCONFIG (backup b4 HW upgrade)copy *.BAK to pc
> 4. Trash the server and install NW 6.5 (bexec also) into its own tree.
> 5. Restore all volumes using the backup software.
> 6. Ensure servername and ID are identical to the old config.copy DS
> backup file to SYS:SYSTEM.
> 7. Reboot server
> 8. Remove DS off the server.
> 9. Run nwconfig/directory option/directory backup and restore
> options/restore NDS after hardware upgrade.
> 10. Restore trustees with trustbar.
>
> Are all the steps in the correct order.Did i miss anything ??? 😞
> Or is there an easier way 🙂
>
> Thanks
> Minesh

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

Hi Duane

No free space to use VCU.I cant resize the partition.Yes I know Portlock
can do the job.I have had discussions with the customer and Portlock is a
definate NO NO.So is my plan OK. Can I go ahead

Thanks
Minesh

> Another thing to consider is the time involved. What is the time worth?
> If you go as you suggest, it could take a very long time. With
> Portlock, it would take relatively little time at all. Plus, you now
> can image all of your servers if you want.
>
>
> mineshp@webmail.co.za wrote:
> > Hi
> >
> > I need to re-install NW 6.5 on the same server(upgraded from NW5.1) in a
> > 10 server tree.My reason for this is that I need to convert all the
> > volumes( SYS included)which are traditional to NSS.The customer doesnt
> > have the budget to buy Portlock software.
> >
> > The backup software I am using is Bexec 9.2.
> >
> > Is the following plan viable:
> >
> > 1. Backup the server.
> > 2. trustbar all the volumes.
> > 3. Backup the DS using NWCONFIG (backup b4 HW upgrade)copy *.BAK to pc
> > 4. Trash the server and install NW 6.5 (bexec also) into its own tree.
> > 5. Restore all volumes using the backup software.
> > 6. Ensure servername and ID are identical to the old config.copy DS
> > backup file to SYS:SYSTEM.
> > 7. Reboot server
> > 8. Remove DS off the server.
> > 9. Run nwconfig/directory option/directory backup and restore
> > options/restore NDS after hardware upgrade.
> > 10. Restore trustees with trustbar.
> >
> > Are all the steps in the correct order.Did i miss anything ??? 😞
> > Or is there an easier way 🙂
> >
> > Thanks
> > Minesh


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

Thanks Duane

But Portlock is not an option.I have to go the long route.Are the
procedures below correct ???/
Thanks
Minesh

> Another thing to consider is the time involved. What is the time worth?
> If you go as you suggest, it could take a very long time. With
> Portlock, it would take relatively little time at all. Plus, you now
> can image all of your servers if you want.
>
>
> mineshp@webmail.co.za wrote:
> > Hi
> >
> > I need to re-install NW 6.5 on the same server(upgraded from NW5.1) in a
> > 10 server tree.My reason for this is that I need to convert all the
> > volumes( SYS included)which are traditional to NSS.The customer doesnt
> > have the budget to buy Portlock software.
> >
> > The backup software I am using is Bexec 9.2.
> >
> > Is the following plan viable:
> >
> > 1. Backup the server.
> > 2. trustbar all the volumes.
> > 3. Backup the DS using NWCONFIG (backup b4 HW upgrade)copy *.BAK to pc
> > 4. Trash the server and install NW 6.5 (bexec also) into its own tree.
> > 5. Restore all volumes using the backup software.
> > 6. Ensure servername and ID are identical to the old config.copy DS
> > backup file to SYS:SYSTEM.
> > 7. Reboot server
> > 8. Remove DS off the server.
> > 9. Run nwconfig/directory option/directory backup and restore
> > options/restore NDS after hardware upgrade.
> > 10. Restore trustees with trustbar.
> >
> > Are all the steps in the correct order.Did i miss anything ??? 😞
> > Or is there an easier way 🙂
> >
> > Thanks
> > Minesh


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

> No free space to use VCU.I cant resize the partition.Yes I know Portlock
> can do the job.I have had discussions with the customer and Portlock is a
> definate NO NO.So is my plan OK. Can I go ahead
>

I take it that you are not billing the customer for the time here -- I
think what Duane was getting to is that if you are billing the customer
for the time you take, Portlock might be cheaper for the customer. If,
on the other hand you are 'off the clock' then the customer is saving
money (at your expense in effort of course).


--
Barry Schnur
Novell Support Connection Volunteer Sysop
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

Here was my procedure that worked PERFECTLY for this very operation: Reload
same server reload with Netware 6.5 to remove traditional volumes and end up
with NSS volumes. It's pretty long, but you asked for it!!!

Get a backup of the server with new tapes

FORCE DECOMPRESSION OF COMPRESSED FILES - very important since NSS doesn't
support restoring compressed files.


Also - make sure that no master replicas are on this server. Assign another
server any Masters that are on this server until the server is reloaded or
else NDS will be bunged up. Do this well in advance to allow for
syncronization.



Plan for you volume and partitions before so you know how big to make them
now.



Trustee backup on all volumes



Verify previous night's backup of data files on old server before starting
procedure!!!!



Backup of NDPS printing via copying full NDPS folder while NDPS agents are
down



Backup of NDS via EMBOX - copy to laptop/PC



Reboot server after REMMING out everything not needed - just to freshen
things up.



Run dsrepair on Master Replica server - verify synchronizaton



Run Dsrepair locally on server to be reloaded.





PREPARE For Hardware Upgrade method



1) Make sure several machines are logged into server as ADMIN

2) Use "Save local NDS information before Hardware Upgrade" in NWCONFIG.
Copy resulting files to several local hard drives

3) When the database is locked, copy the sys:system\nici directory. Copy
files to several local hard drives



4) Nuke old server and reload Netware using temporary server name, IP and
tree and pre-migration server option

Make sure all patches are applied and that all configurations are
done as per a normal new server install



LOAD NEW SERVER Record temporary server name/tree/admin
password/context
Server Install - Pre-migration Patch to current level



Record IP Address and server name, Gateway, DNS servers, Network card
speed/duplex settings



Recreate other volumes if any with correct name spaces



**INETCFG - first time setup



**Set timesync configured sources ON

TimeSync Type and Configured Sources



**Set Parameters - or whatever is standard for you

Minimum Packet Receive Buffers = 1000 to 2000

Maximum Packet Receive Buffers = 10000

Minimum Directory Cache Buffers = 1500

Maximum Directory Cache Buffers = 10000

Minimum Service Processes = 100

Maximum Service Processes = 1000

Dirty Disk Cache Delay Time = 0.1

NLS Search Type = 1

maximum concurrent disk cache writes = 1500 - 3000

maximum concurrent directory cache writes = 300 - 500

directory cache allocation wait time = 0.1 sec

CLIENT FILE CACHING ENABLED =OFF

Level 2 oplocks enabled=off



**Copy new BTI.CFG into Sys:\system (this was for me and my Arcserve)




**Install programs: Toolbox, GWIP, PKIDIAG, STUFFKEY, Raidman, Ipsmon,
cron/crontab, Mcafee



**Set SLP discovery option to 4

set scope to whatever is appropriate for your environment under Server
Parameters, SLP



** - things to do BEFORE a reboot REBOOT NOW





5) Make sure multiple workstations are logged into TEMP server and tree

6) Copy the files from steps 2 & 3 to new server Sys:\TEMP folder

7) Rename new NICI folder and put copy of backup in Sys:\system\NICI

😎 Remove NDS from temporary server

9) SEARCH for config files with wrong ip address or name and change in
inetcfg, hosts, hostnames, autoexec Rename new server with correct server
name and IP addresses and restart so then NICI files copied in step 7 are in
effect.

10) Use "Restore local NDS information after Hardware Upgrade" in NWCONFIG -
Point to Sys:\Temp\

11) Restart the server and from ConsoleOne click on the Organization CA and
validate the certificates.

12) PKIDIAG - fix problems

13) Install other products (Backup software, Groupwise, antivirus, etc.)

14) Load Broker & Manager then unload and restore NDPS\RESDIR folder pieces
(psmdb.dat/psmdb.idx)



Run Unattened Full dsrepair after server has had time to boot and
synchronize



Check HOSTS file, HOSTNAME file and RESOLV.CFG



Verify Replica Type using iManager (change replicas back if they were
changed for the upgrade)



Check items in autoexec.ncf vs. OLD server to make sure you've got
everything covered



Verify time server type and settings: secondary, daylight savings time,
timesync server

(change time server types back if they were changed for the upgrade)



Verify NDS and Time synchronization



Boot load test - everything loads - NDPS stuff, BACKUP, GROUPWISE, etc



Get backup software running again for restore of DATA volumes

Data Restore on VOLUMES - Check name spaces on new server before restoring



Verify users can log in, printing works, drives mapping



Verify that users have rights to Groupwise Software Distribution Directory
and that they are not prompted to upgrade when they log in.



Setup backup jobs again for regular backups




<mineshp@webmail.co.za> wrote in message
news:N7VPf.8061$oh5.4324@prv-forum2.provo.novell.com...
> Thanks Duane
>
> But Portlock is not an option.I have to go the long route.Are the
> procedures below correct ???/
> Thanks
> Minesh
>
>> Another thing to consider is the time involved. What is the time worth?
>> If you go as you suggest, it could take a very long time. With
>> Portlock, it would take relatively little time at all. Plus, you now
>> can image all of your servers if you want.
>>
>>
>> mineshp@webmail.co.za wrote:
>> > Hi
>> >
>> > I need to re-install NW 6.5 on the same server(upgraded from NW5.1) in
>> > a
>> > 10 server tree.My reason for this is that I need to convert all the
>> > volumes( SYS included)which are traditional to NSS.The customer doesnt
>> > have the budget to buy Portlock software.
>> >
>> > The backup software I am using is Bexec 9.2.
>> >
>> > Is the following plan viable:
>> >
>> > 1. Backup the server.
>> > 2. trustbar all the volumes.
>> > 3. Backup the DS using NWCONFIG (backup b4 HW upgrade)copy *.BAK to pc
>> > 4. Trash the server and install NW 6.5 (bexec also) into its own tree.
>> > 5. Restore all volumes using the backup software.
>> > 6. Ensure servername and ID are identical to the old config.copy DS
>> > backup file to SYS:SYSTEM.
>> > 7. Reboot server
>> > 8. Remove DS off the server.
>> > 9. Run nwconfig/directory option/directory backup and restore
>> > options/restore NDS after hardware upgrade.
>> > 10. Restore trustees with trustbar.
>> >
>> > Are all the steps in the correct order.Did i miss anything ??? 😞
>> > Or is there an easier way 🙂
>> >
>> > Thanks
>> > Minesh

>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server


nice write up, thanks for the effort.




--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

A small point, but NSS does support restores of compressed files, provided
compression is enabled on the NSS volume. I've got a small NSS volume on
one of the servers here with compression enabled purely so that I can get
files back from older tapes.

Cheers Dave


--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

True, but out of the box NSS volumes don't have compression enabled and
anyone not knowing might try to restore using files from a compressed
backup. Should have mentioned it though for thoroughness.


John
"Dave Parkes" <Dave@Norgren.co.uk> wrote in message
news:xn0ekdyh41hyw8h014@support-forums.novell.com...
>A small point, but NSS does support restores of compressed files, provided
>compression is enabled on the NSS volume. I've got a small NSS volume on
>one of the servers here with compression enabled purely so that I can get
>files back from older tapes.
>
> Cheers Dave
>
>
> --
>
> Dave Parkes [NSCS]
> Occasionally resident at http://support-forums.novell.com/



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

True, it isn't on by default, but I didn't think it was with TFS either ?

Cheers Dave


--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server


"Dave Parkes" <Dave@Norgren.co.uk> wrote in message
news:xn0ekl4c17ekfag036@support-forums.novell.com...
> True, it isn't on by default, but I didn't think it was with TFS either ?
>
> Cheers Dave

Compression is on by default on the traditional file system, unless the
volume is specifically created without compression. It cannot be fully
turned off without backup of the volume, blow away, then restore. However,
one can change the properties of the volume to add the Dc (don't compress)
attribute to all files and directories starting at root. This workaround
allows adding compression to specific areas of the volume if later desired.

Jim Cason, CNI, CNE


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reinstallation of NW 6.5 on the Same server

OK, thanks, I've been working with NSS too long obviously 🙂

Cheers Dave


--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
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.