# Which database DevOps software has reliable rollback mechanisms to protect against failed deployments and data loss?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Rollback is the feature you hope never to use and cannot afford to have fail, so I looked at which database DevOps tools reviewers actually trust to protect against failed deployments and data loss. From the<a class="a a--md" elv="true" href="https://www.g2.com/categories/database-devops-software"> </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/database-devops-software">database DevOps software</a> category:</p><ol>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/liquibase/reviews"><strong>Liquibase</strong></a>: reviewers cite rollbacks that automatically reverse changes. Did rollback stay reliable on large or interdependent changesets?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/harness-platform/reviews"><strong>Harness Platform</strong></a>: automated rollback that reverts a failed deploy without manual steps. Did it catch failures before users did?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/redgate-flyway/reviews"><strong>Redgate Flyway</strong></a>: versioned migrations, though reviewers note advanced rollback is a paid-tier feature. Did the free rollback path cover you, or did you upgrade?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/dbmaestro-dbmaestro-devops-platform/reviews"><strong>DBmaestro DevOps Platform</strong></a>: release automation with audit trails to trace what changed. Did that help you recover cleanly after a bad release?</li>
</ol><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">For anyone who hit a failed deployment, which tool's rollback actually saved you? And did it protect data, or just revert schema?</p>

##### Post Metadata
- Posted at: 29 days ago
- Author title: Marketer
- Net upvotes: 1


## Comments
### Comment 1

Yeah rollback is the scary part of database automation, so it&#39;s the right thing to focus on. Redgate Flyway and Liquibase are the two most associated with this, both are built around versioned migrations and support undo or rollback of changes, so a failed deployment can be reversed in a controlled way rather than by hand. Liquibase has explicit rollback commands and tagging, and Flyway supports undo migrations. Honest caveat you need to hear though: not every database change is cleanly reversible, dropping a column or transforming data can&#39;t always be undone without a backup, so rollback tooling protects schema changes far better than it protects lost data. So pair whatever you pick with solid backups and test rollbacks in a staging environment before trusting them in production. Are your risky changes mostly schema, or data migrations? That determines how much you can lean on rollback alone.

##### Comment Metadata
- Posted at: 18 days ago





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4