In the Domino Change Manager, these demand sets are titled "database move sequences." Each database move sequence has a maximum of 25 moves. The contents of each move sequence is generated automatically. You can see these database move sets when you submit a resource-balancing plan to the Domino Change Manager. You can restructure the contents by cutting and pasting the demands from one demand set into another or by creating additional demand sets and new demands. (To cut and paste, select a demand and use the Edit menu.) The Domino Administrator creates as many of these demand sets as needed to accomplish a move. For example, the Acme Move Plan includes 55 database moves, so the Domino Change Manager creates three database move sequences -- two that include 25 moves, and one that includes 5 moves.
You can determine whether the database moves and database move sequences are executed sequentially or concurrently or any combination of the two. By default, all are moved concurrently. Using the Acme Move Plan example, the Domino Change Manager attempts to perform all three database move sequences at the same time. Within each database move sequence, the Domino Change Manager attempts to move all databases at the same time.
What happens if a move fails
A database move can fail for a number of reasons. For example, a database move fails if a server is down, if the destination server does not have create replica rights, or if the source database has been manually moved or deleted. How the Domino Change Manager handles the failure depends on how the moves are executed: