Design pattern to model transactions

There is a set of tasks I need to execute as an atomic transaction. i.e while executing the tasks, if any task fails, I need to revert the changes done during the previous tasks and exit without executing the subsequent tasks. This is similar to how DB transactions are handled. Is there a well known design pattern to address this case ?

P.S. I tried to search on internet but got a bunch of research papers, since the question must be common to most of the systems, I m just checking whether there is a known recommended method to solve this problem.