I did not hear back (and forgot to follow up with them). I'll ping them again. Sorry.

Computer B is unaware of what Computer A is doing. If you issue a sync, then you are telling Computer B the current state of the files in storage, but it will not know about any changes after that time. The Sync process can be time-consuming

If you are only using Computer B for restores, you can run the agent in Restore-Only Mode and when you perform a restore operation, you'll be given the choice of computers in Backblaze and files to restore. https://help.msp360.com/cloudberry-backup/restore/restore-only-mode#:~:text=To%20restore%20data%20from%20the,launch%20in%20restore%2Donly%20mode.

Another option if the two computers are on the same network would be to create a network share on Computer B and restore from Computer A to the share on Computer B - as that would avoid the need to run Backup on Computer B and also avoid the sync issues.

But maybe if you describe your use case a little more we can provide some better guidance.

I know there is one fix coming in 1.2 related to a similar issue. I will reach out to the support team and ask about next steps for you. Stay tuned.

I meant remote desktop... sorry.

You’ll need to open a support case and submit the logs for analysis. https://kb.msp360.com/backup-mac-linux/obtaining-logs-on-macos&linux

What version are you using?

Backup version?

Do it on the OS where you are seeing the bad_auth_token error. Just get the case opened and if they need something specific, they'll tell you where to get it.

I was asking because I saw a report of a similar issue that was fixed in 6.3.1, so I'm guessing this is something else. You'll need to open a support case so the team can review the logs (Tools - Diagnostic toolbar option).

I have given the support team a heads-up. Please refer to this post in the submission.

What version are you using?

When does that error come up? Is it when you try to select the bucket?

Also what version are you using?

If what you're after is scheduled sync, then you'd be better off using our Backup software in Simple mode which copies files to S3 on whatever schedule you need. It also includes features like VSS support so files can be copied even if they are in use. https://www.msp360.com/backup/windows/desktop.aspx

Have you defined your B2 storage account exactly as defined on the source PC?

I moved your post to the correct section. How are you connecting to the remote systems? Unattended Access? What's the issue with the Windows Login screen? Are you unable to log into the Windows system?

Which product are you using? You posted in Managed Backup, but I'm guessing this is a question about Remote Desktop / Assistant?

unfortunately 15 minutes is the default backup.. If you need backups to run more frequently using a custom design schedule, then I would use advanced backup, which is the preferred backup method anyway, and create a backup job to back up those files using advanced backup.

I'll ask the team if they are aware of any similar issues. Did you connect using to the remote system with the full version installed there or did the remote system use the QuickSupport option?

When you say locked out, are you saying that you try to reconnect after some period and the reconnection is unsuccessful? Or are you saying that during a live session you sometimes get disconnected?

The regular remote desktop will continue to be free.
Managed remote desktop will eventually be a paid product, designed for those that need to manage large numbers of remote connections through a management interface. If that's what you're looking for you can sign up for the free beta here: https://www.msp360.com/remote-desktop/managed.aspx

I cannot tell from the error what's going on. It's possible the product could not establish a connection with the cloud storage or something local was going on. In any case, you'll need to submit the logs for review to the Support team. https://kb.cloudberrylab.com/backup-mac-linux/obtaining-logs-on-macos&linux

Roger, you might be better off running two separate backups: One to local and one to the cloud if you find that the backup and copy method is too prone to error. Managing a backup of a backup might make it more troublesome to restore from the cloud.