8/21/2023 0 Comments Data backup and restore![]() ![]() PITR only supports cluster-level restore and does not support database-level or table-level restore.PITR only supports restoring data to an empty cluster.This section describes the prerequisites for using TiDB backup and restore, including restrictions, usage tips and compatibility issues. Clone the production environment, which is convenient for troubleshooting, performance tuning, and simulation testing.Perform history data auditing to meet the requirements of judicial supervision.Handle the cases of misoperations from applications by rolling back data to a time point before the error event.Back up cluster data to a disaster recovery (DR) system with an RPO as short as 5 minutes, reducing data loss in disaster scenarios.On this basis, to further ensure data safety, TiDB provides the Backup & Restore (BR) feature as the last resort to recover data from natural disasters and misoperations. When a few nodes in the cluster fail, the cluster can still be available. While not sufficient for low recovery time objective (RTO) use cases, it can be used for a hot/cold restoration scenario where an RPO on the order of minutes is desirable.Based on the Raft protocol and a reasonable deployment topology, TiDB realizes high availability of clusters. Full system backups can also be run periodically (perhaps monthly) in order to capture a snapshot of the state of the server(s) should a catastrophe strike that requires a full system restoration.Ī live data backup is appropriate in order to frequently capture the state of the application data in order to provide rapid restoration of a previous state in case of a failure. Live Data Backups: Only Appian application data directories listed in the live data backup procedure, the RDBMS data, and, optionally, the log files are backed up.Ī full system backup is appropriate when upgrading Appian or applying a patch/hotfix.Full System Backups: The entire server hosting Appian is backed up, which includes Appian application data, logs, and Appian software and other executable artifacts that are provided by the installer. ![]() Use your preferred backup mechanism for the specific RDBMS used in the Appian environment. External data sourcesĪll external data sources used with Appian must be backed up separately and simultaneously. The folders containing this application data should be backed up at the same time. Appian application dataĪpplication data comprises files stored on the server that are referenced by Appian engines, including documents stored in the document management system, archived processes, search indices, the keystore file, data managed by the data service, and other data files. Otherwise, you might encounter synchronization issues. This ensures that during recovery the system's data snapshot is synchronized and consistent. When scheduling a script to backup the Appian data, external databases must be backed up at the same time. Appian application data (documents, archived processes, and other files)Įach of these components is backed up separately, yet all backups must occur simultaneously so that data can be restored in a consistent state.There are two primary data components that should be backed up: Instead, the High Availability configuration should be used for disaster recovery with low RPO requirements. While backups are an approach to achieving an RPO on the order of hours, it is not the preferred method for achieving very low RPOs (minutes). This concept is referred to as the Recovery Point Objective (RPO). If you back up nightly, the most data you might lose is one day's worth. Using backups to preserve data when a catastrophic event occurs requires more frequent backups that ultimately depend on how much data you are willing to lose when restoring the data. The frequency of conducting backups depends on the use case.įor data archival and auditing purposes, backing up weekly or even monthly may be sufficient. The main reasons for backing up Appian installations and related data are for data archival and auditing purposes and as a protection against catastrophic events. This page outlines the backup process for Appian documents and data. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |