<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Explosive Cloud</title>
    <link>https://explosive.cloud/</link>
    <description>Recent content on Explosive Cloud</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 11 Dec 2024 23:19:17 +0000</lastBuildDate>
    <atom:link href="https://explosive.cloud/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Accessing Veeam 13 Web UI via Cloudflare Tunnels</title>
      <link>https://explosive.cloud/accessing-veeam-13-web-ui-via-cloudflare-tunnels/</link>
      <pubDate>Wed, 11 Dec 2024 23:19:17 +0000</pubDate>
      <guid>https://explosive.cloud/accessing-veeam-13-web-ui-via-cloudflare-tunnels/</guid>
      <description>&lt;p&gt;Now that we know &lt;a href=&#34;https://explosive.cloud/first-look-at-veeam-backup-and-replication-13-on-linux/&#34;&gt;Veeam Backup and Replication 13&lt;/a&gt; will have its own special WEB UI, a thought crossed my mind: &amp;ldquo;How can I get visibility into my Veeam environment safely and securely?&amp;rdquo; One can use some form of traditional VPN, but maybe you don&amp;rsquo;t want to utilize any traditional VPN, or you don&amp;rsquo;t want a separate VPN just for Veeam. How about accessing your Veeam Backup and Replication 13 WEB UI with a Cloudflare Tunnel?&lt;/p&gt;</description>
    </item>
    <item>
      <title>First Look at Veeam Backup and Replication 13 on Linux</title>
      <link>https://explosive.cloud/first-look-at-veeam-backup-and-replication-13-on-linux/</link>
      <pubDate>Tue, 19 Nov 2024 22:56:52 +0000</pubDate>
      <guid>https://explosive.cloud/first-look-at-veeam-backup-and-replication-13-on-linux/</guid>
      <description>&lt;p&gt;Veeam has released a special build for V100 members to give us a first look at Veeam Backup and Replication 13 on Linux. Keep in mind that this is a preview build, and any/all functionality may change upon GA.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Installing Veeam Backup &amp;amp; Replication 12.2</title>
      <link>https://explosive.cloud/installing-veeam-12-2/</link>
      <pubDate>Tue, 17 Sep 2024 21:23:34 +0000</pubDate>
      <guid>https://explosive.cloud/installing-veeam-12-2/</guid>
      <description>&lt;p&gt;Just recently Veeam Backup &amp;amp; Replication version 12.2 was just released offering many new features and some very important security fixes! Here we will walk you through how to install Veeam 12.2.&lt;/p&gt;&#xA;&lt;h2 id=&#34;iso&#34;&gt;ISO&lt;/h2&gt;&#xA;&lt;p&gt;First, download the latest version from Veeam in ISO format from their downloads page. &lt;a href=&#34;https://www.veeam.com/products/downloads/latest-version.html&#34;&gt;https://www.veeam.com/products/downloads/latest-version.html&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying an Object First Appliance – WEB UI</title>
      <link>https://explosive.cloud/deploying-an-object-first-appliance-web-ui/</link>
      <pubDate>Tue, 10 Sep 2024 22:47:49 +0000</pubDate>
      <guid>https://explosive.cloud/deploying-an-object-first-appliance-web-ui/</guid>
      <description>&lt;p&gt;Now that we have racked and configured the first Object First OOTBI cluster, let&amp;rsquo;s look at the WEB UI.&lt;/p&gt;&#xA;&lt;h2 id=&#34;logging-in---first-time&#34;&gt;Logging in - First Time&lt;/h2&gt;&#xA;&lt;p&gt;The first time you log into the Object First WEB UI you get presented with a nice little wizard to walk you through everything you need to do to get your first bucket setup. It works well - you get what you need done, step by step. I wanted to poke around first, but I went through the wizard anyway, just to make sure I am getting the full OOTBI experience.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying an Object First Appliance – Configuration</title>
      <link>https://explosive.cloud/deploying-an-object-first-appliance-configuration/</link>
      <pubDate>Mon, 09 Sep 2024 19:11:37 +0000</pubDate>
      <guid>https://explosive.cloud/deploying-an-object-first-appliance-configuration/</guid>
      <description>&lt;h2 id=&#34;ipmi&#34;&gt;IPMI&lt;/h2&gt;&#xA;&lt;p&gt;First, you need to connect to the IPMI interface. You can either plug this into a network with DHCP enabled and connect to that DHCP-provided IP, or you can enter the setup menu during boot and configure the IPMI with a static IP. If you choose to go the DHCP route, you can always switch this to static later either via the IPMI web GUI or via the boot menu.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying an Object First Appliance - Unboxing</title>
      <link>https://explosive.cloud/deploying-an-object-first-appliance-unboxing/</link>
      <pubDate>Sun, 08 Sep 2024 20:05:50 +0000</pubDate>
      <guid>https://explosive.cloud/deploying-an-object-first-appliance-unboxing/</guid>
      <description>&lt;p&gt;So you&amp;rsquo;ve received your Object First Appliance. What now?&lt;/p&gt;&#xA;&lt;p&gt;First, we&amp;rsquo;re going to have to unbox it and deploy it. In the box, we get everything we need to set up our new OOTBI. Yes, OOTBI (Out of the box immutability). It is a silly name, but it has one goal - to provide you with a solid Veeam-compatible storage appliance with immutability enabled right from the start.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Veeam Service Provider Grafana Dashboard</title>
      <link>https://explosive.cloud/veeam-service-provider-grafana-dashboard/</link>
      <pubDate>Fri, 06 Sep 2024 19:38:31 +0000</pubDate>
      <guid>https://explosive.cloud/veeam-service-provider-grafana-dashboard/</guid>
      <description>&lt;p&gt;The newest release of Veeam v12.2 came with an unexpected twist - multiple &lt;a href=&#34;https://www.veeam.com/kb4649&#34;&gt;high level CVEs&lt;/a&gt; were reported to be fixed in Veeam v12.2. While security fixes are generally expected in every new release of any software, what was unexpected was this disclosure came so quickly after the Veeam 12.2 version was released.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Veeam Immutability - Governance Mode</title>
      <link>https://explosive.cloud/veeam-immutability-governance-mode/</link>
      <pubDate>Tue, 13 Aug 2024 20:33:59 +0000</pubDate>
      <guid>https://explosive.cloud/veeam-immutability-governance-mode/</guid>
      <description>&lt;p&gt;Immutability is an important component of any backup strategy. However, as an S3 provider, immutability can often leave you with data locked for a longer term than you really want.&lt;/p&gt;&#xA;&lt;h2 id=&#34;immutable-modes&#34;&gt;Immutable modes&lt;/h2&gt;&#xA;&lt;p&gt;Minio offers &lt;a href=&#34;https://min.io/product/data-immutability-for-object-storage&#34;&gt;three different immutability modes&lt;/a&gt; that can be enabled on objects.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NSX Upgrade Failure</title>
      <link>https://explosive.cloud/nsx-upgrade-failure/</link>
      <pubDate>Wed, 08 May 2024 19:05:39 +0000</pubDate>
      <guid>https://explosive.cloud/nsx-upgrade-failure/</guid>
      <description>&lt;h2 id=&#34;issue&#34;&gt;Issue&lt;/h2&gt;&#xA;&lt;p&gt;When upgrading our one production NSX 4.1.2.1 environment I ran into an interesting error trying to upgrade our Bare Metal Tier 0 nodes.&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Prepare edge upgrade bundle https://10.10.0.1/repository/4.1.2.3.0.23382408/Edge/nub/VMware-NSX-edge-4.1.2.3.0.23382424.nub failed on edge TransportNode UUID: clientType EDGE , target edge fabric node id UUID, return status Download and verify bundle failed with msg: Checking upgrade bundle /var/vmware/nsx/file-store/VMware-NSX-edge-4.1.2.3.0.23382424.nub contents Verifying bundle VMware-NSX-edge-4.1.2.3.0.23382424.bundle with signature VMware-NSX-edge-4.1.2.3.0.23382424.bundle.sig Failed to verify bundle: [&amp;#39;gpg&amp;#39;, &amp;#39;--homedir&amp;#39;, &amp;#39;/root/.gnupg&amp;#39;, &amp;#39;--verify&amp;#39;, &amp;#39;/tmp/tmpc75b6zcx/VMware-NSX-edge-4.1.2.3.0.23382424.bundle.sig&amp;#39;, &amp;#39;/tmp/tmpc75b6zcx/VMware-NSX-edge-4.1.2.3.0.23382424.bundle&amp;#39;] returned 2: b&amp;#34;gpg: Signature made Mon 26 Feb 2024 10:40:20 PM MST\ngpg: using RSA key E51BDAAAFDF4DC95\ngpg: Can&amp;#39;t check signature: No public key\n&amp;#34; .&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;However, my T1 edge nodes (which were set to upgrade first) had no problem with the same upgrade package. What a mystery!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tuning Minio - Ethernet Settings</title>
      <link>https://explosive.cloud/set-minio-rx-and-tx-buffers/</link>
      <pubDate>Fri, 09 Feb 2024 18:25:23 +0000</pubDate>
      <guid>https://explosive.cloud/set-minio-rx-and-tx-buffers/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;There are some tuning benefits you can utilize for your Minio deployments to make things a bit smoother. Here I&amp;rsquo;ll walk you through how to configure certain &amp;ldquo;ethtool&amp;rdquo; settings and have them persist across reboots, specifically on RX and TX buffers and coalescing values.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware Cloud Director - VAMI Backup Failure</title>
      <link>https://explosive.cloud/vmware-cloud-director-vami-backup/</link>
      <pubDate>Fri, 26 Jan 2024 16:26:20 +0000</pubDate>
      <guid>https://explosive.cloud/vmware-cloud-director-vami-backup/</guid>
      <description>&lt;h2 id=&#34;vmware-cloud-director-vami-backup&#34;&gt;VMware Cloud Director VAMI Backup&lt;/h2&gt;&#xA;&lt;p&gt;You may find yourself in a situation where you want to take a VMware Cloud Director VAMI Backup, but run into the error: Unable to create backup: A failure occured while creating the backup on the primary.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NSX - Node with the same IP already exists</title>
      <link>https://explosive.cloud/nsx-same-ip-already-exists/</link>
      <pubDate>Fri, 29 Sep 2023 14:29:07 +0000</pubDate>
      <guid>https://explosive.cloud/nsx-same-ip-already-exists/</guid>
      <description>&lt;h2 id=&#34;versions-for-posterity&#34;&gt;Versions, for posterity&lt;/h2&gt;&#xA;&lt;p&gt;vCenter 8.0.1 - build 22088981&lt;br&gt;&#xA;ESXi - 22088125&lt;br&gt;&#xA;NSX - 4.1.0.2&lt;/p&gt;&#xA;&lt;h2 id=&#34;backstory&#34;&gt;Backstory&lt;/h2&gt;&#xA;&lt;p&gt;I recently came across a rather interesting issue. Long story short, I needed to rebuild one of my NSX-prepared hosts. I put the host in maintenance mode, pulled it out of my NSX cluster, disconnected the host, and removed it from vCenter.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Minio and Veeam - Cleaning up Expired DeleteMarkers</title>
      <link>https://explosive.cloud/minio-and-veeam-cleaning-up-expired-delete-markers/</link>
      <pubDate>Mon, 14 Aug 2023 19:58:34 +0000</pubDate>
      <guid>https://explosive.cloud/minio-and-veeam-cleaning-up-expired-delete-markers/</guid>
      <description>&lt;h2 id=&#34;why-this-article-exists&#34;&gt;Why this article exists&lt;/h2&gt;&#xA;&lt;p&gt;I sought to answer a couple of questions for Veeam and Minio buckets:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;How much space does Veeam backups take up on a Minio-based Object Storage repository?&lt;/li&gt;&#xA;&lt;li&gt;How much does the Block Size setting make on space consumed?&lt;/li&gt;&#xA;&lt;li&gt;What are the object size distributions when the Block Size settings are changed?&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;In an effort to answer these questions, I came across an interesting discovery. When Veeam would delete objects that are no longer required due to retention policy settings, it left behind DeleteMarkers that would never get cleaned up. This amounted to a million DeleteMarkers being created in only two weeks. These expired DeleteMarkers are zero-byte objects that Minio has to deal with. Ouch. Most of the time, these DeleteMarkers are not causing much of a problem. They do not consume a lot of space, nor do they impact the performance of backups or restores.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Configuring VMware NSX Backups Using SSH Keys</title>
      <link>https://explosive.cloud/configuring-vmware-nsx-backups-using-ssh-keys/</link>
      <pubDate>Thu, 03 Aug 2023 22:30:35 +0000</pubDate>
      <guid>https://explosive.cloud/configuring-vmware-nsx-backups-using-ssh-keys/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; Starting with version 4.0, VMware NSX-T Data Center is known as VMware NSX.&lt;/p&gt;&#xA;&lt;p&gt;That&amp;rsquo;s important to note because when you google anything with NSX these days, you either get NSX-T documentation or NSX-v documentation. This post is about VMware NSX (Specifically NSX 4.1.0.2, but this should work on any NSX 4+ installation).&lt;/p&gt;</description>
    </item>
    <item>
      <title>There and Back Again (a Veeam Tale)</title>
      <link>https://explosive.cloud/there-and-back-again-a-veeam-tale/</link>
      <pubDate>Wed, 07 Jun 2023 17:48:56 +0000</pubDate>
      <guid>https://explosive.cloud/there-and-back-again-a-veeam-tale/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Today we are backing up on-premises vSphere VMs with Veeam direct to a Minio S3 bucket, then restoring that VM to a VMware Cloud Director ORG in the cloud. Once complete, we will then back that VM up direct to a Minio S3 bucket and recover it back to the on-premises vSphere deployment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Create a Grafana, Telegraph and InfluxDB Docker Compose</title>
      <link>https://explosive.cloud/create-a-grafana-telegraph-and-influxdb-docker-compose/</link>
      <pubDate>Thu, 11 May 2023 15:10:05 +0000</pubDate>
      <guid>https://explosive.cloud/create-a-grafana-telegraph-and-influxdb-docker-compose/</guid>
      <description>&lt;h2 id=&#34;setup-docker&#34;&gt;Setup Docker&lt;/h2&gt;&#xA;&lt;p&gt;Once you install the OS of your choosing, you will want to install Docker/Docker Compose. For this, we choose Centos 9 Stream, although the steps will be similar under any OS you choose.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Create a WordPress Site</title>
      <link>https://explosive.cloud/create-a-wordpress-site/</link>
      <pubDate>Sun, 11 Oct 2020 04:31:47 +0000</pubDate>
      <guid>https://explosive.cloud/create-a-wordpress-site/</guid>
      <description>&lt;p&gt;If you haven&amp;rsquo;t installed PHP, Apache, and MySQL, head over to &lt;a href=&#34;https://explosive.cloud/php-apache-mysql/&#34;&gt;this post&lt;/a&gt; first to see how to get that setup.&lt;/p&gt;&#xA;&lt;p&gt;I like to start to create a WordPress site by getting the WordPress database setup and a user account created specifically to access the newly created WordPress database.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Home</title>
      <link>https://explosive.cloud/home/</link>
      <pubDate>Sun, 11 Oct 2020 03:22:50 +0000</pubDate>
      <guid>https://explosive.cloud/home/</guid>
      <description></description>
    </item>
    <item>
      <title>Install PHP, Apache and MySQL on Ubuntu 16.04</title>
      <link>https://explosive.cloud/php-apache-mysql/</link>
      <pubDate>Sun, 11 Oct 2020 03:22:50 +0000</pubDate>
      <guid>https://explosive.cloud/php-apache-mysql/</guid>
      <description>&lt;p&gt;Sometimes you are stuck with an older OS. You can still get the most out of your server. Here we outline how to get a fully functional Wordpress installation running on Ubuntu 16.04.&lt;/p&gt;&#xA;&lt;p&gt;First, we start with the basics - get your Ubuntu updated.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Privacy Policy</title>
      <link>https://explosive.cloud/privacy-policy/</link>
      <pubDate>Sun, 11 Oct 2020 03:22:50 +0000</pubDate>
      <guid>https://explosive.cloud/privacy-policy/</guid>
      <description>&lt;h2 id=&#34;who-we-are&#34;&gt;Who we are&lt;/h2&gt;&#xA;&lt;p&gt;Our website address is: &lt;a href=&#34;http://explosive.cloud&#34;&gt;http://explosive.cloud&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-personal-data-we-collect-and-why-we-collect-it&#34;&gt;What personal data we collect and why we collect it&lt;/h2&gt;&#xA;&lt;h3 id=&#34;comments&#34;&gt;Comments&lt;/h3&gt;&#xA;&lt;p&gt;When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
