DR .kdb files

Question

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 backed up .kdb files. There are presently 36 .kdb files for one of the engines dated from 31/5/2019 to today 5/6/2019. If we were to copy those .kdb files to the application folder, would the DR system then be up to date wilt all data between 2017 and the most recent .kdb files.

Eliot Gerson · Accepted Answer

I'd recommend reviewing the documentation on backup and restoration https://docs.appian.com/suite/help/19.2/Configuring_Backup_and_Restoration.html . Following the documented procedures will ensure that your data is appropriately backed up. 
 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.

ericg329 · Answer

If you haven't already, I would also suggest taking a look at some of the Playbook articles on DR. 
 https://community.appian.com/w/the-appian-playbook/180/setting-up-for-disaster-recovery 
 https://community.appian.com/w/the-appian-playbook/205/high-availability-and-disaster-recovery-configurations#Disaster_Recovery_Configurations 
 
 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.

DR .kdb files

Top Replies