upgrade SFHA
Hi All, Regarding the need of configuring DR with VVR we have purchase the new licence Infoscale 7.1 Can we upgrade from SFHA 6.1 to Veritas Infoscale Enterprise 7.1? if not what are the best method to preserve data when installing the new product. Thanks in advance.1.8KViews0likes0Comments
What volume name does VVR use for replication?
I'm about to implement volume replication with InfoScale 7.0 on windows. Currently, InfoScale is only installed on the new DR server and isn't on the production server yet. When I look at the VEA console, select my disk group and click on the volumes tab, I see all the volumes I have set up. But there is a Volume column and a Volume Name column. For example, Volume MailArchive01 is known with the internal volume name of Volume2. For various reasons, the volumes are being created in advance on our DR server and I understand that VVR will replicate volume-to-volume. But will it be replicating MailArchive01 to MailArchive01 or Volume2 to Volume2? The internal volume names seem to be arbitrarily assigned by the software, so when I install in production, there is no guarantee that they are all going to be mapped to the same internal names. For example, it could be MailArchive01:Volume2 on DR and MailArchive01:Volume3 on Prod. I see that there is an option to "change internal volume name" in the VEA console but don't know if this is necessary.Solved1.7KViews0likes1Commentvvr replication not ok .....need help to fix it
Hello, Replication is not happening , however RVG is enabled /active and Rlink is conect/active .... below are the details :--> -> vxprint -Pl Disk group: ossdg Rlink: to_sec_site_ossrvg info: timeout=500 packet_size=1452 rid=0.113591 latency_high_mark=10000 latency_low_mark=9950 bandwidth_limit=none state: state=ACTIVE synchronous=off latencyprot=off srlprot=autodcm assoc: rvg=ossrvg remote_host=sec_site-ossrvg IP_addr=10.52.214.68 port=4145 remote_dg=ossdg remote_dg_dgid=1444153050.96.secmas1o remote_rvg_version=30 remote_rlink=to_prisite_ossrvg remote_rlink_rid=0.1263 local_host=prisite-ossrvg IP_addr=10.52.214.67 port=4145 protocol: UDP/IP flags: write enabled attached consistent connected asynchronous dcm_logging -> vradmin -g ossdg repstatus ossrvg Replicated Data Set: ossrvg Primary: Host name: prisite-ossrvg RVG name: ossrvg DG name: ossdg RVG state: enabled for I/O Data volumes: 20 VSets: 0 SRL name: oss_srl_vol SRL size: 300.00 G Total secondaries: 1 Secondary: Host name: sec_site-ossrvg RVG name: ossrvg DG name: ossdg Data status: consistent, behind Replication status: logging to DCM (needs dcm resynchronization) Current mode: asynchronous Logging to: DCM (contains 61101728 Kbytes) (SRL protection logging) Timestamp Information: N/A -> vxrvg -g ossdg cplist ossrvg Name MBytes % Log Started/Completed ---- ------ ------ ----------------- point1 <Checkpoint overflowed> -> vxrlink -g ossdg status to_sec_site_ossrvg DCM is in use on rlink to_sec_site_ossrvg. DCM contains 61101728 Kbytes (19%) of the Data Volume(s). -> vxrlink -g ossdg stats to_sec_site_ossrvg Messages Errors Flow Control -------- ------ ------------ # Blocks RT(msec) Timeout Stream Memory Delays NW Bytes NW Delay Timeout 1 0 0 0 0 0 0 100000 1 10 primas1o{root} #: vxprint -PV Disk group: ossdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 rl to_sec_site_ossrvg ossrvg CONNECT - - ACTIVE - - rv ossrvg - ENABLED - - ACTIVE - - primas1o{root} #: vxrlink -g ossdg -i 5 status to_sec_site_ossrvg Mon Nov 30 17:24:01 2015 VxVM VVR vxrlink INFO V-5-1-12887 DCM is in use on rlink to_sec_site_ossrvg. DCM contains 61443008 Kbytes (19%) of the Data Volume(s). VxVM VVR vxrlink INFO V-5-1-12887 DCM is in use on rlink to_sec_site_ossrvg. DCM contains 61443008 Kbytes (19%) of the Data Volume(s). VxVM VVR vxrlink INFO V-5-1-12887 DCM is in use on rlink to_sec_site_ossrvg. DCM contains 61443040 Kbytes (19%) of the Data Volume(s). VxVM VVR vxrlink INFO V-5-1-12887 DCM is in use on rlink to_sec_site_ossrvg. DCM contains 61443232 Kbytes (19%) of the Data Volume(s). VxVM VVR vxrlink INFO V-5-1-12887 DCM is in use on rlink to_sec_site_ossrvg. DCM contains 61443232 Kbytes (19%) of the Data Volume(s). VxVM VVR vxrlink INFO V-5-1-12887 DCM is in use on rlink to_sec_site_ossrvg. DCM contains 61443264 Kbytes (19%) of the Data Volume(s). ^Cprimas1o{root} #: ===================================================================================================================== Secondary ======================================================= -> vxprint -Pl Disk group: ossdg Rlink: to_prisite_ossrvg info: timeout=500 packet_size=1452 rid=0.1263 latency_high_mark=10000 latency_low_mark=9950 bandwidth_limit=none state: state=ACTIVE synchronous=off latencyprot=off srlprot=autodcm assoc: rvg=ossrvg remote_host=prisite-ossrvg IP_addr=10.52.214.67 port=4145 remote_dg=ossdg remote_dg_dgid=1327928106.32.secmas1o remote_rvg_version=30 remote_rlink=to_sec_site_ossrvg remote_rlink_rid=0.113591 local_host=sec_site-ossrvg IP_addr=10.52.214.68 port=4145 protocol: UDP/IP flags: write enabled attached consistent connected -> vradmin -g ossdg repstatus ossrvg Replicated Data Set: ossrvg Primary: Host name: prisite-ossrvg RVG name: ossrvg DG name: ossdg RVG state: enabled for I/O Data volumes: 20 VSets: 0 SRL name: oss_srl_vol SRL size: 300.00 G Total secondaries: 1 Secondary: Host name: sec_site-ossrvg RVG name: ossrvg DG name: ossdg Data status: consistent, behind Replication status: logging to DCM (needs dcm resynchronization) Current mode: asynchronous Logging to: DCM (contains 61442560 Kbytes) (SRL protection logging) Timestamp Information: N/A -> vxrvg -g ossdg cplist ossrvg The cplist command can only be used on a primary rvg -> vxrlink -g ossdg status to_prisite_ossrvg The status command can only be used on a primary rlink -> vxrlink -g ossdg stats to_prisite_ossrvg Messages Errors Flow Control -------- ------ ------------ # Blocks RT(msec) Timeout Stream Memory Delays NW Bytes NW Delay Timeout 334089805 0 0 1927960 0 0 0 100000 1 10 Also, I ran the below command to check rlink bandwidth usgae and it is 0% utilised Cprimas1o{root} #: vrstat -R Mon Nov 30 17:43:49 2015 Replicated Data Set ossrvg: Data Status: sec_site-ossrvg: DCM contains 61543520 Kbytes. Network Statistics: Messages Errors Flow Control -------- ------ ------------ # Blocks RT(msec) Timeout Stream Memory Delays NW Bytes NW Delay Timeout primas1o 1 0 0 0 0 0 0 100000 1 10 Mon Nov 30 17:43:59 2015 Replicated Data Set ossrvg: Data Status: sec_site-ossrvg: DCM contains 61543552 Kbytes. Network Statistics: Messages Errors Flow Control -------- ------ ------------ # Blocks RT(msec) Timeout Stream Memory Delays NW Bytes NW Delay Timeout primas1o 0 0 0 0 0 0 0 100000 1 10 Bandwidth Utilization 0.00 Kbps. I am wondering if rlink in connect/active state then why its not replicating ? Regards SSolved3.3KViews0likes6CommentsHow to re-create RVG
I have mistankly deleted 2 disks that were used as cachevol for secondary RVG and data in secondary become unaccessible, for that i went through deleting the DG and succeeded. now i am trying to create RVG group again, for that i should delete both RVG in main and DR which seems impossible, even dissociate SRL volume from primary RVG seems impossible any hint please? BR,Solved2.3KViews0likes6Comments
When will SRL be played for initial sync using backup/restore
Understood all the points in https://www-secure.symantec.com/connect/forums/clustering-one-physical-and-one-virtual-node-gco but the resync using backup/restore is still confusing. """"When using checkpoints, you take backup of the data on the Primary and physically ship the backup media to the Secondary location, and restore the backup on the Secondary. When you start the backup, mark the starting point, by using the checkstart operation on the Primary. When you end the backup, mark the ending point by using the checkend operation on the Primary. While the backup and restore are going on, updates are written to the Replicator Log volume. To bring the Secondary data up-to-date, restore the block-level backup. After the restore is complete, start replication to the Secondary with checkpoint using the same checkpoint name that you had specified for the checkstart operation on the Primary. The Secondary can be brought up-to-date only if the updates are still present in the Replicator Log volume. Using checkpoints is a multi-step process and therefore, needs to be done very carefully."""""" When will the replicator log will be played? Also once the logs have been committed will the pair notify us about those logs being played?Solved1.4KViews0likes2Commentsneed to fix vvr replication
Earlier node 1 was primary and node2 was secondary Node1 crashed and node 2 become primary. Now, we have brought node1 up as below and below is the status of rlink Please provide fix root@node1:# vradmin -g ossdg -l repstatus ossrvg Replicated Data Set: ossrvg Primary: Host name: punjab_core-ossrvg RVG name: ossrvg DG name: ossdg RVG state: enabled for I/O Data volumes: 24 VSets: 0 SRL name: oss_srl_vol SRL size: 400.00 G Total secondaries: 1 Config Errors: delhi_core-ossrvg: Primary-Primary configuration root@node1:# vxprint -PV Disk group: ossdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 rl to_delhi_core_ossrvg ossrvg ENABLED - - PAUSE - - rv ossrvg - ENABLED - - ACTIVE - - root@node1:/ericsson/hagcs/etc# vxprint -Pl Disk group: ossdg Rlink: to_delhi_core_ossrvg info: timeout=500 packet_size=1452 rid=0.1329 latency_high_mark=10000 latency_low_mark=9950 bandwidth_limit=none state: state=PAUSE synchronous=off latencyprot=off srlprot=override assoc: rvg=ossrvg remote_host=delhi_core-ossrvg IP_addr=10.161.21.197 port=4145 remote_dg=ossdg remote_dg_dgid=1374151282.15.node1 remote_rvg_version=30 remote_rlink=to_punjab_core_ossrvg remote_rlink_rid=0.7142 local_host=punjab_core-ossrvg IP_addr=10.161.54.197 port=4145 protocol: UDP/IP flags: write enabled attached primary_paused consistent disconnected asynchronous root@node1:/ericsson/hagcs/etc# ========================================= root@node2:/ericsson/hagcs/etc# vradmin -g ossdg -l repstatus ossrvg Replicated Data Set: ossrvg Primary: Host name: delhi_core-ossrvg RVG name: ossrvg DG name: ossdg RVG state: enabled for I/O Data volumes: 24 VSets: 0 SRL name: oss_srl_vol SRL size: 400.00 G Total secondaries: 1 Config Errors: punjab_core-ossrvg: Primary-Primary configuration root@node2:/ericsson/hagcs/etc# vxprint -PV Disk group: ossdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 rl to_punjab_core_ossrvg ossrvg ENABLED - - ACTIVE - - rv ossrvg - ENABLED - - ACTIVE - - root@node2:/ericsson/hagcs/etc# vxprint -Pl Disk group: ossdg Rlink: to_punjab_core_ossrvg info: timeout=500 packet_size=1452 rid=0.7142 latency_high_mark=10000 latency_low_mark=9950 bandwidth_limit=none state: state=ACTIVE synchronous=off latencyprot=off srlprot=autodcm assoc: rvg=ossrvg remote_host=punjab_core-ossrvg IP_addr=10.161.54.197 port=4145 remote_dg=ossdg remote_dg_dgid=1384451046.29.node2 remote_rvg_version=30 remote_rlink=to_delhi_core_ossrvg remote_rlink_rid=0.1329 local_host=delhi_core-ossrvg IP_addr=10.161.21.197 port=4145 protocol: UDP/IP checkpoint: point1 flags: write enabled attached consistent disconnected asynchronous dcm_logging resync_started root@node2:/ericsson/hagcs/etc# Please provide me fixSolved2.9KViews1like6Comments
VVR has 2 primaries
I have successfully installed NBU on both nodes. Thanks for the help everyone. The only outstanding issue I now have is with the replication. If this needs to be a new post in a different section let me know! I have run the Volume Replicator Agent Configuration wizard successfully and my initial testing of failing between nodes went perfectly. However, at some point during the testing both nodes have ended up thinking that they are the primary in the GUI and I cannot see the secondaries listed, although everything looks correct in VCS and I can still bring everything online on each side with no errors. Something clearly isn't right with it though. I have tried deleting the RDS in the GUI and using commands to create it again, but it seems to be somewhat stuck and I can't seem to remove it or change anything now! Here's the output on what should be the primary node: C:\>vradmin -g NBUCATDG takeover nbuRVG Error occurred on host HOST1. Error V-106-58644-541: Primary takeover is not supported in present configuratio n. C:\>vradmin -g NBUCATDG stoprep nbuRVG HOST2 Error occurred on host HOST2. Error V-106-58644-528: Cannot complete operation. RDS is incomplete, either prim ary or secondary node is missing. C:\>vradmin -g NBUCATDG delsec nbuRVG HOST2 Error occurred on host HOST1. Error V-106-58644-513: This operation cannot be performed in present state of th e configuration. Please try again. C:\>vradmin -g NBUCATDG -f delpri nbuRVG Failed to perform the operation. Error V-106-58644-698: Operation not allowed. The RVG cluster resource is alread y configured for this RVG. Use -f option to forcefully stop it. C:\>vradmin -g NBUCATDG -f delrds nbuRDS Failed to perform the operation. Error V-107-58644-917: Cannot identify the correct RDS. C:\>vradmin -l printrvg Replicated Data Set : nbuRDS Primary : Hostname : HOST1 <localhost> RvgName : nbuRVG DgName : NBUCATDG Datavol_cnt : 1 Srl : vvrlog Rlinks: Name = rlk_primary ,rlink_state = ACTIVE, synchronous = override UPDATE: After switching back to what should be the secondary node (HOST2) I found that most of the above commands give a different error: "Error V-106-58644-697: Cannot perform this operation on an acting secondary RVG". However in the VEA GUI it is listed as the primary.Solved2.1KViews1like2CommentsCreate second RDS using volumes from same disk group in Veritas volume replicator
Hi all, I have one query. I have one disk group with 5 volumes, which are more than 2 TB and are configured for replication. Now i want to add 2 more volumes in the RDS but it will resync all the volumes after adding these 2 volumes, so is it possible to make second RDS for only those 2 new volumes. Also can we use same IP for replication.5.5KViews0likes8Comments
Creating Parallel Service Group VVR on VCS 6.1
Dear All, I have 2 servers at the Production and 1 server at the DR site. I have 4TB data i want to replicate from Prod to DR using Veritas Volume Replicator. The volume I will need to replicate is a CFS volume mounted on both servers in the Production. What is the best way to replicate this volume? Regards, Thokozani MabasoSolved860Views0likes1Commentvvr primary -primary configuration error
Dear support when i execute vradmin repstatus <rvg> the command reports the configuration error: "Primary-Primary configuration" the data now is on the secondary site and i haven't possibility to switch to the primary site with GCO tools Please your feedback on this situation ThanksSolved3.6KViews1like1Comment
Create second RDS using volumes from same disk group in Veritas volume replicator
Hi all, I have one query. I have one disk group with 5 volumes, which are more than 2 TB and are configured for replication. Now i want to add 2 more volumes in the RDS but it will resync all the volumes after adding these 2 volumes, so is it possible to make second RDS for only those 2 new volumes. Also can we use same IP for replication.