AFP Issues - SLES 10 SP3 / OES2 SP2

I'm having issues with AFP. The service seems to be working then will stop at least once a day. If i do a 'rcnovell-afptcpd status' it shows "unused". Sometimes I can get the service to work again by 'rcnovell-afptcpd start', but in some cases it won't restart until I reboot the server.
I'm using novell-afptcpd-1.1.0-0.13.5 is there a newer version? Is there a configuration problem that could be causing this?

gwatson wrote:
>
> I'm having issues with AFP. The service seems to be working then will
> stop at least once a day. If i do a 'rcnovell-afptcpd status' it shows
> "unused". Sometimes I can get the service to work again by
> 'rcnovell-afptcpd start', but in some cases it won't restart until I
> reboot the server.
>
> I'm using novell-afptcpd-1.1.0-0.13.5 is there a newer version? Is
> there a configuration problem that could be causing this?
>
>
When is the last time you did the channel updates. I don't remember what the
latest version is but they have done a lot of fixes in the end of July
patches.

Similar Messages

[SOLVED] Upgrade from SLES10 SP3 & OES2 SP2 to SP4/SP3 breaks NCS

Hi folks,
(This post was originally meant to be a rant and a request for help, but
while writing the final paragraph i found the solution. It's still a
rant, but i figured i'd post my solution here in case someone else runs
into the same issue.)
I've just spent several hours banging my head against a broken cluster
node. My system is a 32-bit SLES 10 VM running on VMware ESX 3.5.x.
I upgraded from SLES10 SP3 and OES2 SP2 to the next service packs for
each (using the move-to-oes-sp3 script in yast2 online_update).
Everything went well for the first few update/reboot sequences, then
after the final reboot on SLES10 SP4 & OES2 SP3, cluster services would
not load or join the cluster on restart.
I checked dmesg and found errors about "Loading module compiled for
kernel version 2.6.16.60-0.54.5-vmi" into a previous kernel version, so
i tried downgrading to that kernel version, only to find that it was
older than the one i had just upgraded from (it's the original SLES10
SP3 kernel). So i tried upgrading back to the same kernel which is
running on the other cluster node (2.6.16.60-0.77.1-vmi), but that did
not work any better.
<preaching>
I have to say that i'm not impressed that OES2 SP3 isn't even compiled
against the appropriate kernel, and because of SUSE's kernel RPM
overwrite policy there's no way i can select to boot from a previous
kernel to see if that fixes things. Note to SUSE and other distro
builders: if you're not doing kernel package upgrades like Red Hat or
Ubuntu (so that we can select to boot from the previous kernel from the
boot menu), you're doing it *WRONG*.
</preaching>
I then upgraded again to the latest recommended kernel for SLES10 SP4,
and still no joy. Dmesg shows this error before the rot starts:
allocation failed: out of vmalloc space - use vmalloc=<size> to increase
size.
When searching for this error i stumbled across
http://ubuntuforums.org/showthread.php?t=1613132
which pointed me to
http://www.mythtv.org/wiki/Common_Pr...lloc_too_small
Adding vmalloc=192M to /boot/grub/menu.lst and rebooting solved the
problem for me.
Regards,
Paul

Originally Posted by Paul Gear
On 13/10/11 07:36, magic31 wrote:
> ...
> Not sure if it's related to the issue you've hit, but along the lines
> of what Kevin already mentioned, there are issues that can arries when
> using the VMI kernel (that I've seen) if having multiple flavors of the
> kernel installed along with it (as in having both kernel-vmi as also
> kernel-smp packages installed) ...
> Curious, is that also the case with your setup?
The system in question has kernel-bigsmp and kernel-vmi installed. We
only ever boot from kernel-vmi.
> I've moved to only using the smp kernel on VMware (along with the
> clock=pit boot option to avoid time drift issues, or pmtr I think in
> your case when also running NCS services in the vm).
When we installed the system (on OES2 SP1, i believe) it was a while
ago, and kernel-vmi with clocksource=acpi_pm on the kernel command line
was the only solution we could find to get reliable time. If there are
updated best-practice documents, i'd be happy to hear about them.
However, this is a production cluster and my boss is (rightly) rather
reticent to make major changes.
Paul
the official Vmware paper on time is that IF you're using SLES 10.x 32-bit you will use VMI and NO kernel params (ie, get rid of the clockpit and clocksource=blah).
But if 64-bit then you're okay.
The easiest, IMO (especially with vmware) is to use the miggui (migration utility). That's how I'm converting all my 32-bit servers in vmware to 64-bit. Works quite well.
--Kevin

