![]() BlobTier Archive -File "G:\Video\Movie1.mp4","G:\Video\Movie2.mp4" BlobTier Archive -File "G:\Video\Movie1.mp4" ![]() Upload-AzureBlob -ContainerName video -DestinationFolder HomeMovies ` Possible Values: Īnd finally, some use examples: # single file Which tier of blob storage this file should be set to. If you have lots of bandwidth feel free to increase it. How many threads should upload the file. I like everything to be in a folder, so I kept that in mind when scripting this out. Name of the (virtual) destination folder inside the container. Name of the file or files to be uploaded. This script has just a few parameters, which are as follows: Parameter You can also find both versions of this script on my GitHub. UPDATE: The script previously located in this post has been updated in a later blog post.ĭon’t forget to copy in the name of your storage account (in the case of this demo I would paste “teststore700”) and the access key! Copy one of them for pasting into the script below. You will see two access keys provided for your account. Go back to the storage account menu and select “Access keys”. (click to enlarge)įinally, for the Powershell script to work, you will need a key to access the storage account. Clicking on the container will show you the container is empty, and you will see that you can upload files to it right through the portal interface. Your container will now appear in the list. Since I share my archives with no one, I make my containers Private. Give your container a name, and select an access level. Then click the “+” at the top to add a new container (click to enlarge) Click on the storage account, and then choose “Containers” from the menu on the left. Now we need to create a container within that account. Once created, your storage account will appear in the list. Select your subscription or create one if you need to, and do the same for your resource group. I like security, so I require secure transfers. ![]() Since I’m doing archiving, I opt for standard performance, and set the access tier to Cool by default. Choose whichever location you like, but realize that one which is closer to you will probably be faster. For all new accounts Microsoft recommends the “Resource manager” model. You’ll need to give it a name which is globally unique, so it may take you a few tries. Next, enter the details for your storage account. On the storage account screen, click “Add” In the Azure Portal, select “Storage accounts” If you don’t already have one, these are simple to create. Once you’re into Azure, you’ll need a storage account. If you don’t already have an Azure account, you’ll need to create one. Creating a Storage Accountįirst, log in to the Azure Portal. But if you’re new to Azure or don’t already have a storage account, follow along with me to get one set up. If you’re already an Azure pro, feel free to skip ahead. At this point, I decided to write my own method using Powershell, which I am happy to share below. While I found several third party tools that can upload files to the archive tier, none were free. The free Azure Storage Explorer client is no better. If one is using the Azure Portal to do this, there’s several clicks involved per blob. Once a blob is uploaded, it must explicitly be moved into the archive tier. While a storage account can be configured to have all blobs placed in either the hot or cool tier by default once they are uploaded, the archive tier is not an option. Rather than branding this capability as a new product, Microsoft decided to present it as a new tier of Azure Blob Storage, alongside the existing hot and cool storage tiers.Ī noticeable difference from the hot and cool storage tiers is that the archive storage tier is only available on a per-blob basis. My wish came true in Fall of 2017 when an archive tier of Azure Blob Storage was announced. As happy as I’ve been with Amazon Glacier since its introduction in 2012, I always hoped Microsoft would offer a similar service. Two of the products I use extensively for this purpose are Amazon Glacier and, more recently, Microsoft Azure Blob Storage Archive Tier. The tradeoff for this lower storage cost is that should you need to retrieve the data, it is not immediately available and you may have to wait a few hours. The ideal use case for these products, however, is that the data never needs to be retrieved at all, it is simply an additional copy being stored for safekeeping. As cloud offerings matured, products specific to archival were introduced that allowed for long-term storage at very low price points. Early on I realized that the cloud was a great way to protect all my photos, videos, and other digital keepsakes that I absolutely could not stand to lose. As a former DBA, it should be no surprise that I am a big fan of keeping data safe, and not just corporate data – this extends to my personal data as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |