Support is brainstorming the issue. I should have some reply for you by tomorrow.

is the address book completely empty or are there a limited number of items in it? If it's completely empty, I'll have to ask the remote assistant team

Use the Tools Diagnostic toolbar option to submit the logs. Thanks.

It's my understanding you should leave the C: files in place as we track the older backups and file versions. If you delete them, you may inadvertently delete file backups you were hoping to keep. Plus, your repository will be out of sync if you delete directly on B2 (always use our delete functionality in the Storage tab to remove old backup files). I'll confirm this with the team (confirmed).

Please open a support ticket using the Tools - Diagnostic toolbar option and reference this post. Support can assist with older versions as well.

The Backup will continue where it left off. You should not use AWS versioning, so turn it off. Files are uploaded with unique folders for each version of a file we upload, so there won’t be duplicate object names in Glacier. But we do not manage versions so there’s no reason to have that feature enabled on the a Glacier side.

https://www.msp360.com/download.aspx?prod=cbra

Click download Windows and it's on that page.

Try using an appropriate domain account or local account with sufficient rights to the folder in question for the Drive service account and restart the service and see if that helps.

Are you saying you use some built-in or some other third-party software to back up the QNAP appliance for offsite backup, and you're looking for a way to use the QNAP and an app on the QNAP itself to back up a Windows desktop/server for DR?

The short answer is we do no have a native QNAP agent. In order to back up files stored on the QNAP appliance, you'd have to expose a network share and back up the files from another supported platform (usually this is a Windows endpoint or server) by referencing the network share as the location for files to be backed up. You can then send the files to local storage or any support cloud storage provider using your own cloud storage accounts.

As far as performing an image backup of the Windows computer for DR, you need to run the MSP360 agent on the Windows machine (unless it's a VM, in which case you can use the host-level VM backup features in our VM Edition). There is no way to perform an image backup of a Windows machine from a QNAP appliance.

If I've misunderstood your configuration or question, please clarify.

Thanks.

I also want to make sure I am clear on your statement about restoring the latest versions of files. That is supported when restoring to the computer that initiated the backup. It's only when you are restoring to another PC where you either need to use Restore Only Mode or Sync the repository if you're planning to, say, move backups to a replacement PC and want to be able to retain what's already stored in the cloud. If your use case is the need to periodically restore a set of files on a second computer, then currently you need to use restore only mode or perform a sync so the second computer knows what is stored in the cloud. or, as I mentioned earlier, if the two computers are on the same network, you can issue the restore from the original computer and create a share on the second computer to receive the restored files - this will not require any additional steps regarding the repository.

The database is not stored in the cloud or with our Managed Backup service. It is stored with the agent on the PC where the backups occur. So there's no way for computer B to get the database on computer A unfortunately.

Having said that, I'll add a request feature to possibly do that in a future release. Thanks.

I am waiting for some information to better answer this post. Will like have the reply tomorrow.

When you plug in a removable disk, Windows assigns it the next available drive letter. Depending on what devices you plug in and remove over time, these automatically assigned drive letters can change. I do not know if this is the issue, but if you set the backup plan to back up to the D: drive because that's how the drive is normally exposed, and Windows assigns E: the next time the drive is plugged in, the local backup will fail. Can you verify the drive letter assigned in Windows matches what you are using in the backup plans? Also, you can assign a permanent drive letter using this method: https://www.groovypost.com/howto/assign-permanent-letter-removable-usb-drive-windows/

how is the USB drive exposed by the OS? Drive letter, mapped drive? Same drive attached to one server but accessed by both or do you move the drive?

where are you sending the local backups? Is it to a local disk or to a network share?

We can back up FreeNAS. All you need to do is create a network share and then use the Windows agent to back up all the files. Is that solution insufficient for your needs? If not, what is lacking in your opinion?
https://thesolving.com/storage/how-to-create-a-windows-share-with-freenas/

Do you mean a native agent to back up those operating systems? If so, I do not think so. In the meantime you can back up any NAS by simply exposing a network share and backing up the files themselves.

Sent as a direct message on forum.

It's currently scheduled for the 2.5 release.I don't have a release date yet.