Wondering if people have the same observation in 4D v18 vs v17 , regarding
backups.
Seems odd (to me) to backup a system based on the name of the App/Structure
instead of the name of the database.
Curious if other people saw this, or if there is a feature I'm unaware of?
I do have an open case.
In v17 and before Database Backups where based on a backup set defined in file
/(database_location)/preferences/Backup/Backup.xml
In v18 its now based on /(database_backup_location)/backupHistory.JSON
Within that v18 JSON file the Structure (aka Application/Code .4db/.4dc)
determines the Backup set number.
like so
...
"(path)/APP-Version1.4DB": [
{
"structurePath": "(path)/APP-Version1.4DB",
"dataPath": "(path)/PROD.4DD",
"backupPath": "/(path)/PROD[0001].4BK",
...
Well if you do like we do, and change version number on a deployment, we
observed that the new v18 backup design overwrites our backups, as in starts
the sequence number over because its based on the structure name. So yeah...
Sequence number is based on structure but its name is based on the database. If
4D would have picked one or the other for both the sequence number and name of
the backup, then there wouldn't have been overwritten backup files.
here we see backup 2 overwriting our 4BK file
"(path)/APP-Version2.4DB": [
{
"structurePath": "(path)/APP-Version2.4DB",
"dataPath": "(path)/PROD.4DD",
"backupPath": "/(path)/PROD[0001].4BK",
...
We switched to keep the name of the app/structure deployed always the same.
though we considered other options. (like renaming the backup file after the
backup completes)
Regards
Aaron
**********************************************************************
4D Internet Users Group (4D iNUG)
New Forum: https://discuss.4D.com
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
