Versions Compared

Old Version 40

changes.mady.by.user jtel Support

Saved on

compared with

New Version Current

changes.mady.by.user jtel Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Dependencies

All services of the platform are dependent on two central entities:

  • The Storage(s)
  • The Database(s)

To boot the solution, the storage should always be booted first. If this is external to the solution, continue with the next step. Otherwise, the computer (or in case of redundancy - both computers) is started on which the storage is located. This is usually the load balancer, but for larger systems a separate storage machine could have been implemented. Afterwards, the master database is booted. As soon as its is finished, the slave can be started up. Finally, the telephony servers and web servers can be started up in any order, even simultaneously.

Small

Small V1

Small V2

Small V3

Shutdown for Small, Medium and Large systems

Small V1

First shutdown acd-tel. You do not have to wait until acd-tel is down before starting the shutdown at acd-store/lb/dbm/dbs/dbr/jb.

Small V2

First shutdown acd-tel. You do not have to wait until acd-tel is down before starting the shutdown at acd-dbm/dbs/dbr. Wait for acd-dbm/dbs/dbr to shutdown before starting the shutdown on acd-store/lb/jb.

Small V3

First shutdown acd-tel and acd-jbN in no particular order. You do not have to wait until acd-tel and acd-jbN are down before starting the shutdown at acd-dbm/dbs/dbr. Wait for acd-dbm/dbs/dbr to be shutdown before starting the shutdown on acd-store/lb.

Medium V1

First shutdown acd-tel and acd-jbN in no particular order. You do not have to wait until acd-tel and acd-jbN are down before starting the shutdown at acd-dbs/dbr. Wait until acd-dbs/dbr is shutdown before starting the shutdown on acd-dbm. Wait until acd-dbm is shutdown before starting the shutdown on acd-store/lb.

Medium V2

First shutdown acd-tel and acd-jbN in no particular order. You do not have to wait until acd-tel and acd-jbN are down before starting the shutdown at acd-dbs/dbr. Wait until acd-dbs/dbr is shutdown before starting the shutdown on acd-dbm. Wait until acd-dbm is shutdown before starting the shutdown on acd-lb. Wait until acd-lb is down before starting the shutdown on acd-store

Large V1

When shutting down a redundant database architecture, the inactive machines are shutdown first. Therefore, before a shutdown procedure can begin, the active machines must be known. The table at Large V1 assumes that acd-dbm2 is currently the active master database and displays the shutdown procedure according to that.

Large V2

When shutting down a redundant load balancing architecture, the inactive machines are shutdown first. Therefore, before a shutdown procedure can begin, the active machines must be known. The table at Large V2 assumes that acd-lb2 is currently the active load balancer and displays the shutdown procedure according to that.

Large V3

When shutting down a redundant storage architecture, the inactive machine is shutdown first. Therefore, before a shutdown procedure can begin, the active machine must be known. The table at Large V3 assumes that acd-store2 is currently the active storage and displays the shutdown procedure according to that.

Large

Redundancy - Controlled Failovers

If you wish to shutdown only one side of your redundant jtel cluster, the following child page provides a guide for this procedure  Shutdown/Startup Procedure - Redundancy - Controlled Failover and Failback

This procedure is useful for cases where one of your VM-Hosts must be shutdown, but your jtel ACD is required to maintain service during this time. 

jtel System Dependencies

All services of the platform are dependent on two central entities:

  • The Storage(s)
  • The Database(s)

To boot the solution, the storage should always be booted first. If this is external to the solution, continue with the next step. Otherwise, the computer (or in case of redundancy - both computers) is started on which the storage is located. This is usually the load balancer, but for larger systems a separate storage machine could have been implemented. Afterwards, the master database is booted. As soon as its is finished, the slave can be started up. Finally, the telephony servers and web servers can be started up in any order, even simultaneously.

Redundant Systems

Shutting down redundant clusters is generally easier than starting them back up. If problems occur after starting back up, some components must be checked:

Medium

Medium V1

Medium V2

Startup for Small, Medium and Large systems

Small V1

The two computers must be started in the correct order. Wait until acd-store/lb/dbm/dbs/dbr/jb is up before starting acd-tel.

Small V2

First start acd-store/lb/jb and wait until it is up. Start acd-dbm/dbs/dbr and wait until it is up. Start acd-tel afterwards.

Small V3

First start acd-store/lb and wait until it is up. Start acd-dbm/dbs/dbr and wait until it is up. Start acd-jbN and acd-tel afterwards in no particular order.

Medium V1

First start acd-store/lb and wait until it is up. Start acd-dbm and wait until it is up. Start acd-dbs/dbr and check the MySQL replication status after it is up. Start acd-jbN and acd-tel afterwards in no particular order.

Medium V2

First start acd-store and wait until it is up. Start acd-lb and wait until it is up. Start acd-dbm and wait until it is up. Start acd-dbs/dbr and check the MySQL replication status after it is up. Start acd-jbN and acd-tel afterwards in no particular order.

Large V1

First start acd-store and wait until it is up. Start acd-lb and wait until it is up. Start acd-dbm and wait until it is up. Start acd-dbs/dbr and check the MySQL replication status after it is up. Start acd-jbN and acd-tel afterwards in no particular order.

Large V2

Large V3

When starting a Small or Medium system, 

  1. Storage (Separates Storage acd-store or Load-Balancer acd-lb). 

    Wait until Storage is up.

  2. With separate storage, now start the load balancer acd-lb.

    There is no need to wait here.

  3.  acd-dbm - Database Master .

    Wait until DB-Master is up.

  4.  acd-dbs -  Database Slave- .

    Wait until DB slave is up.

  5. Boot acd-jb1 ... acd-jb(x) aswell as acd-tel1 ... acd-tel(x)

Checks

  1. Log on to the Web via the load balancer. 

    1. Log on OK?

      If Not, check /home/jtel/jboss-(version)/standalone/log/server.log

    2. ESSENTIAL: Logo visible in the web application?

      If not, the storage is not up. Check with mount on the web servers. If necessary restore mount /home/jtel/shared Mount.

  2. Call System.

    1. Calls are put through?

      If not, check the telephony server.

      Look for red messages in the telephony server and act accordingly.

    2. Calls are signalled in the Agent Home or Mini Client?

      If not, check the Hazelcast cluster (PlatformListener for telephony and web server).

Large

Large V1 - Redundant Databases

Large V2 - Redundant Databases + Load Balancing

Large V3 - Redundant Databases + Load Balancing + Storage

Startup Dependencies for Large Systems

Shutting down redundant clusters is easier than starting them back up.

Some components must be checked directly after starting up, before work can continue.

Database:

  • MySQL Replication between all replication partners

Load

Balancing:
  • pcs cluster status

Storage:

  • pcs cluster status
  • drbd status

Startup and Shutdown - Redundant components

If the entire system is shut down, some components may not be immediately available or manual intervention may be necessary.

Storage (Redundant) - CentOS

Sv translation
languageen
Warning
titleUnder Construction

This site is currently under construction. Contained Information is subject to change.

Introduction

A jtel ACD consists of a minimum of 2

of

virtual machines and may grow to sizes of 30 or more,

in concurrence with for example

depending on redundancy or performance requirements. Based on a systems architecture, there are certain dependencies between the services, so a clean startup and shutdown is required and only done in a certain order to prevent problems during and after startup. The following

page describes

pages describe the general parameters, as well as some of the various possible scenarios for proper shutdown and startup procedures, depending on the systems architecture. 

Info
titleOn Premise

Caution for on premise jtel ACD systems:

Shutting down and starting the virtual machines of your jtel

ACD back

System is not part of the jtel service contract and may incur service fees as a result, if assistance from jtel is required. For further information, or to book a service appointment, please contact us at service@jtel.de 

Page Layout

This page is split into three rows, each named after a different type of sizing

The pages are split into a parent and child pages. This parent page contains general information. The child pages each contain information about the specific procedure, depending on the sizing of the system. The sizing variants are Small, Medium and

Large  

General

Info

The Hostnames of an ACDs jtel virtual machines may not be in concurrence with the aliases displayed below.

AliasSignifiesShutdown PriorityStartup Priority
acd-dbmDatabase MasterThirdThird
acd-dbm1First Database MasterThirdThird
acd-dbm2Second Database MasterThirdThird
acd-dbsDatabase SlaveSecondFourth
acd-dbs1First Database SlaveSecondFourth
acd-dbs2Second Database SlaveSecondFourth
acd-dbrReporting DatabaseSecondFourth
acd-lbThe Load BalancerFourthSecond
acd-lb1First Load BalancerFourthSecond
acd-lb2Second Load BalancerFourthSecond
acd-storeThe File StorageLastFirst

acd-tel1
...
acd-telN

The Telephony Machine(s) Numbered from 1 ... NFirstLast

acd-jb1
...
acd-jbN

The Webserver Machine(s) Numbered from 1 ... NFirstLast
acd-apiThe REST-APIFirstLast
acd-chatChat and or WhatsAppFirstLast
acd-chatbotChatbot FirstLast
Steps 1 to NShutdownStartup
1acd-telacd-store/lb/dbm/dbs/dbr/jb
2acd-store/lb/dbm/dbs/dbr/jbacd-tel
Steps 1 to NShutdownStartup
1acd-telacd-store/lb/jb
2acd-dbm/dbs/dbracd-dbm/dbs/dbr
3acd-store/lb/jbacd-tel
Steps 1 to NShutdownStartup
1acd-telacd-store/lb
2acd-jbNacd-dbm/dbs/dbr
3acd-dbm/dbs/dbracd-jbN
4acd-store/lbacd-tel
Steps 1 to N

Shutdown

Startup

1

acd-tel

acd-store/lb

2

acd-jbN

acd-dbm

3

acd-dbs/dbr

acd-dbs/dbr

4

acd-dbm

acd-jbN

5

acd-store/lb

acd-tel

Steps 1 to N

Shutdown

Startup

1

acd-tel

acd-store

2

acd-jbN

acd-lb

3

acd-dbs/dbr

acd-dbm

4

acd-dbm

acd-dbs/dbr

5

acd-lb

acd-jbN

6

acd-store

acd-tel

Steps 1 to NShutdownStartup
1acd-telNacd-store
2acd-jbNacd-lb
3acd-dbs1/dbr1acd-dbm2
4acd-dbs2/dbr2acd-dbm1
5acd-dbm1acd-dbs2/dbr2
6acd-dbm2acd-dbs1/dbr1
7acd-lbacd-jbN
8acd-storeacd-telN
Steps 1 to NShutdownStartup
1acd-telNacd-store
2acd-jbNacd-lb2
3acd-dbs1/dbr1acd-lb1
4acd-dbs2/dbr2acd-dbm2
5acd-dbm1acd-dbm1
6acd-dbm2acd-dbs2/dbr2
7acd-lb1acd-dbs1/dbr1
8acd-lb2acd-jbN
9acd-storeacd-telN
Steps 1 to NShutdownStartup
1acd-telNacd-store2
2acd-jbNacd-store1
3acd-dbs1/dbr1acd-lb2
4acd-dbs2/dbr2acd-lb1
5acd-dbm1acd-dbm2
6acd-dbm2acd-dbm1
7acd-lb1acd-dbs2/dbr2
8acd-lb2acd-dbs1/dbr1
9acd-store1acd-jbN
10acd-store2acd-telN
Warning

This checklist is not viable for installations that use the new DRBD construct of Primary/Secondary. It is viable only for constructs that use Primary/Primary

Shut down (only one)

Always shut down one after the other.

