Here Comes Another Azure Drive

By -
I have been using Gladinet Cloud Desktop to map a network drive to the Windows Azure Blob Storage, backing up documents, moving files from PC to PC. The Azure storage looks to me just like another network share on the LAN. If you ask me, where is your Azure Drive? I would point to the Windows Explorer on my local PC.

explorer_380


Now here comes another Azure Drive, Microsoft just came out with a beta release of the Windows Azure Drive. As quoted from MSDN,
“Customers have told us that they want to take their already running Windows applications and run them in the cloud using the standard Windows NTFS APIs, and make sure that the data is durable.   With Windows Azure Drive, your Windows Azure applications running in the cloud can use existing NTFS APIs to access a durable drive.   This can significantly ease the migration of existing Windows applications to the cloud, enabling customers a more seamless migration experience while simultaneously reducing the amount of time it takes to move their applications from your own Windows environment to a Windows Azure environment. The Windows Azure application can read from or write to a drive letter (e.g., X:\) that represents a durable NTFS volume for storing and accessing data.  The durable drive is implemented as a Windows Azure Page Blob containing an NTFS-formatted Virtual Hard Drive (VHD).”  - Quoted from MSDN
So what is the difference between the two Azure Drives? The key is to point out where they exist. The Microsoft Azure Drive is not local to your PC while the Gladinet Azure Drive is local to your PC.

The second difference is the purpose of the drive. The Microsoft Azure Drive is for application migration. If you have a Windows app using NTFS APIs, you can continue to use NTFS APIs when the app runs inside the Azure Virtual Machines.   Conceptually it is similar to Amazon’s Elastic Block Storage (EBS) for the Amazon EC2.  The Gladinet Azure Drive is for data migration. Since the drive is mapped locally, you can do drag and drop to transfer files to Azure Blob Storage. 

The third difference is the audience. The Microsoft Azure Drive is for developers. You will need to use specific API (Azure SDK Feb. 2010)to mount the drive inside the Azure VM. On the other hand, the Gladinet Azure Drive is for regular user that needs to use cloud storage to store and backup online content.
The two Azure Drive implementations are two sides of a coin, one helps on application migration, the other helps on data migration to Azure. One helps developer and the other helps regular user to use Azure. One lives remotely in the Azure cloud and the other lives locally, connecting your PC to the Azure cloud.

Related Links:
Use Azure Blob Storage From Windows Explorer

Comments

ABC123456 said…
I am a happy Gladinet user and gladly paid for the software. But why do you show screenshots from the 2.0 version? This is misleading, as I understand it is still only for internal use. The 1.4 version lacks a lot of features, like storing files on google docs without having to convert them

So please - use real screenshots from public versions - or better - release 2.0!
February 19, 2010 at 8:58 AM
Post a Comment

Popular posts from this blog

Access and Backup to HP Cloud Storage

By -
Image
Today HP moved its cloud services to public beta. Gladinet has been working closely with HP Cloud Service since private beta to provide product integration support. Gladinet is also announcing today the support of HP Cloud Storage service with the full Gladinet Suite of products. In the latest Gladinet Desktop Client, you will see the HP Cloud drop down, which allows you to attach your HP Cloud Storage account into Windows Explorer as a mapped network drive. At the next screen, you can enter the related HP Cloud account information.
Read more

7 Biggest Limitations of SharePoint Online And How to Fix Them

By -
Image
SharePoint benefits encourage businesses to migrate their file server data online. However, there are at least 7 limitations of SharePoint Online and OneDrive that need to be effectively addressed to reduce migration costs and eliminate OneDrive sync failures. In this article, we'll identify some of the common issues that complicate SharePoint migrations and ways to simplify the migration and solve the issues. Here's a list of common issues: 5,000 item limit in a document library 100,000 item sync limit for the OneDrive client NTFS permission reorganization requirements Maximum name length limitations Prohibitive costs of data reorganization 93 day recycle bin threshold Lack of support for legacy application data (databases, etc…) Obviously, you may not hit every issue in each migration but migrator beware if there's a lack of awareness of how these limitations could impact user experience, productivity, and cost. A Real-World Example Before we discuss each of these items
Read more

Optimizing 3D Rendering and AutoCAD Performance in Remote Work Environments

By -
Image
Introduction: The Challenge of Remote Work Whether you are a design company or an architecture firm , you'll find that managing large 3D and AutoCAD files across remote team members creates performance and collaboration issues. This article introduces CentreStack as the one-stop solution for transforming your remote work experience. Identifying the Obstacles in Remote 3D Rendering and AutoCAD Usage The Challenge of Distance Data must traverse long distances when working in separate locations, introducing latency issues that hamper real-time collaboration. The Burden of Growing Files Technological advancements in 3D rendering tools and AutoCAD have led to larger file sizes, making performance even more of a challenge. The Downside of VPNs and Cloud Storage Solutions Traditional VPN technology has become more sluggish over time despite hardware upgrades or additional bandwidth. Common cloud services like Dropbox, Google Drive, and SharePoint aren't optimized for AutoCAD file typ
Read more