by Dmitry Kirsanov
7. March 2019 12:44
I think every system administrator is doing this often enough to think about automating it. When you make changes to file, deploy a new version and not sure if you’ll need to revert, and there is a number of previous copies that you would like to keep track of.
This little command line utility does exactly that – it creates the .bak file for whatever file, maintains any number of older backups (.bak1, .bak2 and so on), restores from .bak (this will also rename .bak2 to .bak1 and all older versions too), deletes all backups if needed, and can also keep backups in different directory – for cases when you are modifying file in publicly available directory or just don’t like clutter.
Get more information and binary on utility page