dcm resynchronization does not start automatically
Hi all: I am testing the vcs/vvr cluster . When I write a data which size exceeds the srl volume size, VVR goes to "logging to dcm" state. # vradmin -g data_dg -l repstatus rvg_b Replicated Data Set: rvg_b Primary: Host name: 192.168.100.111 RVG name: rvg_b DG name: data_dg RVG state: enabled for I/O Data volumes: 1 VSets: 0 SRL name: srl_b SRL size: 150.00 M Total secondaries: 1 Secondary: Host name: 192.168.100.112 RVG name: rvg_b DG name: data_dg Rlink from Primary: rlk_192.168.100.112_rvg_b Rlink to Primary: rlk_192.168.100.111_rvg_b Configured mode: asynchronous Latency protection: off SRL protection: autodcm Data status: consistent, behind Replication status: logging to DCM (needs dcm resynchronization) Current mode: asynchronous Logging to: DCM (contains 5572672 Kbytes) (SRL protection logging) Timestamp Information: N/A Bandwidth Limit: 100.00 Mbps Compression Mode: On After writing, the vvr keeps in "needs dcm resync" status and the resynchronization does not start automatically. What should I set to let the resync start auto? Btw:another question. If a new write operation on block operation coming in when the block is in dcm resync state, is the write action blocked or not?diskgroup does not start on secondary host
HI All: I configure a single vcs cluster with vvr. I save the configuration on the following pictures As you see on these pictures, I configure a service named apache2 using the RVGPrimary of vvrgroup, and set the relation between two service groups with command: >hagrp -link apache2 vvrgrp online local hard All the service group and resource take online successfully. But on the secondary node of VVR, the disk group is exported and the replication does not occur. vcs2:/var/VRTSvcs/log # vradmin -g data_dg repstatus rvg_b Replicated Data Set: rvg_b Primary: Host name: 192.168.100.112 RVG name: rvg_b DG name: data_dg RVG state: enabled for I/O Data volumes: 1 VSets: 0 SRL name: srl_b SRL size: 1.00 G Total secondaries: 1 Config Errors: 192.168.100.111: disk group missing Is there anything wrong in my configuration ? >cat main.cf include "OracleASMTypes.cf" include "types.cf" include "Db2udbTypes.cf" include "OracleTypes.cf" include "SybaseTypes.cf" cluster vcs ( UserNames = { admin = aHGcEBdBGeFBgJHbHFgGIg } ClusterAddress = "192.168.4.100" Administrators = { admin } ) system vcs1 ( ) system vcs2 ( ) group ClusterService ( SystemList = { vcs1 = 0, vcs2 = 1 } AutoStartList = { vcs1, vcs2 } OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) IP webip ( Device = eth0 Address = "192.168.4.100" NetMask = "255.255.255.0" ) NIC csgnic ( Device = eth0 ) webip requires csgnic // resource dependency tree // // group ClusterService // { // IP webip // { // NIC csgnic // } // } group apache2 ( SystemList = { vcs1 = 0, vcs2 = 1 } ) Application httpd2 ( StartProgram = "/etc/init.d/apache2 start" StopProgram = "/etc/init.d/apache2 stop" PidFiles = { "/var/run/httpd2.pid" } ) IP ip_res ( Device = eth0 Address = "192.168.4.200" NetMask = "255.255.255.0" ) Mount appmount ( MountPoint = "/srv/www/htdocs" BlockDevice = "/dev/vx/dsk/data_dg/data_volume" FSType = vxfs FsckOpt = "-n" ) RVGPrimary DataRVG_pri ( RvgResourceName = DataRVG ) requires group vvrgrp online local hard appmount requires DataRVG_pri httpd2 requires appmount httpd2 requires ip_res // resource dependency tree // // group apache2 // { // Application httpd2 // { // IP ip_res // Mount appmount // { // RVGPrimary DataRVG_pri // } // } // } group vvrgrp ( SystemList = { vcs1 = 0, vcs2 = 1 } AutoStartList = { vcs1, vcs2 } ) DiskGroup DataDG ( DiskGroup = data_dg ) NIC vvrnic ( Device = eth1 ) RVG DataRVG ( RVG = rvg_b DiskGroup = data_dg ) DataRVG requires DataDG DataRVG requires vvrnic // resource dependency tree // // group vvrgrp // { // RVG DataRVG // { // DiskGroup DataDG // NIC vvrnic // } // }
Migrating VVR to different Linux platform
Hi Folks, My company is switching Linux vendor and I need to help migrating some VVR setup from SuSE Linux Server 9 to RedHat Enterprise Linux 5, to make things even more complicated, we would want to upgrade the SF from 4.1 to 5 altogether. I am looking for the safest way to handle this, I care the most is the data and a way to reliably fall back if something wrong happen. I am thinking to make the RedHat server a secondary VVR node first and then promote it to primary. Not sure this is workable and is the best way, any input or suggestions will be welcome. Thanks, Tom