<?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: DB corruption after power failure? in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24358#M1881</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I thought this behavior was no longer happening, we had this type of corruption quite a lot with 2012 appliances (like 2200 and 4x00) in Asian and African countries where power outages are quite often happening. The problem occurs when a writew action is taking place during the power cut. Mostly the only way to recover is a reinstall, either from USB or from a snapshot.&lt;/P&gt;&lt;P&gt;When you're lucky you might be able to recover using fsck while booted in maintenance mode.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jan 2019 13:58:26 GMT</pubDate>
    <dc:creator>Maarten_Sjouw</dc:creator>
    <dc:date>2019-01-14T13:58:26Z</dc:date>
    <item>
      <title>DB corruption after power failure?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24357#M1880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello friends,&lt;/P&gt;&lt;P&gt;&amp;nbsp;we had a power issue in one of our sites due to UPS issue, checkpoint 5200 appliance running as a gateway rebooted, it came up without security policy , fw stat - showed as "default policy" and it didn't pass any traffic. It also lost the connection with mgmt server. Resetting SIC didn't help, as when I pushed policy I got error "load on module failed". I had to restore the gateway to factory defaults to get it back working. This was the second time we faced such an issue, earlier with a different site. Worked with TAC, they said some DB corruption and did the same (restored to factory defaults) as a fix. Is there a way we can avoid this kind of corruption ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Nishad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jan 2019 12:42:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24357#M1880</guid>
      <dc:creator>Nishad_Abooback</dc:creator>
      <dc:date>2019-01-14T12:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: DB corruption after power failure?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24358#M1881</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I thought this behavior was no longer happening, we had this type of corruption quite a lot with 2012 appliances (like 2200 and 4x00) in Asian and African countries where power outages are quite often happening. The problem occurs when a writew action is taking place during the power cut. Mostly the only way to recover is a reinstall, either from USB or from a snapshot.&lt;/P&gt;&lt;P&gt;When you're lucky you might be able to recover using fsck while booted in maintenance mode.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jan 2019 13:58:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24358#M1881</guid>
      <dc:creator>Maarten_Sjouw</dc:creator>
      <dc:date>2019-01-14T13:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: DB corruption after power failure?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24359#M1882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree. On such sites I with risk of power failure I would always have a snapshot on local and external disk. Then you're back in business fairly quickly - just boot using snapshot&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jan 2019 21:53:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24359#M1882</guid>
      <dc:creator>Kaspars_Zibarts</dc:creator>
      <dc:date>2019-01-14T21:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: DB corruption after power failure?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24360#M1883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2019 09:39:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DB-corruption-after-power-failure/m-p/24360#M1883</guid>
      <dc:creator>Nishad_Abooback</dc:creator>
      <dc:date>2019-01-15T09:39:12Z</dc:date>
    </item>
  </channel>
</rss>

