• New Version - Backup Agent 7.2 for Windows

    Couldn't agree more. We have no problem setting up new client's on the updated backup format going forward, but forcing widescale retroactive adoption and placing the burden onto your customers seems to be strongarm tactic that doesn't sit well with us. You guys are selling almost exclusively to MSP's now, not individual businesses. You must understand that a complete systematic change like these has huge impact on us. We have hundreds of terabytes of data that would need to be reuploaded to cloud storage to accommodate the new format. Also, we'll be the ones to incur the additional cloud storage costs if switching to the new format since it would be a different backup plan, and therefore separate storage. We've been with you guys for a few years now, and there really seems to be a disconnect between the company and your clientele. From our perspective, there's a high level of focus placed on "what's the next new feature" vs. making your existing software bulletproof and gradually improving it over time.

    Unrelated, but having a "current bugs" or "known issues" tab in the management console would be immensely helpful. I also saw the "backup client's out of date" bug this morning, and end up having to drill down into the forums to find information regarding this, or I have to call your support just for them to tell me it's a known issue, it's just doesn't seem very efficient for you or us.
  • New Version - Backup Agent 7.2 for Windows

    That's all well and good for new clients, but we have nearly 800 backup plans at this point in time running on the "legacy" backup format. I agree with Steve Putnam in re-uploading hundreds of clients data is hardly a viable option. When is this supposed to be enforced? This is something that would take us an unbelievable amount of man hours to complete as the change would need to be individually handled on each machine which is just crazy to even think of.

    Also, in the new backup format, there's no option to run full only backups? you have to first enable incremental backups to allow for full image backups, but then have no option for exclusively running a full image backup.
  • Block-level no longer automatically working with chained image backups. Please help!

    Yeah, I've given up on this issue being fixed at this point. It's been over a year and to this day, I'm still manually modifying text documents on every new setup we do.
  • Restore Verification (beta)
    Hi Ivan,

    I noticed you mentioned it downloads "a part of the backup data required to start a test Windows Hyper-V VM" Could you elaborate on that and exactly what data would be getting restored? Thanks.
  • Is there currently a service outage/issue?
    I called into phone support and they confirmed there's currently a large scale issue that's being investigated.

    I wanted to express our disappointment that there was no information or notification sent out regarding something as significant as this. I currently have 147+ overdue client backups from last night as a direct result of this issue.

    A system status page, or an alert in the management console would go a long way in keeping customers in the loop and reassuring us that you're on top of things. An explanation of what happened and what's being done to mitigate something like this from occurring in the future feels like an appropriate response in this situation.

    We love your guys product when it works as intended, but lately it seems we're getting into an ugly pattern of new issues popping up and never being properly adressed.
  • What's going on with Synthetic full backups? Major RAM issue.

    Anton, following up as this issue is still occuring. Really hoping for a fix to resolve this. Today is the 1st of the month and we're having the same problems as we were previously. I've had a ticket open for a month and it was escalated to the developers, but I haven't heard anything back. Thanks.
  • Block-level no longer automatically working with chained image backups. Please help!

    Hi Matt,
    It's been quite some time, hope all is well. I just noticed this morning that version 6.3 has been released. I checked the release notes, but did not see this mentioned. Can you please confirm if this has been resolved in the lastest version?
  • Block-level no longer automatically working with chained image backups. Please help!
    Guys, Still waiting for an update on this. We're busier than ever and this is adding additional time and frustration to each new setup we're deploying. Please address this.
  • Block-level no longer automatically working with chained image backups. Please help!

    Hoping for an update on this as it's been well over a month. We've been taking on and converting a lot of client's lately to this setup with Cloudberry, and I'm growing tired of the manual workaround that I'm having to use each time. Also while it does work, I've noticed that when using the manual workaround correction you have to modify the file twice to get the changes to actually stick.

  • Block-level no longer automatically working with chained image backups. Please help!
    Hi Anton,

    Very cool to see Powershell module. However, I'm not sure what you've referenced is what I'm trying to accomplish. Our problem is chained backups running full backups daily instead of block level backups daily.

    We run as follows. NAS backup full daily, then chained cloud backup block level daily. Then the cloud backup needs to run a synthetic full once a month.

    The method you've described here is just to force a chained backup to run as full correct?

  • Block-level no longer automatically working with chained image backups. Please help!
    Just wanted to update. I was assisted by support who was able to provide a workaround for the issue. The fix requires manually modifying the backup configuration file from the backup agent on the server, and changing values for 3 different lines of code.

    While I truly appreciate the help and temporary workaround, I'd just like to reiterate the importance of a timely fix for this. Having to login to each server and manually update a .txt configuration file for each client's backup plan is very tedious, and a time waste for our limited resources.

    Since the tech was able to fix it, I'm assuming you're aware of the specifics and where the problem is occurring? If not, I'd be happy to show you exactly where the issue is happening.

  • Block-level no longer automatically working with chained image backups. Please help!

    Sergey, Thanks for that. I've just checked one of the machines with this issue and can confirm that <ForceFullNextPlan> is already set to false.
  • Block-level no longer automatically working with chained image backups. Please help!

    Hi Sergey, I will take look at that this morning. Also, I didn't create a ticket, but I called into phone support last night, spoke with a tech and got him remotely connected to one of the machines. I provided him with an email address and my information, but am not sure if a ticket was created. I didn't receive an email notification indicating that a ticket was created. Thanks.
  • Image backups keep the last version

    Thanks Matt. Is there any negative effect to having this option enabled/disabled then? I'm just wondering going forward if I should leave it on or off by default when creating new image based backup plans for other clients going forward.
  • Image backup failure. Not all chunks were uploaded
    Still having continued issues with this. Issue is affecting more than one client at this point. I've provided multiple sets of logs and other requested data but have not heard back regarding this. Please advise as my clients are becoming increasing concerned that their backup has not run in over a week.
  • Running weekly or monthly fulls

    Hey Matt,

    Thanks. Just wondering how this would lead to reduced storage charges? We use Wasabi and try to accommodate their 90 day retention policy. Our current monthly full backup means we'd be storing a minimum of 3 full backups per 90 days. If using the weekly full format we'd then be storing 12 full backups to accommodate the 90 day policy.