Windows 2012 Failover Cluster - File server role (vCO)

Hi,
I wonder if anybody can shed some light on a query i have.
A windows 2012 failover cluster will be built in AD domain example.uk. Cluster File server roles will be created and will reside in this domain also.
We also have a requirement to run a cluster file server role in the child domain off secure.example.uk. Is this possible? or do the file server roles and related vCO's have to reside in the same domain as the cluster (CNO).
I know the CNO can be used to create the VCO but could a prestage a VCO in the child domain of secure.example.uk.
Mark

Hi Mark,
By default CNO will create
VCO automatically in default domain computer OU, we generally use the
KISS principle to place the CNO and VCO to the same OU, and as far as I know there no known design document indicate the VCO can be placed in different domain, therefore I suggest you place the CNO and V CO at same OU.
More information:
When Creating a New Resource or Role in Windows Server 2012 R2 Failover Cluster, the Network Name Fails to Come Online or Failed to Create Associated Computer Object in Domain
http://blogs.technet.com/b/askpfeplat/archive/2014/11/17/when-creating-a-new-resource-or-role-in-windows-server-2012-r2-failover-cluster-the-network-name-fails-to-come-online-or-failed-to-create-associated-computer-object-in-domain.aspx
CNO Blog Series: Increasing Awareness around the Cluster Name Object (CNO)
http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.aspx
How to Create a Cluster in a Restrictive Active Directory Environment
http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
Prestage Cluster Computer Objects in Active Directory Domain Services
https://technet.microsoft.com/en-us/library/dn466519.aspx
I’m glad to be of help to you!
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 Support, contact [email protected]

Similar Messages

Failover cluster File Server role best practices

We recently implemented a Hyper-V Server Core 2012 R2 cluster with the sole purpose to run our server environment. I started with our file servers and decided to create multiple file servers and put them in a cluster for high
availability. So now I have a cluster of VMs, which I have now learned is called a guest cluster, and I added the File Server role to this cluster. It then struck me that I could have just as easily created the File Server role under my Hyper-V
Server cluster and removed this extra virtual layer.
I'm reaching out to this community to see if there are any best practices on using the File Server role. Are there any benefits to having a guest cluster provide file shares? Or am I making things overly complicated for no reason?
Just to be clear, I'm just trying to make a simple Windows file server with folder shares that have security enabled on them for users to access internally. I'm using Hyper-V Core server 2012 R2 on my physical servers and right now I have Windows
Server Standard 2012 R2 on the VMs in the guest cluster.
Thanks for any information you can provide.

Hi,
Generally with Hyper-V VMs available, we will install all roles into virtual machines as that will be easy for management purpose.
In your situation the host system is a server core, so it seems that manage file shares with a GUI is much better.
I cannot find an article specifically regarding "best practices of setting up failover cluster". Here are 2 articles regarding build guest cluster (you have already done) and steps to create a file server cluster.
Hyper-V Guest Clustering Step-by-Step Guide
http://blogs.technet.com/b/mghazai/archive/2009/12/12/hyper-v-guest-clustering-step-by-step-guide.aspx
Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
https://technet.microsoft.com/en-us/library/cc731844(v=ws.10).aspx
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

FTP in Windows 2012 Failover Cluster

Hi,
Understand that Windows 2012 is having much improved Failover Clustering features,however i have faced issues when i configured FTP in Windows 2012 Failover Cluster.
1) As per the process configured the shared disk for FTP data path.
2)Installaed FTP feature in both Nodes of Clustert
3)Finally created the Generic Service in Cluster Roles for FTP Service.
After the configuration i found everything working fine but when i try to failover the FTP role found that FTP resource is not moving smoothly. Also i observed that Microsoft FTP service gets in to "starting" mode in the destination Node. To run the FTP
resource Microsft FTP service should be in Started mode.
This happens only when we try to failover else it works fine if you start freshly.
Have any one tried this? Any clue about such issue ?
Regards:Mahesh

Hi,
In earlier versions of Internet Information Services, Microsoft provided generic resource monitor components to support high availability Web server instances by using the Microsoft Clustering infrastructure. However, custom code was needed to fully realize
the potential of this solution. Also, the generic scripts that Microsoft provided did not satisfy customer needs.
From IIS 7 to configure IIS in a clustered environment by using Windows Server failover clustering, you have to use a custom (scripting) code to enable such a high availability scenario.
Note:
We recommend that administrators carefully evaluate the use of Network Load Balancing (NLB) instead of using failover clustering as the primary and preferred method for improving the scalability and availability of Web applications that have multiple servers
that are running new IIS (from IIS 7) . One benefit of NLB is that all servers can actively participate in the concurrent handling of incoming HTTP requests. Another benefit is that in an NLB IIS environment, it can be much easier to support rolling updates
and rollbacks while still providing high availability of Web applications.
To configure high availability for IIS FTP servers using Failover Clustering:
Install the Web Server role on all cluster nodes.
Install the Failover Clustering feature on all cluster nodes and create the cluster.
Set up a file share that will be used for IIS shared configuration
Configure the IIS shared configuration on all cluster nodes
Configure Offline Files for IIS Shared Configuration on all cluster nodes
Configure the FTP site and specify the location of its content on one cluster node
Configure high availability for your FTP site by creating a generic script in Failover Cluster Manager
For more detailed configuration procedure please refer to following MS articles:
Note: I didn’t find IIS 8 in Windows Server 2012 failover cluster configuration guide, below guide was published for II 7 in Windows server 2008 and Windows Server 2008 R2, but its basis configuration procedures should also apply to Windows Server 2012.
How to configure FTP 7.5 for IIS 7.0 in a Windows Server 2008 failover cluster
http://support.microsoft.com/kb/974603
Configure IIS Network Load Balancing
http://www.iis.net/learn/web-hosting/configuring-servers-in-the-windows-web-platform/network-load-balancing
Deploying IIS on a Failover Cluster
http://blogs.msdn.com/b/clustering/archive/2009/06/01/9674799.aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

Migrating single file server to failover cluster file server

Hi,
Currently we have one file server which is our Domain controller also. File Server data stored in SAN storage lun. Users home folders also resides at file server.Now we want to create 2 node failover cluster file server.
Questions:
1)Can we assign same storage lun to failover cluster?
2)Do we need to assign all permissions and storage quota again?
What is the best option to achieve this goal.

Hi,
if you attach the same LUN to the failover cluster the NTFS permission (security tab) are retained because they are stored in the LUN itself
Share permission are lost because they are stored in the registry of the file server. If you have few share with a simple share permission structure, simply recreate them in the cluster. If you have a lot of shares and complex permission tree, you have to
export registry hives related to lanmanserver\shares

Windows 2012 Failover Cluster

Having a problem creating 2 node cluster. I launch FCM, begin the process of adding nodes. Node 1 goes in fine. Node 2 gives an error which is, "unable to connect to xxx.xxxx.com via WMI. This may be due to networking issues
or firewall configuration.
Node 1 and 2 are virtual. Have tried them on the same metal and on different metal.
Any advice would be much appreciated.

Hi shageman0304,
Unfortunately, the available information is not enough to have a clear view of the occurred behavior. Could you provide more information about your environment. For example,
the exact text of any error? When this problem occurs the system log record information, screenshots is the best information.
If you have install any third party software on this node please disable or exit them, please install the Recommended hotfixes and updates for Windows Server 2012-based failover
clusters updates then monitor this issue again.
Recommended hotfixes and updates for Windows Server 2012-based failover clusters
http://support2.microsoft.com/kb/2784261
After install the updates, if the issue still exist please performing the following steps:
1. Open Task Manager on the affected server and check if the wmiprvse.exe is running if not please enable the wmi service.
2. Restart wmi service.
3. Restart the server.
Please rerun the validation test then post the error part, that report will quickly locate the issue.
More information:
Unable to launch Cluster Failover Manager on any node of a 2012/2012R2 Cluster
http://blogs.technet.com/b/askcore/archive/2013/12/17/unable-to-launch-cluster-failover-manager-on-any-node-of-a-2012-2012r2-cluster.aspx
Event Logs
http://technet.microsoft.com/en-us/library/cc722404.aspx
I’m glad to be of help to you!
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.

