|
If your SERVERware is restarted for some reason, there is a list of needed steps that you need to perform in order to have SERVERware up and working correctly:
1. Log in to the primary controller (controller1) and check that DRBD is started. If it shows a status other than 'stopped', then it is already running and everything is working fine. If it is stopped, execute: /etc/init.d/drbd start
2. Repeat step 1 for the secondary controller (controller2)
3. On the first controller (controller1) check the DRDB status with the following commands:
/etc/init.d/drbd status
# cat /proc/drbd
version: 0.7.17 (api:77/proto:74)
SVN Revision: 2093 build by tester@test1, 20060327 12:41:17
0: cs:SyncSource st:Primary/Secondary ld:Consistent
ns:122084 nr:0 dw:662016 dr:782689 al:165 bm:174 lo:19 pe:67 ua:82 ap:0
[===>................] sync'ed: 19.2% (540188/662008)K
finish: 0:01:45 speed: 5,080 (4,872) K/sec
If you get the above output, everything is working as it should. Synchronization is in process and you will have to wait until it is finished.
But, if you get the following output:
version: 0.7.17 (api:77/proto:74)
SVN Revision: 2093 build by tester@test1, 20060327 12:41:17
0: cs:SyncSource st:Secondary/Secondary ld:Consistent
you will need to execute the following command:
# drbdadm -- --do-what-I-say primary all
and after that, please check the status of DRBD again to see if it is syncing.
4. Start heartbeat on the primary controller (controller1):
# /etc/init.d/heartbeat start
Wait about 3 minutes for the heartbeat to initialize virtual ip, mounts DRBD partition, and start SERVERware.
5. Go to the secondary controller2 and start the heartbeat there too.
After those steps are executed your SERVERware should work fine.
|
