1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. NETWARE 6-DOCUMENTATION
  6. Manual

Novell NETWARE 6-DOCUMENTATION Manual

Hide thumbs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
Table of Contents

Advertisement

Quick Links

Novell
NetWare
6
®
w w w . n o v e l l . c o m
6 . 0
R E A D M E

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NETWARE 6-DOCUMENTATION and is the answer not in the manual?

Questions and answers

Related Manuals for Novell NETWARE 6-DOCUMENTATION

Summary of Contents for Novell NETWARE 6-DOCUMENTATION

  • Page 1 Novell NetWare ® w w w . n o v e l l . c o m 6 . 0 R E A D M E...
  • Page 2 Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
  • Page 3 Novell Directory Services and NDS are registered trademarks of Novell, Inc. in the United States and other countries. Novell Distributed Print Services is a trademark and NDPS is a registered trademark of Novell, Inc. in the United States and other countries.

  • Page 5: Table Of Contents

    DNS/DHCP iManage 1.0 and iMonitor 1.5 for Novell eDirectory 8.6 iManage 1.0 ..........27 iMonitor 1.5.
  • Page 6 18 Novell Compatibility Mode Driver 19 Novell eDirectory 8.6 for NetWare 20 Novell GroupWise 21 Novell iFolder 22 Novell International Cryptographic Infrastructure (NICI) 23 Novell Modular Authentication Service (NMAS) 24 Novell Native File Access Protocols General Issues ......... . 75 Macintosh / AFP Issues .

  • Page 7: Netware 6 Readme

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. NetWare 6 Readme...
  • Page 8 NetWare 6 Readme...

  • Page 9: General Information

    The NetWare 6 package consists of the following: Operating System CD Client CD Novell Client 4.81 for Windows* NT*/2000 Novell Client 3.31 for Windows 95/98 NMAS Client 2.0 NICI Client 1.5.7 for Windows NICI Client 2.0.2 for Windows Novell NetDrive Client 4.0 Novell ConsoleOne 1.3 with snap-ins...
  • Page 10 Scripting products (NSN, Perl, and UCS) All other NetWare 6 components included with this release function in an MP environment. Compatibility with Other Novell Products The following Novell products are compatible with NetWare 6: Account Management 2.1 for Windows 2000 DirXML 1.01 ®...
  • Page 11 Novell Portal Services 1.0 Novell Single Sign-on 2.1 If you install Novell Single Sign-on to a NetWare 6 server that is not an SD Key Server and you select No when prompted to make the server an SD Key Server, you may see messages indicating that Novell Single Sign- on did not successfully install.
  • Page 12 Client DOS Utilities Many DOS utilities have been removed from NetWare 6. The following utilities are still included for your convenience, but they are not supported: CAPTURE FILER LOGIN LOGOUT NCOPY NDIR NetWare Administrator NLIST NPRINTER RIGHTS International Issues Euro Character. There are several places throughout Netware 6 where the euro character is displayed as its hex value “[20AC]”.

  • Page 13: Installation And Upgrade

    Installation and Upgrade This chapter contains the following subsections: “Before the Installation or Upgrade” on page 13 “During the Installation or Upgrade” on page 16 “After the Installation or Upgrade” on page 18 You should also review the other sections of this Readme for additional installation and upgrade issues.
  • Page 14 Prepare a Server with NDS 7 and NSS step in NetWare Deployment Manager. For this reason, complete this step just before you upgrade to NetWare 6. Update NetWare 5 Servers Running NMAS before Installing Novell Native File Access Protocols ®...
  • Page 15 Deployment Manager and specifically complete Step 3: Prepare for NDS eDirectory 8.6. This step identifies and updates a server on the network that holds the Master or Read/Write replica of the Root of the tree. NetWare Deployment Manager (NWDEPLOY.EXE) runs on a Windows workstation and is located on the NetWare Operating System CD.

  • Page 16: During The Installation Or Upgrade

    During the Installation or Upgrade Copying and Overwriting Existing Files Because all the components of NetWare 6 have been tested as a whole, you should select Overwrite on all files that report a new date conflict during an upgrade. Installing from a Bootable CD If your server supports a bootable CD-ROM and you want to boot to the NetWare Operating System CD, make sure that the machine boot order specifies that the CD boots before the hard drive.
  • Page 17 DN attribute in the Security.KAP.WO container is a NetWare 6 server, then a NetWare 5.1 server installation into the tree will fail with this error. This error happens during the final file copy and shows up as part of the Novell Certificate Server installation.

  • Page 18: After The Installation Or Upgrade

    Search, iManage, NetWare Web Access, and Novell NetStorage. If you plan to install any of these products after the upgrade, make sure that you install the Apache Web server first. After the Installation or Upgrade Missing Device Drivers The server installation program copies to a startup directory (C:\NWSERVER) only drivers (such as HAMs, CDMs and PSMs) for devices that were auto-detected during the installation process.
  • Page 19 To maintain backup and restore services on NetWare 6 and your network, you must install the patch. The patch will supersede the SMS modules installed by default during the NetWare 6 installation. For more information, see the Readme included with the patch. Agent Installation for GroupWise 6 Replaces LDAP Files Needed by iFolder ®...
  • Page 20 NetWare 6 Readme...

  • Page 21: Consoleone 1.3

    A Client CD containing the NICI client for Microsoft* Windows operating systems is included with NetWare 6. NICI clients for Solaris* and Linux* can be found on the Novell software download page (http://www.novell.com/ download). To install the NICI client from the Client CD, insert the CD. An autorun application begins.
  • Page 22 For more information on this issue, refer to Solution #2943528 (http:// support.novell.com). Administering Volumes and Files Using Novell Client for Windows 95/ There is a defect in earlier versions of Novell Client for Windows 95/98 that causes problems when you try to administer volumes and files in ConsoleOne.
  • Page 23 Option Setting File Cache Level Change from 3 to 0. File Write Through Change from Off to On. True Commit Change from Off to On. Click OK. Support for the Hong Kong Supplementary Character Set This release of ConsoleOne does not support the Hong Kong Supplementary Character Set (HKSCS).
  • Page 24 NetWare 6 Readme...

  • Page 25: Dns/Dhcp

    Special Instructions For improved performance, configure the DNS/DHCP scope settings before you start using the Novell iManage browser-based DNS/DHCP management utility. The recommended settings for the Novell iManage browser-based DNS/ DHCP management utility are as follows:...
  • Page 26 DHCP server, this reference is automatically replaced by a reference to the default DHCP server that you specify. The Novell DNS and DHCP servers are based on ISC BIND Version 4.9.6 and ISC DHCP Version 2. NetWare 6 Readme...

  • Page 27: Imanage 1.0 And Imonitor 1.5 For Novell Edirectory 8.6

    English, you can now create and view objects containing European characters. Using Internet Explorer 5.5, do the following: Click Tools > Internet Options. Click Language > Add. Select a European language (such as Portuguese or German) and then click OK. iManage 1.0 and iMonitor 1.5 for Novell eDirectory 8.6...
  • Page 28 Setting Up Encoding for Foreign Languages If you are experiencing problems with correct character display in iManage, you should verify that your browser's language and character set encoding are configured properly. To enable iManage to display information in the language you expect, you need to Set your browser's language preference to the appropriate language Select the encoding that supports your browser's language...
  • Page 29 You can create a role without any tasks and then modify the role to include tasks. However, we recommend instead that you re-install the product packages in order to re-create the removed roles. Use the Install Package task in iManage to reinstall the product packages. iManage 1.0 and iMonitor 1.5 for Novell eDirectory 8.6...
  • Page 30 Modifying the iManage Installation Path during a NetWare 6 Custom Installation You should not modify the iManage installation path during the NetWare custom installation unless the container you specify in the installation field already exists. If you do specify a container that does not exist, you will receive -601 (No Such Entry) errors on the following files: .../BASE/EDIR.XML .../DNSDHCP/DNSDHCP.XML...

  • Page 31: Imonitor 1.5

    When using iMonitor to browse an eDirectory tree for objects, an object with extended characters in the name might not hyperlink to the object properties correctly. This problem does not happen with any objects that contain double- byte characters. iManage 1.0 and iMonitor 1.5 for Novell eDirectory 8.6...
  • Page 32 NetWare 6 Readme...

  • Page 33: Iprint/Ndps

    Novell Gateway, the Novell Gateway (NDPSGW.NLM) is used. When you use NetWare Administrator to create a Printer object and select the Novell Gateway, the gateway comprised of PH.NLM and NDPDS.NLM is used. This is the only version of the gateway that supports RP protocol and local ports.
  • Page 34 Running iPrint Map Designer To have full functionality of the iPrint Map Designer, IPPSRVR.NLM must be loaded before starting iPrint Map Designer. Changing Printer Security Levels If you change the printer agent security level to high and do not check the Requires Security check box on the IPP Support page of the printer’s Client Support Page in iManage, you will receive the following error: Error message: iPrint Client - "The request requires user...
  • Page 35 Remount the volume with TTS enabled by entering mount NDPS_Manager_host_volume_name iPrint Client Install Page Has No Link When using a map generated by the iPrint Map Designer, if users click on a printer from a workstation that does not have the iPrint client installed, they might be redirected to an iPrint client install page that does not have the client install link.
  • Page 36 NetWare 6 Readme...

  • Page 37: Ipx Dependencies

    IPX Dependencies ® If you select TCP/IP as your only protocol during the NetWare 6 installation, IPX/SPX will no longer be available. If you have problems loading IPX/SPX-dependent NLM programs, add the following line after the Server Name in the AUTOEXEC.NCF file: serverID XXXXXXXX Replace XXXXXXXX with the internal IPX address you want to assign to...
  • Page 38 NetWare 6 Readme...

  • Page 39: Netware Enterprise Web Server

    Security settings must allow ActiveX Controls to be downloaded and run. When the following message appears, accept the module to allow it to run: Novell DAVICONS.OCX Signed ActiveX Controls Being Downloaded If your Web folders still do not display the icons, you must repair Internet Explorer 5 by doing the following: From your desktop, click Start >...
  • Page 40 Click Microsoft Internet Explorer 5 > Change/Remove > Repair Internet Explorer. Restart your system if required. INDEX.HTML Renamed When upgrading to NetWare 6 from an earlier version of NetWare, the file INDEX.HTML in the document root of the Enterprise Web Server (volume:\NOVONYX\SUITESPOT\DOCS) might be renamed to INDEX_ENTERPRISE.HTML.

  • Page 41: Netware Ftp Server

    NetWare FTP Server Intruder Detection To disable intruder detection, both intruder detection parameters (INTRUDER_HOST_ ATTEMPTS and INTRUDER_USER_ATTEMPTS) must be set to zero (0). To enable intruder detection, both intruder detection parameters (INTRUDER_HOST_ ATTEMPTS and INTRUDER_USER_ATTEMPTS) must be set to a value greater than zero (0).
  • Page 42 NetWare 6 Readme...

  • Page 43: Netware Migration Wizard 6

    Migration Wizard 6 installation. Once Migration Wizard is installed, you can also view the Readme before you launch the wizard by clicking Start > Programs > Novell > NetWare Migration Wizard > NetWare Migration Wizard Readme. Migrating to NetWare 6 NSS Volumes...
  • Page 44 NetWare 6 Readme...

  • Page 45: Netware Webaccess

    NetWare WebAccess is based on Novell Portal Services technology. Therefore, the limitation of not being able to run two instances of Novell Portal Services on the same server also applies when attempting to run NetWare WebAccess and Novell Portal Services on the same server.
  • Page 46 NetWare 6 Readme...

  • Page 47: Netware Web Manager

    NetWare Web Manager Upgrading Products Accessible through NetWare Web Manager If you are upgrading products accessible through NetWare Web Manager, new configuration files will be written out and the old configuration files will be backed up in their current location. A “_BKddd”...
  • Page 48 NetWare 6 Readme...

  • Page 49: Netware Web Search Server

    NetWare Web Search Server Web Search and Web Server Interaction The NetWare Web Search installation program automatically detects and registers itself with both the Apache and Enterprise Web servers if they are installed on your server. However, the NetWare Web Search Manager (AdminServlet) will be registered only with the Apache Web server, which is the Web server used by all NetWare Web administration utilities (such as NetWare Web Manager and NetWare Remote Manager).
  • Page 50 To fix this problem so that all available indexes display on the search page, either use the templates that ship with the newer Web Search (located in the \NSearch\Templates\Samples directory) or make the following changes to the SEARCHTEMPLATE.HTML file that you are currently using as your search page: 1.

  • Page 51: Novell Advanced Audit Service

    NAAS is not supported a mixed network environment containing NDS 6.x, 7.x, and 8.x. NAAS enables auditing only for NetWare servers that are running in pure NDS (Novell eDirectory ) 8.x networks. It does not audit NetWare servers running NDS 8.x even if they are part of a mixed network running NDS versions earlier than NDS 8.x.
  • Page 52 The default configuration utility can make a user Auditor for only one partition. To make the same user an Auditor for more than one partition, do the following: Manually configure NAAS. Grant the auditor Read and Compare rights to the LDAP Server attribute for the partition containing the User object.
  • Page 53 FSSHIM.NLM NSSSHIM.NLM DSSHIM.NLM eDirectory Auditing Auditing is not enabled for the following events in Novell eDirectory: DSE ADD MEMBER DSE DELETE MEMBER If the NetWare server hosts two partitions and the server partition is a child partition of the other, only the server partition is audited.
  • Page 54 NetWare 6 Readme...

  • Page 55: Novell Certificate Server

    These error messages will occur only once on the first object access. You will typically not have LDAP SDK in your ConsoleOne distribution if you obtained ConsoleOne directly from the Novell Web site. You should use the version of ConsoleOne provided with NetWare 6. The ConsoleOne shell is located on the Client CD at \CONSOLEONE\C1.EXE and the snap-ins are...
  • Page 56 Browser Support You must use the Internet Explorer 5 or later or the Netscape Navigator 4 or later browser to use the certificates generated by Novell Certificate Server for SSL or LDAP connections. Older browsers are not supported. Removing a Server from NDS ®...

  • Page 57: Novell Client For Windows

    Novell Client for Windows ® See the Novell Client Readme (http://www.novell.com/documentation/lg/ noclienu/index.html) for issues related to the Novell Client for Windows 95/ 98 and Novell Client for Windows NT/2000. Novell Client for Windows...
  • Page 58 NetWare 6 Readme...

  • Page 59: Novell Cluster Services

    Shared Cluster Volumes Disabled in NetWare Deployment Manager Shared volumes are disabled after you complete the Prepare a Novell Cluster for Upgrade step in NetWare Deployment Manager. Once the upgrade to NetWare 6 is complete, the shared volumes are re-enabled.

  • Page 60: Other Issues

    NSS volume corruption occurs if all of the following conditions exist on your system: The Prepare a Novell Cluster for Upgrade option in the Deployment Manager was run and completed. At least one of the NetWare 5 servers in the cluster was upgraded to NetWare 6.
  • Page 61 If you are using NetWare Remote Manager to create NSS pools and volumes to use in your cluster, do not check the Prepare Volume for Use by Novell Cluster Services check box. This feature does not work and will not correctly cluster enable your newly created pool or volume.
  • Page 62 NetWare 6 Readme...

  • Page 63: Novell Compatibility Mode Driver

    Novell Compatibility Mode Driver There is no control on the Designated Router Election process. To make any migration agent a Designated Router, use INETCFG to assign it the highest priority IP Address. Novell Compatibility Mode Driver...
  • Page 64 NetWare 6 Readme...

  • Page 65: Novell Edirectory 8.6 For Netware

    For information on preparing an existing tree for a NetWare 6 installation, see "Updating the eDirectory Schema for NetWare" in Chapter 1, "Installing and Upgrading Novell eDirectory," of the Novell eDirectory Administration Guide. You can also use NetWare Deployment Manager to prepare your tree for installation.
  • Page 66 Additional Readme Information For information on additional eDirectory issues for this release, see #10063534 (http://support.novell.com) in the Novell Support Connection Knowledgebase. NetWare 6 Readme...

  • Page 67: Novell Groupwise

    If NetWare 6 is installed on a system where GroupWise 5.5 Enhancement Pack WebAccess has already been installed, the NetWare 6 installation ® program changes WebAccess from using the Novell Servlet Gateway to using the Tomcat Servlet Gateway. Your existing WebAccess software is not designed to work with Tomcat.
  • Page 68 NetWare 6 Readme...

  • Page 69: Novell Ifolder

    To fix this, complete one of the following procedures for each iFolder workstation. Modify Workstation Permissions Open Explorer and click Program Files > Novell > iFolder. Right-click the iFolder folder and then click Properties > Security. Make sure the user has Full Control permissions.
  • Page 70 Apply the iFolder Patch Go to the Novell Support Web site (http://support.novell.com) and click Patches and Files. Enter IFLDRCLA.EXE The A is a variable and will change as the iFolder client is updated. Double-click IFLDRCLA.EXE to begin the download process.

  • Page 71: Novell International Cryptographic Infrastructure (Nici)

    Microsoft Windows operating systems. NICI clients for Solaris and Linux can ® be found on the Novell software download page (http://www.novell.com/ download). To install the NICI client from the Client CD, insert the CD. An autorun application begins. Select the NICI client from the list. Novell International Cryptographic Infrastructure (NICI)
  • Page 72 NetWare 6 Readme...

  • Page 73: Novell Modular Authentication Service (Nmas)

    Update NetWare 5 Servers Running NMAS before Installing Novell Native File Access Protocols Before installing Novell Native File Access Protocols (as part of the NetWare 6 installation or otherwise), all NetWare 5 servers (in the tree) running NMAS must be updated to NMAS 2.0.1, NICI 2.0.1, and ConsoleOne 1.3.
  • Page 74 Configure the BorderManager services to use the Login Policy Object. Refer to the Border Manager documentation (http://www.novell.com/ documentation/) for details. Run the NMAS installation from the server-side GUI. Reinstall any NMAS Methods and re-create any NMAS login sequences. Simple Password and Force Password Change The Simple Password method is used for various authentication services in NetWare 6.

  • Page 75: Novell Native File Access Protocols

    General Issues Update NetWare 5 Servers Running NMAS before Installing Novell Native File Access Protocols Before installing Novell Native File Access Protocols (as part of the NetWare 6 installation or otherwise), all NetWare 5 servers (in the tree) running NMAS must be updated to NMAS 2.0.1, NICI 2.0.1, and ConsoleOne...
  • Page 76 Uninstalling the Software To remove the software, complete the following steps on each server running Novell Native File Access Protocol software. Run Native File Access for Macintosh* (AFP) Uninstall using NWCONFIG or the GUI Uninstall. Reboot the server or unload the AFPTCP.NLM (AFPSTOP.NCF).
  • Page 77 ConsoleOne 1.2d1: NMAS PutLoginConfig -1460 (NICI_E_NOT_FOUND error) This error could be caused by either of the following: NICI Client is not installed. You must install the client. NICI Partition key is missing. You must reinstall NetWare. Novell Native File Access Protocols...

  • Page 78: Macintosh / Afp Issues

    AppleTalk Not Supported as a Transport Protocol The legacy AppleTalk* protocol stack is not supported as a transport protocol in this version of Novell Native File Access Protocols for Macintosh. AppleTalk migration is targeted for a subsequent release. Older Mac applications that have unique dependencies upon AppleTalk as a transport protocol must be updated to a version that is known to work over TCP/IP.
  • Page 79 AFPTCP will have no effect. There is no need to unload WSPDSI manually. AFPTCP.NLM loads it automatically on startup and AFPSTOP.NCF does not unload it. It remains loaded. Under normal use, you should not see this warning. Novell Native File Access Protocols...

  • Page 80: Windows / Cifs Issues

    Volume ID You might get pervasive errors in a clustered AFP environment when the volume ID is set to higher than 32. To eliminate these errors, use ConsoleOne to edit the cluster AFP/TCP volume resource and change the volume ID to 32 or lower.
  • Page 81 Network Neighborhood. This can happen if you have a domain that contains only Windows 95/98 and no NT/2000/XP servers or clients. To correct this problem, enter the server name or IP address in Find Computer. Novell Native File Access Protocols...

  • Page 82: Unix / Nfs Issues

    MS Paint "Out of Memory" Error CIFS users might occasionally see an Out of Memory error when using MS Paint on a Windows NT workstation. This error message is incorrect and no processes are out of memory. The error message will disappear if the data file is first saved to local storage and then copied to the remote storage directory.
  • Page 83 Refresh to display its data. When managing the NFS server through ConsoleOne, if you try to export a volume without logging in to the Novell eDirectory tree, the following message displays erroneously: Config file is open. To export a volume, log in to the Novell eDirectory tree.
  • Page 84 Traditional volumes can be mounted only using NFS version 2. Even though showmount shows the volumes as exported, they are not mountable using NFS version 3. You need to explicitly mount the exported traditional volumes specifying the mount version as 2. If a Windows workstation user who has write permission to a file created in a mounted volume by a UNIX user attempts to modify the file, the ownership of the file will change from the UNIX user to the Windows...

  • Page 85: Novell Netdrive

    Novell NetDrive NetDrive supports HTTPS for WebDAV only on Windows NT 4.0 and Windows 2000 workstations. If your NetDrive client is behind a firewall regulated by a BorderManager server that is configured for FTP proxy and authentication, NetDrive cannot map a network drive via FTP to any servers that reside outside the firewall.
  • Page 86 NetWare 6 Readme...

  • Page 87: Novell Netstorage

    Novell NetStorage Changing iFolder IP Address after NetStorage Installation If you change the iFolder server IP address, DNS name, or port number after NetStorage has been installed, you must either reinstall NetStorage or edit the XSYNCNSP\IFOLDER SERVER registry setting to reflect the change.
  • Page 88 Internet Explorer Unable to Open Some Web Folders If you use Microsoft Web Folders with NetStorage to create a new folder, you might not be able to open that folder using Internet Explorer. Hosts File Not Usable by NetStorage NetStorage cannot use the SYS:\ETC\HOSTS file to resolve DNS names. If you have applications that can use DNS names (such as iFolder), your DNS names must be registered with a valid DNS server which is identified in the SYS:\ETC\RESOLVE.CFG file.

  • Page 89: Novell Storage Services

    Novell Storage Services Previous NSS Volumes Not Automatically Upgraded Previous NSS volumes are not automatically upgraded during the NetWare 6 installation process. After you install NetWare and reboot the server, you can upgrade previous NSS volumes to the current NSS volume layout.
  • Page 90 After you upgrade the first server in a cluster, the shared NSS volumes might appear as free space in a traditional partition on the remaining NetWare 5 servers. Creating a volume in this space will corrupt the NSS volumes. For more information, see Chapter 17, “Novell Cluster Services,” on page NetWare 6 Readme...

  • Page 91: Novell Tcp/Ip

    Novell TCP/IP Missing INETCFG Information If any information is missing from INETCFG after a new installation, it is because no information was uploaded to the TCPIP.CFG file. Similarly, if INETCFG information is missing or you get configuration error messages after an upgrade, it is because no new information was uploaded to the TCPIP.CFG file and some entries have become invalid.
  • Page 92 Load Balancing Load balancing might not work when all the clients’ IP address are mapped to a single server NIC and all the clients start data transfer simultaneously. Multihoming might not work in some cases where the hosts are supernetted. Viewing Bindings You can discover and load drivers using NWCONFIG and subsequently bind the boards to IP addresses through INETCFG.

  • Page 93: Pervasive.sql

    Pervasive.SQL Pervasive.SQL 2000 Database Licenses A permanent two-user license is installed during the NetWare 6 installation process. If you are upgrading an existing NetWare server, an unlimited license that will expire 90 days after installation is also installed. The permanent two-user license is intended for use by the NetWare operating system.
  • Page 94 Known Issues So that Pervasive can update known issue reports periodically between releases, all Known Issues are now published in the Pervasive Knowledge Base (http://support.pervasive.com/eSupport/). Search on "Pervasive.SQL 2000 Service Pack 3 known issues". You can also see a static list of known issues, including links to the associated Knowledge Base articles, at their Fixed Defects and Known Issues Web page (http://www.pervasive.com/support/updates/psql2kfixed.asp).

  • Page 95: Scripting Products

    ScriptEase (SE) is not installed as part of NetWare 6. If the system is upgraded from NetWare 5.1 to NetWare 6, SE will be available because it was part of the NetWare 5.1 system. Note that Novell will not provide customer support for SE in a NetWare 6 environment.
  • Page 96 Novell Script Pages ® Novell Script Pages (NSP) prevents any NSP page from being uploaded and executed without the execute bit set on the NSP file itself or on the parent directory. To mark an NSP file or directory with the execute bit, do the following: ®...

  • Page 97: Storage Management Services (Sms)

    Backup and Restore Issues Update SMS Components A new release of Storage Management Services (SMS) is available at the Novell Support Web site (http://support.novell.com). This release contains important fixes to the SMS components delivered with NetWare 6. The fixes ensure compatibility between earlier versions of NetWare and the NetWare 6 SMS modules.

  • Page 98: Client Issues

    Exclude/Include Options for Workstation Restore When Exclude/Include options are set for a workstation restore, only the selected data sets are restored. The log file and the status window of the session reports incorrect status. All the data sets are reported as restored, whereas only the data sets matching the specified options are actually restored.

  • Page 99: Other Issues

    If you need to assign a security policy to a group, do the following: Return to the Administrative Tools window and click Local Security Policies > Local Policies > User Rights Assignment. The list of policies and the local and effective settings are displayed. Double-click Act As Part of the Operating System Security Policy to display the Local Security Policy Setting dialog box.
  • Page 100 100 NetWare 6 Readme...

  • Page 101: Third-Party Adapters, Drivers, And Applications

    Although these drivers might work, they have been included only for use in cases where laptop servers are needed for demonstration purposes. They should be considered not supported by Novell. See the Readme in the UNSUPDRV directory for details. Third-Party Adapters, Drivers, and Applications 101...
  • Page 102 Patches for Backup Patches for backup and restore operations will be available on the Novell Support Web site (http://support.novell.com) concurrent with the shipment of NetWare 6. WAN Support WAN support is not included with NetWare 6. If you are upgrading from a previous version of NetWare, your AUTOEXEC.NFC and STARTUP.NCF...
  • Page 103 Novell NetWare 6 w w w. n o v e l l . c o m Q U I C K S T A R T Installation and Upgrade M I N I M U M S Y S T E M R E Q U I R E M E N T S...
  • Page 104 ® Novell Client for DOS and Windows* 3.1x (optional, for installing from a NetWare server running IPX IP Server Connection Utility (optional, for installing from a NetWare server running IP only). For instructions, see PRODUCTS\SERVERINST\IPCONN.TXT on the Novell Client CD.
  • Page 105 IP address and domain names (required for connecting to the Internet): An IP address An IP address of a domain name server The name of your domain Network board and storage device properties, such as the interrupt and port address (required if not included in NetWare) P R E P A R E T H E N E T W O R K 1 Run NetWare Deployment Manager (NWDEPLOY.EXE), located on the NetWare 6 Operating...
  • Page 106 U P D A T E N S S V O L U M E S ( U P G R A D E O N L Y ) If you upgraded from a NetWare 5.1 server with Novell Storage Services (NSS) volumes, you must complete the following procedure to update NSS volumes.
  • Page 107 Deployment Manager or from the GUI server console screen. Copyright © 2001 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. eDirectory, iFolder, Internetwork Packet Exchange and IPX, Novell Client, Novell Cluster Services, and Novell Storage Services are trademarks and NetWare and Novell are registered trademarks of Novell, Inc.
  • Page 108 Novell NetWare ® w w w . n o v e l l . c o m O V E RV I E W A N D I N S TA L L AT I O N G U I D E...
  • Page 109 Eliminate Client Software with Novell Native File Access Protocols ....11 Print from Anywhere with Novell iPrint ......12 Access and Manage Your Files From Anywhere with Novell iFolder.
  • Page 110 Migrate Network Data to another Server with NetWare Migration Wizard ... 23 Use Other Installation Options to Simplify the Move to NetWare 6 ....24 Let’s Get Started .
  • Page 111 Setting Up Novell iManage ........77...
  • Page 112 NetWare 6 Overview and Installation Guide...

  • Page 113: Preface

    Novell Product Documentation Web site (http:// www.novell.com/documentation). Novell Education offers a variety of courses that help you maximize your investment in NetWare 6. For course descriptions, details, and locations of training events, visit the Novell Education Web site (http:// www.novell.com/education/netware6).

  • Page 114: User Comments

    User Comments We want to hear your comments and suggestions about this manual and the other documentation included with NetWare 6. To contact us, send e-mail to webdoc@novell.com or send comments to: Novell, Inc. Product Documentation MS PRV-E-232 1800 South Novell Place...

  • Page 115: Welcome To Netware 6

    Several new products help end users access, synchronize, and print their files from any location. Eliminate Client Software with Novell Native File Access Protocols ® Novell Native File Access Protocols let Macintosh*, Windows*, and UNIX* workstations access and store files on NetWare servers without having to install any additional software—such as Novell Client...

  • Page 116: Print From Anywhere With Novell Iprint

    Guide. Access and Manage Your Files from Anywhere with Novell iFolder Novell iFolder is a file storage and management solution to the universal problems associated with storing and retrieving data. With iFolder you have the latest version of your data when you need it and where you need it from any computer that you regularly use.

  • Page 117: Use Novell Netstorage To Access Files With An Internet Browser

    Web or FTP server with only an Internet connection, thereby eliminating the need to have a Novell Client. When connected to the Web or FTP server, they can perform all the familiar file operations that they now use in Windows Explorer.

  • Page 118: Access Internet Services From A Centralized Location With Netware Webaccess

    NetWare WebAccess allows administrators to set up a Web page that lets users access multiple network resources from their Web browser. Users do not need a Novell Client or VPN client to access to their resources. They can access these resources on the Web from any computer with a compliant browser.

  • Page 119: Manage Edirectory Objects From An Internet Browser With Imanage

    ConsoleOne is a Java-based administration tool that you can use to flexibly manage Novell and third-party products on a variety of platforms. Running on either a NetWare server or a Windows workstation, ConsoleOne provides a single point of administration for your network resources, including eDirectory objects, schema, partitions, replicas, and NetWare servers.

  • Page 120: Manage Ip Addresses With The Novell Dns/Dhcp Administration Tool

    Engine, NetWare Enterprise Web Server, Apache Web Server, and WebDAV, technologies that enable Novell’s Net Services products to work. The following diagram depicts the role that Novell Web Services plays as the Web-enabling technology for Net Services Software such as iFolder, iPrint, iLogin, and Web Search Server.
  • Page 121 Services. Manage Novell Web Services with NetWare Web Manager NetWare Web Manager is the tool you use to manage all of your Novell Web Services and to access other Web-based management tools. You can manage your Novell Web Services from any place on the Internet using an Internet browser.

  • Page 122: Publish Web Pages With Netware Enterprise Web Server

    Manage UNIX and NetWare Networks with Network Information Services Network Information Service (NIS) lets you use Novell eDirectory manage UNIX computers by providing information about users, groups, and hosts and other information that NIS client might require. It maintains all information in the form of eDirectory objects organized under the eDirectory tree.

  • Page 123: Track Network Usage With Novell Advanced Audit Service

    Novell Advanced Audit Service (NAAS) is an Novell eDirectory enabled robust, flexible, and scalable auditing framework. It can audit services, both Novell and third-party, and can provide a single, unified view of audit data for the entire Net. It provides a single point of management by storing configurable audit policies in eDirectory.

  • Page 124: Manage Millions Of Network Objects With Novell Edirectory

    Novell Cluster Services allows you to configure up to 32 NetWare servers into a high-availability cluster, where resources can be dynamically switched or moved to any server in the cluster. Resources can be configured to automatically switch or be moved in the event of a server failure, or they can be moved manually to troubleshoot hardware or balance the workload.

  • Page 125: Manage Disk Storage Devices With Novell Storage Services

    Manage Disk Storage Devices with Novell Storage Services Novell Storage Services (NSS) is a file storage and management system that meets the needs of your growing file system requirements. NSS can take free space from multiple storage devices and create unlimited volumes which can store up to 8 trillion files (each up to 8 terabytes in size).

  • Page 126: Back Up Data With Storage Management Services

    It provides high security, performance, and reliability of the host in the Internet environment. Novell TCP/IP offers an extensive set of configurable parameters for all supported protocols. You can use these parameters to modify the default characteristics of the initial configuration and also to configure advanced features and optimize host, router, and LAN performance options.

  • Page 127: Reduce Deployment Costs With Netware 6

    segments. The Migration Agent is used to migrate systems from IPX to IP in a phased manner without losing connectivity. For more information, see the Server Communications Administration Guide. Reduce Deployment Costs with NetWare 6 NetWare 6 includes several options that help you install a new server, upgrade a legacy NetWare server, or migrate from a Windows NT* server.

  • Page 128: Let's Get Started

    Use Other Installation Options to Simplify the Move to NetWare 6 Several other options are also available to help you install or upgrade to NetWare 6. Quickly upgrade with NetWare Accelerated Upgrade—You can run NetWare Accelerated Upgrade from a Windows client workstation so that you don’t need to be physically present at the server console.
  • Page 129 Use advanced installation/ Other Installation Options upgrade options All this information is available on the NetWare 6 Online Documentation CD included with the NetWare 6 product and on the NetWare 6 Product Documentation Web site (http://www.novell.com/documentation/lg/nw6p). Welcome to NetWare 6...
  • Page 130 NetWare 6 Overview and Installation Guide...

  • Page 131: Setting Up Netware 6

    Specify hardware and software settings Create volume SYS: Name the server and install the server file system Install networking protocols Set up Novell eDirectory Install other networking products Meeting System and Software Requirements System Requirements NetWare will run on the minimum system requirements listed below. For optimal performance, the computer should meet the recommended requirements.

  • Page 132: Software And Other Requirements

    A Super VGA display adapter A DOS partition of at least 200 MB and 200 MB available space 2 GB of available disk space outside the DOS partition for volume SYS: One network board A CD drive A USB, PS/2*, or serial mouse (recommended but not required) Recommended System Requirements For optimal performance, NetWare 6 has the following recommended system requirements:...
  • Page 133 IP Server Connection Utility (optional, for installing from a NetWare server running IP only). For instructions, see PRODUCTS\SERVERINST\IPCONN.TXT on the Novell Client CD. IP address and domain names (required for connecting to the Internet): An IP address An IP address of a domain name server...

  • Page 134: Preparing The Network

    Double-click the Network Preparation folder to view the tasks and read the Overview section to get an understanding of the tasks. ® Back up any server data and Novell eDirectory data following the instructions in the Back Up Data step.
  • Page 135 Run the View and Update eDirectory Version program to update eDirectory as required. HINT: If you are prompted to log in again while running NetWare Deployment Manager, you can enter the IP address of the server by clicking Details. Run the Prepare for eDirectory program to extend the network schema. Setting Up NetWare 6...
  • Page 136 (Conditional) If you are upgrading a cluster of NetWare servers, run the Prepare a Novell Cluster for Upgrade program. ® (Conditional) If you are upgrading a NetWare 5 server running NDS that has NSS volumes, run the Prepare a Server with NDS 7 and NSS program.

  • Page 137: Preparing The Computer

    Preparing the Computer To prepare your computer for NetWare 6, do the following: Install computer and networking hardware Create and format a DOS partition Access the installation files Installing Computer and Networking Hardware Follow the manufacturer’s instructions to install and connect the network board and network cabling to your computer.

  • Page 138: Accessing The Installation Files

    BUFFERS=30 commands. (Conditional) If you are installing from files located on a network, install the Novell Client for DOS and Windows 3.1x or IP Server Connection Utility software located on the Novell Client CD. After accessing the files for the installation program, you can begin the installation.

  • Page 139: Installing The Software

    Installing the Software To begin the installation, complete the following steps. Insert the NetWare 6 Operating System CD, or log in to the network to access the installation files on the network. At the CD drive or network drive prompt, enter INSTALL. Navigating in the Character-Based Screens The initial screens of the installation program display in text-based mode.

  • Page 140: Selecting The Language And Accepting The License Agreement

    Selecting the Language and Accepting the License Agreement The installation program is available in several languages. You can install other language options, such as the language for the operating system or for users, later during the installation program. Accepting each License Agreement means that you have read and you accept terms and conditions contained in the License Agreement.
  • Page 141 New Server, Upgrade or Pre-Migration Server You can install NetWare on a new computer or you can upgrade an existing computer running NetWare 4 or NetWare 5. New Server—Installs a new server. Creates a new NetWare partition but does not delete system partitions or other partitions such as DOS, UNIX*, or Windows.

  • Page 142: Specifying Server Settings

    Specifying Server Settings You can change the following default server settings for your networking environment. Server ID Number—A unique server identification number (up to eight hexadecimal digits) identifies the server on the network. The server ID number functions like an internal IPX number. Although a server ID number is created automatically, you might need to enter a specific server ID number if you are installing in either of the following conditions: Filtered environment—Routers between network segments can be...

  • Page 143: Selecting The Regional Settings

    Selecting the Regional Settings Choose the country, code page, and keyboard mapping for your language and computer. Selecting the Mouse and Video Type Setting Up NetWare 6...

  • Page 144: Selecting A Platform Support Module And Storage Adapter

    Mouse Type—Choose a mouse type, if available on the computer. The installation program supports USB, PS/2 and serial mouse types, but a mouse is not required. Video Type—The NetWare installation program is optimized to display with video display hardware that is VESA 2 compliant. NOTE: The video type is not auto-detected by the installation program.

  • Page 145: Selecting A Platform Support Module (If Required)

    To delete a driver, in the Options box select Modify. Select the driver field and press Enter. Select the driver to delete and press Delete. To modify a driver, in the Options box select Modify. Select the driver field and press Enter. Select the driver to modify and press Enter. Select the property to modify.

  • Page 146: Selecting A Storage Device And A Network Board

    Editing the Properties of the Storage Adapter (If Required) The storage adapter must be installed and configured correctly. Properties such as interrupt, port value, and slot must not conflict with any other device in the computer. If you need specific storage adapter properties, contact the storage adapter manufacturer.

  • Page 147: Selecting A Storage Device

    NetWare 6 or add a new driver from a diskette. CDMs can be obtained from the storage device manufacturer. Selecting a Network Board Network boards, such as the Novell NE3200 board, require a software driver in order to communicate with the network. The software driver for a network board is called a LAN driver.

  • Page 148: Creating A Netware Partition And Volume Sys

    Creating a NetWare Partition and Volume SYS: Partitions correspond with operating systems, such as NetWare, DOS, or UNIX. Partitions divide a large storage region into smaller, more manageable sections. A single storage device can contain up to four partitions. You can divide NetWare partitions into smaller sections called volumes. Each NetWare partition can contain up to eight volumes.

  • Page 149: Creating Volume Sys

    During the initial stages of installation, the installation program guides you through the steps to create a single NetWare partition containing volume SYS:. It is created as a Novell Storage Services (NSS) volume, which has many advantages over a traditional volume.

  • Page 150: Summary

    Volume SYS: Size—The size that you specify for the NetWare partition will be used for the size of volume SYS:. To modify the volume SYS: size, in the Options box select Modify. Select the appropriate storage device. Select the NetWare Partition Size field and press Enter.
  • Page 151 Although a mouse is recommended, you can use the keyboard commands in Table 1 to navigate through the installation program. Use the arrow keys on the numeric keypad for cursor movements. HINT: NumLock (number lock) must be on in order for cursor movements to be enabled on the keypad.

  • Page 152: Enabling Cryptography

    Keystroke Action Hold Shift while pressing Accelerate cursor movement keypad Keypad 5 Select or click an object Keypad 0 Lock a selected object (for dragging) Keypad . (period) Unlock a selected object (to drop) Keypad + (plus) Double-click an object Alt+F7 Move to next window Alt+F8...

  • Page 153: Installing The Netware Server File System

    ). The volume name cannot begin with an underscore (_) or have two or more consecutive underscores. You can create two types of volumes—Novell Storage Services (NSS) volumes or traditional volumes. NSS volume—NSS is advanced file system technology that enhances the management of large files, large volumes, namespaces, and storage devices.

  • Page 154: Creating Volumes

    Creating Volumes Volumes are created from free space. A large disk can be divided into several volumes during installation. Conversely, a volume can be distributed over multiple disks. WARNING: Creating a volume that spans two or more storage devices is not recommended.

  • Page 155: Modifying Volumes

    To create a volume, select Free Space and click Create. Type the name of the volume and click OK. To allocate only a portion of the selected free space to the volume, type the amount of space to use and click Apply to Volume. Modifying Volumes The size of any existing volume can be increased but not decreased.
  • Page 156 Mount Volumes Now—You should mount volumes now if you plan to install additional products and services, such as documentation, on volumes other than volume SYS:. You should also mount volumes that you might be moving forward from a previous NetWare server so they can be updated.

  • Page 157: Installing Networking Protocols

    Installing Networking Protocols NetWare 6 can process IP (Internet Protocol) network packets and traditional IPX (Internetwork Packet Exchange ) packets. Both protocols can be assigned to a single network board, which allows the server to communicate using IP and IPX. To install IP, click a network board and then check the IP check box.

  • Page 158: About Internet Protocol (Ip)

    About Internet Protocol (IP) Internet protocol (IP) lets your network share data with other IP networks, including the Internet. Using IP requires a unique IP address, a subnet, and a router or gateway address. IP Address—Identifies each device on the network. The address consists of 32 bits, which are represented as decimal values separated by periods, such as 123.45.67.89.

  • Page 159: About Ipx

    About IPX Novell’s traditional protocol, Internetwork Packet Exchange (IPX), lets you continue using IPX-based applications. If IPX, but not IP, is installed on your server, it will actively process IPX packets and ignore packets using other protocols, such as IP.
  • Page 160 HINT: If this server will not be available to the Internet, you can skip this screen and ignore any associated error messages. If you want this server to be available to the Internet, you must enter the following: Host Computer—The simple, readable name on the DNS server that matches this NetWare server’s name (or the name that you have bound to the network board).

  • Page 161: Configuring A Netware Server As A Dns Server (Optional)

    Advanced time synchronization settings are available during the Customize section of the installation. Setting Up Novell eDirectory Novell eDirectory provides global access to all networking resources. eDirectory allows users with the proper access rights to log in to the network and view and access network resources.

  • Page 162: Choosing The Type Of Edirectory Installation

    Choosing the Type of eDirectory Installation To set up eDirectory, you must choose one of the following options: Install the server into an existing eDirectory tree Create a new eDirectory tree Before completing this task, you should understand the concepts relating to eDirectory trees, containers, and context.

  • Page 163: Install The Server Into An Existing Edirectory Tree

    Install the Server into an Existing eDirectory Tree Installing your server into an existing eDirectory tree incorporates the server into your network. The server can be installed in any Organization (O) or Organizational Unit (OU) container in the eDirectory tree where you have the Supervisor right. You can create containers during the installation program.

  • Page 164: Summary

    Each eDirectory tree must have a name unique from other eDirectory trees on the network. You will also be prompted to create a user (default name Admin) with the Supervisor right, identify an eDirectory context, and assign a password. Summary Now that you have created a new eDirectory tree or installed the server into an existing eDirectory tree, the NetWare Server object and Volume objects will be installed in the container you specified.

  • Page 165: Licensing The Netware Server

    If you have created a new eDirectory tree, a user (default name Admin) with Supervisor rights to the eDirectory tree will be created in the same eDirectory container as the NetWare Server object. IMPORTANT: Record the administrator password and other relevant information before proceeding.

  • Page 166: Install Networking Products

    If prompted, select where in the tree you want to install the license. Install Networking Products After completing the NetWare server portion of the installation, you can select other networking products to install. Other networking products provide enhanced functionality, such as network management and Internet access, to NetWare 6.
  • Page 167 For more information on configuration requirements for specific products, refer to each product documentation as part of the NetWare 6 documentation at the NetWare 6 Documentation site (http://www.novell.com/documentation/ lg/nw6p/index.html). Setting Up NetWare 6...

  • Page 168: Configuring Ip-Based Services (Conditional)

    Getting Results with Novell Web Services. Installing Novell Certificate Server Novell Certificate Server enables secure data transmissions and is required for Web-related products such as NetWare Web Manager and NetWare Enterprise Web Server. It also allows you to mint, issue, and manage digital certificates by creating a Security container object and an Organizational Certificate Authority (CA) object.
  • Page 169 Only one Organizational CA object can exist in an eDirectory tree. Once the Organizational CA object is created on a server, it cannot be moved to another server. Deleting and re-creating an Organizational CA object will invalidate any certificates associated with the Organizational CA. Make sure that the server that you intend to permanently host the Organizational CA object and will be a reliable, accessible, and continuing part of your network.

  • Page 170: Configuring Ldap

    Configuring LDAP TCP and SSL port numbers can be configured for LDAP services. You can also configure ports after the server installation using ConsoleOne. The default setting for the Allow Cleartext Passwords option (unchecked) disallows cleartext passwords, effectively disabling eDirectory user binds on non-SSL connections.

  • Page 171: Installing Novell Native File Access Protocols

    About Native Protocols Novell Native File Access Pack software enables the NetWare server to use the same protocol (referred to as "native") as the client workstation to copy, delete, move, save, and open files. Windows workstations perform these tasks using the native Common Internet File System (CIFS) protocol, and Macintosh workstations use the native Apple* Filing Protocol (AFP).
  • Page 172 NNFAP Server Name The name specified in the NNFAP Server Name field displays as the server name when Windows workstations without Novell Client software browse the network You can change the name but it must be different than the NetWare Server name and no longer than 15 characters.
  • Page 173 Domain authentication. Local Authentication The server running Novell Native File Access Protocol software performs the user authentication when clients are a member of a workgroup. With local authentication, the username and password on NetWare must match the username and password used to log in to the Windows workstation.
  • Page 174 Workgroup and Domain are interchangeable. WINS Address: Address of WINS server to be used to locate the primary domain controller (PDC), if the PDC and server running Novell Native File Access Protocols software are on different subnets. Windows Internet Naming Service (WINS), part of the Microsoft Windows NT and 2000 Servers, manages the association of workstation names and locations with Internet Protocol (IP) addresses.
  • Page 175 PDC Address The address of the PDC must be static; otherwise, if the PDC reboots and the address changes, the server running Novell Native File Access Protocols software will not be able to contact the PDC. Setting Up NetWare 6...
  • Page 176 Selecting IP Addresses to Service Windows Workstations Although we recommend that you enable the CIFS protocol on all IP addresses, you can specify which IP addresses will respond to CIFS protocol requests. Specifying Share Points for Windows Workstations Any volume or directory on the server can be specified as a shared point and made accessible via the Network Neighborhood or My Network Places.
  • Page 177 Directory The path to the server volume or directory which becomes the root of the sharepoint. Beginning at the volume name, the full path must be specified and it must end with a backslash (\). For example: VOL1:GRAPHICS\ Share Name The name by which the sharepoint is displayed to Windows computers.
  • Page 178 You must specify the NDS contexts of Windows users that require access to the network. These contexts are saved in the context search file. When the Windows user enters a username, the Novell Native File Access Protocol software searches through each context in the list until it finds the correct User object.

  • Page 179: Setting Up Netware Webaccess

    NetWare WebAccess lets administrators set up a Web page that allows users access to multiple network resources from their Web browser. Users do not need a Novell Client or VPN client to access to their resources. They can access these resources on the Web from any computer with a compliant browser.
  • Page 180 Choose which gadgets you want to enable and configure now and which gadgets you want to enable and configure later by checking or unchecking the check boxes next to each gadget type. All gadgets are installed automatically when you install NetWare WebAccess. This screen lets you choose whether to enable and configure those gadgets now or later.

  • Page 181: Setting Up Novell Imanage

    For Lotus* Notes*, provide the URL for accessing your Lotus Notes server. The URL might be something like showcase2.notes.net. For Novell Internet Messaging Services (NIMS), provide the URL to the NIMS server. The URL was created when you installed and configured NIMS, and might be something like https://webmail.myrealbox.com.
  • Page 182 During installation, roles and tasks are installed and associated with the logged-in user (typically the Admin user) by default. These role and task objects are stored in a new eDirectory container (rbsCollection). You can select the location and name of the new container or use the defaults provided. Location Enter the path to the eDirectory container that you want to create the rbsCollection container in, or use the default location.

  • Page 183: Install Novell Ifolder

    Install Novell iFolder Novell iFolder is a file storage and management solution to the universal problems associated with storing and retrieving data. With iFolder you have the latest version of your data when you need it and where you need it from any computer that you regularly use.

  • Page 184: Install Novell Netstorage

    Internet. It allows users secure file access from any Internet location, with nothing to download or install on the user's workstation. Files and folders on a Novell network can be accessed using either a browser or Microsoft Web Folders. DNS Name or IP Address of Primary eDirectory Server and Context Specify the IP address or DNS name of a server in your eDirectory tree that has the master replica or a read/write replica of eDirectory.
  • Page 185 Specify the IP address or DNS name and the port number that you assigned to Novell iFolder. The iFolder DNS name or IP address and the port number are optional but, if specified, will allow NetStorage users to access and manipulate files and directories on the iFolder server.

  • Page 186: Customizing The Installation

    Customizing the Installation You can customize the installation of many products for your networking environment. To customize products and components, at the Summary screen click Customize to access the Customize screen. NetWare 6 Overview and Installation Guide...

  • Page 187: Completing The Server Installation

    Select the product to customize. Click Properties. Modify the product as required. Click OK to return to the Summary screen. Completing the Server Installation The server installation program is now ready to copy files to your computer. Depending on which products you are installing, you might be prompted for additional information.

  • Page 188: What's Next

    Chapter 1, “Welcome to NetWare 6,” on page Although many products can be installed during the basic server installation, some additional products such as Novell Cluster Services can be installed only after completing the server installation. You can install additional...
  • Page 189 NetWare Deployment Manager or from the GUI server console screen. Install Additional Products Using NetWare Deployment Manager Log in to the network from a Windows workstation running Novell Client software. Run NWDEPLOY.EXE located at the root of the NetWare 6 Operating System CD.
  • Page 190 NetWare 6 Overview and Installation Guide...

  • Page 191: Upgrade To Netware 6

    Specify hardware and software settings Create additional disk volumes (if required) Select and install networking protocols ® Set up Novell eDirectory Install other networking products During the upgrade program, the server is upgraded to NetWare 6 by automating the following tasks: Device drivers and LAN drivers for the NetWare 6 operating system are loaded.

  • Page 192: Meet System And Software Requirements

    Meet System and Software Requirements To upgrade to NetWare 6, your system must meet the minimum requirements listed below. System and Software Requirements The server to be upgraded must be running one of the following: NetWare 5.1 with Support Pack 2 or later NetWare 5 with Support Pack 6 or later NetWare 4.2 with Support Pack 8 or later NetWare 4.0 with Support Pack 8 or later...

  • Page 193: Preparing The Network

    IP Server Connection Utility (optional, for installing from a NetWare server running IP only). For instructions, see PRODUCTS\SERVERINST\IPCONN.TXT on the Novell Client CD. IP address and domain names (required for connecting to the Internet): An IP address An IP address of a domain name server...
  • Page 194 Double-click the Network Preparation folder to view the tasks and read the Overview section to get an understanding of the tasks. Back up any server data and Novell eDirectory data following the instructions in the Back Up Data step. Run the View and Update eDirectory Version program to update eDirectory as required.
  • Page 195 Run the Prepare for eDirectory program to extend the network schema. (Conditional) If you are upgrading a cluster of NetWare servers, run the Prepare a Novell Cluster for Upgrade program. Upgrade to NetWare 6...
  • Page 196 ® (Conditional) If you are upgrading a NetWare 5 server running NDS that has NSS volumes, run the Prepare a Server with NDS 7 and NSS program. Follow the instructions in the Update Certificate Authority (CA) Object step to create or update a Security container object and a Certificate Authority (CA) object.

  • Page 197: Preparing The Computer

    If you installed WebSphere to a different directory, specify that directory. Complete the upgrade to NetWare 6. After the upgrade, continue migrating the applications by following the instructions in "Migrating from WebSphere to Tomcat in Getting Results with Novell Web Services. Upgrade to NetWare 6...

  • Page 198: Verify A Valid Dos Partition

    “Setting Up NetWare 6” on page HINT: If your computer does not meet the minimum requirements, you might try using the Novell Migration Wizard utility to migrate data to another computer. For more information, see www.novell.com/documentation. Access the Installation Files NetWare 6 can be upgraded from the server’s local CD drive or from...

  • Page 199: What's Next

    Make sure that the CONFIG.SYS file contains the FILES=50 and BUFFERS=30 commands. (Conditional) To upgrade from NetWare 6 files located on a network, install the Novell Client for DOS and Windows 3.1x or IP Server Connection Utility software located on the Novell Client CD. What’s Next...
  • Page 200 NetWare 6 Overview and Installation Guide...
  • Page 201 Novell NetWare ® w w w . n o v e l l . c o m O T H E R I N S TA L L AT I O N O P T I O N S...
  • Page 202 Contents Overview Using NetWare Accelerated Upgrade ....... . 9 Automating the NetWare Installation with a Response File ..... 9 Using Installation Scripts for NetWare Installation .
  • Page 203 Performing a Fully Automated Installation......78 [Novell:NOVELL_ROOT:1.0.0] Section ......78 Automating the Installation of Additional Products and Services .
  • Page 204 [Novell:SBDFiles:1.0.0] Section ....... . 94 [Novell:portalzip:1.0.0] Section ....... . . 94 [Novell:Rconjzip:1.0.0] Section .
  • Page 205 Other Installation Options...

  • Page 206: Overview

    Overview ® The following advanced options can help you upgrade or install NetWare servers. Using NetWare Accelerated Upgrade You can run NetWare Accelerated Upgrade from a Windows* client workstation, so that you don’t need to be physically present at the server console.

  • Page 207: Using Installation Scripts For Netware Installation

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. Other Installation Options...

  • Page 208: Using Netware Accelerated Upgrade

    Using NetWare Accelerated Upgrade ® The NetWare Accelerated Upgrade utility is an advanced utility that can be used to upgrade a NetWare 4.11, NetWare 4.2, or NetWare 5 server to NetWare 6. NetWare Accelerated Upgrade is intended for use by network administrators who are skilled at troubleshooting and installing NetWare networks.
  • Page 209 NetWare 4 or 5 targeted server Logs in File copy Windows Logs in client workstation running NetWare Accelerated Upgrade Staging server After the NetWare 6 Operating System CD files are copied to the staging server, you will log in to a Windows workstation and launch the NetWare Accelerated Upgrade utility (ACCUPG.EXE), located at the root of the NetWare 6 Operating System CD.

  • Page 210: Upgrading To Netware 6

    3.3 or later and Support Pack 1 or later The Windows NT and Windows 2000 workstations must be running Novell Client for Windows version 4.8 or later and Support Pack 1 or later PS/2* or serial mouse recommended, but not required.
  • Page 211 For information on using script files, see "Upgrading an Enterprise Using the NetWare Accelerated Upgrade" (AppNotes, April 1999) at the Novell Developer Net Web site (http://developer.novell.com/research/ completearchive.htm). When the source server is ready, continue with the next section, "Prepare the Target Server."...

  • Page 212: Prepare The Target Server

    For more information about upgrading servers with ZENworks, see ZENworks for Server 2 Installation and Setup Guide (http://www.novell.com/ documentation/lg/zfs2/index.html) > Installing and Setting Up Management and Monitoring Services > Setting Up Management and Monitoring >...
  • Page 213 Update the target server with the latest NetWare Support Pack. Support Packs are available at the Novell Support Web site (http:// www.support.novell.com/filefinder). NetWare 4.11 and NetWare 4.2 require NetWare 4 Support Pack 8 (IWSP6A.EXE) or later...

  • Page 214: Prepare The Network

    Run the NetWare Deployment Manager utility (NWDEPLOY.EXE), located at the root of the NetWare 6 Operating System CD. Click Network Preparation > Prepare a Novell Cluster for Upgrade. Run DSREPAIR > Time Synchronization at the server console of the ®...

  • Page 215: Run Netware Accelerated Upgrade

    Run NetWare Accelerated Upgrade From your workstation, log in to the staging server and double-click the NetWare Accelerated Upgrade executable (ACCUPG.EXE), located at the root of the NetWare 6 Operating System CD. Read the Welcome screen and click the right-arrow. Enter the location where you copied or mounted the NetWare 6 files to the staging server and click the right-arrow.
  • Page 216 Check any of the following options that you want NetWare Accelerated Upgrade to automatically perform during the upgrade, and then click the right-arrow: Reboot the target server after the upgrade is completed. Even if you checked this option, there might be an instance where you might need to manually reboot the target server once the file copy is complete.

  • Page 217: Complete Post-Upgrade Tasks

    NetWare Accelerated Upgrade does not install additional products. If you want to add network products, you can do so in one of two ways: Through the server console by clicking the Novell icon on the servertop and then Install. Through Deployment Manager (located at the root of the NetWare 6 Operating System CD).

  • Page 218: Troubleshooting Server-To-Server Connections

    LAN segment as the target and staging servers. Detaching from Unauthenticated Servers From a Windows 95/98 or Windows NT client, right-click the red Novell N. Click NetWare Connections. Select the server that you are not authenticated to. Click Detach.

  • Page 219: Setting The Target Server's Gate Parameter To Its Default Router Ip Address

    Setting the Target Server’s Gate Parameter to Its Default Router IP Address For a NetWare 4 Target Server At the server console, enter LOAD INSTALL Select NCF Files Options > Edit AUTOEXEC.NCF File. In the AUTOEXEC.NCF file, add LOAD TCP/IP Add a command that loads the network board and specifies the slot, frame, and name of the network board (the AUTOEXEC.NCF file should list this information).
  • Page 220 At the BIND IP command line, after the mask address, set the gate parameter to the default router IP address for the target server. For example, if your default router IP address was 137.65.178.1, at the BIND IP command line you would enter the following after the mask address: gate=137.65.178.1 Using NetWare Accelerated Upgrade...
  • Page 221 Other Installation Options...

  • Page 222: Automating The Netware Installation With A Response File

    Using a response file to install NetWare can be very useful to a variety of ® customers and vendors. Novell customers who have established server hardware standards in their enterprise can use the response file to rapidly deploy multiple NetWare servers.

  • Page 223: Creating A Response File

    This chapter contains the following sections: “Creating a Response File” on page 26 “Using a Response File” on page 27 “Syntax” on page 28 “NetWare Sections and Keys” on page 33 “Performing a Fully Automated Installation” on page 78 “Automating the Installation of Additional Products and Services” on page 79 “CD Boot and the Response File”...

  • Page 224: Using A Response File

    Copy RESPONSE.NI from the SYS:NI\DATA directory to either a diskette or to the new server. Modify the file by adjusting the parameters and removing unwanted sections. “Syntax” on page 28 for a description of the parameters Using a Response File A response file can be used during a server installation in one of two ways: Identified during the server installation Entered at the command line...

  • Page 225: Syntax

    Syntax A response file is a Windows .INI-type file. Data items are identified as keys, and keys have associated values (Key = value). These keys are grouped in sections. For the NetWare installation program, each data input screen has one or more sections associated with it.
  • Page 226 Section Purpose “[NWI:Excluded From Detection] Identifies what drivers will be excluded Section” on page 44 from the auto-detection. “[NWI:Multi-Processor System] Identifies the driver associated with the Section” on page 44 processor system in the server. “[NWI:Storage Adapter n] Section” Identifies the driver and its associated on page 45 parameters for a specific storage adapter.
  • Page 227 Specifies whether to use the response file on page 77 or the AUTOEXEC.NCF file for the server name during an upgrade. “[Novell:NOVELL_ROOT:1.0.0] Specifies full automation of installation. Section” on page 78 “[Selected Nodes] Section” on page Specifies full automation of products and services.
  • Page 228 Specifies full automation of factory install. Section” on page 92 “[Novell:ConfigDirectory:1.0.0] Specifies full automation of factory install. Section” on page 93 “[Novell:LANFiles:1.0.0] Section” on Specifies full automation of factory install. page 93 “[Novell:SBDFiles:1.0.0] Section” on Specifies full automation of factory install.
  • Page 229 In the following example, the data input screen will be displayed with the NDS information already filled in: [NWI:NDS] Prompt = True Tree Name = Novell New Tree = True Server Context = O=Utah Admin Context = O=Utah Admin Login Name = Admin...

  • Page 230: Netware Sections And Keys

    NetWare Sections and Keys The NetWare installation sections and their associated keys are specified below. Section names and Key names are in bold. Included with each key are the default value, possible values, whether the Key is required for the NetWare installation to run silently (for example, to create a new NDS tree without any user input, New Tree=True must appear in the response file).

  • Page 231: [Nwi:language] Section

    Small Business = <string> Default False Value True or False Key Required Example Small Business = True Purpose Controls whether the Small Business licensing model is used. [NWI:Language] Section Prompt = <string> Default True Values True or False Key Required Example Prompt = True Purpose...

  • Page 232: [Nwi:install Options] Section

    Additional Languages = <integers separated by commas> Default (none) Values 1-100 (values are specified in INSTALL\PROFILE.TXT) Key Required Example Additional Languages = 5,6 Purpose Specifies additional languages that will be installed on the server. [NWI:Install Options] Section Prompt = <string> Default True Values...
  • Page 233 Startup Directory = <string> Default C:\NWSERVER Values (existing DOS path up to 255 characters) Key Required Example Startup Directory = C:\NWSERVER Purpose Identifies the directory where the server’s initialization files will reside on the Boot Partition. Allow User response file = <string> Default True Values...

  • Page 234: [Nwi:server Settings] Section

    [NWI:Server Settings] Section Prompt = <string> Default True Values True or False Key Required Example Prompt = True Purpose Controls whether the screen is displayed. NDS Version = <integer> Default Values 7 or 8 Key Required Example NDS Version = 8 Purpose Specifies the version of NDS to install on this server.

  • Page 235: [Nwi:locale] Section

    CD Driver = <string> Default NetWare Values NetWare or DOS Key Required Example Source Media Access = NetWare Purpose Determines the driver type (DOS or server) used to access the CD during installation. [NWI:Locale] Section Prompt = <string> Default True Values True or False Key Required...

  • Page 236: [Nwi:mouse And Video] Section

    Code Page = <integer> Default Values (values are specified in INSTALL\NLS\language number\LOCALE.TXT) Key Required Example Code Page = 437 Purpose Sets the character set for the server. Keyboard = <string> Default United States Values (values are specified in INSTALL\NLS\<language number>\LOCALE.TXT) Key Required Example Keyboard = United States...

  • Page 237: [Nwi:hardware] Section

    Mouse = <string> Default PS/2 Values PS/2, Serial COM1, Serial COM2, No Mouse (values are specified in INSTALL\NLS\language number\LOCALE.TXT) Key Required Example Mouse = PS/2 Purpose Specifies the mouse type that will be used for the graphical portion of the installation. Use Super VGA = <string>...
  • Page 238 Update Storage Driver Directory = <DOS path> Default (none) The Install always looks in C:\NWUPDATE as well. Values (existing DOS path up to 255 characters) Key Required Example Update Storage Driver Directory = F:\DRV\UPDATE Purpose Specifies the directory path where updated storage (HAM and CDM) drivers will be found;...
  • Page 239 Update PSM Driver Directory = <DOS path> Default (none) The Install always looks in C:\NWUPDATE as well Values (existing DOS path up to 255 characters) Key Required Example Update PSM Driver Directory = F:\DRV\UPDATE Purpose Specifies the directory path where updated processor (PSM) drivers will be found;...
  • Page 240 Storage Detection = <string> Default True Values True or False Key Required Example Storage Detection = True Purpose Controls whether detection of storage adapters and driver matching is performed. If storage adapter and driver information is identified in the response file (see Storage Adapter section), detection can be set to False.

  • Page 241: [Nwi:excluded From Detection] Section

    HotPlug Detection = <string> Default True Values True or False Key Required Example HotPlug Detection = True Purpose Controls whether detection of Hot Plug devices and driver matching is performed. [NWI:Excluded From Detection] Section Driver File = <filename> Default (none) Values (name of driver) Key Required...

  • Page 242: [Nwi:storage Adapter N] Section

    [NWI:Storage Adapter n] Section Example [NWI:Storage Adapter 1] Description This section can be included for each storage adapter in the server. Several Keys are described under this section which are optional; if the driver is detectable by NetWare, only the Driver File key is required for the section.

  • Page 243: [Nwi:storage Device N] Section

    INT = <hexadecimal number> Default (none) Values Key Required No, unless the driver is for an ISA adapter. Example INT = F Purpose Specifies the interrupt that the adapter is set to; this parameter is commonly used for ISA bus adapters. PORT = <number>...

  • Page 244: [Nwi:network Adapter N] Section

    [NWI:Network Adapter n] Section Example [NWI:Network Adapter 1] Description This section can be included for each network adapter in the server. Several Keys are described under this section which are optional; if the driver is detectable by NetWare, only the Driver File Key is required for the section. The other Keys and Values are varied and are extracted from the driver’s corresponding LDI file.
  • Page 245 INT = <hexadecimal number> Default (none) Values Key Required No, unless the driver is for an ISA adapter Example INT = F Purpose Specifies the interrupt that the adapter is set to; this parameter is commonly used for ISA bus adapters. PORT = <number>...
  • Page 246 Frame Type n = <frame type> Default (none) Values (frame types supported by the driver are found in the driver’s LDI file) Key Required Example Frame Type 1 = Ethernet_802.2 Purpose Identifies the network frame type to be used when loading the driver.

  • Page 247: [Nwi:reserved Adapter N] Section

    [NWI:Reserved Adapter n] Section Example [NWI:Reserved Adapter 1] Description This section can be included for each slot in the server. SLOT = <integer> Default (none) Values (can be a 5-digit Hardware Instance Number assigned on servers with buses that support detection—such as PCI) Key Required No, unless the driver is for an ISA adapter Example...

  • Page 248: [Nwi:netware Loadable Module] Section

    [NWI:NetWare Loadable Module] Section Driver File = <filename> Default (none) Values (name of NLM) Key Required Example Driver File = ROUTE.NLM Purpose Identifies the NLM to load during installation. This is typically used for network support NLM programs. [NWI:File System] Section Prompt = <string>...

  • Page 249: [Nwi:partition N] Section

    GUI Prompt = <string> Default True Values True or False Key Required Example GUI Prompt = True Purpose Controls whether the File System screen is displayed during the graphical portion of the install. [NWI:Partition n] Section Example [NWI:Partition 0] Description This section allows partitions to be created on specific devices in the system during installation.
  • Page 250 IDE Device Serial Number = <string> Default (none) Values (string of characters) Key Required Example IDE Device Serial Number = AX8273430930. Purpose Specifies the serial number of the device designated by the manufacturer. (It is usually found on a sticker attached to the device.) IDE Device Channel = <integer>...
  • Page 251 SCSI Device Adapter Slot = <integer> Default (none) Values 1 to16 Key Required Example SCSI Device Adapter Slot = 1 Purpose Identifies the physical slot number of the SCSI adapter SCSI Device ID = <integer> Default (none) Values 0 to 15 Key Required Example SCSI Device ID = 0...
  • Page 252 Partition Size = <integer> or <ALL FREE SPACE> Default (none) Values (up to the size of free space on the device in MB) Key Required Example Partition Size = 1000 Purpose Identifies the size of the partition. Note that the number is modified to align with a cylinder boundary.

  • Page 253: [Nwi:volume N] Section

    [NWI:Volume n] Section Example [NWI:Volume 0] Description This section can be included for each volume defined on the server. Note that SYS must be Volume 0. This section allows volumes to be created on specific partitions in the system during installation. The partitions are specified by the key entries in the section.
  • Page 254 Block Size = <integer> Default (calculated on the size of the first segment of the volume) Values 4 or 8 or 16 or 32 or 64 Key Required Example Block Size = 64 Purpose Identifies the volume’s block size. Note that this key does not apply to NSS volumes.
  • Page 255 Data Migration = <string> Default False Values True or False Key Required Example Data Migration = True Purpose Specifies whether data migration is enabled on the volume. Note that this key does not apply to NSS volumes. Mount = <string> Default False Values...

  • Page 256: [Nwi:misc] Section

    (text) Key Required No, unless it is a network installation. Example Relogin Password = Novell Purpose Specifies the password for the user connection being used while installing across the network. When this section is properly used, the install bypasses the reauthentication screen following the loading of the LAN driver and prior to the preliminary file copy.

  • Page 257: [Nwi:file Server] Section

    (text up to 47 characters—see NetWare documentation for valid set of characters) Key Required Example Servername = Novell Purpose Specifies the name of the server. Note that a server is brought up with temporary name until a valid Servername is entered.

  • Page 258: [Nwi:protocols] Section

    [NWI:Protocols] Section Prompt = <string> Default True Values True or False Key Required Example Prompt = True Purpose Controls whether the protocols screen is displayed. Single Network Adapter=<string> Default False Values True or False Key Required Example Single Network Adapter=True Purpose If this key is set to True then in the [NWI:TCPIP] and [NWI:IPX] sections of the response file the "Logical Name...

  • Page 259: [Nwi:tcpip] Section

    Default IPX Frame Typer=<string> Default (none) Values (Frame types that are supported by a driver are found in the driver’s LDI file Key Required Example Default IPX Frame Type=Ethernet 802.2 Purpose Identifies the network frame type to be bound to the IPX stack when the "Single Network Adapter"...

  • Page 260: [Nwi:ipx] Section

    Subnet Mask n = <decimal number> Default (none) Values (valid IP address) Key Required No, unless Logical Name is set. Example Subnet Mask 1 = 255.255.255.0 Purpose Specifies the subnet. Divides the IP address into network address and node address. Gateway n = <decimal number>...

  • Page 261: [Nwi:ipcmd] Section

    IPX Address n = <hexadecimal number> Default (address detected by the installation program) Values 00000001-FFFFFFFF Key Required No, unless Logical Name is set Example IPX Address 1 = 01010102 Purpose Specifies the IPX address to be bound. [NWI:IPCMD] Section IPX Compatibility = <string> Default True Values...

  • Page 262: [Nwi:snmp] Section

    CMD Net Number = <string> Default (none) Values 00000001-FFFFFFFF Key Required Example CMD Net Number = 01010101 Purpose Specifies the network number. Preferred IP Address = <decimal number> Default (none) Values (valid IP address) Key Required Example Preferred IP Address = 130.1.130.1 Purpose Specifies the IP address.
  • Page 263 Location = <string> Default (none) Values (text) Key Required Example Location = Building A Purpose Identification information that is sent with SNMP traps to assist in troubleshooting. Contact = <string> Default (none) Values (text) Key Required Example Contact = John Doe Purpose Identification information that is sent with SNMP traps to assist in troubleshooting.

  • Page 264: [Nwi:dns] Section

    True or False Key Required Example Prompt = True Purpose Controls whether the DNS screen is displayed. Domain = <string> Default (none) Values (text) Key Required Example Domain = novell.com Purpose Specify a domain. Automating the NetWare Installation with a Response File...

  • Page 265: [Nwi:host Name] Section

    Prompt = True Purpose Controls whether the screen is displayed. Host Name n = <string> Default (none) Values (text) Key Required Example Host Name 1 = install.novell.com Purpose Specifies the host name associated with an IP address already bound. Other Installation Options...

  • Page 266: [Nwi:time Zone] Section

    IP Address n = <decimal number> Default (none) Values (valid IP address) Key Required Example IP Address 1 = 130.1.130.1 Purpose Specifies the IP address associated with a Host Name. Note that Host Name 1 will be set as the Primary address. [NWI:Time Zone] Section Prompt = <string>...

  • Page 267: [Nwi:time Synchronization] Section

    Use Daylight Saving Time = <string> Default True, if Time Zone supports Daylight Saving Time Values True or False Key Required Example Use Daylight Saving Time = True Purpose Controls whether daylight saving time is set. [NWI:Time Synchronization] Section Default Time Server Type = <string> Default (Single if new tree, Secondary if existing tree) Values...
  • Page 268 Tree Name = <string> Default (none) Values (text) Key Required Example Tree Name = Novell Purpose Specifies the tree name for either a new tree or an existing tree to install the server into. New Tree = <string> Default False...
  • Page 269 Add Replica = <string> Default (none) Values True or False Key Required Example Add Replica = True Purpose Controls whether a replica is added to the server. This only applies if the server is not one of the first three servers added to an NDS tree (by default the first three servers receive replicas).
  • Page 270 Admin Context = <string> Default (none) Values (NDS distinguished name) Key Required Example Admin Context = .install.novell Purpose Identifies the NDS context in which the server administrator is to be installed into. Admin Password = <string> Default (none) Values (text)

  • Page 271: [Nwi:license] Section

    Display Summary = <string> Default True Values True or False Key Required Example Display Summary = True Purpose Controls whether the NDS Summary screen is displayed [NWI:License] Section Prompt = <string> Default True Values True or False Key Required Example Prompt = True Purpose Controls whether the license screen is displayed.
  • Page 272 Install Licenses Later = <string> Default False Values True or False Key Required Example Install Licenses Later = True Purpose Specifies that no licenses will be installed on the server. If this key is set to True, all remaining licensing keys will be ignored.

  • Page 273: [Nwi:add To Startup] Section

    Search For Existing License = <string> Default True Values True or False Key Required Example Search For Existing License = False Purpose Controls whether the licenses (such as MLA licenses) are searched for in the tree. Used in conjunction with the next key.

  • Page 274: [Nwi:append To Autoexec.ncf] Section

    Append Line n = <decimal number> Default (none) Values (decimal number) Key Required Example Append Line 1 = LOAD NFS.NAM Purpose Adds the line to the end of the STARTUP.NCF file. If multiple lines are listed, n should increment sequentially. [NWI:Append To Autoexec.ncf] Section Line n = <decimal number>...

  • Page 275: Performing A Fully Automated Installation

    For a fully automated installation to work, these sections must appear in the response file in addition to all of the required keys listed in “NetWare Sections and Keys” on page [Novell:NOVELL_ROOT:1.0.0] Section closeScreen = <string> Default (none) Values...

  • Page 276: Automating The Installation Of Additional Products And Services

    allowSummary = <string> Default True Values True or False Key Required Example allowSummary = False Purpose Controls whether the installation Summary screen is displayed. silent = <string> Default False Values True or False Key Required Example silent = False Purpose Global key that controls whether the installation runs in silent mode with no user interaction.

  • Page 277: [Selected Nodes] Section

    :DS_Install:1.0.0, Novell:LicensePrompt:1.0.0,Novell:NW:1.0.0,Novell:NDPS Server Files:1.0.0 Novell:NW:1.0.0=Novell:Startup:1.0.0,Novell:SYS:1.0.0,Novell:DriverFiles:1.0. Novell:Startup:1.0.0=Novell:StartupDirectory:1.0.0 Novell:SYS:1.0.0=Novell:SYSDirectory:1.0.0,Novell:ETCDirectory:1.0.0,Novell:P ROFINST_NODE:1.0.0 Novell:DriverFiles:1.0.0=Novell:LANFiles:1.0.0,Novell:SBDFiles:1.0.0 Novell:NDPS Server Files:1.0.0=Novell:NDPS System:1.0.0,Novell:NDPS Public:1.0.0 Novell:Products:1.0.0=Novell:NICIInstall:1.0.0 Novell:NICIInstall:1.0.0=Novell:NICIModule:1.0.0 Novell:NWUpdateGroup:1.0.0=Novell:NWUpdate:1.0.0 NOTE: You can add more lines according to your needs, but these represent the minimum information that must be included in the [Selected Nodes] section.
  • Page 278 Web Services bundle plus WebSphere* Application Server. To specify a custom bundle of Additional Products and Services, do not include this key, and specify each product as described below. Novell:Products:1.0.0 = <strings separated by commas> Default Novell:NICIInstall:1.0.0 NOTE: This NICI install string must be included.

  • Page 279: Installing Multiple Products On A Server

    Product Keys and Values In addition to identifying the product in the Novell:Products:1.0.0 key, each product has its own keys and values for the [Selected Nodes] section. These keys and values for each product are listed below. We recommended that you reuse a response file from a previous installation rather than attempting to type these keys and values into the file.

  • Page 280: Additional Services

    Novell:PKIInstall:1.0.0=Novell:PKIModule:1.0.0,Novell:NICIModule:1.0.0 Novell:PKIModule:1.0.0=Novell:PKIFiles:1.0.0 Novell Internet Access Server Novell:RAS:4.1.0=Novell:RAS Server Files:1.0.0,Novell:SVCDEF_NODE:1.0.0,Novell:SupportedOS:1.0.0,Novell:UpgradeF rom:1.0.0 Novell:RAS Server Files:1.0.0=Novell:RAS System Connect:1.0.0,Novell:RAS System Connect Scripts:1.0.0,Novell:RAS Public:1.0.0 Storage Management Services Novell:SMS:1.0.0=Novell:SMSFiles:1.0.0 Novell:SMSFiles:1.0.0=Novell:SMSSystemFiles:1.0.0,Novell:SMSPublicFiles:1.0.0 Novell DNS/DHCP Services No additional keys and values are used for the installation of this service.
  • Page 281 adminID = <string> Default (none) Values (NDS distinguished name) Key Required Example adminID=.CN=admin.O=install Purpose Identifies the Admin name and NDS context; this should correspond with the Admin Login Name and Admin Context identified in the NWI:NDS section of the response file. Note the case of the characters in the string.
  • Page 282 [Novell:DNS_DHCP:1.0.0] Section Prompt = <string> Default None Values true or false Key Required Example Prompt=false Purpose Controls whether the DNS/DHCP configuration screen is displayed. TreeName = <string> Default (none) Values (text) Key Required Example TreeName=Novell Purpose Specifies the NDS tree name in which DNS/DHCP Services will be installed.
  • Page 283 ExtendDNIPSchema = <string> Default (none) Values true or false Key Required Example ExtendDNIPSchema=true Purpose Controls whether the schema is extended for DNS/DHCP Services. Note that this should be set to true. LocatorNDSContext = <string> Default (none) Values (NDS distinguished name) Key Required Example LocatorNDSContext=O=install...

  • Page 284: Cd Boot And The Response File

    In addition to the DNS/DHCP keys identified above, there must also be a line in the [Settings] section with the entry: Novell:DNS_DHCP:1.0.0= CD Boot and the Response File There are two options available for passing a response file into the NetWare installation: using the /RF switch at the command line, or from the Install Options screen.

  • Page 285: [Nwi:install Script] Section

    There are two places in the NetWare installation where you can use install scripts: At the end of the preliminary file copy (just prior to the launching of the graphical portion of the install). An install script executed here can be used for copying files from the DOS partition to the SYS volume.
  • Page 286 If the support pack image is on a remote server, use this path: Support Pack script=prv- athena\images:nw5\cobra\sp1 128.524\spack.ips TRANSPORT=IPX u="SITESTER2" a=01010155:000000000001:0451 DS c="CN=SITESTER2.OU=INSTALL.OU=DEV.O=NOVELL" z=PRV-ATHENA-TREE e=C:\err.log s=PRV- ATHENA\IMAGES:NW5\COBRA\SP1 128.524 Purpose Identifies the filename and path of an Install Script that will be executed at the end of the install.

  • Page 287: Performing A Factory Install

    Performing a Factory Install A Factory Install can reduce the complexity and time spent on an installation. Much of the hardware configuration and file copy is done in the Factory so that you only need to use the graphical portion of the NetWare installation to complete the on-site configuration.

  • Page 288: [Nwi:factory] Section

    [NWI:Factory] Section Preinstall = <string> Default True Values True or False Key Required Example Preinstall = True Purpose Controls whether the Factory Install option of the NetWare installation is invoked. If Preinstall=True, the remaining keys are checked. Copy Products to SYS = <string> Default False Values...

  • Page 289: [Novell:startupdirectory:1.0.0] Section

    [Novell:StartupDirectory:1.0.0] Section Precopy = <string> Default True Values True or False Key Required Example Precopy = True Purpose Controls whether the files in the \STARTUP\NLS directory of the install image and destined for the C:\Startup_Directory\NLS directory are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine.

  • Page 290: [Novell:configdirectory:1.0.0] Section

    [Novell:ConfigDirectory:1.0.0] Section Precopy = <string> Default True Values True or False Key Required Example Precopy = True Purpose Controls whether the files in the \CONFIG directory of the install image, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine.

  • Page 291: [Novell:sbdfiles:1.0.0] Section

    [Novell:SBDFiles:1.0.0] Section Precopy = <string> Default True Values True or False Key Required Example Precopy = True Purpose Controls whether the files in the \DRIVERS\SBD directory of the install image, destined for the SYS:SYSTEM directory, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine.

  • Page 292: [Novell:rconjzip:1.0.0] Section

    [Novell:Rconjzip:1.0.0] Section Precopy = <string> Default True Values True or False Key Required Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine.

  • Page 293: [Novell:beanszip:1.0.0] Section

    [Novell:beanszip:1.0.0] Section Precopy = <string> Default True Values True or False Key Required Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine.

  • Page 294: [Novell:scripteszip:1.0.0] Section

    [Novell:scripteszip:1.0.0] Section Precopy = <string> Default True Values True or False Key Required Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine.

  • Page 295: [Novell:ldapzip:1.0.0] Section

    [Novell:ldapzip:1.0.0] Section Precopy = <string> Default True Values True or False Key Required Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine.

  • Page 296: Install Command Line Options

    Install Command Line Options The following command line options that can be used when initiating the installation executable. /SERVER_LOG = <string> Default (none) Values (existing DOS path up to 255 characters) Key Required Example Install /LOG=C:\TMP\ERROR.LOG Purpose Designates where an installation log file will be created. /IIPX <decimal number>...
  • Page 297 100 Other Installation Options...

  • Page 298: Installation Scripts For Netware

    Novell may discontinue or decline to support any software feature described within this document at any time.

  • Page 299: Launching A Script File

    Launching a Script File At the server console, enter NWCONFIG.NLM. Click Products Options on the Configuration Options screen. Click Other Installation Actions menu > Install a product not listed. Press F3, and then specify the directory path to the script file. The directory path is first checked for an .IPS file.

  • Page 300: Descriptors And Commands

    Descriptors and Commands This section describes the descriptors and commands found in NETMAIN.ILS and other installation script files. The product installation script files you write contain the same types of descriptors and commands as those in NETMAIN.ILS. A descriptor is a keyword preceded by the @ character. The installation NLM scans the descriptors and uses them to build linked lists and menus in memory.

  • Page 301: Comments

    ANSI escape sequences are recognized by the parser within double or single quotes. For example, '\\', "\n", and '\t' represent a backslash, a new line, and a tab, respectively. A NULL character (ASCII value 0) is not allowed anywhere in the file. Comments Syntax ;...
  • Page 302 @DeletePartition Syntax @DeletePartition <comma-separated list of partition types> Description @DeletePartition deletes the existing partitions that you specify. In contrast, the installation NLM’s automatic partition creation deletes (by default) existing partitions of the first two types listed below. In both cases, all active partitions are left untouched.
  • Page 303 @Driver @EndDriver Syntax @Driver Help: “Help description for finding drivers” [Dir: <DSK | LAN>, <subdirectory name>, <vol label>, <disk description>] [Dir: <DSK | LAN>, <subdirectory name>, <vol label>, <disk description>] @EndDriver Description @Driver specifies help for finding drivers in maintenance-mode installations, or finding disks and directories that contains drivers.
  • Page 304 Example @Driver Help: “If installing from a floppy, disk drivers will be on disk NetWare-2 and LAN drivers will be on disk NetWare-3. If installing from CDROM, all drivers will be in the directory <cdrom drive>:\NW40\SERVER\DRIVERS.” Dir: DDSK, '', 'NETWARE-2', 'NetWare-2' Dir: LAN, '', 'NETWARE-3', 'NetWare-3' @EndDriver Disk NetWare-2 will be scanned for .DSK and .DDI files;...
  • Page 305 Class specifies how the fileset will be used: File Action MANDATORY Always executed. CORE Always copied in a sequential install, but optionally copied in the selective install/maintain mode. OPTIONAL Displayed to the user for selection. They are defaulted to on (selected for copy). OPTIONAL_OFF Displayed for the user to choose, but are defaulted to off.
  • Page 306 For a DOS file: Attribute1 Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Volume Label For a NetWare file: Attribute1 Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Execute 00000010 Subdirectory 00000020 Archive 00000080 Shareable 00000700 Smode 00001000 Transaction 00004000 Read Audit...
  • Page 307 The meaning for Attribute2 is 00000001 (do not decompress or process file). The default for Attribute2 is zero, which should be used in all usual circumstances. Flag Meaning 00000001 Do only for a custom install. 00000002 Do in first-phase copy (bit reset = second-phase). 00000004 Do only if NetWare for OS/2*.
  • Page 308 @IncludeFile @EndIncludeFile Syntax @IncludeFile File: <filename> [DiskDescription: “...[disk description]...”] [DiskVolume: 11 char vol name>] @EndIncludeFile Description @IncludeFile specifies a file (<filename>) with additional commands to parse and execute. DiskDescription specifies the printed name on the media that shows where the include file is located; DiskVolume is the corresponding media volume name.
  • Page 309 @MessageFile @EndMessageFile Syntax @MessageFile File: <filename> [Version: <message file version number>] @EndMessageFile Description @MessageFile specifies a file, usually with the extension .MSG, containing message strings. It is typically located in the same directory as the script file or in an NLS subdirectory. When <message file version number> name variables are encountered when the remainder of the script file is parsed (including @Include files), the symbols are substituted with definitions from the message file.
  • Page 310 [AppAdminNotes: “...Text...”] [AppFaultTolerance: <List of fallover apps>] [AppLoadBalancing: <List of load balancing apps>] @EndAppObject Description ® Use @StartAppObject to create NDS objects for use with the Novell Application Launcher (NAL) product. It is used with NetWare for Small Business. Variable Description...
  • Page 311 Variable Description AppContact The list of usernames to contact for resolving issues with the Application object. AppMapping A list of drive mappings that are made for the application to run correctly. AppIcon The filename and location of the applications icon. AppWorkingDir The startup directory for the application.
  • Page 312 Description Description is the menu description displayed for the @Other configuration option. This label must be first in the set of labels for a particular @Other option. File specifies the *.IPS file to execute, or the NLM to load to install the @Other option.
  • Page 313 If the other filename extension is .IPS, the file is assumed to be a script and is interpreted. If the other filename extension is .NLM, the file is loaded and executed as an NLM. Example @Other Description: “Install NetWare for Macintosh” DiskDescription: 'NWM System 1' DiskVolume: 'MAC-1' File: PINSTALL.NLM...
  • Page 314 @StartSchemaMod @EndStartSchemaMod Syntax @StartSchemaMod SchemaFileName: <Filename>, <Description> @EndSchemaMod Description @StartSchemaMod lets NDS schemas be extended through installation scripts. SchemaFileName specifies the filename for the schema file, along with a Description for displaying to the screen during the modification. Example @StartSchemaMod SchemaFileName: “sys:\\system\\schema\\nwadmin.sch”, “NetWare Administrator”...
  • Page 315 Standard specifies information to be displayed to the user once the time zone has been selected. This includes the time zone abbreviation and the adjust +/- x:xx:xx from GMT (Greenwich Mean Time) or UTC (Universal Coordinated Time). If Daylight exists, it specifies that daylight savings time exists for part of the year.
  • Page 316 Two time zone descriptions are displayed. When one is selected, the time parameters are filled in according to the above information, and the user can verify or edit them. @TranslateModule @EndTranslateModule Syntax @TranslateModule <old driver name1>,<new driver name1>, <old driver name2>,<new driver name2>, @EndTrandlateModuel Description @TranslateModule is used internally by NETMAIN.ILS.

  • Page 317: Commands

    Commands Command Syntax Command <command handler name> Description Command specifies the name of an optional command handler for commands not included in this file. The command handler name must be eight characters or less and correspond to the name of an NLM that exports external command entry points.
  • Page 318 Example CopyDriverToServer SYSTEM, '*.LAN', 'NETWARE-3', “NetWare diskette [3]” The *.LAN files are copied to the SYS:SYSTEM directory. CopyDriverToStartup Syntax CopyDriverToStartup <file_spec>, <source_volume>, <source_description> Description CopyDriverToStartup replaces driver files in the startup or boot directory (where STARTUP.NCF is) with new driver files. The source files are assumed to be those on the distribution CD (which might have been copied to a user- specified directory).
  • Page 319 <target_directory_path> is a directory path relative to SYS: where the files will be copied. <file_spec> names the files to be copied; it might be in the “directory/file” form to copy files from a subdirectory. <source_volume> specifies the name of a diskette volume label and <source_description> specifies the string used to prompt for the diskettes.
  • Page 320 Exec Syntax Exec <filename> Description Exec issues the operating system command LOAD <filename>, pauses until the child NLM unloads, then continues executing. To load from other subdirectories of the system volume besides \SYSTEM, specify a filename (SYS:/<directory>/<file> and <directory>/<file>). Example Exec MY.NLM MY.NLM will be loaded and executed.
  • Page 321 Record Type Data Delete STARTUP line (255 char max) Delete file line (255 char max) Example ProductRecord MYPROD, 1, “Description for my product” This creates a product description record for MYPROD with the quoted description. RegisterLanguage Syntax RegisterLanguage <language ID>, <language name> Description RegisterLanguage renames <language ID>...

  • Page 322: External Commands

    Example SaveLanguageFile SERVER.MSG If the current language ID is 4, SERVER.MSG in the DOS startup directory (BOOT directory) is copied to the subdirectory 4 in the DOS startup directory. Spawn Syntax Spawn <file name> Description Spawn issues the operating system command LOAD <file_name>, then the installation continues to execute.

  • Page 323: External Command Syntax

    Using this method ensures that the ICMD.NLM version in SYS:SYSTEM is the actual 4.10 version and that all built-in products that use it will work properly. The new ICMD.NLM might still be fully backward-compatible, but it has not yet been fully tested in that regard. External Command Syntax To use any of the external commands made available by the ICMD.NLM command handler, include the statement command [<filepath>] ICMD in the...
  • Page 324 Description AppendFile appends the contents of the source file onto the destination file. It creates a temporary file that is as large as the destination file, then renames that file to the destination file. Wildcard characters for <src file spec> are not allowed.
  • Page 325 CheckFile Syntax CheckFile <var name>, <file spec>, <vol name>, <description> Description CheckFile checks for the existence of <file spec> at a path determined by the value of <var name>. If the path is a floppy, and <vol name> is non-null (not ''), the user will be prompted for disk <description>...
  • Page 326 and time services information. The existing AUTOEXEC.NCF on SYS:SYSTEM is overwritten. Console Syntax Console <text>, <delay in seconds> Description Console enters the text on the system console screen and delays <delay in seconds> before returning control back to the calling process. Because the system installation process executes in a different thread from the console, it is possible that the next command might finish before this Console command does.
  • Page 327 <directory flag> (0|1|2|3) Value Description Source is a file. Source (including <src file spec>) is a directory; copy directory contents to destination. Source and the destination are files (file-to-file copy). <recurse flag> must be 0 if <directory flag> is 2 Source (including <src file spec>) is a directory;...
  • Page 328 <attributes> For a DOS file: Attribute Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Volume Label For a NetWare file: Attribute Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Execute 00000010 Subdirectory 00000020 Archive 00000080 Shareable 00000700 Smode 00001000 Transaction 00004000...
  • Page 329 Reserved path names (<src|dest var name>) are NWSRC, NWDST and NWBOOT, the standard source, destination and boot path for NetWare files. <dest dir name> can be a null string. <conditional copy flag> Value Description 0 (or not present) Unconditionally copy this file. Copy if destination file is not present.
  • Page 330 CopyFloppyImage Syntax CopyFloppyImage <floppy type flag>, <diskette name>, <src var name>, <src file spec>, <src vol name>, <src descr>, <dest var name>, <dest dir>, <dest vol name>, <dest descr> Description CopyFloppyImage copies a diskette image file sector by sector to the specified drive (destination path which must be a diskette drive).
  • Page 331 DiskReset Syntax DiskReset <var name> Description DiskReset tells DOS to rescan the directories on the <var name> floppy drive. This is necessary because the drive change interrupt is disabled while NetWare has control. Example Assuming myDir corresponds with A:\ DiskReset myDir Drive A:\will be rescanned.
  • Page 332 Example GetPath sys, 1, 'SYS:', '' Display_Text_File sys, “license.txt”, ccode The completion code will return a 0 (zero) for a successful return. Anything else is an error. Display Syntax Display <0|1|2>, “...<text>...” Description Display displays a message, accompanied by a beep if the first argument is 1. If the argument is 2, the message is displayed as a copy status.
  • Page 333 Time services will be installed with this server as a secondary server using existing tree name URSA. Directory services will be installed, with this server in container O=Novell. This server will have a replica installed, and its bindery will be upgraded.
  • Page 334 EraseFile Syntax EraseFile <directory flag>, <var name>, <file spec>, <vol name>, <vol descr> Description EraseFile recursively erases the file or directories indicated in <file spec>. Wildcards are acceptable. In NetWare, files can be removed no matter what their attributes; in DOS, only normal files can be removed. IMPORTANT: Use this command with care to delete only the intended data.
  • Page 335 Example GetPath startup, 1, 'C:\\NWSERVER', '' EditNCF_KEYSTRING '' EditNCF_KEYSTRING 'PK411.NLM' EditNCF startup, 'startup.ncf', 'bak', ccode The contents of C:\NWSERVER\STARTUP.NCF will be searched for a line containing PK411.NLM and will be commented out by the EditNCF command. Ccode will contain the following: 0 - Success 1 - Duplicate Extension 2 - Open Error...
  • Page 336 EditNCF_KEYSTRINGS Syntax EditNCF_KEYSTRINGS <keystring> Description EditNCF_KEYSTRINGS defines a list of keystrings to be used by EditNCF when determining which lines to comment out. (A line will be commented out if it contains any of the keystrings). NOTE: The list must be terminated with a null string (empty quotes) for the last entry.
  • Page 337 The variable version contain the string “v2.11”. ExtractVersionNumbers returns a value of 2 in the variable major, a value of 11 in the variable minor. And a value of 0 in the variable revision. FileVersion Syntax FileVersion <src var name>, <src file spec>, <src vol name>, <src descr>, <Module major number>, <Module minor number>, <Module rev number>, <Module description>, <return code>...
  • Page 338 GetPath Syntax GetPath <var name>, <path type>, <default>, <prompt>, [<base var name>] Description GetPath prompts the user for a path using the prompt. The prompt string will be displayed, with “%s” (like C-language print formatting) being replaced by the <default> string. The keystrokes to modify will be added to your prompt.
  • Page 339 Goto Syntax Goto <label_name> Description Goto causes execution to continue at the first occurrence of label <label_name>. The scope of a label is always local to a file set. Therefore, a Goto statement cannot transfer execution to a file set different from the current one. Example Goto Done Label Done...
  • Page 340 GotoIfNEqual GotoIfGreater GotoIfLess GotoIfGrEqual GotoIfLsEqual Syntax GotoIfNEqual <arg1>, <arg2>, <label_name> GotoIfGreater <arg1>, <arg2>, <label_name> GotoIfLess <arg1>, <arg2>, <label_name> GotoIFGrEqual <arg1>, <arg2>, <label_name> GotoIfLsEqual <arg1>, <arg2>, <label_name> Description These are identical to GotoIfEqual (page 142), except that execution branches only if (respectively): <arg1>...
  • Page 341 IsSubString Syntax IsSubString <string>, <substring>, <index> Description IsSubString returns the zero based <index> of <string> where <substring> starts, if <substring> is indeed contained within <string>, otherwise <index> is -1. Example IsSubString ‘Little Miss Muffet sat on’, ‘Miss Muffet’, index In this example, <index> would return as 7. Label Syntax Label <label_name>...
  • Page 342 Description LangVar sets a variable to the number of a language. It starts with <src var dir name>, then it looks for a subdirectory whose name is a number that matches the current server language number. If the subdirectory is found, <lang var> is set to that number;...
  • Page 343 NLMExec NLMExecIO Syntax NLMExec <block flag>, <command line> Description NLMExec executes the NLM specified by <command line>. If <block flag> is 1, NLMExec waits for the NLM to complete execution, then continues. NLMExec is the external command version of the Exec (page 123) command.
  • Page 344 PromptForCD Syntax PromptForCD <CD Volume Name>, <seconds to mount> Description PromptForCD is to be used with DisMountCD (above). PromptForCD will prompt the user to insert the CD labeled <CD Volume Name> into the CD drive and then will attempt to mount the CD volume within the <seconds to mount>...
  • Page 345 This command is the counterpart to the ProductRecord command. See “ProductRecord” on page 123 for more information on record types. Example ReadProductRecord MYPROD, 0, version, ccode The command will search the products database and return the value for <version> for product 'MYPROD'. Read_Var_File Syntax Read_Var_File <path>, <filename>, <completion code>...
  • Page 346 indicates normal attributes. If the <0|1> argument is 1, the server container object (or everyone) is given <rights> rights to the directory. Example If myDir corresponds to VOL1:\ SetDir myDir, DOC, '', '', 10, 1, 0 The directory VOL1:\DOC will be created and all applicable users will have rights to it.
  • Page 347 SetLConfigLang Syntax SetLConfigLang <value> Description SetLConfigLang looks for the LCONFIG.SYS file in the server boot directory. The default server language ID number is changed to <value>. Example SetLConfigLang 9 The default server language ID number in the LCONFIG.SYS file is changed to 9 (Japanese).
  • Page 348 SGotoIfEqual SGotoIfNEqual SGotoIfGreater SGotoIfLess SGotoIfGrEqual SGotoIfLsEqual The SGotoIf commands have the same options as the GotoIf commands. The SGotoIf commands perform a string comparison instead of an integer comparison. SpaceCheck Syntax SpaceCheck <path var name>, <value> Description SpaceCheck looks at <path var name>. If it matches a NetWare volume, SpaceCheck checks whether the volume is large enough for <value>...
  • Page 349 SrchNCF Syntax SrchNCF <ncf path var>, <ncf file name>, <keystring>, <foundline var name> Description SrchNCF searches an .NCF file for line containing a substring matching <keystring> (non case-sensitive). If found, the line of text will be returned; otherwise <foundline var name> will be empty. NOTE: The same value as not found will be returned if an error is encountered (for example, invalid filename, read error, etc).
  • Page 350 Volumes Syntax Volumes <minimum vol SYS: size in sectors> Description Volumes creates and mounts volumes on this server, with the volume SYS: placed on the first device larger than <minimum volume SYS: size in sectors> (512 bytes per sector). Additional volumes, named “VOL1”, “VOL2”, etc., will be created on other devices, one per device.

  • Page 351: External Command Programming Interface

    part of the variable name and must be included with the variable when referencing it later. If the filename doesn't exist, it will be created. The varname and var value will then be written. If the file does exist, the varname and var value will be appended to the contents of the file.

  • Page 352: Icmdgetvar

    ICMDGetVar Use the ICMDGetVar function to get the value of a script variable. Function int ICMDGetVar (char *variableName, char *variableValue) *variableName: Pointer to name of variable *variableValue: Buffer containing value of variable; must be at least 128 bytes Return 0 if successful; non-zero error code if unsuccessful or if variableName does not exist.

  • Page 353: External Command Variable Substitution

    External Command Variable Substitution A variable, such as the value returned by GetPath (page 141), can be used inside any quoted string within an executed external command. The variable is global. It goes out of scope only when the command processor is replaced by a different one.

  • Page 354: Example

    All path variables, including the predefined ones, allow subfield specifiers in the form <path var>.<specifier>. <path var> <specifier> PATH String containing the actual path. Disk volume name. PROMPT Disk volume prompt. TYPE Path type. SUBTYPE Path subtype. CONN Connection number (hex). ENGINE Engine number.

  • Page 355: Installation Nlm Command Line Options

    Installation NLM Command Line Options Command line options can be preceded by '-', but this is not required. IMPORTANT: These options are not intended for general distribution; they apply only to the NetWare installation NLM. Other Switches are not guaranteed to be supported in all versions.

  • Page 356: Other Switches

    Other Switches Switch Description MDEBUG Memory debug. TRANSPORT Transport layer type. (IPX is the default). Source path remote context. Specifies that NDS authentication will be used. If command is not present, the connection is made through the bindery. Front end flag. Q simplified mode T calculate file set totals V suppressed delayed init (DELAY)

  • Page 357: Netware 4.1 Remote Installation Wrapper

    NetWare 4.1 Remote Installation Wrapper You can use NetWare installation to remotely install a product that was not originally intended for remote installation. Create a wrapper script that copies the associated files to the server before executing PINSTALL.NLM. Make sure the system volume is large enough to contain the scratch files, even in local install cases.

  • Page 358: Netware Installation Command Version Availability

    NetWare Installation Command Version Availability The following tables list the available NetWare installation and external installation commands. NetWare Install Commands Command NetWare 4.10 NetWare 4.11 NetWare for Small NetWare 5 and Business NetWare 6 @CDName @DeletePartition @Driver @FileSet @IncludeFile @MessageFile @Other @StartAppObject @StartSchemaMod...

  • Page 359: Netware External Install Commands

    Command NetWare 4.10 NetWare 4.11 NetWare for Small NetWare 5 and Business NetWare 6 Exec ProductRecord RegisterLanguage SaveLanguageFile Spawn NetWare External Install Commands Command Version of ICMD.NLM 2.00 2.18 3.20 3.25 Activate AppendFile CheckFile Config Console CopyFile CopyFloppyImage Delay DiskReset Display_Text_File Display DSInst...
  • Page 360 Command Version of ICMD.NLM 2.00 2.18 3.20 3.25 EditNCF_Keystrings EraseFile ExtractVersionNumbe GetDOSServer GetPath Goto GotoIfEqual GotoIfNEqual GotoIfGreater GotoIfLess GotoIfGrEqual GotoIfLsEqual Is_NLM_Active Label LangVar Menu NLMExec NLMExec_IO Partitions Quit ReadProductRecord Read_Var_File Installation Scripts for NetWare 163...
  • Page 361 Command Version of ICMD.NLM 2.00 2.18 3.20 3.25 SetDir SetDOSServer SetLConfigLang SetVar SgotoIfEqual SgotoIfNEqual SgotoIfGreater SgotoIfLess SgotoIfGrEqual SgotoIfLsEqual SpaceCheck SrchNCF ValueAdd ValueSet Volumes Write_Var_File 164 Other Installation Options...
  • Page 362 Novell NetWare Migration ® Wizard 6 w w w . n o v e l l . c o m A D M I N I S T R AT I O N G U I D E...
  • Page 363 Creating a Template Object ........11 Run Novell NetWare Migration Wizard....... 12 Model Your Migration Project .
  • Page 364 Migrate Users and Data to the Destination NDS Tree..... . . 46 Perform Post-Migration Tasks ........50 Troubleshooting General Connection Problems .

  • Page 365: Netware Migration Wizard 6 Administration Guide

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. NetWare Migration Wizard 6 Administration Guide...
  • Page 366 NetWare Migration Wizard 6 Aministration Guide...

  • Page 367: Migrating Data From Netware 3

    Windows NT 4.0/2000 Workstation To migrate data from NetWare 3, complete the following tasks in the order they are listed. “Meet System and Software Requirements” on page 10 “Run Novell NetWare Migration Wizard” on page 12 Migrating Data from NetWare 3...

  • Page 368: Meet System And Software Requirements

    The Windows NT/2000 workstation must be running Novell Client for Windows NT/2000 version 4.8 or later. To check your current Novell Client version, right-click the N icon on the workstation toolbar, and then click Novell Client Properties > Client. If...

  • Page 369: Preparing The Source Server

    Preparing the Source Server The source server is the existing server that contains the data that will be copied to the destination NDS tree. The source server must be running NetWare 3.11 or later. Load the following NLM program at the server console of each NetWare 3 source server that you are planning to migrate: For NetWare 3.11, load TSA311.NLM For NetWare 3.12 and 3.2, load TSA312.

  • Page 370: Run Novell Netware Migration Wizard

    Run Migration Wizard from the location where you installed it. The installation program, by default, installs Migration Wizard at this location: Start Menu > Programs > Novell > Netware Migration Wizard > NetWare Migration Wizard. Read the Welcome screen and click OK.
  • Page 371 Name your migration project, choose a place to save it, and then click Next. By default, Migration Wizard saves your project in C:\Program Files\Novell\NetWare Migration Wizard. Select the source servers that you want to migrate. Only servers that you are already logged in to appear in the Selected Servers text box.
  • Page 372 any changes, Migration Wizard will automatically merge the NetWare 3 user with the displayed NDS user. Figure 1 Merging Your NetWare 3 Users with Duplicate NDS Users You have the following options for each NetWare 3 user: Merge the NetWare 3 user with the displayed NDS user Simply leave the NetWare 3 user displayed as it is in the table and continue with the next user.

  • Page 373: Model Your Migration Project

    Once you have made a decision for each listed NetWare 3 user, click Finish. The NetWare 3 users that you chose to merge with NDS User objects appear automatically as dropped objects in the destination NDS tree. Continue with the next section, "Model Your Migration Project."...
  • Page 374 Figure 2 Using the Project Window Dialog Box The three basic steps outlined in this dialog box should be performed for each migration project. Once you are familiar with the tasks that you will be performing, click Close to access the Project Window and begin modeling your migration.

  • Page 375: Verify Your Migration Project

    NLM files that Migration Wizard prompts you to. After copying the NLM files, reboot the NetWare 3 source server and launch Migration Wizard again. The Products\NW3X directory is located in the same directory where Migration Wizard was installed (C:\Program Files\Novell\Novell NetWare Migration Wizard\Products\NW3X). Read the Welcome Screen and then click Next.
  • Page 376 If prompted, select what volume you want to migrate your NetWare 3 print queue volume to, and then click Next. If you want to apply a Template object to newly created users, browse the tree, select the Template object from the tree view and then click Next. If you do not want to use a Template object, uncheck the check box and click Next.
  • Page 377 Click Next to verify that you have enough disk space on the destination volume to accommodate your NetWare 3 file system. Migration Wizard will also scan the contents of all dropped folders and verify that you have sufficient rights to migrate them. If prompted, resolve any naming conflicts between different-type objects, and then click Next.

  • Page 378: Perform Post-Migration Tasks

    Make sure that applications have migrated correctly. After migration, if you want to install additional network products and services, you can do so from the servertop by clicking the Novell icon > Install. Make sure that each migrated user has the correct Novell Client properties to log in to the destination NDS tree.

  • Page 379: Migrating Data From Netware 4, 5, Or 6

    ® When you migrate data from a NetWare 4, NetWare 5, or NetWare 6 source ® server to a NetWare destination server, Novell NetWare Migration Wizard 6 ® copies the file system and NDS database from the source server to the newly installed NetWare destination server.

  • Page 380: Meet System And Software Requirements

    IMPORTANT: NetWare Migration Wizard 6 does not run on Windows 95 workstations. The Windows NT 4/2000 workstation must be running Novell Client for Windows NT version 4.8 or later. If migrating from NetWare 4, the IPX protocol should be configured on your Novell Client workstation.

  • Page 381: Preparing The Destination Server

    (Conditional) If you are migrating data from NetWare 4, make sure that the source server’s volumes are running long name space support on all volumes to be copied. To add long name space support to a NetWare 4.11 or NetWare 4.2 volume, enter the following at the server console: LOAD LONG and then ADD NAME SPACE LONG TO volumename.
  • Page 382 For instructions on installing NetWare 5, see the NetWare 5 Overview and Installation Guide (http://www.novell.com/ documentation/lg/nw5/docui/index.html). Make sure that you select the New Server option on the Additional Products and Services screen during the NetWare 5 installation, and deselect all products except SMS.

  • Page 383: Run Migration Wizard

    Run Migration Wizard from the location where you installed it. The installation program, by default, installs Migration Wizard at this location: Start Menu > Programs > Novell > Netware Migration Wizard > NetWare Migration Wizard. Read the Welcome screen and click OK.

  • Page 384: Copy Volumes

    Copy Volumes In the Project Window, click Copy Volumes. Before Migration Wizard starts copying files, it backs up your directory and file trustees and saves them in files located on the source and the destination server. Once the NDS migration is complete, Migration Wizard restores the trustees from the files it stored on the destination server.
  • Page 385 directories, Migration Wizard migrates them to the SYS:SYS.MIG directory on the destination server. If there are files in the source server’s SYS: directories that you want to utilize on the destination server, after the NDS migration is completed, copy the files from the SYS:SYS.MIG directory into the appropriate SYS: directory on the destination server.

  • Page 386: Edit Configuration Files

    Edit Configuration Files In the Project Window, click Edit Configuration Files. Migration Wizard lets you modify any .NCF or .CFG files on the destination server. These files contain default LOAD statements and parameters. IMPORTANT: If you are editing your AUTOEXEC.NCF, make sure the file is closed before you migrate your NDS database.

  • Page 387: Begin Nds Migration

    Begin NDS Migration In the Project Window, click Begin NDS Migration. Back up all volumes that you are not planning to migrate and complete the following tasks before continuing: Make sure all volume data migrated successfully. Make sure all critical errors from the file copy are resolved. Make sure the servers in your source NDS tree are in time sync and that NDS is synchronized.
  • Page 388 IMPORTANT: If you are getting NICI errors when NDS is trying to load or when you are copying the NICI files, you should first check and see if PKI.NLM will load on the destination server. If PKI.NLM won’t load, see “NICI Errors”...

  • Page 389: Finish Nds Migration

    Reboot your workstation and log in to the former destination server. If you can’t log in, refer to “Workstation-to-Server Connections” on page Continue with the next section, "Finish NDS Migration." Finish NDS Migration In the Project Window, click Finish NDS Migration. Read the Continue NDS Migration screen and make sure that The former destination server has restarted and taken on the name and identity of the source server...

  • Page 390: Perform Post-Migration Tasks

    NDS objects to the NDS tree. If your destination server was running NetWare 5.1, you might see warnings on your server referring to SMS, LDAP, Novell Certificate Server, or NetWare Management Portal. Just ignore the warnings and reinstall the products after NDS has been migrated.

  • Page 391: Migrating Data From Windows Nt

    Migrating Data from Windows NT ® ® Novell NetWare Migration Wizard 6 automates key tasks, such as migrating users and their file permissions, assigning passwords, and migrating ® the NT file system to a designated NDS tree. This automation eliminates the need to choose from various utilities that would help you perform these tasks individually.
  • Page 392 This information will help you decide which NT servers to migrate first and how many servers you will need to migrate at one time. When you migrate your users and groups, you will want to migrate all files and directories that they have access to at the same time that you migrate their User objects.

  • Page 393: Meet System And Software Requirements

    Do you have any trusted domains? If so, you must reassign any trusted domain permissions to the appropriate NT user and groups after the migration is complete. Use ConsoleOne to reassign all lost trusted domain permissions. Once you have planned your migration, you’re ready to begin your NT migration.

  • Page 394: Perform Prerequisite Tasks

    Packs, see the ZDNet Web site (http://updates.zdnet.com/products/ pr_13616.htm). To check your current Novell Client version, right-click the N icon on your workstation and click Novell Client Properties > Client. To download the Novell Client, see the Novell Download Web site (http://www.novell.com/ download).

  • Page 395: Creating Zenworks User Policy Packages

    If there is a conflict between the properties of a Template object and an NT policy, the properties of the Template object will, in most cases, take priority. For example, if a minimum password length of seven characters is specified for user Jeff in an NT policy and a minimum password length of nine characters is specified in the Template object, then when Jeff’s object is migrated, the object will be created in NDS with a password length of nine...

  • Page 396: Registering The Workstation

    In ConsoleOne, click the user policy package icon in the toolbar. If you don’t know which icon it is, mouseover the icons to see a short description. For more information about installing and using ZENworks, see the Novell Product Documentation Web site (http://www.novell.com/documentation). Registering the Workstation If you are running Migration Wizard from a workstation, make sure that the workstation is registered within the domain that you want to migrate.

  • Page 397: Run Migration Wizard

    Launch Migration Wizard from the Start menu by clicking Programs > Novell > NetWare Migration Wizard > NetWare Migration Wizard. Click Create a New Project > OK. Click Microsoft Windows NT 3.51/4 Server > OK.
  • Page 398 The destination NDS tree is the NDS tree that you want to migrate your NT data to. If you are not logged in to your NDS tree, the NDS tree name will not appear in the drop-down list. If this is the case, click the Browse button to log in to your NDS tree.
  • Page 399 Figure 3 Merging Your NT Users with Duplicate NDS Users You have the following options for each listed NT user: Merge the NT user with the displayed NDS user. Simply leave that user as it is displayed in the table and continue with the next listed NT user.

  • Page 400: Model Your Migration Project

    Model Your Migration Project Most of your work will be done in the Project Window, where you can drag and drop NT User and Group objects into NDS containers, and NT folders and volumes into any volume or folder in the destination NDS tree. The Project Window is a place to model different migration scenarios before you begin the actual migration without affecting your NT domain or your destination NDS tree.
  • Page 401 performing, click Close to access the Project Window and begin modeling your migration project. Using the Project Window Review the following tips to help you organize your migration project and use the Project Window more effectively. Creating a New NDS Organizational Unit or Folder—To create a new NDS Organizational Unit (OU), right-click the parent NDS Organizational Unit or folder and then click New Organizational Unit or New Folder.
  • Page 402 Uppercase and lowercase letters, underscores, and spaces are not acknowledged by NDS. For example, Manager_Profile and MANAGER PROFILE are considered identical names in NDS. Setting the Context—To set the context, right-click an NDS Organizational Unit and then click Set Context. When you set the context, you can designate what part of the NDS tree will appear in the right side of the Project Window.

  • Page 403: Verify Your Migration Project

    Finding Out Where a Dropped NT Object Came From—To find out where a dropped object was located in the NT domain, right-click an NT object and then click Where Did It Come From? When dragging and dropping a large number of objects, this will help you remember where a dropped object was previously located in the NT domain.

  • Page 404: Migrate Users And Data To The Destination Nds Tree

    Migrate Users and Data to the Destination NDS Tree Although you have selected the volumes and containers where the NT data will be copied, no data has yet been migrated. When migrated, NT User objects are converted to NDS objects and placed in the destination NDS tree. To begin the migration, do the following: From the Migration Wizard toolbar, click Project >...
  • Page 405 Review the NT groups that you chose to associate with specific ZENworks User Policy Packages, and then click Next. If you want to change an association, click Back and follow the instructions in Step HINT: This screen will not appear if you are using ZENworks 3.0. Decide how you want to handle any duplicate filenames between the Microsoft NT domain and the destination NDS tree.
  • Page 406 Everyone permissions, be sure to drop the NT Domain Info object high enough in the NDS tree so that all NT users will inherit those permissions. HINT: Every new folder that is created in the NT domain automatically receives the Everyone permissions by default. Restart Option—Normally, this information is not erased;...
  • Page 407 If prompted, verify that you do not want to migrate the listed NT users and groups, and then click Next. This procedure must be done three times—once for all your NT local groups, NT global groups, and NT users that were not dragged and dropped into the destination NDS tree.

  • Page 408: Perform Post-Migration Tasks

    Perform Post-Migration Tasks After you’ve migrated your NT data to the destination NDS tree, complete the following tasks: Install the latest Novell Client software on any workstations that it was not previously installed on. You can download the client from the...

  • Page 409: Troubleshooting

    Troubleshooting Refer to the appropriate section if you are having trouble with any of the following: General Connection Problems (page 51) Workstation-to-Server Connections (page 52) Server-to-Server Connections (page 53) File Copy (page 53) SMDR Errors (page 54) Restoring Trustees (page 54) NUWAGENT.NLM (page 55) NICI Errors (page 55) NDS Migration (page 56)

  • Page 410: Workstation-To-Server Connections

    Search for the server by its IP or IPX address instead of its name. Enter the IP or IPX address in the Server field of the Novell Login dialog box. Try connecting to the server and not the NDS tree by entering only the name of the server and leaving the tree name and context blank.

  • Page 411: Server-To-Server Connections

    Server-to-Server Connections If you have problems establishing or maintaining connections between your servers, try one or more of these troublshooting suggestions: Do not remove the source or destination server from the NDS tree. The servers must be able to communicate with the other servers in the tree during the migration.

  • Page 412: Smdr Errors

    SMDR Errors Sometimes the SMDR.NLM program that is running on the destination server can’t make a connection to the source server. To correct this problem, try one or more of the following: Reboot the source server. Unbind the protocol you are not using from the destination server. For example, if you are using IPX for the migration, but IP is bound on the destination server, unbind the IP protocol on the destination server during the migration.

  • Page 413: Nuwagent.nlm

    Rename the *.NFK file that you just copied to NICIFK (this has no extension). Go to the Novell Support Web site (http://support.novell.com/filefinder) and download NREPAIR3.EXE. Extract NREPAIR3.EXE and locate NREPAIR.NLM. Run NREPAIR.NLM on the server, clicking Yes at all the prompts.

  • Page 414: Nds Migration

    NDS Migration If the migration fails during the NDS Migration step, you need to restore the source and destination servers to their original configuration before you can retry the NDS migration. The instructions for restoring the servers to their original configurations are different depending on when the migration of data failed.

  • Page 415: Remove Nds From The Destination Server

    To perform the NDS migration again, launch Migration Wizard and open the project you were previously working on. When the project opens and you see the Project Window, click the Begin NDS Migration button and follow the instructions in “Begin NDS Migration” on page Remove NDS from the Destination Server If Begin NDS Migration, button 3, successfully completed and the destination server has already rebooted and taken on the name and identity of the source...

  • Page 416: Remove Nds From The Source Server

    Directory Services again. If a message indicates that NDS is already removed, continue with the next section, "Restore NDS to the Source Server." If NDS was not properly removed, contact Novell Technical Support at 1-800- 858-4000. NetWare Migration Wizard 6 Aministration Guide...

  • Page 417: Restore Nds To The Source Server

    Restore NDS to the Source Server By removing NDS from the source server, you removed the server from any replica rings that held a partition of the source server. Now you must complete the following procedure to restore NDS to the source server. Enter one of the following at the server console: If your source server was running NetWare 4, enter LOAD INSTALL.

  • Page 418: Reinstall The Destination Server

    Enter the Admin username and password. Exit DSREPAIR. At the workstation where you performed the migration, open your project. From the Migration Wizard Tools menu, click Restore Trustees to restore the trustee assignments. If the source server held the master replica of any partitions and you want to restore these partitions prior to doing the NDS migration again, use DSREPAIR to re-create them.
  • Page 419 Novell Client for Windows w w w . n o v e l l . c o m I N S TA L L AT I O N A N D A D M I N I S T R AT I O N G U I D E...
  • Page 420 Additional Information ........16 Installing Novell Client at the Workstation ......17 Configuring Network Protocols .
  • Page 421 Uninstalling Novell Client ........
  • Page 422 Text File Usage ......... 67 Other .
  • Page 423 Software Compatibility Issues ....... . . 111 Novell Client for Windows...

  • Page 424: Novell Client Documentation

    NT*/2000 version 4.81, and Novell Client for Windows 95/98 version 3.31 and later software. If you are using a previous version of Novell Client software, you should update it to the latest version (http://www.novell.com/download). If you are using a previous version of Novell Client software, some of the information in this documentation might not apply.
  • Page 425 Novell Client for Windows...

  • Page 426: Installing Novell Clients

    This chapter explains how to install Novell Client for Windows XP, Novell Client for Windows NT/2000, and Novell Client for Windows 95/98 software on one workstation or across the network. It describes the following tasks: Preparing to Install the Client Software (page 13)

  • Page 427: Checking Server Protocols And Requirements

    Workstations using IPX Compatibility Mode cannot have an IPX internal network number configured. If you have configured an IPX internal network number on your workstation and you are planning to install the Novell IP Client with IPX Compatibility Mode, then remove the IPX internal network number before installing the client.

  • Page 428: Downloading The Latest Client Software

    ADD NAME SPACE LONG TO VOLUME volume_name Downloading the Latest Client Software Novell Client software is shipped on CD and is also available from the Novell Web site. You should install the latest version of the software. To download the latest Novell Client software, complete the following steps.

  • Page 429: Checking For Client Workstation Incompatibilities

    Windows NT/2000/XP Novell Client cannot be installed on Windows 2000 or Windows XP if the Local Area Connection Properties Page is open. Close this page before running the Novell Client install.

  • Page 430: Additional Information

    “Installing Clients from the Network” on page 19 Installing Novell Client at the Workstation If you plan to install Novell Client software on a small number of workstations, or if the workstations are not yet connected to a network, install...

  • Page 431: Configuring Network Protocols

    Once Novell Client is installed, check your network protocol configuration. “Configuring Network Protocols” on page Configuring Network Protocols After you install Novell Client, make sure that it is configured correctly for your network. WARNING: Before you configure network protocols, make sure you have the correct information and any addresses needed.

  • Page 432: Installing Clients From The Network

    The process involves six tasks: 1. Creating a folder on the server. 2. Copying Novell Client files and other required files to the new folder. Workstations can then read the files during login. 3. Granting rights to the new folder.

  • Page 433: Copying Files

    Copying Files Do one of the following: From the Novell Client CD, copy the WINNT or WIN95 directories to the new folder. If you are installing only one platform, you need to copy only the platform directory (WINNT or WIN95) for the platform you will install.

  • Page 434: Modifying The Acu Configuration File

    File setting. [ADMINISTRATOR Specifies additional text that will Message=the message you MESSAGE] appear when the user is prompted want to appear to start an ACU. Installing Novell Clients...

  • Page 435: Updating The Platform-Specific Configuration Files

    Yes in the ACU.INI file. Each platform-specific installation utility reads a configuration file generated by Novell Client Install Manager in order to configure the client properties. This file provides information such as where to copy drivers during installation and the most recent version number. This file must be placed in the same folder as the installation utility.
  • Page 436 If you are configuring Windows 95/98 workstations, options that were set in the NWSETUP.INI file or on the command line in previous versions of Novell Client (such as Display First Screen or CAB FIX) are now set up in Novell Client Install Manager.

  • Page 437: Creating Or Modifying The Login Script

    If the login script that you just created was for a Profile object, you must associate the User object with the Profile object and make the User object a trustee of the Profile object. For additional information on all login scripts, see “Creating or Modifying Login Scripts” on page Novell Client for Windows...

  • Page 438: What Users See

    #\\server1\sys\public\client\winnt\i386\acu.exe IF "%ERROR_LEVEL" = "1" THEN EXIT At this time, you cannot use a login script to install Novell Client for Windows XP version 4.82. This feature will be available in a future release. NOTE: If you are using this sample script to replace the Microsoft Client with Novell Client for Windows95/98, some user intervention is necessary.

  • Page 439: Upgrading A Client Workstation To Windows 2000

    If the Novell Client version is 4.6 or earlier, Windows 2000 installs the Novell Client version 4.51 from the Windows 2000 CD. If the Novell Client version is 4.7 or later, Windows 2000 leaves it intact but removes all installed components and changes the protocol selection.

  • Page 440: Upgrading A Client Workstation To Windows Xp

    “Installing Novell Client at the Workstation” on page Upgrading a Client Workstation to Windows XP If you are upgrading your Windows operating system on workstations that already have the Novell Client installed, you must first uninstall the Novell Client to ensure a clean upgrade. Uninstall Novell Client.
  • Page 441 Novell Client for Windows...

  • Page 442: Setting Up Client Login

    When a user successfully logs in to the network, one or more login scripts are executed which automatically set up the workstation environment. Login ® scripts are similar to batch files and are executed by the Novell LOGIN utility. You can use login scripts to map drives and search drives to directories, display messages, set environment variables, and execute programs or menus.
  • Page 443 WARNING: Don’t delete the login directory (SYS:LOGIN) created during network installation. It contains the Novell LOGIN and NLIST utilities. If users run command line utilities, they can use these utilities to log in and view a list of available NetWare servers.

  • Page 444: Where Login Scripts Should Be Located

    Where Login Scripts Should Be Located Login scripts are properties of objects. Consequently, only certain objects can contain login scripts. This, in turn, largely determines where login scripts can be located. The following figure shows how the different types of login scripts can reside in an NDS tree and how they affect users.

  • Page 445: Creating Or Modifying Login Scripts

    Before you create or modify login scripts, you must have the Write property right to the object that will contain the login script. In addition, the Organization, Organizational Unit, Profile, or User object that you plan to assign the login script to must already exist. Novell Client for Windows...
  • Page 446 To create or modify a login script using ConsoleOne, complete the following steps: Double-click the object whose login script you want to create or modify. Click Login Script. Enter the login script commands and information into the login script text box.

  • Page 447: Creating Login Scripts From A Sample Or Existing Login Script

    For sample login scripts included in this documentation, see “Sample Login Scripts” on page Copy the sample or existing login script. In ConsoleOne, open the login script, copy the sample and then paste it into the login script. Novell Client for Windows...

  • Page 448: Printing Login Scripts

    Make necessary changes to the sample login script to customize it for your network. IMPORTANT: Make sure that you edit the sample login script to match the server names, directory paths, and specifications of your own network. Click OK to save the new login script. If the login script that you just created was a container or user login script, you’re finished.

  • Page 449: Setting Up Login Restrictions

    You can create a location profile on a single workstation or you can create location profiles for multiple workstations by using the ZENworks Workstation Configuration policy packages. Novell Client for Windows...
  • Page 450 To create a location profile on a specific workstation, complete the following steps: Open the Client property pages. Right-click the N icon in the system tray and then click Novell Client Properties > Location Profiles. Right-click Network Neighborhood and then click Properties > Location Profiles.

  • Page 451: Removing A Location Profile

    Select the name of the profile that you want to remove and then click Remove. Customizing the Novell Login Dialog Box The Novell Login dialog box can be customized to show the features that you want users to have access to. Customizing gives you control over the following:...
  • Page 452 If Dialup is not installed on the workstation, the fields on the Dialup tab are disabled. If the Novell Login dialog box is being used to log in to a specific tree, the Tree field is disabled to prevent the user from changing the tree.

  • Page 453: Logging In To The Network

    We recommend that users do not use the command line LOGIN utility. There are several ways to initiate a Novell Client Login once users have already logged in to NetWare or to the local workstation: Right-click the red N icon in the System Tray and then click NetWare Login.

  • Page 454: Setting Client Properties

    HINT: A new Advanced Menu Settings tab has been added to the Novell Client Property Page. This tab lets you set menu options and control settings such as the ability to send messages to the server console or how Network Neighborhood is configured.

  • Page 455: Setting Properties On A Single Workstation After Installation

    You can set up one workstation the way you want other workstations to be set up, and then use Novell Client Install Manager to import the settings from that workstation’s registry and save them to the configuration file you will use during the ACU install.

  • Page 456: Using Dhcp

    DHCP server supplying an IP address to the client. Using DHCP Like an NDS Server Name Service Provider You can set up a DHCP server to inform Novell Client workstations that use ® the IP protocol about an NDS tree name and the IP addresses of servers that are on that tree.
  • Page 457 Novell Client for Windows...

  • Page 458: Managing Novell Client

    Novell Client desktop. Common Networking Tasks Novell Client software is integrated with Windows. Features are integrated into standard Windows interfaces such as My Computer, Network Neighborhood, Control Panel, and the N icon in the system tray.

  • Page 459: Checking File Or Folder Rights

    Combine Multiple Trustees check box on the NetWare Rights page. In Windows Explorer or Network Neighborhood, click a file. Press and hold Control while clicking additional files. Right-click the selected files. Click Properties > NetWare Rights. The Combine Multiple Trustees check box is enabled. Novell Client for Windows...

  • Page 460: Setting Up Autoadminlogon For Windows Nt/2000/Xp

    Windows NT or Windows 2000 to correct them. HINT: To bypass the AutoAdminLogon process, and to log in as a different user, hold down the Shift key after a logout or after a Windows NT restart. Managing Novell Client...

  • Page 461: Autoadminlogon Options

    DefaultDomain or Local WorkstationName=Name of DefaultLocationProfile=Name of the Location Domain or Local Workstation Profile that contains the information about the Novell User to log in to the NetWare network such DefaultUserName=Windows User Name as Username, Tree, Context, Server, etc. DefaultPassword=Windows Password for the...
  • Page 462 AutoAdminLogon=0 AutoAdminLogon=1 DefaultLocationProfile=Name of the Location Profile that contains the information about the Novell User to log in to the NetWare network such as Username, Tree, Context, Server, etc. DefaultPassword=Novell Password for the DefaultUserName specified in the Location Profile Location profiles allow you to save a user’s specific login information. The profile automatically sets up login information such as the user’s name, server,...

  • Page 463: Setting The Autoadminlogon Options

    Login AutoAdminLogon=1 DefaultLocationProfile=Name of the Location Profile that contains the information about the Novell User to log in to the NetWare network such as Username, Tree, Context, Server, etc. DefaultPassword=Novell Password for the DefaultUserName specified in the Location Profile Turn Off AutoAdminLogon...

  • Page 464: Uninstalling Novell Client

    NetWare Login does not update the Registry setting for AutoAdminLogon. Uninstalling Novell Client You can uninstall the Novell Client by using the uninstall utility or by selecting Remove in Network Properties. For Windows 95/98, double-click the uninstall utility (UNC32.EXE) located in the WIN95\language_directory\ADMIN directory.
  • Page 465 Novell Client for Windows...

  • Page 466: Printing To A Network Printer

    Users can set up network printing on a workstation by specifying the name of the printer in any of the following programs: Windows Add Printer Wizard ® Novell Capture Printer Port The following can automate printer connections so that the computer connects to network printers each time a user log in: ®...

  • Page 467: Setting Up Network Printing

    Windows 3.x application that relies on print captures and you can’t put the capture in a login script. To access the Capture Setting dialog box, complete the following steps: Right-click the N icon in the system tray. Click Novell Capture Printer Port. Novell Client for Windows...

  • Page 468: Setting Up Point And Print

    Enter the correct information in the dialog box. Click Settings. These settings apply only to printer ports that are captured from Windows. Printer ports that are captured in a login script or from the command line do not use these settings. These settings do not apply to printers that appear in the Windows Printers folder.

  • Page 469: Printing Dbcs Characters From Dos In Windows Nt/2000

    Only DOS applications can be run from this window, but anything that is printed will be rendered by the printer driver that you installed. Any DOS commands that affect the print driver must be entered in this window. DOS applications can be started by any method. Novell Client for Windows...

  • Page 470: Disabling Netware Login Dialog Boxes Brought Up By The Print Provider

    Windows NT/2000/XP has two registry setting options for disabling login dialog boxes: If you set HKLM\SOFTWARE\Novell\Print\Delay Login\Delay Login=1 the print provider tells Windows that the printer is a NetWare printer even though the user is not authenticated. Then, the provider waits for an action that requires authentication is detected before displaying a login dialog box.
  • Page 471 Printers folder, right-clicking the printer, and deselecting Print Offline. If you set HKLM\SOFTWARE\Novell\Print\Never Login\UserDialupSettings=1 the print provider sets Never Login to the dial-up connection settings and attempts to print. NOTE: This functionality is available only in Windows 95B or later. Novell Client for Windows...

  • Page 472: Login Script Commands And Variables

    Commands that work only on DOS or Windows 3.x workstations have not been included. These commands include CLS, COMSPEC, DOS VERIFY, MACHINE, NOSWAP, and SWAP. For information on using these commands, see ® the help file that accompanies the Novell Client for DOS and Windows 3.x software.
  • Page 473 Type identifier variables exactly as shown. To display the value of an identifier variable as part of a WRITE command, you must enclose the identifier in quotation marks and precede it by a percent sign (%). See “Using Identifier Variables” on page Novell Client for Windows...
  • Page 474 To map to a cluster-enabled volume, you would use the following syntax: MAP N:= .NDS object's fully distinguished name including context For example: MAP N:= .cluster2_vol1.xyz.provo.novell For more information on mapping, see “MAP” on page Login Script Commands and Variables...

  • Page 475: Using Identifier Variables

    Using the %GREETING_TIME variable displays the time of day. If Bob Smith logs in during the morning, both of the following lines display the same message (Good morning, SMITH) on his screen: WRITE "Good "; GREETING_TIME;", "; LAST_NAME WRITE "Good %GREETING_TIME,%LAST_NAME" Novell Client for Windows...
  • Page 476 The following table lists the identifier variables. Category Identifier Variable Function Date Day number (01 through 31) DAY_OF_WEEK Day of week (Monday, Tuesday, etc.) MONTH Month number (01 through 12) MONTH_NAME Month name (January, February, etc.) NDAY_OF_WEEK Weekday number (1 through 7; 1=Sunday) SHORT_YEAR Last two digits of year (99, 00, 01) YEAR...
  • Page 477 Workstation’s connection number WINVER Version of the workstation’s Windows operating system NetWare DIALUP 0 = Not using dialup Mobile 1 = Using NetWare Mobile Client dialup profile OFFLINE 0 = Not offline 1 = Disconnected login Novell Client for Windows...

  • Page 478: Login Parameters With %N Variables

    Category Identifier Variable Function <variable> Any DOS environment variable can be used in Environment angle brackets. To use a DOS environment variable in MAP, COMSPEC, and FIRE PHASERS commands, add a percent sign (%) in front of the variable. Miscellaneous ACCESS_SERVER Shows whether the access server is functional (TRUE = functional;...

  • Page 479: Login Scripts Commands By Task

    Login Script Execution BREAK (page 70) FIRE or FIRE PHASERS (page 73) GOTO (page 74) IF...THEN (page 75) INCLUDE (page 78) NO_DEFAULT (page 82) PAUSE (page 82) PROFILE (page 83) SCRIPT_SERVER (page 84) SHIFT (page 86) Novell Client for Windows...

  • Page 480: Workstation Environment

    Workstation Environment SET (page 84) SET_TIME (page 86) Text File Usage @ (page 68) # (page 67) DISPLAY (page 71) EXIT (page 72) FDISPLAY (page 72) TERM (page 88) WRITE (page 90) Other LASTLOGINTIME (page 80) REMARK (page 83) Use the # command to execute a program that is external to the login script. The # command executes an external program and waits until it is finished running before continuing with other login script commands.

  • Page 481: Command Format

    ACU uses a text file that can be called from the login script. To call this file from the login script for a workstation running Novell Client for Windows NT/2000, place one of the following commands in the login script: #Z:\PUBLIC\INSTALL\NTCLIENT\SETUPNW.EXE /ACU...

  • Page 482: Command Format

    The executable file cannot be found Insufficient workstation memory is available to load the file Command Format @ [path] filename [parameter] Replace path with a drive letter. Replace filename with an executable file (files that end in .EXE, .COM, or .BAT, for example).

  • Page 483: Break

    For example, if you are in the context SALES.NOVELL_US and you want to move up one level to the context NOVELL_US, add the following line to the login script. CONTEXT . To move up two levels, enter two periods, etc. Novell Client for Windows...

  • Page 484: Display

    DISPLAY Use DISPLAY to show the contents of a text file when the user logs in. When you use DISPLAY, all characters in the file, including any printer and word processing codes, appear. This command works best with an ASCII file. To display only the text and suppress codes, use “FDISPLAY”...

  • Page 485: Command Format

    ASCII file, see “DISPLAY” on page When you use FDISPLAY to display a word processing file, the text is filtered and formatted so that only the text is displayed. FDISPLAY will not display tabs. Novell Client for Windows...

  • Page 486: Command Format

    NOTE: If the given path does not exist or if the file is not found, no error message appears on the screen when the user logs in. Command Format FDISPLAY [path] filename Replace path with either a drive letter or a full directory path beginning with the NetWare volume name.

  • Page 487: Examples

    In this case, the commands to be executed are labeled AGAIN (as indicated in the second line). SET X="1" AGAIN: SET X=<X> + "1" ;see compound strings for this WRITE <X> IF <X> < "9" THEN GOTO AGAIN Novell Client for Windows...
  • Page 488 The GOTO command looks at the value of <X> (a DOS environment variable). If the value of <X> is less than 9, then <X> increments by 1 and GOTO loops back to the AGAIN label. When <X> gains the value of 9, the IF...THEN test becomes false, the GOTO is ignored, and the script continues normally.

  • Page 489: Command Format

    If you place the following command in a login script, the message Status report is due today appears when the user logs in on Monday and Have a nice day! on other days: IF DAY_OF_WEEK="MONDAY" THEN WRITE "Status report is due today." ELSE WRITE "Have a nice day!" Novell Client for Windows...
  • Page 490 The following lines mean “If the hour (on a 24-hour scale) is greater than or equal to 12, then write ‘afternoon’”: IF VALUE HOUR24>="12" THEN WRITE "afternoon" The following command executes the CAPTURE utility on the fourth day of the week (Wednesday): IF NDAY_OF_WEEK="4"...

  • Page 491: Include

    Replace filename with the complete name (including the extension) of the text file. To execute another object’s login script as part of a login script, replace object_name with the name of the object whose login script you want to use. Novell Client for Windows...

  • Page 492: Examples

    Examples To execute a text file called SCRIPT.NEW (located in volume VOL1) as a subscript, add the following line to your main login script: INCLUDE VOL1:ADMIN\USERS\SCRIPT.NEW Suppose you are creating a container login script for all users under the Organizational Unit object SALES_LA. You recently created a container login script for users under the Organizational Unit object SALES_PV.

  • Page 493: Lastlogintime

    Do not map over the local drive containing the Windows directory. Do not map a drive to a network drive such as a CD-ROM drive. Novell Client for Windows...

  • Page 494: Command Format

    Command Format MAP [[options]|[parameters][drive:=path] Replace drive with any valid network drive letter, local drive letter, or search drive number. Replace path with either a drive letter, a full directory path, a Directory Map object, or an NDS object such as a cluster-enabled volume. More than one command can be on the map line if the commands are separated by a semicolon ( ;...

  • Page 495: No_Default

    If you include PAUSE, the message Strike any key when ready... appears on the workstation screen. NetWare Login then waits for a key to be pressed before it executes the rest of the login script. Novell Client for Windows...

  • Page 496: Command Format

    Command Format PAUSE PROFILE Use PROFILE in a container script to set or override a user’s assigned or command line-specified profile script. This is useful when defining a group profile. Command Format PROFILE profile_object_name Example To override the profile script assigned to a user, and to cause the user to execute a PROFILE script called team_profile, use the following command: PROFILE team_profile REMARK...

  • Page 497: Example

    (\\"). You do not need to include SET commands in login scripts. For example, you might decide place some SET commands in the workstation’s AUTOEXEC.BAT file. Where you use SET commands depends upon your individual needs. Novell Client for Windows...

  • Page 498: Command Format

    This command does not work in a login script if the DOS workstation’s environment is too small. In this case, you should set the environment size in the CONFIG.SYS file. After you use the SET command to set a value for an environment variable, you can use that variable in other login script commands.

  • Page 499: Set_Time

    In the login script, you can add SHIFT with a positive or negative number to move the variables in either direction. For example, SHIFT -3 moves each %n variable three positions to the right. Novell Client for Windows...

  • Page 500: Command Format

    Command Format SHIFT [n] Replace n with the number of places that you want the variable to shift. The default is SHIFT 1. Examples When Mary logs in, she wants to access her word processing program, change the way it is set up, and map a drive to her work directory called ACCNTS. Mary also has a command in her login script to map a drive to her DATABASE directory, but she does not need it today.

  • Page 501: Term

    If you add TERM to a container login script, it prevents other profile or user login scripts from running. If you put TERM in a profile login script, it prevents the user login script from running. Novell Client for Windows...

  • Page 502: Command Format

    Command Format TERM nnn Replace nnn with an error level. Any error level between 000 and 999 is valid. Example If you want the login script to exit and return an error code of 718, you can add the following statement to the login script: TERM 718 TREE The TREE command can be used only with clients that support multiple NDS...

  • Page 503: Example

    However, if you put a semicolon at the end of all but the last WRITE commands, the commands all appear as one continuous sentence or paragraph (although they might wrap onto additional lines on the workstation’s screen). Novell Client for Windows...

  • Page 504: Command Format

    Text strings can include the following special characters: Character Meaning Causes a carriage return Starts a new line of text \" Displays a quotation mark on the screen Makes a beep sound In addition to the semicolon, you can use other operators to form compound strings (in other words, to join text and identifier variables into one command).
  • Page 505 Bob Smith logs in: WRITE "Hello, ";%LAST_NAME WRITE "Hello, %LAST_NAME" To make a beep sound occur while the phrase Good morning appears on the screen, add the following line to the login script: WRITE "Good %GREETING_TIME \7" Novell Client for Windows...

  • Page 506: Sample Login Scripts

    Sample Login Scripts ® You can create login scripts from these sample login scripts using NetWare Administrator. Using a sample login script can help reduce syntax errors, reducing the time it takes you to create your login scripts. For more information on how to create login scripts, see “Creating Login Scripts from a Sample or Existing Login Script”...

  • Page 507: Sample Profile Login Script

    “Login Script Commands and Variables” on page MAP DISPLAY OFF MAP ERRORS OFF MAP INS S16:=VOL1:APPL\DB MAP *5:=VOL1:ACCOUNTS\NEW MAP *6:=VOL1:ACCOUNTS\RECORDS @GRPWISE5 MAP DISPLAY ON WRITE IF DAY_OF_WEEK="FRIDAY" THEN WRITE "Weekly progress report is due today." FIRE 2 Novell Client for Windows...

  • Page 508: Sample User Login Script

    ® You can’t modify the default login script because it is coded into the Novell LOGIN utility. Instead, you can create container, profile, or user login scripts. The following sample of the default login script lists its contents and lets you find out more information about each command in the default login script.
  • Page 509 Novell Client for Windows...

  • Page 510: Troubleshooting Issues

    5.1 Support Pack 3. Refer to TID 10062546. Update Required on NetWare 4.11 and NetWare 4.2 Servers NetWare 4.11 and NetWare 4.2 servers require an update on the server prior to the installation of this Novell Client. The server update information is Troubleshooting Issues...
  • Page 511 CMDINFO at the DOS prompt. This command should list all configured or discovered MAs, depending on the IPX compatibility configuration. ZENWorks for Desktops 2 Remote Management Does Not Work after Upgrading to Novell Client for Windows 95/98 Version 3.31 If you upgraded Novell Client software and chose to update Remote...

  • Page 512: Login

    Installing ZENWorks for Desktops 2 Remote Management and Novell Client Software Version 3.31 on a New Workstation If you have new workstations that require ZENworks for Desktops 2 Remote Management and Novell Client for Windows 95/98 version 3.31, do one of the following. Install Remote Management Using an Application Object Install Novell Client for Windows 95/98 version 3.31 without selecting...

  • Page 513: Dial-Up Networking

    Dial-Up Networking over IP: SLP Configuration In order to use SLP name resolution with dial-up networking, you must add the directory agent’s IP address to the directory agent list on the Novell NetWare Client Properties Service Location tab. Right-click the N icon in the system tray and then click Novell Client Properties.
  • Page 514 The client uses an NWHOST file, if present, which contains server names and their addresses. This might be a preferred way to run your client. (The file is created in the NOVELL\CLIENT32 directory on the workstation.) The client also supports DNS names. After connecting to the dial-up host, make sure that your DNS server is working properly by attempting to ping your server using its DNS name.

  • Page 515: Printing

    Workstations using IPX Compatibility Mode cannot have an IPX internal network number configured. If you have configured an IPX internal network number on your workstation and you plan to install the Novell IP Client with IPX Compatibility Mode, then remove the IPX internal network number before installing the client.
  • Page 516 TCP/IP Source Path Parameter for Unattended Installation The TCP/IP Source Path parameter has been added to the unattended network installation. This parameter is not included in Novell Client Install Manager. To use this parameter, you must add it manually to the UNATTEND.TXT file:...

  • Page 517: Login

    Novell Client runs with MFC42.DLL version 4.21.7022 or later. MFC42.DLL version 6.00.8267.0 is installed when you install Novell Client. If an older version is installed over the version installed by Novell Client, the client login fails with an error message similar to the following: The ordinal 6453 could not be located in the dynamic link library MFC42.DLL.

  • Page 518: Login Script

    From the Display Options group, click Window. Login Script Command SET_TIME ON/OFF Behaves Differently on NT Novell Client for Windows NT/2000/XP Properties > Advanced Settings contains a Set Station Time property. When this setting is On, the workstation time is always synchronized with the network during GINA Login.
  • Page 519 USE command can be used to correctly connect and list network drives for both NetWare and NT servers. MAP.EXE Might Fail When Mapping a Drive to a Novell eDirectory Object on Windows NT MAP.EXE is not IP-aware for eDirectory objects. As a result, MAP.EXE might fail if you try to use it to map a drive to an eDirectory object—for...
  • Page 520 If this problem occurs, enter the default context for all eDirectory trees on the Client tab of the Novell Client Configuration page. This is accessed by right- clicking Network Neighborhood and then clicking Properties > Services > Novell Client for Windows NT > Properties.

  • Page 521: Printing Issues

    RAS server does not forward IP multicast packets between the client and the network, then you must set up and configure SLP Directory Agents. You can configure SLP Directory Agents through the Novell Client property pages or through DHCP. 108 Novell Client for Windows...

  • Page 522: Ipx Compatibility

    Network Numbers (also known as CMD Network Numbers) for each adapter used by your workstation to access the network if you want to allow your Novell IP Client to simultaneously access IPX Servers through each one of the adapters. For example, you could allow IPX Compatibility to use the default...
  • Page 523 RAS connection over a WAN adapter. If you have a multihomed Novell IP Client and you want to use the service of IPX Compatibility over only one of the network attachments and you are getting unwanted results, then you can disable IPX Compatibility over the other network attachments.

  • Page 524: Software Compatibility Issues

    NetWare 3.12 servers. Since FPNW does not support these features, the client is unable to use FPNW. A fix is available from Microsoft, but Novell testing indicates that the fix still does not provide a complete solution.
  • Page 525 112 Novell Client for Windows...
  • Page 526 Novell NetWare ® w w w . n o v e l l . c o m N O V E L L L I C E N S I N G S E RV I C E S A D M I N I S T R AT I O N G U I D E...
  • Page 527 Documentation Conventions ........8 Understanding Novell Licensing Services Key NLS Terms .
  • Page 528 Novell Licensing Services Administration Guide...

  • Page 529: Overview

    NetWare servers. Typically, the server installation program installs license certificates for NetWare and other selected NLS-enabled products. You can use iManage, Novell’s browser-based management tool, to install additional license certificates and to manage license units for NLS-enabled products. You can also create metered certificates and then use ZENworks to manage applications that are not NLS-enabled.

  • Page 530: Documentation Conventions

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. Novell Licensing Services Administration Guide...

  • Page 531: Understanding Novell Licensing Services

    Understanding the following terms will help you maintain licensing and license units on your network. Novell Licensing Services (NLS)—Software components and technology that provide a balance between your company’s need to manage and access license units and a software manufacturer’s need for enforcement of licensing requirements.
  • Page 532 NLS adds an attribute on the NCP Server object. This attribute points to the license service provider so that NLS has a link between the NCP Server object and the license service provider. Novell Licensing Services Administration Guide...
  • Page 533 License unit—A component of a license certificate. When you purchase a product, you purchase one or more license units for it. For example, a 100 Additive User License for Novell BorderManager Firewall Services 3 contains 100 license units, allowing 100 users to access BorderManager services.
  • Page 534 Activation Key, a prompt allows you to enter it. Envelope—An .NLF file that contains one or more license certificates; a convenient way of packaging multiple license certificates to be distributed as a single file. Novell Licensing Services Administration Guide...
  • Page 535 NLS can support many models of licensing. For example: Nonconcurrent connections in BorderManager Server Connection Licensing (SCL) in NetWare 4 and NetWare 5 User Access Licensing (UAL) for Novell Cluster Services NetWare 6 For information about the licensing model for the product that you use, refer to the product-specific documentation.
  • Page 536 Decides whether to grant access to certain program functionality Informs the license service provider when a license unit is no longer being used Contains mechanisms (policy) for handling errors concerning failed requests for license units Novell Licensing Services Administration Guide...
  • Page 537 A hard stop policy informs users that they are out of compliance with the terms and conditions of the license agreement. A hard stop prevents users from accessing a license unit. The hard stop could result from all available license units already being in use. Understanding Novell Licensing Services...

  • Page 538: Examples Of Nls Clients

    NLS itself does not enforce licensing. Instead, it checks out a license unit or returns the appropriate error condition to the application. The policy manager part of the application then determines whether the user can use the application or how the error condition is reported. Novell Licensing Services Administration Guide...

  • Page 539: How Nls Works

    The server issues this request to the NLS client. 2. The NLS client library packages the request from the application and submits it to an license service provider. Understanding Novell Licensing Services...
  • Page 540 In NetWare, for example, the license service provider starts in the user’s context and searches up the eDirectory tree for a user license. The following figure illustrates how an license service provider searches for a license certificate in the User Access Licensing model. Novell Licensing Services Administration Guide...
  • Page 541 In NetWare, for example, the server determines an action. If the status is successful, the server allows a connection to the server. Otherwise, the server allows a grace connection if one is available, or denies service if a grace connection isn’t available. Understanding Novell Licensing Services...
  • Page 542 Novell Licensing Services Administration Guide...

  • Page 543: Installing Novell Licensing Services

    Installing Novell Licensing Services This chapter discusses “Guidelines for Installing NLS” on page 21 “Installing NLS” on page 22 “Verifying That NLS Is Installed” on page 22 Guidelines for Installing NLS Prepare the network. If you are upgrading a server, the server should have a read/write replica ®...

  • Page 544: Installing Nls

    Verifying That NLS Is Installed At the server console GUI, click Novell > Install, and then look for an NLS entry. Do one of the following: If NLSLSP.NLM is running on the server, enter the following at the...

  • Page 545: Using Novell Licensing Services

    Using Novell Licensing Services ® You can manage NLS functionality in iManage, the Novell browser-based management tool, to complete the following tasks: “Managing License Certificates” on page 23 “Deleting a License Certificate” on page 25 “Moving a License Certificate” on page 25 “Modifying or Deleting Server Assignments”...

  • Page 546: About Envelopes

    If the licenses are to be installed in different contexts, you should install the licenses one at a time. If you choose to install a server license and one is already assigned to the server, the server license install will fail. Novell Licensing Services Administration Guide...

  • Page 547: Deleting A License Certificate

    Navigate to and select a license to move, and then click Next. Navigate to and select the context where you want to move the license to, and then click Next. A results screen displays showing the result of the moving the certificate. Click OK. Using Novell Licensing Services...

  • Page 548: Assigning Licenses To A Server

    License Certificate container or license. In iManage, click License Management > Manage License Properties. Navigate to and select a license file, and then click Next. Select a tab to display the information you want to view. Novell Licensing Services Administration Guide...

  • Page 549: Using Snmp

    SNMP packets and displays their contents to you, as the network administrator. Typically these consoles are run on client computers for convenience, but that functionality can be implemented on any computer on the network. Using Novell Licensing Services...

  • Page 550: Three Configuration Files For Snmp

    Then unload and reload NLSTRAP.NLM. (The changes won't take effect until you reload NLSTRAP.NLM.) Edit SNMP.CFG. Edit TRAPTARG.CFG to specify all targets that are to receive SNMP trap messages. Run the management console. Novell Licensing Services Administration Guide...
  • Page 551 SNMP.NLM (the SNMP agent) provides the APIs and framework to allow SNMP to work on NetWare. SNMP.NLM traps events, generates SNMP messages about the trapped events, and sends the messages to the management console. At the management console, view the SNMP messages. Using Novell Licensing Services...
  • Page 552 Novell Licensing Services Administration Guide...

  • Page 553: Troubleshooting Novell Licensing Services

    Some NLS clients might not have access to licensing services Place license certificates as close as practical to the actual users but high enough in the eDirectory tree so that everyone who needs to access them can do so. Consider the following guidelines: Troubleshooting Novell Licensing Services...

  • Page 554: The System Erroneously Reports Duplicate Licenses

    (Don’t delete the License Container object if it contains other license certificates.) Solution: Deploy the current version of NLS by installing the NetWare 4 Support Pack 6a and NetWare 5 Support Pack 4 on you servers. Novell Licensing Services Administration Guide...

  • Page 555: Error Codes And System Messages

    Error Codes and System Messages ® Many messages for Novell Licensing Services are self-documenting; information that you need appears on-screen with the message. Additional information about error codes are provided below. Other error codes are provided in NLSLSP Messages in System Messages.

  • Page 556: Error Code C0001005 Diplays

    Deleting Server Assignments” on page TIDs The following TIDs might help you resolve some issues relating to NLS on your network. The TIDs are available at www.support.novell.com/servlet/ knowledgebase. Description 2943405 What to do when the server is unable to obtain a valid server...
  • Page 557 Novell iFolder w w w . n o v e l l . c o m 1 . 0 A D M I N I S T R AT I O N G U I D E...
  • Page 558 Browser Requirements ........19 Installing Novell iFolder on NetWare 6 ....... 20 Post-Installation Tasks .
  • Page 559 Optimizing Your iFolder Server ........40 Novell iFolder Administration Guide...

  • Page 560: Novell Ifolder Administration Guide

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. Novell iFolder Administration Guide...
  • Page 561 Novell iFolder Administration Guide...

  • Page 562: Welcome To Novell Ifolder

    Welcome to Novell iFolder ® Novell iFolder gives you automatic, secure, and transparent synchronization of files between your hard drive and the iFolder server, which results in easy access to personal files anywhere, anytime. Being able to access your files from any computer from any location eliminates the editing mistakes and menial updating tasks that frequently occur when your local machine is not accessible from different access points.

  • Page 563: What Is Novell Ifolder

    The iFolder Web site is meant to be customized to fit your company’s look, feel, and business needs. iFolder client software Novell iFolder client is compatible with Windows* 95, 98, 2000, NT, and ME workstations. The iFolder client must be installed on every workstation that you will use to access your iFolder files.
  • Page 564 If you are installing Novell iFolder on NetWare 5.1, follow the instructions in Chapter 2, “Installing Novell iFolder on NetWare 5.1,” on page If you are installing Novell iFolder on NetWare 6, follow the instructions in Chapter 3, “Installing Novell iFolder on NetWare 6,”...
  • Page 565 If you are installing Novell iFolder on Windows NT 4.0 or Windows 2000, follow the instructions in Chapter 4, “Installing Novell iFolder on Windows NT 4.0 or Windows 2000,” on page If you are installing Novell iFolder on Novell Cluster Services, follow the instructions in Chapter 5, “Installing Novell iFolder on Novell Cluster...

  • Page 566: Installing Novell Ifolder On Netware

    If you have a DNS name configured for your iFolder server, verify that the DNS name and its corresponding IP address are in the SYS:ETC\HOSTS file of your iFolder server. Installing Novell iFolder on NetWare 5.1...

  • Page 567: Browser Requirements

    Enterprise Web server, you must set the secondary IP address prior to the iFolder installation and assign either the Apache or Enterprise Web server to that secondary IP address. On your workstation, map a Novell drive to the SYS: volume on the server where you plan to install iFolder and Apache. IMPORTANT: Apache must be installed on the SYS: volume.
  • Page 568 After you delete this directory, you should be able to install Novell iFolder on another server from the same workstation.
  • Page 569 Check the Show All Properties check box located at the bottom of the screen, select the CN property from the list, and then click OK. Check the Inheritable check box and then click OK > Apply > Close. Continue with Step Novell iFolder Administration Guide...
  • Page 570 The Admin names must have user accounts in your LDAP directory. If you are entering more than one name, separate the usernames with a semicolon, not spaces. For example, if you wanted users jsmith and Installing Novell iFolder on NetWare 5.1...
  • Page 571 Click Finish to complete the installation. Do one of the following: If you are using only one IP address, to start Novell iFolder you can reboot your server (this will run the edited AUTOEXEC.NCF) or enter the following commands at the server console:...

  • Page 572: Server Requirements

    Installing Novell iFolder on NetWare 6 Before you begin the iFolder installation, make sure that you have met the following iFolder server, client, and browser requirements. Server Requirements 10 MB of free space on the SYS: volume where you plan to install iFolder.
  • Page 573 Installing Novell iFolder on NetWare 6 Do a Custom install of NetWare 6. For instructions on installing NetWare 6, see the NetWare 6 Overview and Installation Guide. During the NetWare 6 installation, select iFolder as one of the products that you want to install.
  • Page 574 LDAP login DN context, check this option. IMPORTANT: If you selected to do subcontainer searches, there will be some post-installation configuration required after the NetWare 6 installation. For more information, see “Subcontainer Searches” on page Installing Novell iFolder on NetWare 6...

  • Page 575: Post-Installation Tasks

    These post-installation tasks are not optional. If you disreguard them, iFolder will not function properly. If your iFolder selections do not require post-installation tasks, see Chapter 6, “Using Novell iFolder,” on page 37 to learn more about Novell iFolder. Post-Installation Tasks Complete the appropriate post-installation tasks.
  • Page 576 CN property from the list, and then click OK. Check the Inheritable check box and then click OK > Apply > Close. Novell iFolder is now installed and running on your NetWare 6 server. To learn more about Novell iFolder, go to Chapter 6, “Using Novell iFolder,”...

  • Page 577: Ldap Over Ssl

    Novell iFolder is now installed and running on your NetWare 6 server. To learn more about Novell iFolder, go to Chapter 6, “Using Novell iFolder,” on page LDAP over SSL If your LDAP server is not the same server as your iFolder server, and you want LDAP over SSL, you need to export your LDAP server’s trusted root...

  • Page 578: Installing Novell Ifolder On Windows Nt 4.0 Or Windows 2000

    For other operating systems, export the LDAP server’s root certificate and then copy it to your iFolder server. Get an SSL certificate and install it onto your iFolder server. Installing Novell iFolder on Windows NT 4.0 or Windows 2000...

  • Page 579: Browser Requirements

    You can do this in either of two ways: 1) If you have your own certificate server, such as Novell Certificate Server, then you can get a certificate from your server, or 2) You can go to a certificate vendor, such as Entrust* or VeriSign*, and purchase a certificate from them.
  • Page 580 LDAP login DN context, make sure you check the Subcontainer Search check box. (Conditional) If you are doing a subcontainer search, you must assign the CN property to the Public object or create an LDAP proxy user. Installing Novell iFolder on Windows NT 4.0 or Windows 2000...
  • Page 581 Compare and Read rights. Right-click the LDAP Group object and then click Properties > General. Click the Browse button next to the Proxy Username field and browse to the user that you just gave trustee rights to. Novell iFolder Administration Guide...
  • Page 582 Click Finish to complete the installation. Restart the IIS server. After Novell iFolder is installed, you have a few things left to configure through the Internet Services Manager in order for the iFolder Web site and the Java applet to work correctly.

  • Page 583: Configuring The Ifolder Web Site On Windows Nt 4.0

    Check the Enable Default Documents check box and then click Add. Enter index.html into the text field and click OK. Novell iFolder in now installed on your Windows NT 4.0 server. For more information about Novell iFolder, go to Chapter 6, “Using Novell iFolder,” on...
  • Page 584 Check the Enable Default Documents check box. Click the Add button. Enter index.html into the text field and click OK. Novell iFolder in now installed on your Windows 2000 server. For more information about Novell iFolder, go to Chapter 6, “Using Novell iFolder,” on page Installing Novell iFolder on Windows NT 4.0 or Windows 2000...
  • Page 585 Novell iFolder Administration Guide...

  • Page 586: Installing Novell Ifolder On Novell Cluster Services

    Before you set up Novell iFolder on Novell Cluster Services , you should already have a basic understanding of how Novell Cluster Services works. A short overview is provided in the Novell Cluster Services Overview and Installation Guide (http://www.novell.com/documentation/lg/ncs/ index.html).

  • Page 587: Post-Installation Tasks

    NSS volume that you plan to make. For more information on creating pools and NSS volumes, see Novell Cluster Services (http://www.novell.com/documentation/lg/ ncs6p/index.html). Do one of the following: For NetWare 5.1 servers, cluster-enable the NSS volume that you just...
  • Page 588 SYS:Apache\iFolder\Server directory and edit the HTTPD.CONF file. Modify the following parameters: Locate the Listen parameter. Set this parameter to the IP address of the cluster-enabled volume by either adding a new Listen parameter or by modifying an existing one. Installing Novell iFolder on Novell Cluster Services...
  • Page 589 Add the following commands to the beginning of the existing unload script: stopifolder delay 2 Click Apply > Close. Novell iFolder is now installed. For more information on using Novell iFolder, Chapter 6, “Using Novell iFolder,” on page Novell iFolder Administration Guide...

  • Page 590: Using Novell Ifolder

    The default iFolder Web site This site contains the iFolder Client Quick Start Guide and other important information about Novell iFolder. It is also where users will download the iFolder client and access their iFolder files via a browser. You can modify this page to fit your company’s internal needs.

  • Page 591: Using The Conflict Bin

    From this site, you perform administrative tasks and manage the activity between the server and the iFolder clients. Access the Server Management Console by opening a browser and entering https:// ifolderserverip/iFolderServer/Admin. IMPORTANT: The Server Management Console URL is case sensitive. Novell iFolder Administration Guide...

  • Page 592: Removing An Ifolder Account

    Removing an iFolder Account Click User Accounts. Select the user ID that you want to remove, scroll to the bottom on the list, and then click Remove User. Click Yes to confirm the removal of the user account. Using Novell iFolder...

  • Page 593: Restoring A User's Folder

    Current defaults: 5-second delay after file activity 20-second server polling interval To improve performance, make the following changes: 30-second delay after file activity 1-minute server polling interval Novell iFolder Administration Guide...
  • Page 594 Novell NetWare ® w w w . n o v e l l . c o m N E T D R I V E A D M I N I S T R AT I O N G U I D E...
  • Page 595 Contents Novell NetDrive Administration Guide Documentation Conventions ........7 Installing Novell NetDrive Workstation Requirements .
  • Page 596 Novell NetDrive Administration Guide...

  • Page 597: Novell Netdrive Administration Guide

    NetDrive is an easy-to-use Internet client that lets you access your ® NetWare 6 servers over standard Internet protocols, such as WebDAV and FTP. NetDrive does not rely on the Novell Client in order to map network drives. Documentation Conventions In this documentation, a greater-than symbol (>) is used to separate actions...
  • Page 598 Novell NetDrive Administration Guide...

  • Page 599: Installing Novell Netdrive

    Once a network drive is mapped, the drive letter that you assigned during the mapping appears in Windows* Explorer and functions just like those that are mapped through Novell Client. You can connect to your NetWare 6 servers through any of the following protocols: iFolder—Use this protocol if you are connecting to iFolder...

  • Page 600: Workstation Requirements

    ZoneAlarm—Set the Internet security level to medium to allow NetDrive to access the Web server. F-Secure Anti Virus and KasperSky Anti Virus—If you are using Windows NT or Windows 2000 and NetDrive, disable the anti-virus software only while using NetDrive. Otherwise, your workstation might hang. Novell NetDrive Administration Guide...

  • Page 601: Installing Netdrive

    From the NetDrive Main Window that appears, you can create new sites, map network drives, and configure and manage the Web sites that you have mapped drives to. To learn more about using NetDrive to map drives, see Chapter 2, “Using Novell NetDrive,” on page Installing Novell NetDrive...
  • Page 602 Novell NetDrive Administration Guide...

  • Page 603: Using Novell Netdrive

    Using Novell NetDrive Once NetDrive is installed, you can perform many basic tasks within the ® NetWare Main Window. Adding a Site In the NetWare Main Window, click New Site. Enter the name of your site and the URL for the NetWare 6 server in the appropriate fields of the New Site dialog box.

  • Page 604: Mapping A Drive

    NetDrive Main Window > Advanced > PASV - Passive Mode > OK. Then try connecting to the Web server again. Once NetDrive has successfully connected to the NetWare 6 server, the Monitor dialog box appears. It provides you with connection status, file transfer statistics, and a connection log. Novell NetDrive Administration Guide...

  • Page 605: Copying Files

    Explorer. To disconnect from the server, right-click the Drive icon in Explorer and click Disconnect. WARNING: Since a connection can be interrupted in the middle of a file transfer, you should always keep a backup copy of files that are transferred or modified on your server. Using Novell NetDrive...
  • Page 606 Novell NetDrive Administration Guide...

  • Page 607: Using Netdrive In A Thin-Client Environment

    Terminal Services Client Citrix* MetaFrame ® Novell OnDemand Services To access your iFolder files, do the following: Install NetDrive on your thin-client server. NETDRIVE.EXE is located at the root of the NetWare 6 Client CD.
  • Page 608 Novell NetDrive Administration Guide...

  • Page 609: Troubleshooting Ftp Problems

    Troubleshooting FTP Problems The following are troubleshooting tips that should help when you encounter FTP errors. ® If you can’t create files using Microsoft Word, your NetWare 6 FTP server that is running FTP might not support filenames that have the tilde (~).
  • Page 610 NetWare 6 FTP server’s CONFIG.SYS file and then restart your server. If you get a TCP/IP connection error and you are using the ZoneAlarm firewall, make sure the security level is set to medium or disable ZoneAlarm. Novell NetDrive Administration Guide...
  • Page 611 NetStorage is a Net services software solution that is a bridge between a company’s protected Novell network and the Internet. It gives users secure file access from any Internet location, with nothing to download or install on the user’s workstation. Files and folders on a Novell network can be accessed using either a browser or Microsoft* Web Folders.
  • Page 612 If you have met the requirements for NetWare 6 and have NetWare 6 installed, you have met almost all of the system requirements for NetStorage. The following list specifies the system requirements for installing and running Novell NetStorage: At least one NetWare 6 server in the eDirectory tree where NetStorage will be installed A Netscape* Navigator* 4.7 or later or Internet Explorer 5.0 or later browser or Microsoft...
  • Page 613 You might need to load CDROM.NLM on the server to access the NetWare 6 Operating System 2 From the Novell menu on the NetWare 6 console GUI, select Install. 3 Click Add and then browse to the root of the NetWare 6 Operating System CD.
  • Page 614 S T A R T I N G A N D U S I N G N O V E L L N E T S T O R A G E Once you install NetStorage, it will start automatically when you start your NetWare 6 server. If NetStorage is not accessible, restart the NetWare 6 server where NetStorage is installed.
  • Page 615 Copyright © 2001 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. eDirectory and iFolder are trademarks and NetWare and Novell are registered trademarks of Novell, Inc.
  • Page 616 Novell NetWare ® w w w . n o v e l l . c o m N O V E L L S TO R A G E S E RV I C E S A D M I N I S T R AT I O N G U I D E...
  • Page 617 System Requirements ........19 Setting Up Novell Storage Services ....... . 19 Updating NSS Volumes .
  • Page 618 View Partitioned Free Space ....... . . 57 Troubleshooting Novell Storage Services Administration Guide...

  • Page 619: Introducing Novell Storage Services

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. Introducing Novell Storage Services...
  • Page 620 Novell Storage Services Administration Guide...

  • Page 621: Overview

    ® Novell Storage Services is the default storage and file system for NetWare You use it to create, store, and maintain both traditional and NSS volumes. The NSS volumes are called logical volumes. When you install NSS, it creates a storage pool SYS: and an equal sized volume SYS:.

  • Page 622: Nss Features And Benefits

    NSS logical volumes. See “Using ConsoleOne to Configure Novell Storage Services” on page NOTE: NWCONFIG and NSS Menu are not compatible with some of the NetWare 6 NSS features. Use ConsoleOne for all NSS configuration and management procedures.

  • Page 623: Exceed The Limit Of Volumes In A Storage Pool (Overbooking)

    Exceed the Limit of Volumes in a Storage Pool (Overbooking) Individual logical volumes cannot exceed the size of a storage pool. However, you can create numerous volumes in a storage pool. Individual logical volumes must be smaller than the storage pool, but the sum of multiple logical volumes can exceed the pool size.

  • Page 624: Retain Previously Saved Files (Snapshot)

    Some storage devices exist in a storage area network (SAN). These devices can be shared by multiple servers in a cluster. For more information about clustering, see Novell Cluster Services Overview and Installation. Enable File Compression NSS supports file compression. This lets you decide whether to compress the files in your volumes to create additional space.

  • Page 625: Prevent Access To Deleted Files (Data Shredding)

    Prevent Access to Deleted Files (Data Shredding) The Data Shredding feature overwrites purged disk blocks with random patterns of hexidecimal characters. This prevents unauthorized users from using a disk editor to access purged files. You can place up to seven data shred patterns over deleted data.

  • Page 626: Redirect Data From Unreliable Blocks (Hot Fix)

    If Hot Fix is enabled, then it is always active unless the disk fails or the redirection area is full. You can view Hot Fix activity in MONITOR by selecting Storage Devices and then a Hot Fix partition. For information on using MONITOR, see MONITOR in the Utilities Reference. Novell Storage Services Administration Guide...

  • Page 627: Repair Storage Pools Instead Of Individual Volumes

    You can specify no Hot Fix Redirection Area when you create disk partitions. Having no Hot Fix Redirection Area saves partition space. This might be useful on large RAID systems that provide a method of fault tolerance. IMPORTANT: If Hot Fix is not enabled, then the partition will not have the fault tolerance provided by NetWare.

  • Page 628: Stripe Data Across Storage Devices (Raid)

    This is called disk striping. The RAID stripe size is the amount of data the file system places on a disk before moving to the next disk. You can use the software RAID 0 on both logical and traditional volumes. Novell Storage Services Administration Guide...

  • Page 629: Features Not Currently Supported By Nss

    Important Information about NSS RAID Each element in the RAID configuration should come from a different device. NSS will let you obtain RAID elements from the same device, but this will severely impede the performance of your file system. Currently, the NSS RAID supports RAID 0. The stripe size ranges between 4 KB and 256 KB in increments of 2 KB.
  • Page 630 Free Space = Storage Deposit Partitioned Free Space Free Free Free Space Space Space Storage Storage Pool Pool Volume size can equal storage pool size Traditional Logical Logical Logical volume volume Vol1 Vol2 Vol3 (Read-Only) Novell Storage Services Administration Guide...

  • Page 631: Setting Up And Configuring Novell Storage Services

    ® NetWare 6. This section provides instructions for setting up and configuring Novell Storage Services (NSS) after the installation. It also contains information about configuring and maintaining traditional partitions and volumes. System Requirements A server running NetWare 6...
  • Page 632 If the time stamp shows a time earlier than when you began the upgrade, the backlink process is not complete. Repeat Step 1a through Step 1c until the backlink is complete. Novell Storage Services Administration Guide...

  • Page 633: Transaction Tracking System (Tts)

    You can set the buffers in percentages rather than integers. Use the following commands at the server console to set your cache buffers or tune your cache parameters. You can set or tune cache buffers at anytime. Setting Up and Configuring Novell Storage Services...
  • Page 634 Use percentages instead of This sets the buffers to percentages nss/(No)CacheBalance integers for cache balancing rather than integers for dynamic balancing of free memory for the buffer cache. The default is ON. Use this switch with /MinBufferCacheSize. Novell Storage Services Administration Guide...
  • Page 635 Limit the number of cache This is the maximum number of cache nss/ buffers buffers you want. Every time you do a cacheBalanceMaxBuffer cache balance, limit the number of cache buffers to this amount. Setting Up and Configuring Novell Storage Services...
  • Page 636 If many trustees have been set on different files and directories, we recommend that you increase this number. The default is 1024. The range is 16 to 50000. Novell Storage Services Administration Guide...

  • Page 637: Using Consoleone To Configure Novell Storage Services

    This is useful for checking the results of changes to the system. Using ConsoleOne to Configure Novell Storage Services ConsoleOne is the primary utility you use to configure and maintain partitions, storage pools, and volumes in NSS. To open ConsoleOne and access the options you need, complete the following: Open ConsoleOne.

  • Page 638: Setting Up Consoleone On A Workstation

    3. Mirror partitions. “Creating a Partition” on page 4. Create storage pools. “Creating a Storage Pool” on page 5. Create logical and traditional volumes. “Creating a Logical Volume” on page 32 “Creating a Traditional Volume” on page Novell Storage Services Administration Guide...
  • Page 639 You can select one or more devices, but select only the ones you want to use for the RAID configuration. Click Finish. The file system first creates a virtual device unit, then creates a RAID device. Setting Up and Configuring Novell Storage Services...
  • Page 640 Make sure you add all the physical storage devices you want to the RAID device before you click Restripe. Click Restripe. The Restripe option recognizes new devices in your RAID configuration and distributes the data across all the devices. Novell Storage Services Administration Guide...
  • Page 641 NSS storage pools and logical volumes. From ConsoleOne, open the tree you want. Right-click the server object and select Properties. Click Media > Partitions > New. Select a device to create a partition on. Setting Up and Configuring Novell Storage Services...
  • Page 642 Right-click the server object and select Properties. Click Media > Partitions > Mirror. Select the partition you plan to delete, click Remove. This removes the partition from the mirror group. You can now delete the partition. Novell Storage Services Administration Guide...
  • Page 643 Sharable for Clustering. Available if Clustering is installed and you want to use the feature. Activate. Activates your pool and any logical volumes when you create the pool. Otherwise, you can activate it later. Click Finish. Setting Up and Configuring Novell Storage Services...
  • Page 644 Clear this flag if the volume is empty or if backing up the data is unnecessary. This backup option is separate from the third-party backup vendor you Novell Storage Services Administration Guide...
  • Page 645 Activate. Activates logical volumes as soon as you create them. Mount. Mounts logical volumes as soon as you create them. Click Finish. You can now store and manage files in the NSS system. Setting Up and Configuring Novell Storage Services...

  • Page 646: Renaming A Storage Pool

    Right-click on the server object and select Properties. Click Media > NSS Pools. Select the storage pool you want to increase, then click Increase Size. Select the storage objects you want to obtain the space from. Novell Storage Services Administration Guide...

  • Page 647: Deleting Nss Pools Or Logical Volumes

    NSS automatically purges the volume.You can change the Purge Delay time to extend or reduce the time for the automatic purging cycle. See “Changing the Purge Delay Setting” on page 36. You can also manually purge Setting Up and Configuring Novell Storage Services...

  • Page 648: Changing The Purge Delay Setting

    The Purge Delay change command is not permanent. You must enter the command each time you restart the server. If you want to make the new setting permanent, enter the command in the AUTOEXEC.NCF file. Novell Storage Services Administration Guide...

  • Page 649: Creating A Traditional Volume

    This creates space for new and more commonly accessed data. Selecting this option only enables the attribute. The data migration feature uses a third-party software package that does the migration function. Setting Up and Configuring Novell Storage Services...

  • Page 650: Increasing The Size Of A Traditional Volume

    From ConsoleOne, open the tree you want. Right-click on the server object and select Properties. Click Media > Traditional Volumes. Select the volume you want to rename and click Rename. Enter a name. Click Finish. Novell Storage Services Administration Guide...

  • Page 651: Deleting A Traditional Volume

    A hardware failure either prevented a volume from mounting or caused a disk read error. NOTE: Although VREPAIR can't fix hardware problems, VREPAIR can sometimes fix related volume damage. A power failure caused a corrupted volume. Setting Up and Configuring Novell Storage Services...
  • Page 652 Accept the default options, or select alternate options, as appropriate. The first time you try to repair a volume, accept the default options. If the default options fail to repair the volume, select alternate options. To accept the default options, continue with Step 3. Novell Storage Services Administration Guide...
  • Page 653 Step 2 through Step 6. Repeat until VREPAIR finds no errors. If you are unable to mount the volume after running VREPAIR several times, you must delete the volume, re-create the volume using ConsoleOne. Setting Up and Configuring Novell Storage Services...

  • Page 654: Setting Up File Snapshot

    You need to set an additional bit 0x20000000 in the information mask. This bit is defined at RNSSInfoOnSnapshot in NSS header files. Both open and getinfo calls require the bit for requested rights and the bit for additional info mask. Novell Storage Services Administration Guide...

  • Page 655: Converting Traditional Volumes To Logical Volumes

    The following is a sample command line with all the available parameters for converting traditional volumes: vcu /p /l /i /d /r originalVolume nssPool [ds_container [ds_volName]] /p: Do not print directory file names. /l: Do not write errors to log file (Dst_Vol:error.out). /i:Keep file COMPRESS_FILE_IMMEDIATELY_BIT. Setting Up and Configuring Novell Storage Services...
  • Page 656 /r xxxx yyyy_old[ds_container[ds_volName]] In this example, xxxx is the original traditional volume name, yyyy_old is the modified traditional volume name. If xxxx is longer than 11 characters, yyyy_old might be VCU0000_old, otherwise yyyy_old will be xxxx_old. Novell Storage Services Administration Guide...

  • Page 657: Modifying Nds Objects

    If the user you want is not in the list, do the following: Click Add. Browse for the user you want. Double-click on the user. The User Space Restriction dialog box opens. You can enter or modify the User Space Restriction parameters in this box. Setting Up and Configuring Novell Storage Services...

  • Page 658: Setting Up Directory Space Restrictions

    REBUILD and VERIFY. When you use REBUILD and VERIFY a log file is generated to the root of the DOS drive. For instructions on running REBUILD and VERIFY, see “Rebuilding NSS Storage Pools and Volumes” on page From ConsoleOne, open the tree you want. Novell Storage Services Administration Guide...

  • Page 659: Salvaging And Purging Deleted Files

    Restore services, see the Storage Management Services Administration section in the Storage Management Services Administration Guide. IMPORTANT: Be sure to use the version of the Target Service Agent (TSA600). Earlier versions do not work with NSS. Setting Up and Configuring Novell Storage Services...

  • Page 660: Rebuilding Nss Storage Pools And Volumes

    You then need to mount the volume again. You can also verify a pool by entering nss /verify for a list of pool names, and then selecting the pool. Verify is a read-only assessment of the pool. Novell Storage Services Administration Guide...

  • Page 661: Nss Server Console Commands

    /(No)StorageAlertMessages Turns ON or OFF the low storage message to users. The default is ON. nss /NumWorkToDo=value Sets the number of WorkToDo entries which may be concurrently executing. NSS uses WorkToDo entries for Setting Up and Configuring Novell Storage Services...
  • Page 662 DataShredding Specify <vol name> [:<count>]. Enables data shredding for the volume. This is the number of times you want to shred data. The default value is 1. The maximum value is 7. NoDataShredding Disable data shredding on the volume. Novell Storage Services Administration Guide...
  • Page 663 PoolAutoDisplay Displays current pool load time policies. PoolAutoMaintenance=pool Places specified pools in maintenance mode at pool load time. PoolAutoVerify Verifies the specified pool’s physical integrity at startup time. PoolRebuild=pool Rebuild specified pools. Setting Up and Configuring Novell Storage Services...
  • Page 664 ZLSSVolumeUpgrade Allow the 5.x/ZLSS VolumeUpgrade to the NetWare 6 format to occur during the installation process. LVDeleteStatusBasic Displays information about deleted logical volumes. LVDeleteStatusSalvagable Displays information about salvagable logical volumes. ZLSSPoolScan Scans for and loads all ZLSS pools. Novell Storage Services Administration Guide...

  • Page 665: Dos Fat Commands

    Hierarchical File System (HFS) file formats. Dual formatted CDs are mounted as two separate volumes. This means both Macintosh and Windows clients will see the same CD ROM volumes with two different layouts. Setting Up and Configuring Novell Storage Services...

  • Page 666: Dos Partitions As Logical Volumes

    Long filenames (such as DOS filenames for file systems such as OS/2). This uses the Windows* 95/98 method for placing long names onto a DOS FAT partition. NetWare trustee rights. Only users with supervisor rights can access the volume. Novell Storage Services Administration Guide...
  • Page 667 NetWare volumes can do the same with DOS FAT partitions. MAP command. NetWare clients can map to the volume and use it as any other NetWare mapping. Local partition. Allows access to the local partition. Setting Up and Configuring Novell Storage Services...
  • Page 668 Novell Storage Services Administration Guide...

  • Page 669: Viewing Storage Objects

    Viewing Storage Objects We recommend that you monitor the status of your storage objects and ® Novell Storage Services configuration to ensure they work properly and have available disk space. Viewing Storage Devices You can use ConsoleOne to view your storage devices and see which ones have free space.
  • Page 670 Right-click on the server object and select Properties. Click Media > Traditional Volumes. The left panel lists all the traditional volumes set up on your server. Select the volume you want. For information about the Traditional volumes screen, click Help. Novell Storage Services Administration Guide...
  • Page 671 View the Status of Your NSS Storage Pools You can view the status of NSS storage pools. For example, you might want to see what volumes are in a particular storage pool, or how much space is in all your storage pools. From ConsoleOne, open the tree you want.
  • Page 672 Right-click on the server properties and select Properties. Click Media > Logical Volumes > Properties > Attributes > NSS Attributes. Make any attribute changes you want. For information about the NSS attributes screen, click Help. Novell Storage Services Administration Guide...

  • Page 673: Troubleshooting

    The following table describes some problems you might experience with ® Novell Storage Services (NSS) and provides suggestions for solving the problems. For additional troubleshooting information, see the Novell Knowledgebase at (www.support.novell.com). Problem Explanation Solution NSS does not recognize a...
  • Page 674 Apply the file compression option compression option when you to an existing logical volume: create a logical volume. From ConsoleOne, click Media > NSS Logical Volumes > Properties > Attributes > NSS Attributes. Then select compression. Novell Storage Services Administration Guide...
  • Page 675 Novell NetWare ® w w w . n o v e l l . c o m T R A D I T I O N A L F I L E S E RV I C E S A D M I N I S T R AT I O N G U I D E...
  • Page 676 Contents Contents Preface Documentation Conventions ........8 Overview of Traditional File System Volume .
  • Page 677 Mapping Drives ......... . 28 Mapping Drives in Windows 95/98, NT/2000 .

  • Page 678: Preface

    Consequently, there are sometimes a variety of ways in which a particular procedure can be performed. There are also various ways in which the file system itself can be viewed. Novell clients, for example, provide access to file system features and functionality that were once accessible only through NetWare utilities.

  • Page 679: Documentation Conventions

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. Traditional File Services Administration Guide...

  • Page 680: Overview Of Traditional File System

    For instructions on setting up partitions and volumes, see Setting Up and Configuring Novell Storage Services in the Novel Storage Services Administrator Guide. Volume There are two types of volumes: traditional and logical.

  • Page 681: Understanding Mounting A Volume

    A NetWare server is divided into one or more volumes. The first network volume is named SYS: and is created during NetWare installation. Using ConsoleOne, you can create a new volume on any hard disk that has a NetWare partition. A NetWare server supports up to 64 volumes. NetWare volumes are subdivided in two ways: Physically.

  • Page 682: Volume Objects In Nds

    FAT takes up cache buffers. NOTE: The new file system, Novell Storage Services (NSS), mounts volumes more quickly and can mount any size volume with 1 MB of memory. NSS volumes can be used along with traditional NetWare volumes. For information about NSS...

  • Page 683: Directories

    However, when you spread segments of a volume over several disks, you should protect the volumes against disk failure by mirroring; otherwise, if a single disk fails, one or more entire volumes shut down. You can add segments to a volume, but removing a segment from a volume destroys the entire volume.

  • Page 684: Fake Root

    characters in a directory path (counting the drive letter and delimiters), but DOS permits only 127 characters. Also, some applications restrict the number of characters in the directory path. For more information, check the application's documentation. Fake Root A fake root is a subdirectory that functions as a root directory. NOTE: Fake roots work with the NetWare DOS Requester, with NetWare shells, and clients including Windows* 3.x, Windows 95, and Windows NT*.

  • Page 685: Optimizing Performance

    Utilities Reference. Monitor compression activity via the SET command's compress screen parameter. Backup applications that use Novell Storage Management Services (SMS ) back up and restore compressed files. Other applications may decompress them. Traditional File Services Administration Guide...

  • Page 686: Salvageable Files

    Salvageable Files Salvageable files are files saved by NetWare, after being deleted by users, that can be salvaged (recovered). Salvageable files are usually stored in the directory they were deleted from. If a user deletes that directory, the salvageable files are saved in a DELETED.SAV directory located in the volume's root directory.

  • Page 687: Drive Mapping

    Drive mapping A drive mapping is a pointer to a location in the file system, represented as a letter assigned to a directory path on a volume. A path includes the volume, directory, and any subdirectories leading to the file. A drive mapping assigns a letter to a path so that the letter can be used instead of the complete path name.

  • Page 688: Network Drive Mappings

    Network Drive Mappings Network drive mappings point to volumes and directories on the network. Normally, drives F: through Z: are used for network mappings. Each user can map drive letters to different directories. To create a network drive mapping, use the MAP command. Network Search Drive Mappings Network search drive mappings point to directories containing files such as applications or files.

  • Page 689: Security

    Security Security is one of the most important aspects of file system organization. NDS rights and the file system's directory and file attributes allow you to determine who may access what, and whether that access amounts to being able to merely read a file or modify it.

  • Page 690: Planning

    (NSS) file system to meet your file system needs. NSS lets you create and maintain NSS logical volumes along with ® traditional NetWare volumes. For information on Novell Storage Services file system and its advantages, see the Overview in the Novell Storage Services Administration User Guide.

  • Page 691: Application Directories

    When creating application directories, you should also consider issues related to ease of distribution, installation, and operational control for network applications. For more information on creating application directories, see the ZENworks for Desktops 3.2 (http://www.novell.com/documentation/lg/zdfs/ index.html). Although you can access applications from local drives, installing them on the network provides convenient access.
  • Page 692 The following figure shows this type of directory structure: Figure 2 Application Volume SYSTEM PUBLIC LOGIN NetWare server MAIL WORDPROC APPSVOL DBAPP SPRDSHT Create a separate directory off volume SYS: for each application. Make trustee assignments for each application. Then go into the system or profile login script and map a search drive to each application.

  • Page 693: Data Directories

    However, users can see and use all applications. Use this directory structure only if you want all users to have access to all applications. The following figure shows this type of directory structure. Figure 5 Application Directory in SYS:PUBLIC WORDPROC APPS DBAPP PUBLIC...

  • Page 694: Home Or Username Directories

    Home or Username Directories To provide personal workspace for users, create home or username directories. You can create a parent directory in volume SYS: called HOME or USERS. Or, you can create a separate HOME or USERS volume. Then you can create a subdirectory for each user.
  • Page 695 Traditional File Services Administration Guide...

  • Page 696: Setting Up The File System

    The procedures in this section of the documentation focus on specific tasks pertaining to system administration. Procedures involve various utilities and applications that are provided in the Novell Storage Services Administration Guide. The most productive use of file system documentation is to identify the task you want to complete and find an appropriate procedure.

  • Page 697: Calculating Memory Required For Name Space Support

    The following name space NLM programs are available with NetWare: MAC.NAM (Macintosh) LONG.NAM (OS/2, Windows 95/NT/2000) NFS.NAM (NFS). An FTAM name space module is available from third-party providers. Calculating Memory Required for Name Space Support Use the following formula to calculate the name space memory requirement for traditional NetWare non-DOS volumes: 0.032 x volume_size (in MB) / block_size (in MB) Round the size up to the highest number.

  • Page 698: Removing Name Spaces

    You can remove the name space by deleting the volume and re-creating it, or by using VREPAIR. For instructions on using VREPAIR, see Repairing a Traditional Volume in the Novell Storage Services Administration Guide. Creating a Directory You create directories in ConsoleOne . To create a directory, you must have the Create right for the directory which the new directory will be added to.

  • Page 699: Mapping Drives

    Mapping Drives Mapping Drives in Windows 95/98, NT/2000 See Common Networking Tasks in the Novell Client for Windows documentation. Mapping Drives in DOS Use the command to map drives and search drives to network directories. For a general description of the MAP command, see in Utilities Reference.

  • Page 700: Security: Rights To Files And Directories

    “Viewing/Modifying the Inherited Rights Filter for Directories and Files” on page 30 For information on how to use Windows 95 to set rights, see Common Networking Tasks in Novell Client for Windows 95 (http://www.novell.com/ documentation/). For Windows NT, see NetWare File Security in Novell Client for Windows NT (http://www.novell.com/documentation/).

  • Page 701: Description Of Directory And File Rights

    Description of Directory and File Rights Trustee rights determine the access users have to directories and files. These rights can be given to NDS object such as User objects, Group objects, Organizational Role objects, or container objects. The following table contains a list and description of rights. Table 1 Trustee Rights Right...

  • Page 702: Setting Directory Or File Attributes

    “Changing Attributes of a Directory or File” on page 33 For information on how to use Windows 95 to set directory or file attributes, see Common Networking Tasks in Novell Client for Windows 95 (http:// www.novell.com/documentation/). Description of Directory and File Attributes Directory and file attributes assign properties to individual directories or files.
  • Page 703 Attribute Description Applies to code Do not Migrate prevents directories and files from being migrated Directories and files from the server's hard disk to another storage medium. Do not Suballocate prevents data from being suballocated. Files only The Hidden attribute hides directories and files so they cannot be Directories and files listed using the DIR command.

  • Page 704: Changing Attributes Of A Directory Or File

    Attribute Description Applies to code The Execute Only attribute prevents the file from being copied, Files only modified, or backed up. It does allow renaming. The only way to remove this attribute is to delete the file. Use the attribute for program files such as .EXE or .COM.
  • Page 705 Traditional File Services Administration Guide...

  • Page 706: Optimizing File System Performance

    Optimizing File System Performance This chapter on file system optimization focuses exclusively on tasks for the network administrator. Procedures in this section pertain primarily to disk space utilization, and affect performance only as space utilization affects network performance. Saving Disk Space with File Compression “Enabling File Compression”...

  • Page 707: Disabling File Compression

    For instructions on enabling or file compression, see Creating a Traditional Volume in the Novell Storage Services Administration Guide. Disabling File Compression File compression is enabled and disabled at the volume level. If you do not enable file compression when you create a volume, you can subsequently enable it using the SET utility.

  • Page 708: Suspending File Compression

    Saving Disk Space with File Purging You can conserve disk space by purging files from volumes. For information and instructions on purging files, see Deleting NSS Pools or Logical Volumes in the Novell Storage Services Administration Guide. Optimizing File System Performance...

  • Page 709: Saving Disk Space With Block Suballocation

    (RAID). For background information and instructions, see Creating a RAID Device in the Novell Storage Services Administration Guide. If one of the disks fails, the entire volume becomes unavailable. Therefore, you should mirror or duplex drives containing spanned volumes. If a disk containing a spanned volume fails, the entire volume must be restored from a backup across all segments before you can use it again.

  • Page 710: Managing

    Novell Storage Services (NSS) is the primary storage and file system. It supports large volumes and files. Information about the following sections are in the Setting Up and Configuring chapter of the Novell Storage Services Administration Guide: Creating a Logical Volume...

  • Page 711: Viewing Directory And File Information

    Deleting a Traditional Volume Repairing a Traditional Volume Volume Conversion Viewing Directory and File Information You can see extended information about a directory or file using ConsoleOne. For instructions on viewing directory and File information, see Viewing or Modifying Information about a File or Folder in the ConsoleOne 1.3 User Guide.

  • Page 712: Salvaging And Purging Files

    This provides considerable flexibility in protecting partitions. For information on mirroring and duplexing partitions, see Creating a Partition in the Novell Storage Services Administration Guide. IMPORTANT: Access the ConsoleOne online help for important information about mirroring partitions. Using Directory Map Objects A Directory Map object represents a particular directory in the file system.
  • Page 713 If you create a Directory Map object to point to an application, users can access the application by mapping a drive to the Directory Map object. Directory Map objects can be especially useful in login scripts by indicating directories that contain applications or other frequently used files. For instructions on creating Directory Map Objects, see Creating a Directory Map Object...

  • Page 714: Troubleshooting

    Troubleshooting This chapter presents various troubleshooting procedures for resolving problems with traditional volume including the following: Resolving File I/O Errors (page 43) Resolving Volume I/O Errors (page 44) Resolving Problems When the Server Hangs after Mounting Last Volume (page 44) Resolving Problems When No Volumes Mount (page 45) Resolving Problems When Only Some Volumes Mount (page 45) Resolving Disk Error Problems When a Volume Is Mounting (page 46)

  • Page 715: Resolving Volume I/O Errors

    Repair the volume using VREPAIR. Make sure that the volume is visible. If you have tried all of the above without success, contact a Novell Support Provider or the disk drive manufacturer. Resolving Problems When the Server Hangs after...

  • Page 716: Resolving Problems When No Volumes Mount

    Make sure that all server and workstation network boards are seated properly and that cabling and connections are attached securely. Make sure that the terminators on cables have the right ohm rating and are installed correctly. The IBM* PC Cluster sends a broadcast message during initialization and then stops processing if the network is not cabled or terminated properly.

  • Page 717: Resolving Disk Error Problems When A Volume Is Mounting

    The server does not have enough RAM The disk driver for external drives are not be loaded To resolve problems when only some volumes mount, do the following: Add more RAM. Verify which drivers are loaded. Resolving Disk Error Problems When a Volume Is Mounting To diagnose problems when disk errors occur while a traditional volume is mounting, identify whether the following conditions exist:...

  • Page 718: Resolving Volume Mounting Problems Because Of Corrupted Directory Entry Tables Or File Allocation Tables

    Each additional name space support that you add to a volume increases the size of the file allocation tables and directory entry tables. Adding name space support can cause the tables to grow so large that the server does not have enough RAM to mount the volume. To resolve memory errors when a volume mounts, perform the following actions or ensure that the following conditions exist: Check the status of the available cache buffers.

  • Page 719: Resolving Volume Mounting Problems Because Of Name Space Module

    A power failure has occurred and the server has not been shut down with the DOWN command. A hard disk has failed. A disk channel error has occurred. A volume does not dismount when you enter the DISMOUNT command. Directory information in cache is not completely written to disk. To resolve problems when mismatches exist in the duplicate copies of the FAT and DET, do the following: Run VREPAIR.

  • Page 720: Other Troubleshooting Information

    WARNING: This is a destructive step that destroys all of the extended file information. Back up all non-DOS files. Load VREPAIR and select Set VRepair Options. Then select the Remove Name Space Support from the Volume and Write All Directory and FAT Entries to Disk options.
  • Page 721 Traditional File Services Administration Guide...
  • Page 722 Novell NetWare ® w w w . n o v e l l . c o m N E T WA R E S E RV E R D I S K S A N D S TO R A G E D E V I C E S...
  • Page 723 Contents Contents Server Disks and Storage Devices Documentation Conventions ........7 Partitioning Disks.
  • Page 724 Novell Cluster Services w w w . n o v e l l . c o m 1 . 6 O V E RV I E W A N D I N S TA L L AT I O N...
  • Page 725 Run the Installation Program ........19 Setting Up Novell Cluster Services....... . . 22 Create Shared Disk Partitions .
  • Page 726 Some Applications Do Not Fail Over ......46 Novell Cluster Services Console Commands ......46...

  • Page 727: Introduction To Novell Cluster Services

    In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® Also, a trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. Introduction to Novell Cluster Services...
  • Page 728 Novell Cluster Services Overview and Installation...

  • Page 729: Overview

    Product Features Novell Cluster Services includes several important features to help you ensure and manage the availability of your network resources. These include: Support for shared SCSI or fiber channel storage area networks.

  • Page 730: Product Benefits

    Product Benefits Novell Cluster Services allows you to configure up to 32 NetWare servers into a high-availability cluster, where resources can be dynamically switched or moved to any server in the cluster. Resources can be configured to automatically switch or be moved in the event of a server failure, or can be moved manually to troubleshoot hardware or balance the workload.
  • Page 731 Figure 1 Three-Server Cluster Web Server 1 Web Server 2 Web Server 3 Web Site A Web Site C Web Site E Web Site F Web Site B Web Site D Fiber Channel Switch Shared Disk System During normal cluster operation, each server is in constant communication with the other servers in the cluster and performs periodic polling of all registered resources to detect failure.
  • Page 732 Web Server 1, and Web Server operation will return back to the way it was before Web Server 1 failed. Novell Cluster Services also provides resource migration capabilities. You can move applications, Web sites, etc. to other servers in your cluster without waiting for a server to fail.

  • Page 733: Cluster Configuration

    Cluster Configuration Typical cluster configurations normally include a shared disk subsystem connected to all servers in the cluster. The shared disk subsystem can be connected via high-speed fiber channel cards, cables, and switches, or be configured to use shared SCSI. If a server fails, another designated server in the cluster automatically mounts the shared disk volumes previously mounted on the failed server.

  • Page 734: Cluster Components

    From 2 to 32 NetWare servers configured to use IP, each containing at least one local disk device (used for a local SYS: volume). Novell Cluster Services software running on each NetWare server in the cluster. A shared disk subsystem connected to all servers in the cluster (optional, but recommended for most configurations).

  • Page 735: Installation And Setup

    Installation and Setup Hardware Requirements ® The following list specifies hardware requirements for installing Novell Cluster Services . These requirements represent the minimum hardware configuration. Additional hardware might be necessary depending on how you intend to use Novell Cluster Services.

  • Page 736: Shared Disk System Requirements

    If the disks in the shared disk system are not configured to use W A R N I N G : mirroring or RAID 5, a single disk error can cause a volume failure. Novell Cluster Services software will not protect against such faults.

  • Page 737: Installing Or Upgrading Novell Cluster Services

    After running the Novell Cluster Services installation the first time to create a new cluster, you will need to run the Novell Cluster Services installation again each time you want to add new servers to your cluster or upgrade Novell Cluster Services software on an existing cluster.

  • Page 738: Prepare Cluster Servers For An Upgrade

    Prepare Cluster Servers for an Upgrade If you are upgrading Novell Cluster Services from a previous version and your cluster has shared storage, you must prepare your cluster servers before upgrading them to NetWare 6 and before upgrading Novell Cluster Services.

  • Page 739: Run The Installation Program

    Click Create a New Cluster, Add New Nodes to Existing Cluster, or Upgrade Software in Existing Cluster, and then click Next. The Skip File Copy check box is checked by default and prevents Novell Cluster Services files from being copied during the installation. The NetWare 6 installation program automatically copies all Novell Cluster Services files to every NetWare 6 server.
  • Page 740 I M P O R T A N T : NSS partition on one of the shared disk drives to create the cluster partition. If no free space is available, the shared disk drives can’t be used by Novell Cluster Services.
  • Page 741 If you choose to not start Novell Cluster Services software on each server that you upgrade or add to your cluster, you will need to manually start it after the installation or you will need to reboot cluster servers to automatically start it.

  • Page 742: Setting Up Novell Cluster Services

    You might also need to create shared disk partitions if they do not already exist and, if necessary, configure all shared disk system pools and volumes to work with Novell Cluster Services. You might also need to cluster enable the shared disk system pools and volumes.
  • Page 743 The volume that is created will be allowed to grow to the pool size. The Prepare Volume for Use by Novell Clustering Services check box is currently not functional and does not need to be checked.

  • Page 744: Create Nss Pools

    Create NSS Pools The new Storage Pools feature in NSS gives you more flexibility in planning and configuring your storage to work with Novell Cluster Services. More than one cluster-enabled volume can now be part of a single cluster resource, and volumes can dynamically grow as needed to take advantage of free disk space.

  • Page 745: Create Cluster Volumes

    If you have a volume that is not being managed by Novell Cluster I M P O R T A N T : Services, the volume will need to be mounted before you can access it.

  • Page 746: Cluster Enable Pools And Volumes

    Some server applications don’t require NetWare client access to volumes, so cluster enabling pools and volumes might not be necessary. Pools should be deactivated and volumes should be dismounted before being cluster enabled. Novell Cluster Services Overview and Installation...
  • Page 747 Using ConsoleOne Browse and select the Cluster object. Click File > New > Cluster > Cluster Volume. Browse and select a volume on the shared disk system to cluster enable. Enter an IP address for the volume. This is only required for the first volume to be cluster enabled in the pool. This IP address will be assigned to the pool where the volume resides.

  • Page 748: Create Cluster Resource Templates

    ® Novell Cluster Services currently provides templates for DHCP, GroupWise and NetWare Enterprise Web Server, as well as a generic IP SERVICE template. The generic IP SERVICE template can be used when configuring certain server applications to run on your cluster.

  • Page 749: Create Cluster Resources

    To finish creating a cluster resource template, you need to configure load and unload scripts, set failover and failback modes and, if necessary, change the node assignments for the resource template. Using NetWare Remote Manager On the left column under the Clustering section, click Cluster Config. At the bottom of the screen above Create New Objects, click New Cluster Resource.

  • Page 750: Configure Load Scripts

    Load scripts are automatically created for disk pools when you cluster enable them. Because of this, it might not be necessary to configure or change the load script for a pool. Novell Cluster Services Overview and Installation...
  • Page 751 Using ConsoleOne Select the Load Script tab on the resource property page. Edit or add the necessary commands to the script to load the resource on the server. Some commands may require command line input. You can add << to a command to indicate command line input.

  • Page 752: Configure Unload Scripts

    On the Resource Information screen, click Unloading. Edit or add the necessary commands to the script to unload the intended resource on the server. Specify the Load Wait Time and click Apply to save the script. Novell Cluster Services Overview and Installation...

  • Page 753: Set Start, Failover, And Failback Modes

    (Conditional) Check the Ignore Quorum check box if you don’t want the cluster-wide timeout period and node number limit enforced. The quorum default values were set when you installed Novell Cluster Services. You can change the quorum default values by accessing the properties page for the Cluster object.

  • Page 754: Assign Nodes To A Resource

    Right-arrow button to move the selected server to the Assigned Nodes list. Repeat this step for all servers you want assigned to the resource. You can also use the Left-arrow button to unassign servers from the resource. Novell Cluster Services Overview and Installation...

  • Page 755: Configuration Settings

    Configuration Settings Depending on your needs and cluster setup, some additional configuration may be required for you to effectively use Novell Cluster Services. This additional configuration might consist of changing the values on some of the properties for the Cluster object and the Cluster Node objects.

  • Page 756: Cluster Protocol Properties

    The Quorum Membership is the number of nodes that must be running in the cluster before resources will start to load. When you first bring up servers in your cluster, Novell Cluster Services reads the number specified in the Membership field and waits until that number of servers is up and running in the cluster before it starts loading resources.
  • Page 757 Max Retransmits This option is not currently used with Novell Cluster Services but will be used for future versions. Installation and Setup...

  • Page 758: Cluster Ip Address And Port Properties

    Cluster IP Address and Port Properties The Cluster IP address is assigned when you install Novell Cluster Services. The Cluster IP address normally does need to be changed, but can be if needed. The default cluster port number is 7023, and is automatically assigned when the cluster is created.

  • Page 759: Cluster E-Mail Notification

    Click the Apply button to save changes made to resource priorities. Cluster E-Mail Notification Novell Cluster Services can automatically send out e-mail messages for certain cluster events like cluster and resource state changes or nodes joining or leaving the cluster.
  • Page 760 Specify an 8 to receive notification of all cluster state changes in XML format. XML format messages can be interpreted and formated with a Novell Cluster Services Overview and Installation...

  • Page 761: Cluster Node Properties

    parser that lets you customize the message information for your specific needs. Click the Apply button to save your changes. Cluster Node Properties You can view or edit the cluster node number or IP address of the selected node or view the context for the NetWare Server object. Using ConsoleOne Select the Cluster object and right-click the desired cluster node on the right side of the ConsoleOne display screen.

  • Page 762: Migrating Resources

    It will not load on any other servers in the cluster and will remain unloaded until you load it again. This option is useful for editing resources because resources can’t be edited while loaded or running on a server. Novell Cluster Services Overview and Installation...

  • Page 763: Identifying Cluster And Resource States

    You can reverse the sort order by pressing the Shift key while clicking on a column heading. The Event Log is stored on the special cluster partition that was created during the Novell Cluster Services installation, which ensures it is always available. You can also save the Event Log to a file.
  • Page 764 Quorum Wait The resource is waiting None. for quorum to be established so it can begin loading. Novell Cluster Services Overview and Installation...

  • Page 765: Additional Cluster Operating Instructions

    Install Novell Cluster Services on the new server. (Conditional) If you have changed the failover order, add the new server to the failover list. By default, Novell Cluster Services will include all nodes on the failover list, including newly added nodes. Installation and Setup...

  • Page 766: Readding A Node To A Cluster That Was Prevously In The Cluster

    The node will assume its former identity. Cluster-enabled Volume Connection Required for Some Utilities Because Novell Cluster Services uses NDS to find objects and resolve names, you must first establish a client connection to a cluster-enabled volume for it to be visible to certain utilities.
  • Page 767 Cluster Console Command Description ALERT {resource}{YES/NO} The resource start, failover, or failback mode is set to manual and the resource is waiting to start on a node, or fail over or fail back to another node. Specify the resource name in the command and use the YES or NO switch to specify whether or not you want the resource to fail over, fail back, or start.
  • Page 768 POOLS Lists the NSS pools on the shared disk system that are accessible by Novell Cluster Services. RESOURCES Lists all resources that currently exist in the cluster.
  • Page 769 NetWare Server Disks and Storage Devices Administration Guide...

  • Page 770: Server Disks And Storage Devices

    ® With NetWare , you can create up to four NetWare (or other) partitions on one ® hard disk. The primary storage and file system for NetWare is Novell Storage Services (NSS). For information about the NSS file system, see...
  • Page 771 NetWare Server Disks and Storage Devices Administration Guide...
  • Page 772 Overview of Server Disks and Storage Devices Server hard disks and remote storage devices (such as tape drives and CD- ® ROM drives) are all managed by the NetWare operating system. Hard disks are divided into partitions, including one DOS partition and at least one NetWare partition per server.

  • Page 773: Partitioning Disks

    A hard disk can contain as many as four partitions, including a DOS partition, multiple NetWare partitions, or non-NetWare partitions (such as Windows* NT* or UNIX). The disk can also contain free space assigned to the Novell Storage Services (NSS) file system.

  • Page 774: Logical Partitions

    Figure 2 DOS Partition on First Disk, NetWare and Non-NetWare Partitions on Second Disk Disk 1 Disk 2 SYS: Volume (1 disk segment) Data1: Volume NetWare (1 disk segment) DOS Partition Partition (Entire Disk) Data2: Volume (1 disk segment) Hot Fix Redirection Area Non-NetWare Partition...

  • Page 775: Device And Partition Numbering

    If you do not use Hot Fix and mirroring, the entire physical partition is the logical partition. Figure 4 Logical and Physical Partitions on a Server Disk Disk NetWare NetWare Logical Physical Partition Partition Hot Fix Redirection Area Partition The logical partition contains four redundant copies of the volume definition table (VDT).

  • Page 776: Object Numbers

    0x0001: [V312-A0-d4:0] iomega jaz 1GB rev:H.72 0x0000: [V025-A1] Novell IDE Host Adapter Module 0x0003: [V025-A1-D1:0] WDC AC22100H 0x0002: [V025-A2-D2:0] NEC CD-ROM DRIVE:282 rev:3.07 0x0006: DOS Partitioned Media...

  • Page 777: Device Names

    Partition examples The following are example partition entries with the device information: Unpartitioned - D:0x1-1 Unpartitioned indicates that the device is unpartitioned. D:0x is the device number. -1 is the chunk number. (A unique number that this is the first unpartitioned segment on device 1.) NSS-P:0x15-1 NSS-P:0x15-1 indicates that this is an unassigned NSS partition.
  • Page 778 LUN almost always appears as 0. The Device name represents the device in all Novell utilities and console commands, including MONITOR, LIST DEVICES, etc. Fault tolerance systems such as Hot Fix use the Device name to report that data blocks on disks have relocated.

  • Page 779: Drivers For Host Adapters And Storage Devices

    Drivers for Host Adapters and Storage Devices All storage devices require drivers. The NetWare Peripheral Architecture (NWPA) divides device drivers into two kinds: a custom device module (CDM) that drives the device itself and a host adapter module (HAM) that drives the adapter has been attached to.
  • Page 780 In the following illustration, several smaller disks are mirrored to partitions on one larger disk. Disk 4 Mirrored to Disk 3 partition 3 NetWare Partition 3 Mirrored to NetWare Disk 2 partition 2 Partition 2 NetWare Mirrored to Disk 1 Partition 1 partition 1 NetWare...

  • Page 781: Redirecting Bad Blocks

    ranges in order to make the data area identical to the other partitions in the group.) Mirrored partitions must have the same sharable status. Partitions you add to a mirror group cannot be part of any other mirror group. They must be standalone Mirror objects. The partitions you add must include the Mirror and Hot Fix options.
  • Page 782 Read redirection occurs following a disk error during a read request. If the disk is mirrored, the system retrieves the data from the mirrored disk and redirects the data on the primary disk. If the disk isn't mirrored, the data is lost, and the block is marked as bad. Read-after-write-verify redirection occurs after data is written to disk.
  • Page 783 Data on corrupted sectors of the disk will not be redirected to the Hot Fix Redirection Area. For instructions on how to specify no Hot Fix redirection area, see Creating a Partition in the Novell Storage Services Administration Guide. NetWare Server Disks and Storage Devices Administration Guide...

  • Page 784: Optimizing Storage Disk Capacity

    Redundant Array of Inexpensive Disks (RAID). For more information about RAID, see Stripe Data Across Storage Devices (RAID) the Novell Storage Services Administration Guide. The following is a list of suggestions for saving disk space: Compressing files. See...
  • Page 785 For information about enabling block suballocation, see Creating a Partition in the Novell Storage Services Administration Guide. Once block suballocation is enabled, you cannot disable the feature without recreating the volume. If you use block suballocation, set your file block size to 64 KB. The larger block size causes the system to transfer more data at one time so it improves performance.
  • Page 786 prevent large volumes from mounting. As soon as possible, upgrade the system to a newer board that can access higher memory. For instructions on using the SETcommand, see in Utilities Reference. For instructions on using MONITOR, see MONITOR in Utilities Reference. Use a driver that supports scatter gather functionality.

  • Page 787: Improving Disk Reads

    CD-ROM drives can create large index files. Don't use or mount the CD-ROM unless you have enough space. Limit the size of auditing files. (Auditing works only on traditional NetWare partitions.) Improving Disk Reads On a server that is read-intensive, the following procedures can improve the speed of disk reads.

  • Page 788: Changing The Turbo File Allocation Table (Fat) Wait Time For Faster Reads

    Increase the value of Directory Cache Buffer Non Referenced Delay. This parameter specifies how long a directory entry must be cached before it can be overwritten. Increasing this value causes the system to allocate more directory cache buffers and thus speeds up directory access. If the parameter is currently set to the default value of 5.5 seconds, try setting the value to 60 seconds.

  • Page 789: Improving Disk Writes

    70 % of total cache buffers, increase the number of concurrent write requests. For an explanation of file caching, see Setting the Cache Buffers in the Novell Storage Services Administration Guide. NOTE: Increasing the number of concurrent disk cache writes slows disk cache reads.

  • Page 790: Changing Disk And Directory Caching For Faster Writes

    Changing Disk and Directory Caching for Faster Writes Use this procedure if network users frequently make many small write requests and the server is slow to respond to the requests. From the MONITOR Available Options, select Server Parameters > File Caching.

  • Page 791: Turning Off Read-After-Write Verification

    NOTE: Increasing the number of concurrent directory cache writes decreases the speed of directory cache reads. Balance the speed of writes and reads to meet the needs or your users. If the parameter is currently at the default value of 10, try increasing the value to 25.
  • Page 792 Creating a Partition in the Novell Storage Services Administration Guide. ® Disk space not assigned to NetWare partitions can be used for the Novell Storage Services (NSS) file system. For information about creating NSS partitions, storage groups, and volumes, see...

  • Page 793: View A List Of Adapters And Devices

    View a List of Adapters and Devices To see a list of server hardware devices, type the following at the server console prompt: LIST DEVICES To see a list of storage adapters and the devices they drive, at the server console prompt enter: LIST STORAGE ADAPTERS The screen lists each adapter, followed by a list of devices driven by that...

  • Page 794: Checking For Disk Errors

    Scroll to Disk Space and note the available disk space for the volume and record it in a log. Press Tab to return to the list of Mounted Volumes. Check additional volumes as necessary. Press Esc until you return to Available Options. Repeat this procedure weekly for each volume.

  • Page 795: Adding And Replacing Hard Disks

    System Hot Fix Blocks: The number of blocks in the Hot Fix redirection area set aside for Hot Fix and Mirroring tables. These blocks are used to manage both Hot Fix and mirroring. The number of available Hot Fix blocks equals the total number of Hot Fix blocks, minus the used and system Hot Fix blocks.

  • Page 796: Replacing A Hard Disk

    After you install the new hard disk you can use ConsoleOne to configure the disk. For more information about configuring the disk, see Setting Up and Configuring Novell Storage Services in the Novell Storage Services Administration Guide. Replacing a Hard Disk If a hard disk becomes unreliable or unusable, follow this procedure to remove the disk from the network.

  • Page 797: Loading Disk Drivers

    After you install the new hard disk you can use ConsoleOne to configure the disk. For more information about configuring the disk, see Setting Up and Configuring Novell Storage Services in the Novell Storage Services Administration Guide. Loading Disk Drivers If you add or replace a hard disk adapter on your NetWare server, you must load the corresponding disk driver.

  • Page 798: Replacing Disk Drivers

    NetWare partitions can be created on any hard drive and can coexist with other partitions such as DOS, Windows* NT* UNIX*. Disk space not assigned to NetWare partitions can be used for the Novell Storage Services file system. When there is a DOS partition on the drive, it should always be the first partition.

  • Page 799: Deleting Netware Partitions

    Storage Services Administration Guide. Deleting NetWare Partitions This section explains how to delete traditional NetWare partitions. For information about deleting NSS partitions, storage groups, and volumes, see Setting Up and Configuring Novell Storage Services in the Novell Storage Services Administration Guide. NOTE: The partition table displays partitions such as OS/2*, UNIX, and XENIX* as Unknown Partition Type #.

  • Page 800: Mirroring And Duplexing Partitions

    For instructions on unmirroring partitions, see Deleting a Partition in the Novell Storage Services Administration Guide. Recovering Data from an Out of Sync Disk Once a hard disk is unmirrored, its status is listed as either Not Mirrored or Out of Sync on the Disk Partition Mirroring Status list.

  • Page 801: Managing Removable Media Devices

    From ConsoleOne, open the tree you want. Right-click on the server object and select Properties. Click Media > Partitions. Select a Partition that contains the data you want to recover, click Mirror > Resync. This initiates the resynchronization process for the mirror group that contains the partition you selected.

  • Page 802: Dismounting A Removable Media Device

    Select Mount Drive. Press Esc until you return to Available Options. Dismounting a Removable Media Device Use this procedure to dismount a removable media device, such as a CD-ROM device. From the MONITOR Available Options, select Storage Devices. For instructions on using MONITOR, see MONITOR in Utilities Reference.
  • Page 803 A list of Registered Storage Objects appears. The device information associated with a highlighted storage device appears in the upper window. Check the Device Type field to verify the type of storage device. NOTE: Storage devices are listed in hierarchical order to reflect each object's dependencies.
  • Page 804 Novell NetWare ® w w w . n o v e l l . c o m S TO R A G E M A N A G E M E N T S E RV I C E S...
  • Page 805 Contents Contents Preface Documentation Conventions ........7 Overview Backup Services .
  • Page 806 Loading SBCON ......... . 46 Prerequisites .

  • Page 807: Preface

    These services are performed by a collection of components that are independent of operating systems and hardware. You can backup SMS Targets such as Novell eDirectory , binderies, the file system, cluster-enabled pools or an individual workstation's hard disk onto a media that can be stored off-site.
  • Page 808 Storage Management Services Administration Guide...

  • Page 809: Overview

    Overview ® Backup services is an essential piece of the Novell Storage Management Services (SMS ) software, a collection of services that provides backup, restore, and data migration. These services are performed by various components and are independent of operating systems and hardware.

  • Page 810: Sms Components

    “Backups and Clusters” on page 29 “Session Files” on page 37 SMS Components Storage Management Engine (SME) for backup and restore operations. Novell provides the SBCON utility as a basic SME for NetWare. “Storage Management Engine (SME)” on page 12 for more information.
  • Page 811 keeps the names of these workstations in an internal list and displays the list, allowing you to select a target for a backup or restore procedure. The SBCON process involves two machines: The host server is typically the NetWare server running the backup program.

  • Page 812: Supported Storage Devices And Drivers

    IMPORTANT: To ensure reliable operations, pretest all media storage devices that are not Novell certified with the appropriate NetWare device driver and SBCON backup and restore utility. Use the driver files recommended by your hardware manufacturer. Storage Management Engine (SME) The Storage Management Engine (SME) is central to the SMS architecture.

  • Page 813: Storage Management Data Requester

    Storage Management Data Requester The Storage Management Data Requester (SMDR) is the communication module in the SMS architecture. It provides transparent access to SMS services in an intranet as it allows access to local or remote SMS services. The SMDR APIs are used by SBCON and other third-party applications as well. SMDR uses TCP Port Number 413.
  • Page 814 Location Protocol (SLP) for locating other SMDRs. This enables SMDRs to locate other SMDRs running on servers that belong to different trees. Every SLP enabled SMDR will register itself in the smdr.novell domain when loaded. The SLP enabled SMDRs will query this domain for locating registered SMDRs.

  • Page 815: Memory Requirements

    If NetWare Common Install is used to install SMS (see “Customizing the NetWare Server as the Backup Server” on page 43 for more information), this problem will not occur. If the SMDR is explicitly loaded for the first time, the screen for configuration information will not be hidden.

  • Page 816: Backup Types

    Backup Types SBCON has three types of backup sessions: Full backup—Backs up the entire file system of the selected target regardless of whether the data has changed since the last backup, and clears the Modify bit after the backup. Differential backup—Available only for the file system; backs up only data that has been changed since the last full or incremental backup.
  • Page 817 Exclude and Include Options Whenever you perform a custom backup or restore, you can use the exclude and include options to select subsets of what you want to back up. Whether you use exclude or include usually depends on the size of the data you want to back up, compared to the size of the data you do not want to back Exclude To back up most of the file system structure or eDirectory tree structure while...
  • Page 818 The same principle applies when you specify a directory with the include option. The figure below shows that all directories, subdirectories, and files under the NetUsers directory are included in the backup. All other areas of the file system structure are excluded from the backup. Public Project A2ZCO...

  • Page 819: Scan Data Sets

    Public Project A2ZCO Mail Widget.exe System Login Report January.prj February.prj HOME NetUsers Karl March.prj Appl Proposal Tessier.Inc Nu_Artco Directories Mary Subdirectories Files Thomas Directories Subdirectories Files Scan Data Sets You can specify a different type of data set to be scanned. A data set is a group of data that can be manipulated by SBCON.
  • Page 820 Public Project A2ZCO Mail Widget.exe System Login Report January.prj February.prj HOME NetUsers Karl March.prj Appl Proposal Tessier.Inc Nu_Artco Training Mary Workbook Viewgraph Script Schedules June July August Thomas Manuals Widget.Co chapt.1 chapt.2 chapt.3 chapt.4 appx.A appx.B glossary index Acme.Inc pamphlet Parents (all units above final) maps Children (final units only)

  • Page 821: Keeping A Backup Logbook

    Keeping a Backup Logbook Keep a hard copy log of your backups in case your online log and error files become corrupted. The log should contain the following information: Source backed up (such as the server or workstation name) Full path for session log and error files directory Full path for backed-up data...

  • Page 822: Preparing To Back Up

    How to prepare for a backup How to track backup Open Files Backup TSA600.NLM supports backup of open files on Novell Storage Services (NSS) volumes if the CopyOnWrite feature is enabled. To enable CopyOnWrite on a single NSS volume, do the following:...

  • Page 823: Determining An Appropriate Backup Type

    Determining an Appropriate Backup Type Each type of backup has a different effect on the backup and restore process. When planning your backup schedule, consider all of the following variables before determining which schedule is right for you. Media usage and backup speed. This helps increase the speed of the restore. Restoring after incremental backups.
  • Page 824 Distributed Database The network of servers that comprise an eDirectory tree structure continually exchange updates and other time-sensitive information. The eDirectory database exists as a set of files that are stored in the SYS: volume and are hidden so they are not accidentally tampered with or deleted. The eDirectory database files cannot be backed up, as was the case with bindery files in NetWare 3.12 or earlier versions.
  • Page 825 Placeholder (Unknown) Objects Whenever insufficient information is known about an object, such as when one of its mandatory attributes is missing, eDirectory creates as a placeholder an Unknown object. During a restore session of the eDirectory database information, Unknown objects are created when restoring an object that has an access control list (ACL) or any other attribute that refers to other objects that do not currently exist in the eDirectory tree structure.
  • Page 826 traffic during the backup process and improves performance when the backup program performs name resolution across the eDirectory tree structure. The version of TSANDS.NLM that ships with NetWare allows selective backup and restoration of an eDirectory tree structure. HINT: Not all third-party backup applications support this selective backup and restoration.

  • Page 827: Backups And The File System

    eDirectory backup to back up the portions of the tree for which they have rights. The network administrator assigns the Supervisor right to the backup administrators for the section of the eDirectory tree structure that they are responsible to back up. The network administrator then needs to create a TSANDS.CFG file that lists the fully distinguished names of the containers where each of the backup administrators' rights begin.
  • Page 828 Trustee Assignments Trustee assignments are stored as part of the file system as an ID. They are backed up by default when the file system is backed up with the SMS TSA software. If a User object is deleted and then re-created or restored, its object ID changes.

  • Page 829: Backups And Clusters

    Consolidation of applications and operations on a cluster has benefits such as lower costs, scalability, and increased availability. See the Novell Cluster Services documentation (http:// www.novell.com/documentation) for more information. For a cluster to work as a high-availability system, the file system, the applications, and services that run on the cluster should be cluster- enabled.SBCON supports backup and restore of cluster-enabled pools.

  • Page 830: Target Service Agents (Tsas)

    If a cluster server is chosen as the target, only noncluster volumes will be backed up. You have to back up each pool individually. You might abort an ongoing backup job with the intention of resubmitting the same job later. In such situations, the job will not restart from where it was terminated;...

  • Page 831: Restore Services

    The TSA packages data from the target and presents it to the SME in a generic format. This allows one SME to interact with many types of TSAs. NetWare 6 provides TSA600.NLM, with the following features: Supports backup and restore of traditional NetWare file system and NSS file system Supports backup and restore of cluster-enabled pools (see “Backups and...

  • Page 832: How Sms Restores Data

    How SMS Restores Data During a restore session, SBCON reads the backup storage media, and the Target Service Agent (TSA) compares the media data set to the existing hard disk data set. The Target Service Agent evaluates each data set according to the following criteria: Is this data set...
  • Page 833 BEGIN Go to backup session on storage media. there Read data set. another data set to read? Overwrite Is the data set? data set to renamed only if newer Open mode ignore Rename the dataset option data set restore a subset of what you´re restoring? Compare date of...

  • Page 834: Restore Options

    Restore Options For a custom restore session, you can specify exactly which data to restore. Several options work together to allow you maximum flexibility in your restore session. These options allow you to do the following: Choose subsets of data to restore Open mode options Overwrite an existing parent (such as a container) or child (such as an object)

  • Page 835: Restoring Edirectory And The File System

    Restoring eDirectory and the File System The only way to ensure that your eDirectory database can be fully restored is through partition replication, with replicas of the entire database on multiple servers. On a single-server network, you need to rely more heavily on backing up the data because you do not have replicas to restore information.
  • Page 836 stored on volume SYS:, losing SYS: is equivalent to removing NetWare and eDirectory from the file server. You must reinstall NetWare and eDirectory before you restore your data. The procedures for this scenario are divided into two cases: Loss of the only server in a single-server network. Loss of a single server in a multiple-server network.

  • Page 837: Restoring Cluster-Enabled Pools

    5. Restore the file system. (See “Restoring Data” on page 62 “Custom File System Restore” on page 74.) 6. Restore any replicas that were removed from the server. Loss of the Entire eDirectory Tree If all servers on a network are destroyed because of a disaster, you must perform a complete restore of NetWare, eDirectory, and file system data.

  • Page 838: Log And Error Files

    Log and Error Files The files of the backup session are stored in a default directory (such as SYS:SYSTEM\TSA\LOG). If you prefer, you can create your own directory for the log and error files as long as it resides on the host server. The files of the restore session are stored in the directory (SYS:SYSTEM\TSA\RESTORE).
  • Page 839 Error File The error file is created on the host server the first time a particular set of data is backed up. It contains a list of any errors that occurred during a backup or restore session. This file contains the following: The session date and time and the description you entered.
  • Page 840 Storage Management Services Administration Guide...

  • Page 841: Setting Up

    Setting Up In addition to being able to back up data from a server with SBCON, you can use a Windows 95, 98, 2000 or Windows NT workstation to perform your backups using the graphical interface. This chapter discusses the following: How to customize the NetWare server as the backup server.

  • Page 842: Sbcon Guidelines

    SBCON Guidelines Before you set up and begin backups, follow these guidelines to make backups easier and to avoid problems later. Log in. You will have limited success backing up and restoring if you log in without the Supervisor right. For security reasons, many SBCON options are limited to the network administrator.

  • Page 843: Before Loading The Backup Software

    Before Loading the Backup Software Before you load the backup software on the server or on a Windows machine, you need to configure a server to execute your backups. Determine the following: The tree to which the server belongs which must be made the current tree The full eDirectory context of the server Before Running the Backup Software...

  • Page 844: Loading Controller And Storage Device Drivers On The Server

    The SMDR Group object is where all NetWare and workstation SMDRs are registered for name resolution purposes. Accept the default name of the Backup Queue where all backup jobs will be submitted, or enter a new name and context. Loading Controller and Storage Device Drivers on the Server Controller and device drivers control the mechanical operation, such as read, write, forward, back, and stop of various storage devices and media.

  • Page 845: Loading The Target Service Agents

    Windows 2000 and NT Target workstation TSAPREFS.EXE, TSAMAIN.EXE (installed with the Novell Client). See the online help for more information. Follow these general steps when backing up or loading the software: Backing up the eDirectory database. Load TSANDS.NLM once on the server with a replica of the largest partition.

  • Page 846: Loading Sbcon

    Loading the files when the server starts. Place the commands in the server's STARTUP.NCF, and in the workstation's NET.CFG file, AUTOEXEC.BAT file (for DOS), or Startup folder (for OS/2). Loading SBCON You can load SBCON from the server command line. If you use NWBACK32 on a client, you do not need to load SBCON.

  • Page 847: Unloading Sbcon

    Unloading SBCON To ensure maximum memory utilization and throughput, you should unload backup software and other Storage Management Services (SMS ) modules when you are finished performing your backup. That way, more memory will become available on your host or target. Exit SBCON from the Main Menu.

  • Page 848: Exiting Nwback32

    Run NWBACK32.EXE from SYS:PUBLIC. The following screen appears. You are now ready to back up data. Go to “Backing Up Data” on page 49 continue. Exiting NWBACK32 Exit NWBACK32 from the Quick Access window. Unload all the modules loaded on the server by entering the following command at the server console: SMSSTOP Unloads all the previously loaded SMS modules.

  • Page 849: Backing Up Data

    Table 2 on page Set the backup server and its tree as the primary resource using the Novell Client. This lets you view the tape devices in NWBACK32. If you are backing up the eDirectory database, ensure that eDirectory synchronization and communication are functioning properly.

  • Page 850: Backing Up From The Server

    Ensure that media is inserted into your storage device. You can back up your data two ways: from a server using SBCON or from a Windows workstation using NWBACK32. Backing Up from the Server When you back up your data from one server to a target server or workstation, you should use the command line.
  • Page 851 Select a target from the Target Services list. The following table describes the targets that can be selected for backup. If you are Backing Up Then Select Cluster-enabled pools The cluster-enabled pool you want to back up The file system The server whose file system you want to back The eDirectory database The server with TSANDS loaded...
  • Page 852 This is a descriptive name of the job, which will help you identify the specific backup session; if a restore is necessary, you can easily identify the session you need. There is no special requirement for what to enter as the session description.
  • Page 853 To return to the Main Menu, press Esc until you back out to the Main Menu. To exit SBCON, press Esc again and answer the confirmation prompt. Customizing Backup You can customize your backup using the Advanced Backup Options form when you use SBCON at the server to launch your backup program.
  • Page 854 Select Subsets of What To Backup. The default setting means that everything in the Subsets of What You Want to Backup screen is backed up. Include/Exclude TSA Resources—Includes or excludes resources such as servers or volumes. Include/Exclude Directories—Includes or excludes directories. Include/Exclude Files—Includes or excludes files.

  • Page 855: Backing Up From A Workstation

    The day, month, or year you enter should not be the actual date when you want the job to run; rather, it is the duration after which the job gets executed. Example If you have scheduled a job to run on 03/20/1999 and want to rerun the job after two months and at the same time, then the Rerun Interval field should be the following: Year: 0, Month: 2, Day: 0...

  • Page 856: Backing Up Cluster-Enabled Pools From The Server

    Select where you want your backup data to go. Double-click Where to Backup. Change to the correct eDirectory tree structure and context by clicking the Change to Context button on the toolbar. Double-click Queues. Select a Queue object from the list. Right-click the server to open the drop down box.
  • Page 857 When prompted, enter the username (and context, if required) for the target. If SBCON rejects the username you entered, you probably need to include the context where the User object is located. For example, instead of entering ADMIN as the username, enter .CN=ADMIN.O=company_name or .ADMIN.company_name.
  • Page 858 If the storage media does not have a label, SBCON displays a message saying that the media cannot be identified. Set the label before selecting it for a backup job. Select Advanced Options and set the desired values for all the fields. For more details, see “Customizing Backup”...

  • Page 859: Backing Up A Workstation

    NOTE: If W95TSA is installed and registered, a shield-like icon appears in the system tray and indicates Novell TSA (Listening) message. You will also see an SMS screen popup when you log in to NetWare. At the target workstation, register with the W95TSA.
  • Page 860 Windows 2000 and Windows NT Workstation Make sure that the NT TSA is installed and configured. It is a part of the Novell Client modules (checkbox for Novell Target Service Agent). The Windows NT TSA has two parts: TSA Service (TSAMAIN.EXE) is a service that waits for and acts when there is a request from the backup engine.

  • Page 861: Changing Your Target

    Changing Your Target Any time you are performing a series of backup or restore sessions, you might need to change your target. This can be easily done from the SBCON Main Menu either at the command line or from the Windows workstation using NWBACK32.

  • Page 862: Restoring Data

    Restoring Data Use SBCON to restore information from tape backup. These procedures use SBCON as the Storage Management Engine (SME). Know the username and password for the target server or workstation to which you want to restore data. Know the session description that you want to restore. You can get this information from your session log and error files.
  • Page 863 Load SBCON. “Loading SBCON” on page Select Main Menu > Job Administration > Restore. The Restore Options screen appears. Select Target Service and then the NetWare server running your backup and restore Target Services Agent. This is the name of the server or workstation on which you want to restore your data.
  • Page 864 Target Service to Restore Dataset to Select Workstation The workstation's host server and then the workstation Server-specific The server whose server-specific information information you want to restore and then the file system to restore When prompted for the target username, enter your username (and context if required) as the network administrator for the target.
  • Page 865 volume without compression, the file is corrupted and no error message is displayed. Specify the path to the session log file of the session you want to restore. Use one or more of the following methods: Press Enter to accept the default; then go to Step 12 on page Press Insert to select from a list of directories, press Esc to return to the previous window, and then go to...
  • Page 866 The Esc key allows you to exit SBCON one screen at a time until you reach the Main Menu. If you want to exit SBCON, answer the confirmation prompt. NOTE: To unload SBCON and applicable Target Service Agents, see “Unloading SBCON”...
  • Page 867 The screen lists major and minor resources. Default indicates that none of that type of subset has been specified. To specify a subset, do the following: Select any item on the screen. Edit the Include or Exclude screens using Insert and Enter. Press Esc to save changes.

  • Page 868: Restoring Data From A Workstation

    Restoring Data from a Workstation When you restore data, you are copying your backed up data to a server or workstation. Run NWBACK32. “Loading NWBACK32” on page You can run the NWBACK32 program (NWBACK32.EXE) from SYS:PUBLIC. At the Quick Access window, click Restore. Click What you Want to Restore.

  • Page 869: Restoring Edirectory

    Restoring eDirectory The procedures in the following sections are performed at the beginning of the restore process. “Restoring a Volume Other Than SYS:” on page 69 “Restoring Volume SYS: in a Single-Server Network” on page 69 “Restoring Volume SYS: in a Multiple-Server Network” on page 70 “Restoring the Entire eDirectory Tree Structure”...
  • Page 870 Make sure disk partitions are at least as large as they were before, and that the volumes are defined as before. Restore eDirectory using “Customizing Restore” on page Restoring Volume SYS: in a Multiple-Server Network To restore SYS: volumes on several servers, do the following. Restore the server-specific eDirectory information file (SERVDATA.NDS) to another server on the network following the custom (advanced) file system restore (see...
  • Page 871 Select Remove This Server from the Replica Ring. Enter the supervisor name and password. Select Yes to continue. Exit DSREPAIR. Reinstall NetWare. Begin the installation. When prompted for DS install, select Create a New DS Tree and complete the installation. Load NWConfig and remove DS.
  • Page 872 Restoring the Entire eDirectory Tree Structure To restore an entire network from a full backup in a multiple-server environment, do the following: Reinstall NetWare on the first server. By default, this server will hold the master replica of the [Root] partition. When NWCONFIG asks for the names of Organization objects immediately under the [Root] object, use the same names that existed before in the eDirectory tree.

  • Page 873: Edirectory Restore Session Types

    eDirectory Restore Session Types You can choose to restore eDirectory in one of the following ways: “Single Server or an Entire Tree Restore” on page 73 “Custom eDirectory Restore” on page 73 “Custom File System Restore” on page 74 “Server-Specific Information Restore” on page 76 “Single File or Directory Restore”...
  • Page 874 If you do not want to overwrite the parent or child that exists on the hard disk, regardless of whether the existing version or the backed-up version has the latest date, select the option (parent or child or both), and enter N. Continue through Step 14 on page 65 Step 19 on page...
  • Page 875 Follow these important rules about restoring to a new location: When you specify a particular portion of the file system structure as the source location, it does not necessarily mean that this will be the only data restored. You can influence what is restored by using the Include and Exclude options on the Choose Subsets Of What You're Restoring screen (Job Administration >...
  • Page 876 If you want to overwrite the child that exists on the hard disk only if the date of the backed-up copy on the media is later than the date of the copy on the hard disk, select Overwrite Existing Child and select the option. Continue through Step 15 on page 65 Step 19 on page...
  • Page 877 Press Insert and enter the name space for the name space format you used when entering the file or directory name. The name space allows SBCON to correctly interpret the path information entered earlier in this menu in either the directory field or the location field.

  • Page 878: Completing The Edirectory Restore

    Completing the eDirectory Restore If you restored the eDirectory database to volume SYS:, you should complete the restoration for the following to make sure the eDirectory database is working properly: Volume Other than SYS: To finish restoring eDirectory on a volume other than SYS:, do the following. Bring the server up.
  • Page 879 Entire Tree To finish restoring eDirectory on the tree, do the following. Restore the file system information to each server following “Restoring Data” on page Re-create partitions and replicas. (Optional) Verify proper restoration of the data, trustee assignments, file ownership, and other related information by spot-checking some of the restored directories and files.

  • Page 880: Restoring Cluster-Enabled Pools

    identifies the file server on which the queue directory resides. This information is used to determine the physical location of the resource. The specifics of restoring objects vary depending on what type of object is involved and whether the object's dependencies are physical entities (servers and volumes) or logical entities.

  • Page 881: Managing

    Managing After you install and load SBCON, you can manage your jobs, data, devices, reports, and so on either from the server or workstation. Though the screens might look different, you can perform the same tasks in each interface. Be sure to read “Prerequisites for SBCON Tasks”...

  • Page 882: Jobs

    Jobs The backup or restore jobs created by you can be administered anytime. You can delete, hold, reschedule, abort, or enable a job. Administering Jobs Jobs can be managed either from the server or from the workstation. From the Server On the SBCON Main Menu at the server, the Current Job List option gives you a job management facility where you can delete a job, hold a job, or enable it if it has been disabled after a job failure.
  • Page 883 Dynamic properties contains data that indicates how much data has been backed up along with the filenames. This dialog box appears when a job is running and SBSC is loaded on the server. Enable job allows you to start a job that has been disabled. Delete the job allows you to remove a job.
  • Page 884 Viewing Job Details This screen gives you all the details of the job you submitted including job name, the time the job was submitted, and the time the job should be executed. You can also schedule the job to run at a predefined time again after its execution.
  • Page 885 Serviced By—This indicates the name of the server where the job is to be executed. From a single server, you can submit jobs to various servers. This field indicates which job is serviced by which server. This field is active only when the job is active; otherwise, it indicates None.

  • Page 886: Storage Devices

    From a Workstation At the Quick Access window, click Job Administration. Double-click the context. Double-click Queues. Select the job to place on hold. Right-click the job and then click Start/Hold the Job. (Optional) You can also hold the job using the toolbar. Click Job Administration >...
  • Page 887 From the Server Select Main Menu > Storage Device Administration. Select a device and press Insert. Select Utilities > Device Status. The Device Status screen is displayed listing the following information: Current Operation—Indicates whether the device is currently reading, writing, formatting the media, or none of these. Device Mode—Indicates whether the device is selected for reading, writing, or both.
  • Page 888 You can change a device label from the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page From the Server Select Main Menu > Storage Device Administration. Select a device name and press Insert. Select Utilities >...
  • Page 889 From the Server Select Main Menu > Storage Device Administration. A list of devices is displayed. If no device is displayed in the list, run LIST DEVICES at the server prompt. Select a device name and press Enter. The List of Media screen appears displaying the following information: Slot—The slot number given by the manufacturer.
  • Page 890 Erasing or Retaining Media This task erases media headers, erases all data on the media, or retentions media in tape devices. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page The following table describes all media options. Option Explanation Change the Media Label...
  • Page 891 Double-click Queues. Double-click the preferred queue. Double-click Servers. Double-click the preferred server. Double-click Devices. Right-click the media > click Erase Media [or] Retension. (Optional) You can also use the toolbar. Click Device Administration > Media > Erase Media [or] Retension. Checking the Media Status in a Device This task lets you check the status of a particular media type from either the server or a workstation.

  • Page 892: Spanning Storage Media

    Media mode—Whether the media is selected for reading, writing or both, or whether the mount request is pending. Media type—The type of media in the device, such as 4mm DDS (Digital Data Storage) tape, or 8mm tape. Total capacity—The total capacity of the media, if known. Sometimes it is not displayed, depending on the media manager.

  • Page 893: Log And Error Files

    Log and Error Files SBCON keeps a list of all the log and error files, which show specific information about the backup and restore session. See “Session Files” on page for more information. You can manage these files as follows: View information contained in the log and error files.
  • Page 894 To change the directory, delete the existing directory path and type a new one, and then go to Step 3 on page You can also press Insert during this process to select existing parts of the path from a list. The backup log displays all supported name space types.
  • Page 895 From the Server From the SBCON Main Menu, select Log File Administration > View an Error File. If necessary, set the location of the log and error files for a backup session. (This option is not supported for a restore session.) To set the location, use one or more of the following methods: Press Enter to accept the default location, and then go to Step 3 on...
  • Page 896 Double-click the preferred queue. Double-click Servers. Right-click the preferred server. Select Error Report. Creating Log and Error Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks”...
  • Page 897 Deleting the Log Files SBCON allows you to overwrite sessions and reuse storage media. When you delete the log file for a session using the following procedure, you automatically delete the corresponding error file as well. To prevent outdated session information from taking up disk space and to help prevent confusion when you select sessions to view or restore, delete the session log files for any session that has been overwritten.
  • Page 898 Creating Session Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them from either the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks”...
  • Page 899 Select the preferred media. Right-click the job and select Submit the Job. Check the appropriate fields in the Submission of Job dialog box. Verifying Backup Data This option allows you to check the data on the media from either the server or a workstation to make sure it has been backed up properly, and to check later that the data is valid and can be restored.
  • Page 900 From a Workstation At the Quick Access window, click Verify. Double-click the context if necessary. Double-click Queues. Double-click the preferred queue. Double-click Servers. Double-click the preferred server. Double-click Devices. Double-click the preferred device. Right-click the preferred media. Select Submit the Job. In the Submission of Job dialog box, click the session.

  • Page 901: Optimizing

    Optimizing This chapter discusses the following topics: Whether you should compress your files before backup. See “Compressed Files” on page 101. How to increase speed when backing up your files. See “Host Server Performance” on page 102. How to enhance or optimize server performance. See “Setting Minimum Packet Receive Buffers”...

  • Page 902: Host Server Performance

    Backups are faster if files already compressed are left compressed. Compression is not supported in some environments (such as a NetWare 3.11 server, a DOS workstation, or Novell Storage Services ). If you intend to restore a file that is currently compressed to an environment that does not support compression, back it up in a decompressed state.
  • Page 903 Setting Minimum Packet Receive Buffers Packet receive buffers represent the space in the server memory dedicated to handling network traffic. If the buffers are set too low, the server performance may be degraded. To reset the packet receive buffers at the server console prompt, include the following SET command in the STARTUP.NCF file: SET MINIMUM PACKET RECEIVE BUFFERS = X The x represents the number of buffers.
  • Page 904 104 Storage Management Services Administration Guide...

  • Page 905: Troubleshooting

    Troubleshooting Common Backup Problems The media owner is unidentified Possible Cause: Media is blank or was written in a non-SIDF format. Action: “Checking the Media Status in a Device” on page Backup speed is slow Possible Cause: Compressed files are being backed up in a decompressed format. Action: “Compressed Files”...
  • Page 906 Data is corrupted, but no error message was given Possible Cause: Compressed files were restored to a volume without compression. Action: Step 10 on page You (the network administrator) can't back up a workstation Possible Cause: The /Password option is set and is denying access to data on the workstation. Action: “Setting Rights to Back Up Portions of the eDirectory Tree”...
  • Page 907 Files were restored but the error file contains a message specifying which name space formats were not restored Possible Cause: The file attributes and name space formats are not configured on the volume you restored to. Action: Check to make sure you selected the correct name space. Can't list devices or see the Session/Error Report from the client and the message Unable to Establish Communication with Server appears Possible Cause:...
  • Page 908 108 Storage Management Services Administration Guide...
  • Page 909 Novell NetWare ® w w w . n o v e l l . c o m S TO R A G E M A N A G E M E N T S E RV I C E S...
  • Page 910 Contents Contents Preface Documentation Conventions ........7 Overview Backup Services .
  • Page 911 Loading SBCON ......... . 46 Prerequisites .

  • Page 912: Preface

    These services are performed by a collection of components that are independent of operating systems and hardware. You can backup SMS Targets such as Novell eDirectory , binderies, the file system, cluster-enabled pools or an individual workstation's hard disk onto a media that can be stored off-site.
  • Page 913 Storage Management Services Administration Guide...

  • Page 914: Overview

    Overview ® Backup services is an essential piece of the Novell Storage Management Services (SMS ) software, a collection of services that provides backup, restore, and data migration. These services are performed by various components and are independent of operating systems and hardware.

  • Page 915: Sms Components

    “Backups and Clusters” on page 29 “Session Files” on page 37 SMS Components Storage Management Engine (SME) for backup and restore operations. Novell provides the SBCON utility as a basic SME for NetWare. “Storage Management Engine (SME)” on page 12 for more information.
  • Page 916 keeps the names of these workstations in an internal list and displays the list, allowing you to select a target for a backup or restore procedure. The SBCON process involves two machines: The host server is typically the NetWare server running the backup program.

  • Page 917: Supported Storage Devices And Drivers

    IMPORTANT: To ensure reliable operations, pretest all media storage devices that are not Novell certified with the appropriate NetWare device driver and SBCON backup and restore utility. Use the driver files recommended by your hardware manufacturer. Storage Management Engine (SME) The Storage Management Engine (SME) is central to the SMS architecture.

  • Page 918: Storage Management Data Requester

    Storage Management Data Requester The Storage Management Data Requester (SMDR) is the communication module in the SMS architecture. It provides transparent access to SMS services in an intranet as it allows access to local or remote SMS services. The SMDR APIs are used by SBCON and other third-party applications as well. SMDR uses TCP Port Number 413.
  • Page 919 Location Protocol (SLP) for locating other SMDRs. This enables SMDRs to locate other SMDRs running on servers that belong to different trees. Every SLP enabled SMDR will register itself in the smdr.novell domain when loaded. The SLP enabled SMDRs will query this domain for locating registered SMDRs.

  • Page 920: Memory Requirements

    If NetWare Common Install is used to install SMS (see “Customizing the NetWare Server as the Backup Server” on page 43 for more information), this problem will not occur. If the SMDR is explicitly loaded for the first time, the screen for configuration information will not be hidden.

  • Page 921: Backup Types

    Backup Types SBCON has three types of backup sessions: Full backup—Backs up the entire file system of the selected target regardless of whether the data has changed since the last backup, and clears the Modify bit after the backup. Differential backup—Available only for the file system; backs up only data that has been changed since the last full or incremental backup.
  • Page 922 Exclude and Include Options Whenever you perform a custom backup or restore, you can use the exclude and include options to select subsets of what you want to back up. Whether you use exclude or include usually depends on the size of the data you want to back up, compared to the size of the data you do not want to back Exclude To back up most of the file system structure or eDirectory tree structure while...
  • Page 923 The same principle applies when you specify a directory with the include option. The figure below shows that all directories, subdirectories, and files under the NetUsers directory are included in the backup. All other areas of the file system structure are excluded from the backup. Public Project A2ZCO...

  • Page 924: Scan Data Sets

    Public Project A2ZCO Mail Widget.exe System Login Report January.prj February.prj HOME NetUsers Karl March.prj Appl Proposal Tessier.Inc Nu_Artco Directories Mary Subdirectories Files Thomas Directories Subdirectories Files Scan Data Sets You can specify a different type of data set to be scanned. A data set is a group of data that can be manipulated by SBCON.
  • Page 925 Public Project A2ZCO Mail Widget.exe System Login Report January.prj February.prj HOME NetUsers Karl March.prj Appl Proposal Tessier.Inc Nu_Artco Training Mary Workbook Viewgraph Script Schedules June July August Thomas Manuals Widget.Co chapt.1 chapt.2 chapt.3 chapt.4 appx.A appx.B glossary index Acme.Inc pamphlet Parents (all units above final) maps Children (final units only)

  • Page 926: Keeping A Backup Logbook

    Keeping a Backup Logbook Keep a hard copy log of your backups in case your online log and error files become corrupted. The log should contain the following information: Source backed up (such as the server or workstation name) Full path for session log and error files directory Full path for backed-up data...

  • Page 927: Preparing To Back Up

    How to prepare for a backup How to track backup Open Files Backup TSA600.NLM supports backup of open files on Novell Storage Services (NSS) volumes if the CopyOnWrite feature is enabled. To enable CopyOnWrite on a single NSS volume, do the following:...

  • Page 928: Determining An Appropriate Backup Type

    Determining an Appropriate Backup Type Each type of backup has a different effect on the backup and restore process. When planning your backup schedule, consider all of the following variables before determining which schedule is right for you. Media usage and backup speed. This helps increase the speed of the restore. Restoring after incremental backups.
  • Page 929 Distributed Database The network of servers that comprise an eDirectory tree structure continually exchange updates and other time-sensitive information. The eDirectory database exists as a set of files that are stored in the SYS: volume and are hidden so they are not accidentally tampered with or deleted. The eDirectory database files cannot be backed up, as was the case with bindery files in NetWare 3.12 or earlier versions.
  • Page 930 Placeholder (Unknown) Objects Whenever insufficient information is known about an object, such as when one of its mandatory attributes is missing, eDirectory creates as a placeholder an Unknown object. During a restore session of the eDirectory database information, Unknown objects are created when restoring an object that has an access control list (ACL) or any other attribute that refers to other objects that do not currently exist in the eDirectory tree structure.
  • Page 931 traffic during the backup process and improves performance when the backup program performs name resolution across the eDirectory tree structure. The version of TSANDS.NLM that ships with NetWare allows selective backup and restoration of an eDirectory tree structure. HINT: Not all third-party backup applications support this selective backup and restoration.

  • Page 932: Backups And The File System

    eDirectory backup to back up the portions of the tree for which they have rights. The network administrator assigns the Supervisor right to the backup administrators for the section of the eDirectory tree structure that they are responsible to back up. The network administrator then needs to create a TSANDS.CFG file that lists the fully distinguished names of the containers where each of the backup administrators' rights begin.
  • Page 933 Trustee Assignments Trustee assignments are stored as part of the file system as an ID. They are backed up by default when the file system is backed up with the SMS TSA software. If a User object is deleted and then re-created or restored, its object ID changes.

  • Page 934: Backups And Clusters

    Consolidation of applications and operations on a cluster has benefits such as lower costs, scalability, and increased availability. See the Novell Cluster Services documentation (http:// www.novell.com/documentation) for more information. For a cluster to work as a high-availability system, the file system, the applications, and services that run on the cluster should be cluster- enabled.SBCON supports backup and restore of cluster-enabled pools.

  • Page 935: Target Service Agents (Tsas)

    If a cluster server is chosen as the target, only noncluster volumes will be backed up. You have to back up each pool individually. You might abort an ongoing backup job with the intention of resubmitting the same job later. In such situations, the job will not restart from where it was terminated;...

  • Page 936: Restore Services

    The TSA packages data from the target and presents it to the SME in a generic format. This allows one SME to interact with many types of TSAs. NetWare 6 provides TSA600.NLM, with the following features: Supports backup and restore of traditional NetWare file system and NSS file system Supports backup and restore of cluster-enabled pools (see “Backups and...

  • Page 937: How Sms Restores Data

    How SMS Restores Data During a restore session, SBCON reads the backup storage media, and the Target Service Agent (TSA) compares the media data set to the existing hard disk data set. The Target Service Agent evaluates each data set according to the following criteria: Is this data set...
  • Page 938 BEGIN Go to backup session on storage media. there Read data set. another data set to read? Overwrite Is the data set? data set to renamed only if newer Open mode ignore Rename the dataset option data set restore a subset of what you´re restoring? Compare date of...

  • Page 939: Restore Options

    Restore Options For a custom restore session, you can specify exactly which data to restore. Several options work together to allow you maximum flexibility in your restore session. These options allow you to do the following: Choose subsets of data to restore Open mode options Overwrite an existing parent (such as a container) or child (such as an object)

  • Page 940: Restoring Edirectory And The File System

    Restoring eDirectory and the File System The only way to ensure that your eDirectory database can be fully restored is through partition replication, with replicas of the entire database on multiple servers. On a single-server network, you need to rely more heavily on backing up the data because you do not have replicas to restore information.
  • Page 941 stored on volume SYS:, losing SYS: is equivalent to removing NetWare and eDirectory from the file server. You must reinstall NetWare and eDirectory before you restore your data. The procedures for this scenario are divided into two cases: Loss of the only server in a single-server network. Loss of a single server in a multiple-server network.

  • Page 942: Restoring Cluster-Enabled Pools

    5. Restore the file system. (See “Restoring Data” on page 62 “Custom File System Restore” on page 74.) 6. Restore any replicas that were removed from the server. Loss of the Entire eDirectory Tree If all servers on a network are destroyed because of a disaster, you must perform a complete restore of NetWare, eDirectory, and file system data.

  • Page 943: Log And Error Files

    Log and Error Files The files of the backup session are stored in a default directory (such as SYS:SYSTEM\TSA\LOG). If you prefer, you can create your own directory for the log and error files as long as it resides on the host server. The files of the restore session are stored in the directory (SYS:SYSTEM\TSA\RESTORE).
  • Page 944 Error File The error file is created on the host server the first time a particular set of data is backed up. It contains a list of any errors that occurred during a backup or restore session. This file contains the following: The session date and time and the description you entered.
  • Page 945 Storage Management Services Administration Guide...

  • Page 946: Setting Up

    Setting Up In addition to being able to back up data from a server with SBCON, you can use a Windows 95, 98, 2000 or Windows NT workstation to perform your backups using the graphical interface. This chapter discusses the following: How to customize the NetWare server as the backup server.

  • Page 947: Sbcon Guidelines

    SBCON Guidelines Before you set up and begin backups, follow these guidelines to make backups easier and to avoid problems later. Log in. You will have limited success backing up and restoring if you log in without the Supervisor right. For security reasons, many SBCON options are limited to the network administrator.

  • Page 948: Before Loading The Backup Software

    Before Loading the Backup Software Before you load the backup software on the server or on a Windows machine, you need to configure a server to execute your backups. Determine the following: The tree to which the server belongs which must be made the current tree The full eDirectory context of the server Before Running the Backup Software...

  • Page 949: Loading Controller And Storage Device Drivers On The Server

    The SMDR Group object is where all NetWare and workstation SMDRs are registered for name resolution purposes. Accept the default name of the Backup Queue where all backup jobs will be submitted, or enter a new name and context. Loading Controller and Storage Device Drivers on the Server Controller and device drivers control the mechanical operation, such as read, write, forward, back, and stop of various storage devices and media.

  • Page 950: Loading The Target Service Agents

    Windows 2000 and NT Target workstation TSAPREFS.EXE, TSAMAIN.EXE (installed with the Novell Client). See the online help for more information. Follow these general steps when backing up or loading the software: Backing up the eDirectory database. Load TSANDS.NLM once on the server with a replica of the largest partition.

  • Page 951: Loading Sbcon

    Loading the files when the server starts. Place the commands in the server's STARTUP.NCF, and in the workstation's NET.CFG file, AUTOEXEC.BAT file (for DOS), or Startup folder (for OS/2). Loading SBCON You can load SBCON from the server command line. If you use NWBACK32 on a client, you do not need to load SBCON.

  • Page 952: Unloading Sbcon

    Unloading SBCON To ensure maximum memory utilization and throughput, you should unload backup software and other Storage Management Services (SMS ) modules when you are finished performing your backup. That way, more memory will become available on your host or target. Exit SBCON from the Main Menu.

  • Page 953: Exiting Nwback32

    Run NWBACK32.EXE from SYS:PUBLIC. The following screen appears. You are now ready to back up data. Go to “Backing Up Data” on page 49 continue. Exiting NWBACK32 Exit NWBACK32 from the Quick Access window. Unload all the modules loaded on the server by entering the following command at the server console: SMSSTOP Unloads all the previously loaded SMS modules.

  • Page 954: Backing Up Data

    Table 2 on page Set the backup server and its tree as the primary resource using the Novell Client. This lets you view the tape devices in NWBACK32. If you are backing up the eDirectory database, ensure that eDirectory synchronization and communication are functioning properly.

  • Page 955: Backing Up From The Server

    Ensure that media is inserted into your storage device. You can back up your data two ways: from a server using SBCON or from a Windows workstation using NWBACK32. Backing Up from the Server When you back up your data from one server to a target server or workstation, you should use the command line.
  • Page 956 Select a target from the Target Services list. The following table describes the targets that can be selected for backup. If you are Backing Up Then Select Cluster-enabled pools The cluster-enabled pool you want to back up The file system The server whose file system you want to back The eDirectory database The server with TSANDS loaded...
  • Page 957 This is a descriptive name of the job, which will help you identify the specific backup session; if a restore is necessary, you can easily identify the session you need. There is no special requirement for what to enter as the session description.
  • Page 958 To return to the Main Menu, press Esc until you back out to the Main Menu. To exit SBCON, press Esc again and answer the confirmation prompt. Customizing Backup You can customize your backup using the Advanced Backup Options form when you use SBCON at the server to launch your backup program.
  • Page 959 Select Subsets of What To Backup. The default setting means that everything in the Subsets of What You Want to Backup screen is backed up. Include/Exclude TSA Resources—Includes or excludes resources such as servers or volumes. Include/Exclude Directories—Includes or excludes directories. Include/Exclude Files—Includes or excludes files.

  • Page 960: Backing Up From A Workstation

    The day, month, or year you enter should not be the actual date when you want the job to run; rather, it is the duration after which the job gets executed. Example If you have scheduled a job to run on 03/20/1999 and want to rerun the job after two months and at the same time, then the Rerun Interval field should be the following: Year: 0, Month: 2, Day: 0...

  • Page 961: Backing Up Cluster-Enabled Pools From The Server

    Select where you want your backup data to go. Double-click Where to Backup. Change to the correct eDirectory tree structure and context by clicking the Change to Context button on the toolbar. Double-click Queues. Select a Queue object from the list. Right-click the server to open the drop down box.
  • Page 962 When prompted, enter the username (and context, if required) for the target. If SBCON rejects the username you entered, you probably need to include the context where the User object is located. For example, instead of entering ADMIN as the username, enter .CN=ADMIN.O=company_name or .ADMIN.company_name.
  • Page 963 If the storage media does not have a label, SBCON displays a message saying that the media cannot be identified. Set the label before selecting it for a backup job. Select Advanced Options and set the desired values for all the fields. For more details, see “Customizing Backup”...

  • Page 964: Backing Up A Workstation

    NOTE: If W95TSA is installed and registered, a shield-like icon appears in the system tray and indicates Novell TSA (Listening) message. You will also see an SMS screen popup when you log in to NetWare. At the target workstation, register with the W95TSA.
  • Page 965 Windows 2000 and Windows NT Workstation Make sure that the NT TSA is installed and configured. It is a part of the Novell Client modules (checkbox for Novell Target Service Agent). The Windows NT TSA has two parts: TSA Service (TSAMAIN.EXE) is a service that waits for and acts when there is a request from the backup engine.

  • Page 966: Changing Your Target

    Changing Your Target Any time you are performing a series of backup or restore sessions, you might need to change your target. This can be easily done from the SBCON Main Menu either at the command line or from the Windows workstation using NWBACK32.

  • Page 967: Restoring Data

    Restoring Data Use SBCON to restore information from tape backup. These procedures use SBCON as the Storage Management Engine (SME). Know the username and password for the target server or workstation to which you want to restore data. Know the session description that you want to restore. You can get this information from your session log and error files.
  • Page 968 Load SBCON. “Loading SBCON” on page Select Main Menu > Job Administration > Restore. The Restore Options screen appears. Select Target Service and then the NetWare server running your backup and restore Target Services Agent. This is the name of the server or workstation on which you want to restore your data.
  • Page 969 Target Service to Restore Dataset to Select Workstation The workstation's host server and then the workstation Server-specific The server whose server-specific information information you want to restore and then the file system to restore When prompted for the target username, enter your username (and context if required) as the network administrator for the target.
  • Page 970 volume without compression, the file is corrupted and no error message is displayed. Specify the path to the session log file of the session you want to restore. Use one or more of the following methods: Press Enter to accept the default; then go to Step 12 on page Press Insert to select from a list of directories, press Esc to return to the previous window, and then go to...
  • Page 971 The Esc key allows you to exit SBCON one screen at a time until you reach the Main Menu. If you want to exit SBCON, answer the confirmation prompt. NOTE: To unload SBCON and applicable Target Service Agents, see “Unloading SBCON”...
  • Page 972 The screen lists major and minor resources. Default indicates that none of that type of subset has been specified. To specify a subset, do the following: Select any item on the screen. Edit the Include or Exclude screens using Insert and Enter. Press Esc to save changes.

  • Page 973: Restoring Data From A Workstation

    Restoring Data from a Workstation When you restore data, you are copying your backed up data to a server or workstation. Run NWBACK32. “Loading NWBACK32” on page You can run the NWBACK32 program (NWBACK32.EXE) from SYS:PUBLIC. At the Quick Access window, click Restore. Click What you Want to Restore.

  • Page 974: Restoring Edirectory

    Restoring eDirectory The procedures in the following sections are performed at the beginning of the restore process. “Restoring a Volume Other Than SYS:” on page 69 “Restoring Volume SYS: in a Single-Server Network” on page 69 “Restoring Volume SYS: in a Multiple-Server Network” on page 70 “Restoring the Entire eDirectory Tree Structure”...
  • Page 975 Make sure disk partitions are at least as large as they were before, and that the volumes are defined as before. Restore eDirectory using “Customizing Restore” on page Restoring Volume SYS: in a Multiple-Server Network To restore SYS: volumes on several servers, do the following. Restore the server-specific eDirectory information file (SERVDATA.NDS) to another server on the network following the custom (advanced) file system restore (see...
  • Page 976 Select Remove This Server from the Replica Ring. Enter the supervisor name and password. Select Yes to continue. Exit DSREPAIR. Reinstall NetWare. Begin the installation. When prompted for DS install, select Create a New DS Tree and complete the installation. Load NWConfig and remove DS.
  • Page 977 Restoring the Entire eDirectory Tree Structure To restore an entire network from a full backup in a multiple-server environment, do the following: Reinstall NetWare on the first server. By default, this server will hold the master replica of the [Root] partition. When NWCONFIG asks for the names of Organization objects immediately under the [Root] object, use the same names that existed before in the eDirectory tree.

  • Page 978: Edirectory Restore Session Types

    eDirectory Restore Session Types You can choose to restore eDirectory in one of the following ways: “Single Server or an Entire Tree Restore” on page 73 “Custom eDirectory Restore” on page 73 “Custom File System Restore” on page 74 “Server-Specific Information Restore” on page 76 “Single File or Directory Restore”...
  • Page 979 If you do not want to overwrite the parent or child that exists on the hard disk, regardless of whether the existing version or the backed-up version has the latest date, select the option (parent or child or both), and enter N. Continue through Step 14 on page 65 Step 19 on page...
  • Page 980 Follow these important rules about restoring to a new location: When you specify a particular portion of the file system structure as the source location, it does not necessarily mean that this will be the only data restored. You can influence what is restored by using the Include and Exclude options on the Choose Subsets Of What You're Restoring screen (Job Administration >...
  • Page 981 If you want to overwrite the child that exists on the hard disk only if the date of the backed-up copy on the media is later than the date of the copy on the hard disk, select Overwrite Existing Child and select the option. Continue through Step 15 on page 65 Step 19 on page...
  • Page 982 Press Insert and enter the name space for the name space format you used when entering the file or directory name. The name space allows SBCON to correctly interpret the path information entered earlier in this menu in either the directory field or the location field.

  • Page 983: Completing The Edirectory Restore

    Completing the eDirectory Restore If you restored the eDirectory database to volume SYS:, you should complete the restoration for the following to make sure the eDirectory database is working properly: Volume Other than SYS: To finish restoring eDirectory on a volume other than SYS:, do the following. Bring the server up.
  • Page 984 Entire Tree To finish restoring eDirectory on the tree, do the following. Restore the file system information to each server following “Restoring Data” on page Re-create partitions and replicas. (Optional) Verify proper restoration of the data, trustee assignments, file ownership, and other related information by spot-checking some of the restored directories and files.

  • Page 985: Restoring Cluster-Enabled Pools

    identifies the file server on which the queue directory resides. This information is used to determine the physical location of the resource. The specifics of restoring objects vary depending on what type of object is involved and whether the object's dependencies are physical entities (servers and volumes) or logical entities.

  • Page 986: Managing

    Managing After you install and load SBCON, you can manage your jobs, data, devices, reports, and so on either from the server or workstation. Though the screens might look different, you can perform the same tasks in each interface. Be sure to read “Prerequisites for SBCON Tasks”...

  • Page 987: Jobs

    Jobs The backup or restore jobs created by you can be administered anytime. You can delete, hold, reschedule, abort, or enable a job. Administering Jobs Jobs can be managed either from the server or from the workstation. From the Server On the SBCON Main Menu at the server, the Current Job List option gives you a job management facility where you can delete a job, hold a job, or enable it if it has been disabled after a job failure.
  • Page 988 Dynamic properties contains data that indicates how much data has been backed up along with the filenames. This dialog box appears when a job is running and SBSC is loaded on the server. Enable job allows you to start a job that has been disabled. Delete the job allows you to remove a job.
  • Page 989 Viewing Job Details This screen gives you all the details of the job you submitted including job name, the time the job was submitted, and the time the job should be executed. You can also schedule the job to run at a predefined time again after its execution.
  • Page 990 Serviced By—This indicates the name of the server where the job is to be executed. From a single server, you can submit jobs to various servers. This field indicates which job is serviced by which server. This field is active only when the job is active; otherwise, it indicates None.

  • Page 991: Storage Devices

    From a Workstation At the Quick Access window, click Job Administration. Double-click the context. Double-click Queues. Select the job to place on hold. Right-click the job and then click Start/Hold the Job. (Optional) You can also hold the job using the toolbar. Click Job Administration >...
  • Page 992 From the Server Select Main Menu > Storage Device Administration. Select a device and press Insert. Select Utilities > Device Status. The Device Status screen is displayed listing the following information: Current Operation—Indicates whether the device is currently reading, writing, formatting the media, or none of these. Device Mode—Indicates whether the device is selected for reading, writing, or both.
  • Page 993 You can change a device label from the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page From the Server Select Main Menu > Storage Device Administration. Select a device name and press Insert. Select Utilities >...
  • Page 994 From the Server Select Main Menu > Storage Device Administration. A list of devices is displayed. If no device is displayed in the list, run LIST DEVICES at the server prompt. Select a device name and press Enter. The List of Media screen appears displaying the following information: Slot—The slot number given by the manufacturer.
  • Page 995 Erasing or Retaining Media This task erases media headers, erases all data on the media, or retentions media in tape devices. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page The following table describes all media options. Option Explanation Change the Media Label...
  • Page 996 Double-click Queues. Double-click the preferred queue. Double-click Servers. Double-click the preferred server. Double-click Devices. Right-click the media > click Erase Media [or] Retension. (Optional) You can also use the toolbar. Click Device Administration > Media > Erase Media [or] Retension. Checking the Media Status in a Device This task lets you check the status of a particular media type from either the server or a workstation.

  • Page 997: Spanning Storage Media

    Media mode—Whether the media is selected for reading, writing or both, or whether the mount request is pending. Media type—The type of media in the device, such as 4mm DDS (Digital Data Storage) tape, or 8mm tape. Total capacity—The total capacity of the media, if known. Sometimes it is not displayed, depending on the media manager.

  • Page 998: Log And Error Files

    Log and Error Files SBCON keeps a list of all the log and error files, which show specific information about the backup and restore session. See “Session Files” on page for more information. You can manage these files as follows: View information contained in the log and error files.
  • Page 999 To change the directory, delete the existing directory path and type a new one, and then go to Step 3 on page You can also press Insert during this process to select existing parts of the path from a list. The backup log displays all supported name space types.
  • Page 1000 From the Server From the SBCON Main Menu, select Log File Administration > View an Error File. If necessary, set the location of the log and error files for a backup session. (This option is not supported for a restore session.) To set the location, use one or more of the following methods: Press Enter to accept the default location, and then go to Step 3 on...
  • Page 1001 Double-click the preferred queue. Double-click Servers. Right-click the preferred server. Select Error Report. Creating Log and Error Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks”...

This manual is also suitable for:

Netware 6

Table of Contents