Yes, I've had to re-apply the user account from the new UI in Remote Management. It was also showing as the backups being successful in the old UI which was not correct...

Can you restore an image backup stored on a external USB with an internet connection? (without pulling data from the Cloud)

What'd you do? I might have to do a restore from a external hard drive to a machine. Bare metal.

Still does not portray correctly.

If you set a backup plan to have say, a 7 day retention policy, when you go to edit the policy again, it will say 365 days. It will show 7 days in the agent. If you go to edit the remote deploy general settings, you also have to edit the backup plan to put back to the 7 day retention policy, otherwise it'll go back to 365 days. Words might have been confusing but hopefully you can fix this.

Well I realize that the Storage Account I made for the network share is practically useless because I need that directory backed up to the cloud and not to the network share. Therefore, there is no place to enter credentials for that network share via MSPBackups since my destination is my cloud bucket. Sorry if that sounds unclear. So to get this done, I just need to enter the credentials for that network share location on the machine itself and I can not do that through MSPBackups correct?

What I did as a temporary solution was enter CMD via the "nt authority/system" account through my RMM and ran a simple "net use" to the network share, inputted the credentials, and now the backup is running. (i'm sure that is not the best/correct way to do it but it works)

I think I configured it wrong, although I'm not sure if its possible to configure the way I was looking for. I need the \\synology\Data directory to backup to the Cloud and hopefully be able to send those credentials via remote deploy. Can I do that? Or do I need to map the drive via CMD to the computers I want the backup run on and then it'll work since it'll have credentials?

Did you find any fixes? Today we are getting 2-2.2 MB/s recovery speeds via Ethernet which is just dumb. Maybe it's using the wrong region or something??? Still pulling 200Mbps+ on the device that is getting a bare metal recovery and other devices on SpeedTest are also pulling 200Mbps+. To take over 24hours for 186 GB of data is .. I see it got up to 3.6MB but it's still not up to snuff.

Is this on your guy's radar? I know that it probably is applied correctly in the Windows application but it would make me feel better to see it on the website properly represented.

https://forum.msp360.com/discussion/2378/bug-with-retention-policy-not-sticking-in-new-backup-format

Agreed. Especially on workflow time, I know what I'm doing so I like to do it fast but I have to wait for the website to load painfully slow.

We were getting 2.2MB/s last Friday which is unacceptable despite Wasabi speedtest pulling 220Mbps (27MB/s).

Sounds right. I got a suggestion

When deleting a computer from Remote Management, is there anyway for a checkbox to be added to also delete that computers data in the backup storage (cloud)? What happened a while back is we had old computers that we deleted but the data was still in the cloud (essentially paying for cloud backup storage on computers that have been replaced..)

We resolved this by going to the users tab, hitting the X button and deleting backed up data only for the computers that were replaced but having to remember to do that every time we offboard a computer might result in some being missed.

I was hoping that going into the gear icon and changing the prefix there would do the same thing. That is what I tried for a test computer. I did start a full backup and it looks like the prefix is different under Backup Storage in the Backup app. Or do I actually have to go into Wasabi or CloudBerry Explorer and rename it there? What does the one under Gear do?

Thanks!

What is the best way to rename a bucket name without losing any backups? Is it best to just make a new destination bucket on mspbackups?

OR, Can I rename the bucket through Wasabi and just select sync local repository in the backup settings for the backup plans?

" I was thinking of a GUI of system drives at the Where to Backup screen"

I'm talking about in the wizard on the website. After thinking about it, perhaps this is unnecessary and I just need to configure a Storage Account for File System (which I have done) and get all the drive letters on external USB drives to be consistent.

Does renaming under Remote Management > Gear Icon > Edit Account and changing the prefix work? Or do I need to actually login to Wasabi or the explorer to do that?

Yep, that is what I am talking about. Is there an easy way to rename the bucket prefixes because computer names change over time and having the prefix be the old computer name gets confusing.

1. What if I just put "Delete versions older than 1 months" and uncheck "keep number of versions"? Is that the same thing?

2. Aare you saying to put "Delete versions older than: 1 months" and "Keep number of versions: 31"

3. What would be the equivalent settings for the GFS policy? I put "Keep backup for 60 days" and "Keep monthly full for 1 month". Not sure if that is the right configuration.

It's a tad slow, like not instantaneous, but its usable at times. Too impatient haha.

I definitely wrote the part about local drives wrong. I was thinking of a GUI of system drives at the Where to Backup screen when creating a new plan for a computer and not relayed to Remote Deploy. I'm not really a fan of making a storage account, then going to users, adding a backup destination, etc, etc, seems like a very long and arduous task but I understand if its left as is.

While were on the topic of Remote Deploy, there is a bug on the Web UI with partition selection. As someone in the support ticket I made said about a month or two ago, to keep it short, the settings are applied correctly in the app, but are not shown properly in the MBS wizard via remote deploy. Hope you guys can fix that up with the new cloning format.

I am talking about images. What would be the best setting for this? We deployed "Delete versions older than" to 30 days and "Keep 2 versions for each file" and "Always keep the latest version." Unfortunately, its not working as we thought. We do a Full Backup every Month, and a Block Incremental every day. What I am looking for is basically so when my full backup runs on November 1, it doesn't wipe out all of October 1-30 until December 1.

I played around with the new format and GFS and it seems way more straight forward but still a tad confusing. Seems like that will be the way to go going forward once its in the remote management console. I settled on GFS for keep backup for 60 day and keep monthly full 1 month. Not sure if that's the right configuration but...

After talking it over, it seems like to get what I am looking for is to UNSELECT keep number of versions for each file and keep delete versions older than, set to 30 days. Once a full runs on 11/01, it will delete 10/01 backup, then when the incremental runs on 11/02, it will delete the 10/02 incremental, so on and so forth?? Right?? I also use Wasabi so it seems like I should just set the delete versions older then 90 days instead of 30 or what?