With:

Translations Ignore
Code Block
pcs status 

determine which node is Primary.

On the Secondary Node:

Translations Ignore
Code Block
drbdadm secondary jtelshared
shutdown now

Then shut down the Primary Node.

Translations Ignore
Code Block
shutdown now

Boot up (only one)

After booting the Secondary Node, check the status. It should be Secondary and UpToDate

Translations Ignore
Code Block
pcs status 

Check Sync status with :

Translations Ignore
Code Block
cat /proc/drbd

After the sync is done, if necessary, and is ready:

Translations Ignore
Code Block
drbdadm primary jtelshared

Check status with: It should be Primary/Primary + UpToDate/UpToDate

Translations Ignore
Code Block
cat /proc/drbd

Shut down (both)

With:

Translations Ignore
Code Block
pcs status

determine which node is active (the node on which Samba and the virtual IP is running). This is the Primary Node. 

Set the secondary Node to secondary with:

Translations Ignore
Code Block
drbdadm secondary jtelshared
shutdown now

On the Secondary Node first, then Primary:

Translations Ignore
Code Block
shutdown now

Start up (both)

Boot the Primary Node first

Check DRBD sync Status and pcs cluster status

Check with:

Translations Ignore
Code Block
pcs status
cat /proc/drbd

The Primary Node should be primary, and Secondary Node should be secondary. Disc should be UpToDate

Then on Secondary Node

Translations Ignore
Code Block
drbdadm primary jtelshared
Check with: 
Translations Ignore
Code Block
cat /proc/drbd

Both nodes should be set to Primary/Primary + UpToDate/UpToDate

Then check if everything works a final time:

Translations Ignore
Code Block
pcs status
cat /proc/drbd

Balancing:

  • pcs cluster status

Storage:

  • pcs cluster status
  • drbd status

Checks after starting a system

To ensure proper system functionality after a boot, tests are required. Follow the guideline on this page: System Health Check

Machines and Shutdown Priorities

Info

The Hostnames of an ACDs jtel virtual machines may not be in concurrence with the aliases displayed below.


AliasSignifiesShutdown PriorityStartup Priority
acd-dbmDatabase MasterThirdThird
acd-dbm1First Database MasterThirdThird
acd-dbm2Second Database MasterThirdThird
acd-dbsDatabase SlaveSecondFourth
acd-dbs1First Database SlaveSecondFourth
acd-dbs2Second Database SlaveSecondFourth
acd-dbrReporting DatabaseSecondFourth
acd-lbThe Load BalancerFourthSecond
acd-lb1First Load BalancerFourthSecond
acd-lb2Second Load BalancerFourthSecond
acd-storeThe File StorageLastFirst

acd-tel1 ... acd-telN

The Telephony Machine(s) Numbered from 1 ... NFirstLast

acd-jb1 ... acd-jbN

The Webserver Machine(s) Numbered from 1 ... NFirstLast
acd-apiThe REST-APIFirstLast
acd-chatChat and or WhatsAppFirstLast
acd-chatbotChatbot FirstLast


de
Sv translation
languagede


Warning
titleAlt

Diese Seite ist veraltet und aktuell nur in englischer Version verfügbar.

Sv translation
language

Hoch- und Runterfahren

Alle Systeme sind so gestaltet, dass Sie hochfahren und alle Dienste selbstständig starten.

Dennoch ergeben sich gewisse Abhängigkeiten zwischen den Diensten, sodass ein sauberes Hoch- und Herunterfahren am besten geschieht, wenn eine gewisse Reihenfolge betrachtet wird. 

Hochfahren

Abhängigkeiten

Alle Dienste der Plattform sind von zwei zentrale Entitäten abhängig:

  • Das Storage
  • Die Datenbank(en)

