<?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: OCUM 6.4P2 Database backup fails to create backup in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-6-4P2-Database-backup-fails-to-create-backup/m-p/126948#M22814</link>
    <description>&lt;P&gt;try below to see if helps:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Cause 1: After recent upgrade, perform the following steps:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Check to see if the link to&amp;nbsp;/usr/bin/mysqldump&amp;nbsp;has been removed. If so, add this link back during the upgrade script, as the link is removed but not added back.&lt;/LI&gt;&lt;LI&gt;Check the output from the following command:&lt;BR /&gt;ls -l /usr/bin | grep mysqldump&lt;/LI&gt;&lt;LI&gt;If this gives no output, then run the following command to fix:&lt;BR /&gt;ln -s /opt/mysql/server-5.6/bin/mysqldump /usr/bin/mysqldump&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Cause 2: If the backup fails even though there is a link to the mysqldump, perform the following steps:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;In some cases, it might be necessary to add an additional entry for jboss into the&amp;nbsp;/etc/sudoers&amp;nbsp;file. Add the following line to the&amp;nbsp;/etc/sudoers&amp;nbsp;file:&lt;BR /&gt;jboss ALL=(ALL) NOPASSWD: /usr/bin/mysqldump&lt;BR /&gt;The resulting output will look similar to the following:&lt;BR /&gt;[root@oum-xxx1 ocum-backup]# cat /etc/sudoers | grep jboss&lt;BR /&gt;jboss ALL=(ALL) NOPASSWD: /usr/bin/mysqldump&lt;BR /&gt;[root@oum-xxx1 ocum-backup]&lt;/LI&gt;&lt;LI&gt;If the customer has run the upgrade on the vApp from 6.3 -&amp;gt; 6.3P1, check to see if the link to&amp;nbsp;/usr/bin/mysqldump&amp;nbsp;has been removed. If so, add this link back during the upgrade script, as the link is removed but not added back.&lt;/LI&gt;&lt;LI&gt;Check the output from the following command:&lt;BR /&gt;ls -l /usr/bin | grep mysqldump&lt;/LI&gt;&lt;LI&gt;If this gives no output, then run the following command to fix:&lt;BR /&gt;ln -s /opt/mysql/server-5.6/bin/mysqldump /usr/bin/mysqldump&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Fri, 13 Jan 2017 05:50:38 GMT</pubDate>
    <dc:creator>Jeff_Yao</dc:creator>
    <dc:date>2017-01-13T05:50:38Z</dc:date>
    <item>
      <title>OCUM 6.4P2 Database backup fails to create backup</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-6-4P2-Database-backup-fails-to-create-backup/m-p/126562#M22741</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We recently installed OCUM 6.4 and there were no errors during installation . Now when we configured the DB backup it has been failing since 2 days with the same reason.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Error:&lt;/P&gt;&lt;P&gt;"Daily database backup 'UM_6.4P2_backup_unix_12-27-2016-14-00.7z' creation failed. Reason: Failed to create database backup using mysql utility."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestions?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 16:11:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-6-4P2-Database-backup-fails-to-create-backup/m-p/126562#M22741</guid>
      <dc:creator>NetappUser281</dc:creator>
      <dc:date>2025-06-04T16:11:52Z</dc:date>
    </item>
    <item>
      <title>Re: OCUM 6.4P2 Database backup fails to create backup</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-6-4P2-Database-backup-fails-to-create-backup/m-p/126948#M22814</link>
      <description>&lt;P&gt;try below to see if helps:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Cause 1: After recent upgrade, perform the following steps:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Check to see if the link to&amp;nbsp;/usr/bin/mysqldump&amp;nbsp;has been removed. If so, add this link back during the upgrade script, as the link is removed but not added back.&lt;/LI&gt;&lt;LI&gt;Check the output from the following command:&lt;BR /&gt;ls -l /usr/bin | grep mysqldump&lt;/LI&gt;&lt;LI&gt;If this gives no output, then run the following command to fix:&lt;BR /&gt;ln -s /opt/mysql/server-5.6/bin/mysqldump /usr/bin/mysqldump&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Cause 2: If the backup fails even though there is a link to the mysqldump, perform the following steps:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;In some cases, it might be necessary to add an additional entry for jboss into the&amp;nbsp;/etc/sudoers&amp;nbsp;file. Add the following line to the&amp;nbsp;/etc/sudoers&amp;nbsp;file:&lt;BR /&gt;jboss ALL=(ALL) NOPASSWD: /usr/bin/mysqldump&lt;BR /&gt;The resulting output will look similar to the following:&lt;BR /&gt;[root@oum-xxx1 ocum-backup]# cat /etc/sudoers | grep jboss&lt;BR /&gt;jboss ALL=(ALL) NOPASSWD: /usr/bin/mysqldump&lt;BR /&gt;[root@oum-xxx1 ocum-backup]&lt;/LI&gt;&lt;LI&gt;If the customer has run the upgrade on the vApp from 6.3 -&amp;gt; 6.3P1, check to see if the link to&amp;nbsp;/usr/bin/mysqldump&amp;nbsp;has been removed. If so, add this link back during the upgrade script, as the link is removed but not added back.&lt;/LI&gt;&lt;LI&gt;Check the output from the following command:&lt;BR /&gt;ls -l /usr/bin | grep mysqldump&lt;/LI&gt;&lt;LI&gt;If this gives no output, then run the following command to fix:&lt;BR /&gt;ln -s /opt/mysql/server-5.6/bin/mysqldump /usr/bin/mysqldump&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Fri, 13 Jan 2017 05:50:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-6-4P2-Database-backup-fails-to-create-backup/m-p/126948#M22814</guid>
      <dc:creator>Jeff_Yao</dc:creator>
      <dc:date>2017-01-13T05:50:38Z</dc:date>
    </item>
  </channel>
</rss>

