page_type | languages | products | description | urlFragment | ||||
---|---|---|---|---|---|---|---|---|
sample |
|
|
How to use the Azure Storage JavaScript SDK with read-access geo-redundant. |
redundant-storage-javascript |
In this sample, you will find the following folders:
- v10 - references Storage Blob SDK v10
- v12 - references Storage Blob SDK v12
If you don't have a Microsoft Azure subscription, you can get a free account before you begin.
Following prerequisites are needed to run this sample and verify that files are downloaded from primary storage:
-
Add your storage account credentials to the
.env.example
file and then rename it to.env
.AZURE_STORAGE_ACCOUNT_NAME=<ReplaceWithYourStorageAccountName> AZURE_STORAGE_ACCOUNT_ACCESS_KEY=<ReplaceWithYourStorageAccountAccessKey>
You can find this information in the Azure portal by navigating to your storage account and selecting Access keys in the Settings section.
-
Install the required dependencies in the console window by running
npm install
.
Steps to test secondary storage access:
-
Open a command prompt with administrator privileges.
-
Get the IP address of your storage account primary endpoint domain by entering the following command, replacing
STORAGEACCOUNTNAME
with the name of your storage account.nslookup STORAGEACCOUNTNAME.blob.core.windows.net
-
Get the IP address of your local host by entering
ifconfig
on Linux oripconfig
on Windows. -
Add an invalid static route for a destination host. Replace
<DestinationIp>
with your storage account IP address, and<GatewayIp>
with your local host IP address.Linux
route add <DestinationIp> gw <GatewayIp>
Windows
route add <DestinationIp> <GatewayIp>
- Create a storage account.
- Create a container.
- Upload a file to blockblob.
- Enter D to download the file or Q to quit.
This sample creates a new container in blob storage and uploads a sample file into it called HelloWorld.jpg
. It then checks secondary storage repeatedly until both the container and file have been replicated. The user can then enter D to download the file or Q to quit. If the file is successfully downloaded, the sample indicates whether it came from primary or secondary storage. When the user quits the sample, it deletes the container and file.
To run this sample and verify that files are downloaded from primary storage, we are going to:
-
Launch the sample from the console window by running
node index.js
. -
Wait until the sample reports that the container and file have replicated to secondary storage.
-
When prompted, press D to download the sample file and verify that it comes from primary storage.
To test secondary storage access, we are going to:
-
In the console window with the running sample, press D to download the sample file and verify that it comes from secondary storage.
-
Remove the invalid static route.
Linux
route del <DestinationIp> gw <GatewayIp>
Windows
route delete <DestinationIp>
-
In the console window with the running sample, press D to download the sample file and verify that it comes from primary storage.
-
Press Q to quit the sample and delete the container and file from storage.