Cluster Volumes

1. After trying to install the netware agent using my windows 7 machine, I got an error message about it not being able to determine my version of netware. So I switched to an XP machine to install the Netware agent.
2. My Netware servers are cluster servers. After installing the agent, I am only able to scan the SYS volumes on those servers. I couldn't find any information on how to setup the agent for the cluster virtual servers. Anybody done this who can share what they know?

Hi Marc,
1.(a) I will have our testing department test the agent installation
from a Windows 7 box. I haven't heard of any issues, and the entire
department is running Windows 7. But I will have you some results soon.
I just tried it with my Windows 7 installing an agent to a VM Netware
6.5 sp8 server.
I will still get a ruling from our testing department.
2.(a) The engineers are about to release a version of the NFR Agent
that will have "proxy" abilities to be able to proxy for cluster virtual
servers as well as NAS virtual servers. In the meantime, I have a back
door way to do it. With the agent installed on the cluster node itself,
there is a SRAGENT.CFG file under SYS:NFR. You can modify that file and
add a tag (if it doesn't exist) below the <BaseDir> tag:
<ServerName>virtual server name</ServerName>
Let the agent heartbeat in with this name and you will be able to scan
the volumes.
Hope this helps!
NFR team
marcporter wrote:
> 1. After trying to install the netware agent using my windows 7 machine,
> I got an error message about it not being able to determine my version
> of netware. So I switched to an XP machine to install the Netware
> agent.
>
> 2. My Netware servers are cluster servers. After installing the agent,
> I am only able to scan the SYS volumes on those servers. I couldn't
> find any information on how to setup the agent for the cluster virtual
> servers. Anybody done this who can share what they know?
>
>

Similar Messages

Migrate from server core 2008 r2 hyper-v with failover cluster volumes to server core 2012 r2 hyper-v with failover cluster volumes on new san hardware

We are getting ready to migrate from server core 2008 r2 hyper-v with failover cluster volumes on an iscsi san to server core 2012 r2 hyper-v with failover cluster volumes on a new iscsi san.
I've been searching for a "best practices" article for this but have been coming up short. The information I have found either pertains to migrating from 2008 r2 to 2012 r2 with failover cluster volumes on the same hardware, or migrating
to different hardware without failover cluster volumes.
If there is anyone out there that has completed a similar migration, it would be great to hear any feedback you may have on your experiences.
Currently, my approach is as follows:
1. Configure new hyper-v with failover cluster volumes on new SAN with new 2012 r2 hostnodes and 2012 r2 management server
2. Turn off the virtual machines on old 2008 r2 hyper-v hostnodes
3. Stop the VMMS service on the 2008 r2 hostnodes
4. copy the virtual machine files and folders over to the new failover cluster volumes
5. Import vm's into server 2012 r2 hyper-v.
Any feedback on the opertain I have in mind would be helpful.
Thank you,
Rob

Hi Rob,
Yes , I agree with that "file copy " can achieve migration.
Also you can try "copy cluster wizard " :
https://technet.microsoft.com/en-us/library/dn530779.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Mounting NSS Cluster Volumes on other Linux Nodes

Hi,
have anyone experience how to mount OES NSS Cluster Volumes on other
Linux Servers (SLES/RedHat/Centos)?
Traditional i would say i have to use NFS, but did this run fine on OES
Cluster Volumes?
How must i do this here, what are the recommend mount options?
Documentation say do it "native to Linux"???
hmm, how?
How should i write the /etc/exports file on OES Cluster Nodes(should
these look same on all Cluster Nodes)?
What happen on Resource Failover, should nfsd restarted?
Have anyone running this?
Regards
Thomas

Since you're using NSS in a clustered setup, I am assuming you're using just NCP?
I'm not sure if the ncpmount or the NCL (Novell Client for Linux) work on anything other than the Suse platforms (you mentioned RHEL and CentOS).
Otherwise you MAY be able to also run CIFS to "publish" the NSS volume and then you should be able to use native SMB connection methods to connect from the other linux OS's.
I would probably avoid NFS only because it has no concept of file locking (or at least doesn't seem to care) and may happily overwrite a file that's in use by someone with NCP access.

Mac 10.8.4 - OES11 Cluster volume migration

I am posting this question as we are trying to implement the 'same' features we are used to with Windows.
The kanaka client 2.8 & server are configured and have the clustering resources set to the same vol-name as in the documentation
Now some questions:
1) when a cluster resource moves - the kanaka client loses connectivity - is there a way to have it auto reconnect as windows clients do?
2) When Word is open and editing a document on a network volume - The network volume is migrated - Word crashes and loses the contents
Is there a timeout for reconnecting? I see a timeout for logging in and the default is 60 seconds.
what are some of the best solutions for what I am asking ?
Thanks in advance
Joe

Some further info
In our testing without cluster migration we have noticed that volumes have been dropped.
When the Macs went to sleep (for about 15 minutes) - all the volumes were present.
When they were asleep for longer - some volumes dropped but not all ?

Distributing files on Cluster Volumes

Hi,
has anybody already distributed files to a NetWare 6.5 SP5-Cluster
Shared Volume?
It´s easy to distribute to a native server with a volume DATA:. But in
the cluster environment we have volumes called DATA1:, DATA2:, etc..
I tried to used multiple components in the software package. Every
component has a requirement of a directory on the shared volume (i. e.
component1: 'DATA1:\SYSTEM', component2: 'DATA2:\SYSTEM', etc.) and a
'copy file' with the same files to different volumes.
It works fine, but TED includes the same files for every component
again. It results in a file size twice or three times greater than normal.
What are you doing?
Thanks,
Guido.

Guido,
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:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at http://support.novell.com in both the "free product support" and "paid product support" drop down boxes.
- You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums)
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/

Case insensitive NSS volume on cluster

We are trying to migrate from Apache2 running on a Netware server to a OES2 Linux server running on a two node cluster. The Cluster Volume is NSS and when Apache runs we appear to have a case sensitivity issue. I have read on the Forums that NSS can be configured to be case insensitive but I am unsure how I change the cluster to mount NSS case insensitive.
Can anyone assist? (It would sure help because trying to change all of the folders and files to lowercase and change all of the .php scripts to load the lowercase folders has been a nightmare!)
Thanks for any information that you can provide!
Charlie
~~~

Originally Posted by utman
I found an OES 1 doc that says if you add the long namespace it will make it case insensitive.
Novell Documentation
Any idea if I LOSE anything by mounting it with Long Namespace? I have never been quite sure WHY you would want it to be Case Sensitive in Linux. It just seems to make for a lot of confusion. (HOME vs. home)

Server 2012 File Server Cluster Shadow Copies Disappear Some Time After Failover

Hello,
I've seen similar questions posted on here before however I have yet to find a solution that worked for us so I'm adding my process in hopes someone can point out where I went wrong.
The problem: After failover, shadow copies are only available for a short time on the secondary server. Before the task to create new shadow copies happens the shadow copies are deleted. Failing back shows them missing on the primary server as
well when this happens.
We have a 2 node (hereafter server1 and server2) cluster with a quorum disk. There are 8 disk resources which are mapped to the cluster via iScsi. 4 of these disks are setup as storage and the other 4 are currently set up as shadow copy volumes
for their respective storage volume.
Previously we weren't using separate shadow copy volumes and seeing the same issue described in the topic title. I followed two other topics on here that seemed close and then setup the separate shadow copy volumes however it has yet to alleviate the
issue. These are the two other topics :
Topic 1: https://social.technet.microsoft.com/Forums/windowsserver/en-US/ba0d2568-53ac-4523-a49e-4e453d14627f/failover-cluster-server-file-server-role-is-clustered-shadow-copies-do-not-seem-to-travel-to?forum=winserverClustering
Topic 2: https://social.technet.microsoft.com/Forums/windowsserver/en-US/c884c31b-a50e-4c9d-96f3-119e347a61e8/shadow-copies-missing-after-failover-on-2008-r2-cluster
After reading both of those topics I did the following:
1) Add the 4 new volumes to the cluster for shadow copies
2) Made each storage volume dependent on it's shadow copy volume in FCM
3) Went to the currently active node directly and opened up "My Computer", I then went to the properties of each storage volume and set up shadow copies to go to the respective shadow copy volume drive letter with correct size for spacing, etc.
4) I then went back to FCM and right clicked on the corresponding storage volume and choose "Configure Shadow Copy" and set the schedule for 12:00 noon and 5:00 PM.
5) I noticed that on the nodes the task was created and that the task would failover between the nodes and appeared correct.
6) Everything appears to failover correctly, all volumes come up, drive letters are same, shadow copy storage settings are the same, and 4 scheduled tasks for shadow copy appear on the current node after failover.
Thinking everything was setup according to best practice I did some testing by changing file contents throughout the day making sure that previous versions were created as scheduled on server1. I then rebooted Server1 to simulate failure. Server2
picked up the role within about 10 seconds and files were avaiable. I checked and I could still see previous versions for the files after failover that were created on server1. Unfortunately that didn't last as the next day before noon I was going
to make more changes to files to ensure that not only could we see the shadow copies that were created when Server1 owned the file server role but also that the copies created on Server2 would be seen on failback. I was disappointed to discover that
the shadow copies were all gone and failing back didn't produce them either.
Does anyone have any insight into this issue? I must be missing a switch somewhere or perhaps this isn't even possible with our cluster type based on this: http://technet.microsoft.com/en-us/library/cc779378%28v=ws.10%29.aspx
Now here's an interesting part, shadow copies on 1 of our 4 volumes have been retained from both nodes through the testing, but I can't figure out what makes it different though I do suspect that perhaps the "Disk#s" in computer management / disk
management perhaps need to be the same between servers? For example, on server 1 the disk #s for cluster volume 1 might be "Disk4" but on server 2 the same volume might be called "Disk7", however I think that operations like this
and shadow copy are based on the disk GUID and perhaps this shouldn't matter.
Edit, checked on the disk numbers, I see no correlation between what I'm seeing in shadow copy and what is happening to the numbers. All other items, quotas, etc fail and work correctly despite these diffs:
Disk Numbers on Server 1:
Format: "shadow/storerelation volume = Disk Number"
aHome storage1 = 16
aShared storage2 = 09
sHome storage3 = 01
sShared storage4 = 04
aHome shadow1 = 10
aShared shadow2 = 11
sHome shadow3 = 02
sShared shadow4 = 05
Disk numbers on Server 2:
aHome storage1 = 16 (SAME)
aShared storage2 = 04 (DIFF)
sHome storage3 = 05 (DIFF)
sShared storage4 = 08 (DIFF)
aHome shadow1 = 10 (SAME)
aShared shadow2 = 11 (SAME)
sHome shadow3 = 06 (DIFF)
sShared shadow4 = 09 (DIFF)
Thanks in advance for your assistance/guidance on this matter!

Hello Alex,
Thank you for your reply. I will go through your questions in order as best I can, though I'm not the backup expert here.
1) "Did you see any event ID when the VSS fail?
please offer us more information about your environment, such as what type backup you are using the soft ware based or hard ware VSS device."
I saw a number of events on inspection. Interestingly enough, the event ID 60 issues did not occur on the drive where shadow copies did remain after the two reboots. I'm putting my event notes in a code block to try to preserve formatting/readability.
I've written down events from both server 1 and 2 in this code block, documenting the first reboot causing the role to move to server 2 and then the second reboot going back to server 1:
JANUARY 2
9:34:20 PM - Server 1 - Event ID: 1074 - INFO - Source: User 32 - Standard reboot request from explorer.exe (Initiated by me)
9:34:21 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy49
F:
T:
The locale specific resource for the desired message is not present"
9:34:21 PM - Server 1 - Event ID 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy1
H:
V:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 6, 13, 18, 22, 27, 32, 38, 41, 45, 51,
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy4
E:
S:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 5, 10, 19, 21, 25, 29, 37, 40, 46, 48, 48
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Legacy Network Service service entered the stopped state."
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the stopped state.""
9:34:29 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Client Service service entered the stopped state."
9:34:30 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Discovery Framework service entered the stopped state."
10:44:07 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
10:44:08 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Microsoft Software Shadow Copy Provider service entered the running state."
10:45:01 PM - Server 2 - Event ID: 48 - ERROR - Source: bxois - "Target failed to respond in time to a NOP request."
10:45:01 PM - Server 2 - Event ID: 20 - ERROR - Source: bxois - "Connection to the target was lost. The initiator will attempt to retry the connection."
10:45:01 PM - Server 2 - Event ID: 153 - WARN - Source: disk - "The IO operation at logical block address 0x146d2c580 for Disk 7 was retried."
10:45:03 PM - Server 2 - Event ID: 34 - INFO - Source: bxois - "A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name."
JANUARY 3
At around 2:30 I reboot Server 2, seeing that shadow copy was missing after previous failure. Here are the relevant events from the flip back to server 1.
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy24
F:
T:
The locale specific resource for the desired message is not present"
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy23
E:
S:
The locale specific resource for the desired message is not present"
We are using Symantec NetBackup. The client agent is installed on both server1 and 2. We're backing them up based on the complete drive letter for each storage volume (this makes recovery easier). I believe this is what you would call "software
based VSS". We don't have the infrastructure/setup to do hardware based snapshots. The drives reside on a compellent san mapped to the cluster via iScsi.
2) "Confirm the following registry is exist:
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Settings"
The key is there, however the DWORD value is not, would that mean that the
default value is being used at this point?

Problem instaling Subscriber in netware cluster

Hello.
I am using ZSM 7.0.1 installation program and trying to install only
subscriber functinality on a cluster OES Netware with Sp5.
The installation says it goes successful in the 2 logfiles that comes up
after the installation but when I try to offline and then online the
cluster-volume with the ZSM7 installed on it it goes into comatose because
the zfs.ncf is missing in the zenworks folder on the volume. I can not find
the file on any other volume on the server. I also have the ZDM701 installed
on the server before I install ZSM701 on it. The ZDM701 install was totaly
fine and it works great. The only ZDM701 services installed on the server on
the same volume is WOL, Import and Removal.
So my question is, how am I supose to get the right files and folders into
the cluster and to get it work. It should not be a problem.
Does anyone no what to do.
Thanks
Best regards Jonas Rydstrom

ZSM is supported on a cluster, you have to choose though to have either a
single cluster resource installed with ZSM or installing in on the
individual nodes. In this case it looks like Jonas installed ZSM on a
cluster resource, that's supposed to work, not sure why zfs.ncf isn't there.
Ron
"Jared Jennings" <[email protected]> wrote in message
news:Jv_4i.5587$[email protected]..
> Jonas Rydstrm,
>
>>OK, can you be more specific about what is not supported. I was succesful
>>installing both ZDM701 and ZSM701 Distributor, Subscriber and database on
>>a
>>single server to specific zenworks volume and the services on that server
>>seems to run fine.
>
> It is not supported to run individual subscriber objects on cluster nodes.
> The only portion of ZFS that is supported in a cluster environment is the
> distributor object.
>
> So, you are correct in that you can run ZFS, ZFD, and the database on a
> non-clustered server.
>
> You can also run ZFD on a clustered resource. The ZFD 7.0 with SP1 install
> correctly installed all the files to the clustered volume so that the
> services could load and fail-over with the information being consistent.
> All ZFD services load from \\clusteredvolume\public or
> \\clusteredvolume\system etc.
>
> ZFS supports clustered environments, but the clustered resource that loads
> the distributor code, cannot send distributions to subscriber objects
> representing nodes in the cluster, nor can it send to the clustered
> subscriber object that does exist and represents the clustered zfs
> resource.
>
> --
> Jared Jennings - Data Technique, Inc.
> Novell Support Forums Sysop
> My Blog and Wiki with Tips, Tricks, and Tutorials
> http://jaredjennings.org

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.

Ghost VM resources under failover cluster manager roles

Hello, everyone,
I had a Windows 2012 R2 hyper-v host with few VMs running on it. I deployed a second host, and using SC VMM created a failover cluster. Also I added a shared cluster volume and migrated all VMs to the shared storage using SC VMM console. In
the process I also checked the checkbox to make the VM highly available. Everithyng worked fine.
Now when I look in to Failover Cluster Manager console I see some "ghost" vm roles. Their names are correspondend to the names of the running VMs, which I also can see in the console. For example I have vm HDCADC01, there is another
role in the console "SCVMM HDCADC01 Resources", the status is off, settings are empty.
Does anyone knows what are these resources? Is it somekind of glitch during the migration? Is it safe to remove them?
Thank you,
Jamal.

Where should I run this command?
On my VMM server Update-clustervirtualmachineconfiguration command complains that The cluster services is not running.
On the one of hyper-v server, cluster nodes, "get-vm -name hdcadc01" returns "Get-VM : A parameter is invalid. Hyper-V was unable to find a virtual machine with name hdcadc01". The same result is when I used "ghost" resources name.

NIC not failing Over in Cluster

Hi there...I have configured 2 Node cluster with SoFS role...for VM Cluster and HA using Windows Server 2012 Data Center. Current set up is Host Server has 3 NICS (2 with Default Gateway setup (192.x.x.x), 3 NIC is for heartbeat 10.X.X.X). Configured CSV
(can also see the shortcut in the C:\). Planning to setup few VMs pointing to the disk in the 2 separate storage servers (1 NIC in 192.x.x.x) and also have 2 NIC in 10.x.x.x network. I am able to install VM and point the disk to the share in the cluster volume
1.
I have created 2 VM Switch for 2 separate Host server (using Hyper-V manager). When I test the functionality by taking Node 2, I can see the Disk Owner node is changing to Node 1, but the VM NIC 2 is not failing over automatically to VM NIC 1 (but I can
see the VM NIC 1 is showing up un-selected in the VM Settings). when I go to the VM Settings > Network Adapter, I get error -
An Error occurred for resource VM "VM Name". select the "information details" action to view events for this resource. The network adapter is configures to a switch which no longer exists or a resource
pool that has been deleted or renamed (with configuration error in "Virtual Switch" drop down menu).
Can you please let me know any resolution to fix this issue...Hoping to hear from you.
VT

Hi,
From your description “My another thing I would like to test is...I also would like to bring a disk down (right now, I have 2 disk - CSV and one Quorum disk) for that 2 node
cluster. I was testing by bringing a csv disk down, the VM didnt failover” Are you trying to test the failover cluster now? If so, please refer the following related KB:
Test the Failover of a Clustered Service or Application
http://technet.microsoft.com/en-us/library/cc754577.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Alert: The backup operation for the cluster configuration data has been canceled due to an abort request

Hello,
Alert: The backup operation for the cluster configuration data has been canceled due to an abort request
Alert description: The backup operation for the cluster configuration data has been canceled. The cluster Volume Shadow Copy Service (VSS) writer received an abort request.
This is the backup of VSS which is sending this alert every morning.
Event ID 1544
All fixes I found are applied..
kb2277439 has already been applied
978527 is there too
975921 is there too..
any other id
Cluster Node /Status gives both nodes up A & B
The error is coming only on Node A...
Any idea?
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi,
Which backup software do you use to do a backup? Please also try to apply those hotfix on the Cluster:
A transient communication failure causes a Windows Server 2008 R2 failover cluster to stop working
http://support.microsoft.com/kb/2550886
The network location profile changes from "Domain" to "Public" in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2524478
Recommended hotfixes and updates for Windows Server 2008 R2 SP1 Failover Clusters
http://support.microsoft.com/kb/2545685/EN-US
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DHCP on OES11 Cluster

Hello,
I have some problems to get DHCP Service running in a Cluster Evironment (OES11 SP1, NSS Volume). The Ressource is up and running, but the DHCP Service wont load.
LDAPS session successfully enabled to 10.0.181.36:636
Error: Cannot find LDAP entry matching (&(objectClass=dhcpServer)(cn=DHCP_CLUSTER-DNSDHCP-SERVER))
Configuration file errors encountered -- exiting
The standard command rcnovell-dhcp start did work. So it looks like the rights or seomthing else is missing on the cluster volume /media/nssDHCP...
Maybe I am misunderstanding the doc as well. It states in the DHCP Linux Guide:
8.3.3. hot wo use a different user - it states that it would use the dhcpd user , but no such user was created. Do I need to create it manually?
Thanks for your help!
Regards Jrgen

Hi,
If I recall correctly from my setup, I had to create a user and LUM enable it, and match the UID to the local account.
See here: http://www.novell.com/documentation/...a/bbe81cc.html
Let us know how it goes.
Cheers,

Iprint over cluster NSS

Hi all:
Template inheritance is possible only for EVMS cluster volume and pools,
Iprint_template inheritance is currently not possible for NSS cluster volumes and pools.
For NSS clusters, iprint_nss_relocate script has to be inserted manually....
How I can do it?
I Created NSS pools and volumes and moved data whit:
iprint_nss_relocate -a cn=admin,o=XX -p password -n /media/nss/printers -l cluster
And now ? .....
where I can find information about the script for NSS?
Thanks.

It works :=)
Load Script
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error nss /poolact=IMPRESION
exit_on_error ncpcon mount IMPRESION=252
exit_on_error add_secondary_ipaddress 10.XX.XX.XX
exit_on_error ncpcon bind --ncpservername=CLUSTERHP_IMPRESION_SERVER --ipaddress=10.XX.XX.XX
ignore_error mv /media/nss/IMPRESION/var/opt/novell/iprint/
iprintgw.lpr /media/nss/IMPRESION/var/opt/novell/iprint/
iprintgw.lpr.bak
exit_on_error rcnovell-idsd start
exit_on_error rcnovell-ipsmd start
exit 0
Unload Script.
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
ignore_error rcnovell-ipsmd stop
ignore_error rcnovell-idsd stop
ignore_error ncpcon unbind --ncpservername=CLUSTERHP_IMPRESION_SERVER --ipaddress=10.XX.XX.XX
ignore_error del_secondary_ipaddress 10.XX.XX.XX
ignore_error nss /pooldeact=IMPRESION
exit 0

Upgrade OES2 to OES11 Cluster

Hi all,
we plan to upgrade our 2-node Cluster running on OES2SP3 x64 to current
version running on OES11SP1. The cluster provides GroupWise, File and iPrint
Services and is connected via QLogic iSCSI HBA to our SAN.
What would you recommend how the Upgrade could be done without major
trouble?
Thanks in advance
Alex

On 16.02.2014 14:54, Alexander Lorenz wrote:
> Hi all,
>
> we plan to upgrade our 2-node Cluster running on OES2SP3 x64 to current
> version running on OES11SP1. The cluster provides GroupWise, File and iPrint
> Services and is connected via QLogic iSCSI HBA to our SAN.
>
> What would you recommend how the Upgrade could be done without major
> trouble?
There should be no trouble at all. Move all ressources to one Node, then
update the free node to OES11 as documented, move ressources to the
upgraded server, test, then do the same with the other node. But I
suggest use SP2 instead of SP1. There's really not much special on a
cluster node vs a "normal" server.
One thing you may need to check into is iPrint. If it's fully clustered,
your weg data of iPrint will reside on a clustered volume, which however
will never be available on the node that's currently upgraded, so you
likely end up with the old iPrint stuff there. Yuo may want to re-run
the iprint cluster setup script again (or if you feel able to, copy the
local iPrint data over to the cluster volume).
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

Cluster Volumes

Similar Messages

Maybe you are looking for