NetStorage server without eDirectory installed on Linux OES2-SP2

Hello Forums
I was wondering if NetStorage can be working on a Single
SLES10-SP3/OES2-SP2, server without actually having eDirectory on the
server itself but pointing the NetStorage configuration to any server
holding a R/W replica of eDirectory, by this making the NetStorage
easier to move to e.g. DMZ, e.t.c, or just making it a simpler setup for
the NetStorage.
I have tried this with 2 servers, one server with eDir installed and one
where only NetStorage is "ticked" under the OES Install and Configuration.
I can get as far as getting the login page up byt aint able to authenticate.
for the Certificate i took the pem file from the server i points to and
place in the /etc/ssl/servercerts/xxx.pem
Well i think i read sometime this was possible without eDirectory
actually on the NetStroage server, could be i'm Wrong.
Any ideas on this would be great.
Thanks
- Michael

Any OES2 server HAS to have eDirectory on it (that I'm aware of to function properly). However, you may be asking the question in the wrong way. Not sure how you'd login to iManager on the OES2 server to manage NetStorage if the eDir database isn't on there.
You MAY be wanting to know if the OES2 server needs an eDirectory REPLICA on it (there's a big difference).
If that's what you REALLY are asking, then the answer is:
No, you do not need an eDir replica on the server that runs NetStorage. In fact, you could even put the NetStorage server into its own tree if you had to (it's a little more complex to setup at that point, but it CAN be done).
I hope this helps.

Migedir Error going from NW6.5SP8 to OES2 SP2 on SLES10 SP3

I've searched the forums and was not able to find this particular problem so hopefully someone more knowledgeable than I can help. I have an issue with the Transfer ID utility erroring out at the DIB copy portion of a NetWare 6.5 SP8 migration to 64-bit OES2 SP2. The eDirectory Precheck and Preparation portion of the Transfer ID complete successfully with green check marks. When the Transfer ID gets to the DIB copy part I get a series of error messages.
This is the error from the mignds.log file:
05-05-2011:09:56:20:Information: The DS version on the source server is 10554.
05-05-2011:09:56:20:Fatal: Setting up the NetWare eDirectory migration environment...
05-05-2011:09:56:20:Information: Package 'ncpfs' has been installed.
05-05-2011:09:56:20:Information: Mounting the SYS volume of 'xxx.xxx.xxx.xxx' at /var/opt/novell/.edir_migrate/mnt...
05-05-2011:09:56:20:Information: SYS mounted successfully.
05-05-2011:09:56:20:Information: 'novell-ncpserv' package is available.
05-05-2011:09:56:20:Information: Copied scp peer file (ncpmig.nlm) to source server successfully.
05-05-2011:09:56:20:Fatal: SERVER: load nlm ncpmig.nlm failed rc=158.
In the Transfer ID Migration Log this is what appears:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:*****************Command output start**********************************
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:eDirectory migration utility for Linux
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Version: 2.0 for OES Linux 2.0
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Copyright (c) 2007, Novell Inc. All rights reserved.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Creating the eDirectory migration file locations...
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Get the source server administrator credentials -
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir: Enter adminDN(e.g: cn=admin.o=administrators): Enter password:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Source server, xxx.xxx.xxx.xxx is reachable.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:The source server, xxx.xxx.xxx.xxx is running on NetWare platform.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:OS Version: v5.70.8
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Product Version: v6.50.8
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:NCP Engine Version: 1
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:NCP Engine Platform: 0:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:The NetWare source server is running on OES Platform
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:eDirectory packages are installed.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Performing pre-migration checks on the source server, 'xxx.xxx.xxx.xxx'...
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:ndscheck performed successfully.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Checking time synchronization between source and target servers.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Source and Target servers are in time synchronization
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Performing eDirectory migration...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:This may take time depending on the size of the data on the server that is being migrated.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:The DS version on the source server is 10554.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Setting up the NetWare eDirectory migration environment...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Package 'ncpfs' has been installed.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Mounting the SYS volume of 'xxx.xxx.xxx.xxx' at /var/opt/novell/.edir_migrate/mnt...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:SYS mounted successfully.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:'novell-ncpserv' package is available.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Copied scp peer file (ncpmig.nlm) to source server successfully.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:ERROR: Could not load secure NCP NLM, ncpmig.nlm on the source server - SERVER: load nlm ncpmig.nlm failed rc=158..
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:SERVER: load nlm ncpmig.nlm failed rc=158.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:*****************Command output end**********************************
It looks like the Mig utility can't run ncpmig.nlm on the source server for whatever reason. The previous steps completed successfully so I don't think it's an issue of login rights. The OES2 SP2 server is fully patched with all critical and optional patches. I'd like to add that I've done a couple migrations in my test lab prior to this and they both went through smoothly. I'm also following the exact same steps I used when I performed the lab migrations.
I've also tried the same migration using OES2 SP1 (fully patched and not), OES2 SP2 (non-patched) and OES2 SP3 (patched and not) with the exact same error message. This leads me to believe it's something in the source server causing the issue but I can't, for the life of me, figure out what.
Source server is running NW6.5 SP8 and eDir 8.7.3.10. Target server is OES2 SP2 and eDir 8.8.5 HP6. Does anyone have insight into why the Transfer ID is failing at the DIB copy? Thanks in advance.

Sorry for the late reply. Been extremely busy with our migrations and other issues. To answer the last question, our default administrator login to the tree is not called admin. We prefer not to use default names as they decrease security. I used my own login credentials, which also has full rights to the tree, to proceed with the migration. Determined, as a precaution, that the person performing the migration should add him or herself as a trustee to the source/destination servers AND the container the server objects live in. It's probably a redundant step but should decrease the likelihood of encountering the original issue.

OES11 SP2 -- Use SLES SP3?

The question is simple.
Part1
Should I also be upgrading to SLES SP3 when I do the upgrade to OES 11 SP2?
Due to version confusion -- the answers given in this forum are not always Crystal Clear.
Part 2:
Is this spelled out somewhere in the (thousands of pages) of the documentation that I missed somewhere? (Perhaps I am having a "senior moment" and just can't see the words in one of the manuals.
Thanks for any help.
Cheers!

On 09/01/2014 11:16 AM, davewr50 wrote:
>
> The question is simple.
>
> _PART1_[/B]
> SHOULD I ALSO BE UPGRADING TO SLES SP3 WHEN I DO THE UPGRADE TO OES 11
> SP2?
>
> DUE TO VERSION CONFUSION -- THE ANSWERS GIVEN IN THIS FORUM ARE NOT
> ALWAYS CRYSTAL CLEAR.
Yes; OES versions are, by default (with very, very few exceptions) linked
directly to SLES versions, with OES versions being one SP behind SLES SPs.
Thus, OES 11 SP2 is linked to SLES 11 SP3.
> [B]_PART_2:_
> Is this spelled out somewhere in the (thousands of pages) of the
> documentation that I missed somewhere? (Perhaps I am having a "senior
> moment" and just can't see the words in one of the manuals.
https://www.novell.com/documentation...a/btmu44d.html
Top of the page under Meeting All Server Software and Hardware Requirements:
Code:
Server Software
As part of the OES 11 SP2 installation, you install SUSE Linux Enterprise
Server 11 SP3.
IMPORTANT:OES 11 SP2 services were developed and tested on a default and
fully-patched SLES 11 SP3 server base.
As you install OES 11 SP2, do not change any of the SLES 11 SP3 Base
Technologies package selections, such as Java support. Doing so can cause
various problems, such as the installation failing or one or more OES 11
SP2 services not working properly.
If you are installing on an existing SLES 11 SP3 server, be sure to verify
that all of the default SLES 11 SP3 components are installed before
attempting to install OES 11 SP2 services.
I would not define missing this as a senior moment; powerful products come
with lots of docs, and knowing exactly where to find one specific piece of
information is not always clear.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

OES2 sp2 AFP threads recommendation

I am in the process of migrating from NW65 to OES2 sp2 x86_64 running on VMware.
VM has 4GB mem and dual CPU.
Users will be mostly using NCP, but upto 100 Mac's simultaneously using AFP.
What is the recommended threads (minimum and maximum for AFP)?
There is nothing in the documentation about it.
Thanks,
Hein

On 30/06/2010 01:06, heinkonijn wrote:
> I am in the process of migrating from NW65 to OES2 sp2 x86_64 running on
> VMware.
> VM has 4GB mem and dual CPU.
>
> Users will be mostly using NCP, but upto 100 Mac's simultaneously using
> AFP.
> What is the recommended threads (minimum and maximum for AFP)?
> There is nothing in the documentation about it.
I don't think there are any recommendations for minimum and maximum so
it's a case of experimenting.
Personally I'd leave minimum threads at the default value of 3 but look
at increasing maximum threads from default value of 32 (since maximum
value is 32768).
HTH.
Simon
Novell Knowledge Partner (NKP)
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partners (TTP) group. See www.novell.com/ttp for more details.

Networking failing since migrating OES2 sp2 Linux VM

I have an OES2 sp2 Linux server on one ESXi server that needs to be rebuilt and I want to migrate it off to another ESXi server while I rebuild that server then move it back.
I tested this using VM ware convertor and it worked OK on a windows and standard suse10 sp3 server but I have since tried the OES2 Linux server and it fails to load the networking correctly.
For a start using VM Convertor it creates a new nic on the migrated server which needs the ip address info added which the windows and standard suse server took with no problems.
The OES2 server though even when I have added exactly the same network info onto the new card and deleted the old it doesnt work. I then went back in and checked the details were right which they were and re activated the nic again and the networking starting working.
I restarted the server to make sure all services started up correctly as rcndsd status showed nds as dead as well as various other services that had failed due to the networking being down but it failed to start the network again?
It does eventually start and its as if once edirectory fails to load, the networking then starts working? I can then rcnds restart and eventually it starts up OK but it then means I have to restart all the other services as well that are in a failed state due to lack of networking connectivity? If I reboot again it still fails to start edirectory and networking???
so.....
Does edir bind direct to a nic card, could that be the issue as now it has a new nic effectively? Any ideas would be appreciated?

Try this TID
Cloned machine does not boot up properly
Essentially, you need to clear the /etc/udev/rules.d/*-persistent_net.rules file, reboot, and let it repopulate based on the new machine. Hope that helps.

OES2 SP2 update channels?

I need to upgrade my OES2 SP1 servers to SP2, these servers has no internet connection they are only connected to a local ZLM server.
What channels should I mirror for completly move to SP2?
cheeeeeers,
AB

I've read the Cool-Solution Article: http://forums.novell.com/newsflash/w...-oes2-sp2.html
In my Case the OES-Servers are installed virtual on a Citrix-XEN-Server. (At the moment for testing porpouses).
Both Machines are ZLM enabled. The ZLM-Server is on 73IR1.
I have mirrored the SLES10SP3-Online, -Pool and -Update-Channel. Also the OESSP2-Online, -Pool and -Update-Channel. The two OES's i've assigned the Online and Update-Catalog for SLES10SP3 and OES2SP2 via ZLM.
After that i've done a "rug ref" and a "rug up" for one of the servers.
All seems to be done, but when look at the output of SPident the following is displayed on the updated OES:
Summary (using 1155 packages)
Product/ServicePack conflict match update (shipped)
UnitedLinux-1.0-x86_64 0 0% 0 0% 4 (884 0%)
SLES-8-x86_64 0 0% 0 0% 1 (90 0%)
SLES-8-Supplementary-x86_64 0 0% 0 0% 1 (403 0%)
UnitedLinux-1.0-x86_64-SP2 0 0% 0 0% 0 (97 0%)
UnitedLinux-1.0-x86_64-SP3 0 0% 0 0% 1 (221 0%)
UnitedLinux-1.0-x86_64-SP4 0 0% 0 0% 4 (316 0%)
SLES-9-x86_64 0 0% 0 0% 11 (1597 0%)
NLD-9-x86_64-SP1 0 0% 0 0% 11 (1648 0%)
SLES-9-x86_64-SP1 0 0% 0 0% 10 (524 0%)
SLES-9-x86_64-SP2 0 0% 0 0% 11 (700 0%)
SLES-9-x86_64-SP3 0 0% 0 0% 11 (833 0%)
SLES-10-x86_64 0 0% 306 26.5% 31 (2100 14.6%)
SLE-10-x86_64 0 0% 306 26.5% 34 (2754 11.1%)
SLED-10-x86_64 0 0% 274 23.7% 22 (2030 13.5%)
SLE-10-x86_64-SP1 0 0% 404 35.0% 34 (2938 13.8%)
SLE-10-x86_64-SP2 0 0% 537 46.5% 37 (3111 17.3%)
SLE-10-x86_64-SP3 5 0.2% 900 77.9% 40 (3275 27.5%)
Unknown 253 21.9%
CONCLUSION: System is NOT up-to-date!
found SLE-10-x86_64-SP2 + "online updates"
expected SLE-10-x86_64-SP3
On the "not touched" OES2SP1, SPident gave me:
Summary (using 1125 packages)
Product/ServicePack conflict match update (shipped)
SLE-10-x86_64 0 0% 320 28.4% 243 (2754 11.6%)
SLE-10-x86_64-SP1 0 0% 438 38.9% 254 (2938 14.9%)
SLE-10-x86_64-SP2 0 0% 657 58.4% 255 (2337 28.1%)
Unknown 468 41.6%
CONCLUSION: System is up-to-date!
found SLE-10-x86_64-SP2 + "online updates"
After a reboot the machine came up without no problems. eDir works. A query in the rpm-Database shows me the new packages.
Any idea what to to do? Or is there a better way to update an OES2SP1 to SP2?
Regards
Edmund

Virtualizing OES2 SP2 on ESXi 4.1

I have physical OES2 SP2 server that I want to virtualize on VMware ESXi 4.1 but when I try to import it using converter I'm getting error "Unable to detect disks or volumes on the source machine..."
OES2 server has one logical volume (harware RAID5) controlled by evms
Enyone had this issue before?
Kamenko

Originally Posted by ucsusa
I have physical OES2 SP2 server that I want to virtualize on VMware ESXi 4.1 but when I try to import it using converter I'm getting error "Unable to detect disks or volumes on the source machine..."
OES2 server has one logical volume (harware RAID5) controlled by evms
Enyone had this issue before?
Kamenko
Hi Kamenko,
Unless it has changed, converter does not support OES2, more importantly also not EVMS -only SLES with native Linux/LVM formated volumes AFAIK.
You might want to consider using the miggui's transfer ID option.
-Willem

Migrating from NW 6.5 SP8 to OES2 SP2

I'm looking to move from NW 6.5 sp8 (no clustering) to Oes2 sp2 (clustering). The main goal in this migration is to no effect on the user experience. The big issue is server name, I want to keep the existing server names. A lot of users have shortcuts that use UNC (\\servername\vol\filename). I looked at using an alias in DNS but the shortcuts still won't work.
So I'm looking at doing a migration with clustering all at one time. Of course with a clustering resource I can use the existing server name. The issue that comes up is when I'm doing the cut over, how will clustering react to creating that cluster resource with the same server name that already has a server object with that name. I brought this up to Xang(spelling) at Brainshare this year. I wanted to see if anyone has gone through this. I have setup a test network to go through the scenario and see what happens. Does anyone have any ideas on this scenario or been through this? Thanks in advance.

Originally Posted by timothyaw
I'm looking to move from NW 6.5 sp8 (no clustering) to Oes2 sp2 (clustering). The main goal in this migration is to no effect on the user experience. The big issue is server name, I want to keep the existing server names. A lot of users have shortcuts that use UNC (\\servername\vol\filename). I looked at using an alias in DNS but the shortcuts still won't work.
So I'm looking at doing a migration with clustering all at one time. Of course with a clustering resource I can use the existing server name. The issue that comes up is when I'm doing the cut over, how will clustering react to creating that cluster resource with the same server name that already has a server object with that name. I brought this up to Xang(spelling) at Brainshare this year. I wanted to see if anyone has gone through this. I have setup a test network to go through the scenario and see what happens. Does anyone have any ideas on this scenario or been through this? Thanks in advance.
From what I'm reading clustering is more a means to a migration question than wanting it as solution...?
1) You are going to be running in a virtual environment? (can have implications for clustering)
2) From what I read, clustering is not something you want for what it offers in HA terms... but more as a means to reach your goal of keeping the old server name?
Have you had a look at the Transfer ID option? It sounds like a good option in your case.
Another possibility that also keeps downtime to a minimum (have used this many times to split up migration tasks) - quick overview:
1) Setup or use an existing OES2 server to host the new data volumes. This server should be using storage that can easily be swapped over to the new OES2 server that will be replacing the NetWare server.
2) Create the NSS pools/volumes with the correct names, sizes etc
3) Use the miggui (or SCMT) tool to do the file migration. This will sync keeping all file attributes and metadata - this fase can be done a day or two before breaking down (removing from tree) your NetWare server.
4) Setup a new SLES 10 server with the OES2 media added in (but no products selected or configured!) so it's ready to be installed into the tree. At this time it has a temporary name and ip...
5) Decommission the NSS volumes from the temporary assigned server (offline NSS pools and remove the eDirectory pool and volume objects) and disconnect the disks from the server (so they are ready to be connected to the new server)
6) At the planned time remove the NetWare server from the tree using nwconfig, remove leftover objects for that server from the eDirectory.. then give it a new ip, change the name in the autoexec and reboot.
After reboot you can either install the server back into eDir in the existing tree or a temporary one (I prefer the last to keep it fully separate)
7) After having removed and renamed the NetWare server, check eDir health, reconfigure the SLES server with the correct name and ip and install & configure eDirectory using YaST's OES install and configure (also add nss).
8) When this is done and running ok, bring down the new server, connect the data disks to it and boot it back up.
9) Commission the disks to the server using nssmu <ALT><F4> on pools and volumes
10) Run a tool to sync changes from the old NetWare server to the new OES2 server (mirror sync, so the new data volume is identical to the old one).
I still use the old robocopy script to do this mirror sync as it works well.
DO TAKE CARE : exclude syncing the ._NETWARE folder on the root of each NCP volume... as you will otherwise wipe the trustee xml files.
To do a last check comparison, tools like beyond compare/Total commander can do a good job here.
Post jobs could include re-linking user home directories and default server assignments sing the HOMES tool (HBware).
If the NetWare server was also doing other tasks... you can choose to reconfigure those takes before doing the steps mentioned above, or reconfigure after. It's dependant on what you have running on the original server.
Cheers,
Willem

Want to do a non-destructive restore of XP Professional SP3 (Was SP2)

System: Presario SR1817cl, as originally configured from factory. XP Professional 32-bit SP3 (was SP2) 512 MB RAM, onboard card reader, ATI onboard video. AMD processor. IE8 installed.
System was badly infected with 31 malware, (trojans, exploits, and a rogue a/v program that did not completely install).
Out-of-date Adobe Flash and Java present on system.
System is infection-free. Used OTL, Combofix under the instructions and guidance of essexboy over at the Avast! user forums. Also was able to install and run w/ latest definitions for the following programs: Avast! Free A/V, Malwarebytes, SUPERAntispyware. Avast! found and removed the vast majority of malicious files and placed them in quarantine. All such files found were put in quarantine by their respective programs when run.
Now looking at System Restore as a service is enabled (automatic) but does not run, cannot find it either in My Computer, or in Start>All Programs>Accessories>System Tools. Cannot manually start it either.
When running sr.inf in Windows\inf folder (hidden) by right-clicking install, file begins to install, but points towards a missing folder (entire folder is gone) in Windows\ServicePackFiles\i386. Size of i386 folder should be at least 400 MB and contain at least 2,200 files. Without this folder, unable to complete install of System Restore. There is nothing there.
Option 1: Copy and paste the i386 folder from another XP Pro system to where it belongs on the now clean system.
Option 2: Perform a non-destructive re-install of Windows where all personal data is left intact or able to use the native Windows File Transfer Wizard to capture and back up such data.
Use and access the OEM install partition on the drive as a restore disc was not supplied to owner when this system was purchased.
Particularly need to know how to access the hidden OEM partition if copy and paste of i386 folder does not work, and no recovery disc is available. Running sfc \scannow cmd will not work w/o disc, either. How to point scannow to OEM partition?
Basically, this system is now in the repair phase, and I need to ensure all security settings are back to default and running. Option 2 is the logical way to restore the system back to default settings; however, personal data such as pictures, music, etc., is in excess of 25 GB in size.
Help here will be appreciated.
If option 2 is the only viable option, do I need to uninstall SP3 from system before running this? As this system's regional setting is in Spanish, will this setting change as well if a non-destructive restore is done?
mchainmchainmc
XP Home Edition SP3 P4 2.8 2 GB RAM

Assuming you have a standard setup, you need to restore the iTunes folder from backup into the Music folder.
You need to have iTunes closed duing these steps.
As you have something in your library as already, drag the entire current iTunes folder to the desktop first. Then re-add the audiobook back to iTunes after you have your old iTunes library working. It should be in the iTunes Music folder in the iTunes folder your dragged out.
One catch when restoring folders from another PC to a Vista computer is that Vista is fussy about permissions and may not regard you as the owner of the iTunes folder. You need to check the permissions and make sure your account has full control after you have restored the iTunes folder from backup.

MyBook World Edition - Time Machine - AFP Issue

So after 60 mins on the phone with the ppl at WD, it was determined that i most likely have any issue with Time Machine accessing the wd_backup partition of my mybookworld NAS drive. Simply put - I can access the drive via SMB ('cept for the backup partition - which is what i want anyway) but TM (nor the finder) wont access the backup partition at all.
WD says its an AFP issue. Ive spent all day searching google and forums and I cant find a good answer. Can anyone help?
Thanks

Sorry I'm not adding anything positive but I too am having problems with my MBW NAS drive. Every time I try to connect with the "Public" drive, I get the "The operation cannot be completed because the original file for "Public" cannot be found." I connect through SMB as well but it is annoying. I never been able to connect to MBW-Backup. Again, sorry to piggyback but just wanted to let you know you are not alone in your search.

AFP issues with 10.4.6

Hi,
I have network of 3 Macs running 10.4.6. Two are wired and the other is my laptop and it is wireless. When I try to connect with AFP to any maching (wired to wired, wired to wireless, or wireless to wired) I get the following error:
"Connection Failure
The server may not exist or it is not operational at this time. Check the server name or IP address and try again."
I get the same message when I try to connect by IP address or name.
I have IPv6 and Appletalk turned off on all machines. All machines also have static IPs and DNS info entered manually. If I scan each machine with NMAP port 548 is open and I can telnet to it. I also can see the server when I browse the network for AFP servers.
Any ideas?
Thanks in advance,
Andy
Mac OS X (10.4.6)

Hmm thinking twice about it, sounds like MacOS-BSD idiosyncrasy...
Every time we update MacOS X the I/O and network catalog is being reset, returning most of the settings to default values (at least when dealing with default (not customized) installations)...
Your issue regarding TCP sendspace sounds like a good feedback to Apple.
I'll fire an email to the developers...
btw: mark your question as answered, it's the most interesting AFP issue I've read so far
Macs running 9.x, Macs running 10.4.x, SGI workstations running Irix 6.5.x

Install ZSM7SP1IR4_HP1.zip on OES2 SP2

Hello,
I want to install this patch manually on OES2 Sp2 Linux Server, because ZFS will not start on OES 2 Server. Does anyone know, which file have to copy to which directory?
regards

Adeckert,
the files are all shown in the dirstruct\raw_files directory, it's
quite straighforward...
Shaun Pond

Trustees not syncing to OES2 SP2 64-bit NSS

At first I thought this was a fluke, but this is the third volume now that I've migrated from NetWare 6.5.8 NSS to OES2 SP2 Linux 64-bit in an NCS mixed cluster
The NSS volume mounts fine, but the trustees are not being synced/converted
I thought this was supposed to happen automatically?
Apparently not
I can manually sync them and they'll work fine
Is there supposed to be some command in the load/unload scripts that has to be there to do this?
I looked at the cluster convert preview and I don't see any "sync" operation and I don't see anything on the /var/log/messages either.

Okay we THINK we got it working.
It seems to only work if you OFFLINE the resource on NetWare and then ONLINE it onto OES2
vs
MIGRATING the resource from NetWare to OES2
don't ask me why, but it only seems to work that way
I've got log files from the "migration" method that show it never kicks off the trustee sync
but if you offline/online then it DOES kick off the trustee sync (albeit a few minutes AFTER the resource is onlined so it's a little slower and not as much feedback as if you run the sync manually).

AFP Issues - SLES 10 SP3 / OES2 SP2

Similar Messages

Maybe you are looking for