<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://trashpanda.fisherflix.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://trashpanda.fisherflix.com/feed.php">
        <title>Trash Panda Guides - operations</title>
        <description></description>
        <link>http://trashpanda.fisherflix.com/</link>
        <image rdf:resource="http://trashpanda.fisherflix.com/_media/wiki/dokuwiki.svg" />
       <dc:date>2026-06-21T08:18:07+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://trashpanda.fisherflix.com/operations/automated_maintenance?rev=1781706370&amp;do=diff"/>
                <rdf:li rdf:resource="http://trashpanda.fisherflix.com/operations/lifecycle_management?rev=1781706643&amp;do=diff"/>
                <rdf:li rdf:resource="http://trashpanda.fisherflix.com/operations/logging_telemetry?rev=1781706342&amp;do=diff"/>
                <rdf:li rdf:resource="http://trashpanda.fisherflix.com/operations/power_states?rev=1781706626&amp;do=diff"/>
                <rdf:li rdf:resource="http://trashpanda.fisherflix.com/operations/troubleshooting?rev=1781706610&amp;do=diff"/>
                <rdf:li rdf:resource="http://trashpanda.fisherflix.com/operations/veeam_dr?rev=1781706357&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://trashpanda.fisherflix.com/_media/wiki/dokuwiki.svg">
        <title>Trash Panda Guides</title>
        <link>http://trashpanda.fisherflix.com/</link>
        <url>http://trashpanda.fisherflix.com/_media/wiki/dokuwiki.svg</url>
    </image>
    <item rdf:about="http://trashpanda.fisherflix.com/operations/automated_maintenance?rev=1781706370&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-17T14:26:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>automated_maintenance</title>
        <link>http://trashpanda.fisherflix.com/operations/automated_maintenance?rev=1781706370&amp;do=diff</link>
        <description>Automated Maintenance &amp; Watchdogs

To truly achieve a zero-touch architecture, the ecosystem must be capable of self-healing from minor software hangs, VPN disconnections, or out-of-memory container crashes without requiring manual administrator intervention.</description>
    </item>
    <item rdf:about="http://trashpanda.fisherflix.com/operations/lifecycle_management?rev=1781706643&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-17T14:30:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>lifecycle_management</title>
        <link>http://trashpanda.fisherflix.com/operations/lifecycle_management?rev=1781706643&amp;do=diff</link>
        <description>Application Lifecycle Management (Updates)

While the base operating systems handle their own security patches via the configurations in Unattended Upgrades, the application layer requires manual, sequenced updates to prevent breaking API dependencies between Prowlarr, Sonarr, and Overseerr.</description>
    </item>
    <item rdf:about="http://trashpanda.fisherflix.com/operations/logging_telemetry?rev=1781706342&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-17T14:25:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>logging_telemetry</title>
        <link>http://trashpanda.fisherflix.com/operations/logging_telemetry?rev=1781706342&amp;do=diff</link>
        <description>Centralized Event Logging (Telemetry)

In a decoupled architecture, logging into five separate servers to parse application logs during an outage is highly inefficient. This section configures RSYSLOG on your Linux hosts to forward all system events over the network to the Synology NAS (The Vault) running LogCenter.</description>
    </item>
    <item rdf:about="http://trashpanda.fisherflix.com/operations/power_states?rev=1781706626&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-17T14:30:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>power_states</title>
        <link>http://trashpanda.fisherflix.com/operations/power_states?rev=1781706626&amp;do=diff</link>
        <description>Emergency Power States &amp; Cold Boot Sequence

In a highly interdependent architecture, powering on hosts in the incorrect order will result in cascading failures. Specifically, if the ARR stack boots before the NFS storage fabric is accessible, databases can corrupt, and download paths will fail over to the local</description>
    </item>
    <item rdf:about="http://trashpanda.fisherflix.com/operations/troubleshooting?rev=1781706610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-17T14:30:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>troubleshooting</title>
        <link>http://trashpanda.fisherflix.com/operations/troubleshooting?rev=1781706610&amp;do=diff</link>
        <description>Troubleshooting &amp; Health Diagnostics

Due to the highly segmented nature of this architecture, standard single-host troubleshooting logic does not apply. When an application fails, the fault could lie at the container, host OS, hypervisor, or firewall gateway layer.</description>
    </item>
    <item rdf:about="http://trashpanda.fisherflix.com/operations/veeam_dr?rev=1781706357&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-17T14:25:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>veeam_dr</title>
        <link>http://trashpanda.fisherflix.com/operations/veeam_dr?rev=1781706357&amp;do=diff</link>
        <description>Veeam CE Disaster Recovery Orchestration

Raid is not a backup. To protect the hypervisor configurations, Docker states, and critical application databases (Prowlarr, Sonarr, Plex), we utilize Veeam Backup &amp; Replication Community Edition running on VM-C (Windows Server 2022)</description>
    </item>
</rdf:RDF>
