Windows 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
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.8KViews2likes2CommentsStorage Foundation 5.1 and MSCS not working
Hi. We want to use Storage Foundation 5.1 to manage our dual path disk. We are clustering MS BizTalk 2006 so we need to use MSCS to Cluster BizTalk. Problem is that MSCS cannot see the disk group created in SF. We are using Windows 2003 Enterprise Server R2 We installed SF first and the disk groups appear fine. Then we tried to configure MSCS and it could not see the disk. During some investigation we discovered we needed the MSCS Option, so we added our "VRTS STORAGE FOUNDATION OPTION MICROSOFT CLUSTER 5.1 WIN FOR OS TIER ENTERPRISE EDITION STD LIC" license key and it indicated that the MSCS option is available. However, when we go back to Add/Remove programs to select this option, it does not appear as a choice in the add/remove SF options. How should we proceed? Is there a seperate plug in we need to download or should it appear in the list of options in the SF installation screen? Do we need to have MSCS configured before we install SF so it can detect it? Any advice would be appreciated. WarrenSolved1.9KViews0likes4Comments
Initializing disk on Windows
hai, i just started learning VXVM. As suggested by one of our friends on this forum, Lee, i have installed SF for Windows 5.1 on by windows 2008 virtual machine. i have provisioned couple of iSCSI luns from my NetApp Filer. everything went fine as far as disk discovery on the server. my problem is when i run the #vxdisk list command, it shows that the disks are not initialized. i think i cant go forward with out doing that. but the good side is, i can able to see the disks in the VEA GUI and i am able to initialize the disks, create disk groups, volumes and so on... i am curious to know how to initialize the disks using command line.......coz after that i can use other good commands to create the disk groups, volume and so on.... is there any difference between how VERITASsees SCSI disks and iSCSI disks? Thanks Krrish.Solved1.9KViews0likes11Comments
Storage Foundation 3.2.542.0 error message
Hi all, we have a veritas enterprise administrator runnning on windows 2003 server cluster running. Now i see an exclamation mark on some volumes and hd's. If opne a volume and see one of the disks i see this alerts: Warning V-76-58645-1000 Aler Propagated and Error V-76-58645-1080 Subdisk Detached If i take a look on my SAN it seems that all HD's are ok. At the moment I'm not really know what it means and what i have to do. Can anyone help me here? Or i have just to reactivate the harddisks? or just du cluster turn to the other cluster node? Thank you very much!Solved1.8KViews0likes11CommentsTricky Volume Group cration question
Hello, We would like to have 2 RDM attached to a VM. Is it possible to keep same volume group name ? The reason why I'm asking is that. SAN team will do the frame base copy time to time from RDM1 to RDM2 so I can't have different volume group name, metadata (Private region) will be overwritten when SAN team do the copy. For the project purpose some times I need to mount RDM1 or RDM2 using VBS. Is it possible to do?Solved1.7KViews0likes5Comments
Storage Foundation for Windows - WELCOME SPLASHSCREEN
Hello, I am in the middle of engineering a new build for my company and we are rolling out Vertias Storage Foundation for Windows 5.1 SP2 to all new servers going forward (R2 SP1). One of the things I have noticed when Veritas has been installed is the "Solutions Configuration Center" splashscreen that appears when the user logs in. Nowthen, I know there us a checkbox to disable it so it does not appear again but was wondering if there is a registry key I can call so that this can be done automatically so it does not launch. Everything is automateed so makes sense to follow this approach - hate to have hundreds of users call asking how annoying the splashscreen is! Thanks,Solved1.6KViews0likes3Comments