Comments

  • Immutable Backups
    For both Azure and local / private, there are open feature requests. I will add your requests to the system. For local / private cloud, we do support S3 compatible Minio, but we do not yet support Minio Object Lock / Immutability. But since Minio is S3-Compatible, if the feature is added, it will may end up for S3 Compatible and Minio.
  • Backup History export line limit?
    This is a known issue reported by a few customers. I'll add your comments to the item and will reply back here when I know more.
  • License error (code: 1406) Unexpected error on checking license
    Glad I could help. Apologies for the inconvenience.
  • License error (code: 1406) Unexpected error on checking license
    there was a fix in the latest version for a licensing issue. Could very well be related to the issue you're seeing. Please download the latest build, put it in the sandbox, and test it on a machine that's currently having the issue to see if it's addressed. Thanks.
  • License error (code: 1406) Unexpected error on checking license
    I would encourage you to upgrade to the latest version. I suspect that will address your issue. If you're new to managing the product and are not sure how to do that, please let me know.
  • License error (code: 1406) Unexpected error on checking license
    let me move the post to the managed backup section. And then I'll reply again from there.
  • License error (code: 1406) Unexpected error on checking license
    what version of the agent are you currently running? And is this for standalone or managed backup?
  • RIP Free unattended access
    I'll try to address your questions. If I miss something, please let me know.

    David, do you know if what you thought was going to happen with the next release (3.1 is now out) was implemented? Meaning, a person with a single Pro license could install it on as many of the machines they manage from as needed?Jared Pickerell - DCEduCoop

    There have been no licensing changes for version 3.1. The way Pro licensing works, as you've already seen, is that you need to license any endpoint where you need to initiate an unattended session for administration purposes. Remote systems do not require a Pro license. Just install the free version of Connect on any remote systems you need to connect to in unattended fashion.

    If you can restrict your admin computer to one computer, you can use it for all your unattended sessions. If you do need to kick off unattended access from another computer, it will need a Pro license.

    There are no restrictions on interactive / attended sessions with a remote user / machine. You can use Connect Free for that purpose.

    I would "consider" purchasing a $89 a year for my personal use, but would be much more likely if it was less expensive, or if I could make a one-time purchase.

    We understand that the Pro pricing may not work for every customer. If you cannot use the free product to serve your family / work, then a Pro subscription would be the next option.

    For work use, I could see my Coop paying a yearly $89 for me to use. But I couldn't see them paying $89 for each machine that I use (including home/personal devices), that I may use to use to connect to one of the few RD/Connect machines in the schools and Coop that I remote into. I'd really love my 3 district tech directors and our 1 district tech assistant to also be able to use the unattended access into our management PCs. And what would be fantastic, is to be able to purchase the manged licence to push out the agent to all of our District and Coop PCs and Macs and let any of our tech staff remote into.

    Again, you'd just need to restrict starting an unattended session to the Pro licensed computer. None of the other computers require a Pro license. I think this is your understanding, but something you wrote above made me think that maybe you thought all computers need Pro licenses - which is not the case.

    Last time i talked to sales [...] If memory serves me right, there were several client settings that couldn't be set in the management console when I had demo'd it (including not being able to set/see/manage the encryption and MFA settings. Maybe this has improved in the last few months

    For Managed Connect, 2FA is managed from the login to the management console. You can enable 2FA for all administrator accounts and 2FA will be required when connecting to the management console and allow you to kick off a Connect session. Security credentials are managed automatically in Managed Connect and encryption is always enabled. List price is $34.99 / Month per Admin / Technician if you're a reseller like an MSP. That enables you to access any number of remote endpoints and use any computers to perform unattended administration or initiate interactive sessions with remote users.
  • Moving from Datto to MSP360 (Image and File backups)
    Thanks for the update. If you'd like a private demo of the product, please reach out to our team as they'd be happy to show you whatever you'd like to see. https://www.msp360.com/personal-demo/

    Our weekly demo webinar is here: https://get.msp360.com/webinar/getting-started-with-msp360-managed-backup
  • Moving from Datto to MSP360 (Image and File backups)
    You can restore files or folders from Image and VM backups with MSP360 Managed Backup.
  • Windows Home Server, AWS, TLS 1.2
    That version is long out of support. I think you could simply upgrade or purchase a newer edition, but you would need to check with Support to make sure that the latest versions will work on WHS 2011. You could also try using that old version to backup up to Amazon S3 Standard and moving data via a lifecycle policy to Glacier of that's supported in that older version. Newer versions support S3 Glacier using the S3 APIs rather than the legacy Glacier APIs from Amazon. But reach out to support via the web site and see what they say.
  • Can I delete folder in S3 ? will it mess up the indexing?
    no, please do not delete from the bucket directly. While you can do that, the repository will then be out of sync. What I recommend you doing is going to the storage tab in the product, navigating to the folder in question, right click it and select delete. Just make sure no other backups are backing up any files on your C drive to that same location.

    Once you do that the repository will be updated automatically with the deletion. Please just make sure that you delete exactly what you do not need as they'll be no way to recover data once the deletion is complete.
  • Backup Window too big on laptop screen, can't see buttons
    Are you saying you cannot find the install folder for the product in order to run the commands in the article? Were you able to find the folder but something else is happening when you try to execute the commands. You should have support in that product. What version are you using?
  • Backup Window too big on laptop screen, can't see buttons
    The solution would be to move to the WebUI. You can report to Support if you want but the WebUI should not have that issue. https://www.msp360.com/resources/blog/taking-advantage-of-web-access-for-macos-linux/
  • Rename file-folder dialog keeps popping up, over and over
    Glad we fixed it - even if we're not sure what the issue was. On-Screen Keyboard FTW.
  • Rename file-folder dialog keeps popping up, over and over
    Sounds more like a keyboard issue like a stuck key. Can you try unplugging the keyboard and plugging back in to see if that addresses. If not, open the onscreen keyboard in Windows (type onscreen in the start menu). See if any keys are showing up as depressed.
  • Connection error Code: 1056
    Thanks Steve. A heartfelt "Sorry" to all those customers affected by that regression issue.

    "May your regressions be infrequent and far between." - The first developer
  • Connection error Code: 1056
    That's what I would do. Since the only fix is what I mentioned above, I think moving to build 109 is probably best and low risk if you've already vetted build 107.
  • CloudBerry Backup now warns about EFS encrypted files instead of backing them up
    After a quick review of the release notes, EFS support was added when using the New Backup Format only. You get backup options for decrypting EFS files at backup time or backing them up with EFS encryption intact. But if you need EFS backup support, you'll need to move to the new backup format.

    As an option: If your EFS files are contained in a limited number of folders, leave your legacy backups in place, but with a change that excludes any folders with EFS encrypted files. Then create a new file backup format plan that manages only those folders with EFS encrypted files. Please let me know if you have any additional questions.