• SamboNZ
    0
    I have a MSP360 Standalone Backup client which is backing up to an SMB share on the local network.
    This configuration works perfectly for the multiple other clients I have running on the network, backing up to the same location, and did in fact work for this client once in the past week (after a full OS reinstall).

    I am able to access (and write to) the destination SMB share using Windows explorer on the client.
    The destination computer shows the client login as successful.
    The MSP360 backup configuration confirms the credentials I had entered for the local storage location as correct and working.

    However, when I attempt to run a backup, I receive the following error:

    Network resource cannot be accessed (Code: 1514)
    Credentials for the following network resource(s) are not specified: \\server\share\folder\

    I even went so far as to completely delete the '%ProgramData%\CloudberryLab' folder, and reconfigure the backup entirely from scratch, with the same result.

    I am using the 'Legacy' backup type, in 'simple' mode.

    However, I noticed during my testing that the backup was reporting that it was failing on empty folders. Deleting the folder in question simply caused the backup to fail on a different empty folder.

    Unselecting the 'backup empty folders' option allowed a full backup to complete successfully.

    I can't see anything special about these failed empty folders and it doesn't seem to fail on ALL empty folders, just some of them.

    Based on the results of my testing, I suspect that the error I'm getting is not accurate.

    Not sure where to go from here!
  • SamboNZ
    0
    Ok, this is weird.

    I did a bit more testing and managed to 'solve' the problem by putting a file (just a blank text file) into the folder the backup was failing on, and it completed the entirety of the backup without failing...

    We'll see if this continues to work correctly over the next few days...
  • SamboNZ
    0
    So this is definitely an ongoing issue and it happened again today.

    In this case, the folder was:
    C:\Users\UserName\AppData\Local\SourceServer\8569009a4bc56cb306676939718ced68f7a8a78f96079249e53de77e527951c6

    Again, adding an empty file worked around the issue.

    Interestingly, another, virtually identical empty folder backed up without issue:
    C:\Users\UserName\AppData\Local\SourceServer\60afa13063e0486041e632ed702bf4d5e2730d5054962f7c48eda99ddb006b51

    Neither folder existed in the backup destination prior to running the failing backup.

    Running the latest build: 8.0.4.5

    This is definitely a bug of some kind @Alexander Negrash.
    I can re-create the issue.
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment