We're not using the "pure Glacier", just the storage class. Even then, the synthetic backup fails (support has told me that Glacier was the cause of the errors, and so I cannot use synthetic).

Anyways, thanks for the response for pausing the local backup. Looks like we'll have to figure something else out. Thanks!

Hello Matt, thank you for your response, and answering the question if a seeding an image-based backup is possible.

Our use case defines that we use Glacier for our storage, and so a synthetic full backup is not possible.

Is there a way to give the local backup precedence, effectively pausing the cloud backup? The worry is that if a cloud backup is taking a while (say, more than a week), then the local, image-based backups will not occur for that length of time.

Thanks for your response!

Thanks for the quick response!

When will that future update be scheduled for release? I've noticed that even hidden computers show up on the CB Remote Management app. Maybe hidden computers shouldn't show up on the app? Or have the functionality to delete computers? Should a disaster happen, I won't be able to reliably uninstall the software from the machine. Thanks!

Thanks!
I've synced the local repository, but now I get the "Restore limit is exceeded" when trying to sync the cloud repository:


Edit:
On further investigation of the above error, it seems the xml files are in glacier now because of the lifecycle policy applied through mspbackups.com . Doesn't seem that the software can restore those files. Guess I'm going to have to delete everything and start over since it would cost more to retrieve the configuration files.

Absolutely.

Client screenshot:


This adds up to 276.45 GB

CB web:


Amazon S3:


Not sure what's going on. Any help would be appreciated. Thanks!

Thanks David, that makes more sense from a managed level. Although I wish I could just upload straight to glacier without a lifecycle rule. Thanks!