<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Backup on Aperture Zone</title>
    <link>https://aperturezone.com/tags/backup/</link>
    <description>Recent content in Backup on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Mon, 23 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/backup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automate network device configuration backup with Ansible</title>
      <link>https://aperturezone.com/posts/ansible2/</link>
      <pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/ansible2/</guid>
      <description>&lt;p&gt;Whether in a home lab or a professional infrastructure, network equipment is often overlooked in backup strategies. We think about backing up VMs, data, and servers—but rarely the configurations of switches and Wi-Fi access points. However, in the event of a failure or hardware replacement, not having the configuration on hand can result in hours of work to rebuild the system.&lt;/p&gt;
&lt;p&gt;In this article, we’ll set up an Ansible playbook that automatically backs up our network equipment configurations, stores them locally with a 30-day retention period, and sends an HTML report via email after each run.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
