In the digital age, data is considered one of the most valuable assets. However, as data continues to grow and become more complex, the risk of accidental data loss or damage also increases accordingly. To ensure the reliability and security of data, backing up data has become a necessary measure. But merely backing up data is not enough; we also need to consider how to perform database disaster recovery. Database disaster recovery typically refers to measures taken to protect the availability and integrity of a database in the event of a disaster. So, do you back up your data? What reasons would you consider for database disaster recovery? Let’s take a look at this important topic.
This Topic:
Do you back up your data? What reasons would you consider for disaster recovery?
Activity Rewards:
Participation Award
Participate in this discussion to receive 30 points as a reward.
Activity Time:
2023.11.24 - 2023.12.01
The Chat Tea Party is about to reach 100 sessions!
In the 101st session, the Chat Tea Party will select the top participants to receive our Ti Speaking Badge + Mystery Merchandise.
Do you back up your data? What reasons would you consider for disaster recovery?
Not backing up is like running naked, the consequences are catastrophic!
In terms of disaster recovery, business-level disaster recovery generally requires additional considerations beyond the construction of IT systems. Therefore, from an IT perspective, business-level disaster recovery is not the top priority. However, data-level disaster recovery must be considered, ranging from primary-backup real-time, local disaster recovery, to off-site, and finally two-site three-center setups, because data is the most important IT information asset.
Backup: To address potential data loss caused by various reasons such as hardware failures, software bugs, human errors, malicious attacks, etc.
Disaster Recovery: Business continuity requirements, security compliance requirements, and to cope with regional disasters like fires, earthquakes, floods, etc.
Of course, the data will be backed up; otherwise, we would have no choice but to run away.
The necessity of disaster recovery is also related to cost. The basic consideration is the inability to use the data due to reasons such as data center failures or cloud failures, and the cost is not sufficient to maintain a multi-location, multi-center architecture.
The transaction system needs to be backed up. Previously, we used Oracle RAC with dual servers and dual storage mirroring, same-city disaster recovery, and both logical and physical backups. In the future, when we switch to TiDB, we also plan to have the full set, including same-city disaster recovery, logical backups, physical backups, etc.
Data definitely needs to be backed up, but it depends on whether the conditions allow it. If not, then create the conditions! A database crash once pushed for the allocation of resources, and then we implemented dual-cluster disaster recovery backups.
If you’ve experienced database crashes, abnormal data loss, and the anxiety that comes with it, you will naturally consider disaster recovery, or even active-active setups.
The first rule of a DBA: Backup is more important than anything.
So backups must be done.
As for disaster recovery, it needs to be weighed based on the importance of the data and the cost of disaster recovery.
Backup is definitely necessary. For relatively mature solutions, CDP/CDM backup is used, which can both back up and perform disaster recovery drills to prevent data loss or ransomware encryption.
|
username: Billmay表妹
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: