# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Cherry Blossom

# CherryBlossom -- Installation Guide

19 July, 2012

- 1
- 2
…
- 18
- 19
- 20
- 21

SECRET//20350112
9 (U) CB Master Server Failover Procedures
(U) This section contains the instructions for CB Server Failover in the case of a CB
Master Server failure. If you have followed the troubleshooting directions of Section 8,
and are convinced that a CB Master Server has had a severe hardware failure and is in
need of repair, then follow the instructions in this section to failover – i.e., to make the
hot spare CB Slave server become the CB Master server. To bring the failed server back
into service, follow the instructions in Section 9.2.
(U) IMPORTANT: The failover procedure requires that only one CB Master Server be in
service (i.e., receiving Beacons, Alerts, Copy Data, etc.) at any given time. Do not flip-
flop between two CB Master Servers -- i.e., once a CB Slave is promoted to Master, the
previous Master MUST be enabled/activated by following Server Recovery Procedures in
Section 9.2. Otherwise the system will diverge into two separate databases that are not
easily merged.
9.1 (U) Server Failover Procedure
(U) Run all commands as root unless cbuser is specified.
1. Open a “root” console (see section 5.4) or DRAC console into both Master and
Slave servers (see network diagram of section 5.1 for Master and Slave server
Persistent IP addresses).
2. Have the Master relinquish its CB CC Service IP (see 5.2). If the Master is not
responding, it must be powered down (see section 8.4) OR the network interface
assigned as the Master’s CB CC Service IP must be shut down. The preferred
option is to disable the service interfaces while the Master server is online, by
running “~cbuser/bin/disable-server.sh”
3. Convert the Slave to the Master. On the Slave, run the following:
cd ~cbuser/bin && ./make-cb-master.sh
o Note: the make-cb-master.sh script will generate an error message if
it discovers that another host is using the virtual IP. In this scenario, the
server is in the Disabled Master state and can be activated.
(U) If you encounter difficulties or errors in the process, contact an appropriate CB staff
member (see section 3).
SECRET//20350112
20

- 1
- 2
…
- 18
- 19
- 20
- 21