280 likes | 382 Views
Netware 6 Upgrade tips . James Dore, New College IT Officer James.dore@new.ox.ac.uk http://www.new.ox.ac.uk/it/netware. What’s new in Netware 6?. File system improvements - NSS V3 Native File Access Web and Portal Services. NSS V3. Volume mount times are independent of Volume size.
E N D
Netware 6 Upgrade tips • James Dore, New College IT Officer • James.dore@new.ox.ac.uk • http://www.new.ox.ac.uk/it/netware
What’s new in Netware 6? • File system improvements - NSS V3 • Native File Access • Web and Portal Services
NSS V3 • Volume mount times are independent of Volume size. • Much lower memory requirements than for Traditional Netware volumes. • Disk Partitions are put into one or more NSS Pools (FDISK will think this is free space) • Volumes are created from the free space in those pools • Disk quotas now supported! • Compression, Shredding also supported. • Soft limits on Volume size supported
NSS Cont… • Volumes can temporarily take free space not yet used • Volumes can expand to use space not yet used by other volumes in the pool • Volumes can be assigned more space than exists in underlying pool • E.g: 10 Gb pool on physical disk. Each Volume can be assigned 10Gb, and usage gets dynamically assigned. • Very large volumes – up to 8Tb • Very large individual files – up to 8Tb
Journaling File system • Changes logged to disk • Intermediate access via that log. • Changes committed during free time
Distributed File system • Import a NetWare volume from elsewhere into the file system, • Appears as a subfolder in that file system – like NFS • The imported volume can be any Netware kind – Trad, NSS V2 or V3. • However, not yet supported by Client32! Oops!
Native File Access • Native NDS login for multiplatform environments • Windows (via CIFS/SMB) • Macintosh (via AppleTalk/AFP) • UNIX flavours • Solaris, Tru64, HP/UX, AIX, Linux etc.
Web and Portal services • (e.g. iFolder) • How many web servers?! • Four! • Enterprise webserver (Novonyx) • HTTPStk • Two instances of Apache
Enterprise web server • Port 80 and 443 • Home Page and WebDAV • Regular web server • Not as quick as Apache, but offers more ‘Netware aware’ services for Apps such as GroupWise, and Portal Services
HTTPStk. • Ports 81, 8008, 8009 (secure) 631 and 443 • Remote Manager console (Web management of Netware server) • NDPS and IPP
Apache • Ports 2200, 2211, 51080, 51443 • App managers • Websearch • Webaccess
Apache (again) • 52080 52443 (secure) • iFolder access • Install them all, then switch them off if you don’t need them!
The beginning • Check your NDS. • NDS Health Check: TID 10060600 • http://support.novell.com/cgi-bin/search/searchtid.cgi?/10060600.htm
Upgrade your NDS • Netware 5.0 and DS7.x? Get to NDS 8 first • there is a glitch with upgrading NDS 7.x to 8.6 as supplied with Netware 6. • DS Versions: • Netware 5.0 – V7 current 7.51 (sp6a) • Netware 5.1 – V8.0 – Currently 8.78 • eDirectory – V8.5 (aka DS 85) • Netware 6 – v8.6 • Type MODULES DS at your server console to find your version number.
DS Names • Pre DS8: Record Manager • DS 8.0 -> 8.35: SKADS • DS 8.36 -> DS 8.78: Fusion • eDirectory/DS 85/NDS 8.5 : Tao • DS 8.6: Dove
Apply latest service packs • You can find them all on ftp://micros.oucs.ox.ac.uk/netware/updates
Backup! • Data • Use your favourite backup method – Tape, HFS, etc. • Trustee / File system rights • Use tbackup.exe at root of each volume to write trustee rights to a batch file. They can then be replaced if the worst happens. TBACKUP is available from micros.oucs • Alternatively, TRUSTBAR.NLM can be used, which is found on the Netware 6 Install cd. • TRUSTBAR <volname> -B • See TID 10066145
Backup your NDS • DSREPAIR –RC • Creates backup of NDS • SYS:SYSTEM/DSREPAIR.DIB for NDS 6.x and 7.x • SYS:SYSTEM\DSR_DIB\ for NDS 8 and later • See TID 10063534
Prep your source server • Your server needs a Master or Read/Write replica of NDS • Kick off Active users. • Comment out applications in AUTOEXEC.NCF e.g. Printing, BackupExec, etc • Reboot • Load DSREPAIR.NLM • Check Timesync is happy • (optional) Extend the NDS Schema from the NW6 CD • Health Check your NDS again (see TID 10060600 as before)
Upgradestrategies • In place • Accelerated • Regular upgrade • As indoor sport
In Place upgrade • Upgrades NDS and preserves your info • Preserves app and user files • Preserves trustee rights • Does not upgrade SYS: Volume to NSS • Quick • ! New Products can overwrite older versions • ! Destructive process – NDS is modified so have backups. • Uses NWDeploy, which is on the root of the Netware 6 CD. • Runs from a Windows workstation
Acceleratedupgrade • Requires two servers (one to hold the CD only) and is coordinated by NWDeploy running on a Windows Workstation. • Bare-bones upgrade • No Licenses installed • No network products installed, e.g. Native File Access or iFolder. • Precede an Accelerated upgrade with NWDeploy to prep the NDS Tree • Follow an Accelerated Upgrade with NWDeploy to install optional components.
Over-the-wire • Uses Migration Wizard (migwiz6.exe) • Requires a Windows Workstation to coordinate the procedure. • Pours contents of old server to new hardware. • New machine behaves as if it were the old one – IP, NDS values etc. • Preserves NDS and upgrades it. • Preserves user data • Server Applications may need reinstalling.
Upgrade Wizard issues! • The Windows software is not too robust - Java app • It’s fussy about the Workstation’s video as well • IP Communications can be iffy – IPX is preferable. • NDS on the source server is not left intact – removed and hidden (but it can be recovered) • You need to physically move the NICI keys by sneakernet.
Upgrade wizard bonus items: • It will upgrade the following systems: • Netware 4.x to any later version • Netware 5.0 to 5.0 (hardware move only) or later versions • Netware 5.1 to 5.1 or 6.0 • Netware 6.0 to 6.0
NDS Migration As Indoor Sport • A Tale of three servers… • Server A, to be replaced. • Server B, the new hardware. • Server C, a placeholder for the NDS. • Servers A & C are in the target tree already and have been prepared.
Cut to the chase…. • On server B, Install NW 6 into a Dummy Tree, using NWDeploy (no applications, basic setup). • Remove NDS from it. • Reinstall NDS into the same NDS Container as source server A (to server A or C) • Extend the Schema on your actual NDS tree, and let the dust settle. • Copy User files from A to B, keeping the list of Trustee rights from A • (i.e. use TBACKUP.exe to backup the trustee rights to a batch file, and apply them to server b.) • The schema is now extended for NW 6 to work – A and C hold it, B is not yet present. • Make server C the Master replica. • Go for coffee, which lets you and NDS settle down.
We continue… • Down Server A. put a sign on it not to be put on the network as is (else Very Bad Things Happen) • We are finished with Server A. It’s off the air but intact. • Start Server B, install NDS on it into existing tree • Use context AND name of server A • Edit autoexec.ncf and etc/hosts, and run INETCFG to use IP/IPX details of server A • Edit Apps for new IP/IPX details and server name • Reapply trustee rights from server A’s TBACKUP batch file • Optionally, make B master NDS replica, and remove C. • Retire gracefully to hostelry for liquid refreshment.