Bootable USBs are universal and can be used on any machine. Just make sure you're creating it on one of the latest Windows versions.

Great! Good to know that. The issue shouldn't reoccur.

Seems like the emails don't reach you for some reason, we get the "invalid email address" when sending messages to you.

On another note, a new build has been released recently, so please update to 5.9.3 and please re-send the logs if the problem persists on the latest version.

Sorry, no updates yet.

Yeah, unfortunately, no ETA yet. We'll try to implement that in the nearest future, but it all depends on the priorities of our R&D.

You can ignore those "not equal messages", Sync and Compare functionality have been deprecated a couple of years ago, so I don't suggest to rely on it, it's provided "as is". If you can open the files and control sums are identical you should be fine.

Sorry, we need the logs sent to us via tools > diagnostic menu. That way we would receive proper log archive with all the required info.

Hi,

The answer to all three questions would be "yes".
Regarding the issue itself: I guess it would be better to properly troubleshoot this via the ticket system
Please send us the diagnostic logs via tools > diagnostic menu with the issue description and link to this forum thread.

That seems to be a known issue we're working on. To properly register it please send us the logs from the machine via tools > diagnostic menu. I'll provide some troubleshooting steps and if that's the issue I mentioned I'll be able to provide you the build with the fix.

Quick update on the situation: the bug seems to be quite random, so in case anyone encounters something like that again we would need the diagnostic logs from the software sent from the latest version for internal investigation by our R&D.

Hi!
Yeah, we're thinking of implementing something like that, so the plan is to display the upload date and actual last modified date for the files.
No release date yet, but it's on our road map.

It's always a good practice to keep the software updated to the latest version. Currently it's 5.9.2. The issue you mentioned might be related to an old bug which I believe was fixed in 5.7.

Oh, sorry, didn't notice that you're using Openstack, my bad.
Well, I'm honestly not that familiar with giving granular permissions in Swift, but pretty sure they have documentation on that. ACLs might help in that: https://docs.openstack.org/swift/latest/overview_acl.html

Well, most likely the software was simply able to re-upload that amount of data in that time. That's my only guess. Sending the logs to our support team via tools diagnostic menu after reproducing the situation would definitely help. You can do so via tools > diagnostic menu.

You should be able to get that working with the following policy:

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:ListBucketMultipartUploads"
],
"Resource": "arn:aws:s3:::mybucket",
"Condition": {}
},
{
"Effect": "Allow",
"Action": [
"s3:AbortMultipartUpload",
"s3:DeleteObject",
"s3:DeleteObjectVersion",
"s3:GetObject",
"s3:GetObjectAcl",
"s3:GetObjectVersion",
"s3:GetObjectVersionAcl",
"s3:PutObject",
"s3:PutObjectAcl",
"s3:PutObjectVersionAcl"
],
"Resource": "arn:aws:s3:::mybucket/*",
"Condition": {}
},
{
"Effect": "Allow",
"Action": "s3:ListAllMyBuckets",
"Resource": "*",
"Condition": {}
}
]
}

Of course, mybucket should be replaced with the name of your bucket for each user you create in your AWS console.

Search function is not yet available for Glacier, but it's on our road map. I've added you to the list of people to be notified upon it's release.

Hm, that is quite interesting, but I actually heard that ceph works much better in S3-like mode and most of our clients use it that way.

Synthetic algorithm is based on fusing previous backups and it looks like something is wrong with the chain of incrementals. I'd suggest to uncheck synthetic full option, run full backup and then you can actually enable synthetic full back again.
Make sure you're doing all of this on the latest version of the software.

Yeah, the IP belongs to Amazon, so it is a purely connection issue. Let us know if any further assistance is required.

Looks like in this case one of the revisions can't be found on storage side, maybe it was deleted manually.
If the original machine is intact I can suggest to make a new full backup and then re-try restoring that image again.