Softmirror Netware

1)Убираем клона.
2)Смотрим, что без него все работает.
2)На другой или этой же машинке с клона удаляем ВСЕ разделы.
Ну можно и нужно ДОС раздел оставить, если он есть на работающем диске. Новый диск должен быть девственно чист и никакими разделами не занят, кроме
ДОС.
3)После чего идем в NSSMU, в Raid device открываем по очереди каждый объект и удаляем сегменты, находящиеся в OFFLINE!!!!.
4)Потом идем в Disk Partition и кнопочкой F3 зеркалим нужные разделы.
Ошибиться невозможно, зеркалится только на свободное пространство.

P.S.
Поэтому, поскольку вы сделали клона, зеркалирование принципиально невозможно сделать. А в инете вряд ли найдете, все просто как грабли.
Если бы вы хоть раз сами сделали зеркало NSS, вы бы сразу поняли, что нужно делать.

инфа с форума

Установка ncpfs в CentOS 5.x

Установка ncpfs в CentOS 5.x  

Собственно нужен только nsend, для рассылки сообщений по сети клиентам NetWare.

wget http://arm.koji.fedoraproject.org//packages/ncpfs/2.2.6/13.fc12/src/ncpfs-2.2.6-13.fc12.src.rpm
rpm -ivh ncpfs-2.2.6-13.fc12.src.rpm
rpm --nomd5 -ivh ncpfs-2.2.6-13.fc12.src.rpm
rpmbuild -ba  ncpfs.spec   (получаем ipxutils-2.2.6-13.i386.rpm и ncpfs-2.2.6-13.i386.rpm ...)
rpm -ivh -- nodeps ncpfs-2.2.6-13.i386.rpm

p.s. ipxutils не нужен т.к. nsend отлично работает по tcp/ip

iManager. Перенос на другой сервер

Netware 6.5 sp8 eDir8.3.7
Вывожу из эксплуатации старый сервер. Новый с среде VMWare.
iManager 2.7.3 (Field Patch 4 for iManager 2.7.3)
На новом сервере iManager подхватил новые плагины, CIFS не корректно работает, на старом все устраивало. Задача сделать iManager на новом, как на старом.

Скопировал папку sys\tomcat со старого на новый сервер

tc4stop
tc5stop
ap2webdn
java -exit

sys:\tomcat\4\bin\startup
sys:\tomcat\5.0\bin\startup
ap2webup

-----------------------------------------------------------------------

Если устарели сертификаты, Переиздать и перегрузить Apache

But whenever I type tc4stop or tc5stop or tomcat4 or tomcat 5 all the
console responds with is...."Loading Module Perl.NLM. Autoloading Module
LibPerl.NLM

I don't think that's the correct behavior if I am trying to shutdown or
start Tomcat. Any thoughts?

That tactic is below...

NETWARE: tc4stop
(Terminate Tomcat. For Tomcat 5.0, use tc5stop instead.)

NETWARE: ap2webdn
(Shutdown the Apache web server.)

NETWARE: java -exit
(Shutdown Java.)

NETWARE: pkidiag
(This will open the PKI wizard for detecting and repairing public key
infrastructure in Netware. Follow the menu items namely 4, 5, 6, 0)

NETWARE: tckeygen
(Restore LDAP connectivity for Tomcat.)

After a few minutes, start the services.

NETWARE: tomcat
(You may also use /tomcat/5.0/bin/startup start to start Tomcat 5.0.)

NETWARE: ap2webup
(Start up the Apache web server.)

SDIDIAG

Verify That Your SDI Domain Key Servers Are Ready for Universal Password

TID-10086669 Using SDIDiag - Switches and Options ( 23SEP2005)

SECURITY DOMAIN SERVER MANAGEMENT

Name	Shortcut Command	Command
Add All Write Partition Servers	ADDPARTITIONSERVERS	AP
Add Domain Server	ADD	AS
List Domain Server	LISTSERVERS	LS
Remove Domain Server	REMOVE	RS
Sync Domain Server	SYNCDOMAIN	SD

SERVER MANAGEMENT

Name	Shortcut Command	Command
Find Servers in Container	FINDSERVERS	FS
List Server Keys	LISTKEYS	LK
Resync Keys for Container	RESYNC	RD
Sync Server Keys from Domain	SYNCSERVER	SS

