![]() Resync paused due to network disconnection Resynchronization to Secondary is paused because of the following errors: Resynchronization to Secondary is paused because of some administrative action. Smartsync - Resynchronization type is autosync using SmartMove. Resynchronization to the Secondary is in progress.Īutosync - Resynchronization type is autosync.ĭcm resynchronization - Resynchronization after an SRL overflow.įailback resynchronization - Resynchronization using failback logging. Replication to Secondary is paused because of some network problem.Ĭonnected - Replication can take place if there are updates on the Primary data volumes Secondary log error - Secondary SRL has an I/O error. Secondary config error - Secondary has some configuration error. Replication to Secondary is paused because of the following errors: Secondary paused - Secondary RLINK is paused. Primary paused - Primary RLINK is paused. Replication to Secondary is paused because of some administrative action. Primary needs_recovery - Primary RLINK in needs_recovery state and needs to be recovered before replication can resume. To continue replication, start failback resynchronization on the new Primary.ĭata is not being replicated to Secondary because Primary RLINK is in needs_recovery state. This Primary RVG is acting as Secondary as part of the fast failback process. See Failing back using fast failback synchronization. Needs failback synchronization - To continue replication, start failback synchronization to this Secondary. See Incrementally synchronizing the Secondary after SRL overflow. Needs dcm resynchronization - To continue replication, resynchronize the Secondary using DCM resynchronization. The following information may be displayed: The following table lists the values for the Replication status field and their meanings:ĭCM is active for this Secondary, that is, new updates on Primary are tracked using DCM for this Secondary. Replication status: Displays the status of the replication to the Secondary. See Changing the replication settings for a Secondary. This value can be different from the configured replication setting if the configured mode is synchronous=override. For information about the state, use the vxprint -l rlink_name command on the Primary and Secondary.Ĭurrent mode: Displays the mode of replication, asynchronous or synchronous, that is being used to replicate data to the Secondary. This may occur because of a configuration error on this Secondary. The vxrlink recover command clears this state.Ĭurrent state of the Secondary data cannot be determined. The data on the Secondary volumes is not consistent and the Secondary cannot take over. The Primary role can be migrated to this Secondary. The Secondary data is consistent and is current or up-to-date with the Primary data. Replication to this Secondary has been stopped the Primary RLINK is detached. The data on this Secondary is consistent. Secondary data is consistent but not up-to-date with the Primary data. Seattle: Pri or Sec IP not available or vradmind not running, Secondary up-to-date as of: Oct 10 04:32:21 Timestamp Information: behind by 00:00:00 hours ![]() Logging to: SRL (0 updates behind, last update ID 18533.0) Replication status: replicating (connected) Displayed status information is from Secondary and can be out-of-date. Output resembles: VxVM VVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has configurationĮrror. When the Primary is unreachable from the Secondary hosts and the vradmin repstatus command is run from the Secondary host: # vradmin -g hrdg -l repstatus hr_rvg Logging to: DCM (contains 169728 Kbytes) (autosync) Replication status: resync in progress (smartsync autosync) ![]() Output resembles: Replicated Data Set: hr_rvg When the Primary is reachable from all the Secondary hosts and the vradmin repstatus command is run from any host: # vradmin -g hrdg -l repstatus hr_rvg If the vradmin repstatus command is run on a Secondary that has a few configuration errors or cannot reach the Primary, the output displays the status known to the Secondary before the above condition occurred and therefore might be out of date. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |