Clustering GWMon on OES2

Good Morning -
I have setup a 3 node GW Cluster on OES2sp1 using NSS. When installing GWMon it wants access to a domain. The only way I can see this is working if I do an ncpmount command to where the primary domain is. If anyone has any other ideas, please let me know. Do I have to create a permenant ncpmount to that cluster resource on all 3 nodes?
Thanks,

I have a SLES box that runs our GWMonitor. I have the Novell Client for Linux installed on it which does the mapping to a domain (GWMonitor wants to talk to a domain). The eDirectory account I use on that server has a personal login scripts that maps it.
From the console, I run:
'nwlogin -u my.user.name -p <users_pw> -t MYTREE -s <server_with_domain> -r'
The '-r' will have it process the login script which thereby connects via map. You can put this command into an executable file if need be.
For me, that box is so stable and so little trouble, I just use the command history when I get connection issues (which is rare).
HTH,
Aaron

Similar Messages

OES2 Cluster on VMware ESX

Has anyone installed an OES2 cluster on VmWare ESX successfully.

Originally Posted by rllangford
Has anyone installed an OES2 cluster on VmWare ESX successfully.
We have set up two ESX hosts (ESX 3.5 U4) and have two SLES10 64 clustered VMs with OES2 installed. We have two RDMs set up with a split brain partition (quorum drive). We have no problems setting all of this up and when it works it works well. What we have problems with is when we do maintainence on the ESX hosts.
We get the dreaded "Unable to power up machine due to afile lock" on the second clustered VM when we power it up after doing maintaince on the ESX host. The first clustered VM is powered up and ok but we are unable to clear the lock as ESX does not see it. VMware does not support this and Novell seems to point us to VMware. The only way we have cleared this up is by shutting down the ESX host for about 10 minutes and then powering it back up. This clears the lock sometimes. The most extreme case was we had to power down the SAN to release the lock.
There seems to be nothing specific on the web about our proble, only similar cases. Any help or advice would be appreciated.

File ownership ext3 resource dissappears

I have iPrint clustered on 2 OES2/L servers, stored on an ext3/evms
container. Both servers are LUM enabled, and I set the owner of a
directory to be a LUM user. I then offline the iPrint resource, which
deactivates the evms container. When I online the resource, the
ownership that I just set is gone, and root owns the directory again.
It does this even if I bring it back online on the same node.
The same thing also happens when I chown the directory to a local user
that exists on both servers.
If I mount the filesystem with the 'acl' flag, the ACLs stick, but the
ownership does not.
Any ideas why this is happening?

Agabriel,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

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

NSM does not create homedirs in an OES2-Linux-Cluster

Our situation:
The NSM Engine 2.5.1.1 (Jan 12 2010 15:30:55) is running under Netware6.5SP8, on the same server are also a NSM Event Monitor and a NSM Agent. We have a second server under SLES10SP3/OES2a with the Agent and Event Monitor running. While both Event servers can be seen with the NSM-Admin appliction the agent server configuration window displays only the Netware server, and the "eligible agent server" list consists only of Netware boxes.
The Netware and the Linux server contain both the complete replica of all partitions of our NDS-tree. Because we are on transition from Netware to Linux we deploy both Netware and Linux clusters (NCS)
The problem:
On our Netware-cluster (NW6.5SP8) NSM is able to perform all operations (create homedir, move homedir, delete, browse with the Path Analysis tool). Neither does the Linux cluster. No homedirs are created. While the clustered volumes occure in the volume list, with the Path Analysis tool it isn't possible to browse these volumes. No directory tree of these clustered volumes is displayed, but an error message instead: "Policy paths are unreachable". Non clustered volumes on the Linux boxes (including NSS-Volumes SYS and VOL1) can be browsed with the Path Analysis tool.

Hello,
I applied the last updates (no more warning signs in NSM-Admin-Tool) and after this the agent hosted on the linux box is visible in the Admin-Tool.
While rebuilding the volume list the following two kinds of messages appear:
For Netware-Cluster Volumes
01/06 16:13:52 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWKS.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:02 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP03V.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:11 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP04V.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:21 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP05V.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:30 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP06V.C2.UKJ) doesn't exist; Result = -603.
For Linux-Cluster Volumes
01/06 16:15:53 3: GetSERVERObjectsFromDSContainer: Failed to get the product version information for server (C3_NL3A01S.C3.UKJ); Result = 35073.
01/06 16:15:53 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C3_NL3A02S.C3.UKJ) exists (NSS /media/nss/NL3A02S); Result = 0.
01/06 16:15:56 4: GetServerConnection: open connection rc=35073 <C3_NL3A02P_SERVER>
01/06 16:16:00 4: GetServerConnection: open connection rc=35073 <C3_NL3A02P_SERVER>
01/06 16:16:00 3: GetSERVERObjectsFromDSContainer: Failed to get the product version information for server (C3_NL3A02S.C3.UKJ); Result = 35073.
01/06 16:16:01 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C3_NL3G01S.C3.UKJ) exists (NSS /media/nss/NL3G01S); Result = 0.
01/06 16:16:03 4: GetServerConnection: open connection rc=35073 <C3_NL3G01P_SERVER>
Any suggestions?
Greetings
M.

Rolling Cluster Upgrade (OES2 to OES11) - GPT partition

We've got an OES2 SP3 cluster that we'll be rolling cluster upgrading to OES11 SP2.
We are currently at max capacity for several of the NSS volumes (2 TB).
If I'm reading/interpreting the OES11 SP2 docs correctly:
AFTER the cluster upgrade is complete, the only way I can get to larger volumes will be to create new LUNs on the SAN and intialize those with GPT. Then I could do the NSS Pool Move feature to get the existing 2 TB volumes to the larger setup?
Is that correct?
Or is there a better way that doesnt' require massive downtime?

Originally Posted by konecnya
In article <[email protected]>, Kjhurni wrote:
> We are currently at max capacity for several of the NSS volumes (2 TB).
I was on the understanding that you could bind multiple partitions to
create NSS volumes up to 8TB. But I'd be hesitant to do that for a
clustered volume as well.
> I could do the NSS Pool Move feature to get the existing 2 TB
> volumes to the larger setup?
> Or is there a better way that doesnt' require massive downtime?
My first thought is the migration wizard so that the bulk of the copy can
be done while system is live but in the quieter times. Then the final
update with down time should be much faster.
But then do you really need down time for the Pool Move feature?
https://www.novell.com/documentation...a/bwtebhm.html
Certainly indicates it can be done live on a cluster with the move
process being cluster aware.
Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
Migration = pew pew (re-doing IP's/etc and copying 4 TB of data is ugly especially when it's lots of tiny stuff).
haha
Anyway, when I asked about a better way that doesn't require massive downtime what I meant was:
Is there a better way vs. Pool Move that doesn't require massive downtime (in other words, the "other way" having the massive downtime, not the Pool Move).
Choice A = Pool Move = No downtime
But let's say that's not a good option (for whatever reason) and someone says use Choice B. But Choice B ends up requiring downtime (like the data copy option).
I just didn't know if Pool Move required that you create the partition ahead of time (so you can choose GPT) or if it kinda did it all for you on the fly (I'll have to read up when I get to that point).
I'm not terribly keep on having multiple DOS partitions, although that technically would work. Just always scares me. It's just temporary for the next 8 months anyway while we migrate to NAS from OES, but I'm running out of space and am on an unsupported OS anyway.

Best plan for this scenario (migrate oes2 to oes11)

Hi there!
I would like to ask you guys the best plan for migrate a few servers that I have
in oes2 to oes11.
I have four servers in oes2sp2/sp3, these servers have a few NSS
volumes over NCS. Also I have my iPrint service on two machines,
also using NCS. I have one cluster between two machines and
other cluster between the other two machines. For exmaple,
machine1 and machine2, three NSS volumes (every NSS volume is a cluster
resource) and other resource in the same cluster for iPrint. Cluster: CL1
machine3 and machine4, one NSS volume (for other people in the company)
in other cluster. Cluster: CL2. In this cluster only have a NSS volume/resource.
Machine1/3 are physical, machine2/4 are virtual (vmware)
My CA is in other server that I will migrate after a while. So, It seems that there is
no problem with the certificate. Machine1 and machine3 are a replica for the eDir in
my organization.
My plan: I have deployed two virtual machines and one physical with oes11sp1 and sles11sp2.
I think that the best plan is migrate with migration tool iPrint first, like a cluster resource,
and NSS volumes, and after that, make a transfer ID (like a different project)
For machine1/3, move NSS volumes and after, make a transfer ID.
Is this correct? I dont know If I have to delete the current clusters (cl1 and cl2) and
create new ones, after that, create every resource as It was on the old ones.
thank you so much !
Antonio.

Originally Posted by kjhurni
This is just my opinion, of course, but:
If you don't want to have to migrate your NSS data and keep the same server names/IP/s and cluster load scripts, then I believe a Rolling Cluster Upgrade is a good way to go.
If you look in my signature, there's a link to my OES2 guides. Somewhere there is one that I did for our Rolling Cluster Upgrade.
If all you have is NSS and iPrint, then you only need to use the miggui (migration utility) for iPrint--or so I think (I do have to followup on this one as I vaguely recall I asked this a while back and there may have been a way to do this without migrating stuff again).
But your NSS data will simply "re-mount" on the OES11 nodes and you'll be fine (so that's why I like the rolling cluster upgrades).
Let me double-check on the OES2 -> OES11 cluster option with iPrint.
--Kevin
Thank you Kevin for your answer.
Finally, I think Im going to proceed using transfer ID on my servers that Im only using NSS over NCS (I only have two machines with one NSS volume)
because it seems that its a good option. I would like to keep old IPs from all the servers, cluster and resources if possible. So, testing this
migration on my test environment it seems that it works fine:
- I use miggui for transfer id between all the machines: physical -> physical and virtual -> virtual. eDirectory assumes new hostname, IP, etc.
the only task "out of the box" is that I have to delete the cluster and regenerate (reconfigure NCS on the new servers) but its pretty easy. This way
I have the two old ips from the older machines and all the ips from the cluster and the cluster resources also. I think that its the best plan.
For the other two machines that has 4 nss volumes and iPrint I must think about a plan. But with those, Im going to proceed this way. I hope
I have chosen a good plan!
thank you so much all for your answers / advices

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

CIFS enable existing clustered NSS volume

I'm rolling out CIFS shares of our existing clustered volumes. Perhaps I'm looking at this the wrong way, but I see no way to CIFS enable an existing cluster volume so as to create the Virtual CIFS server object. If I create a fresh pool & volume I can do it but I have 15TB of existing data.
thanks,
Andrew

Originally Posted by aferris
I'm rolling out CIFS shares of our existing clustered volumes. Perhaps I'm looking at this the wrong way, but I see no way to CIFS enable an existing cluster volume so as to create the Virtual CIFS server object. If I create a fresh pool & volume I can do it but I have 15TB of existing data.
thanks,
Andrew
I've got a nifty Word document I can send you. We're on OES2 SP3 NCS but I imagine the same applies for OES11. We do it slightly differently than the docs because we want to be able to edit the actual CIFS name that shows up, so you have to adjust the eDir objects, I believe (if you follow the actual docs, you get stuck with some of the default items and have to resort to manually editing some things if you wish to change their names).
Just send me a PM and I'll see if I can clean up any incriminating IP's, etc.
--Kevin

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