Für das Hochfahren der Lösung, sollte immer zuerst das Storage hochgefahren werden. Wenn dies Extern zur Lösung ist, dann fährt man mit den nächsten Schritt fort. Ansonsten, wird der Rechner (oder bei Redundanz - beide Rechner) gestartet auf den das Storage ist. Dies ist in der Regel der Load-Balancer, bei größere Systeme kann jedoch eine separate Storage-Maschine implementiert worden sein.

Anschließend, wird die Master Datenbank hochgefahren. Sobald dieser oben ist, kann der Slave hochgefahren werden.

Zum Schluss können die Telefonieserver und Webserver in einer beliebigen Reihenfolge, auch gleichzeitig, hochgefahren werden.

Reihenfolge

Im Folgenden wird von einer nicht redundante Lösung ausgegangen. Der Betrieb einer redundanten Lösung bedarf eine gesonderte Schulung.

Somit ergibt sich folgende Startreihenfolge:

  1. Storage (Separates Storage acd-store oder Load-Balancer acd-lb). 
    Warten bis Storage oben ist.
  2. Bei separater Storage, nun den Load-Balancer acd-lb hochfahren.
    Hier muss nicht gewartet werden.
  3. acd-dbm - Datenbankmaster - hochfahren.
    Warten bis DB-Master oben ist.
  4. acd-dbs - Datenbankslave - hochfahren.
    Warten bis DB-Slave oben ist.
  5. acd-jb1 ... acd-jb(x) sowie acd-tel1 ... acd-tel(x) hochfahren.

Prüfungen

  1. Am Web über den Load-Balancer anmelden. 
    1. Anmeldung OK?
      Wenn nicht, /home/jtel/jboss-(version)/standalone/log/server.log prüfen.
    2. GANZ WICHTIG: Logo in der Webanwendung sichtbar?
      Wenn nicht, ist das Storage nicht oben. Mit mount auf den Webservern prüfen. Ggf. mit mount /home/jtel/shared Mount wiederherstellen.
  2. System anrufen.
    1. Anrufe werden durchgestellt?
      Wenn nicht, Telefonieserver prüfen.
      Nach rote Meldungen im Telefonieserver schauen und entsprechend handeln.
    2. Anrufe werden im Agent-Home bzw. Mini-Client signalisiert?
      Wenn nicht, Hazelcast-Cluster (PlatformListener auf Telefonie, sowie Webserver) prüfen.

Herunterfahren

Reihenfolge

Das Herunterfahren geschieht in der umgekehrten Reihenfolge:

  1. Alle Webserver acd-jb1 ... acd-jb(x) und Telefonieserver acd-tel1 ... acd-tel(x) herunterfahren.
    Schritt fertigstellen bzw. sicherstellen dass die Rechner wirklich am herunterfahren sind bevor man weitermacht.
  2. Datenbank Slave acd-dbs herunterfahren.
  3. Datenbank Master acd-dbm herunterfahren.
  4. Load Balancer acd-lb herunterfahren.
  5. Bei separater Storage, acd-store herunterfahren.

Zwischen den einzelnen Schritten ist es nicht zwingend notwendig zu warten, ledeglich Schritt 1 sollte insgesamt abgeschlossen sein bevor man fortfährt.

Hoch- und Runterfahren - Redundante Komponeten

Wenn das gesamte System heruntergefahren wird, kann es sein, dass manche Komponenten nicht sofort verfügbar sind, bzw. dass ein manueller Eingriff notwendig ist.

Storage (Redundant)

Runterfahren (nur einer)

Immer eins nacheinander herunterfahren.

Mit:

Translations Ignore


Code Block
pcs status 


feststellen welcher Node aktiv ist.

Auf den anderen node:

Translations Ignore


Code Block
drbdadm down jtelshared


Dann diesen Node herunterfahren.

Hochfahren (nur einer)

Wurde nur ein Node neu gestartet, dann kann der Betrieb wieder aufgenommen werden indem man auf den Secondary folgendes nach dem Neustart eingibt:

Translations Ignore


Code Block
drbdadm up jtelshared


Sync status prüfen mit:
Translations Ignore


Code Block
cat /proc/drbd


Nachdem der Sync ggf. erfolgt ist, und fertig ist:

Translations Ignore


Code Block
drbdadm primary jtelshared


Runterfahren (beide)

Mit:

Translations Ignore


Code Block
pcs status


feststellen welcher Node aktiv ist (der Node auf den das Samba sowie die virtuelle IP läuft). Dies ist der Primary Node. 

Mit:

Translations Ignore


Code Block
pcs cluster stop --all


den Cluster auf inaktiv setzen.

Auf auf den Secondary zuerst, dann Primary:

Translations Ignore


Code Block
drbdadm down jtelshared
shutdown now



Hochfahren (beide)

Beide nodes booten.

Auf beide Nodes (Primary zuerst):

Translations Ignore


Code Block
drbdadm up jtelshared


Prüfen mit:

Translations Ignore


Code Block
cat /proc/drbd


Beide Nodes sollten auf Secondary stehen, aber kein Sync sollte erfolgen.


Dann auf beide Nodes (Primary zuerst):

Translations Ignore


Code Block
drbdadm primary jtelshared


Prüfen mit: 
Translations Ignore


Code Block
cat /proc/drbd


Beide Nodes sollten auf Primary stehen, aber kein Sync sollte erfolgen.

Dann auf den Primary:

Translations Ignore


Code Block
pcs cluster start --all
pcs resource cleanup 



Dann prüfen ob alles läuft:

Translations Ignore


Code Block
pcs status




Sv translation
languagefr


Warning
titleAncien

Cette page est obsolète et n'est actuellement disponible qu'en version anglaise.

Démarrage et fermeture

Tous les systèmes sont conçus pour démarrer et faire démarrer tous les services indépendamment.

Toutefois, il existe certaines dépendances entre les services, de sorte qu'un démarrage et un arrêt propres sont mieux réalisés lorsqu'une certaine commande est envisagée. 

Démarrage

Dépendances

Tous les services de la plate-forme dépendent de deux entités centrales :

  • Le stockage
  • Base(s) de données

Pour démarrer la solution, le stockage doit toujours être démarré en premier. Si cela est externe à la solution, passez à l'étape suivante. Sinon, l'ordinateur (ou en cas de redondance - les deux ordinateurs) est démarré sur lequel se trouve le stockage. Il s'agit généralement de l'équilibreur de charge, mais pour les systèmes plus importants, une machine de stockage distincte aurait pu être implémentée.

Ensuite, la base de données principale est lancée. Dès qu'elle est terminée, l'esclave peut être démarré.

Enfin, les serveurs de téléphonie et les serveurs web peuvent être démarrés dans n'importe quel ordre, même simultanément.

Ordre

Une solution non redondante est supposée dans ce qui suit. Le fonctionnement d'une solution redondante nécessite une formation supplémentaire.

Il en résulte l'ordre de départ suivant :

  1. Stockage (Stockage séparé acd-store ou Load-Balancer acd-lb). 
    Attendez que le stockage soit terminé.
  2. Avec un stockage séparé, démarrez maintenant l'équilibreur de charge acd-lb.
    Il n'est pas nécessaire d'attendre ici.
  3.  acd-dbm - Base de données principale .
    Attendez que le DB-Master soit en place.
  4.  acd-dbs -  Base de données Esclave- .
    Attendez que l'esclave de la DB soit en place.
  5. Démarrer acd-jb1 ... acd-jb(x) ainsi queacd-tel1 ... acd-tel(x)

