Dropbox announced a new initiative at their Open conference on Tuesday called Project Infinite. Project Infinite utilizes a new interface that allows users to see all of the files they have stored in the cloud within their machine’s file explorer. Users will not be required to keep local copies of each document, image, spreadsheet, or other data file, everything stored in Dropbox will be readily available regardless. Just like with any locally stored files, users will be able to move and manage their files in the cloud by moving them around inside the Mac OS X Finder or Windows File Explorer.
The current Dropbox format hasn’t changed much since its initial launch around 7 years ago. This new initiative is a big move for the company as well as the cloud reliant community. Project Infinite would build upon the original functionality of Dropbox and allow users to work with a greater volume of files, without the added hassle. As with anything else, a lot has been left unanswered when it comes to Project Infinite. Dropbox won’t say when it plans to incorporate the new version into the publicly available version of its desktop applications. In addition to the lack of a launch date, the company has not released which customers will be able to use Project Infinite once it does launch.
Dropbox has also released a new File Properties API that allows third party involvement. Users will now be able to apply custom metadata to files stored in Dropbox, enabling security applications such as data migration services and digital loss prevention services.
Dropbox has entertained the idea of paid cloud storage, trying to persuade businesses to choose Dropbox over other cloud storage options. Pushing hard for commercial adoption leaves the possibility that this new interface may be completely unavailable without subscription.
Guess we’ll just have to wait and see.
If you would like to educate yourself in more detail about the information presented in this blog post please visit: Dropbox wants to stretch desktop file storage to infinity
If you are using Hyper-V virtual machine, with thin provisioned (or dynamic) virtual disks, you may find yourself needing to compact those virtual disk files (.VHD) to reclaim free space.
Typically you would compact a virtual hard disk in situations such as the following:
- After you install the guest operating system (which uses many temporary files)
- After you delete large amounts of data
- When you are preparing the virtual hard disk for archiving, for deployment to another computer or CD-ROM, or for distribution
To ensure that you get the smallest possible file size when you compact the virtual hard disk, you need to do some file system maintenance before you compact the disk. In the guest operating system of the virtual machine that is using the disk you want to compact, do the following:
- Remove any temporary folders or unwanted folders or files.
- Empty the Recycle Bin.
- Defragment the disk.
Note that when running a defrag, you will actually grow the .VHD file prior to compacting, so make sure the host server has enough free space to accommodate it.
Shut down the VM, then go to the settings and go to the disk settings and click edit. This will bring up the disk edit wizard and the keep the first selected option, Compact.
Depending on the size of the .VHD file, and the available “white space” within the file, compacting may take a significant amount of time. So be sure to plan your downtime accordingly.
You may receive the error message “The system failed to compact disk.vhd. Error Code: The requested operation could not be completed due to a file system limitation” when attempting to compact the .VHD file.
First, check to see that there are no VSS backups on the VHD by running a “vssadmin list shadows” command in an elevated command prompt.
Second, delete any VSS backups that are present by running “vssadmin delete shadows /all“. If this fails to delete the VSS backups, you may need to resort to the “DiskShadow” utility in WS2K8 and WS2K8R2. (There’s some more information on DiskShadow here (free registration required) and also here.)