I did something similar to this once, and it took 4 days to upload all of my data. They will copy the blobs into your storage account where you can decrypt the data and send you the hard drives back (probably packed with a lot less tape). What if you have a ton of data in Azure and you want to get a copy of it so you can run it through an analyzer on your local infrastructure? They will copy your blob storage from your storage account to your hard drives, encrypt it, and return the drives to you (again, probably with a reasonable amount of tape).Frankly, I don’t really have that much patience — I’m not a doctor. Let’s talk about the nitty gritty details (not to be confused with the Nitty Gritty Dirt Band).
Be sure to set your job up correctly so they don’t do it backwards!
Let’s look at the requirements for using this service: If you’re sending in drives to have data exported from blob storage, the only difference in the steps to follow is that you also specify the blobs to be exported.
You use the same Windows Power Shell 2.0 command to migrate content into or out of RBS, or to another RBS provider.
When RBS is implemented, SQL Server itself is regarded as an RBS provider.
Since that is irrelevant to Blob storage, I’m going to use 3.0. If you start looking on your start menu for “Az Copy”, you will be disappointed.
The download link gives you an msi called Microsoft Azure Storage It’s actually not in an obvious location – it’s added to your Start Menu as “Microsoft Azure Storage command line”.
You can also view the Bit Locker keys in the same tab if you have an export job. The list of regions currently supported is: East US, West US, North Central US, South Central US, North Europe, West Europe, East Asia, and Southeast Asia.
After this blog entry is posted, they will add new data centers.
The most recent version of Az Copy out in General Availability is 3.1.