Day-35 - ETCD Backup & Restore in Kubernetes

Day-35
Today I explored ETCD Backup & Restore in Kubernetes — the heart of cluster state management!

Key Learnings:
1️⃣ ETCD is the brain of Kubernetes — every object, pod, and config lives there as key-value pairs.
2️⃣ kubectl get all -A -o yaml isn’t enough — it misses PVs, PVCs, and low-level cluster state.
3️⃣ For full resilience, always back up ETCD using etcdctl snapshot save /opt/etcd-backup.db.
4️⃣ Before any cluster upgrade or major release, take a snapshot — it’s your safety net!
5️⃣ Restoring is simple: etcdctl snapshot restore + update --data-dir in etcd.yaml and restart the kubelet.
6️⃣ For managed clusters (EKS/AKS/GKE), tools like Velero make backup automation seamless.

💡Pro Tips:
Schedule ETCD backups as a cron job and push them to AWS S3 or secure storage — automation saves you in emergencies.

Backups aren’t just about disaster recovery — they’re about confidence, continuity, and control over your Kubernetes world!

ReadMore: https://lnkd.in/d4TCZQMS

Comments

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works 1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS. 2. ESXi detects low free memory on the host. 3. ESXi inflates the balloon in selected VMs. 4. Balloon driver occupies guest memory, making the OS think RAM is full. 5. Guest OS frees idle / unused pages (because it believes memory is needed). 6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens? • Host free memory is very low. • ESXi wants the VM to release unused pages before resorting to swapping. Example • Host memory: 64 GB • VMs used: 62 GB • Free: 2 GB → ESXi triggers ballooning • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

ESXi Host Troubleshooting Checklist

🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...

vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...

Tech-Gen

Search This Blog