Vérifications

  1. Connectez-vous au Web via l'équilibreur de charge. 
    1. Connexion OK ?
      Si ce n'est pas le cas, cochez /home/jtel/jboss-(version)/standalone/log/server.log
    2. ESSENTIEL: Logo visible dans l'application web ?
      Sinon, le stockage n'est pas en place. Vérifiez avec le montage sur les serveurs web. Si nécessaire, restaurez la monture mount /home/jtel/shared.
  2. Système d'appel.
    1. Les appels sont passés ?
      Si ce n'est pas le cas, vérifiez le serveur de téléphonie.
      Recherchez les messages rouges dans le serveur de téléphonie et agissez en conséquence.
    2. Les appels sont signalés dans la maison de l'agent ou du mini-client ?
      Si ce n'est pas le cas, vérifiez le cluster Hazelcast (PlatformListener pour la téléphonie et le serveur web).

Shutdown

Ordre

La fermeture se fait dans l'ordre inverse :

  1. Fermer tous les serveurs web acd-jb1 ... acd-jb(x) et les serveurs de téléphonie acd-tel1 ... acd-tel(x) 
    Terminez l'étape ou assurez-vous que les ordinateurs sont vraiment en train de s'éteindre avant de continuer.
  2. Arrêter l'esclave des bases de données acd-dbs.
  3. Fermer la base de données principale acd-dbm.
  4. Éteindre l'équilibreur de charge acd-lb.
  5. Pour un stockage séparé, fermer acd-store.

Il n'est pas absolument nécessaire d'attendre entre les différentes étapes, il suffit de terminer l'étape 1 avant de continuer.

Démarrage et arrêt - Composants redondants

Si l'ensemble du système est arrêté, certains composants peuvent ne pas être immédiatement disponibles ou une intervention manuelle peut être nécessaire.

Storage (Redundant) - CentOS

Warning

Cette liste de contrôle n'est pas viable pour les installations qui utilisent la nouvelle construction DRBD de primaire/secondaire. Il n'est viable que pour les constructions qui utilisent le primaire/primaire.

Arrêt (un seul)

Toujours fermer l'un après l'autre.

Avec:

Translations Ignore


Code Block
pcs status 


déterminer quel nœud est Primaire.

Sur le Nœud Secondaire :

Translations Ignore


Code Block
drbdadm secondary jtelshared shutdown now


Ensuite, arrêtez le Noeud Primaire.

Translations Ignore


Code Block
shutdown now


Démarrer (un seul)

Après avoir démarré le Noeud Secondaire ,vérifiez son état. Il doit être secondaire et actualisé.

Translations Ignore


Code Block
pcs status 


Vérifiez le statut de sync avec :

Translations Ignore


Code Block
cat /proc/drbd


Après la synchronisation est fait, si nécessaire, et est prêt :

Translations Ignore


Code Block
drbdadm primary jtelshared


Vérifiez le statut avec : Il devrait être Primaire/Primaire + UpToDate/UpToDate

Translations Ignore


Code Block
cat /proc/drbd


Arrêter (les deux)

Avec:

Translations Ignore


Code Block
pcs status


déterminer quel nœud est actif (le nœud sur lequel Samba et l'IP virtuel fonctionnent). C'est le Nœud primaire. 

Définissez le nœud secondaire comme secondaire avec :

Translations Ignore


Code Block
drbdadm secondary jtelshared shutdown now


Sur le nœud secondaire d'abord, puis le Primaire :

Translations Ignore


Code Block
shutdown now



Démarrage (les deux)

Démarrer le Noeud Primaire d'abord

Vérifier l'état de la synchronisation DRBD et l'état du cluster pcs.

Vérifier Avec

Translations Ignore


Code Block
pcs status cat /proc/drbd


Le Noeud primaire devrait être primaire, et le Noeud Secondaire devrait être secondaire. Le disque doit être UpToDate


Puis, sur le Nœud Secondaire

Translations Ignore


Code Block
drbdadm primary jtelshared


Vérifier Avec 
Translations Ignore


Code Block
cat /proc/drbd


Les deux noeuds doivent être réglés sur Primaire/Primaire + UpToDate/UpToDate

Vérifiez ensuite si tout fonctionne : pour la dernière fois :


Translations Ignore


Code Block
pcs status cat /proc/drbd