Comments

  • Cannot complete a backup since upgrade to 4.0.0.260
    Okay, thanks. I submitted the logs via the GUI. Case #00173749 (not sure it helps to reference the case # here but in case it does).
  • Bad file ID?
    Just to close this one out, I contacted MSP360 support and, after reviewing my backup logs, they suggested the following:

    It seems that the sync between Cloud storage and Local database is slightly outdated.

    Please synchronize the repository following these steps:
    1. Go to Settings - Application - Synchronize Repository.
    2. Choose your account from drop-down menu.
    3. Press Synchronize Now     — MSP360 support

    I did that and am happy to report it seems to have solved the problem. How my cloud storage and local database got out of sync in the first place remains a mystery. At least now I know what to try first if it happens again.

    And kudos to Anton at MSP360 for the fast reply and resolution.

    Brad
  • Bad file ID?
    Okay. Thank you for trying. Weird one.

    Brad
  • Bad file ID?
    The storage is Backblaze B2.

    An example message would be something like:

    /*
Operation     Purge
Plan name     user-backup
File          /CBB_computer/CBB_VOLUMES/.../DSC_8083.NEF$/20190729215800/DSC_8083.NEF
Size          0.00 B
Finish Time   1/6/22 11:02 AM
Duration      00:00:01
Date Modified 7/29/19 3:58 PM
Message       Bad file ID:
*/

    In all cases the file size is 0 bytes.

    Thanks,

    Brad
  • Moved but un-modified files needing to be re-copied
    Thanks for the info. The new backup format sounds great (no need for any server-side gymnastics).

    I'm on the Linux version so I've signed up for the beta when it's available.
Home » QIC-40