<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Problem with appliance backup in HPE Morpheus VM Essentials Software</title>
    <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272783#M2853</link>
    <description>&lt;P&gt;Hi Calvin,&lt;/P&gt;&lt;P&gt;thank you for your reply.&lt;/P&gt;&lt;P&gt;Yes, the problem was introduced after upgrading from 9.0.1 --&amp;gt; 9.0.2&lt;/P&gt;&lt;P&gt;I have tested the DB connection using passwd from&amp;nbsp;/etc/morpheus/morpheus-secrets.json&lt;/P&gt;&lt;P&gt;root@vmem:~# /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -p -h 127.0.0.1 morpheus&lt;/P&gt;&lt;P&gt;The connection is OK. So where can i change the password used in the backup job?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jirka&lt;/P&gt;</description>
    <pubDate>Tue, 15 Sep 2026 13:19:50 GMT</pubDate>
    <dc:creator>jkre</dc:creator>
    <dc:date>2026-09-15T13:19:50Z</dc:date>
    <item>
      <title>Problem with appliance backup</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272543#M2823</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;since&amp;nbsp;upgrading to 9.0.2 the backup job "Morpheus Appliance" is failing. Does anyone know the reason?&lt;/P&gt;&lt;P&gt;Jirka&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2026 08:02:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272543#M2823</guid>
      <dc:creator>jkre</dc:creator>
      <dc:date>2026-09-09T08:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with appliance backup</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272662#M2834</link>
      <description>&lt;DIV&gt;&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've seen a few cases where backup jobs start failing right after an upgrade, but it's difficult to say if this is a general 9.0.2 issue or something specific to your environment.&lt;/P&gt;&lt;P&gt;Could you share the exact error message from the &lt;STRONG&gt;Morpheus Appliance&lt;/STRONG&gt; backup job or any related logs? That would help narrow it down.&lt;/P&gt;&lt;P&gt;Also, did the backup work normally before the upgrade, and did anything else change besides moving to 9.0.2?&lt;/P&gt;&lt;P&gt;A little more detail should help the community point you in the right direction.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 11 Sep 2026 12:53:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272662#M2834</guid>
      <dc:creator>Cparra_</dc:creator>
      <dc:date>2026-09-11T12:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with appliance backup</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272681#M2836</link>
      <description>&lt;P&gt;Agree with&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2440105"&gt;@Cparra_&lt;/a&gt;&amp;nbsp;that more information is needed to understand what is going on. I asked my Copilot notebook based on v9.0.1 documentation and it suggests (along with more details) the following:&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;There are a few things I'd check:&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The appliance backup job backs up the Morpheus database and is controlled from &lt;STRONG&gt;Administration &amp;gt; Settings &amp;gt; Backups &amp;gt; Backup Appliance&lt;/STRONG&gt;. The docs note that appliance backups have a &lt;STRONG&gt;hard 2-hour timeout&lt;/STRONG&gt;, and backups exceeding that limit will be abandoned and marked failed.&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;The v9.0.1 release notes include several upgrade-related fixes, including an issue where upgrades could fail when database connections were closed unexpectedly and another where appliance upgrades could fail because of service/plugin issues. While not backup-specific, they suggest checking appliance health after the upgrade, especially database and queue health.&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;I'd also verify the backup target (bucket or file share). Appliance backups write the Morpheus database dump to the configured storage target, so connectivity, credentials, or storage availability issues could cause failures.&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Check &lt;STRONG&gt;Administration &amp;gt; Health&lt;/STRONG&gt; for database, storage, and RabbitMQ queue warnings, and review the appliance logs under &lt;STRONG&gt;Administration &amp;gt; Health &amp;gt; Morpheus Logs&lt;/STRONG&gt; around the time the backup job runs. The documentation specifically points to these locations for troubleshooting appliance issues.&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;If the environment was just upgraded, I'd also confirm that all host/agent updates recommended after the upgrade were completed. The release notes specifically recommend verifying HVM host agent upgrades after upgrading the appliance.&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;
&lt;DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;One additional thing to check is appliance backup health. The documentation notes that appliance backups have a hard two-hour execution limit, and any backup that exceeds that limit will fail. If the appliance database has grown significantly or storage performance/access characteristics have changed over time, it's possible a backup that previously completed successfully is now timing out.&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;It may also be worth reviewing &lt;STRONG&gt;Administration &amp;gt; Health &amp;gt; VM Essentials Health&lt;/STRONG&gt; for any warnings or errors. The health checks specifically monitor database connectivity, storage utilization, memory usage, Elasticsearch/OpenSearch health, and RabbitMQ queue backlogs, any of which could contribute to backup-related failures.&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Was the backup failure immediate after the upgrade, or did it begin sometime later? Are there any relevant messages in the appliance logs around the time the backup job fails?&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Can you share the actual error message from the failed backup job? That will probably narrow it down quickly.&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 11 Sep 2026 14:25:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272681#M2836</guid>
      <dc:creator>CalvinZito</dc:creator>
      <dc:date>2026-09-11T14:25:43Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with appliance backup</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272740#M2846</link>
      <description>&lt;P&gt;Thank you for your comments. The exact error is:&lt;/P&gt;&lt;P&gt;mysqldump: Got error: 1045: Access denied for user 'morpheus'@'localhost' (using password: YES) when trying to connect.&lt;/P&gt;&lt;P&gt;Health status is OK&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2026 13:55:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272740#M2846</guid>
      <dc:creator>jkre</dc:creator>
      <dc:date>2026-09-14T13:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with appliance backup</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272747#M2849</link>
      <description>&lt;DIV&gt;
&lt;DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;I gave my Copilot notebook the additional information and here's what it comes back with.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;This suggests the backup job is failing because the appliance cannot authenticate to the local database using the &lt;CODE&gt;morpheus&lt;/CODE&gt; database account. The backup process relies on creating a MySQL dump of the appliance database, so if database authentication fails, the appliance backup cannot start.&lt;/EM&gt;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;A few things I'd check:&lt;/EM&gt;&lt;/DIV&gt;
&lt;OL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;&lt;STRONG&gt;Was the problem introduced immediately after upgrading to 9.0.2?&lt;/STRONG&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;EM&gt;If backups worked prior to the upgrade and failed immediately afterward, it's possible the database credentials stored for the backup process no longer match the credentials configured in MySQL.&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;&lt;STRONG&gt;Verify appliance health&lt;/STRONG&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;EM&gt;Navigate to &lt;STRONG&gt;Administration &amp;gt; Health&lt;/STRONG&gt; and check the Database status. The VM Essentials Health page specifically monitors database connectivity and database health indicators. Any database access or connection issues should show up there.&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;&lt;STRONG&gt;Check the Morpheus secrets file&lt;/STRONG&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;EM&gt;The documentation shows that the appliance stores the Morpheus database password in:&amp;nbsp;/etc/morpheus/morpheus-secrets.json&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="___hy8ozz0 f10pi13n f1koksc9 ffwt4oh frbg12y fgutdgb f159t74k f1irbtxz fml94gg f14e36gq f17qsv72 fcwkhs0 f19q529j fr8ou9z f1ccdub3 f1pfoh9j f1511p4b"&gt;
&lt;DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="-1" role="group" aria-label="Code Preview"&gt;
&lt;DIV class="scriptor-component-code-block d070bad42a6e0a1f scriptor-codeblock-virtualized" tabindex="-1"&gt;
&lt;DIV class="f1422389f8ad26be _8cfd0b13468ba9a7 _5523e654b3bbae7d a1ab1e8feefdde43"&gt;
&lt;DIV class="_78573113eb47589f a9860a7618f70ba6 _83b20678a526fd51"&gt;
&lt;DIV class="f8ceb055160b69aa" data-virtualized-code-find-root="true"&gt;
&lt;DIV class="_93fd5d342ee3198c"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;During restore procedures, the documented method is to retrieve the &lt;CODE&gt;morpheus_password&lt;/CODE&gt; value from that file and use it to connect to the database.&lt;/EM&gt;&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;&lt;STRONG&gt;Test the database account manually&lt;/STRONG&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;EM&gt;From the appliance shell, try connecting using the credentials stored in &lt;CODE&gt;morpheus-secrets.json&lt;/CODE&gt;:&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="___hy8ozz0 f10pi13n f1koksc9 ffwt4oh frbg12y fgutdgb f159t74k f1irbtxz fml94gg f14e36gq f17qsv72 fcwkhs0 f19q529j fr8ou9z f1ccdub3 f1pfoh9j f1511p4b"&gt;
&lt;DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="-1" role="group" aria-label="Code Preview"&gt;
&lt;DIV&gt;
&lt;DIV class="scriptor-component-code-block d070bad42a6e0a1f scriptor-codeblock-virtualized" tabindex="-1"&gt;
&lt;DIV class="a587fd52497c13aa"&gt;
&lt;DIV class="rrd10u0 fui-AriaLive__assertive" aria-live="assertive"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="f1422389f8ad26be _8cfd0b13468ba9a7 _5523e654b3bbae7d a1ab1e8feefdde43"&gt;
&lt;DIV class="_78573113eb47589f a9860a7618f70ba6 _83b20678a526fd51"&gt;
&lt;DIV class="f8ceb055160b69aa" data-virtualized-code-find-root="true"&gt;
&lt;DIV class="_9669cf2af21203bd d14c3c05a375c369 _43ad1bf50028cc19 _2f94a5565f6d0290 _84e714c3b0b6d1e5" tabindex="0" role="textbox" aria-label="Code editor" aria-multiline="true" aria-readonly="true"&gt;
&lt;DIV class="_869c5746d80d20b1 _2172f00c4881ce5b" data-line-index="0"&gt;&lt;EM&gt;mysql -u morpheus -p -h 127.0.0.1 morpheus&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="_93fd5d342ee3198c"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;If that login fails, you've likely identified the root cause: the password in the appliance configuration and the password configured in MySQL are no longer in sync.&lt;/EM&gt;&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;&lt;STRONG&gt;Review appliance logs&lt;/STRONG&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;EM&gt;Check &lt;STRONG&gt;Administration &amp;gt; Health &amp;gt; Morpheus Logs&lt;/STRONG&gt; around the time the backup runs to see whether there are additional database authentication or credential-related errors. The documentation specifically points to this area for appliance troubleshooting.&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;At this point I would focus almost entirely on resolving the database authentication issue rather than things like backup targets, storage connectivity, or the 2-hour backup timeout. Those can certainly cause backup failures, but the &lt;CODE&gt;1045 Access denied&lt;/CODE&gt; message is occurring earlier in the process and is likely the primary problem.&lt;/EM&gt;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;Can you share:&lt;/EM&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;EM&gt;Whether this started immediately after the 9.0.2 upgrade, and&lt;/EM&gt;&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;&lt;EM&gt;The output of a manual MySQL login test using the &lt;CODE&gt;morpheus&lt;/CODE&gt; account?&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&lt;EM&gt;That will tell us very quickly whether we're dealing with a credential mismatch versus a broader database issue.&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2026 21:26:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272747#M2849</guid>
      <dc:creator>CalvinZito</dc:creator>
      <dc:date>2026-09-14T21:26:15Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with appliance backup</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272783#M2853</link>
      <description>&lt;P&gt;Hi Calvin,&lt;/P&gt;&lt;P&gt;thank you for your reply.&lt;/P&gt;&lt;P&gt;Yes, the problem was introduced after upgrading from 9.0.1 --&amp;gt; 9.0.2&lt;/P&gt;&lt;P&gt;I have tested the DB connection using passwd from&amp;nbsp;/etc/morpheus/morpheus-secrets.json&lt;/P&gt;&lt;P&gt;root@vmem:~# /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -p -h 127.0.0.1 morpheus&lt;/P&gt;&lt;P&gt;The connection is OK. So where can i change the password used in the backup job?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jirka&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2026 13:19:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-vm-essentials/problem-with-appliance-backup/m-p/7272783#M2853</guid>
      <dc:creator>jkre</dc:creator>
      <dc:date>2026-09-15T13:19:50Z</dc:date>
    </item>
  </channel>
</rss>

