Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to solve Sequoiadb backupOffline-related problems". In daily operation, I believe many people have doubts about how to solve Sequoiadb backupOffline-related problems. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts about "how to solve Sequoiadb backupOffline-related problems". Next, please follow the editor to study!

[question 1]

The current backupOffline method of sdb supports incremental backup without blocking read and write requests to the database.

If there are the following scenarios

1 yesterday's backup lsn was 1000

2 when performing incremental backups today, the lsn is 1200

3 during the incremental backup, the lsn changes to 1300

Then this incremental backup, is the backup lsn from 1000-1200, or 1000-1300?

[question 2]

The current backupOffline method supports the execution of group for backup, as well as full cluster backup.

I understand that both full cluster backup and designated group backup are found by the database for each group.

The master node makes related backups.

In other words, the backupOffline method relies on the master node.

Because the incremental backup depends on the lsn number of the last backup point, how will the database behave if the master node of a group changes when the user performs this incremental backup?

If you do an incremental backup in a full cluster, suppose there are three group, and only one of the group's master has been switched. For the other two group, will a new incremental backup file be generated? Or will it be rolled back automatically?

[solution]

Question 1:

During the incremental backup, if the database is still in operation, it is possible to back up some of the operations successfully, that is, the lsn of the backup is between 1000 and 1300.

Question 2:

1. In the process of performing an incremental backup, the master of the node will not affect the backup process. The result of the backup is that the original master node produces incremental backup.

2. In the case of full backup of the full cluster, for example, group1/2/3 has made a full backup, that is, the master node of each group has made a full backup, and then a master node of group has changed. For example, if the master node of group1 switches from machine A to machine B, and the global incremental backup is carried out at this time, the other two group will still be backed up successfully, but only the master node of the host group1 fails. Because its new master node does not have a full backup when performing an incremental backup, it throws a-264 error, which can be viewed in more detail through getLastErrObj ().

[supplementary questions]

Solution 2 mentions:

Incremental backup of primary node with primary group1 failed because its new primary node found that there were no full backups during incremental backup.

I would like to ask how to determine whether the node has a full backup, by checking whether there are full backup files in the backup directory?

[solution]

Check whether the node has a full backup. You can view the backup information through db.listBackup (). If the backup information of the changed node contains "EnsureInc": false, then the backup is a full backup file.

At this point, the study of "how to solve Sequoiadb backupOffline-related problems" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.