Claims
- 1. A method for managing replication of database changes between servers of a database network, each of the servers having a server identification for labeling database changes originated by said each server, the method comprising:detecting a restoration of a restored server of the database network from backup, the restored server having an old server identification for labeling database changes originated by the restored database before the restoration; assigning a new server identification different than the old server identification to the restored server for labeling database changes originated by the restored server after the restoration; and storing the old server identification of the restored server and backup data indicating an extent of backup of database changes labeled with the old server identification.
- 2. A method as in claim 1, wherein the backup data includes a backup sequence number set to be an update sequence number of a last database change stored for backup under the old server identification.
- 3. A method as in claim 2, further including:receiving from a destination server in the database network a replication request for database changes, the replication request including a replication watermark for database changes labeled with the old server identification; determining whether the replication watermark is below the backup sequence number; if the replication watermark is below the backup sequence number, sending to the destination server database changes made under the old server identification and between the replication watermark and the backup sequence number.
- 4. A method as in claim 3, further including sending database changes made by the restored server under the new server identification to the destination server.
- 5. A method as in claim 4, further including updating, by the destination server, a replication watermark for database changes under the new server identification of the restored server.
- 6. A method as in claim 1, further including storing, by the restored server, a replication watermark for the old server identification containing the old server identification and the backup sequence number thereof for replication from other servers of the database network.
- 7. A method as in claim 6, further including presenting, by the restored server, the replication watermark for the old server identification to the other database servers of the database network for replication.
- 8. A method as in claim 1, further including assigning an update sequence number greater than the backup sequence number to a database change made by the restored server subsequent to the restoration.
- 9. A method as in claim 8, wherein the update sequence number assigned to the database change made by the restored server subsequent to the restoration is consecutive to the backup sequence number.
- 10. A computer readable medium having computer executable instructions for a restored server of a database network to perform steps comprising:detecting a restoration from a backup; storing an old server identification used by the restored server at time of the backup for labeling database changes and a backup sequence number indicating an extent of backup of database changes by the restored server under the old server identification; assuming a new server identification for identifying the restored server after the restoration; and labeling database changes originated by the restored server after the restoration with the new server identification.
- 11. A computer readable medium as in claim 10, having further computer-executable instruction to perform the steps of:receiving a replication request from a destination server of the database network containing a replication watermark for the old server identification; and sending to the destination server database changes made under the old server identification and having update sequence numbers greater than said replication watermark and up to the backup sequence number.
- 12. A computer-readable medium as in claim 11, having further computer-executable instructions to perform the step of sending to the destination server database changes under the new server identification made by the restored server after the restoration.
- 13. A computer-readable medium as in claim 10, wherein the step of labeling includes assigning an update sequence number greater than the backup sequence number to a database change made by the restored server after the restoration.
- 14. A computer-readable medium as in claim 13, wherein the update sequence number assigned to the database change originated by the restored server subsequent to the restoration is consecutive to the backup sequence number.
- 15. A computer readable medium as in claim 10, having further computer-executable instructions to perform the step of storing the old server identification and the backup sequence number in a replication watermark for the old server identification.
- 16. A computer-readable medium having stored thereon a data structure, comprising:(a) a first data field containing a plurality of retired server identifications previously used by a server in a database network for labeling database changes originated by the database server for replication with other database servers of the database network; (b) a second data field containing data indicating an extent of restoration from backup of database changes made by the database server under each of the retired server identifications.
- 17. A computer-readable medium as in claim 16, wherein the retired server identifications are numbers uniquely identifying the server in the database network.
- 18. A computer-readable medium as in claim 17, wherein the data in the second data field includes a plurality of highest backup update sequence numbers associated with the retired server identifications.
CROSS REFERENCE TO RELATED APPLICATION
This application claims the benefit of U.S. Provisional Application Ser. No. 60/144,576 filed Jul. 19, 1999 abandonment.
US Referenced Citations (3)
Number |
Name |
Date |
Kind |
5721915 |
Sockut et al. |
Feb 1998 |
A |
5884322 |
Sidhu et al. |
Mar 1999 |
A |
6122630 |
Strickler et al. |
Sep 2000 |
A |
Provisional Applications (1)
|
Number |
Date |
Country |
|
60/144576 |
Jul 1999 |
US |