{"id":950,"date":"2026-09-29T17:05:26","date_gmt":"2026-09-29T16:05:26","guid":{"rendered":"https:\/\/guillaumesblog.net\/?p=950"},"modified":"2026-09-29T17:05:26","modified_gmt":"2026-09-29T16:05:26","slug":"always-have-your-back-ups-ready","status":"publish","type":"post","link":"https:\/\/guillaumesblog.net\/index.php\/always-have-your-back-ups-ready\/","title":{"rendered":"Always have your back-ups ready!"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Always assume the worst immediately! Fun story I got locked out from my Debian instance because of a bug in the distro update, and this did prevent me from logging in from SSH. To make matters worst I did not set-up user passwords at VM creation and hence could not to access the console from the serial connection… so there was no way for me to enter the instance and to troubleshot.<\/p>\n\n\n\n\n\n\n\n

\"\"
Could not access the machine.. I did not setup any password<\/figcaption><\/figure>\n\n\n\n

I am talking about this weird error from Debian 13 here<\/a>… Anyway I ended up being very nervous about my ability to recover my website (this blog), since I usually do the back-ups manually (!) and also did not run one for a while… I would have for sure lost a couple of articles. I would have though that Debian would spare me from such dumb issues, as the distro had a reputation to be extremely stable. What happened is that I did an update during the previous connection a few months ago and did not take the necessary precautions you should always take before making any kind of updates.<\/p>\n\n\n\n

Thankfully I solved it by unmounting the disk and mounting it onto a new instance, attach my reserved IP to it and I could get going again. The take away is to not forget to setup passwords on users, and also to automate the back ups.<\/p>\n\n\n\n

#!\/bin\/bash\n# THE CRON JOB CODE\n\necho \"Prepping variables...\"\nCURRENTEPOCTIME=`date +\"%Y-%m-%d_%H%M%S\"`\nBACKUP_PATH=\"\/home\/admin\/backups\/backup_nginx_${CURRENTEPOCTIME}\"\necho \"Creating backup folder....\"\nmkdir -p \"${BACKUP_PATH}\"\necho \"Backing up DB....\"\nmysqldump -u root wordpress_db > \"${BACKUP_PATH}\/backup_db_${CURRENTEPOCTIME}.sql.bak\"\necho \"Backing up html folder...\"\ncp -R \/var\/www\/html \"$BACKUP_PATH\"\/\necho \"Tar-ing the lot...\"\ntar -czf \"${BACKUP_PATH}\"\/..\/backup_wp_website-\"$CURRENTEPOCTIME\".tar.gz -C \"$BACKUP_PATH\"\/.. .\nrm -rf \"${BACKUP_PATH}\"\necho \"Sending it to s3 Ohio...\"\n. \/root\/tos3\/env\/bin\/activate\npython \/root\/tos3\/main.py\necho \"Done\"<\/code><\/pre>\n\n\n\n
And the python code with boto3 for an upload of the backup into S3<\/p>\n\n\n\n
import boto3, os, logging\nfrom botocore.exceptions import ClientError\n\ns3 = boto3.resource('s3')\ns3_client = boto3.client('s3')\nmy_bucket = s3.Bucket('bucket_name')\np = r\"\/home\/admin\/backups\/\"\n\nprint(\"Begin copy to bucket....\")\n\nfor file in os.scandir(p):\n    if file.is_file():\n        obj_name = os.path.basename(file)\n        try:\n            resp = s3_client.upload_file(file, my_bucket.name, obj_name)\n        except ClientError as e:\n            logging.error(e)\n\nprint(\"Script executed\")<\/code><\/pre>\n\n\n\n
Now I can sleep better, my cron job will execute periodically and store my backups safely in S3…<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Here are my take away, appreciate I am stating the obvious here \ud83d\ude42<\/p>\n\n\n\n