Shulou(Shulou.com)06/02 Report--

1 / / status view [root@chy database] # drbd-overview NOTE: drbd-overview will be deprecated soon.Please consider using drbdtop. 0:r0/0 Connected Primary/Secondary UpToDate/UpToDate / database ext4 93M 1.6m 85m 2% [root@chy database] # cat / proc/drbdversion: 8.4.10-1 (api:1/proto:86-101) GIT-hash: a4d5de01fffd7e4cde48a080e2c686f9e8cebf4c build by mockbuild@ 2017-09-15 14:23:22 0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-ns:6 nr:24 dw:30 dr:1385 al:2 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0cs: connect state ro: indicates role information ds: disk status information Inconsistent/UpToDatens/nr: data packets sent / received by the network dw/dr: device read and write Information [root@chy database] # drbdadm cstate R0 / / connection status of the resource (R0 is the resource) WARN: You are using the 'drbd-peer-outdater' as fence-peer program. If you use that mechanism the dopd heartbeat plugin program needs to be able to call drbdsetup and drbdmeta with root privileges. You need to fix this with these commands: chgrp haclient / lib/drbd/drbdsetup-84 chmod Omurx / lib/drbd/drbdsetup-84 chmod UBSs / lib/drbd/drbdsetup-84 chgrp haclient / usr/sbin/drbdmeta chmod Omurx / usr/sbin/drbdmeta chmod UBSs / usr/sbin/drbdmetaConnected resource connection status; a resource may have one of the following connection states: StandAlone independent: network configuration is not available The resource has not been connected or disconnected by management (using the drbdadm disconnect command), or Disconnecting is disconnected due to authentication failure or brain fissure: disconnect is only a temporary state, and the next state is StandAlone independent Unconnected suspended: it is a temporary state before trying to connect, and the next state may be WFconnection and WFReportParams Timeout timeout: connection timeout with peer node, also temporary state The next state is Unconected suspended BrokerPipe: the connection with the peer node is lost, which is also temporary, the next state is Unconected suspended NetworkFailure: the temporary state after promoting the connection with the peer node, the next state is Unconected suspended ProtocolError: the temporary state after promoting the connection with the peer node, and the next state is Unconected suspended TearDown disassembly: temporary state, peer node shutdown The next state is Unconected suspended WFConnection: waiting to establish a network connection with peer node WFReportParams: TCP connection has been established, this node is waiting for the first network packet Connected connection from peer node: DRBD has established connection, data mirror is now available, node is in normal state StartingSyncS: full synchronization, synchronization initiated by administrator has just begun, possible future status is SyncSource or PausedSyncS StartingSyncT: full synchronization Synchronization initiated by an administrator has just started, and the next status is WFSyncUUID WFBitMapS: partial synchronization has just started, and the next possible status is SyncSource or PausedSyncS WFBitMapT: partial synchronization has just started, and the next possible status is WFSyncUUID WFSyncUUID: synchronization is about to begin. The next possible state is SyncTarget or PausedSyncT SyncSource: synchronization with this node as synchronization source is in progress SyncTarget: synchronization with this node as synchronization target is in progress PausedSyncS: local node is a source of continuous synchronization, but synchronization has been paused at present, probably because another synchronization is in progress or synchronization is paused with command (drbdadm pause-sync) PausedSyncT: local node as the target of continuous synchronization But synchronization has been paused, which may be because another synchronization is in progress or the synchronization VerifyS is suspended using the command (drbdadm pause-sync): online device verification with the local node as the verification source is performing VerifyT: online device verification with the local node as the verification target is performing 2 resource roles [root@chy database] # drbdadm role r0Primary/SecondaryParimary Master: the resource is currently primary and may be being read or written If not, the Secondary will only appear on one of the two nodes: the resource is currently secondary, and the update Unknown of the normal receiving peer node is unknown: the resource role is currently unknown. Local resources do not appear in this state. 3 hard disk status [root@chy database] # drbdadm dstate R0 / / R0 Resources UpToDate/UpToDate Local and peer nodes' hard drives may be in one of the following states: Diskless has no disk: no local block devices are allocated for DRBD use, which means that no devices are available Or use the drbdadm command to manually detach or the underlying I Negotiating O error causes automatic detach Attaching: failed to read the instantaneous status Failed when there is no data: the local parcel device reports the next state of the Diskless O error, and its next state is Diskless diskless Inconsistent: instant state before connected DRBD setting for Attach read no data Inconsistent: data is inconsistent A new resource is created immediately after this state occurs on both nodes (before the initial full synchronization). In addition, this state occurs on a node during synchronization (synchronization target) Outdated: data resources are consistent, but obsolete DUnknown: this state occurs when a peer node network connection is not available Consistent: a node without a connection is consistent in data, and when a connection is established, it determines whether the data is UpToDate or Outdated UpToDate: consistent up-to-date data state, which is normal state 4 enable / upgrade resources

Manually enable resources

Manually enable resources

Drbdadm up

Manually disable resources

Drbdadm down

Resource: resource name; of course, you can also use all to indicate [deactivate | enable] all resources.

Upgrade and downgrade resources

Upgrade Resourc

Drbdadm primary

Downgrade resources

Drbdadm secondary

Note: in DRBD in single master mode, two nodes are connected at the same time, and any node can become master within a specific time; but only one of the two nodes can be primary. If there is already one master, you need to downgrade before upgrading. There is no such restriction in dual master mode.

5 initialize device synchronization

Select an initial synchronization source; if it is newly initialized or empty, this choice can be arbitrary, but if one of the nodes is already in use and contains useful data, it is important to select the synchronization source; if you choose the wrong initialization synchronization direction, it will result in data loss, so you need to be very careful.

Initialize full synchronization, which can only be done on one node that initializes the resource configuration, and on the node selected as the synchronization source

[root@chy database] # drbdadm-overwrite-data-of-peer primary R0 / / R0 is a resource

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.