Windows 2008 R2 Failover Cluster: Removing Cluster Resource (SFW Disk Group)
Hi forum, I have to remove a SFW cluster resource (virtualized storage consisting of three disk arrays) from a Windows Server 2008 R2 Fileserver Cluster, and just want to make sure that I don't delete the SFW volume by removing it from the cluster. So my Step-by-Step plan looks like the following. Did I forget something or is something wrong? Name of the File Server: "MyFileServer" Name of the volume to be removed: "MyVOL" 1. Open Windows Failover Cluster Manager and expand in the navigation column the tree to your File Server "MyFileServer" 2. Section "File Server" (in the main window): Switch File Server "MyVOL" to OFFLINE 3. Section "Drives" (in the main window): Switch Drive "MyVOL" to OFFLINE 4. Section "File Server" (in the main window): Right click on File Server "MyVOL" and select "Delete" from the context menu 5. Section "Drives" (in the main window): Right click on Drive "MyVOL" and select "Remove from MyFileServer" from the context menu By step 5, I guess that under "Storage" (click on "Storage" in the navigation column) the resource "MyVOL" will be shown under "Available Resources". Question: Does it have to be removed also from here to remove it completely from the Windows Cluster? If the answer is "yes": 6. Choose "Storage" in the navigation column 7. Section "Available Drives": Delete MyVOL Once again: The aim is to remove the MyVOL resource from the cluster but keep it as a SFW volume (as it has to be connected later on as a normal dynamic disk group to one of the file server nodes). (I'm sure this is a very simple question to answer for anybody who has ever removed a SFW volume from a Windows Failover Cluster.) Thank you very much for your answer! Regards, BobSolved2.8KViews2likes2CommentsInstallation of Storage Foundation on Win 2003 Ent. R2
Hi, We have two servers with two non-standerd application running. The Operating System - Windows 2003 Ent. R2 FC based storage connected with both the servers. Now we wants a DR site with host to host replication ... Will this solution work ..........any caution need to take care... I came accross some docs..that the C drive need to be in adifferent arry... IS IT.. Is there any thing else need to take care... Can we also do through Backup Exec to take a backup and create a DR site ...or something.. Please, help.. :) Thanks.SFHA - Windows with VMware shared vmdk disk
IHACr who wants to Implement a Windows SFHA Cluster with a shared vmdk disk. They have procured the SFHA Windows license. The Cluster nodes/VM's will be hosted on seperate ESX hosts. Few questions: a) Is this configuration (shared vmdk) supported in a Windows SFHA cluster? b) What happens in case one VMware ESX host fails? Will the VM in the second host continue having access to the shared vmdk? c) This question is not related to Symantec but more specific to VMware ESX. How should the datastore in VmWare be configured. My understanding is that a SAN LUN datastore can only be seen by one VMware host at a time?Solved1.1KViews1like2CommentsStorage Foundation Agents Queries
Dear Team, As VVR and VCS is a part of Storage foundation there are several applications/solutions for which you need to configure VCS and VVR. So I'm a bit confused the agents that are available for Storage Foundation are for VSC only or there are agents for VVR also.SolvedStorage Foundation for Windows 5.1 SP2 on Windows 2008R2 SP1 (Full Version)?
Hi, We want to install SFW HA 5.1 Sp2 on Windows 2008 R2 SP1 (x64, Full GUI version). I noticed only Windows 2008 R2 CORE is listed in the compatability matrix, but the full GUI version of W2K8 R2 is not for some reason... Can anybody at Symantec please confirm that I can install SFW HA 5.1 SP2 on Windows 2008 R2 SP1 (x64, Full GUI version) ??? Thank you in advance! FredSolved813Views1like3CommentsWindows File Share keeps getting lost on reboot of server
I wonder if anyone here can assist with this problem. We have a backup server which uses SFW5.0 which has a FC SAN connected o it. When we reboot the server it loses its File Share which we use to save all our backups to. The file share is located on a single volume, on an imported disk group. The volume comes up fine, but the share is always missing when we reboot. The only thing we can think of is that we had to implement a latestart on the Vertias service because it wasn't importing the disks correctly without this. Our feeling is that it might be to do with Microsoft waiting for the disk volume, when it doesn't see it, it stops trying to share the folder, perhaps because it is coming in so late as a result of the latestart. Has anyone encountered this or have a workaround to keep the shared folder coming up on reboots? NickSolved4.7KViews1like5Comments