On 2010-10-14 12:36, davidm01 wrote:
> Ok, have talked to one of the two people who were doing this, and am
> getting a moderately good picture of what decisions have been made, and
> what has happened. I should emphasise right away that what caused us to
> get into the situation we are may or may not get us back to a working
> system, but here goes.
> This was an experienced and loyal Novell user. To move forward, it was
> wanted to continue with a familiar system if possible, and the nearest
> was SLES netware. We wanted simple user rights management, nothing much
> except file and iPrint services, NSS file system and Salvage. Extensive
> attempts to achieve this with SUSE 11.1 and 11.2 failed to support
> Netware. Success was achieved with SUSE 10.2.0.91, and there was a good
> system running tests for weeks. -There are weeks of effort in this
> system concerning setting up users, data, facilities etc. All this is
> going to waste right now.-
Netware is a commercial product of Novell, and I’m not familiar with it, except it existence. I had
to look it up in the wikipedia. I don’t see “SLES netware” there.
What you have might be this:
Open Enterprise Server
Main article: Novell Open Enterprise Server
OES 2 was released on October 8, 2007. It includes NetWare 6.5 SP7, which supports running as a
paravirtualized guest inside the Xen hypervisor and new Linux based version using SLES10.
Novell Open Enterprise Server (OES) is the successor product to Novell, Inc.'s NetWare operating
system, based on Suse Linux Enterprise Server. Originally released in March 2005, the current (2009)
release is OES 2 SP2.
Novell Open Enterprise Server (OES) is best thought of as a platform for delivery of -level shared
network services (file, print, directory, clustering, backup, storage management, PKI, web
applications, etc.) and common management tools. OES can run atop either a Linux or a NetWare
kernel. Clustered configurations can include nodes with either kernel types, and most services can
migrate freely between the platforms. Thus, customers can deploy the platform selection that best
suits their needs, as opposed to being locked into a single platform.
When installed using a Linux kernel, the product is known as OES-Linux. This uses SUSE Linux
Enterprise Server (SLES) as its platform. Atop the SLES install, daemons are added to provide NCP,
eDirectory, NSS, iPrint and other services delivered by OES.
When installed using a NetWare kernel, the product is known as OES-NetWare. This uses NetWare v6.5
as its platform. Atop the NetWare install, NLMs are added to provide Apache web server, Tomcat,
OpenSSH, NCP, eDirectory, NSS, iPrint and other services delivered by OES.
I have absolutely no experience with this setup (and I don’t have clear which one of those it is) -
you have to ask your vendor. At least, ask on the Novell SLES/SLED forums, not the openSUSE forums.
In your first post you mentioned “SUSE OES netware server”, which means the OES-NetWare above ->
netware kernel. This has nothing to do with these forums, you can not ask us to help you if that is
what you have.
Thus I’ll assume you have OES-Linux as above description.
> Before going live, the final tests of imaging and daily backup were
> begun, using Acronis Backup & recovery 10 Advanced server. This needs
> to be installed under yast in order to be scheduled, which was done.
> Attempts were made to backup to a USB drive, one could set the drives to
> backup and set the drive to backup to, but execution failed with errors
> ‘could not create archive’. Discovering a need to run linux software to
> enable writing to NTFS formatted drives, so this was installed.
Acronis is a comercial product with which I’m not familiar. I can’t help.
About NTFS writing, I have to assume that you got it from official channels…
In any case, using ntfs to backup some kind of linux system, is generally a mistake.
> A successful write of a small test file was completed, so the main
> server drives backup was begun, resulting in the same sort of ‘could not
> create archive’ error as before, plus other critical errors such as
> 0x00000FF1 and 0x0000FF2. FF1 seems to have to to with permissions. FF2
> is unknown. At this point the server was frozen, and after a hard reset
> could not be restarted. Which is where we are now. The server seems to
> be full, the partitions don’t seem to be completely described.
I can’t even give educated guesses.
> I know just enough to run a few listing commands. Here are the
There are partitions, of a type I never used. And two raids (dm-0, 1)
> device boot start end blocks Id system
> /dev/sda1 * 1 9 72261 83 Linux
> /dev/sda2 19 1966 15719602+ 8e Linux LUM
> /dev/sda3 1967 88849 697887697+ 65 Novell Netware 386
> Right now, the console screens say
> F1 screen
> about 30 lines ending
> Found a Linux console termial on /dev/console…
> *** Starting YAST2 ***
You are running the install CD, I guess. You did not say.
Sorry, I can’t help you.
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)