• Flush operation is not supported in Read Mode
    It looks like you haven't updated the software for a while. Can you try with the latest version?
  • No event logs left behind cloudberry despite that being turned on.
    This is really difficult to reproduce. As you mentioned it works on your other servers. It works for me too. I checked with our dev and support teams and they couldn't recall similar cases. It doesn't seem like the software problem. Maybe there is something with the Windows events log service.
  • SQL logic error or missing database no such column: destination_id
    The easy way would be to reinitiate the repository db, but that might take quite some time. To do this:
    1. stop the service
    2. close the agent
    3. rename file C:\ProgramData\CloudBerryLab\CloudBerry Backup\data\cbbackup.db (maybe add OLD to the file name)

    again, that might take time to recreate the repository from scratch
  • VSS Error (code: 2404)

    VSS Error (code: 2404)
    VSS System Writer does not have permission to read the service account. Event ID: 513
    Read the instructions in the Knowledge Base article
    Check this KB article

    An error occurred (code: 1003)
    The creation of a shadow copy is already in progress.
    Please contact support

    The issue might be caused by other software for native Windows backup. Make sure another backup is not working at the same time. If this doesn't help, try opening an elevated command prompt, then run the following commands:
    • chdir “C:\Program Files\CloudBerryLab\Online Backup”
    • .\cbb.exe fixVSS -output full
    Also, make sure the backup plan setting "Use system VSS provider" is enabled.
    Reboot might help as well

    another KB worth looking at if the above doesn't help
  • Help understanding retention policies
    To grasp the intricacies of the retention policy, it's important to consider a few key points:

    1. MSP360 employs a generation-based approach to storing backups, with each generation comprising a full and incremental backup set. The term "generation" is closely tied to your full backup frequency.

    2. There are two distinct types of retention: Base retention and GFS retention. Base retention applies to backup generations, excluding the current one, which remains immune to data purging until the next generation is created.

    3. GFS retention, on the other hand, is specifically applicable to full backups. It serves as a complementary retention policy that shines when you need to retain full backups for extended periods. Notably, GFS retention should surpass base retention in duration.

    In your current configuration, both base retention and maximum GFS retention are set at the same value, e.g. 5 years base retention and 60 months GFS retention, resulting in backups being stored for 5 years anyway.

    It's advisable to differentiate between the two:
    • Set the base retention ("Keep backup for") to a duration that aligns with your need for granular restore points, typically represented by each incremental backup.
    • Use GFS retention for full backups that require storage beyond the base retention period.

    Let's illustrate this concept with an example. Although I don't have access to your specific backup schedule, let's assume you perform incremental backups on weekdays and full backups every Saturday. In this scenario, we'll set the base retention period to 1 month.

    Base Retention:

    Under this configuration, you'll have a maximum of 4 full backup generations (comprising both full and incremental backups) stored at any given time. When the 5th generation is created, the 1st generation will be purged in accordance with the base retention policy.

    GFS Retention on Top of Base Retention:

    Now, let's delve into how GFS retention complements base retention based on the settings in your screenshot, where weekly backups are stored for 6 weeks and monthly for 60 months.

    The first full backup generated will be marked as the initial monthly and weekly backup for GFS. The 2nd, 3rd, and 4th full backups will only receive weekly tags.

    When the 5th full backup initiates a new generation, incremental backups from the 1st generation will be purged in accordance with the base retention policy. However, the full backup will be retained based on the GFS retention. Additionally, the 5th full backup will again receive monthly and weekly GFS tags. The 6th and 7th full backups will be tagged as weekly backups, and so on.

    Once the 7th full backup is created, the 1st full backup will lose its weekly GFS tag but won't be purged because it still has a monthly GFS tag. It will be retained in accordance with the monthly GFS retention.

    Subsequently, when the 8th full backup is created, the 2nd full backup will be purged in line with the 6-month retention period for weekly backups, and this cycle continues.

    I hope this explanation clarifies how retention policies work in MSP360 backups. If you have any further questions, please feel free to ask.
  • Initial Licensing
    1TB limit applies to MSP360 storage trial only. If you are connected to a 3rd party storage, there is no limit.

    Speaking of licenses, we charge for the actual license usage at the start of the next month, e.g. you pay for licenses used during the previous month. Once your trial license comes to an end it will be automatically converted to a paid license and at the beginning of next month your account will be charged for the days outside the trial period. No action needed on your end
  • Initial Licensing
    Your trial licenses will convert to paid in 15 days after the activation. Speaking about storage, you can switch to a paid mode by clicking subscribe at
  • Error - Requested Object Does Not Exist
    I would recommend doing full regularly, yes. The most common frequency among our customers is once per week or once per month. Also what important to understand here is that depending on your retention settings multiple full backups may take quite some space on your storage, so plan your schedule and retention accordingly. Choose a reasonable retention period not to keep more data than you actually need. If you need longer retention for your full backups (months or years) consider using GFS settings for monthly backups.
  • Error - Requested Object Does Not Exist
    So looks like this path can not be accessed \\HCU-DC01\HCUdata\Appraisals & Real Estate. Can you send the whole log file in a PM? There is a block with an error description at the end that can help to diagnose.
  • Force Backup after Client open desktop/notebook.
    There is an option to force a missed backup on a computer startup.
  • Moving CloudBerry Drive to a new machine
    Yes you should be able to start a trial on a new server
  • Moving CloudBerry Drive to a new machine
    You can request license transfer via the contact form at . Make sure to pick the right product.

    or you can send an email to
  • Pre-action stuck
    Pre-Post actions are only available with the Ultimate license
  • AWS IAM user issues
    If you are not using the Managed version you don't need sts и ses in the policy
  • Pre-action stuck
    downloaded Cloudberry Backup for Linux with a valid license.Luciano
    What exact license do you have? Linux Ultimate

Alexander Negrash

Start FollowingSend a Message