DIAGNOSTIC

Name	Shortcut Command	Command
Check Key or Domain Problems	CHECK	CK

OTHER COMMANDS

Name	Shortcut Command	Command
Help on most used commands	HELP	HE
Exit SDIDiag	EXIT or QUIT	E or I

>	Redirected output to a file using the '>' redirection switch.
>>	Append output to an existing file.
-A	Access servers regardless of their eDirectory or NICI versions. By default SDIDiag Version 2.00 Thursday, May 22, 2003, references only servers running eDirectory version 8.7.1 or higher. NOTE: It is strongly recommended that all servers be running a minimum of NICI 2.4.2 or higher.
-F	Force operation. Depending on the command, the -F switch removes any Security Domain Servers that do not hold a writeable replica of the W0.KAP.Security object.
-G	Generate a new key. When used with the SD command, all Security Domain Servers will be synchronized to hold this new key.
-I file	Specify an input file of server names to access. This switch specifies a file that holds a list of serverDNs for the command to process. In most cases, the objects are fully qualified dot delimited distinguish names with one server per line. Normally the -O file switch creates this file.
-N containerDN	Specifies with a fully qualified dot delimited distinguished name of a container that the command will reference.
-O file	Create an output file of server names. This switch defines a file to hold output information that may be passed to a command via the -I file switch. Normally, the -O file switch will contain a fully qualified dot delimited distinguished name list of servers.
-R	Revoke all keys. The -R switch will implicitly perform a -G switch operation after revoking all the keys.
-S serverDN	Specifies with a fully qualified dot delimited distinguished name a server name. NOTE: serverDN includes the tree name, for example: -S SERVERA.NOVELL.TEST-TREE
-T	Two pass "Comprehensive" switch for the RD command.
-U file	Create a file of server with incompatible NICI SDI support. The -U switch creates a file that contains a fully qualified dot delimited distinguished name of servers on which NICI must be upgraded to fully support multiple SDI keys. Server names are not displayed when this switch is omitted.
-V	Verbose, display all messages to SDIDiag console.
-X	Limit the search for servers to the container specified with the -n containerDN switch.

EXAMPLES OF SDIDiag COMMANDS

SECURITY DOMAIN MANAGEMENT
AS [-A] [-V] [-S serverDN]  [> file | >> file]
Add server -S serverDN as a Security Domain Server.
Another way to do this is to open Console One and go to the W0 object in the Security Container. Select the "Other" tab on the W0 object and add an additional server as an attribute value to the "NDSPKI:SD Key Server DN" attribute.
LK [-A] [-V] [-S serverDN]  [> file | >> file]
List keys held by the Security Domain Servers.
All servers which are listed under the "NDSPKI:SD Key Server DN" attribute on the other tab of the W0 object will be displayed with their associated SD Keys.
LS [-A] [-V] [-S serverDN]  [> file | >> file]
List the current Security Domain Servers.
Another way to gather this information is to open Console One and go to the W0 object in the Security Container. Select the "Other" tab on the W0 object and view the values of the "NDSPKI:SD Key Server DN" attribute.
RS [-A] [-V] [-S serverDN]  [> file | >> file]
Remove server -S serverDN as a Security Domain Server.
This can also been done through Console One by going to the W0 object in the Security Container. Select the "Other" tab on ther W0 object and delete a server shown as an attribute balue to the "NDSPKI:SD Key Server DN" attribute.
AP [-A] [-V] [-F] [> file | >> file]
Add any server hosting a writeable replica of the .W0.KAP.Security.Tree-Name object as a Security Domain Server.
If the -F switch is given, additionally remove any servers that do not hold a writeable replica.
 SD [-A] [-V] [-R] [-G] [-S serverDN ] [> file | >> file]
Synchronize the Security Domain Servers. The optional -R switch revokes all existing keys and generates a new SD key for use within the tree. The optional -G switch generates a new SD key.

NOTE: If either the -R or -G switches are used, then the RD command may need to be used to resynchronize the new keys to the other servers in the tree.
Revoked keys are retained and used to access any existing items, however, they are not used to manage new keys.
SERVER MANAGEMENT
FS [-N containerDN] [-X] [-O file] [-U file]
Find all servers starting with the -N containerDN and all sub-containers unless the -X switch is given, in which case, limit the search to the -N containerDN only. Output all eDirectory 8.7.1 servers or higher to a file using the -O file while all other server that are listed are outputed to the -U file. The -O file  may be used as an input to any commands that the support the -I file switch.
LK [-A] [-V] [-S serverDN ] [> file | >> file]
List keys held by -s serverDN.
Example of using LK is:
SDIDIAG> LK -A -S .servername.org.tree_name
RD [-A] [-V] [-T] [-N containerDN] [> file | >> file]
Resynchronize the Security Domain Servers with other servers in the tree.
If the -T switch is given, RD or RESYNC, performs a two pass operation by first ensuring that the Security Domain Servers have a copy of all keys on all referenced servers.
Secondly, RD resynchronizes all servers with the updated Security Domain Servers.
If the -N switch is omitted, RD attempts to resync all servers within the tree; whereas when the -N containerDN switch is provided, RD only resynchronizes the Security Domain with all servers holding writeable replicas of the specified containerDN partition. It 1460 persist, then a full RESYNC may be attempted which may take a considerable time as every server will need to be contacted.
Examples of using RD are:
SDIDIAG> RD -T -n .orgUnit.org.tree_name.
SS [-A] [-V] [-R] [-S serverDN] [-I file] [-N containerDN]
Synchronize all keys on the specified -S serverDN, severs in listed in the -I file, or server hosting a writeable replica of the -N containerDN with the Security Domain Servers. The -R switch may optionally be given to revoke all the existing keys on the server before synchronizing with the Security Domain Servers.
Example of using SS is:
SDIDIAG> SS -A -R -S .servername.org.tree_name
DIAGNOSTIC
CK [-A] [-V] [-N containerDN] [> file | >> file]
Check and display possible problems and display recommendations for the Security Domain Servers. If the -N containerDN is provided, also check the servers hosting a writeable replica of the -N containerDN object for possible problems and provide recommendations.
Examples of using CK are:

SDIDIAG> CK
SDIDIAG> CK -N .orgUnit.org.tree-name
SDIDIAG> CK -A -N .orgUnit.org.tree-name >> SYS:\TEMP\OUTPUT.TXT

Install Nw65sp8

eDir 8.7 (instead of eDir 8.8) for a new server installation

If you need to install a new server with eDir 8.7, then boot from NW65SP8 Overlay CDs or DVD. When prompted to press any key to interupt the boot process, do so. Press "p" and specify this parameter (including the squared brackets):
[INST:spedir]
Press ENTER, then "i" to proceed with the installation as usual. This will give you eDir 8.7.3.10, instead of 8.8.4.        Взято

Installing VMware Tools in a NetWare Virtual Machine

1. Power on the virtual machine.

2. Select VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

3. Load the CD-ROM driver so the CD-ROM device mounts the ISO image as a volume. Do one of the following.

In the system console for a NetWare 6.5 virtual machine, type

LOAD CDDVD

In the system console for a NetWare 6.0 or NetWare 5.1 virtual machine, type

LOAD CD9660.NSS

4. When the driver finishes loading, you can begin installing VMware Tools. In the system console, type

vmwtools:\setup.ncf

When the installation finishes, the message VMware Tools for NetWare are now running appears in the Logger Screen (NetWare 6.5 and NetWare 6.0 guests) or the Console Screen (NetWare 5.1 guests).

5. Restart the guest operating system. In the system console, type

restart server

 

TRUSTBAR.NLM

Using TRUSTBAR.NLM to backup file system trustees

This document (3925492) is provided subject to the disclaimer at the end of this document.

Environment

Novell NetWare 5.0
Novell NetWare 5.1
Novell NetWare 6.0
Volumes Traditional and NSS.
Network Storage Services (NSS)

Situation

Using TRUSTBAR.NLM to backup file system trustees

Resolution

In order to backup file system trustees on an NSS volume before a NetWare 6 inplace upgrade or an across the wire migration, TRUSTBAR.NLM should be used. TRUSTBAR.NLM can be found on the NetWare 6 shipping CD in the PRODUCTS\NCS directory. TRUSTBAR will backup both NSS and Traditional volumes. HINT: Use CONLOG.NLM to log all error messages written to the screen. NOTE: TRUSTBAR does NOT work with NetWare 4.x.

