Post by George on May 12, 2019 13:33:58 GMT -5
Another release today. There's a bunch of bug fixes as usual, but the main objective was to release a revised bunch of code for the Backup and Restore that was released in the V10.2.19109 release.
Following the last release, we realized Backup and Restore could have been done a lot better. So rather than let it linger, we're back with a revised, and hopefully better version.
So what changed? Here's the details about Backup and Restore from the Change Log:
George
Following the last release, we realized Backup and Restore could have been done a lot better. So rather than let it linger, we're back with a revised, and hopefully better version.
So what changed? Here's the details about Backup and Restore from the Change Log:
- Instead of a hybrid format for the Backup file that combined the data file
and any associated STATE information, the Data and State files are backed
up separately, and are always unmodified copies of the original files (the
files are said to be "binary equal"). - The backup of the Data file will now maintain the file extension of the
original file. This means that, should you need to, these files can be
opened using its normal application programs using the names you see in
the Backup folder. - Restore now has two operating modes. A standard Restore ("RS") will
restore (and overwrite, if necessary) the data file back to its original
folder with its original name. A Recover with Timestamp ("RST") will copy
the backup file to the original folder without replacing the original
file. The file thus copied back will have its special file name (with the
backup date and time as part of its name) just as you see it in the
$BACKUP directory. This allows file comparisons between the current file
and the backup version, and in cases when you are not sure whether the
current file or the backed up one is the one you want to keep, and you
want to work with both of them. - Added a Backup Retention control feature, to assist in managing your
backup files. This allows you to control how long backup files are kept,
by specifying a retention period (in days), or the number of versions of
backup you wish to keep, or by a combination of these two methods. By
carefully choosing the backup retention factors, you can avoid
accumulating large numbers of backup files that have outgrown their
usefulness, without having SPFLite delete them too soon. - When you use File Manager to view a $BACKUP folder, it will add a file
mask string to hide STATE file backups from the display. Seeing two line
items for a single backup could be a distraction if you were not
especially interested in the State information. You can erase the file
mask to stop hiding these State files if you wish. - Deletion of a data file will now delete the associated State file.
Previously, the State information was not deleted until it was 180 days
old, even though its data file not longer existed. When viewing a $BACKUP
folder with File Manager, deleting either the Data file or the State file
will remove both of them together. Thus, it is not necessary to "un-hide"
the State files, or to delete them separately, to be sure both are deleted
at the same time. - If your backup retention criteria causes removal of all active backups
from a $BACKUP folder, the $BACKUP folder itself will be removed, since it
would no longer be needed. If you subsequently perform a new BACKUP
command after the $BACKUP folder was deleted, a new $BACKUP will be
created again. - If you have already begun to use Backup and Restore under the original
release, your existing Backups will be migrated to the new format
automatically. The only thing you need to do is eventually delete the
old-format backups (files having a file extension of .BACKUP) once you are
satisfied with the new version's support.
Details of the other changes are in the Change Log on the SPFLite website.
George