Menu

1 / 3

Day 76: A Backup of Nothing and a Retiring Default

DEV Community: jenkins·Nnamdi Felix Ibe·11 days ago
#kgDmuLs0
#devtojenkins#devto#dev#jenkins#exit
Reading 0:00
15s threshold

Day 76 of DevOps, Day 26 of Azure. Both tasks today went green, and both were quietly resting on something that will not hold.

A database backup job ran on schedule, produced a file, copied it across two machines, and backed up no tables at all. And an Azure network behaviour I had written in my notes as how Azure works turned out to be a platform default that Microsoft is in the middle of retiring.

One Jenkins task, one Azure task. Schedule a database backup across three servers, then put a VM in a purpose-built virtual network. The tasks come from the KodeKloud Engineer platform.

Task 1: A database backup on a ten-minute schedule

The task: a job named database-backup that dumps a database on stapp01 every ten minutes and copies the dump to the storage server.

Step 1: Two hops, two keys

Three machines are involved, and the Jenkins controller never touches the storage server directly.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.