How to Sync Azure Blob Storage with AzCopy
A couple of months ago, I wrote a blog about how you can sync files to Azure Blob storage using AzCopy. Today I got an exciting update from one of my issues for AzCopy on GitHub, AzCopy version 10.3 now supports the synchronization feature from Azure Blob storage to Azure Blob storage. This means you can now sync Azure Blob to Azure Blob using AzCopy. You can read more here: https://www.thomasmaurer.ch/2019/11/how-to-sync-azure-blob-storage-with-azcopy/Architectural Decisions to maximize ANF investment in HANA N+M Scale-Out Architecture - Part 1
Do you have a large performance-sensitive SAP HANA footprint in Microsoft Azure? Are you looking to leverage SAP’s native resilience solution? Is operational flexibility at the top of your mind? If so, then look no further. This blog covers and answers the above-mentioned questions with Microsoft’s newer (since May 2019) PaaS storage service in partnership with NetApp, called Azure NetApp Files (ANF). In this blog series, I will focus on the technical execution aspects of running SAP HANA scale-out N+M on Azure NetApp Files from a Solution Architect’s point-of-view. More specifically, I will focus on how a solution architect would design, build, and operate the infrastructure, backup/recovery, and HA/DR components for a 2+1 scale-out scenario running on RHEL OS.Blob SAS Token and Signature format
Hi, I was planning to use private endpoint for my storage account, but when copying the file by AZCopy I'm getting only feedback: "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature." I was looking for others and seems that incorrect formats seems quite common challenge but was not really able to find the valid solution. When running AZCopy from command prompt, some has replaces "&" with "&&" and so on. Is there general rule how the SAS Token should look like when using that on command prompt? Also I tested this URL on my browser and that only returned: <AuthenticationErrorDetail>Signature fields not well formed.</AuthenticationErrorDetail> One question is also, should it be possible to test on browser only?AzCopy 5.1.1 Release
Microsoft is pleased to announce the release of AzCopy 5.1.1, and have made the following updates in this release: Integration of Data Movement Library into AzCopy A request we get often is "how does AzCopy work?" With this release, we have now integrated DMLib into AzCopy, which allows you to see exactly how our transfer logic works. Please refer to our Data Movement Library page to learn more. We've also made the following improvements: Perform Blob and File uploads using a Write-Only SAS. When you use a Write-Only destination SAS, you must add the /Y parameter and remove the /XO and /XN parameters. Create a destination container, share, or table with Account SAS. During copy operation, show total amount of data transferred and average transfer speed. Use full path in verbose log instead of relative path. Journal file name has changed from AzCopyEntires.jnl to AzCopyCheckpoint.jnl. Download the latest release version and learn more about how to use AzCopy by checking out the Getting Started with AzCopy documentation. Read more on the Azure blog.
