A. Activity Overview 1. drdb syncrinization
B. Prerequisite and Pre-checks:
Steps:1. On servers BD902G and BD901Gpcs status
Server which is running oracle service ora_igt_rg is Active. (Primary)The other server is Passive (Secondary)
2. drbd General Note:Data is written on Active server by oracle service, and synchronized by drbd to Standby server.drbd has its own CLI, drbdadm
Command are run per LV Group (db2, db1, Ora_Exp, Ora_Online). Each Volume sync can take few minutes to complete.drbdadm status during synchronization, will show progress, in percent.drbdadm commands should be run as root.drbdadm commads are run either on Active (Primary), or on Passive (Secondary) node, per context, see below.
3. Check status before starting synchronizationRun drbdadm status on Active server
Expected result:connection:StandAlone – meaning there is no sync with the Secondary node
root>% drbdadm statusOra_Exp role:Primary disk:UpToDate DBD902G connection:StandAloneOra_Online role:Primary disk:UpToDate DBD902G connection:StandAlonedb1 role:Primary disk:UpToDate DBD902G connection:StandAlonedb2 role:Primary disk:UpToDate DBD902G connection:StandAlone
4. Synchronization commands.Yellow: commands on secondary siteGreen: commands on primary site
drbdadm statusdrbdadm status
drbdadm secondary Ora_Expdrbdadm disconnect Ora_Expdrbdadm -- --discard-my-data connect Ora_Exp// per another documentation, use this:
//drbdadm connect --discard-my-data Ora_Expdrbdadm connect Ora_Expdrbdadm status drbdadm secondary Ora_Onlinedrbdadm disconnect Ora_Onlinedrbdadm -- --discard-my-data connect Ora_Onlinedrbdadm connect Ora_Onlinedrbdadm status
drbdadm secondary db1drbdadm disconnect db1drbdadm -- --discard-my-data connect db1drbdadm connect db1drbdadm status
drbdadm secondary db2drbdadm disconnect db2drbdadm -- --discard-my-data connect db2drbdadm connect db2drbdadm status drbdadm statusdrbdadm status
1.After synchronization check statusNow, Primary node is aware of secondary nodeSecondary node is aware on Primary node.In this example:DBD901G - is PrimaryDBD902G - is Secondary
root@DBD901G:~>% drbdadm statusOra_Exp role:Primary disk:UpToDate SRV902G role:Secondary peer-disk:UpToDate
Ora_Online role:Primary disk:UpToDate SRV902G role:Secondary peer-disk:UpToDate
db1 role:Primary disk:UpToDate SRV902G role:Secondary peer-disk:UpToDate
db2 role:Primary disk:UpToDate SRV902G role:Secondary peer-disk:UpToDate
root@DBD902G:~>% drbdadm statusOra_Exp role:Secondary disk:UpToDate DBD901G role:Primary peer-disk:UpToDate
Ora_Online role:Secondary disk:UpToDate DBD901G role:Primary peer-disk:UpToDate
db1 role:Secondary disk:UpToDate DBD901G role:Primary peer-disk:UpToDate
db2 role:Secondary disk:UpToDate DBD901G role:Primary peer-disk:UpToDate
completed!!
Additional commandsdrbdadm verify <resource>drbdadm verify all- used for monitoring
drbdadm primary <resource>drbdadm secondary <resource>- set resource as Primary or Secondary
drbdsetup status home- get status for current node
drbdsetup status home --verbose --statisticsordrbdsetup status --verbose --statistics- get detailed status for current node
drbdsetup events2 --now r0- Get current stats
drbdsetup events2 r0- Get constant stats, updating each second
drbdsetup events2 --statistics --now r0- Get current stats, with details
drbdadm cstatedrbdadm cstate <resource>:<peer>- Get the node state
- <resource>:<peer> - The default is the peer’s hostname as given in the configuration file.
A resource may have one of the following connection states:
StandAloneNo network configuration available. The resource has not yet been connected, or has been administratively disconnected (using drbdadm disconnect), or has dropped its connection due to failed authentication or split brain.
DisconnectingTemporary state during disconnection. The next state is StandAlone.
UnconnectedTemporary state, prior to a connection attempt. Possible next states: Connecting.
TimeoutTemporary state following a timeout in the communication with the peer. Next state: Unconnected.
BrokenPipeTemporary state after the connection to the peer was lost. Next state: Unconnected.
NetworkFailureTemporary state after the connection to the partner was lost. Next state: Unconnected.
ProtocolErrorTemporary state after the connection to the partner was lost. Next state: Unconnected.
TearDownTemporary state. The peer is closing the connection. Next state: Unconnected.
ConnectingThis node is waiting until the peer node becomes visible on the network.
ConnectedA DRBD connection has been established, data mirroring is now active. This is the normal state.
drbdadm roleResource RolesYou may see one of the following resource roles:
PrimaryThe resource is currently in the primary role, and may be read from and written to. This role only occurs on one of the two nodes, unless dual-primary mode is enabled.
SecondaryThe resource is currently in the secondary role. It normally receives updates from its peer (unless running in disconnected mode), but may neither be read from nor written to. This role may occur on one or both nodes.
UnknownThe resource’s role is currently unknown. The local resource role never has this status. It is only displayed for the peer’s resource role, and only in disconnected mode
drbdadm dstate <resource>Get the Disk State
The disk state may be one of the following:
DisklessNo local block device has been assigned to the DRBD driver. This may mean that the resource has never attached to its backing device, that it has been manually detached using drbdadm detach, or that it automatically detached after a lower-level I/O error.
AttachingTransient state while reading metadata.
DetachingTransient state while detaching and waiting for ongoing I/O operations to complete.
FailedTransient state following an I/O failure report by the local block device. Next state: Diskless.
NegotiatingTransient state when an Attach is carried out on an already-Connected DRBD device.
InconsistentThe data is inconsistent. This status occurs immediately upon creation of a new resource, on both nodes (before the initial full sync). Also, this status is found in one node (the synchronization target) during synchronization.
OutdatedResource data is consistent, but outdated.
DUnknownThis state is used for the peer disk if no network connection is available.
ConsistentConsistent data of a node without connection. When the connection is established, it is decided whether the data is UpToDate or Outdated.
UpToDateConsistent, up-to-date state of the data.
This is the normal state.
A. Activity Overview
1. drdb syncrinization
B. Prerequisite and Pre-checks:
Steps:
1. On servers BD902G and BD901G
pcs status
Server which is running oracle service ora_igt_rg is Active. (Primary)
The other server is Passive (Secondary)
2. drbd General Note:
Data is written on Active server by oracle service, and synchronized by drbd to Standby server.
drbd has its own CLI, drbdadm
Command are run per LV Group (db2, db1, Ora_Exp, Ora_Online). Each Volume sync can take few minutes to complete.
drbdadm status during synchronization, will show progress, in percent.
drbdadm commands should be run as root.
drbdadm commads are run either on Active (Primary), or on Passive (Secondary) node, per context, see below.
3. Check status before starting synchronization
Run drbdadm status on Active server
Expected result:
connection:StandAlone – meaning there is no sync with the Secondary node
root>% drbdadm status
Ora_Exp role:Primary
disk:UpToDate
DBD902G connection:StandAlone
Ora_Online role:Primary
disk:UpToDate
DBD902G connection:StandAlone
db1 role:Primary
disk:UpToDate
DBD902G connection:StandAlone
db2 role:Primary
disk:UpToDate
DBD902G connection:StandAlone
4. Synchronization commands.
Yellow: commands on secondary site
Green: commands on primary site
drbdadm status
drbdadm status
drbdadm secondary Ora_Exp
drbdadm disconnect Ora_Exp
drbdadm -- --discard-my-data connect Ora_Exp
// per another documentation, use this:
//drbdadm connect --discard-my-data Ora_Exp
//drbdadm connect --discard-my-data Ora_Exp
drbdadm connect Ora_Exp
drbdadm status
drbdadm secondary Ora_Online
drbdadm disconnect Ora_Online
drbdadm -- --discard-my-data connect Ora_Online
drbdadm connect Ora_Online
drbdadm status
drbdadm secondary db1
drbdadm disconnect db1
drbdadm -- --discard-my-data connect db1
drbdadm connect db1
drbdadm status
drbdadm secondary db2
drbdadm disconnect db2
drbdadm -- --discard-my-data connect db2
drbdadm connect db2
drbdadm status
drbdadm status
drbdadm status
1.After synchronization check status
Now, Primary node is aware of secondary node
Secondary node is aware on Primary node.
In this example:
DBD901G - is Primary
DBD902G - is Secondary
root@DBD901G:~>% drbdadm status
Ora_Exp role:Primary
disk:UpToDate
SRV902G role:Secondary
peer-disk:UpToDate
Ora_Online role:Primary
disk:UpToDate
SRV902G role:Secondary
peer-disk:UpToDate
db1 role:Primary
disk:UpToDate
SRV902G role:Secondary
peer-disk:UpToDate
db2 role:Primary
disk:UpToDate
SRV902G role:Secondary
peer-disk:UpToDate
root@DBD902G:~>% drbdadm status
Ora_Exp role:Secondary
disk:UpToDate
DBD901G role:Primary
peer-disk:UpToDate
Ora_Online role:Secondary
disk:UpToDate
DBD901G role:Primary
peer-disk:UpToDate
db1 role:Secondary
disk:UpToDate
DBD901G role:Primary
peer-disk:UpToDate
db2 role:Secondary
disk:UpToDate
DBD901G role:Primary
peer-disk:UpToDate
completed!!
Additional commands
drbdadm verify <resource>
drbdadm verify all
- used for monitoring
drbdadm primary <resource>
drbdadm secondary <resource>
- set resource as Primary or Secondary
drbdsetup status home
- get status for current node
drbdsetup status home --verbose --statistics
or
drbdsetup status --verbose --statistics
- get detailed status for current node
drbdsetup events2 --now r0
- Get current stats
drbdsetup events2 r0
- Get constant stats, updating each second
drbdsetup events2 --statistics --now r0
- Get current stats, with details
drbdadm cstate
drbdadm cstate <resource>:<peer>
- Get the node state
- <resource>:<peer> - The default is the peer’s hostname as given in the configuration file.
- <resource>:<peer> - The default is the peer’s hostname as given in the configuration file.
A resource may have one of the following connection states:
StandAlone
No network configuration available.
The resource has not yet been connected, or has been administratively disconnected (using drbdadm disconnect), or has dropped its connection due to failed authentication or split brain.
Disconnecting
Temporary state during disconnection. The next state is StandAlone.
Unconnected
Temporary state, prior to a connection attempt. Possible next states: Connecting.
Timeout
Temporary state following a timeout in the communication with the peer. Next state: Unconnected.
BrokenPipe
Temporary state after the connection to the peer was lost. Next state: Unconnected.
NetworkFailure
Temporary state after the connection to the partner was lost. Next state: Unconnected.
ProtocolError
Temporary state after the connection to the partner was lost. Next state: Unconnected.
TearDown
Temporary state. The peer is closing the connection. Next state: Unconnected.
Connecting
This node is waiting until the peer node becomes visible on the network.
Connected
A DRBD connection has been established, data mirroring is now active. This is the normal state.
drbdadm role
Resource Roles
You may see one of the following resource roles:
Primary
The resource is currently in the primary role, and may be read from and written to.
This role only occurs on one of the two nodes, unless dual-primary mode is enabled.
Secondary
The resource is currently in the secondary role.
It normally receives updates from its peer (unless running in disconnected mode), but may neither be read from nor written to.
This role may occur on one or both nodes.
Unknown
The resource’s role is currently unknown.
The local resource role never has this status.
It is only displayed for the peer’s resource role, and only in disconnected mode
drbdadm dstate <resource>
Get the Disk State
The disk state may be one of the following:
Diskless
No local block device has been assigned to the DRBD driver. This may mean that the resource has never attached to its backing device, that it has been manually detached using drbdadm detach, or that it automatically detached after a lower-level I/O error.
Attaching
Transient state while reading metadata.
Detaching
Transient state while detaching and waiting for ongoing I/O operations to complete.
Failed
Transient state following an I/O failure report by the local block device. Next state: Diskless.
Negotiating
Transient state when an Attach is carried out on an already-Connected DRBD device.
Inconsistent
The data is inconsistent. This status occurs immediately upon creation of a new resource, on both nodes (before the initial full sync). Also, this status is found in one node (the synchronization target) during synchronization.
Outdated
Resource data is consistent, but outdated.
DUnknown
This state is used for the peer disk if no network connection is available.
Consistent
Consistent data of a node without connection. When the connection is established, it is decided whether the data is UpToDate or Outdated.
UpToDate
Consistent, up-to-date state of the data.
This is the normal state.
This is the normal state.
No comments:
Post a Comment