Storage Foundation 5.1 compatibility with HP StoreServ 7000/8000
Dear colleagues, The question is simple: is HP StoreServ 7000/8000 compatible with Storage Foundation 5.1? HCL for Storage Foundation 5.1 (http://www.veritas.com/docs/000008646) does not contain any information regarding StoreServ 7000/8000. HCL for SF 6.0 (http://www.veritas.com/docs/000011772) has StoreServ 7000/8000 compatibility included. So will StoreServ 7000/8000 be backward compatible with Storage Foundation 5.1? Are there any specifiic differences between SF 5.1 anf SF 6.0 that could prevent StoreServ from backward compatibility?1.3KViews0likes2Comments"vxdmpadm pathinfo" reports "internal disk" for Hitachi Luns
Dear all, I have the following infrastructure: Two Windows physical servers in a VCS cluster. Serversare using Hitachi SAN LDEVs. Veritas DMP is used for I/O multipathing. My problem is that on one of the nodes, the command "vxdmpadm pathinfo" returns "internal disk" messages for all the external Hitachi LDEVs. The other nodes is reporting the paths properly as expected. Example: Harddisk23: is an internal disk and no DMP information can be found. I should state that the server does not seem to suffer from any issues with accessing the Hitachi LDEVs. Can you please help me understand - Why does vxdmpadm returns this incorret message? Should any corrective actions be taken? Is this a source for concern? Thank you all in advance.1.6KViews0likes0CommentsStorage Foundation License Tiering
I'm going through some old license purchases, and i've come across a substantial number of Storage Foundation Standard licenses of various license tiers. It also looks like some of the purchases were made on one tiering system (1A, 4C etc), and others were made on a different system (A-N) Does anyone have any guidance on how I interpret these tiers to confirm what my license entitlement is? ThanksSolved2.1KViews1like7CommentsHigh Availability Solution Needed
Hello, I have server hardware hooked up to a SAN, with a very mission critical MS SQL database running. I need a high availability solution that can ensure no SQL transactions are lost in a fail over. Can a Symantec product do this, and which would it be? Server 2008 R2 is running the MS SQL 2008 DB. It currently has two servers in a cluster with some third party software that we are getting rid of due to the hardware limitations per VM, it's old almost EOL software. So I'm shopping for the latest and greatest. Right now the servers are running as a VM under XenServer, this does not have to be the case, we will work around what ever will work best for us. I can put these back on bare metal, put them in some Symantec perfered format, what ever works best. Is the product agent based or does it act as a host to clients in some fashion? I ask because I see there is a Windows version of Storage Foundation, then theres a Linux Cluster server. I'd rather use something that actually runs off Linux, or acts a Linux host. I would like to know the difference between the two and which would work best for me. Thank you very much DarylSolved561Views1like1CommentStorace Exec 5.3 - File Content Signatures
Hi guys, running the now unsupported Storage Exec 5.2 HF 24. I'm trying to ensure that file content checking blocks e-mail files but there are no signatures in the registry for .msg files etc. Is it possible to create them? I assume they are some sort of reg expression check against the file hearder or hash? PS: I'm looking to move away form this product obviously!544Views0likes2CommentsMirroring DCO & DRL - Windows Failover CLuster
Hi everybody, I've got just some questions about DCO and DRL in Storage Foundation. Maybe someone can help ;) I have a 2 nodes failover cluster (windows 2012) and I use Storage Foundation 6.0.2 to create a Dynamic Disk Group. This dynamic disk group contains 2 SAN disks (these disks are located on remote and separated storage arrays) and the option "Create cluster Group" is enabled. I create a new volume (mirrored option enabled) and then, I add Log (DRL) & FastResync (FastResync is mirrored beetweend disks) Sometimes, when a network failure occurs, I have to remove and add again the DRL on the disks which was previously in failure. This behaviour is explained here. Ok, now I wonder if I really need to add the DRL on disks ? I have read here that the DRL is built into DCO Version 20. How can in know which version Storage Foundation uses ? I tried something like vxprint -g name-oft-he-disk-group -F%... but it didn't work. For your information, here is the failue: I do apologize for my english. Regards. MatStackSolved881Views0likes2CommentsV-52410-33095-278
Environment - OS = Windows 2008 R2 - Exchange = 2010 - SFHA/DR = 6.0.1 - Two nodes at Primary and two nodes at DR site - Two Exchange databases created on two individual diskgroups with individual SRL - Two service groups for each database - A dadicated NIC is allocated for Replication. (on Layer-II means no gateway required for replication between both sites) (NIC1 of Node1 at Primary site IP= 172.17.1.1, NIC2 of Node2 at Primary site IP= 172.17.1.2, Virtual IP is 172.17.1.10) (NIC1 of Node1 at Secondary site IP= 172.17.1.3, NIC2 of Node2 at Secondary site IP= 172.17.1.4, Virtual IP is 172.17.1.11) Scenario Phase-I Initially I configured the local HA at Primary site with one Service Group of one Exchange database, and then execute the Disaster recovery wizard so that I can configure the DR HA site and replication between both. I configured the Service Group(s) for one of Exchange database. Now I have two Service Groups at both sites. One is Exchange application service group and second is replication service group Phase-II Again I execute the Disaster recovery wizard to configure the second Service Group for second Exchange database. but at the point of repliction configuration I see the below message. My question is I will have two RVGs(one for Exchange database service group1 and second is for Exchange database service group2 ) but both RVGs will share the same replication link which is dedicated for replication data. So for this I can use the same IPs for both RVGs. Should I ignore this message or use different IPs for each RVG ??? ThanksSolved1.2KViews0likes6CommentsHow to run fbsync on windows ?
Environment OS = Windows 2008 R2 (64bit) SFHA = 6.0.1 One Diskgroup with one volume configured and that volume configured for replication. Replication is running fine and we tried migration between both nodes which is also running fine. Question - I shutdown primary Node and takeover DR node which did successful. - I start entering data on DR site node which is also going good. - I start Primary Node. Now both sites nodes showing Primary Primary. In this situation in Linux I do fbsyc which make DR Site Node New Primary and make the Primary Site Node New DR node. But in windows under VEA i am not able to see the fbsync command. ANy suggestion will be appriciated -Solved1.3KViews0likes7Comments