Automating Website Backups with Bash Script

10 days into the 100 Days of DevOps Challenge by KodeKloud — here's my progress so far! 🗓️ I've been documenting everything on GitHub and now sharing it here on LinkedIn too. Here's a quick look at what I've tackled: ✅ Linux User Management — creating service accounts with non-interactive shells ✅ Temporary Accounts with Expiry — setting time-bound access for developers ✅ Disabling Root SSH Access — hardening servers against brute-force attacks ✅ Script Execution Permissions — managing file permissions for automation ✅ SELinux Configuration — installing and managing security policies ✅ Cron Job Automation — scheduling tasks across multiple servers ✅ SSH Key Authentication — enabling passwordless access for automated scripts ✅ Ansible Setup — installing and configuring a configuration management tool ✅ MariaDB Troubleshooting — diagnosing and fixing a production database outage ✅ Bash Backup Script — automating website backups with secure remote transfer Biggest lesson so far? The basics aren't boring — they're the foundation everything else is built on. Security, automation, and reliability all trace back to getting these fundamentals right. 🏗️ What surprised me the most? How many of these tasks overlap in real-world DevOps — SSH keys show up in backup scripts, permissions show up everywhere, and nothing works without proper user management. Still 90 days to go. One task at a time. 💪 #DevOps #Linux #KodeKloud #100DaysOfDevOps #LearningInPublic #Ansible #Automation #WeeklyRecap

If you’re doing repetitive tasks in Linux manually… you’re wasting power. Because the real magic isn’t in commands… 👉 It’s in automating them ⸻ 💡 Shell scripting = turning effort into systems Not theory. Not syntax. 👉 Real-world problem solving ⸻ 📖 As shown in these real-time examples Even simple scripts can: ✔ Take automated backups ✔ Monitor system services ✔ Run scheduled jobs without manual effort ⸻ 🔁 Example 1: Automated Backup Script From page 1–2 A simple script can: 👉 Copy files from source → destination 👉 Create timestamped backup folders 👉 Ensure data safety automatically 💡 Add cron job → It runs every minute/hour/day without you touching it ⸻ ⏱️ Automation + Cron = Infinite efficiency From page 3 👉 crontab -e → Schedule tasks → Forget manual execution Your system works… even when you don’t 💻 ⸻ 🧠 Example 2: Service Health Monitoring From page 4–5 Script logic: 👉 Check if service is running 👉 If not → start it automatically 💡 Real-world use case: Server down at 2 AM? Script fixes it before you even wake up 😴 ⸻ 🔥 This is where DevOps begins: Before scripting: ❌ Manual backups ❌ Manual checks ❌ Human dependency After scripting: ✅ Automated workflows ✅ Self-healing systems ✅ Reliable operations ⸻ ⚡ Mindset shift: Beginner: ❌ “I run commands” Engineer: ✅ “I automate systems” ⸻ 💡 The truth: Shell scripts are not just scripts… 👉 They are mini automation engines ⸻ 🚀 Final thought: Don’t just execute tasks… Design systems that execute themselves ⸻ #ShellScripting #Linux #DevOps #Automation #Bash #Scripting #Cloud #Engineering #SysAdmin #Infrastructure #SRE #Cron #Monitoring #AutomationTools #CloudComputing #AWS #Azure #GCP #Productivity #Tech #Programming #Developers #IT #OpenSource #Unix #ServerManagement #TechSkills #CareerGrowth #BuildInPublic

🔐 Day 7 of #100DaysOfDevOps — Passwordless SSH authentication Today's task: set up key-based SSH access from the jump host to all 3 app servers so automation scripts can run without any password prompts. This is how EVERY real DevOps pipeline works. Here's the concept: SSH key authentication uses a key PAIR: 🔑 Private key → stays ONLY on your machine (never shared) 🔓 Public key → copied to every server you want to access When you SSH in, the server challenges you to prove your identity using the private key. No password. No human input. Fully automated. The 3 commands that make it happen: 1. ssh-keygen -t rsa → Generates your key pair on the jump host 2. ssh-copy-id tony@stapp01 → Copies your public key to the server (password used once — for the last time) 3. ssh tony@stapp01 → Connects instantly. Zero password prompt. ✅ Repeated for all 3 app servers. Why this matters in DevOps: → CI/CD pipelines deploy code via SSH — they can't type passwords → Cron jobs that SSH between servers need this → Ansible, Terraform, and most automation tools rely on key auth → It's more secure than passwords — virtually impossible to brute force "ssh-copy-id uses a password once so you never need a password again." #DevOps #Linux #SSH #Automation #Security #CloudEngineering #KodeKloud

🚀 100 Days of DevOps – Days 9–12 Journey The past few days pushed me out of my comfort zone — and honestly, that’s where the real learning happened. 🔧 What I worked on: -> Troubleshooting database issues in MariaDB (service failures due to permission problems) -> Fixing application downtime by debugging logs and system services -> Writing automation scripts for backups and enabling password-less SSH -> Setting up and configuring Apache HTTP Server and Apache Tomcat -> Debugging connectivity issues across servers in a multi-tier environment ⚠️ Challenges I faced (and learned from): -> Services failing silently due to wrong permissions -> Ports being blocked even when services were running (this one was tricky!) -> Confusion between different servers and ports during debugging “No route to host” errors that turned out to be network-level restrictions -> Fixing one issue… only to discover another layer underneath 😅 💡 Key lessons: -> Always debug layer by layer (Service → Port → Firewall → Network) -> Logs (systemctl status, journalctl) are your best friend -> Small configuration mistakes can cause big failures -> Real DevOps work is not just writing code — it’s thinking, testing, and troubleshooting #DevOps #Linux #SystemAdministration #100DaysOfDevOps #LearningByDoing #CloudJourney

Master Linux faster with these powerful one-liners. Most engineers overcomplicate simple tasks. Linux already gives you speed. You just need to know where to look. In my training sessions, I focus on one thing. Practical commands that save hours every week. Because real engineers don’t memorize. They optimize. Here’s how these one-liners change your workflow 👇 → Clean logs instantly rm *.log → Find disk hogs in seconds du -ah / | sort -rh | head -n 10 → Create quick backups tar -czvf backup.tar.gz /path → Kill stuck processes fast kill -9 $(pgrep process_name) → Debug logs efficiently grep -Ri "error" /var/log → Spin up quick servers python3 -m http.server 8000 → Monitor system health df -h → Audit open ports netstat -tuln This is not just commands. This is operational efficiency. This is production confidence. This is how DevOps engineers think. What I teach in real training environments 👇 → Think in pipelines, not single commands → Automate repetitive workflows → Debug using logs, not guesswork → Optimize systems before scaling → Build speed without breaking reliability Because in real-world DevOps 👇 Slow engineers debug. Smart engineers prevent. Elite engineers automate. If you master just these fundamentals. You move from beginner to top 10% instantly. Save this. Practice this. Apply this daily. Which Linux command saves you the most time daily? #Linux #DevOps #CloudComputing #Automation #Scripting #Engineering #TechSkills #SystemAdmin #IT #CareerGrowth #LinuxTips #DevOpsEngineer #Productivity #AutomationTools #TechCareers

Glad to see people are doing more and more projects and sharing their knowledge with the community. As I always say, “If you build something, you should let others know what you’ve done and who you are don’t be a ghost.”

🚨 Most DevOps engineers use Linux daily… But many don’t actually understand its file system. That’s a hidden skill gap. If you're working with: ⚙️ Kubernetes ⚙️ CI/CD pipelines ⚙️ Cloud VMs Then Linux isn’t just a tool — it’s your foundation. Without understanding its structure, debugging becomes guesswork. 📁 Linux File System Hierarchy (FHS) — Simplified /boot → System startup files (kernel, GRUB) /etc → Configuration (the brain of your system) /home → User data & files /root → Root user’s home /opt → Third-party software /dev → Devices as files /var → Logs, cache, runtime data (start here for debugging) /bin → Essential commands (ls, cp, cat) /sbin → Admin/system commands /usr → Applications & shared libraries /proc → Process + kernel insights (real-time) /sys → Hardware & kernel interface /run → Runtime state (since last boot) /tmp → Temporary files (auto-cleaned often) 📌 Bonus: /lib, /lib64 → Core libraries /mnt, /media → Mount points /srv → Service data /lost+found → Recovered files 💡 Why this matters (real DevOps impact) ✔ Debug issues faster → check /var/log first ✔ Understand containers at a deeper level ✔ Write better automation scripts ✔ Handle permissions & security confidently ✔ Stay calm during production outages 💬 Quick check: If your app goes down… Which directory do you check first? 👉 Don’t just use Linux. Master it. #DevOps #Linux #CloudComputing #Kubernetes #AWS #Azure #SRE #Infrastructure #SysAdmin #TechCareers #Programming #Containers #CI_CD #LearningInPublic #CareerGrowth

🚀 Day 10/100 — DevOps Journey: Automated Backup Pipeline Today I implemented a real-world automation task by building a backup system for a web application running on a server in a multi-node environment. 🛠️ What I did: -> Created a bash script to compress website files into a zip archive -> Stored the backup locally on the application server -> Automated secure transfer of the backup to a remote storage server using SCP Configured password-less SSH for seamless automation between servers 💡 Key takeaway: ->Automation in DevOps is not limited to a single server. Real systems involve coordination between multiple servers, and tools like SSH and scripting make this communication seamless. This exercise helped me understand how production backup pipelines work in real environments — where application servers generate data and storage servers manage persistence. #DevOps #100DaysOfDevOps #Linux #Automation #Bash #Scripting #SSH #LearningInPublic

9 categories. 45 commands. Every single one with a real example. I put together a Linux command reference specifically for DevOps engineers,  These are the commands that actually come up when you're debugging a deployment, checking a memory leak or trying to figure out why port 8080 is busy at midnight. Swipe through 👇 Here's what's inside: 📁 File & Directory - ls, find, rsync, tar, cp  🔍 Text Processing - grep, awk, sed, cut, wc ⚙️ Process & System - ps, pgrep, lsof, htop, kill 💾 Disk & Storage - df, du, lsblk, iostat, mount 🌐 Networking - curl, ss, dig, scp, traceroute 🔒 Security & Permissions - chmod, ssh-keygen, ufw, openssl, sudo -l 📋 Logs & Monitoring - journalctl, tail -f, watch, dmesg, logrotate 🤖 Automation & Scheduling - cron, nohup, tmux, xargs, env 🌿 Git - log, stash, diff, bisect, cherry-pick If you're just starting out in DevOps or cloud save this, you might need atleast one of these this week. Detailed blog with full explanations at the link below 👇 https://lnkd.in/dX9z_g4V Which command do you use the most? Let me know in the comments below. As always if you found this helpful, give it a like👍 Repost♻️ Follow Balavignesh Manoharan for more such posts💯🚀 #linuxCommands #linux #devops #cloud

Almost every command mentioned here is something I’ve actually used in production. From debugging high CPU issues, checking open ports, analyzing logs, to handling deployments — these commands are part of daily DevOps work. If you're working with Linux or cloud, this is definitely worth saving 👍 Great compilation! 👏