Antivirus: clustered NSS-Volume

hi,
I'm not sure if this is the right forum, but...
we want to install Antivirus-Services (sophos) on our cluster-nodes to protect against viruses on the nss-volume.
1. Does anyone have any experience on this subject - especially on the question if it's a good idea to run the AV on the cluster-nodes (load, locking of files, behaviour on virus detection and so on.)?
2. What is the Novell-recommended way to deal with the AV-Question in a clustered environment (sles10sp3+ oes2sp3)?
would appreciate any help on this.
thx,
hugo

Am 06.07.2011 17:36, schrieb susehoush:
> we want to install Antivirus-Services (sophos) on our cluster-nodes to
> protect against viruses on the nss-volume.
>
> 1. Does anyone have any experience on this subject - especially on the
> question if it's a good idea to run the AV on the cluster-nodes (load,
> locking of files, behaviour on virus detection and so on.)?
A volume mounted as nssvol on an OES2 SP2,3 server might be scanned with
savscan like a local one. We use an entry to /etc/cron.d which is
created by the cluster load and deleted by the cluster unload script.
Cron starts a daily savscan on the cluster volume, eg:
savscan /media/nss/VOL1 -exclude $EXCL -p=$SLOGDIR/sophos-$2-$DATE
-move=$QUARANTINE --no-follow-symlinks --no-reset-atime -archive -all
-pua -nc -mime -oe
Replace the variables with suitable names. Be aware that the "-archive"
and "-all" options might slow down the scan significantly.
A savscan job will result in 100% CPU load. With todays multicore CPU
this should be OK provided that not too many are started at once. I
should add a nice statement to the call also.
Savscan interferes with our backup system. I had to add the
"--no-reset-atime" option. Without it the ctime of all files scanned
will be updated which results in the files being included in the next
incremental backup. This turns all incremental backups in full ones, of
course.
I never tried on access scanning. IMO this does not make much sense on a
file server and should be done on the clients.
> 2. What is the Novell-recommended way to deal with the AV-Question in
> a clustered environment (sles10sp3+ oes2sp3)?
I have no idea. But in general support at sophos is quite responsive.
Gnther

Clustered volume question

I've recently taken over the administration of a network that has the core file shares on 3 physical, clustered Netware 6.5 machines. They are extremely old servers and the Fiber-Channel SAN on which the file shares reside is at end-of-life. The combined size of these file shares is around 1 TB. I need to migrate these volumes to some other platform.
I'm much more familiar with SLES and OES2 than I am with Netware. I need to move these file shares to new Equalogic SAN volumes. I'd like to create a clustered or at least an HA environment. I'd like the hosts to be VM's on ESX 3.5 (soon to be upgraded to ESXi 4.0).
What I'm looking for are some suggestions from the community as to how to proceed. Reliability is an issue as is speed. The Netware/Clustered volume environment has been extremely reliable.
We are a private university with approximately 600-800 concurrent users. Any suggestions would be helpful.

Novell does provide migration tools.. Personally I like to do the work
manually.
To move the data shouldn't be a problem.. you can export on netware the
volumes via NFS and Rsync the Data directly to an OES Server (obviously
you could use CIFS or NCP as well, I just find NFS faster)
If you use the rsync -a option it preserves most file information (there
are other options)
Backup the trustees on Netware (using trustee.nlm)
you will then need to convert this file format to OES file format,
Again I do this via a script that turns each line in to a RIGHTS import
command (rights is used on OES Linux)
If you have moved homedrives you will need to re-apply file permissions
either via trustee export or I just run in linux an 'ls' in a for loop
on the Users folders and apply that using the rights command.
You will also need to re-add the homeDirectory attribute. again I use a
tool, that a colleague wrote, it is called ldapdo and is on coolsolutions
We run a 5 node cluster, on physical hardware, I am not sure how well
supported clustering is on ESX.. Personally I would use physical
hardware. But then I am not a fan of ESX.
Personally, I don't find OES Linux as good as Netware, We had the same
number of resources on fewer servers, That said with the latest updates
stability has vastly improved and so has the cluster migrate speeds.
We currently have up to 2000 concurrent users on a busy day (with up to
80 - 90 concurrent logins for labs). We provide access via NCP, CIFS
and NFS for Linux labs, although we are looking to remove NFS as with
NSS you can only export the file system with a NO_ROOT_SQUASH.
Our data usage is about 14TB across 30 resources, Our university is try
to centralise all IT, onto Windows however are failing to provide a
solution that is stable and able to support multi protocol access. In
the mean time, our system limps on, on old hardware.
If you want any of the scripts let me know, they really were thrown
together but they do the job.. I have to migrate data quite often on to
new disks (Bigger) As our data requirements grow. We use some pretty
reliable but cheap sata SANS called infortrends... As our budget is
minimal..
On 24/09/10 12:36 AM, tagross wrote:
>
> I've recently taken over the administration of a network that has the
> core file shares on 3 physical, clustered Netware 6.5 machines. They are
> extremely old servers and the Fiber-Channel SAN on which the file shares
> reside is at end-of-life. The combined size of these file shares is
> around 1 TB. I need to migrate these volumes to some other platform.
>
> I'm much more familiar with SLES and OES2 than I am with Netware. I
> need to move these file shares to new Equalogic SAN volumes. I'd like to
> create a clustered or at least an HA environment. I'd like the hosts to
> be VM's on ESX 3.5 (soon to be upgraded to ESXi 4.0).
>
> What I'm looking for are some suggestions from the community as to how
> to proceed. Reliability is an issue as is speed. The Netware/Clustered
> volume environment has been extremely reliable.
>
> We are a private university with approximately 600-800 concurrent
> users. Any suggestions would be helpful.
>
>

Issue in Synchronous File Read in clustered environment

Hi,
We are using clustered environment (4 managed servers) in Unix. In a OSB 11gR3 proxy service we are using Synchronous File Read. Randomly we are getting the below error. Let us know what could cause the issue. But the same code is working fine in a single stand-alone server configuration.
Error Code : BEA-380002 , Error Reason : Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/wsdlPathAndName [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content ; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderNamer/Filename.txt to be processed was not found or not available or has no content Please make sure that the file exists in the specified directory.
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/wsdlPathAndName [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content ; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content Please make sure that the file exists in the specified directory.
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:598)
at sun.reflect.GeneratedMethodAccessor1115.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy142.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:670)
at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatchSync(PipelineContextImpl.java:551)
at stages.transform.runtime.WsCalloutRuntimeStep$WsCalloutDispatcher.dispatch(WsCalloutRuntimeStep.java:1391)
at stages.transform.runtime.WsCalloutRuntimeStep.processMessage(WsCalloutRuntimeStep.java:236)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:96)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl$4.run(JCATransportInboundOperationBindingServiceImpl.java:415)
at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl$4.run(JCATransportInboundOperationBindingServiceImpl.java:413)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.sendMessage(JCATransportInboundOperationBindingServiceImpl.java:413)
at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.invokeOneWay(JCATransportInboundOperationBindingServiceImpl.java:126)
at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.post(JCAInboundRequestListener.java:39)
at oracle.tip.adapter.sa.impl.inbound.JCAInboundListenerImpl.onMessage(JCAInboundListenerImpl.java:170)
at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:502)
at oracle.tip.adapter.file.inbound.Publisher.onMessageDelegate(Publisher.java:493)
at oracle.tip.adapter.file.inbound.Publisher.publishMessage(Publisher.java:419)
at oracle.tip.adapter.file.inbound.InboundTranslatorDelegate.xlate(InboundTranslatorDelegate.java:484)
at oracle.tip.adapter.file.inbound.InboundTranslatorDelegate.doXlate(InboundTranslatorDelegate.java:121)
at oracle.tip.adapter.file.inbound.ProcessorDelegate.doXlate(ProcessorDelegate.java:388)
at oracle.tip.adapter.file.inbound.ProcessorDelegate.process(ProcessorDelegate.java:174)
at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:349)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/wsdlPathAndName [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content ; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content Please make sure that the file exists in the specified directory.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
... 56 more
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/wsdlPathAndName [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content ; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content Please make sure that the file exists in the specified directory.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:662)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:353)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:312)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:350)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:253)
... 57 more
Caused by: BINDING.JCA-11007
No Data to process.
No Data to process.
File /root/oracle/domains/osb/11.1.1.4/cluster/data/osb2/FolderName/Filename.txt to be processed was not found or not available or has no content Please make sure that the file exists in the specified directory.
at oracle.tip.adapter.file.outbound.FileReader.readFile(FileReader.java:277)
at oracle.tip.adapter.file.outbound.FileReader.executeFileRead(FileReader.java:181)
at oracle.tip.adapter.file.outbound.FileInteraction.executeFileRead(FileInteraction.java:331)
at oracle.tip.adapter.file.outbound.FileInteraction.execute(FileInteraction.java:395)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:529)
... 61 more
Edited by: 842347 on Jul 6, 2011 3:11 AM

I face the same issue and I have given all permissions to the folder for OS user.
Because of this error my server is not starting up . Is there any way I can undeploy this composite to get my server running.
I cant do this from EM because SOA server is failing to start up.
I have tried removing it from $DOMAIN_HOME/deployed-composites but still when i try restarting the soa server the composite comes up there. Do we need to delete the entry some where else too. Kindly help.
Thanks,
Sri.

What is RID in non clustered index and its use

Hi All,
I need help regarding following articles on sql server
1) what is RID in non clustered index and its use.
2) What is Physical and virtual address space. Difference in 32 bit vs 64 bit Virtual address space
Regards
Rahul

Next time Please ask single question in a thread you will get better response.
1. RID is location of heap. When you create Non clustered index on heap and
lookup happens to get extra records RID is used to locate the records. RID is basically Row ID. This is basic definition for you. Please read
this Thread for more details
2. I have not heard of Physical address space. I Know Virtual address space( VAS)
VAS is simple terms is amount of memory( virtual ) 'visible' to a process, a process can be SQL Server process or windows process. It theoretically depends on architecture of Operating System. 32 bit OS will have maximum range of 4 G VAS, it's calculated
like a process ruining on 32 bit system can address max up to 2^32 locations ( which is equivalent to 4 G). Similarly for 64 bit max VAS will be 2^64 which is theoretically infinite. To make things feasible maximum VAS for 64 bit system is kept to 8 TB. Now
VAS acts as layer of abstraction an intermediate .Instead of all request directly mapping to physical memory it first maps to VAS and then mapped to physical memory so that it can manage request for memory in more coordinated fashion than allowing process
to do it ,if not it will soon cause memory crunch.Any process when created on windows will see virtual memory according to its VAS limit.
Please read
This Article for detailed information
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Space occupied by clustered index Vs non-clustered index

I am trying to understand the indexes. Does clustered index occupy more space than a non-clustered index because it carries the information about rest of the other columns also. Could you guys please help me understand this. Thanks in advance.
svk

Hi czarvk,
Clustered index in SQL Server takes up more space than non-clustered indexes.
Clustered index arranges the way records are stored in a table putting them in order (key, value), all the data are sorted on the values of the index.
A non-clustered index is a completely different object in a table, containing only a subset of columns and a row locator to the table’s rows or to the clustered index’s key.
So clustered index in SQL Server takes up more space than non-clustered indexes.
If you have any question, please feel free to let me know.
Regards,
Donghui Li

Clustering GWMon on OES2

Similar Messages

Maybe you are looking for