Comments

  • Suggestion for clean termination of backup
    Yeah the first one will take over 2 months when done. When I click stop it seems to take a few seconds,I assume releasing the VSS volume and closing all transfers. It’s not a huge deal, but was just making a suggestion. Thanks
  • Suggestion for clean termination of backup
    Correct, but the backup is running for weeks, something happened that the backup could no longer access the VSS snap and crashed. Not saying it is a MSP360 issue, but being able to cleaning stop the backups every week or s and picking back up without lost file transfer time would be great.
  • Suggestion for clean termination of backup
    Correct. But my guess is the VSS snap being in use for weeks on end eventually the OS did something that made it inaccessible to Cloudberry. Has not been a huge deal, but would still like to see a clean stop option eventually.
  • Suggestion for clean termination of backup
    I am running file backups, but it looks like it takes a volume snap before backing up the files. After a few weeks it crashed about unable to read the snapshot volume.
  • Suggestion for clean termination of backup
    I am in the middle up uploading 25TB to Azure then to AWS and my upload speeds are only 35mbps which means months of uploads. I like to patched my server every month, and also I find that the backups after a few weeks may have issues since the volume snapshot is so old.

    Many of my files are 40-80GB so trying to stop a backup at the right time to not have lost all that transfer size/time is a timing game. If there were an option to Stop-Clean when each thread file copy in process would stop once that file is done would be great.
  • How to sync Hybrid backups?
    I just recreated the issue. Syncing the repositories then running a new backup successfully does not recreate the secondary. It only populated the incremental that just ran. There needs to be a menu option on the storage account to "resync" and it should go out and do the compare resolve the mismatch. The current process is rather convoluted. I sent logs to my open case, but for me the easy fix is robocopy. There needs to be a better fix for large hybrid storage to do the sync and repair.
  • How to sync Hybrid backups?


    Yeah that never worked for me. I ran a backup and all that showed in the secondary was the latest incremental. I may try and duplicate the issue to send the logs to support since they were stumped with my issue. I may try it tonight. Also the sync operation is not very clear as to what the source is vs. the destination for a sync.
  • How to sync Hybrid backups?
    I have been fighting this issue myself. And here is how I resolved mine.

    This solution is not practical for many use cases especially if you are going to cloud and it costs time and money to do these steps. I am still waiting on support to tell me the official way to sync 2 repositories.

    I have hybrid VM backups. Where I have a local disk and then external disk I was backing VMs up to. the external disk got corrupt and I have to reformat it. When future backups ran only the incremental backups showed on the external drive. If I ran a consistency check it would remove any listed backups from the external drive in the "Backup Storage" View/tab. Because I was only dealing with 2.5TB and it was all LAN based I did the following:

    Recreated the secondary storage account (external USB drive).
    Robocopy the primary backup target to the secondary maintaining proper directory structure.
    Once complete ran a consistency check on the secondary backup drive and the backups repopulated fine. I did a test restore and it works fine.
  • How long will legacy file backup be supported?
    Correct, I actual use the Hyper-V product and have a Hyper-V plan to backup my VMs to NAS and then a legacy file plan in Simple mode to file sync my media files to Glacier Deep Archive. I have that plan set to delete the file in S3 30 days after it is deleted locally. As long as legacy mode will remain this looks like I will be purchasing it after a few more tests, nice product once you get the knack of it. One suggestion would be to allow simple mode to sync directly to the storage account path. Seems it creates a CBB folder then a folder under that which has the source path as the name.
  • Configuring incremental backups with periodic full backup
    If they remove legacy file option then I am not interested in the product. I want to do pure file syncs from one server to another and then from the server to S3 Glacier Deep Archive. I want to able to access and use the files without having to restore them with Cloudberry. Essentially I want to use it as a file sync operation not a pure backup as I need to be able to have the data usable at all times. It would be nice to know their intent before I buy this once my trial runs out.