<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>DR .kdb files</title><link>https://community.appian.com/discussions/f/best-practices/14998/dr-kdb-files</link><description>We tried to test our DR system over the weekend and quickly determined that the data we were seeing was from 2017. We did not realize that the .kdb files were out of date. We back up out .kdb files to the DR server every four hours. In looking at the</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: DR .kdb files</title><link>https://community.appian.com/thread/67067?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 19:58:13 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:467d0492-87bb-49b7-a360-be2873474cb1</guid><dc:creator>ericg329</dc:creator><description>&lt;p&gt;If you haven&amp;#39;t already, I would also suggest taking a look at some of the Playbook articles on DR.&lt;/p&gt;
&lt;p&gt;&lt;a href="/w/the-appian-playbook/180/setting-up-for-disaster-recovery"&gt;https://community.appian.com/w/the-appian-playbook/180/setting-up-for-disaster-recovery&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/w/the-appian-playbook/205/high-availability-and-disaster-recovery-configurations#Disaster_Recovery_Configurations"&gt;https://community.appian.com/w/the-appian-playbook/205/high-availability-and-disaster-recovery-configurations#Disaster_Recovery_Configurations&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;As Eliot mentioned, you only need the most recent kdb files to start up with the 5/6/2019 data. Appian is going to utilize the most recent kdb file when starting the engines. Copying over all kdb files for a given engine will just waste disk space. You also need to make sure your database(s) has the appropriate data to match the kdb files you plan to use.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DR .kdb files</title><link>https://community.appian.com/thread/67060?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 18:26:50 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c7ba62e3-0d28-42d7-8cb2-c992b87aa17b</guid><dc:creator>Eliot Gerson</dc:creator><description>&lt;p&gt;I&amp;#39;d recommend reviewing the documentation on backup and restoration&amp;nbsp;&lt;a href="https://docs.appian.com/suite/help/19.2/Configuring_Backup_and_Restoration.html"&gt;https://docs.appian.com/suite/help/19.2/Configuring_Backup_and_Restoration.html&lt;/a&gt;&amp;nbsp; . Following the documented procedures will ensure that your data is appropriately backed up.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Any given backup will always be up to date as of when the backup was created. So, a backup taken today will have all data up until now, regardless of whether that data was created yesterday or 10 years ago. But if you wanted to revert to a specific point in time (for example, to try and recover deleted data), you would need a backup from that specific point in time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>