NOTE: Logins must be enabled for TRUSTBAR to work. Make sure that logins are enabled before running.

TRUSTBAR usage:

TRUSTBAR [path]: [-options]

OPTIONS: H B R D V
-H Help
-B Backup trustees
-R Restore trustees
-D Delete trustees
-V Verbose (outputs results to the console)



TO BACKUP TRUSTEES
To back up all file system trustees on VOL2, type the following at the system console prompt:

TRUSTBAR VOL2: -B -V (don't forget the COLON after the volume name)

The output will be similar to the following:
TRUSTBAR: server FS1 DN CN=FS1.OU=Servers.O=novell serverID 0
TrustBar_Trustees(VOL2:Email/Secretary): backup TID 0xB612 name CN=kjones.O=novell rights 83
TrustBar_Trustees(VOL2:Email/Secretary): backup TID 0xB6A1 name CN=dsmith.O=novell rights 65

TRUSTBAR creates a file at the root of whatever volume being backed up called "trustees.xml". Once the file is created, it can be renamed and moved elsewhere. WARNING: if you run TRUSTBAR on a volume which already has a "trustees.xml" file at the root of the volume, the file will be overwritten.



TO RESTORE TRUSTEES
To restore file system trustees, type the following at the console:

TRUSTBAR VOL2:\trustees.xml(or different filename) -R -V (Remember the COLON after the volume name)

The XML file must be somewhere on the volume on which the trustees are being restored, but not necessarily at the root of the volume. If the XML file were in a sub directory called TEMP and the file was renamed to VOL2.XML, the following command would be used:

TRUSTBAR VOL2:\temp\vol2.xml -R -V



TO DELETE TRUSTEES
To delete all file system trustees on VOL2, type the following at the system console prompt:

TRUSTBAR VOL2: -D (don't forget the COLON after the volume name)

***NOTE - This will remove trustee assignments without warning. Please verify that you have Backed up your Trustee Assignments before doing so.***

Additional Information

Formerly known as TID# 10066145

Создание snapshot в Netware

 Взято от сюда http://www.novell.com/coolsolutions/appnote/17000.html


Let's assume that the production server has a DATA pool and a DATA volume. We want to create a snapshot of the DATA pool hosted on the DATA pool. To do this, key the following commands on the production server.

1. To create snapshot: mm snap create DATA DATA DATA_S1
The syntax to create a snapshot is: mm snap create snappool datapool snapname The snappool is the pool that I want to take a snapshot of. In this case, it is DATA The datapool is the pool that the snapshot should reside. In this case, it is also DATA. The snapname is the name of my snapshot. In this case, it is DATA_S1
2. To activate snapshot: mm snap activate DATA_S1
3. To mount the data volume on the snapshot pool: mount DATA_SV
4. To deactivate snapshot: mm snap deactivate DATA_S1
5. To delete snapshot: mm snap delete DATA_S1

Therefore, what we want to achieve is to create and activate a snapshot before the RSYNC synchronization and then after the synchronization is completed, deactivate and delete the snapshot. To achieve this, modify the SYS:\ETC\CRONTAB to include the following lines:

0 18 * * * TRUSTBAR DATA: -B -V 0 19 * * * SYS:\SYSTEM\CREATESNAPSHOT.NCF 0 20 * * * SYS:\SYSTEM\DATABACKUP.NCF 0 6 * * * SYS:\SYSTEM\DELSNAPSHOT.NCF

where CREASNAPSHOT.NCF contains the following lines:

mm snap create DATA DATA DATA_S1 delay 60 mm snap activate DATA_S1 delay 60 mount DATA_SV

where DATABACKUP.NCF contains the following lines:

rsync -rRutvP --delete --volume=DATA_SV: / [IP address of Backup server]::DATA Note: The volume is now DATA_SV not DATA

where DELSNAPSHOT.NCF contains the following lines

dismount DATA_SV delay 60 mm snap deactivate DATA_S1 delay 60 mm snap delete DATA_S1

 ---------------------------------------------
MM SNAP LIST