Cluster Vault Configuration

Jul 10, 2024

Lecture Notes on Cluster Vault Configuration

Standalone and Cluster Vault Overview

Standalone Vault

  • Single Vault is the point of contact for all components (CTM, PVWA, PSM, PSMP)
  • Uses a static IP
  • In case of failure, automatic failover to DR (Disaster Recovery) is possible without manual intervention.
  • For maintenance activities (e.g., Windows patches), a failover is needed to reboot the production vault.

Cluster Vault: Preferred Option

  • Consists of two nodes: Primary (Node 1) and Secondary (Node 2)
  • Nodes are connected via public and private networks
  • Each node checks the status of the other node through private network (cross replication)
  • Virtual IP (VIP) points to the active node

Network Configuration

Types of IPs Needed

  • Private IP for node-to-node communication (ensure same subnet)
  • Public IP for communication between components and nodes through VIP
  • VIP to direct traffic to the active node (added in wall.ini file of components)

Storage Setup

Types of Storage

  1. Quorum Storage: Holds cluster configuration
  2. Shared Storage: Stores all data and files, linked only to the active node

Cluster Composition

  • Two Nodes with Private and Public IPs
  • Five IPs total: 2 Private, 2 Public, 1 VIP
  • Configuration includes Quorum and Shared Storage

Setting Up a Cluster

Pre-requisites

  1. Assign static IPs to node 1 and node 2
    • Ensure two IPs for each node (Private & Public)
    • Use the same subnet to avoid connectivity issues
  2. Set up two Storage drives on a dedicated storage server (shared and Quorum)
    • Install iSCSI role on Windows Server
    • Create storage targets for shared and Quorum drives

Configuring Storage

  • The shared storage and Quorum disk are created and initialized using iSCSI initiator on each node.
  • Shared storage for general data (e.g., account data, database metadata)
  • Quorum storage for holding cluster configuration and election process data

Steps to Implement

  1. Static IP Configuration: Ensure IPs are properly set and reboot if needed.
  2. Install iSCSI Role: On storage server, allow storage allocation.
  3. Create Storage: Create shared and Quorum storage in the storage server and make them available to the nodes.
  4. Initialize Disks: Bring the disks online and initialize; label them appropriately (e.g., S for shared, Q for Quorum).
  5. Ensure Connectivity: Ensure connectivity and proper appearance of the drives in both node 1 and node 2.