receive data and redo transactions step 304 is for parallel processing of redo transactions and database pages and is described in more detail below with reference to parallel process method 304 u2032 of fig4 a to 4d step 305 is for detecting when all database pages have been sent to the backup node and for notifying the backup node that no more pages will be sent step 306 is for acknowledging that all database pages have been received from the backup node and restored step 307 is for reverting back to normal procedure and for switching from a local to distributed commit protocol referring to fig4 a parallel process method 304 u2032 comprises logical process steps 304 a 1 304 a 2 304 a 3 304 a 4 304 f and method 304 b step 304 a 1 is for splitting the process into two separate processes that run in parallel a first process for sending database pages to the backup node starting at step 304 a 2 and a second process for handling redo transactions at method 304 b step 304 a 2 is for determining if a database page is clean or dirty unmodified or modified since the checkpoint image creation dirtyid index 204 is consulted if the database page is not listed in dirtyid index 204 then the page is clean and onto step 304 a 3 else the page is dirty and on to step 304 a 4 the database page is dirty if it is listed in dirtyid index 204 because it has been modified step 304 a 3 is for reading the database page.