Apply SP1 to SQL 2012 clustered on a Windows 2012 failover cluster

For earlier versions of clustering there was an ability to prevent a resource from failing to a particular node. I used this when service packing clusters to ensure that no SQL instances would attempt to fail back to the node I was patching. That ability
doesn't seem to exist anymore. ANd pausing or stopping a node causes rule failure in the SP setup.
Has anyone successfully performed this patching and are there any best practises or tips to follow?
Regards, Matt Bowler MCITP, My Blog

Hello Matt,
This is still available, though I'm not sure where you remember it being. You can choose individual resources in a resource group and can also do it at the resource group level as well. It's in the properties of each level and allows each resource or resource
group to be allowed to run on only the nodes selected.
Here is the KB on it (though they use the command line):
http://support.microsoft.com/kb/958734
I'd patch the instances on the nodes that the instance is not currently active (if more than 1), pause the node and reboot if necessary. Continue rolling until services need to be moved or your patched nodes outweigh your unpatched nodes at which point I'd
move the services and patch all remaining nodes.
-Sean
Sean Gallardy | Blog |
Twitter

Cannot Add File Share to (any) File Server Role of a Cluster in Windows Server 2012

Cannot Add File Share to (any) File Server Role of a Cluster in Windows Server 2012...
Get this message in the Operational Log in "FileServices-ServerManager-EventProvider" section of MS-Windows Eventlogs:
Exception: Caught exception Microsoft.Management.Infrastructure.CimException: The xsi:type attribute (MSCluster_Property_Resource_Network_Name) does not identify an existing class.
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext(Boolean discardResultsAndErrors)
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext()
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.PerformQuery(String cimNamespace, String queryString)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.BuildNodes(ICimSession session, ClusterRole scopeType, String query, IDictionary`2 groupNameToTypeMap)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.GetClusterClientAccessPointNames(ICimSession session, IDictionary`2 groupNameToTypeMap)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.RetrieveClusterConnections(ComputerName serverName, ClusterMemberTypes memberTypeToQuery)
Thanks for help...(everything else works fine in other type of cluster roles).
Thomas.

This issue also happens in fresh Windows 2012R2 installations, not just upgrades from 2008R2!
I have the issue where I cannot modify any settings on SMB shares. Here is the stacktrace. It appears to be WMI related.
Error: ERROR: Task 'TEST.xxxxxxx.COM-ClusterStorage$-SmbShareUpdate-46bcabf6-1dd4-4a48-a525-5e5d374596c7' has failed: Microsoft.FileServer.Management.Plugin.FSACException: Error occurred while updating an SMB share: The requested operation is not supported.
---> Microsoft.Management.Infrastructure.CimException: The requested operation is not supported.
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext()
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
   at Microsoft.Management.Infrastructure.CimSession.ModifyInstance(String namespaceName, CimInstance instance, CimOperationOptions options)
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.ModifyInstance(ICimInstance instance)
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.ModifyInstance(ICimInstance instance, IEnumerable`1 propertiesWithKeys)
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoUpdateInstance(ICimSession session, ICimInstance instance)
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoWork(Object sender, DoWorkEventArgs e)
   --- End of inner exception stack trace ---
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Selecting VHDx as storage for File Server Role (Failover Cluster 2012 R2)

Is it possible to select an already existing (offline) VHD or VHDX as storage when creating the "File Server" role? Reason I want to do that is because I already have a file server setup as a virtual machine and causing issues so my company
decided to make the change towards a File Server role.
Thank you
David

Hi David,
Do you mean you configured it to file server failover cluster via "High Availability Wizard" ?
I think you need to choose a shared volume between two nodes to achieve high availability .
Please refer to following link :
http://technet.microsoft.com/en-us/library/cc731844(v=WS.10).aspx
If you do not select a shared volume , I think there is no difference than sharing a mounted VHDX file on a standalone file server .
I would suggest to copy these files to CSV and share them .
Hope it helps
Best Regards
Elton Ji
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.

Cluster File Server Migration

Dears,
I have my source cluster based on WIndows 2008 R2 with SP1, and my new target cluster is Windows 2012 R2.
when I run the copy wizard it validate if I can migrate the file server, however, it is giving me those in yellow mark:
File Server IP Address is not eligible to be copied. (Failed to read 'EnableDhcp' property)
FileServer01 is not eligible to be copied.
Is this normal?
How to continue migrating file server role?

Hi Jean M,
Could you try to manually configure the IPs by referring to the previous 2008 R2 node, then and bring the new file-servers online?
More related information:
Best practices for migration of cluster windows 2008 R2 / 2012 - As melhores Praticas para migrar um Cluster de Windows 2008 para Windows 2012
http://blogs.technet.com/b/hugofe/archive/2012/12/06/best-practices-for-migration-of-cluster-windows-2008-r2-2012-as-melhores-praticas-para-migrar-um-cluster-de-windows-2008-para-windows-2012.aspx
How to Move Highly Available (Clustered) VMs to Windows Server 2012 with the Cluster Migration Wizard
http://blogs.msdn.com/b/clustering/archive/2012/06/25/10323434.aspx
Migration Paths for Migrating to a Failover Cluster Running Windows Server 2012 R2
https://technet.microsoft.com/en-us/library/dn530781.aspx
I’m glad to be of help to you!
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 Support, contact [email protected]

Mount Points in Windows 2012 R2 Cluster not displaying correctly

Hi,
Try
and I might, I can't get Mount Points displayed properly in a Windows 2012 R2 cluster.
In Windows 2008 R2, I added them, and they appear under Storage, as for Example, Cluster Disk 7: Mounted Volume (S:\SYSDB). (I may have had to bring them offline/online).
in Windows 2012 R2, they are showing up as, for example, '\\?\Volume{7c636157-e7e9-11e4-80dc0005056873123}'
In the error log it shows up as :
Cluster disk resource 'Cluster Disk 7' contains an invalid mount point. Both the source and target disks associated with the mount point must be clustered disks, and must be members of the same group.
Mount point 'SYSDB\' for volume '\\?\Volume{7c636106-e7e9-11e4-80dc-005056873123}\' references an invalid target disk. Please ensure that the target disk is also a clustered disk and in the same group as the source disk (hosting the mount point).
Now I've checked the error, and in
https://technet.microsoft.com/en-au/library/dd353925(v=ws.10).aspx it says
"The mounted disk and the disk it is mounted onto must be part of the same clustered service or application. They cannot be in two different clustered services or applications, and they cannot be in the general pool of Available Storage in the cluster."
So I have created a 'Other Server' Role. When I go right click on the Role and go to 'Add Storage', Cluster Disk 6 (the root volume) displays S:\, and Cluster Disk 9 (hosting the mountpoint) says Mount Point(s): (S:\SYSDB). I select both, and add, but
alas, the Mount Point still shows up as '\\?\Volume{7c636106-e7e9-11e4-80dc-005056873123}\ (not S:\SYSDB or Cluster Disk 6: Mounted Volume (S:\SYSDB).) as I would expect.
They are both clustered disks (iSCSI). I would expect when it says in the "same group", both added to the same role would be in the same group.

Hi,
Thankyou for your response. That's (sort of) good to know, but it seems to be a step backwards from Windows 2008 R2, where you would actually have the meaningful Mounted Volume: (S:\SYSDB) displayed, to the meaningless '\\?\Volume{7c636157-e7e9-11e4-80dc0005056873123}'
GUID. Obviously before you do anything, you need to cross reference the disk number to 'Disk Management'; it would be better if is was displayed correctly in Failover Cluster Manager in the first place.
Secondly, the GUID is somewhat misleading. In Windows 2008 R2 for example, it appears as though the same GUID was displayed on each node (e.g. using Mountvol.exe). In Windows 2012 R2, it appears as though different GUID's are displayed on each node, e.g.
Node 1.
\\?\Volume{7c6368a4-e7e9-11e4-80dc-005056873123}\
S:\SYSDB\
Node 2.
\\?\Volume{97cc0d34-e7e9-11e4-80db-0050568724c4}\
S:\SYSDB\
But the GUID in Failover cluster manager remains the same (you can't really cross reference with what you see in FCM to Mountvol).
Strangely enough, when I check the registry in 'MountedDevices' on Node 1, both of the GUIDs are displayed (even though only one is displayed in MountVol.exe), referencing the same Disk ID listed in Diskpart.exe. I can see this mentioned in
https://support.microsoft.com/en-us/kb/959573, where is says :
A volume can be multiple unique volume names (and thus multiple GUIDs) when it is used by multiple running installations of Windows. This could happen in the following scenarios and in similar scenarios where multiple installations of Windows have
accessed the volume:
Using a volume on a shared disk in a cluster where multiple nodes have accessed the volume.
Oh well, that's progress I guess.

Virtual Domain Controllers in 2012 Failover Cluster. Time Skew

Hi All,
Not sure if this is the correct space for this topic, however i'll give it a go anyway.
We have a 2 Hosts (HP DL385) Windows Server 2012 Failover Cluster.
Storage is provided by a 12 Bay NAS with iSCSI connections (This is catering for CSV's and Quorum)
We are running 2 Virtual domain controllers (2008R2)
The issue we experience is that if the cluster goes down, and when it comes back online the time on the domain controllers (one or the other or both) skews by any where up to 3 days which causes havoc for our office until we can resync clocks with the PDCe.
Time Synchronisation Integration Service is disabled on both Domain Contollers
A few days back we need to reboot the storage on the cluster, and the tasks performed were as follows:
-Power off all virtual machines (Graceful Shutdown)
-Put all CSV's into maintenance mode
-Offline Disk Witness to Quorum
-Rebooted Storage (Waited until it came back online)
-Online Quorum Storage (Successful)
-Bring CSV's out of maintenance mode (Successful & Browsable)
-Power on all Virtual Machines (Successful)
This is where the time Skewed and caused headaches. The time for some reason went to 2 days 11hrs in the past on 1 domain controller.
With this DNS lookups failed to work, Cluster services failed, Cluster Aware Updating Failed, RDP to VM's (and Virtual Hosts) by DNS Name failed (Date time error)
There doesn't seem to be anything in the EventLog except for date/time stamp on events being 2 days in the past.
Now this is why i'm not sure if the issue is cause by fail over clustering, or is an issue with the domain controllers.
Any advice regarding this or if anyone has seen this behaviour before any info would be great
Thanks
Rob

Hi Rob,
Does both this two DCs on your cluster VM and there have not others DCs? Microsoft recommends that files for virtualized domain controllers be placed on non-CSV
disks, Non-CSV disks can be brought online without authentication. Because non-CSV disks can be brought online more easily.
For virtual machines that are configured as domain controllers, it is recommended that you disable time synchronization between the host system and guest operating
system acting as a domain controller. This enables your guest domain controller to synchronize time from the domain hierarchy, please confirm your PDC time is always correct.
The related KB:
Running Domain Controllers in Hyper-V
https://technet.microsoft.com/en-us/library/d2cae85b-41ac-497f-8cd1-5fbaa6740ffe(v=ws.10)#deployment_considerations_for_virtualized_domain_controllers
Things to consider when you host Active Directory domain controllers in virtual hosting environments
http://support.microsoft.com/kb/888794?wa=wsignin1.0
I’m glad to be of help to you!
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 Support, contact [email protected]

SCCM 2007 Distribution Point Share on a Failover Clustered File Server.

Is SCCM 2007 Distribution Point Share supported on a Windows 2008 R2 Failover Clustered File Server? I can get the packages to copy to the DP Share. But if I create them on a non clustered server it works fine. Are there any special settings that need top
be configured for clustered shares?
Thanks,
Steve
Steve

Hi Steve,
As far as I know this scenario is not supported scenario, In Windows Server® 2008 R2, the Cluster Shared Volumes feature included in failover clustering is only supported for
use with the Hyper-V server role.
The creation, reproduction, and storage of files on Cluster Shared Volumes that were not created for the Hyper-V role, including any user or application data stored under the
ClusterStorage folder of the system drive on every node, are not supported and may result in unpredictable behavior, including data corruption or data loss on these shared volumes. Only files that are created for the Hyper-V role can be stored on Cluster Shared
Volumes. An example of a file type that is created for the Hyper-V role is a Virtual Hard Disk (VHD) file.
More information:
Deploying Cluster Shared Volumes (CSV) in Windows Server 2008 R2 Failover Clustering
http://blogs.msdn.com/b/clustering/archive/2009/02/19/9433146.aspx
Backing Up Cluster Shared Volumes in a Failover Cluster in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ff182356(WS.10).aspx
I’m glad to be of help to you!
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 Support, contact [email protected]

Is there any way to enable eventlog replication between two nodes in windows 2008 failover cluster.

Is there any way to enable eventlog replication between two nodes in windows 2008 failover cluster.
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

Hi,
As far as I know there don’t have the log replica function between failover cluster node, if you want to have the Unified log management you can refer the following related
KB:
Configure Computers to Forward and Collect Events
http://technet.microsoft.com/en-us/library/cc748890.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.

Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

Failover cluster server - File Server role is clustered - Shadow copies do not seem to travel to other node when failing over

Hi,
New to 2012 and implementing a clustered environment for our File Services role. Have got to a point where I have successfully configured the Shadow copy settings.
Have a large (15tb) disk. S:
Have a VSS drive (volume shadow copy drive) V:
Have successfully configured through Windows Explorer the Shadow copy settings.
Created dependencies in Failcover Cluster Server console whereby S: depends on V:
However, when I failover the resource and browse the Client Access Point share there are no entries under the "Previous Versions" tab.
When I visit the S: drive in windows explorer and open the Shadow copy dialogue box, there are entries showing the times and dates of the shadow copies ran when on the original node. So the disk knows about the shadow copies that were ran on the
original node but the "previous versions" tab has no entries to display.
This is in a 2012 server (NOT R2 version).
Can anyone explain what might be the reason? Do I have an "issue" or is this by design?
All help apprecieated!
Kathy
Kathleen Hayhurst Senior IT Support Analyst

Hi,
Please first check the requirements in following article:
Using Shadow Copies of Shared Folders in a server cluster
http://technet.microsoft.com/en-us/library/cc779378(v=ws.10).aspx
Cluster-managed shadow copies can only be created in a single quorum device cluster on a disk with a Physical Disk resource. In a single node cluster or majority node set cluster without a shared cluster disk, shadow copies can only be created and managed
locally.
You cannot enable Shadow Copies of Shared Folders for the quorum resource, although you can enable Shadow Copies of Shared Folders for a File Share resource.
The recurring scheduled task that generates volume shadow copies must run on the same node that currently owns the storage volume.
The cluster resource that manages the scheduled task must be able to fail over with the Physical Disk resource that manages the storage volume.
If you have any feedback on our support, please send to [email protected]

Windows 2012 Failover Cluster - File server role (vCO)

Similar Messages

Maybe you are looking for