BAK Files ?

I do automated backups in a custom temp folder.

What is the use of additional BAK files beside the working file ?
Can I deactivate them ?

Comments

  • BAK files are duplicate backup copies of your file.
    They contain the file state you previously saved manually.

  • Can be deactivated in SETTINGS.
    Search for "bak", you'll find:
    "Incremental Save Backup". Uncheck "Create BAK file"

  • Michael Mayer
    edited January 2018

    Yes, I did deactivate them initially because they disturbed me,
    but I was not sure if I will miss something by doing so.

    But still am not completely sure about Back-upping procedure
    in Bricscad in general.

    In every other App I activated Auto Backup copies in case of crashes.
    I set number of versions, time or number of commands and of course Paths
    inside a common local fast SSD folder where I can look for them or clean up
    from time to time if needed.
    So if a file crashes and I missed to manually save sufficiently, I will find my
    last saved file state there, open it manually and if ok, Save As working file.
    (overwriting current working file)
    Fine.

    In Bricscad I set my Save Path and it looks ok, *.BAK and *.SV$ are there.
    (BTW what is that numbering scheme that does not sort in time order in Finder ?)
    I decreased back up time to a reasonable value.
    (expected it would be seconds, not minutes, when defaulting to 60 !)

    But how to recreate the last file state in Bricscad after it crashed and I missed
    manual saving ?

    1.
    Will it automatically care about *.SV$ when I reopen my working file ?
    (looks like it will not)
    2.
    Should I manually open the *.SV$ and overwrite working file manually ?
    3.
    Should I open *.SV$ by "Recover" command ?
    or better
    4.
    Should I open my working file by "Recover" command ?
    (That Bricscad will consider the last *.SV$ ?)

  • To recover a dwg saved as a .SV$, simply change file extension (from .SV$) to .dwg.
    Same applies to .bak files.
    You can check times of creation to find which file is the most recent.
    Search help for .SV$, .bak which will help explain options re: system variables and user preferences.

  • Thanks Robt,
    so if I got it right,
    when I saved my drawing at 2 pm and Bricscad crashes at 4 pm
    and I know reopening my work file would lose 2 hours of work,
    the recommended way to reduce the damage would be :

    to go directly to the *.SV¢ files and open the latest and manually
    overwrite the work file with it (?)

    Yes, It needs to search through file creation dates, to find the
    most recent *.SV$ file, as it currently is. That doesn't necessary mean
    that there couldn't be more convenient solutions, in my opinion.

  • I've found Bricscad to be very stable (possibly more so that AutoCAD), but nevertheless crashes CAN occur.
    One thing I ALWAYS do (especially when working with .dwg s from others) is run AUDIT, PURGE before commencing.
    If you do experience a crash, search for the latest file (.SV$ or .bak).
    I would rename them i.e: drawing(1), drawing(2) so you can open them simultaneously and compare them.
    Get in the habit of manually saving every so often (We've all been frustrated finding out that we forgot to save & lost ~30 minutes work).
    May want to reconsider creation of .bak files.
    Change SAVETIME variable to a more conservative value.

  • Thanks Robt, now I know how to deal with (*.VS$) backups.

    My crash experience may be slightly different, but I am
    a) on macOS
    b) using mostly latest 3D and BIM technologies available
    c) Am new to Bricscad so may tend to use tools in a creative unforeseen way
    that no one tried or tested before.
    :smile:

    But it is not that bad.
    So far no need to add a _qsave after each command :smile:

  • Cheers
    We're all in this together...

This discussion has been closed.