I have discovered over the years that protecting a file, its content, and developing in a controlled, deliberate method is usually something good to keep in mind. I have learned that if I feel an document, project… is important, then to backup the data and then do the edit is the methodology I need to learn.
When I decide to backup a file, first thing I do is to see if there is a
_vault directory. In any location where I had to backup previously, I created this directory. After the first time I did this I realized I was going to have to number these file backups. I reasoned out that
filename_[0-9][0-9] would be a format that would be sufficient, if there was an extension it would be
As I could see that file backups were something that I would regularly do, I decided to create a script that would automate this task. It tests the destination directory if the file exists. For the first backup, the script prepends
00 to the file, after that its prepend the sequential number.
The usage is basic: I define the source file and optionally the destination directory. The current directory is assumed if only the source file is specified.
$ bckfile file.txt _vault ‘file.txt’ -> ‘_vault/file_01.txt’
The script does have one limitation: the filename can only contain one period and it must be for the extension. This is necessary as determination for an otherwise intention would take a lot of work 😊.
bckfile can be found in my general scripts repository.