Backup failing because folder doesn't exist
  • Kris
    0
    I'm trialing MBS at the moment and I am getting machines showing as failing when a backup is run because a folder doesn't exist. I'm using the Desktop version of the app on the client machines and only need to backup a few folders to Azure. The backup plan lists the source as all of the folders that I need to backup but some of these folders only exist on machines that are running an older version of the local app that we need to backup. To keep things simple, I've included both the old folder and the new folder in the backup plan but the backup is showing as failing for those machines that were only installed with the newer version of the app that uses the new folder location.

    It would be a real pain to try to identify which machines have been upgraded and which were installed with only the new version as we will be dealing with 1000s of machines if we proceed past the trial. Is there an option somewhere to not have the backup marked as failed if a backup source folder can't be found?

    View Answer
    Kris Options
  • Sergey
    6
    ↪Kris
    This is currently something that is being discussed to be added to our roadmap.
    So the plans will have a separate option to ignore this "One or more backup paths don't exist" warning.
    I have added you to the list of people interested in such option, so you should be updated once we have further info on it.
    Sergey Options
  • David Gugick
    118
    ↪Kris
    I have a temporary solution for you:

    • Use the Pre-Backup Action option in CloudBerry backup plan
    • Create a script file that creates the missing folder if it does not exist
    • Backups will then run without incident

    @ECHO OFF
    setlocal EnableExtension DisableDelayedExpansion[url]http://C:\Users\dgugick\Desktop\2018-06-28_160527.png[/url]
    SET "OldFolder=C:\Users\david\Desktop\Important Files 2"

    IF NOT EXIST "%OldFolder%\*" (
    MD "%OldFolder%"
    )
    endlocal

    0523zhw1srxod0ov.png
    David Gugick Options
  • David GugickAccepted Answer
    118
    ↪Kris
    I'll just add that the file (a .CMD file) will need to be accessible during backup. So, a shared location where it can be picked up will be required.

    It's not the most elegant solution, but it should get you through this issue until such a time as we have a feature to suppress errors on missing files/folders.

    Thanks.
    David Gugick Options
  • Kris
    0
    Sounds good, David. I will give it a try. Thanks for the suggestion!
    Kris Options
  • Basepack
    0
    You can suppress those warnings if you want as follows:

    There is a way to suppress them by finding the .cbb file for that backup job.
    To find the .cbb files do the following: Tools -> Diagnostics -> Open in Folder and go to the folder that is one layer up.
    The cbb files all have a rubbish name, so what I do is Edit and save the plan again and then sort the folder by datetime. The first .cbb is the one you need.

    Change the <UseIgnoreErrorsOnPathNotFound>false</UseIgnoreErrorsOnPathNotFound> line to <UseIgnoreErrorsOnPathNotFound>true</UseIgnoreErrorsOnPathNotFound> with the help of any text editor and save the file.
    Basepack Options
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment