Glad to hear that it completed. Let me offer alternatives to Glacier that will keep costs low for you. You can store data in Wasabi or Backblaze B2 for $5-6 per TB in hot cloud storage.

I recommend you consider using a different storage class than Glacier or use a different storage vendor with pricing that works for you. My feeling is this is a combination of Glacier and the number of files stored. Did you happen to run the AWS calculator in advance to see the restore costs for Glacier?

Just curious where you are located in relation to the AWS Region you are using. Is it close?

Can you verify what versions you're running at both ends. You might want to just try cycling the service on the remote side see if that fixes the issue.

users are only authentication accounts and don't have to be real people or if actual name is assigned to them. I'm authentication user ID is sufficient. They are assigned to a customer and used to authenticate the agents at that customer in the system so they can be managed properly at the MSP. Administrators are only users that need access to the management console.

Seems to be running slow, but it's hard to know if it's an issue with Glacier, latency, or another issue. If you were running the restore for 12 hours, that would be about 3.6 seconds per file, while might be the maximum speed. Also, the free version is limited to a single stream - so you might see faster restores with the full version.

You should also start using the newer backup format available in the 7.x release. This new format bundles data from multiple files in larger archives to facilitate reducing the the IO and latency related to backing up lots of very small files. There is no conversion for this if you're using the legacy format, You would need to create a new backup plan - and you should start using S3 Glacier instead of legacy Glacier. Create an S3 account and then you can select Glacier as the target storage class on the Compression tab in the backup wizard.

So I tried it and it is clearly not supported. The message is a little confusing, and I'll have to ask the team to update. Still hoping for a use case explanation. Thanks.

Are you saying you are trying to add the same account to both Users and Administrators and the management console is barking at that with the "Busy" message? I've never tried that, but I will now.

Having said that, can you explain what the user case is that you're working from that you want the same email in both places? Generally speaking, a User account is an authentication account for a specific customer and administrators are Techs at the MSP (or possibly an IT user at a customer).


Thanks.

Your employees need to have a special build created for them. Here's a video that explains, but I'll go through the process for you here as well: https://www.youtube.com/watch?app=desktop&v=nupwq6cvDZY

The main installer you see in Downloads at the top section is only for you, the admin - and for any other admins that need to connect remotely to other computers in the office. Install this build on those PCs.

Next, go to Organization - Companies and create a single company for your business. If you're using this internally, you'll only need to do this once. Click Add Company. Then go to Downloads and click the Remote Computers Installation button. Here, you'll set the duration you want access to the remote computers - you can select a term as long as a year. Select the company you just created from the list. Set the options for Proxy, Incoming Connections, limitations on what you want your end user to be able to do, lastly, select the Security options for PIN Length, whether you want PINs to rotate on a schedule for better security, and whether you want to be able to do Unattended Access to these remote PCs. On that last part, you'll need to enter a password.

Lastly, click the Generate Installation Script option and you'll be presented with a link to download the remote computer installer with the options you just selected built in. You can install this build on the remote PCs. As an alternative, you can use the script in the second text entry to apply settings using the regular installer you downloaded and installed on your own PC. Using the /S option causes a silent install if that's how you want the remote agent installed.

Once installed, you'll see those remote computers listed.

The reason the product is designed this way is because we sell a lot to Managed Service providers with many customers who need individualized security settings and expiration options. If you select 1 Year for expiration, you'll only need to reapply the remote agents once a year - or as we release new versions. Settings are not saved anywhere, so if you use a password, then you'll need to securely store it somewhere. You can also redo settings if, for example, one of your admins left the company and you wanted to be sure they could not longer remotely connect.

If you're using Managed Backup, Remote Desktop is integrated into that management console in the Remote Management section, so the console.msp360.com web site is not needed. But I did not get the sense you are Managed Backup customer.

Regarding your other questions:

Each person / admin who requires remote access needs a license. Each license allows unlimited remote connections. So, if you had two admins that need remote access to any of the 14 computers, then you need two licenses at $35 / Month / Admin * 2 = $70. There is discounting, so the total cost will be less. Annual contracts also have a 20% discount on top of the normal discounting.

Can you clarify what product you're using? Is it Drive?

How much data are we talking about? Restoring from Glacier can be very expensive, especially for testing under these circumstances. If it's not a lot of data, consider re-uploading to S3 Glacier and when you're certain the data is successfully stored, delete your old legacy Glacier vaults.

I am guessing then that it is a limitation in the freeware version. Based on the data provided, the upload would take about 17 minutes at maximum speed for that 206 MB, assuming full bandwidth use of the 2 Mbit upstream speed and no latency. I would expect general internet / S3 latency and additional S3 I/O related to object creation and completion to add similar overhead when uploading using a single thread. I'd just wait it out and it should complete soon. The other option, obviously, is to upgrade to Explorer Pro.

the preparation phase on Glacier side does not do any downloading. All AWS is doing is staging the data from Glacier to S3 so can effectively be downloaded by you. The newer S3 Glacier is a great solution for long-term storage and archival purposes. If you plan on doing any type of planned restores from your data, then I would not recommend you use Glacier as your target. If price is driving you to Glacier there are other options available to you that would provide hot cloud storage at a low cost. You can even consider using different AWS storage classes to reduce your storage costs over regular S3 Standard. The best thing I can recommend is try to wait it out. I've seen many reports from customers using our and competitive products over the years reporting that the preparation phase is taking longer than planned. I'm not exactly clear on how Glacier works under the hood, but I believe it may be preparing the entire vault to be downloaded. I don't know that you can simply grab a few individual files from Glacier and let it process just those files. I would check the AWS docs to see if they provide more information on actually what's going on.

I believe the free version uses a single thread, and because of that it may not update the status until the entire file is copied. Can you provide more details about the size and number of files that you're copying and also your upstream bandwidth?

I don't recognize that S3 storage class, but I don't think that should matter. Are you doing a file folder back up or an image backup. When you created the backup in version 7, assuming that's where you created it, did you just start the wizard normally or did you use the drop-down to select the legacy file folder back up format? The reason that's important is because the new file format archives a bunch of files together into a single file and then uploads those larger files to the cloud so the backups and restores occur more quickly. It's not a single file for the entire backup, but just a larger file overall compared to backing up thousands or hundreds of thousands of very small files individually. Depending on what's getting backed up using the new file format it's possible that all the changes fit into a single archive file and that's why you only see a single file moving up to the cloud.


The multi-threading is controlled in the options dialog I believe under advanced where you can see the number of threads. That will determine the maximum number of file streams that are processed in parallel.

As far as your version you say desktop, but I need to know if it's the free version or you paid for the pro version. The free version only supports a single thread to the cloud. Whereas the pro version supports multiple streams.

That process should normally take 4 - 6 hours. But I've seen customers that had to wait longer for Glacier to stage the data. If you start using S3 Glacier instead, you shouldn't run into this issue as an inventory is kept automatically in regular S3.

Thanks for reporting back, and let us know if you have any other questions.

Can you verify exactly which license you have? Can you also verify what type of backup you're doing? Are you using the new backup format?

We support glacier It's just through the new S3 glacier storage interface. It uses the same API as regular S3, and because of that it's much easier for us to support. It also leaves metadata in S3 about the inventory of files, so you no longer have to create a time-consuming inventory from good old-fashioned glacier. I'll have to check but I think you can target S3 Glacier directly even with the new version. But you could try that yourself if you want to see if that's where you want to put the files. If not then as I said you can use a lifecycle policy which you can set up from the product or on AWS directly to move the files to S3 Glacier.

https://kb.msp360.com/cloud-vendors/amazon-aws/s3-glacier-legacy-glacier-difference

when you try a restore it will prompt you for the decryption password and will try it immediately. As an alternative, you could use an AWS utility to copy the files locally then set up a new backup storage target to that local storage and re-sync the repository and then restore from there.

Amazon glacier as well as some other cloud storage vendors have been placed on legacy support. You can still use glacier using the new version through the S3 glacier interface by creating a lifecycle policy and having the data moved to S3 glacier even with zero day latency. But you can also re-enable the legacy account so you'll see glacier in the list using the information in this blog post. https://kb.msp360.com/standalone-backup/general/obsolete-storage-destinations

Are you also using OneDrive as your cloud target?