@Kusalananda Yes, I expect there are many such projects. There might be lists somewhere.
The SETI@home Wikipedia page mentions in a couple.
> SETI@home was released to the public on May 17, 1999,[5][6][7][8] making it the third large-scale use of distributed computing over the Internet for research purposes, after Great Internet Mersenne Prime Search (GIMPS) was launched in 1996 and distributed.net in 1997. Along with MilkyWay@home and Einstein@home, it is the third major computing project of this type that has the investigation of phenomena in interstellar space as its primary purpose.
This is a list of distributed computing and grid computing projects. For each project, donors volunteer computing time from personal computers to a specific cause. The donated computing power comes typically from CPUs and GPUs, but can also come from home video game systems. Each project seeks to solve a problem which is difficult or infeasible to tackle using other methods.
== Distributed computing projects ==
=== Active projects ===
=== Inactive projects ===
(Work on these projects was either finished, or the project was discontinued).
== Grid computing projects ==
While distribut...
Given that the entry level for the 500 fastest computers in the world is .14 petaflops, some of the distributed projects in the list have enough power to be listed in the 500 list.
Database System Concepts says
The basic scheme is to dump the entire contents of the database to stable
storage periodically—say, once per day. For example, we may dump the database
to one or more magnetic tapes. If a failure occurs that results in the loss of physical
database blocks, ...
@Tim The answer to "why" is in the question: "when migrating data to a different instance of the database, or to a different version of the database software"
The answer to "how" is also in the question, you dump the contents to one or several files and then load them in again, possibly on another machine or into another database instance, or to replace the current data.
How this is practically done depends on the type of database being used. With MySQL databases, you would use mysql_dump to dump the data. The output would be in the form of INSERT statements that could, at a later date, be fed into the mysql client to restore the data.