Transfer Trustees from Netware to OES2 SP3

Hi everbody,
with the last metamig, I saw, that saved data from trustee.nlm should be restored.
I saved on the original Netware Server with trustee save /R daten: daten:daten.txt.
But I was not able to restore to my OES 2 SP3, I got a lot of error, ie. invalid token.
The Volume Name is the same as on Netware. All data have the same path.
Can anybody tell me the correct syntax how to restore the trustees to oes?
Thanks for helping,
Regards from Austria,
Reinhold

Originally Posted by rsteini
Hi everbody,
with the last metamig, I saw, that saved data from trustee.nlm should be restored.
I saved on the original Netware Server with trustee save /R daten: daten:daten.txt.
But I was not able to restore to my OES 2 SP3, I got a lot of error, ie. invalid token.
The Volume Name is the same as on Netware. All data have the same path.
Can anybody tell me the correct syntax how to restore the trustees to oes?
Thanks for helping,
Regards from Austria,
Reinhold
I don't believe (I could be wrong) that you can take the trustee.nlm and save the output in a format that OES Linux will understand (the OES LInux uses a .xml format which I think is different)
You could manually read through the file (that NetWare generates) and figure out if you wanted to manually reassign them
Or you could use the miggui (migration utility) on OES Linux to migrate the data (and trustees) from NetWare.

Similar Messages

Netware 6.5 SP8 to OES2 SP3 Migration Error with migfiles

Hi,
at first. We would like to abuse the migfiles tool to mirror data from Netware to OES2 SP3 with trustees !! Do you know a better tool than migfiles, please let me know. Its very important for me to use a CLI Command tool like migfiles, because it should run automatically.
We want to mirror data from a Netware 6.5 SP8 NSS Volume to a OES2 SP3 NSS Volume with trustess. The first migration with following line works without any error:
migfiles -s IPAddress -V Daten -x /media/nss/D4/Test3/ -i
From this point we need the -sync parameter to keep the data current.
I use this:
migfiles -s IPAddress -V Daten -x /media/nss/D4/Test3/ -i --sync "22-07-2011 16:26"
But then i became this errors:
Error: nbackup: Failed to restore: DATEN:VOLDATA.TDF
Error: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
Error: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/
Error: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
Error: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/NWTAPE.CDM
Fatal: Failed to restore data. Could not find destination path. If the destination path is a cluster resource, then check whether the resource is moved.
Fatal: nbackup: Received error: 0xfffdffe5 ((libtsafs.so 6.50.0 282) The data set handle is invalid.) from NWSMTSOpenDataSetForRestore
When the Sync job is finished, no file which was changed on the Source was migrated to the destination.
For your information. With the Novell Migration Tools (GUI) i have the same error. But with the Windows version "Novell Server Consolidation and Migration Toolkit" it works without any errors. But its a GUI tool without the possibility to run it automatically.
Any ideas
Thanks Andreas

Hi,
thank you for your reply. This is the log:
D, [01-08-2011 14:33:07#4872] DEBUG -- migfiles: migfiles command started at 01-08-11 14:33:07
D, [01-08-2011 14:33:07#4872] DEBUG -- migfiles: migfiles command executed as: /opt/novell/migration/sbin/migfiles -s xxx.xxx.xxx.103 -V Daten -x /media/nss/D4/Test3/ -i --sync 22-07-2011 16:26 --debug
D, [01-08-2011 14:33:07#4872] DEBUG -- migfiles: Calling function getCredentialDetails
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: Successfully taken credential Details of source and destination server from user
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: nbackup command executed as LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -U "admin.havas" -R xxx.xxx.xxx.103 --list-tsa-version
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: Major version of source tsafs is 3
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: Minor version of source tsafs is 1
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: ncpshell command executed as /opt/novell/ncpserv/sbin/ncpshell --ip=xxx.xxx.xxx.103 --u="admin.havas" --vinfo --parm1="Daten"
I, [01-08-2011 14:33:22#4872] INFO -- migfiles: Given destination path is NSS
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Source path is Daten:
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Destination path is /media/nss/D4/Test3/
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Successfully returned from function verifyAndFixSrcPath
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Destination volume type: NSS
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Calling function get_nss_vol_and_mnt_point_from_path
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Calling function is_compression_enabled
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Started on: "1-8-2011 14:33:22"
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: smstool cmd = LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/smstool --srcuser ".admin.havas" --destuser "root" -R xxx.xxx.xxx.103 --sync-time "22-07-2011 16:26" --output-file /tmp/smstoolOutFile.4872 --finddiff "Daten: /media/nss/D4/Test3/" 2>&1
I, [01-08-2011 14:33:23#4872] INFO -- migfiles: Generating list of files and folders to be synced
D, [01-08-2011 14:33:23#4872] DEBUG -- migfiles: Executing nbackup command from syncfiles: LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -cF --disable-caching -U ".admin.havas" --expand-compressed-data -R xxx.xxx.xxx.103 -T /tmp/smstoolOutFile.4872 | LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -xvF -U "root" -r "Daten: /media/nss/D4/Test3/"
D, [01-08-2011 14:33:23#4872] DEBUG -- migfiles: nbackup cmd = LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -cF --disable-caching -U ".admin.havas" --expand-compressed-data -R xxx.xxx.xxx.103 -T /tmp/smstoolOutFile.4872 | LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -xvF -U "root" -r "Daten: /media/nss/D4/Test3/"
D, [01-08-2011 14:33:23#4872] DEBUG -- migfiles: Calling function doCmd
D, [01-08-2011 14:33:25#4872] DEBUG -- migfiles: Checkpoined at
D, [01-08-2011 14:33:25#4872] DEBUG -- migfiles: Checkpoined pair 0
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Failed to restore: DATEN:VOLDATA.TDF
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/NWTAPE.CDM
F, [01-08-2011 14:33:25#4872] FATAL -- migfiles: Failed to restore data. Could not find destination path. If the destination path is a cluster resource, then check whether the resource is moved.
F, [01-08-2011 14:33:25#4872] FATAL -- migfiles: nbackup: Received error: 0xfffdffe5 ((libtsafs.so 6.50.0 282) The data set handle is invalid.) from NWSMTSOpenDataSetForRestore
Thank you
Andreas

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).

Moved PO from NW to OES2 and now email is not flowing

We migrated a GW 8.02 Sp2 Post Office and Secondary domain from Netware to OES2 10 Sp3. Our GWIA and Webaccess are located another Netware 6.5 sp8 server in the same network. I updated all of the GW system with the latest GW 8.02 HP3 update.
None of the users in the OES2 post office can send or receive email to the outside. They can send to all internal GW users. They can login to Webaccess which is on the same MTA as GWIA
I have made sure that the GWIA has the correct PO info and that the POA for OES2 server has the correct paths and IP address with Bind Exclusive set.
Any help would be appreciated.
Thanks,

In article <[email protected]>, Pmacjr wrote:
> I have made sure that the GWIA has the correct PO info and that the POA
> for OES2 server has the correct paths and IP address with Bind Exclusive
> set.
>
Perhaps try without the Bind Exclusive, I have had that be a problem
once.
This sounds like drawing out a map of all the components might be of use,
and then check all the agents wpcsin/out and MSLOCAL to see where they are
queuing up. That should help you zero in to where there is a broken link
you've missed so far.
I've often white boarded all the relevant agents when troubleshooting such
an issue with a team.
Another trick I do is create a simple web page with all the agents web
interfaces listed so I can quickly go through them all.
http://www.konecnyad.ca/andyk/adminagents.htm
Andy Konecny
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

Netware to OES2 ID migration WITHOUT using MIGGUI?

Everyone;
I have been able to use the migfiles command, and the iprintmig command to successfully migration files and printers
from a Netware server to an OES2 server. For me, this is just so much faster and easier then trying to use the miggui
wrapper.
My issue is I want to complete the ID migration from Netware to OES2, without having to use the miggui wrapper. (it's a
long story, but I can't install or load X-Windows on the OES2 server).
Has anyone figured out the necessary scripts/commands/syntax to migrate from Netware to OES2, without having to use the
miggui wrapper?
Thanks
Michael

Duh......when all else fails, RTFM.... :-)
Thanks for pointing this out.
Michael
On Fri, 20 Aug 2010 14:06:03 GMT, kjhurni <[email protected]> wrote:
>
>Yes, the steps are listed here:
>
>'Novell Documentation'
>(http://www.novell.com/documentation/...a/bgc4dpv.html)

Migrate NSS volume data from OES2-SP1 to OES2-SP3 server fails

Hello forums
I have a senario where we want to use miggui to migrate all files/folder
and trustees, to e new server using miggui.
When we try to migrate from the existing "VOL" from the old OES2-SP1
server, we get an error on the miggui log running on the new OES2-SP3
server like this:
ERROR - FILESYSTEM:migfiles:Error: nbackup: (libtsafs.so 6.50.0 269) No
data sets can be found or the resource is not available.
In the miggui the Volumes can be dragged and dropped fine.
I do not by not know the old OES2-SP1's patch level, nor the OES2-SP3's
at this time.
Any ideas of what causes this error?
- Michael

Have you looked at this?
Troubleshooting data migration issues with miggui
I'd check and maybe see if the sms/tsa code is working properly on the OES2 SP1 server.

Mac os 10.6.8 cannot login to OES2 sp3

i'm having issues logging into a clean install of OES2 SP3 Linux SLES10 sp4 server here's my log file:
Feb 20 03:23:31 Server-1 afptcpd[4407]: Created session: 10 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:31 Server-1 afptcpd[4407]: Closing session: 10 <0x82afc38>, Socket: 60, Pending requests: 0
Feb 20 03:23:31 Server-1 afptcpd[4407]: Created session: 11 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:31 Server-1 afptcpd[4407]: Closing session: 11 <0x82afc38>, Socket: 60, Pending requests: 0
Feb 20 03:23:41 Server-1 afptcpd[4407]: Created session: 12 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:41 Server-1 afptcpd[4407]: [debug] LDAP user name: cn=horchemg,ou=springfield,o=missouri
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - INFO:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - WEBBACKUP:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - HORCHEMG:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - INFO:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - WEBBACKUP:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - HORCHEMG:\
Feb 20 03:23:42 Server-1 afptcpd[4407]: Closing session: 12 <0x82afc38>, Socket: 60, Pending requests: 0

On 21/02/2012 23:16, ataubman wrote:
> Also, has OES been patched up? You need at least the November 2011
> patches to get AFP to work with 10.6.8 , IIRC.
I think you're getting your Mac OS X versions mixed up as Snow Leopard
(10.6.x) was supported from the beginning with AFP in OES2 SP2 and
later. See
http://www.novell.com/products/opene...owleopard.html
It's OS X Lion (10.7.x) that requires the November 2011 (and earlier)
patches for AFP in OES2 SP3 but it is supported from beginning with OES11.
HTH.
Simon
Novell/SUSE/NetIQ Knowledge Partner
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.

SLES10 SP4/OES2 SP3 32 bit Clean Install - Basic Questions

Hi everyone.
I am now an expert in installing the above software and ending up with a server which does not work as we require. Must be something I am doing wrong. Hope someone can spot it.
Have installed and supported Netware servers for 25 years without major problems. Decided now to move to SLES because Novell say we should and we need Groupwise 12 to replace GroupWise 8.
The operational environment we are targeting is an 80 user edirectory/NDS based single tree, single context containing two Netware 6.5 SP8 HP Proliant servers running uncomplicated file and print services , NSS volumes, Groupwise 8, DHCP, ifolder, Quickfinder and the like, spread across the two servers. It all works a treat. Client PCs are are all XP Pro with Novell client software.
The idea would be to replace one of the two Netware servers first with a SLES/OES server and then the second Netware server with a second SLES/OES server and move GroupWise functionality to one of the SLES/OES servers. Ideally users would continue to log on using their eDirectory accounts without noticing anything was going on in the background.
The test environment we have set up is a 5 user NDS/eDirectory single tree, single context already containing a single Netware 6.5 SP8 Proliant server running file and print, NSS volumes etc and Groupwise 8. Into this tree we are trying to install a 32 bit server with a empty 36 GB SCSI disc running SLES 10 SP4 with OES2 DP3 as an add in, with NSS data volumes.
Because it only takes a few hours to do we have repeatedly run the SLES 10/OES2 install (probably about 9 times!) with minor variations to see whether we can end up with a properly configured SLES/OES server but there is always one problem or another.
The major problem we have is how to configure NSS data volumes on the SLES server and how to allow users to be validated against their eDirectory entries and knowing whether the test server is 'good to go'.
The process we followed for each test install, after checking edirectory was clean and removing any entries placed in the tree by earlier attempts to install the SLES server in the same tree were:
1. Boot the SLES 10 SP4 32 DVD (downloaded ISO and burnt DVD) and selected Installation.
2. Followed the prompts on time zone and language etc and selected i386 OES CD (also downloaded ISO and burnt) as the Software Add-In.
3. Loaded SLES DVD and OES CD as and when requested
4. At the Partitioning stage we selected the EVMS proposal, and at the Software selection stage selected the base software, file server Role, Documentation, DHCP, eDirectory, iFolder, iPrint, Quickfinder, NSS and LDAP.
5. Miscellaneous errors would appear or not appear during the eDirectory stage (eg LUM error, or iFolder error) but the eDirectory stage would still seem to complete OK and get ticked.
6. The system would then reboot and appear to come up OK.
HOWEVER, we are not convinced we have created a fully working reliable server.
and
SPECIFICALLY we are unable to create NSS volumes and we cannot logon users via their eDirectory accounts.
NSSMU shows a single device sda (33.92 Gb) and three partitions sda1 (70Mb), sda2 (31.91GB), and sda3 (1.94GB). sda2 seems to contain all the 'spare' space on the disk (type Linux LVM) but says there is no spare space to create our NSS partitions.
iManager cannot see any devices to configure NSS data volumes on the SLES server but it connects OK
NSSCON status seems to show NSS to be running
EVMSGUI shows /dev/evms/lvm2/system/ro at 10 Gb, /dev/evms/lvm2/system/sw at 2GB and /dev/evms/sda1 at 70 Mb
So my questions are:
Does the above look right?
Why cannot we get at the spare disk space to set up NSS volumes? Did the EVMS proposal grab it all and if so how do we get it back?
Did not selecting the EVMS partitioning proposal do everything needed to run NSS?
[There seems to be some suggestion in the several hundred pages of SLES, OES and NSS Guides, Installation manuals, Configuration manuals etc that we have studied over several days, that we now have to edit a fstab file to make it work properly (Really? in this day and age where clicking on Setup.Exe will configure a fully working Windows server) Is that so? Is there anything else we need to do?]
How do we get the users to access their NDS accounts to log into SLES and Netware?
How do we know the server is OK for operaational use and 'works' ?
HELP!!!
ADB

alandbond wrote:
> I
> have already trawled the self help Forums believing that before SLES
> 11 came along everyone must have been setting up NSS volumes on SLES
> 10/OES2 as a matter of course as they moved from Netware and so me
> trying to do it now should not be akin to rocket science.
You are partially correct. Admins who used NSS on NetWare likely did
install NSS on OES Linux but I suspect they used a separate drive for
NSS either by installing an additional drive, by carving out a chunk of
space on their RAID array and assigning it to a separate LUN, or by
running OES in a VM where storage space on a single disk/array can
appear as separate drives.
> If Novell say in that guide as they do
> (just as do you and ab and Simon in responses to my post) that the
> IDEAL way to include NSS is to have a separate disk for Suse and NSS
> volumes, BUT as long as you use EVMS to manage the volumes it IS
> SUPPORTED, then I consider it should be possible without grief to do
> this and not considered as me putting round pegs in square holes.
Semantics!
IDEAL = Recommended; EVMS != IDEAL; EVMS != Recommended;
IMO, Novell recognised that they had to provide a way for customers to
install NSS on a system that only had a single disk and provided this
procedure as a workaround. By the way, they also support 2-node
clusters but they aren't recommended either. I have also seen cases
where a supported configuration was deemed no longer to be supported as
NTS became aware of additional complications.
My point (and Simon's and ab/Aaron's) is this: Just because it is
supported doesn't mean you should do it. If we can agree on this point,
I'll try to help you to get it working. The last thing I want to do is
give others the impression that by helping you find a solution we think
this is a good idea!!!
> This latest release of software even goes as far as including an EVMS
> Partitioning proposal which can be selected (as I did) within the
> clean install process.
>
> This is what it says:
Okay! I'm only looking at the information you provided. Let's analyse
it!
>
> A.2.1 Understanding the EVMSBased Partitioning Scheme
> Using EVMS to manage the system device allows you to later add NSS
> pools and volumes
Yes, NSS requires the volume manager to be EVMS and not LVM!
> on any *unpartitioned* free space on it.
But you have not left *any* unpartitioned free space!
> You must modify the partitioning scheme to use EVMS during the
> install. It is not possible to change the volume manager for the
> system device after the install.
True.
> Beginning in OES 2 SP3, the Partitioner in the YaST Install offers the
> Create EVMS Based Proposal option to automatically create an EVMS
> solution for the system device.
> For unpartitioned devices over 20 GB in size,
This is what you have...
> this option creates a boot partition
> and a container for the swap and / (root) volumes
> in up to the first 20 GB,
> and leaves the remainder of the space on the device
> as unpartitioned free space.
But it didn't (or you didn't)!
> Table A-1 shows the default proposed setup
> for a machine with 768 MB RAM.
> The default swap size is 1 GB or larger,
> depending on the size of the RAM on your machine.
> The remainder of the device is left as unpartitioned free space.
Let's look at the default proposal. This is *not* what you have.
> Table A-1 Default EVMS Proposal for Devices over 20 GB in Size
>
> Device Size Type Mount Point
> /dev/sda1 70.5 MB Ext2 /boot
> /dev/sda2 14.9 GB Linux LVM
> /dev/evms/lvm2/system 14.9 GB EVMS lvm2/system
> /dev/evms/lvm2/system/root 10.0 GB EVMS /
> /dev/evms/lvm2/system/swap 1.1 GB EVMS swap
A single (SATA/SAS/SCSI) drive will be known as sda (/dev/sda).
/dev/sda1 is the first partition. In the example and in your
configuration this is the /boot partition. In both cases it is 70.5 MB.
/dev/sda2 is the second partition. The partition uses LVM so logical
volumes of various sizes can be created within the partition. The total
size of all logical volumes cannot be larger than the size of the
partition.
In the above example:
/root is 10.0 GB and swap is 1.1 GB. This leaves: 14.9 - (10.0 + 1.1) =
3.8 GB of additional space within /sda2 which can be used to create
additional logical volumes. Furthermore sda1 + sda2 use only ~ 15 GB.
Only 15 GB of the disk has been allocated. The remainder of the disk is
*unallocated* and *unpartitioned*. Presumably, it was left that way so
that the space could be used for NSS.
In your case: sda2 is 31.91 GB
This does not follow the Default EVMS Proposal for Devices over 20 GB
in Size. Either YaST did not allocate space according to the default
proposal or you changed it. Either way, sda2 (+sda3) consume *all* of
the available disk space. It is no wonder that there is no space
available for NSS!
> What do you reckon???
I reckon that something went wrong along the way. If you did not
specifically change the default allocation yourself, then consider this
one example of kinds the things that can happen when one tries to
exploit seldom used, but supported, features!
It looks like it is time for yet another installation. This time, make
sure you leave enough unpartitioned space on the drive for NSS and let
me know how you make out.
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Migrating from Netware to Linux - faster "sync" ?

Hey all,
Planning on doing a TransferID migration from netware 6.5 to linux this weekend and have done some trial data copies.. Main copy is already done, but the "sync" is still taking a large number of hours that I need to try and fit into a smaller window. Any tips on getting sync to go faster? I'm currently using the miggui but wondering if you do the commands manually, leaving things out like displaying progress bar, etc.. if it'll get to it quicker.

Originally Posted by joebrug
Hey all,
Planning on doing a TransferID migration from netware 6.5 to linux this weekend and have done some trial data copies.. Main copy is already done, but the "sync" is still taking a large number of hours that I need to try and fit into a smaller window. Any tips on getting sync to go faster? I'm currently using the miggui but wondering if you do the commands manually, leaving things out like displaying progress bar, etc.. if it'll get to it quicker.
So, we have 6-year old HP DL-385 (no G, that's old they are) that are slower than you know what.
We're migrating to HP DL385 G6 or G7, but we're using VMware ESXi, so the target OES11 server is a Guest VM.
Both servers are on a gigabit switch.
We average approx. 15-20 GB/hour (it's not the AMOUNT of data, it's how many small files that affects things).
We're able to get the sync to fit in a small window (even our large ones, maybe 2-4 hours).
Is that not fast enough (although you may have LOTS more small files that change daily).
Basically we cart the server down, run the sync during the day until it finishes. Obviously it skips things that were in use. Then we kick everyone off the server at 3:00 and start the sync.
Since you're on NetWare to OES, I would NOT recommend rsync. The rsync on NetWare is very touchy/finicky and I don't think you can migrate trustees either.
From OES2 to OES11, you could use rsync, although I'm having mixed results with the trustees at the moment.
One thing we DO have is a "static" set of read-only data on the server, that we do NOT migrate over. We have a central office server that contains the "master" data and the clients run rsync to pull the data. So we don't even back it up either (other than the main office).
I can't remember the EXACT numbers we got when we did NetWare to OES2, but I still think we were averaging somewhere around 12-17GB/hour depending on. The key point was to make sure you were gigabit and didn't have a mis-match because someone in your datacom unit set the **** switch to 100-full or something other than auto-auto.
Oh, and if you have disk quotas, make sure that you either clear them or keep compression enabled. THAT will slow things down because if it tries to copy something, and there's not enough space, it'll retry like X times and then continue on and you find out like 10 hours later it was slow because you didn't have enough directory quota space.

OES2 SP3 DNS/DHCP Console

Just a quick note that currently, the latest DNS/DHCP Console isn't
available for download on Novell's site. You have to get it off of your
OES2 SP3 server instead.
http://servername/welcome/client-software.html
Then you can follow TID 7006450 to configure it so you can view leases.
-Mike

On 25/02/2011 21:35, TitanXV wrote:
> It will only be available if the novell-dnsdhcp-javaconsole rpm is
> installed, and you can also grab it from the directory at
> /srv/www/novell/clients/dnsdhcp
If you do not have the novell-dnsdhcp-javaconsole RPM installed but do
have access to the OES2 SP3 media (and don't want to install DNS/DHCP on
a server just to get the latest JavaConsole) then on a Linux box you can
extract the latest code via:
rpm2cpio /path/to/novell-dnsdhcp-javaconsole-2.0.1-0.33.<arch>.rpm |
cpio -idmv
(where <arch> is i586 or x86_64 depending on 32- or 64-bit - note same
files included in both)
You can then take the relevant DNSDHCP_SA.zip file and use it to install
the JavaConsole on your admin workstation(s).
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 Partner (TTP) program. See novell.com/ttp for more details.

Migration from Netware 6.x NSS to Solaris 10 ZFS

Hi,
I am looking at Solaris and ZFS as being the possible future of our file store for users.
We have around 3TB (40million files) of data to transfer to ZFS from Netware 6.5 NSS volumes.
What is the best way to do this?
I have tried running utilities like richcopy (son of robocopy) , teracopy, fastcopy from a Windows client mapped to the Netware server via NCP and the Solaris server via Samba.
In all tests the copy very quickly failed, rendering the Solaris server unusable. I imagine this has to do with the utilities expecting a destination NTFS filesystem, and ZFS combined with Samba does not fit the bill.
I have tried running the old rsync client from Netware, but this does not seem to talk to Solaris rsyncd.
As well as NCP, Netware has the ability to export its NSS volumes as a CIFS share.
I have tried mounting a CIFS share of the Netware volume on Solaris...but Solaris as far as I am aware does not support mount -t smbfs as this is Linux only. You can mount smb:// from the Gui (Nautilus), but this does not help a great deal. I was hoping to run maybe Midnight Commander, but I presume that I would need a valid smb share to the Netware volume from the command line?
I really want to avoid the idea of staging on say NTFS first, then from NTFS to ZFS. A two part copy would take forever. It needs to be direct.
BTW..I am not bothered about ACL's or quota. These can be backed up from Netware and reapplied with ZFS/chown/chmod commands.
A wild creative though did occur to me as follows -
Opensolaris, unlike Solaris, has its CIFS kernel addition, and hence smb mounts from the command line (I presume), but I am not happy running opensolaris in production.So maybe I could mount the Netware NSS volume as a CIFS share on opensolaris (as a staging server), copy all the data to a ZFS pool locally, and the do a send receive to Solaris 10.......
Maybe not...
I suppose there is FTP, if I can get it to work on Netware.
I really need a utility with full error checking, and that can be left unattended.
Any ideas?

Bu unusable I mean that the mapped ZFS Samba drive to the windows workstation died and was inaccessible.
Logging onto the solaris box after this from the console was almost impossible. There was a massive delay. When I did log in there appeared to be no network at all. There were no errors in the smbd log file. I need to look at other logs to find out what is going on. Looking at the ZFS filesystem some files had copied over before it died.
After rebooting the Solaris box I then tried dragging and dropping the same files to the ZFS filesystem with the native windows expolrer interface on the windows client. This worked, as in the Solaris box did not die and the files were copying happily (until I manually stopped it). As we all know Windows explorer is not a safe unattended way to copy large amounts of files.
This tells me that the copy utilities on Windows are the problem, not native windows copy/paste.

How To Transfer Files From Windows XP?

I want to transfer some pictures and documents from my Windows XP SP3 desktop to my Mac Book.
I have a memory stick (formated in FAT I think) and my CD burning software on the XP desktop can burn CDs in ISO+Joliet, ISOJolietUDF or ISO Level 2 formats. Can I use any of these are do I need to buy something else to transfer my files?

A flash drive formatted FAT32 works fine since both XP and OS X can read from and write to a FAT formatted device.
You can burn CDs if you need to otherwise save the data on the CDs, otherwise you're just going to waste them.

OES2 SP3: Master sends poison pill upon creation of new volumes

I'm experiencing problems when creating a clustered pool and volume on
OES2 SP3. After assigning a new FC LUN which is available on all nodes
I'm using iManager to create a new pool and volume on the master node as
described in the documentation. However, at some point in the procedure
the master starts killing other nodes. Inspection with nssmu shows that
the new pool is just available on some nodes. After a reboot everything
is working nicely.
Should I send the cluster to maintenance mode prior to adding a new
volume? How can I force OES2 to scan for new pools other than rebooting
the system? Is there a known problem or a TID for this behavior?
Gnther

Am 05.09.2012 09:38, schrieb Hans van den Heuvel:
> On Tue, 04 Sep 2012 18:00:53 +0000, Andy Konecny wrote:
>
> Hi Andy
>
>> From this TID, it does look like the fix isn't generally available yet,
>> especially given that the TID was last edited today.
>
> I have modified the wording in the TID, as the 'naming scheme' part
> seemed to be confusing here.
>
> The should have read as in this particular tree, specific services are
> installed and named in a specific way for easy identification purposes,
> and these newly created cluster resources just did not comply to that.
> They were just not named properly, nothing else.
Sorry, but right now I'm completely confused. What are you talking about?
From cluster administration manual:
"10.1.1 Naming Conventions for Cluster Resources
Cluster resource names can be up to 63 characters. Novell
Cluster Services supports only
alphanumeric characters and the underscore character in
cluster resource names:
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwx yz0123456789_
Special characters, such as the following, are not supported
in cluster resource names:
!@#$%&()
Because the NSS pool name and Linux volume names are
automatically used in the cluster resource
name, do not use special characters !@#$%&() in names of NSS
pools or Linux POSIX volumes that
you plan to cluster enable."
I did not use special characters in names of cluster resources, pools or
volumes. So will my problem be still related to this TID?
I will gave to go and check with CRM debugging.
Günther

ZDM 7 on OES2 sp3

Has anyone gotten ZDM 7 to work on OES2, sp3? I tried installing on 2 machines and got 2 different "non-fatal" errors which must have been fatal because I can't start the services. I only want workstation importing, thats it. Errors have to do with jclient/dclient, and some other things. I can post the real text from the install log if anyone has an idea. novell-zmd-awsi status says unknown file, and same for ZFDstart and ZFDstop in /opt/novell/zenworks/bin/whatever...
Thanks.

Originally Posted by jzamiska
Has anyone gotten ZDM 7 to work on OES2, sp3? I tried installing on 2 machines and got 2 different "non-fatal" errors which must have been fatal because I can't start the services. I only want workstation importing, thats it. Errors have to do with jclient/dclient, and some other things. I can post the real text from the install log if anyone has an idea. novell-zmd-awsi status says unknown file, and same for ZFDstart and ZFDstop in /opt/novell/zenworks/bin/whatever...
Thanks.
Along with Shaun's suggestion as it's related... also curious which ZDM install media you used (i.e. 7 SP1 IR4b)?
Cheers,
Willem

IFolder keeps prompting upgrade after OES2 SP3

Hi everyone,
After applying OES2 SP3 our iFolder server keeps prompting upgrade on
Windows XP clients. It suggests upgrading to 3.8.0.4 but when you let it
run, it shows windows installer options install and uninstall, there is
a space where the upgrade button should be. Neither option works.
I've also downloaded from the web server page the ifolder client, but
doesn't seem to be that version number.
Is there any way to disable the annoying prompt?
Thanks,
Miguel.

Originally Posted by mcando
Is there any way to disable the annoying prompt?
Thanks,
Miguel.
Section 6.12 of the iFolder 3.8.4 Admin Guide lists a way to disable the upgrade prompt.
Edit the unix-version.config, mac-version.config, and/or version.config (aka windows-version.config) files located in either /opt/novell/ifolder3/lib/simias/web/update or /opt/novell/ifolder3/lib64/simias/web/update.
Replace the <version> </version> section of the .config files with the level of client your users already have. Then they should not be prompted to upgrade.
Andrew

Transfer Trustees from Netware to OES2 SP3

Similar Messages

Maybe you are looking for